• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

Is Stealth the new Grapple?

The Free Action Complaint:
"Part of Whatever action you are trying to perform stealthily"
A free action typically doesn't hide you - it just means your free action was performed stealthily. Ie, nobody saw or heard you pick your nose, whisper to your friend, or drop an item (typical free actions.)

Not every stealth action makes you unseen. If you merely want to do something quietly (say, pick a lock) you use the stealth skill. "Part of whatever action you are performing stealthily" does not mean you are always unseen with every action. Sometimes it only means unheard, sometimes it only means avoid notice.

Hi redbeard. That's a fair ruling, but nothing in RAW directs you to make it. The only possible consequence for Stealth described in RAW is that under the Success caption. The FAQ is rather coy in what it tells you, but it certainly doesn't suggest that some actions will hide you and others won't.

If you do go this route, you are relying on your sense of fluff to say what should and shouldn't hide you. Free actions are left open as to what they include. Mine could be 'I take a free action to become hidden'. Well, why not?

-vk
 

log in or register to remove this ad

Now - in their turn, your enemies can make active checks. I admit there is an apparent inconsistency here.

On page 186:
Perception: No action required—either you notice
something or you don’t. Your DM usually uses your
passive Perception check result. If you want to use the
skill actively, you need to take a standard action or
spend 1 minute listening or searching, depending on
the task.

Which would seem to tell you that you need to take a standard action for an active check.
However, as the book says, Specific overrules general.
We have a more specific rule:

Page 281, Targeting What You Can't See:
Make a Perception Check: On your turn, you can make
an active Perception check as a minor action...

So it is only a minor action for an active perception check against an unseen (ie, hidden from view, stealthed) target.

However, the rules on page 281 also say that you only know that the creature is present if you make your minor-action Perception check, and only know which square they're in if you beat that check by 10 (which is nigh-impossible or utterly impossible if they beat your passive Perception in the first place).

So, do you ignore that part because your enemy isn't invisible, and allow the minor-action Perception check to break his hidden condition on a raw success? Or is the intent to use the +10 requirement when making a minor-action Perception check, and to use the raw check result only if you make it as a standard action using the rules on page 186?

This is what I was referring to earlier when I said there were debates as to whether to use the detection part of the rules on page 281 in full, in part, or not at all.

(Personally I favour allowing the minor-action Perception check to be a normal Perception check that will succeed if it beats the opponent's Stealth check - but that interpretation is not explicitly written anywhere in the rules).

It is a free action to communicate. If you're facing intelligent enemies, why wouldn't they?

That's not really the question. The question is whether telling someone a hidden creature's location (which they might already know - see the 'hiding behind a pillar' example) automatically allows that person to see the hidden creature as though they'd succeeded at a Perception check, or whether it simply allows them to target the hidden creature's square using the targeting rules from the second column on page 281, and leaves them granting the hidden creature Combat Advantage because, though they now have a good idea where it is, they still can't see it.
 

However, the rules on page 281 also say that you only know that the creature is present if you make your minor-action Perception check, and only know which square they're in if you beat that check by 10 (which is nigh-impossible or utterly impossible if they beat your passive Perception in the first place).

So, do you ignore that part because your enemy isn't invisible, and allow the minor-action Perception check to break his hidden condition on a raw success? Or is the intent to use the +10 requirement when making a minor-action Perception check, and to use the raw check result only if you make it as a standard action using the rules on page 186?

Here's my take, trying to use RAW:

The Targeting What You Can't See rules apply to something unseen.
However, the means by which a stealther in mere concealment/cover (not total) is unseen is through the successful stealth check.
Therefore, if the stealth check is beaten, the stealther is again merely in cover/concealment. No +10.

I think we agree the result is intuitive. What do you think of the use of RAW?

This is what I was referring to earlier when I said there were debates as to whether to use the detection part of the rules on page 281 in full, in part, or not at all.

The FAQ is clear that we need to apply them. A stealth success can be used to be hidden from view. The FAQ refers to "hidden" and equates it to "can't be seen" and the rules on 281. I hope that we can agree that "hidden from view" is equivalent to "hidden." ;)


