Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!

Reply to thread

Message: <blockquote data-quote="(Psi)SeveredHead" data-source="post: 5883742" data-attributes="member: 1165">I've only seen an effect like that once (and it did kill a PC). However, it was a Fourthcore adventure that broke the guidelines (because it's fourthcore, of course). The victim had to make two immediate saving throws, and if they failed both, they died right there. The attack was an AoE!IMO, a death attack is kind of cheesy. There should be ways around it. I saw a post on the charnel firehouse (or whatever it's called) on another forum, as an example. It's a brute with a melee attack that inflicts ongoing fire damage. If it downs an opponent, it immediately gets to attack them again. So the victim, already at 0 hp or below, gets hit again (by a brute's attack), and if they weren't taking ongoing fire damage, they are now. Watch the party scramble to save the PC! Thing is, the party might be able to do it. They can try to heal the PC, or put out the flames/give another saving throw, etc. On the other hand, the raging battle might prevent it. The cleric was dazed and fighting for his life from a zombie swarm, or something.There are a few death effects. The catoblepas and orcus adept (not entirely sure about the latter's name) can inflict penalties to death saves. However, they cannot by themselves (without doing damage, that is) inflict the "death" condition. A death priest working with an undead brute would be a terror; the brute can drop a PC, and then the death priest can get near, while also trying to shut down the PCs' leader(s). Fear of death, risk of death, but not unstoppable sudden death.</blockquote>

Verification