Add optional short alliance victory
Verify and publish checkpoint container / container (push) Successful in 11m2s
Verify and publish checkpoint container / container (push) Successful in 11m2s
This commit is contained in:
1 parent
8fb9f59106
commit
e896570f07
25 files changed
+632
-27
No files matched your search
@@ -16,6 +16,24 @@ open mode gates.
|
||||
|
||||
|
||||
## Current checkpoint and work
|
||||
**Optional three-stronghold two-member alliance — 28 October. Prototyped /
|
||||
Partial.** The host can select the printed shorter target; changes clear human
|
||||
readiness and the normal target remains the default. Public progress and the
|
||||
actual Mentat outcome use the same calculation. A genuine Nexus alliance with
|
||||
a staged three-stronghold board tests both selected and default outcomes;
|
||||
the existing four-stronghold target remains for two physical controllers as a
|
||||
provisional precedence choice. The combined batch passes 96 focused cases and
|
||||
three administrator boundary HTTP cases. The administrator's existing audited
|
||||
lobby controls can also show and change the setting. Larger alliances, wider interactions and deployed
|
||||
acceptance remain open. [Scope](OPTIONAL_ALLIANCE_VICTORY.md).
|
||||
|
||||
**Conditional future-battle Truthtrance in Basic Revival — 28 October.
|
||||
Prototyped / Partial.** The existing phase-five question also works in a quiet
|
||||
phase-four window, using leaders available at answer time without predicting a
|
||||
revival. Native Revival, subsequent real battles and no-battle expiry are
|
||||
covered in the 96-case combined batch. Pending transactions and broader
|
||||
promise compositions remain separately guarded.
|
||||
|
||||
**Conditional future-battle Truthtrance — 28 October. Prototyped / Partial.**
|
||||
A quiet Basic classic game can ask whether a named native leader will be used
|
||||
in the respondent's first later battle this turn, if there is one. The answer
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
# Optional three-stronghold alliance victory
|
||||
|
||||
**Prototyped / Partial — 28 October 2026.** The host can select a shorter
|
||||
two-member alliance game in the lobby. With at least three physical
|
||||
controllers, allied factions need three distinct qualifying strongholds
|
||||
instead of the default four. A solo faction keeps its normal target, a
|
||||
separately agreed extra-stronghold requirement is added afterward, and Tech
|
||||
Tokens retain their existing ownership requirements. The same calculation
|
||||
drives public progress and the Mentat victory decision. Changing the setting
|
||||
clears human readiness; older games omit it and retain the default.
|
||||
|
||||
The 2019 GF9 rulebook's optional alliances table, printed p. 24, lists a
|
||||
two-member alliance with three strongholds as a shorter game. The
|
||||
[publisher rulebook mirror](https://www.boardgamesbot.com/assets/games-library/dune/manual_eng.pdf)
|
||||
preserves that table. This first version keeps the existing four-stronghold
|
||||
target for two physical controllers, including the two-faction-per-person
|
||||
setup; priority between that special setup and this optional table is a
|
||||
provisional interpretation. Larger alliance variants require separate
|
||||
membership and interaction work. Advanced and expansion combinations are not
|
||||
certified by the Basic-focused evidence.
|
||||
@@ -1,5 +1,12 @@
|
||||
# Rule decision index
|
||||
|
||||
## Optional short alliance victory — 28 October 2026
|
||||
|
||||
The printed optional two-member alliance target is selectable at three
|
||||
strongholds. This prototype preserves the four-stronghold two-controller
|
||||
setup as a provisional precedence choice; larger alliances remain separate.
|
||||
[Scope and source](OPTIONAL_ALLIANCE_VICTORY.md).
|
||||
|
||||
## Conditional future-battle leader question — 28 October 2026
|
||||
|
||||
The printed current-turn question can provisionally refer to a named native
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## Conditional next-battle leader question — 28 October 2026
|
||||
|
||||
**Prototyped / Partial.** In a quiet Basic Shipment and Movement window with
|
||||
**Prototyped / Partial.** In a quiet Basic 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,6 +13,8 @@ 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 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
|
||||
|
||||
Reference in new issue
Block a user