Support Basic allied No-Field transit
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
40d567a053
commit
9c6b2d884b
8 files changed
+171
-7
No files matched your search
@@ -2,6 +2,26 @@
|
||||
|
||||
Audit: 7 September 2026. Read-only source and code audit, retained by the coordinating agent. Scope is classic GF9 base rules and the applicable November 2020 FAQ, not tournament or movie-game rules.
|
||||
|
||||
## Basic allied No-Field transit — 28 October 2026
|
||||
|
||||
**Prototyped / Partial.** The November 2020 FAQ p. 2 permits shipment into
|
||||
an ally's territory followed by departure, subject to stronghold limits. The
|
||||
printed Richese alliance ability ships its ally's off-planet forces and
|
||||
immediately reveals the No-Field. Provisionally compose these rules for a
|
||||
Basic offer to the Richese-occupied territory. The recipient consents, the
|
||||
native cancellation and payment sequence applies, and the arriving counters
|
||||
are ordinary physical forces. The pre-arrival physical baseline records only
|
||||
new visitors; finishing without moving them out sends those visitors to Tanks
|
||||
under the existing provisional Basic fallback. A zero-force arrival creates no
|
||||
visitor receipt. The supplier's older marker reveals before this baseline is
|
||||
recorded. Supplier and recipient see the fallback before offering or accepting;
|
||||
minimal AI retains its existing legal empty-destination offer path.
|
||||
|
||||
This composition and the no-departure fallback are software interpretations,
|
||||
not publisher rulings. Advanced allied No-Field transit and other transport
|
||||
combinations remain separate. [FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf),
|
||||
[CHOAM & Richese rulebook](https://www.gf9games.com/dune/wp-content/uploads/2021/11/CHOAM-Rulebook-low-res.pdf).
|
||||
|
||||
## Concealed No-Field at the separation deadline — 27 October 2026
|
||||
|
||||
A deployed marker is one force for all effects, including0, under publisher E2
|
||||
@@ -118,7 +138,7 @@ Tanks. A zero marker reveals without casualties. Physical visitors use the
|
||||
same pre-arrival baseline; an earlier voluntary reveal is not repeated.
|
||||
The source FAQ permits allied shipment transit and the Richese rules count a
|
||||
concealed marker as one force; their combination and no-exit consequence are
|
||||
provisional. Allied No-Field use, paired markers and other
|
||||
provisional. Paired markers and other
|
||||
transport compositions remain separate.
|
||||
|
||||
## Basic ordinary allied shipment prototype — 8 October 2026
|
||||
@@ -148,8 +168,9 @@ co-occupation deadlines still resolve separately. AI prioritizes available
|
||||
native departures and does not retain a stronghold sentinel from a
|
||||
visiting group.
|
||||
|
||||
Allied No-Field arrivals, mobile/homeworld transports and
|
||||
optional arrival compositions are not expanded by the Basic prototype.
|
||||
Mobile/homeworld transports and optional arrival compositions are not expanded
|
||||
by the ordinary Basic prototype. Allied No-Field arrivals have their own
|
||||
later scoped prototype above.
|
||||
Advanced ordinary physical entry is connected in the follow-up above.
|
||||
Refinement of interrupted and mixed-cohort interactions remains later work.
|
||||
|
||||
|
||||
Reference in new issue
Block a user