Free Action to communicate and reveal a stealther:

That's not really the question. The question is whether telling someone a hidden creature's location (which they might already know - see the 'hiding behind a pillar' example) automatically allows that person to see the hidden creature as though they'd succeeded at a Perception check, or whether it simply allows them to target the hidden creature's square using the targeting rules from the second column on page 281, and leaves them granting the hidden creature Combat Advantage because, though they now have a good idea where it is, they still can't see it.

Good question.

Since the free action can occur at any time, the perciever can alert their allies as the other-wised stealthed attack is being made. Duck! Watch out! He's on the left! etc.
For my table, I'd assume that the information sent is enough to remove combat advantage and inform attackers well enough to degrade the -5 total cover/concealment to -2 cover/concealment.
 

Here's my take, trying to use RAW:

The Targeting What You Can't See rules apply to something unseen.
However, the means by which a stealther in mere concealment/cover (not total) is unseen is through the successful stealth check.
Therefore, if the stealth check is beaten, the stealther is again merely in cover/concealment. No +10.

I think we agree the result is intuitive. What do you think of the use of RAW?

It's pretty much there, but ambiguous enough to be a little dodgy. The fact that the action required for an active Perception check differs between pages 186 and 281 could be taken to imply that the minor-action Perception check is not a normal one, and is thus subject to the restrictions on page 281, even though we're not dealing with an invisible creature.

The main problem is that page 281 makes no reference to creatures that are merely hidden rather than invisible, so we've no clear guidance as to where or whether to make that distinction.

The FAQ is clear that we need to apply them. A stealth success can be used to be hidden from view. The FAQ refers to "hidden" and equates it to "can't be seen" and the rules on 281. I hope that we can agree that "hidden from view" is equivalent to "hidden." ;)

Oh, we're certainly agreed on that. What I'm not sure about is whether the FAQ's reference to page 281 is intended to suggest that you should use the entire section, including the left column which deals with detection, or only the parts in the right column which deal directly with targeting.


Free Action to communicate and reveal a stealther:

Good question.

Since the free action can occur at any time, the perciever can alert their allies as the other-wised stealthed attack is being made. Duck! Watch out! He's on the left! etc.
For my table, I'd assume that the information sent is enough to remove combat advantage and inform attackers well enough to degrade the -5 total cover/concealment to -2 cover/concealment.

That's a fair perspective. I prefer to stop a little short of that, granting allies a circumstance bonus (+2, possibly +5) to their Perception checks (active and passive) and letting them know which square the hidden creature is in if they still fail. But the whole "communicate to point out hidden foe" concept doesn't originate from RAW in the first place, so making rulings based upon it is largely a matter of individual judgement and guesswork.
 

Here's my take, trying to use RAW:

The Targeting What You Can't See rules apply to something unseen.
However, the means by which a stealther in mere concealment/cover (not total) is unseen is through the successful stealth check.
Therefore, if the stealth check is beaten, the stealther is again merely in cover/concealment. No +10.

I think we agree the result is intuitive. What do you think of the use of RAW?

I feel like the presence of much of the TWYCS wording in the Stealth rules block has implications. Any thoughts on those?

The FAQ is clear that we need to apply them. A stealth success can be used to be hidden from view. The FAQ refers to "hidden" and equates it to "can't be seen" and the rules on 281. I hope that we can agree that "hidden from view" is equivalent to "hidden." ;)

Darn, I'm going to be a pest. An action can be 'hidden from view' while an entity can be 'hidden'. There is a difference that works in plain English language.

Since the free action can occur at any time, the perciever can alert their allies as the other-wised stealthed attack is being made. Duck! Watch out! He's on the left! etc.
For my table, I'd assume that the information sent is enough to remove combat advantage and inform attackers well enough to degrade the -5 total cover/concealment to -2 cover/concealment.

