D&D 5E Command spell as reaction

[MarkB]

The rules are not perfectly clear on this, so I guess you can expect to see different DMs ruling differently.

The rules do say that if you come out of hiding and approach a creature, it usually sees you. Even if you rule that the rogue is considered Hidden for sneak attack purpose despite that fact that he is seen now, the fact that the paladin can now see him will allow the Command held action to trigger, before the attack occurs.

 

[Hussar]

He's using it exactly right if the readied action is, "I cast command when I see the rogue." He's just adding in the perception vs. stealth to notice the rogue hiding, which is how hiding and perception work. If he notices the rogue hiding, the rogue will be unable to get the attack from hiding check and will be seen first. If he doesn't notice the rogue, then the rogue attacks before being seen. All you've just done is quote the rule exactly as he is using it.

Sorry, no. In order to cast a spell as a reaction, which is what readying does, you need to cast the spell first and then hold the charge as per the concentration rules.

 

[Caliban]

Why? If you fight a rogue that keeps hiding, your only way to be able to fight him effectively is readying actions.

Or remove their ability to hide. Stealth doesn't make you invisible, it make you unseen and if you change things so that they can't use whatever allowed them to hide, then they are no longer hidden.

This could be moving to a position where they have no cover to hide behind, or lighting a lamp/torch or casting light/daylight to remove the shadows/darkness they are hiding in, etc.

Or just dropping a Shatter on their last known position.

 

[Maxperson]

Sorry, no. In order to cast a spell as a reaction, which is what readying does, you need to cast the spell first and then hold the charge as per the concentration rules.

Try to show some understanding. Clearly he's simply using "cast" when he meant "release." It's a very easy switch to make without realizing it.

 

[Hussar]

Try to show some understanding. Clearly he's simply using "cast" when he meant "release." It's a very easy switch to make without realizing it.

Except that the paladin needs to take an action if he's trying to perceive the hidden rogue. You can't actually do both try to perceive the rogue and ready a spell for when you see the rogue. So long as the rogue's hide check beats the paladin's passive perception, the paladin can't see the rogue until the rogue attacks. So, it's always going to be rogue attacks first, which, if successful, will trigger a concentration check on the paladin. If the paladin retains the spell, then he can use his readied command and since the command is "approach", then the rogue spends his movement approaching the paladin.

 

[Maxperson]

Except that the paladin needs to take an action if he's trying to perceive the hidden rogue. You can't actually do both try to perceive the rogue and ready a spell for when you see the rogue. So long as the rogue's hide check beats the paladin's passive perception, the paladin can't see the rogue until the rogue attacks. So, it's always going to be rogue attacks first, which, if successful, will trigger a concentration check on the paladin. If the paladin retains the spell, then he can use his readied command and since the command is "approach", then the rogue spends his movement approaching the paladin.

Passive perception is always on, even in combat. Hide specifically calls that out. If the paladins passive perception is higher than the rogue's hide check, the rogue is seen. If the DM isn't using passive perception and wants to make it an opposed roll instead, so as not to gimp the players, that's perfectly fine as a ruling.