title says it all. I know it says on the Undead traits that
"Undead are immune to any effect that requires a
Fortitude save (unless the effect also works on objects
or is harmless).", but what if the condition was forced without a save?
Undead are not immune to the sickened condition.
Well, does your sickening effect in question work on objects, since it's clearly not harmless?
The effect is from the dryad ability Tree Dependent:
(Su) A dryad is mystically bonded to a single, enormous tree and must never stray more than 300 yards from it. Most dryad trees are oak trees, but other trees function as well (often having subtle influences on a specific dryad's personality and appearance). A dryad who moves 300 yards beyond her bonded tree immediately becomes sickened. Every hour thereafter, she must make a DC 15 Fortitude save to resist becoming nauseated for an hour. A dryad that is out of range of her bonded tree for 24 hours takes 1d6 points of Constitution damage, and another 1d6 points of Constitution damage every day that follows—eventually, this separation kills the dryad. A dryad can forge a new bond with a new tree by performing a 24-hour ritual and making a successful DC 20 Will save.
It does require a fort save for the nauseated portion so the undead dryad would become immune to that, but the sickened happens automatically with no save so I was a bit uncertain as to how those interacted.
An undead dryad would still automatically be sickened, but would be immune to the nauseation and the Con damage effects.
Interesting. Sicken with a fort saving throw cannot affect undead. Sicken without a fort saving throw can.
Might have to add another houserule to add to my list.
Partial list of sickened effects without Fort saves (note this is cursory so might contain errors):
Touch of Evil (evil domain)
Camel's spit attack (druid companion)
Sickening Critical (feat)
Unholy Blight (spell; only if there is a good undead which there generally cannot be)
- Gauss
An... undead dryad? Is its tree undead too?
If you are the one making this thing, you might want to consider making a special variation where the dryad has to make a will save, and the damage is to charisma instead.
no the tree was destroyed, turning said dryad into a ghost. I am running a evil/monster campaign currently and this was someones character concept. I am reluctant to let him play it though mostly because hes just using dryad/ghost to stat stack when I asked everyone to make characters for a more political setting. I was just seeing if there was any rules on the thing that I was missing on a character audit.
This isn't an NPC? Just say no. It's smothered in cheese and reeks of pure munchkinism.
I think this is one of those cases where RAI trumps RAW. Undead cannot be sickened. They have no constitution and thus cannot get ill. Can you picture a skeleton holding its tummy and saying "I don't feel so good"?
Distracted by unending pain and disorientation due to the destruction of their home/heart. Angst-sickened. In this case I'd say the permasickened works.
Note that the actual definition of sickened is:
Sickened: The character takes a –2 penalty on all attack rolls, weapon damage rolls, saving throws, skill checks, and ability checks.
There's no mention of anatomy or stomach issues or anything similar. Some abilities use the standard name even if it doesn't perfectly match the fluff because the mechanical effects are right.
Note that the actual definition of sickened is:
Sickened: The character takes a –2 penalty on all attack rolls, weapon damage rolls, saving throws, skill checks, and ability checks.There's no mention of anatomy or stomach issues or anything similar. Some abilities use the standard name even if it doesn't perfectly match the fluff because the mechanical effects are right.
Yep.
By RAW, if you have a non-save, reflex save, or non-mind-affecting will save that causes sickened, then undead are subject to it. If you want, you can treat it as a disruption to the force that animates them, so that they can't move as smoothly, or something.
I would not allow a PC to have a ghost. I would not even let it get to the table.
|
Consider if you really want players stacking multiple monster types on each other; can't they be special enough with just one monster? Also, blending monsters has heightened risk of cheesy rule funniness.
Second, just because you're playing monsters, should you really be allowing every kind of monster? I'd be very careful with Incorporeal monsters, as it's a very powerful trait that grossly expands the things you can do (kill people without magic with impunity, they have no way of stopping you, walk through the dungeon walls). Likewise with Create Spawn ability; that could also get out of hand.