Not quite any time. Only before or after an action, never during. That can make a difference.

You follow a very reasonable line of argument, but I want to urge you to either disapply line 1 of the stealth block and mandate that you set up your hidden condition with a separate action, and then work with it, or follow line 1 and contain stealth to performing the action stealthily. A lot of mechanical and interpretive difficulties are being caused by straddling this divide.

-vk
 

It's pretty much there, but ambiguous enough to be a little dodgy. The fact that the action required for an active Perception check differs between pages 186 and 281 could be taken to imply that the minor-action Perception check is not a normal one, and is thus subject to the restrictions on page 281, even though we're not dealing with an invisible creature.

Now, disregarding whether it's actually said in the PHB or not, would it not be entirely logical to assume that the rules for Attacking Unseen apply to those times when you know roughly in what square an opponent is, but can't actually see him.

The minor action Perception would take up less time than the "normal" standard action Perception check: For the minor action, you already know where to look, more or less. The standard action Perception check is for those moments when you look for hidden enemies about.

It's sort of a:
"He's somewhere behind those bushes." vs "He must be around here somewhere." (minor vs standard)

I find this entire discussion reasonably intriguing, and slightly surprised that people are a lot less inclined to follow their own common sense rather than taking printed rules and staying convinced they should be followed to however you believe they should be interpreted.

To a person against whom you are hidden: The enemy cannot see you. For all intents and purposes, you are invisible in regard to that creature.

A Sneak Attack occurs when the rogue is able to target vital areas of the target's body because the target is not actively defending them.
In combat, participants are assumed to guard those areas against foes they are aware of, or at least those in sight.
A rogue that attacks a fighter from behind (and from cover) would have attracted some attention from the fighter. Assuming this fighter turns around to face the rogue, he'd guard himself against the square in front of him and the two squares next to that. The rogue could resume hiding by moving through the concealment/cover with a stealth check, and assuming the rogue is able to more or less lap around the fighter without it noticing, another Sneak Attack would be called for.

Truth be told, I'd houserule a Perception bonus if the target attempts to hide while being observed, but that's not strictly necessary.

I suppose it'd be subjugated to some GM insight, but if a target knows roughly what square to expect an attack from (aforementioned possibilities of hiding behind a tree/pillar and sneak attacking every round with range, as well as the cover from an ally and a ranged sneak attack), that's not going to happen.
I would most likely say that common sense would dictate that any enemy who is aware of your approximate location would not be subject to your sneak attacks. Of course, 'approximate location' is something that can be interpreted freely, but consider that this is also highly dependant on range.
'Approximate location' can be the square in front of you or one the square to the left or right it, or one of the squares in the 5 squares long underbrush that's 5 squares away.

Yes, the exact rules on stealth and such *could* be very complicated. But I hardly think any game designer would assume that everything about his game would be completely understood by the gamers, mostly because some rules are unspoken or unwritten. The rules are a powerful basis for a game, but I don't think any of the rules should take precedence over common sense, if applicable.

