As a core class mechanic? Yes. Domains have been relegated to subclass options.Did they take that away?
As a core class mechanic? Yes. Domains have been relegated to subclass options.Did they take that away?
It may be called a "subclass" now, whereas it wasn't in 3.P, but it is if anything more defining. Hardly a relegation.As a core class mechanic? Yes. Domains have been relegated to subclass options.
As a core class mechanic? Yes. Domains have been relegated to subclass options.
Phyrexians are supposedly deploying something called the Planebreaker which will physically connect all the planes and allow anyone to cross. It's been compared to the World Tree from Norse mythology.
This is a problematic choice for at least 2 reasons:Subclasses are core class mechanics in 5e. Every Cleric chooses a domain at level 1, and it's by far the largest within-class mechanical choice they'll make, influencing spell options, proficiencies and the channel divinity feature, as well as granting unique abilities. If that isn't a core class mechanic, I don't know what is.
To the question of including pantheons in the PHB, I'd lean against it, but I think whether they're there matters less than how they're presented. If the presentations is "Here are some lists of deities worshipped in specific settings. Ask your DM if any any of them apply to your game", then I don't see much of an issue. If it's "These are the gods of the D&D multiverse", that's much more problematic, as it's giving players expectations that will make homebrew worldbuilding an uphill battle for their DMs.
This is a problematic choice for at least 2 reasons:
1. It precludes doing anything else with subclasses
2. It precludes having more than 1 domain
You're thinking in needlessly constrained terms. Suppose, for example, your choice of deity provides access to 3 different domains - but you only get a mechanical benefit from having a domain if you pay an opportunity cost (that isn't all-or-nothing like picking a subclass), such as a feat or an attuned item.I don't think doing something else with subclasses would necessarily be impossible. Warlocks' patron/pact boon system essentially lets them choose one subclass from each of two categories. There's no reason Clerics couldn't do the same if the developers thought there was a compelling second category of subclasses.
As for multiple domains, the issue is that we presumably want domains to continue granting mechanical benefits, so having two is only going to be fair if the second comes with equivalent mechanical drawbacks (or if everyone's expected to have two).
You're thinking in needlessly constrained terms. Suppose, for example, your choice of deity provides access to 3 different domains - but you only get a mechanical benefit from having a domain if you pay an opportunity cost (that isn't all-or-nothing like picking a subclass), such as a feat or an attuned item.
Was reading this and didn't quite understand it, but I do now, you mean something similar to 3e domains?As a core class mechanic? Yes. Domains have been relegated to subclass options.
Basically yeahWas reading this and didn't quite understand it, but I do now, you mean something similar to 3e domains?
My ideal cleric would actually be someone that picks a subclass and a domain separately at 1st level with the domain granting spells, and some thematic abilities at later levels. The subclass would be things like war priest, shaman, or mystic which would change how you interact in combat, sort of the difference between divine strike and potent spellcasting.