D&D (2024) Emanation damage point and linked exploits:

It would be harder because the rules state that OA’s are for foes. I know they changed the wording, but the section is 100% clear on the intent.
The fact that they changed the wording is strong evidence that the intent changed. If they did not intend to permit OAs against allies, why else would they have removed the language that restricted OAs to enemies?
 

log in or register to remove this ad

The fact that they changed the wording is strong evidence that the intent changed. If they did not intend to permit OAs against allies, why else would they have removed the language that restricted OAs to enemies?
RAI is right there: Combatants watch for enemies to drop their guard. If you move heedlessly past your foes, you put yourself in danger by provoking an Opportunity Attack.

I understand you can read the rules otherwise, but I won't do it that way at my table.
 

RAI is right there: Combatants watch for enemies to drop their guard. If you move heedlessly past your foes, you put yourself in danger by provoking an Opportunity Attack.

I understand you can read the rules otherwise, but I won't do it that way at my table.

I didn't mean my question to be rhetorical--I'm curious: under your reading, what change did they intend to make to the function of the rule when they changed the language of the rule?
 

I didn't mean my question to be rhetorical--I'm curious: under your reading, what change did they intend to make to the function of the rule when they changed the language of the rule?
I don't really care. I play at my table the way I like. WotC doesn't decide my enjoyment of the game.

My guess is they replaced enemy with creature because of some style agreement.
 




54 damage to each creature in the room for two LV 7 characters, you mean.

Not necessarily. It’s aoe which is a given, but the Druid only can hit about half his move speed since he has to move back to the barbarian. That’s 15ft. If an owl 30ft.

OA’s may further limit what you can hit. Always for the barbarian and anyone the Druid has flyby.

Note: 30ft of movement out and back likely only hits 2-3 creatures. 15ft out and back only likely hits 1-2.
 
Last edited:

You don't need to be a pilot or aerospace engineer to recognize that it's a very big problem if the door falls off an aircraft while sitting on the runway. Sometimes a problem in the rules is significant enough on its own to be unacceptable
You missed my point: We are NOT building boeings here. We are also not flying in boeings. These are abberant exploits of the system. You say these are significant problems that are unacceptable, but that is bollocks. They happen rarely and IF they happen, there are not 200 dead passengers, but one annoyed DM who can easily stop this exploit by their ruling. Playtesting should focus on the gameflow that happens commonly and at every table.
 

Not necessarily. It’s aoe which is a given, but the Druid only can hit about half his move speed since he has to move back to the barbarian. That’s 15ft. If an owl 30ft.

OA’s may further limit what you can hit. Always for the barbarian and anyone the Druid has flyby.
I was sure the owl got 60ft flight speed.
 

Remove ads

Top