Discussion about topics where insight and opinion play great parts, such as this one, is never going to get resolved. Rules from books have been quoted. That's about as far as you're going to get. The rest is speculation and throwing opinions against one another. (I've never been one to ignore a good and healthy debate, so I'm not saying it's a bad thing. Experience seems to point out, though, that such discussions are often long-lasting and without any conclusion)

Let's face it: Most people are going to either use the rules as written or use some house rules to handle stealth. And those rules will be different from person to person. Until WotC comes with any sort of official errata or additions to how this is to be handled, that's how it's going to be.

The rules say you can become hidden from view and/or become unheard/unnoticed if you use Stealth during whatever action you perform. If this involves concealment or cover, you could become hidden and become entitled to Combat Advantage against the target, as long as you keep the concealment or cover advantage right up until your attack.

Those are the rules. There's no disputing it. Whether they are entirely *logical* or *clear*, that's more or less the issue here. And when it comes to that, conclusions about the how, what, when and where will probably not be reached until WotC or some person from the DnD R&D team comes forward with an official errata, addition or statement or whatnot clarifying these things. already I'm starting to see this discussion go in circles...which isn't really helping anyone, right?
 

The rules say you can become hidden from view and/or become unheard/unnoticed if you use Stealth during whatever action you perform. If this involves concealment or cover, you could become hidden and become entitled to Combat Advantage against the target, as long as you keep the concealment or cover advantage right up until your attack.

Those are the rules. There's no disputing it. Whether they are entirely *logical* or *clear*, that's more or less the issue here. And when it comes to that, conclusions about the how, what, when and where will probably not be reached until WotC or some person from the DnD R&D team comes forward with an official errata, addition or statement or whatnot clarifying these things. already I'm starting to see this discussion go in circles...which isn't really helping anyone, right?

I'm getting that feeling too, but just to illustrate why this gets so complicated and 'those are the rules' isn't so clear, consider your first paragraph quoted above. There is no wording in RAW that states you can extend hiding past the end of the action you perform stealthily. Your first line correctly includes the 'during' qualifier, but your last line suggest you're thinking that hiding continues.

WotC_Mearls made an unofficial remark about this, that at the time I took on face value; in fact it's added confusion. RAW does allow you to make an attack stealthily. A: you gain CA. B: your attack ends stealth. A and B occur simultaneously.

But yeah, you're on the money saying this won't be settled until someone official publishes something comprehensive, but there is value in helping DMs decide for themselves until then, and in hopefully influencing WotC in their final rulings.

-vk
 

I think after reading this thread that the OP is spot on: stealth is 4Es grapple. Hopefully it will get officially settled shortly.

--Steve
 

You follow a very reasonable line of argument, but I want to urge you to either disapply line 1 of the stealth block and mandate that you set up your hidden condition with a separate action, and then work with it, or follow line 1 and contain stealth to performing the action stealthily. A lot of mechanical and interpretive difficulties are being caused by straddling this divide.

-vk


No.

Skills in 4th edition are too broad to be defined so narrowly. They are NOT 1 tool that can only be applied only one way in one situation.

Stealth can be used to:
duck behind cover in battle - resulting in a lasting condition
open a door quietly - only applies during the action
melt into the crowd at a market - applies during the action and results in a lasting condition
Whisper instructions unheard during negotiations with the Bishop - only applies during the action
Draw a dagger quietly after having successfully made a stealthy move action on a guard - an skill check to maintain a condition

Etc.
3.5 had broader skills than other skill games such as GURPS. 4th edition skills are even broader.

Other skills can be applied in different ways. Arcana can be used for an action, or for a knowledge check, or even for a magical skill (detect magic). Why, why do you make an exception for stealth?


Yes, that means the DM may need to adjudicate gray areas. That's why we have a DM.
 

I find this entire discussion reasonably intriguing, and slightly surprised that people are a lot less inclined to follow their own common sense rather than taking printed rules and staying convinced they should be followed to however you believe they should be interpreted.

When it comes to a game I'm DMing, I will indeed follow my own common sense - and I'll try to give my players a heads-up and listen to them if they disagree.

The trouble with this is that anyone who plays a stealth-based character in another DM's game - or even who plays in a game where the DM includes lots of stealth-based opponents - will have to learn and adapt to that particular DM's interpretation, and as we've seen, those interpretations vary wildly.

So finding out what the general intent of the rules might be is of some help for the moment - with a lot of luck, these debates may help inform whichever definitive interpretation WotC finally come up with. At the very least, they'll keep us familiar with the problems involved, so that we can quickly pick apart any remaining flaws in that version and get them corrected pronto.

I'm going to be interested to see how stealth is handled at the Living Forgotten Realms games in GenCon UK next month - but just for safety's sake, I won't be taking a rogue to those games.
 

Into the Woods

Remove ads

Top