Skip Navigation
30 comments
  • You gotta have your game plan for why the curse isn’t solvable

    Maybe it’s a disease, not a curse. Maybe it’s an evil magical sword, but it’s not cursed per se, it’s just an asshole. Maybe the magic that operates the McGuffin is set to detonate like a bomb if you make an attempt to disable it. You can feel the balance of energies, such that a slight slip will release an incredible conflagration. Do you really want to continue? You’ll have to do a wisdom check with a pretty high DC. If you’re down for that though, you might be able to remove the curse.

    Yeah I know that’s not what it says in the books. This amulet isn’t from the books. Do you want to keep going with remove curse? Or try to find another way?

    There are always solutions. Remove Curse is bullshit; IDK what they were thinking with it. But yeah you just gotta plan ahead a little bit. Let your players still have their agency; don’t just declare that it doesn’t work (unless you all wanna agree to house rule that it just doesn’t exist or something). Just plan your way around it. Best case is something like your players looking for some way to buff their wisdom enough so they feel confident taking on the Remove Curse, and then you all get to find out what transpires.

  • Counterpoint: The overwhelming majority of curses are either crippling or a complete nonissue. Something like mummy rot will quickly kill a character, and curses that impose penalties on stats or rolls either affect something they use, making the character almost useless, or doesn't, so doesn't matter. If you don't want the party remove cursing a specific curse, just make it more powerful than them.
    Counterspelling is bad for a similar reason curses are bad, not remove curse - the overwhelming majority of counterspelling mechanics make it either too easy to too hard. Too hard and it's just not worth trying, and too easy makes combat a matter of who has more casters.

30 comments