D&D 4E 4e needs a Definitive Guide

pemerton

Legend
The Rest/recharge mechanics (how to use/manipulate them to create the play experience you're looking for.
To me rituals are a lot like 4e itself - potentially AWESOME but so often mis-used or understood
I've pulled these two quotes out because they reminded me of a conversation with my players yesterday evening, after our session finished.

I'm going to write up a full session report soon, but the summary version is that four 27th level PCs, with 9 healling surges between them, having already fought quite a large number of above-level encounters (they started the "day" about half-way through 26th level), defeated a 31st level solo with two elite 24th level friends. They did so at the cost of 3 healing surges, and with only the fighter PC actually losing non-temporary hit points.

As we were reflecting on this outcome, some of us were expressing surprise at the idea, seen more than once on these boards, that 4e is based around a very strict "X on-level encounters between extended rests" baseline. Certainly at paragon and above, the PCs are close to unstoppable!

Another idea that came up from the players was that dailies are far from the be-all and end-all of 4e play, because (at least in our game) you only get to use them once per level or so!

We were also reflecting on issues for solos (eg the well-known problems with action-economy), at which point I showed them the 5e sphinx entry to explain the Legendary Actions rules for 5e. In the course of this, I had to explain to one of my players, whose only D&D experience is with 4e, that in 5e spells don't generally roll to hit but instead are save-for-half! Which in turn led to some discussions about why 4e (and some of its fairly obvious innovations) have been so soundly rejected.

One player, who reads ENworld from time to time, commented that there is enough uniformity to the adverse commentary on 4e that it must somehow be a reflection of something in the system (ie it's not just random bad experiences). It seems that so many people have managed to systematically misunderstand the system, its parameters, its uses, its outcomes.
 

log in or register to remove this ad

One player, who reads ENworld from time to time, commented that there is enough uniformity to the adverse commentary on 4e that it must somehow be a reflection of something in the system (ie it's not just random bad experiences). It seems that so many people have managed to systematically misunderstand the system, its parameters, its uses, its outcomes.

We've discussed this at great length. I think the area that is the most illustrative is the lack of grokking of how Keywords and the exception-based design philosophy are meant to work together.

Consider the AD&D and 3.x Fireball. These lengthy (unwieldy imo) spell descriptions are chock full of all kinds of exceptions embedded right into the spell itself. The mindset of the D&D player used to "casting spells" or adjudicating spellcasting was predicated upon interaction with this layout. Given enough time, somehow, this real-world book format was somehow then internalized as "magic" in the fiction of their gameplay.

Now consider any 4e Fire spell. It contains the Arcane and Implement Keywords. However, it also contains the Fire Keyword. This is absolutely fundamental as it is one of the two primary system components (the other being the math/noncombat resolution framework) for the exception-based design philosophy that the system is predicated upon. The 4e power statblock is meant to elegantly provide (a) only the necessities to facilitate minimal handling time in combat (single target or AoE, ranged or melee, action economy, etc) while also providing (b) the Keyword infrastructure such that when a player proposes an exception-based usage, the GM has the means to adjudicate the effect on the environment. The GM knows that Fire is "explosive bursts, fiery rays, or simple ignition." So if the player of the Wizard is in a Skill Challenge and wants to deploy the spell to ignite materials (for whatever reason), this is an exception (though clearly orthodox) to its standard stat-block usage. The GM uses the of-level math to determine a DC and the player rolls an Arcana check with the outcome being either intended effect (ignition for whatever sought end) or some kind of complication (perhaps still ignition but things may go pear-shaped because the fire/smoke becomes a hazard/impediment to be overcome).

Instead of this being intuitive/easily grokked because the Keyword system and exception-based design philosophy is comprehended, we get:

- "This powers system means there is no magic and/or martial characters are casting spells."

and/or

- "Players can't use any fire spells to cause ignition of building materials (etc) because the target line reads 'creatures'..."
 

We've discussed this at great length. I think the area that is the most illustrative is the lack of grokking of how Keywords and the exception-based design philosophy are meant to work together.

Consider the AD&D and 3.x Fireball. These lengthy (unwieldy imo) spell descriptions are chock full of all kinds of exceptions embedded right into the spell itself. The mindset of the D&D player used to "casting spells" or adjudicating spellcasting was predicated upon interaction with this layout. Given enough time, somehow, this real-world book format was somehow then internalized as "magic" in the fiction of their gameplay.

Now consider any 4e Fire spell. It contains the Arcane and Implement Keywords. However, it also contains the Fire Keyword. This is absolutely fundamental as it is one of the two primary system components (the other being the math/noncombat resolution framework) for the exception-based design philosophy that the system is predicated upon. The 4e power statblock is meant to elegantly provide (a) only the necessities to facilitate minimal handling time in combat (single target or AoE, ranged or melee, action economy, etc) while also providing (b) the Keyword infrastructure such that when a player proposes an exception-based usage, the GM has the means to adjudicate the effect on the environment. The GM knows that Fire is "explosive bursts, fiery rays, or simple ignition." So if the player of the Wizard is in a Skill Challenge and wants to deploy the spell to ignite materials (for whatever reason), this is an exception (though clearly orthodox) to its standard stat-block usage. The GM uses the of-level math to determine a DC and the player rolls an Arcana check with the outcome being either intended effect (ignition for whatever sought end) or some kind of complication (perhaps still ignition but things may go pear-shaped because the fire/smoke becomes a hazard/impediment to be overcome).

Instead of this being intuitive/easily grokked because the Keyword system and exception-based design philosophy is comprehended, we get:

- "This powers system means there is no magic and/or martial characters are casting spells."

and/or

- "Players can't use any fire spells to cause ignition of building materials (etc) because the target line reads 'creatures'..."

Unfortunately there is no section in the rules pertaining to this. I don't even see any indication that the designers INTENDED keywords to work in this fashion. I think it is probable that it was something they THOUGHT OF at some point, in passing, but that the primary intent for keywords was the purely mechanistic interaction with other game elements (IE vulnerability/immunity, other powers, items, feats, etc).

Regardless, they failed utterly to even mention the narrative function of keywords (which is more obvious, the DM describes the fire attack as FIRE, but still not ever discussed). More critically they failed to mention the use you describe, the extension of the rules into areas that aren't covered explicitly, the use of 'Page 42' and its ilk. It was a fatal oversight.

Personally I think the coherence of the objections to 4e has less to do with 4e 'weaknesses' and more to do with fan expectations for D&D. My experience is that most D&D players want to reproduce an EXACT experience with no variation. The details vary depending on when the player was introduced to the game, and there are certainly players that are more flexible, but the typical player is playing 'D&D' and they expect, just like Monopoly, that D&D will be a specific exact thing. Its irrelevant to debate with them or even speculate on why they have specific likes and dislikes.

That isn't to say that we cannot discern the areas that 4e could be improved on by looking at what people have said. I think some forms of complaints are largely spurious when considering 4e IN AND OF ITSELF as a game. For example I put the "classes are too much the same" complaint in this category. Its not a complaint about 4e, its a complaint that arises out of an expectation from a different game.

As for the whole thing with Rituals and being an area that 'needed improvement', I think my answer to that is that the text of the rituals themselves needs improvement. I also think that perhaps even using a scroll might want to be a trained only skill use, and that certainly casting a ritual itself should require training in the requisite skill(s). I think there might be more skills involved as well, though not TOO many. This would force ritual casters to specialize a bit and make things more interesting.

As far as the ritual text itself, I think ALL rituals should be scaling. Many of them are simply due to being a 'beat some DC' sort of thing (like Knock where you have to beat the DC of the 'lock'). Many others however don't have scaling effects at all. These rituals often suffer from becoming trivial at higher levels or are too powerful all around. The other thing that should have happened is that rituals costs should scale with results. If you are getting flying steeds from your Phantom Steeds, that's kinda expensive but getting an ordinary riding horse costs next to nothing.

I think the other thing is that rituals should probably be devised to be a bit more immediately relevant in adventuring. A lot of them ARE, but a LOT of them are pretty auxiliary and it seems to me almost like the design decree from on high was "rituals should never be required to make things work, they should always be an alternate way to do things". Obviously that inherently makes the whole system redundant.
 

MoutonRustique

Explorer
snip... design decree from on high was "rituals should never be required to make things work, they should always be an alternate way to do things". Obviously that inherently makes the whole system redundant.
That part struck me. I'd never actually connected that set of dots. If it is true (and, at the moment, it really feels like it is), it would explain so much!

Mind blown...

On the other hand - I think we're kind of straying from the point of the thread (my fault as much as anyone's) - I will thus try and refrain from further deviations. Like this one right here, that I'm doing right now.
 
Last edited:

pemerton

Legend
I think the area that is the most illustrative is the lack of grokking of how Keywords and the exception-based design philosophy are meant to work together.

<snip>

The 4e power statblock is meant to elegantly provide (a) only the necessities to facilitate minimal handling time in combat (single target or AoE, ranged or melee, action economy, etc) while also providing (b) the Keyword infrastructure such that when a player proposes an exception-based usage, the GM has the means to adjudicate the effect on the environment. The GM knows that Fire is "explosive bursts, fiery rays, or simple ignition." So if the player of the Wizard is in a Skill Challenge and wants to deploy the spell to ignite materials (for whatever reason), this is an exception (though clearly orthodox) to its standard stat-block usage. The GM uses the of-level math to determine a DC and the player rolls an Arcana check with the outcome being either intended effect (ignition for whatever sought end) or some kind of complication (perhaps still ignition but things may go pear-shaped because the fire/smoke becomes a hazard/impediment to be overcome).

Instead of this being intuitive/easily grokked because the Keyword system and exception-based design philosophy is comprehended, we get:

- "This powers system means there is no magic and/or martial characters are casting spells."

and/or

- "Players can't use any fire spells to cause ignition of building materials (etc) because the target line reads 'creatures'..."
This is what puzzles me about the current mantra of "rulings not rules". 4e seems pretty "rulings" focused, to me at least.

Unfortunately there is no section in the rules pertaining to this. I don't even see any indication that the designers INTENDED keywords to work in this fashion. I think it is probable that it was something they THOUGHT OF at some point, in passing, but that the primary intent for keywords was the purely mechanistic interaction with other game elements (IE vulnerability/immunity, other powers, items, feats, etc).

Regardless, they failed utterly to even mention the narrative function of keywords (which is more obvious, the DM describes the fire attack as FIRE, but still not ever discussed). More critically they failed to mention the use you describe, the extension of the rules into areas that aren't covered explicitly, the use of 'Page 42' and its ilk. It was a fatal oversight.
I think they clearly thought of it when writing the object-damage rules in the DMG.

Outside of that context, I'm not sure if they overlooked it, or rather if they just took it for granted as something obvious. As I've often pointed out, the Moldvay Basic fireball spell also mentions only damage to creatures, but we always took it as obvious that you can use a fireball to set things on fire!
 

keterys

First Post
That part struck me. I'd never actually connected that set of dots. If it is true (and, at the moment, it really feels like it is), it would explain so much!

Mind blown...
Note that rituals were excised from the rules entirely with Essentials, not part of any class or even referred to. When I was designing adventures, I had to ensure that I never assumed ritual use (since I had no idea what PCs might play the adventure) which did limit the scope of possibilities. At the same time, I didn't want any ritual to completely alter the way an adventure might work, since I couldn't expect DMs to cope.

It did lead to me putting in a boilerplate reminder about the two rituals that let you extended rest in the middle of the day, since everyone always wanted to use them. People _always_ conveniently forgot the restriction on Fast Recuperation (no, seriously, you can't have had an extended rest in the last 12 hours) and I just had to point out that Solace Bole was from Dungeon and if your character had it, hey, you were cheating (for the campaign, home use do what you want), so that's that ;)

Anyhow, I agree that rituals weren't the best developed part of the system. One thing that struck me particularly as odd was that there wasn't more crossover with magic items. After all, if one group has a passwall item and another has a passwall ritual, you can work around that quite easily.
 

This is what puzzles me about the current mantra of "rulings not rules". 4e seems pretty "rulings" focused, to me at least.
Clearly when there are very detailed rules in ANY given area of an RPG the average GM/player basically seems to assume (at least these days) that said game will be very circumscribed. If we haven't heard 1000 times that 4e "only allows what is in the rules" in some form or other I'm a rubber duck.
I think they clearly thought of it when writing the object-damage rules in the DMG.
Except of course that oddly created the opposite effect. By actually covering one set of common situations that would come up they didn't create an exemplar of how to apply the rules, they just created one more specific rule subsystem that handled those few cases and apparently begged for more. What needed to happen was there needed to be a chapter called "what is beyond the rules, how narrative drives your story" that pounded out about 50 examples of ways you could utilize the different rules elements contextually in your narrative. Clearly whatever imagination it was that sparked the days of early D&D LONGGGGG since fled away from the vast bulk of the community at some point and has to be awakened very explicitly if it is to be relied on.

Outside of that context, I'm not sure if they overlooked it, or rather if they just took it for granted as something obvious. As I've often pointed out, the Moldvay Basic fireball spell also mentions only damage to creatures, but we always took it as obvious that you can use a fireball to set things on fire!

Yeah, it wasn't any more present in earlier editions except sporadically.

Honestly, here's the difference. The 1e rules (as an example) are really so fragmentary and incomplete that they cannot serve as an all-encompassing guide to making rulings in a game. They can serve to rule on the things that they cover, a lot of common situations. They DO give 'advice' on a lot of other situations, and on DMing generally, and it is all very much based in narrative. The 'rules' as such are just little raisins floating in a narrative pudding. So people MUST focus on the narrative needs of the game. The DM's experience is one of being continually faced with situations that are either wholly unique or at least different enough from past situations to require some sort of ruling, and since there is nothing approaching the unified check sort of d20 system of 3e or 4e its always 'wing it'.

If you run 4e (and 3.5 too pretty much) you have a different situation where there are universal mechanics and you CAN stick pretty much to 'the book' in combat at least and something will keep happening, you can go to 'board-game mode'. You can just make it clear that you're only going to apply rules and not ever extrapolate and your job gets very easy and the game is skirmish combat with some sort of varying quality of dialog in-between. Its a terrible way to run a game (unless your players love to play just nothing but minis and don't really RP much). The thing is its the lazy way so it is the most common way.

So, we can clearly see where different experiences come from. I learned the brutally difficult art of running an OD&D game from scratch, with barely even any time as a player and at age 12. It GOT easy, of course it got easy after years, but it was still hard. So when I come along and start running 4e I just laugh and think to myself "great, this is easy, it takes me 5 minutes to make an encounter and I have keywords and page 42 and whatever for in-game when someone pulls out the stops" and it works and there's no 'board game' in sight because I'm WAY into my narrative that I know have a huge amount of time for and rules aren't going to get in my way. But then there's I guess some other guy that just always really wanted a rule for everything if he could find one, and now he can....
 

Remove ads

Top