Enforce maximum values for PF2e numbered conditions #31

New Issue

dostulata · 2026-04-08T23:16:05+02:00

dostulata commented

2026-04-08 23:16:05 +02:00

Summary

Several PF2e valued conditions have rule-defined maximum values that the app currently doesn't enforce. Users can increment these conditions beyond their meaningful range, which doesn't match the game rules.

Acceptance Criteria

Dying condition is capped at 4 (creature dies at dying 4, or 4 minus doomed value)
Doomed condition is capped at 3 (doomed 3 effectively means dying 1 = death)
Wounded condition is capped at 3 (wounded value adds to dying, and dying caps at 4)
Slowed condition is capped at 3 (a creature only has 3 actions to lose)
The condition picker UI prevents incrementing beyond the maximum
Maximum enforcement only applies in PF2e edition — D&D conditions are unaffected

## Summary Several PF2e valued conditions have rule-defined maximum values that the app currently doesn't enforce. Users can increment these conditions beyond their meaningful range, which doesn't match the game rules. ## Acceptance Criteria - [x] Dying condition is capped at 4 (creature dies at dying 4, or 4 minus doomed value) - [x] Doomed condition is capped at 3 (doomed 3 effectively means dying 1 = death) - [x] Wounded condition is capped at 3 (wounded value adds to dying, and dying caps at 4) - [x] Slowed condition is capped at 3 (a creature only has 3 actions to lose) - [x] The condition picker UI prevents incrementing beyond the maximum - [x] Maximum enforcement only applies in PF2e edition — D&D conditions are unaffected

dostulata closed this issue

2026-04-09 00:06:43 +02:00

dostulata referenced this issue from a commit

2026-04-09 00:09:21 +02:00

Enforce maximum values for PF2e numbered conditions

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dostulata/initiative#31