Special Damage Effects (5E)

[jkeller]

https://forge.fantasygrounds.com/shop/items/2778/view

Automates support for various "on damage" effects. To use, simply select the "Feature: Special Damage Effects" when loading your campaign.

Adds support for "Absorption" effects. Attempting to damage some creatures with a particular damage type (e.g. fire for an Iron Golem) will instead heal it.

Iron Golem, Clay Golem, Flesh Golem
Shambling Mound

Adds support for "when damaged" effects. Most have been converted to auras in 2024, but a few remain:

Black Pudding (Corrosive Form)
Gray Ooze (Corrosive Form, but weapon damage only)
Fire Shield spell

Adds support for "Split" effects. For example, when a large or medium Black Pudding is subjected to lightning or slashing damage (or bloodied), it will be removed from the Combat Tracker and map, and replaced with two smaller puddings.

Black Pudding
Ochre Jelly
Troll -> Troll Limbs
Hydra

Adds support for "explode on death" effects. For example, when a Balor is killed, its Death Throes trait has it explode and do 9d6 fire + 9d6 force damage to anyone within 30 feet.

Balor
Magmin

History:
- fixed an issue where the clients were triggering duplicate on-death effects
- added support for "Fire Shield" spell
- 0.5: added support for on-death effects (e.g. Balor, Magmin)
- 0.4: added support for Hydras
- 0.2: check the pudding reaction before splitting; added support for troll limbs

[Farratto]

https://forge.fantasygrounds.com/shop/items/2778/view

Automates support for various "on damage" effects. To use, simply select the "Feature: Special Damage Effects" when loading your campaign.

Adds support for "Absorption" effects. Attempting to damage some creatures with a particular damage type (e.g. fire for an Iron Golem) will instead heal it.

Iron Golem, Clay Golem, Flesh Golem
Shambling Mound

Adds support for "when damaged" effects. Most have been converted to auras in 2024, but a few remain:

Black Pudding (Corrosive Form)
Gray Ooze (Corrosive Form, but weapon damage only)

Adds support for "Split" effects. For example when a large or medium Black Pudding is subjected to lightning or slashing damage (or bloodied), it will be removed from the Combat Tracker and map, and replaced with two smaller puddings.

Black Pudding
Ochre Jelly

Resistance is Futile covers "absorption" and BCEG covers "when damaged", but BCEG is not free.

I like the adding of support for "split" effects. Does it take into account of the pudding has already used it's reaction? How does it know to apply to a creature? With the split trait? By the name of the creature? A CT effect?

[jkeller]

Thanks, I'll take a look at Resistance is Futile (https://forge.fantasygrounds.com/shop/items/2092/view).
I've heard of Better Combat Effects, it looks very powerful!

Regarding splitting: When an NPC with the Split reaction is added to the CT, my extension automatically adds an effect like "Split: lightning,slashing,bloodied".
When damaged, the code checks for that effect and splits if the conditions are met.

I don't currently check if the NPC has used it's reaction, but I'll look into that.

I'm currently adding support for the troll's Loathsome Limb trait, which is similar. Hope to have that done today.

[jkeller]

Uploaded v0.2: pudding reaction, added support for Troll Limbs

[Farratto]

very cool, nice work

[jkeller]

The new version supports Hydras (heads killed per 25 damage, regrow x2 if no fire damage, etc).

Are there any other creatures that do stuff based on damage?

[jkeller]

Added support for on-death effects, like a Balor:

Death Throes. The balor explodes when it dies. Dexterity Saving Throw: DC 20, each creature in a 30-foot Emanation originating from the balor. Failure: 31 (9d6) Fire damage plus 31 (9d6) Force damage. Success: Half damage

[jkeller]

Added support for the Fire Shield spell (it now adds an "OnMeleeHit" to the effect).

Note that the current version of the "5e Reactions" extension conflicts with this extension's ability to detect new effects (which is how support for Fire Shield works). I've posted in that extension's thread to see if it can be fixed.