Extend Truthtrance bidding and prepare alliance controls
Verify and publish checkpoint container / container (push) Successful in 11m0s
Verify and publish checkpoint container / container (push) Successful in 11m0s
This commit is contained in:
1 parent
77376c39d6
commit
e529cc2d7a
10 files changed
+525
-9
No files matched your search
+14
-1
@@ -29,9 +29,22 @@ enabled or claimed complete by the standalone foundation. The shipment helper
|
||||
now models several witnesses and one physical baseline, with the existing pair
|
||||
engine using the same quote. Group receipts, separation, Nexus, funding and
|
||||
other engine paths still need integration before the option can be offered.
|
||||
Unconnected Nexus controls and a funding quote now model unanimous consent,
|
||||
explicit donor allocations and edge-bound pledge authorizations. The engine
|
||||
still must issue and revoke unique edge authorizations, settle and refund
|
||||
escrow atomically, and connect these controls to native actions and AI.
|
||||
The separate printed unlimited-size / three-stronghold variant remains missing;
|
||||
the current group model deliberately caps membership at three. The combined
|
||||
earlier batch passed 189 cases; the shipment batch passed 58 cases.
|
||||
earlier batch passed 189 cases; the shipment batch passed 58 cases. The latest
|
||||
focused funding, Nexus, shipment and Truthtrance union passed 61 cases.
|
||||
|
||||
**Conditional future-battle Truthtrance in Basic Bidding — 28 October.
|
||||
Prototyped / Partial.** The named-leader question also works during a quiet
|
||||
ordinary auction. Its existing current-leader answer, first actual battle and
|
||||
no-battle expiry are preserved; the auction retains its active bid and actor.
|
||||
Four original-action scenarios cover both answers, expiry and legal AI replies.
|
||||
Other windows, faction and module
|
||||
combinations remain separately guarded.
|
||||
|
||||
**Conditional future-battle Truthtrance in Basic Charity — 28 October.
|
||||
Prototyped / Partial.** The named-leader question also works in a quiet
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## Conditional next-battle leader question — 28 October 2026
|
||||
|
||||
**Prototyped / Partial.** In a quiet Basic Charity, Revival or Shipment and Movement window with
|
||||
**Prototyped / Partial.** In a quiet Basic Charity, Bidding, Revival or Shipment and Movement window with
|
||||
classic factions and no optional modules, 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
|
||||
@@ -13,14 +13,15 @@ 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,
|
||||
expansion factions, optional modules and Advanced are not supported here.
|
||||
During Charity and Revival, definite answers use currently available native leaders or
|
||||
During Charity, Bidding and Revival, definite answers use currently available native leaders or
|
||||
Cheap Heroes; they do not forecast a future revival or spend its resources.
|
||||
|
||||
The publisher's [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf)
|
||||
permits game-related current-turn action questions and requires honoring an
|
||||
answer while possible. The first-battle binding and no-opportunity expiry are
|
||||
provisional online interpretations, not specific publisher rulings. The
|
||||
[native runtime tests](../tests/truth-future-battle-leader-runtime.test.ts)
|
||||
[native runtime tests](../tests/truth-future-battle-leader-runtime.test.ts) and
|
||||
[Bidding continuation tests](../tests/truth-future-battle-bidding.test.ts)
|
||||
exercise both answers and expiry without inventing a battle.
|
||||
|
||||
## Printed flight and pre-leader cards — 27 October 2026
|
||||
|
||||
Reference in new issue
Block a user