I’m currently working on my next Two Page Mini Delve, and I’m going to be including a combat with a giant spider. I wanted to simulate, as best as I could, how a spider catches its prety. The spider web fit into existing rules structure as a “trap” with no problems. However, when I came to the part where a spider injects its prey with a paralyzing poison, I got stuck. Yes, there are plenty of poisons in the game, but I didn’t think the rules for them were dynamic enough. The basic poison template is: Ongoing X poison damage, and (sometimes) the target is [status effect], save ends all. That’s not what I wanted, for several reasons. What I wanted was something that represented rapid deterioration of muscle control, not “ongoing damage and status effect, save ends.” So, I kept looking. I found some monster poison attacks (spiders, specifically) that were a little closer to what I wanted – a secondary effect after the first failed saving throw. Better, but not quite. Finally, I found a solution to my problem, but not in the poison stat blocks.
So, what if we treated poisons a little differently? What if we treated poisons as a kind of disease? Honestly, they act in similar ways. They both attack the body, and slowly (or quickly) break down its ability to work properly. When I think about poisons in a disease stat block, immediately I see three advantages.
First, by turning a poison into a modified disease, you’re getting rid of the “save ends” mechanic for something better. Instead of all PCs saving against the effect roughly 55% of the time across the board, you’re now taking into account the character’s constitution score because you’re using an Endurance check instead of “save ends.” Doubling the character’s poison resistance as a bonus to the Endurance check further reinforces a character’s ability to resist the effects of a poison.
Second, by stacking three status effects (or more) on a disease track, you can actually make a broader range of poisons that do all sorts of different things. There are only a certain number of single status effects that you could apply to a traditional poison stat block, but if you put them in combinations of three, you get (not doing the math) a LOT more possibilities. And with a disease track, you can do more than status effects. You could make the poison do increasing damage. You could penalize to hit or defenses. You could even have a “no effect” stage just before you drop the hammer, creating a sense of drama and tension for your players. Bear in mind that you can still include “ongoing” poison damage by including a flat poison damage amount at every stage.
Third, by adjusting the frequency of the Endurance check, you can simulate the speed at which a poison works. For example, a fast-acting poison could require an Endurance check at the end of every round. A very slow acting poison would look a lot like a disease, requiring a check after each extended rest.
By way of an example, here is a (working) copy of what I will use for the spider’s poison in the next Two Page Mini Delve:
A note on bookkeeping
Having said all that, I feel I need to clarify something. I don’t think that this is how all poisons should be treated. In particular, I don’t think that PCs should have access to this type of poison, mostly because there’s an administrative burden placed upon the DM when they have to keep track of which monsters are where on their respective poison tracks. So I do understand why PC accessible poisons were simplified.
“Disease-like” poisons like this should remain squarely in the DM’s toolbox as one more thing that can add flavor and variety to a battle. If you want a poison to be a setpiece in an encounter (combat or otherwise), make it more dynamic and threatening than just another ongoing damage and status effect. Try a disease track – I think you will find that it’s exactly what you’re looking for.
What do you think? Is the “first failed save” mechanic enough for monster poisons? Or would you use a disease track?