A forum for discussing and organizing recreational softball and baseball games and leagues in the greater Halifax area.
This definetly seem very intentional…
-
Funnily enough, Shatter actually has a very easy solution: Objects just take the damage and that’s it.
-
I'd argue you can 'see' the wall if you place something on it, like: - your hand - your frontline's hand (or some other body part) - a ghost's hand - flour, dust, tar, enemies' blood, coughing syrup, and other things that could stick to the surface - gecko, spider, and other creatures that wouldn't fall off; probably also your familiar
-
This post did not contain any content.
-
The problem is that the RAW implies only things considered creatures caught in the area take damage
-
Rulings like this annoy me. Like, if he had said "the spell is poorly written, because our intention is that a wall of force can be targeted by disintegrate, but you're right that that's not what the spell descriptions say", then I'd be able to respect that a lot more than what you describe him saying. Words are a slippery beast, and there will always be a gap between Rules as Intended and Rules as Written. Good game design can reduce that gap, but not if the designers aren't willing to acknowledge the chasm they have created
-
Crawford also rules that See Invisibility doesn't remove the advantage/disadvantage on attack rolls because it doesn't say so in the spell's effect, so... Yeah, I always ignore what he says.
-
The problem is that the RAW implies only things considered creatures caught in the area take damageI'm going to preface this by saying I am 100% in favor of using common sense, and I have always allowed players to damage objects with spells as long as it makes sense. For example, I probably wouldn't let a player "inflict wounds" on a locked door, but I would happily let them "thunderous smite" it. But in the spirit of this thread, if we're applying a rigidly narrow interpretation of the rules as written, a spell only does what its description says it does. Cone of Cold does not say it damages objects. It says it damages creatures that fail a saving throw. Yes, Chapter 8 says "Characters can also damage objects with their weapons and spells" - and indeed they can, if they use a suitable spell such as Fire Bolt or Shatter which can damage objects according to its spell description. Again, that's Rules Lawyer Jesse Pinkman talking, and does not represent my own beliefs or opinions.
-
I'm going to preface this by saying I am 100% in favor of using common sense, and I have always allowed players to damage objects with spells as long as it makes sense. For example, I probably wouldn't let a player "inflict wounds" on a locked door, but I would happily let them "thunderous smite" it. But in the spirit of this thread, if we're applying a rigidly narrow interpretation of the rules as written, a spell only does what its description says it does. Cone of Cold does not say it damages objects. It says it damages creatures that fail a saving throw. Yes, Chapter 8 says "Characters can also damage objects with their weapons and spells" - and indeed they can, if they use a suitable spell such as Fire Bolt or Shatter which can damage objects according to its spell description. Again, that's Rules Lawyer Jesse Pinkman talking, and does not represent my own beliefs or opinions.Who would win, Gravity Fissure vs small porcelain vase
-
As I have said in another comment, that is RAW not what would happen: "You can’t even cast it on something behind the wall, because you cannot target something (or someone) with a spell if they are behind total cover. Total cover is created by being behind completely behind an obstacle (like a wall). This counts even if the obstacle is invisible." Furthermore, because if you chose an invalid target for a spell, you’d still expend the spellslot but there would be no effect. So you actually spend a sixth level spell a lot to achieve nothing." It’s very much not RAI I'd say and I would likely handle exactly like you described, but the RAW was so wonky that I wanted to make the meme when I found out about it.
-
As I have said in another comment, that is RAW not what would happen: "You can’t even cast it on something behind the wall, because you cannot target something (or someone) with a spell if they are behind total cover. Total cover is created by being behind completely behind an obstacle (like a wall). This counts even if the obstacle is invisible." Furthermore, because if you chose an invalid target for a spell, you’d still expend the spellslot but there would be no effect. So you actually spend a sixth level spell a lot to achieve nothing." It’s very much not RAI I'd say and I would likely handle exactly like you described, but the RAW was so wonky that I wanted to make the meme when I found out about it.I guess you're talking about 2024 rules? Because old 5e rules are different and don't have this flaw.
