Enable future battle questions in Basic expansions
Verify and publish checkpoint container / container (push) Successful in 10m55s

This commit is contained in:
Quintine committed 2026-10-29 02:16:15 +11:00
1 parent 7fc6f1cd43
commit 0e52c25355
7 files changed
+151 -14

No files matched your search

+12
View File
@@ -10,6 +10,18 @@ export function futureBattleLeaderTiming(g: Pick<Game, 'phase' | 'stormPending'
return [2, 3, 4, 5].includes(g.phase);
}
/** Share the same quiet-window boundary between question validation and the
* projected editor. Basic expansion factions use the same native battle
* receipt except Ecaz, whose combined battle lead is chosen afterward. */
export function futureBattleLeaderWindow(g: Game): boolean {
return g.status === 'playing' && !g.advanced && futureBattleLeaderTiming(g) &&
!g.players.some(player => player.faction === 'ecaz') && !g.ecazOccupyPreview &&
!g.techTokens && !g.strongholdCards && !g.nexusCards && !g.homeworlds &&
!g.leaderSkills && !g.discoveryEnabled && !g.ecazTreachery && !g.battle &&
!g.response && !g.decision && !g.phaseOpening && !g.pendingRevival &&
!g.pendingKarama && !g.pendingTreacheryDiscard;
}
/** A conditional commitment for the respondent's first later native battle.
* Waiting does not require a battle to occur. The engine owns plan legality,
* answer feasibility and the decision that an obligation became impossible. */