I’ve never liked arbitrary spell targeting restrictions. I say if you want to fire blindly around cover or into a fog cloud you should be able to. It doesn’t come up very often and because it’s easy for players to understand that they’ll have a very high chance of missing and losing the spell slot.
I actually think it’s a fair restriction for spells that require sight. It imposes a somewhat interesting limit on casters, especially since a lot of spells still do something on a miss.
I think spells that target the spirit of a target shouldn’t be able to be fired blind - that’s what i would let it depend on. A cold ray doesn’t need a visible target, but everything mind affecting that is not AoE will need it.
Most of the time I think it’s because the spell calls for a saving throw and there isn’t a mechanic for what a wall’s Con save ought to be. That’s not a unsolvable problem by any means, but I assume that’s why the restrictions exist
But yeah, going with the flow at the table is much more fun. We can bodge a solution here. Roll it as a spellcasting attack for now
If I was doing it that way (which would be fine in my opinion) I’d want to do the same for other attacks like the fighter swinging a flametongue sword at whichever layer it is that needs fire damage. I just suggested the attack roll version because it brings it into line with other approaches
I’ve never liked arbitrary spell targeting restrictions. I say if you want to fire blindly around cover or into a fog cloud you should be able to. It doesn’t come up very often and because it’s easy for players to understand that they’ll have a very high chance of missing and losing the spell slot.
I actually think it’s a fair restriction for spells that require sight. It imposes a somewhat interesting limit on casters, especially since a lot of spells still do something on a miss.
I think spells that target the spirit of a target shouldn’t be able to be fired blind - that’s what i would let it depend on. A cold ray doesn’t need a visible target, but everything mind affecting that is not AoE will need it.
Most of the time I think it’s because the spell calls for a saving throw and there isn’t a mechanic for what a wall’s Con save ought to be. That’s not a unsolvable problem by any means, but I assume that’s why the restrictions exist
But yeah, going with the flow at the table is much more fun. We can bodge a solution here. Roll it as a spellcasting attack for now
In this case, it’s a fucking wall. Just ignore the saving throw and roll for damage. It’s not going to dodge your attack or anything like that.
For blind firing, yeah. You need to do something else. Maybe roll to see if/what they hit, then the target makes the saving throw if it makes sense.
If I was doing it that way (which would be fine in my opinion) I’d want to do the same for other attacks like the fighter swinging a flametongue sword at whichever layer it is that needs fire damage. I just suggested the attack roll version because it brings it into line with other approaches
Funnily enough, Shatter actually has a very easy solution: Objects just take the damage and that’s it.
The ever-reliable bardic frag grenade