fix: recompute active pursuer escape DC - #126
Merged
Merged
Conversation
…-escape-dc # Conflicts: # packages/mcp/tests/test_chase_mcp.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #83.
Recomputes the 2014 chase escape DC from currently active pursuers instead of retaining a dropped pursuer's opening passive Perception. Each participant now carries a validated passive Perception snapshot; legacy snapshots fail closed once their pursuer set changes.
Also orders terminal chase outcomes before drawing the next complication, so the final pursuer/quarry dropping out closes the chase without consuming irrelevant randomness or leaving a pending complication.
Validation: