Support group Fremen worm protection
Verify and publish checkpoint container / container (push) Successful in 10m58s
Verify and publish checkpoint container / container (push) Successful in 10m58s
This commit is contained in:
1 parent
6e26ceb216
commit
40c9651b80
12 files changed
+479
-24
No files matched your search
@@ -1,5 +1,19 @@
|
||||
# Optional three-stronghold alliance victory
|
||||
|
||||
## Group Fremen worm protection — 29 October 2026
|
||||
|
||||
**Staged Basic prototype, not a selectable game mode.** When a worm threatens
|
||||
either or both of Fremen's group allies, Fremen decides separately for each
|
||||
threatened ally in storm order. Each accepted protection has its own Karama
|
||||
response; the worm resolves only after all those choices and Fremen's separate
|
||||
survival response finish. Canceling one protection does not erase another.
|
||||
The choices bind the original worm event and ally, and the existing force
|
||||
loss, spice removal and continuation occur once. Controls name the current
|
||||
ally and minimal bots make the same legal choices. The printed single-ally
|
||||
power does not specify this multi-ally sequence, so its order and separate
|
||||
responses are provisional. Advanced, expansions and optional modules remain
|
||||
outside this staged path; group games are not yet available from the lobby.
|
||||
|
||||
## Group Guild transport — 28 October 2026
|
||||
|
||||
**Staged Basic prototype, not a selectable game mode.** Both Guild group
|
||||
|
||||
Reference in new issue
Block a user