• Skua@kbin.earth
    link
    fedilink
    arrow-up
    11
    ·
    1 day ago

    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

    • Cethin@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 hours ago

      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.

      • Skua@kbin.earth
        link
        fedilink
        arrow-up
        2
        ·
        8 hours ago

        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

    • jounniy@ttrpg.networkOP
      link
      fedilink
      arrow-up
      7
      ·
      19 hours ago

      Funnily enough, Shatter actually has a very easy solution: Objects just take the damage and that’s it.