Ad placeholder
Stirring Execution: Difference between revisions
Jump to navigation
Jump to search
Cattlesquat (talk | contribs) No edit summary |
HiddenDragon (talk | contribs) mNo edit summary |
||
Line 2: | Line 2: | ||
| summary = '''Stirring Execution''' is a passive feature that grants the wielder temporary hit points when they kill an enemy. | | summary = '''Stirring Execution''' is a passive feature that grants the wielder temporary hit points when they kill an enemy. | ||
| description = When you kill an enemy, allies within {{Distance|m=9|ft=30}} gain [[Temporary Hit Points|temporary hit points]] equal to your Charisma [[Ability Modifier|Modifier]] (minimum 1). | | description = When you kill an enemy, allies within {{Distance|m=9|ft=30}} gain [[Temporary Hit Points|temporary hit points]] equal to your Charisma [[Ability Modifier|Modifier]] (minimum 1). | ||
| condition = Temporary Hit Points (Stirring Execution) | |||
| bugs = * Contrary to the in-game description, the number of temporary hit points granted is equal to the Charisma modifier of the character receiving them, not the character who applied the condition. This is likely a bug. | | bugs = * Contrary to the in-game description, the number of temporary hit points granted is equal to the Charisma modifier of the character receiving them, not the character who applied the condition. This is likely a bug. | ||
}} | }} |
Revision as of 08:59, 25 September 2024
Stirring Execution is a passive feature that grants the wielder temporary hit points when they kill an enemy.
Description
When you kill an enemy, allies within 9 m / 30 ft gain temporary hit points equal to your Charisma Modifier (minimum 1).
Condition: Temporary Hit Points (Stirring Execution)
- Affected entity has gained
Charisma Modifier
temporary hit points.
How to learn
Granted by the weapons:
Bugs
- Contrary to the in-game description, the number of temporary hit points granted is equal to the Charisma modifier of the character receiving them, not the character who applied the condition. This is likely a bug.