Enable Ecaz Duke revival with Advanced Harkonnen
Verify and publish checkpoint container / container (push) Successful in 11m23s
Verify and publish checkpoint container / container (push) Successful in 11m23s
This commit is contained in:
1 parent
ecd892b368
commit
88240e2cea
8 files changed
+287
-3
No files matched your search
@@ -1,5 +1,24 @@
|
||||
# Duke Prad Vidal lifecycle
|
||||
|
||||
## Plain Advanced Ecaz/Harkonnen revival — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** Ecaz can now use its native paid or Ghola revival
|
||||
for a publicly dead Duke at supported Advanced Ecaz/Harkonnen tables without
|
||||
optional modules. The supplied revised rulebook, physical p. 30 / printed
|
||||
p. 28, confirms the independent five-spice revival. The user's recorded
|
||||
Ecaz-only decision continues to supersede that source's foreign-Ghola
|
||||
exception. Successful revival keeps the original physical Duke and its death
|
||||
history; existing allowance, discount and prevention rules still apply.
|
||||
|
||||
When a secret capture or execution concerned a different controller, Ecaz's
|
||||
projected revival and Ghola choices use the same public snapshot and a forged
|
||||
attempt cannot reveal the hidden result. Ecaz can act on a secret execution
|
||||
when it was the informed original controller. [Quote cases](../tests/ecaz-duke-plain-harkonnen-revival-quote.test.ts)
|
||||
and [native controls and actions](../tests/ecaz-duke-plain-harkonnen-revival.test.ts)
|
||||
use genuine Advanced setup with explicitly staged Duke custody and conserved
|
||||
Ghola cards. Other capture histories, optional modules, complete games and
|
||||
deployed acceptance remain open.
|
||||
|
||||
## Concealed Duke Ghola guidance — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** Ecaz's private Ghola choice list now uses the Duke
|
||||
|
||||
Reference in new issue
Block a user