Skip to content

HP value being erroneously clamped if HP max is changed at same time #6947

Description

@arbron

in AttributesFields.preUpdateHP the system now clamps the HP value using effectiveMax, but it uses the current effectiveMax. If the creature's maximum hit points are changed as part of the same update operation then it can clamp to a lower value than desired.

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions