Connect the Basic Ecaz new-ally Duke loan
This commit is contained in:
1 parent
c28e24b5fa
commit
2d0f20b69c
11 files changed
+106
-25
No files matched your search
@@ -35,7 +35,7 @@ The [base Harkonnen capture rules, p. 17](https://www.gf9games.com/dunegame/wp-c
|
||||
| Moritani acquisition from captured or ghola custody | Ecaz’s Ambassador explicitly excludes both; Moritani’s acquisition excludes only Tanks and says to take Duke from any controller. Do not silently copy the Ecaz exclusions as a confirmed Moritani rule. The interaction with concealed capture and the apparent ghola restriction needs an explicit supported policy. |
|
||||
| Duke used in a lost battle against Harkonnen | One-battle tenure and postbattle capture both apply. No retrieved Duke-specific text orders release versus selection into the capture pool. Removing him first changes the random pool; keeping him first can change custody. Gate this combination until resolved rather than choosing by handler order. |
|
||||
| Returning a captured Duke | Native identity is Ecaz, but temporary prior custody may be Moritani or a loaned ally. Base capture return plus Duke’s special acquisition restrictions do not explicitly settle active-control versus set-aside destination in every combination. Preserve prior custody rather than discarding that information. |
|
||||
| Loan to the new Ecaz ally | The printed loan lasts this turn. No retrieved passage resolves unused-loan return destination, an alliance breaking mid-loan, or one-battle tenure for a non-Moritani/non-Ecaz recipient. Preserve owner/controller/loan expiry separately and gate unresolved combinations. |
|
||||
| Loan to the new Ecaz ally | The printed loan lasts this turn. The 8 October Basic-first prototype now offers the loan after an accepted Ambassador alliance, with the same physical disc. One-battle tenure and unused living turn-end set-aside are explicitly provisional implementation policies. Advanced, capture and alliance-break interactions remain for refinement; no publisher clarification is claimed. |
|
||||
| Ecaz co-occupied battles | Ecaz’s Occupy rules distinguish participating forces from the faction chosen to fight. Duke eligibility excludes battles involving Ecaz, but no direct combined example decides every Ecaz-ally designation case. Ordinary faction-pair battle lists alone do not certify the full Occupy interaction. |
|
||||
| Revival alternatives | Ecaz’s Tleilaxu Ambassador effect and sharing an Ambassador benefit may interact with the absolute Ecaz-only restriction. No retrieved specific exception permits another faction to revive Duke. Keep that restriction unless a primary clarification establishes otherwise. |
|
||||
|
||||
|
||||
Reference in new issue
Block a user