Extend conditional battle questions across previews
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
0e52c25355
commit
50703664cf
13 files changed
+336
-24
No files matched your search
@@ -2,19 +2,20 @@
|
||||
|
||||
## Conditional next-battle leader question — 28 October 2026
|
||||
|
||||
**Prototyped / Partial.** In a quiet Basic Storm, Spice Blow, Charity, Bidding, Revival or Shipment and Movement window with
|
||||
classic or expansion factions, no Ecaz and no optional modules, a player can ask whether another
|
||||
**Prototyped / Partial.** In a quiet Storm, Spice Blow, Charity, Bidding,
|
||||
Revival or Shipment and Movement window, a player can ask whether another
|
||||
player will use a named native leader in that player's first later battle this
|
||||
turn, if one occurs. A definite answer creates a waiting receipt; it does not
|
||||
require a shipment, movement or battle. At the first actual battle involving
|
||||
that player the receipt binds its real battle event and uses the native plan
|
||||
require a shipment, movement or battle. At the first actual battle for which
|
||||
that player submits a plan, the receipt binds its real battle event and uses the native plan
|
||||
validator and guidance. If no battle occurs, the receipt expires when Battle
|
||||
ends. An independently impossible answer is released by the existing battle
|
||||
promise reconciliation. Another structured action answer for that respondent
|
||||
is guarded while the conditional answer is active; broader promise composition,
|
||||
Ecaz, optional modules and Advanced are not supported here. Ecaz's combined
|
||||
battle may select a different lead after scheduling, so it needs its own binding
|
||||
and expiry treatment before this question can be enabled in those games.
|
||||
optional modules and Advanced Ecaz are not supported here. In Basic Ecaz's
|
||||
combined battle, the selected lead and opponent bind only after the Occupy
|
||||
cancellation response has resolved. The nonleading ally remains waiting for
|
||||
its own later battle; this plan-owner interpretation is provisional.
|
||||
Storm requires its original post-dial, pre-movement window; Spice Blow requires
|
||||
the original pre-draw window with no Nexus or worm continuation. During these
|
||||
windows, Charity, Bidding and Revival, definite answers use currently available native leaders or
|
||||
@@ -28,13 +29,19 @@ provisional online interpretations, not specific publisher rulings. The
|
||||
[Bidding continuation tests](../tests/truth-future-battle-bidding.test.ts) and
|
||||
[Storm/Spice continuation tests](../tests/truth-future-battle-early.test.ts),
|
||||
plus [Basic expansion tests](../tests/truth-future-battle-leader-expansions.test.ts),
|
||||
[Basic Ecaz tests](../tests/truth-future-battle-leader-ecaz.test.ts) and
|
||||
[Advanced tests](../tests/truth-future-battle-leader-advanced.test.ts),
|
||||
exercise both answers and expiry without inventing a battle.
|
||||
|
||||
The Basic expansion widening has focused coverage of CHOAM's Yes and No in
|
||||
actual battles and a Richese physical discard, Semuta pass and no-battle
|
||||
expiry, plus all four minimal answer profiles. The Ecaz guard uses a staged
|
||||
seat; it is not an Ecaz game journey. Semuta exchange, other expansion-faction
|
||||
battle interactions, Advanced and optional modules remain unverified.
|
||||
seat; it is not an Advanced Ecaz game journey. The Advanced tests cover a
|
||||
classic paid-support battle and an Ixian battle. The Basic Ecaz lead and
|
||||
allowed/canceled Occupy cases use genuine setup, real questions and battles,
|
||||
with staged physical cards, rival forces and shipment budgets. Ten related
|
||||
test files pass 75 cases. Semuta exchange, other expansion-faction battle
|
||||
interactions, Advanced Ecaz and optional modules remain unverified.
|
||||
|
||||
## Printed flight and pre-leader cards — 27 October 2026
|
||||
|
||||
|
||||
Reference in new issue
Block a user