Fix AI freeze when declaring attackers with unpayable attack costs#9998
Merged
tool4ever merged 1 commit intoCard-Forge:masterfrom Mar 6, 2026
Merged
Conversation
4382f35 to
5c089c5
Compare
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
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.
PhaseHandlerwould remove one for not paying the tax, the remaining one alone would fail validation, and the loop would restart with the AI making the same decisionAiController, before the attackers reachPhaseHandler'spayment loop. This aligns with CR 508.1d which says the decision to pay attack costs is made during attacker declaration, not as a separate step afterward