Connect Basic Revival gift and arrival continuations
Verify and publish checkpoint container / container (push) Successful in 11m37s
Verify and publish checkpoint container / container (push) Successful in 11m37s
This commit is contained in:
1 parent
6acf2c200c
commit
2cea251afd
10 files changed
+520
-6
No files matched your search
@@ -2,6 +2,22 @@
|
||||
|
||||
Audit date: 2026-09-06. This document distinguishes the printed token lifecycle from engine integration and unresolved combinations. It does not certify Richese, Homeworlds, or any other gated game mode.
|
||||
|
||||
## Basic reveal during CHOAM free Revival — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** In supported Basic games Richese may reveal its
|
||||
deployed No-Field while CHOAM considers another player's committed free force
|
||||
Revival. The existing original Revival quote is checked first; CHOAM retains the
|
||||
same Allow or La La La decision and the original force return or prevention
|
||||
resolves once. Richese may itself be the recipient. The marker materializes
|
||||
using reserves available at the chosen reveal, before any later revived forces
|
||||
return. This online ordering applies the printed before-Battle permission and
|
||||
is not a separate publisher timing ruling.
|
||||
|
||||
The focused public-start test covers Richese and Atreides recipients, both
|
||||
CHOAM decisions and all four legal bot profiles with conserved staged casualties
|
||||
and card locations. Other pending Revival parents, optional modules, full games
|
||||
and deployed acceptance remain open.
|
||||
|
||||
## Basic reveal with public deals — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** An active public agreement no longer independently
|
||||
|
||||
Reference in new issue
Block a user