D&D 5E Observations and opinions after 8 levels and a dragon fight

Line of Sight / Line of Effect are gone with 5e. So are absolute rules as written. We only have guidelines to adjudicate specific situations.
Playtest reports tend to indicate a surprised dragon is a dead dragon, so a CR 13 blindsense had better negating stealth in most cases ! To fool a legendary dragon's heightened senses, you have to be particularly devious, and a casual "stealthy SOP" shouldn't do the trick. A CR 3 blindsense can be framed as "echolocation" , for example, which could be foiled more easily.
I would certainly give my legendary dragon a big edge against being taken unaware when it is careful. To earn your chance at stealth, you'd better get it angry to reach out to you, stone shape, or gate into its lair.
 

log in or register to remove this ad

I'm beginning to think that this edition is more like Dungeon World than its own last two incarnations. That is, a lot of the rules/rulings confusion and whatnot disappear if you think more fiction-first rather than mechanics-first.
I'm not sure of this. For instance, there are quasi-simulationist DC rules, very finicky elements ...

Dungeon World doesn't have any of these issues.
You don't think DW has stealth issues? From what I've seen/read its the single most unclear and widely interpreted area of play. The rules in general rely very much on interpreting what "put somebody in a spot" means. Trust me, DW has plenty of rules that are vague in interpretation, there are even moves for which its unclear who picks the results! (Although maybe those are third party..I'd have to dig that up.)

In any case, I fully recognize that they are quite distinct games. I'm referring to a de- mechanization that seems to have occurred for 5e. That is, while we still have some conditions, we don't have very rigidly defined rules for a variety of possible states "hidden" being chief among them. The skill descriptions lean much more toward a DW-like "when you do X" interpretation than a more 3e/4e interpretation "if you are under conditions A, B, and C or D you may attempt to place condition Z on yourself. This requires a two-thirds action."

Personally, I feel like WOTC didn't quite have a grasp on how to write rules like thus. The lighting and vision rules are (IMO) the worst offenders here. Plain reading leads to a variety of gameplay interpretations that are nonsensical WRT real life. My best guess: they went for a long time without specifying anything about lighting and vision, and then tripped themselves up trying to codify "use common sense".

Most importantly, though. They did write the rules in a flexible manner so that groups can interpret or override them easily. That makes this far less of a problem than it could be.
 

Line of Sight / Line of Effect are gone with 5e. So are absolute rules as written. We only have guidelines to adjudicate specific situations.
Playtest reports tend to indicate a surprised dragon is a dead dragon, so a CR 13 blindsense had better negating stealth in most cases ! To fool a legendary dragon's heightened senses, you have to be particularly devious, and a casual "stealthy SOP" shouldn't do the trick. A CR 3 blindsense can be framed as "echolocation" , for example, which could be foiled more easily.
I would certainly give my legendary dragon a big edge against being taken unaware when it is careful. To earn your chance at stealth, you'd better get it angry to reach out to you, stone shape, or gate into its lair.

Well, yes and no. LOS is still in the rules, just not as clearly stated. Lots of spells, for example, require you to see the target. And the cover rules effectively recreate the LOE rules.
 

Well, yes and no. LOS is still in the rules, just not as clearly stated. Lots of spells, for example, require you to see the target. And the cover rules effectively recreate the LOE rules.
Not exactly. Some effects work if you see a reflection of your target. Some do not. Everything is meant to be ruled on a case by case basis, rather than using a blanket rule.
It may sound as "DM may I ?" style of play, but if the DM make decisions based on genre/level/table expectations, I believe it can yield to a better game (and throw a lot of charop abuse through the window).
Particularly, I think keeping a "level appropriate effects" view inherited from 4e help answering these questions in a consistent, balanced, apropriate way. In this light, dragon blindsight seems easy to adjudicate, as "defeating low-level / casual attempts at stealth". It informs the table that PCs shall earn their stealth, if they opt for this tactic. No "standard operating procedure" cheese, but really engaging the fiction, making tough choices, balancing risk and reward.
Of course, if you prefer rock solid, prescriptive, simulationist rules for sight, go for it and use a 3e based approach. However, nobody should claim he is right "by RAW". There is no RAW for perception and stealth.
 

It does says all that I wrote quite clearly. There is no other way to interpret it. If you feel like allowing Stealth rolls within range of Blindsight, have at it. If you believe your viewpoint is the way the rule works, I'd love to bet you money you're wrong. I'll allow The Sage to settle the bet.

Blindsight effectively negates Stealth within its range. Negates invisibility. Due to defeating both, it is better than sight. Continue to argue until The Sage settles it for players like yourself that are what....allowing Stealth checks within Blindsight range? Don't be surprised if most DMs don't allow it.

You are the one using the logical equivalent of "longswords laying eggs" because you are adding elements to Blindsight that don't exist. Basically, you are claiming that each stealthling can work against blindsight depending on how the creature's blindsight works. Yet individual entries for Blindsight on a per creature basis do not exist. It is a general ability given to a variety of creatures with no exceptions noted that I know of. So you adding exceptions is "longsword laying eggs" logic. Meaning you're adding elements that are not there while I'm saying "a longsword does 1d8 slashing damage" and it doesn't matter if it is cutting an orc with a tough hide or a thin skinned salamander, it still does 1d8 slashing damage.

To put it simply, Blindsight picks up on anything within its range regardless of whether that thing is hidden behind a rock, masked by an invsibility spell, moving silently with elven shoes, or clouded in a mist. Unless the ability says it functions against Blindsight, it doesn't stop Blindsight from detecting you within its range. As in it does exactly what it says it does. What it says it does is better than sight because spells and special abilities that work against sight don't work against Blindsight.

You choose to add exceptions that do not exist. And with that I'm done with this particular discussion as there appears to be no amount of logical discussion that will cause you concede that you are wrong. I imagine only an official ruling will do that. I doubt such a ruling will be made as it is unnecessary for 99% of the community that clearly understands how it works.
Actually, no, I never said anything about a case-by-case treatment of blindsight. Other people have, but I have not. I think it works the same for every creature that has it. I think it works as a substitute for sight because that's what the rule says it is. I'm adding no exceptions or stipulations, and I'm not claiming it does anything beyond what it says it does.

You, on the other hand, are arguing from the position that your conclusion is true. That's called circular logic, and it proves nothing. For a sound argument, you must start from premises that everyone agrees on (in this case, the words written in the rulebooks) and proceed toward your conclusion.

What you are trying to convince me of is that blindsight is the same as x-ray vision. You have given no evidence to support this, but instead you're accepting your own conclusion as a premise, while I'm telling you that your premise itself is flawed. There is nothing in the text that says you can see through solid objects. There are, on the other hand, comparisons to sight and echolocation in the text. I am not the one adding extra traits where they don't exist. I am following what I read in the books.

The blindsight entry says nothing about stealth, so there is no reason to believe it has any special interactions with stealth beyond the logical extension that invisibility and darkness (both of which affect vision) will not help you hide from someone with blindsight. It can also negate effects like displacement, blur, gaze attacks, and obviously blindness. But it's not x-ray vision. The ability to see through solid objects is a pretty big deal, so it stands to reason that they would explicitly mention that if it were the case.

There's a big thread about this on the Wizards community forums where pretty much everyone agrees that this is how blindsight works, not to mention that this is how blindsight has worked in every previous edition that has it (as well as Pathfinder), so I wouldn't go placing any bets if I were you.
 

While I agree with you, these terms have pretty specific game definitions which aren't necessarily the same as plain English ones. You cannot shoot through a bush, for example, at least not easily, thus in D&D terms, it's considered cover - there is a physical barrier blocking line of effect and line of sight between you an the target. Concealment only blocks line of sight. Fog is concealment, since it blocks line of sight, as is darkness. Invisibility is concealment as well. Any physical barrier though? That's considered cover.

Which makes sense to a degree. Trying to swing a sword at someone behind a bush is more difficult than if the bush is not there. It's not more difficult to swing a sword at someone with concealment, just harder to find them in the first place.

If they have "specific game definitions", then I'm sure you'd be able to provide them, where they override the normal definition of the word?

Also, your examples do not imply a definition different than what I said above. Cover is any object that offers protection against physical attack, Concealment can be an object or area that prevents detection, but does not provide protection.

I.e., a bush could be considered cover against a sword attack, but not a crossbow. Masking odor, preventing visual detection, not moving, standing behind a sheet, etc are all forms of concealment, depending on the mode of detection.
 

If they have "specific game definitions", then I'm sure you'd be able to provide them, where they override the normal definition of the word?

Also, your examples do not imply a definition different than what I said above. Cover is any object that offers protection against physical attack, Concealment can be an object or area that prevents detection, but does not provide protection.

I.e., a bush could be considered cover against a sword attack, but not a crossbow. Masking odor, preventing visual detection, not moving, standing behind a sheet, etc are all forms of concealment, depending on the mode of detection.

I'm going to regret this, but, why would a bush not stop provide cover against a crossbow attack, if it was thick enough to provide cover from a sword attack?

And, cover has specific definitions - based on the percentage of the body is covered. Standing behind a three foot high wall provides some cover from a sword wielder standing on the other side of that wall. It would also provide some cover versus a ranged attack as well. It would not, however, provide any concealment.

That being said, I don't think 5e provides any rules whatsoever for concealment actually. Being invisible means that attacks against you have disadvantage, but, it doesn't mean that you are hidden.
 

I'm going to regret this, but, why would a bush not stop provide cover against a crossbow attack, if it was thick enough to provide cover from a sword attack?

Try slashing at a target behind a bush. Then try to shoot a crossbow bolt at a target behind a bush. Basic physics here. With a slashing strike, you have to go hit pretty much every branch in the way. Something small like a bolt, going forward, has a very real chance of not hitting any significant branches at all.

And, cover has specific definitions - based on the percentage of the body is covered. Standing behind a three foot high wall provides some cover from a sword wielder standing on the other side of that wall. It would also provide some cover versus a ranged attack as well. It would not, however, provide any concealment.

Nothing in the rules contradicts what I defined each as above. Cover can also provide concealment. concealment doesn't also provide cover. I don't see how this is all that complicated. The definition of each word is easily available to everyone.
That being said, I don't think 5e provides any rules whatsoever for concealment actually.

So these "specific game definitions" you claimed don't actually exist? Alright then.
 


Is your bush tall and fat or short and skinny? Lol it depends on the bush. Some bushes you wouldn't even see through nor would an arrow make it through. Pretty poor argument IMO.
 

Remove ads

Top