Simple Bleeding Rules (3.5e Variant Rule)

Simple Bleeding Rules

This variant introduces rules for taking damage from bleeding and is meant for a darker-toned, roleplay focused game in order to make combat more dangerous, and encourage character interactions during battle aftermaths. These rules are designed to take as little time as possible away from the action while allowing a more realistic simulation of the dangers of wounds.

Whenever a character takes physical damage greater than (Constitution Modifier + Character Level) the wound they have suffered is now bleeding. A critical hit will always leave a bleeding wound regardless of the damage dealt, and creatures immune to critical hits will never bleed from wounds.

A bleeding character takes 1d6 damage per wound at the end of each minute until they receive a DC (12 + 3 per wound to be healed) heal check. This check takes one full minute to administer during which time the patient will not take bleeding damage (so once the check is passed the patient will not suffer any more damage) although a failed check will result in the patient taking damage as normal for that minute. Cure X wounds spells (though not their mass equivalents) can also be used to cure bleeding by expending 3 points of healing for every wound that is to be closed. Healing potions do not have this effect unless their full contents are poured onto the bleeding area.

Back to Main Page → 3.5e Homebrew → Rules

gollark: Fortunately it only jams itself with certain resolutions, but still...
gollark: I was thinking about automation-type tools, but this sort of thing seems a decent idea too, so I might just do that.
gollark: That might make sense (restricted to the relevant folders, not losg and random stuff, at least).
gollark: What's a good way to manage all my services and stuff in a reasonably centralized fashion (yes, I know this is pretty vague)? I run many random webservices (some run in docker, they're all behind a reverse proxy (caddy)), having manually installed them, configured configuration, and in some cases set up service files for them, but I'm worried about the hassle restoring all this stuff would be in case of server failure and backing up all of `/` just seems inelegant. What I eventually want is to be able to, if my server or drives fail, redownload some scripts/configs/whatever, run some simple commands, load a backup of the relevant data and restart things.
gollark: <@404675960663703552> Random kind of late interjection: Ryzen can do (not the registered kind) ECC memory, though probably not on all boards. There's an ASRock one with IPMI and stuff which supports it.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.