Support staged group shipment funding
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
624f95dde4
commit
34aa64cdef
13 files changed
+828
-16
No files matched your search
@@ -1,5 +1,25 @@
|
||||
# Optional three-stronghold alliance victory
|
||||
|
||||
## Group ordinary-shipment funding — 28 October 2026
|
||||
|
||||
**Staged Basic prototype, not a selectable game mode.** Group allies can set
|
||||
aside separate amounts for each other during Shipment and Movement. A shipper
|
||||
may explicitly allocate amounts from each pledged donor to an ordinary physical
|
||||
reserve shipment; the authoritative payment rechecks those exact pledges,
|
||||
charges the shipper's remainder once, and retains each donor's identity. An
|
||||
outside Guild receives the eligible payment. Unspent pledges return to their
|
||||
respective donors at phase end. Alliance edge authorizations are renewed on
|
||||
formation, preserved for surviving edges and revoked on departure, with
|
||||
aggregated refunds for removed edges. Controls show only the viewer's own
|
||||
outgoing and incoming pledges; bots may continue using their own spice.
|
||||
|
||||
This first path is limited to Basic classic-faction staged groups without a
|
||||
Guild member, optional modules, Karama shipment pricing or special transport.
|
||||
Guild-allied rates, other shipment types, group-funded bidding, and the
|
||||
remaining faction benefits and interactions are not connected. No lobby can
|
||||
start a group game yet. The recipient-specific pledge and allocation procedure
|
||||
is a provisional online convention rather than a printed worked example.
|
||||
|
||||
## Group Nexus negotiation — 28 October 2026
|
||||
|
||||
**Integrated groundwork, not a selectable game mode.** In a staged Basic
|
||||
|
||||
Reference in new issue
Block a user