Integrate Ecaz Duke revival and bounded Mirror Weapon battles
This commit is contained in:
Quintine committed
1 parent
68d782ca82
commit
3b118dd845
39 files changed
+1377
-533
No files matched your search
+21
-1
@@ -63,6 +63,26 @@ tables, where the battle path cannot select Duke. Captured, dead and Ghola
|
||||
destinations and all combined modules remain gated. The Battle-only timing
|
||||
is a documented product boundary rather than printed phase text. This code
|
||||
is not yet in the live image.
|
||||
|
||||
The bounded [Ecaz-only Duke revival](ECAZ_REVIVAL_RULES.md#selected-product-interpretation-28-september-2026)
|
||||
returns the existing dead shared disc alive and set aside after ordinary paid
|
||||
revival or a Ghola card. The user selected this custody interpretation; it is
|
||||
not a publisher clarification. Five spice (three with the existing Tleilaxu
|
||||
alliance discount), stop/cancellation windows, first five-in-Tanks cohort,
|
||||
owner choices, legal AI and JSON/SQLite continuation are connected. Further
|
||||
six-disc native cycles, exceptional custody and Advanced Harkonnen remain
|
||||
guarded; no complete Ecaz start is certified.
|
||||
|
||||
The bounded [Mirror Weapon battle path](MIRROR_WEAPON_ENGINE_AUDIT.md#user-selected-cleanup-interpretation-28-september-2026)
|
||||
admits the canonical physical card in CHOAM/Richese-deck Basic/Advanced
|
||||
classic/CHOAM/Richese battles without combined optional modules. Effective
|
||||
copied attacks, copy-first Tooth/Stone choices, public Stone feasibility,
|
||||
saved custody, human controls and legal AI are connected. A victorious
|
||||
physical Mirror can be kept even after a copied activated Tooth or Artillery
|
||||
attack under the user's interpretation, not a GF9 clarification. Combined
|
||||
modes and full Richese starts remain gated. Neither new path is in the
|
||||
verified live `c9a3625` image.
|
||||
|
||||
The main page
|
||||
labels its build's Git commit in the lobby and active-table masthead; local
|
||||
Git HEAD does not represent uncommitted work. The main-branch container
|
||||
@@ -225,7 +245,7 @@ question was sent; ordinary HMS relocation and force entry/exit remain working.
|
||||
No extra collection is silently applied. The Bureaucrat/Emperor gift question
|
||||
and the other recorded skill boundaries remain pending.
|
||||
|
||||
The reviewed remaining native Ecaz/Moritani effects, Duke revival and Richese
|
||||
Remaining native Ecaz/Moritani effects, repeated six-disc Duke cycles and Richese
|
||||
empty-cache auction arithmetic still cross recorded source questions. Native
|
||||
Tleilaxu revival now creates its skill offer at successful commitment, including
|
||||
automatic response chains; the former dependency is resolved in its Basic profile.
|
||||
|
||||
@@ -64,3 +64,15 @@ The integrated896-unit suite,45 persisted/API tests, typecheck, lint and build p
|
||||
## Direct Ecaz acquisition follow-up
|
||||
|
||||
The direct self-acquisition feature was subsequently implemented and verified. See [Ecaz Duke acquisition](ECAZ_DUKE_ACQUISITION.md) for the integrated controls, AI, persistence and actual battle playtest. Alliance/loan alternatives, revival and exceptional capture remain separate unfinished work. Earlier readiness and integration statements above are historical.
|
||||
|
||||
## Ecaz revival follow-up (28 September 2026)
|
||||
|
||||
Ecaz alone can revive the canonical dead shared disc through ordinary paid
|
||||
revival or a real Ghola card. The user selected the living **set-aside** result
|
||||
after either return: no automatic Ecaz controller, source or acquisition turn.
|
||||
This is a product interpretation, **not** a published Duke-specific ruling.
|
||||
The printed five-spice normal price, existing allied discount/stop/payment
|
||||
accounting, ordinary slot and one physical death history remain separate from
|
||||
the Ghola card's free return. Native first-cohort five-in-Tanks eligibility is
|
||||
supported; repeated six-disc cycles and exceptional custody stay guarded.
|
||||
See [Ecaz revival](ECAZ_REVIVAL_RULES.md#selected-product-interpretation-28-september-2026).
|
||||
@@ -2,6 +2,15 @@
|
||||
|
||||
Read-only review, 7 September 2026. Recommend a shared-disc revival contract before adding a selectable Duke to ordinary revival or Ghola. The printed permission and price are clear; post-revival active custody and subsequent six-disc cycles remain material interpretation boundaries already recorded in [ECAZ_REVIVAL_RULES.md](ECAZ_REVIVAL_RULES.md). This review does not silently resolve them, enable full Ecaz starts, or certify all expansion rules.
|
||||
|
||||
**Runtime follow-up, 28 September 2026:** The user selected the set-aside
|
||||
interpretation for a revived living Duke. Ecaz ordinary paid revival and Ghola
|
||||
now return the same physical disc alive and unclaimed, preserving death
|
||||
history; this is an explicit product decision, not an official clarification.
|
||||
The first five-disc ordinary cohort (including Duke) opens and stays recorded
|
||||
after a return. Repeated six-disc native cycles, exotic capture/Ghola custody
|
||||
and Advanced Harkonnen remain guarded. The gap table and in-memory probe below
|
||||
are historical pre-implementation observations, not present runtime status.
|
||||
|
||||
## Verified rule boundary
|
||||
|
||||
Fresh official indexed retrieval confirms Ecaz can revive Duke at a normal price of five spice without a dead-leader threshold. Five Ecaz leaders in the Tanks, counting Duke, permit ordinary revival even with a survivor. Only Ecaz may revive Duke, including through Ghola. His battle strength remains six and he has no Traitor card. These are Basic Ecaz rules as well as Advanced rules. [GF9 E3, printed pp.8–9](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=8)
|
||||
|
||||
@@ -2,6 +2,28 @@
|
||||
|
||||
Bounded primary-source review, 2026-09-06. This document supplements `DUKE_VIDAL_RULES.md` and separates the ordinary arithmetic and eligibility rules from unresolved shared-disc custody and cycle questions. No runtime edits were made.
|
||||
|
||||
## Selected product interpretation (28 September 2026)
|
||||
|
||||
The user chose **set-aside custody**: a successful ordinary Ecaz revival or Ecaz
|
||||
Ghola returns the same dead Duke disc alive to the shared area, with
|
||||
`controller`, `source` and `acquiredTurn` cleared. It is not automatically
|
||||
playable by Ecaz. This is an explicit product interpretation, **not** a
|
||||
publisher ruling; the Ambassador or another supported living-disc acquisition
|
||||
must subsequently claim him. Ordinary revival costs five spice (three with
|
||||
the existing Tleilaxu alliance discount), spends Ecaz's ordinary leader slot,
|
||||
and follows the normal stop, discount-cancellation and payment/income windows.
|
||||
Ghola spends the actual card instead of spice or that slot. Strength remains
|
||||
six; both paths preserve the physical death history.
|
||||
|
||||
Ecaz's first ordinary cohort opens with five dead discs counting Duke, or
|
||||
when its entire native five-disc roster is unavailable under the existing
|
||||
captured-leader exception. The opened first cohort persists across returns.
|
||||
Further native returns once any of the six histories enters a repeated cycle
|
||||
remain explicitly gated; Duke's independent Ecaz-only permission remains
|
||||
available, without making a repeated six-disc algorithm up. Captured, Ghola
|
||||
or concealed shared-disc custody and Advanced Harkonnen combinations retain
|
||||
their existing uniform boundary.
|
||||
|
||||
## Explicit expansion rules
|
||||
|
||||
Ecaz may revive Duke for **5 spice regardless of how many leaders are dead**. Its ordinary leaders become revivable with **five leaders in the Tanks, including Duke**. The clarification expressly permits this while Ecaz still holds one living leader, regardless of which leader that is. Only Ecaz may revive Duke, including through the Ghola Treachery Card. [GF9 Ecaz & Moritani, printed pp. 8–9](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf)
|
||||
@@ -14,7 +36,9 @@ The same p. 9 clarification restricts Ecaz’s acquisition of Duke to its Ambass
|
||||
|
||||
The ordinary base rule makes a revived leader playable. Applying that ordinary result to the special Ecaz-only revival strongly supports active Ecaz custody, treating the Ambassador sentence as acquisition of a living shared disc. The competing literal reading revives Duke to the shared set-aside area so that Ambassador-only acquisition remains universal. The retrieved expansion does not expressly choose between those readings. The Ghola FAQ permits a revived leader to fight in the same Battle phase, but does not specifically resolve Duke’s custody. [GF9 base rules, printed pp. 9, 22](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf)
|
||||
|
||||
**Implementation boundary:** do not certify either controller assignment as an explicit Duke FAQ result. Obtain a supported interpretation before activating revival, especially Ghola during Battle. Persisting `dead=false` while silently choosing `controller=null` or Ecaz changes whether the paid card/action is useful immediately. If Ecaz control is selected, it must be explicit shared custody rather than inserting Duke into the native five-leader array.
|
||||
Earlier implementation guidance below records the pre-decision boundary. The
|
||||
selected set-aside interpretation and limited first-cohort runtime above now
|
||||
supersede that boundary; it remains a source caveat, not a live blocker.
|
||||
|
||||
## Frequency, prices and Tleilaxu
|
||||
|
||||
@@ -42,4 +66,4 @@ The E3 Ecaz table lists Ambassador, Occupy, Loyalty and Collection; it contains
|
||||
|
||||
## Verification boundary
|
||||
|
||||
Checked official indexed GF9 p. 8/9 passages, the base revival text, Ixian/Tleilaxu alliance and early-revival text, and the November 2020 FAQ p. 6 against existing publisher-authored local extracts. Targeted official GF9 and designer-site searches returned no written Duke-after-revival or six-disc repeated-cycle example. This records a retrieval limit, not proof that no clarification exists. Existing direct publisher download restrictions and crawler dates were not treated as evidence of a new edition. Runtime integration, custody decisions and regression tests remain with the parent task.
|
||||
Checked official indexed GF9 p. 8/9 passages, the base revival text, Ixian/Tleilaxu alliance and early-revival text, and the November 2020 FAQ p. 6 against existing publisher-authored local extracts. Targeted official GF9 and designer-site searches returned no written Duke-after-revival or six-disc repeated-cycle example. This records a retrieval limit, not proof that no clarification exists. Existing direct publisher download restrictions and crawler dates were not treated as evidence of a new edition. The selected set-aside product interpretation and bounded runtime above do not resolve the repeated six-disc, exceptional custody or complete-expansion boundaries.
|
||||
@@ -1,6 +1,6 @@
|
||||
# Physical cards and effective battle weapons
|
||||
|
||||
7 September 2026. This is a shared combat foundation for Mirror Weapon, not activation of its complete gameplay.
|
||||
The 7 September foundation now feeds a bounded, playable Mirror Weapon battle path (28 September 2026). The historical focused test counts below predate that integration.
|
||||
|
||||
## Contract and integration
|
||||
|
||||
@@ -10,24 +10,24 @@ Tooth and Stone copies each receive their own choice, with the copy before its s
|
||||
|
||||
`game/battle-cards.ts` consumes the descriptors for ordinary attacks, self-attacks, Artillery suppression/no-bounty behavior and a shared Lasgun explosion predicate. The authoritative engine and AI's fully known battle calculations use that predicate. Single-card knowledge remains single-card knowledge; no new hidden-hand access was added to AI evaluation. Actual Shield and Shield Snooper trigger explosions; defensive Weirding Way and Portable Snooper do not.
|
||||
|
||||
Physical plan IDs, Atreides inspection, Truthtrance commitments, custody, winning card retention and Moritani retention are unchanged. The engine still rejects Mirror as a Battle Plan weapon. Copy arithmetic must not be confused with completed controls, persisted copied choices, Stone outcome integration or cleanup.
|
||||
Physical plan IDs, Atreides inspection, Truthtrance commitments, custody, winning card retention and Moritani retention remain physical. The engine admits canonical Mirror only for CHOAM/Richese-deck classic/CHOAM/Richese rosters without combined optional modules; it rejects unsupported setups before commitment. It validates the original and copied Stone casualty possibilities using public force pools and checks reserved physical Mirror custody across saved zones.
|
||||
|
||||
## Evidence and boundaries
|
||||
|
||||
The current review in [MIRROR_WEAPON_ENGINE_AUDIT.md](MIRROR_WEAPON_ENGINE_AUDIT.md) remains the source contract. A fresh bounded publisher search again found the November FAQ's general winner-retention rule and named Tooth/Artillery exceptions, but no explicit ruling about the physical Mirror copying those exceptions. The earlier user clarification remains unanswered. The CHOAM package itself supplies Tooth and Artillery; excluding only Ix would not isolate this uncertainty. No source absence or elapsed silence was treated as an adjudication.
|
||||
The [Mirror audit](MIRROR_WEAPON_ENGINE_AUDIT.md#user-selected-cleanup-interpretation-28-september-2026) records the user's explicit choice: a victorious physical Mirror may be retained even after copying activated Tooth or Artillery. The November FAQ names the original Tooth/Artillery cards, but no publisher passage was found assigning their disposal to Mirror. This is a product interpretation, not a GF9 ruling. The revealed decision queue binds copied Tooth/Stone choices to the physical Mirror, copied source and battle event, presents the copy before its original, and saves each owner's independent answer across reload.
|
||||
|
||||
Portable Snooper and Stone Burner now have runtime foundations that were absent when the original audit was written. Their current event, defense, casualty-feasibility and public configuration restrictions remain in force. In particular, introducing a copy must not bypass the original Stone player's precommit feasibility guard or choose a hidden-plan-dependent acceptance boundary.
|
||||
|
||||
Remaining work includes canonical Mirror plan admission and named Voice role; physical prescience and promise checks; event-bound copy/source choice ownership and ordering; Stone's effective outcome; settled cleanup rules; controls, AI choice handling and persisted full battles. General expansion/module and Advanced acceptance remain incomplete.
|
||||
Combined expansion modules, leader skills, alternate card-role changes, complete Richese starts and full-mode release acceptance remain gated. The bounded path has human selectors, copy/retention guidance and legal AI plans/choices, without reading sealed opposing cards.
|
||||
|
||||
## Verification
|
||||
|
||||
`tests/effective-weapons.test.ts` contains ten independent helper tests: both orientations, all actual ordinary/Ix attack roles, canonical Stone, no-copy roles, original-versus-copied Chemistry, independent choice order, malformed/duplicate Mirror and frozen inputs. `tests/effective-battle-effects.test.ts` contains six integration tests using an explicit printed defense matrix, all Tooth activation pairs, Artillery defenses, Lasgun shield combinations, no-attack/Stone boundaries and continued blocked Mirror admission.
|
||||
`tests/effective-weapons.test.ts` exercises the pure physical/effective role matrix; `tests/effective-battle-effects.test.ts`, `tests/battle-resolution-quote.test.ts` and `tests/mirror-weapon-engine.test.ts` cover copied defenses, Carthag's effective poison, Stone outcomes, copy-first post-reveal ownership, JSON continuation, stale events, physical disposal and four-profile Basic/Advanced AI admission. Historical foundation counts below remain archived rather than substituted for end-to-end evidence.
|
||||
|
||||
The focused 53-test combat run passes, including existing authoritative Ix, Tooth/Artillery, Portable and Stone cases: `/tmp/dune-effective-weapons-target.log`. Type checking, lint and production build pass: `/tmp/dune-effective-weapons-type.log`, `/tmp/dune-effective-weapons-lint.log`, `/tmp/dune-effective-weapons-build.log`. No Mirror full-game or card-completion claim follows from these arithmetic tests.
|
||||
The earlier focused 53-test combat run passed before engine admission: `/tmp/dune-effective-weapons-target.log`. Its type, lint and build records (`/tmp/dune-effective-weapons-{type,lint,build}.log`) establish only the earlier foundation. Current integration checks belong to the newer checkpoint in `IMPLEMENTATION_STATUS.md`.
|
||||
|
||||
Full registered suites pass: **1,500 rules/client/component tests and 129 persistence/API tests**, 1,629 total. Logs: `/tmp/dune-effective-weapons-full.log` (67.15 seconds) and `/tmp/dune-effective-weapons-multiplayer.log` (18.64 seconds). The historical 648-game calibration was not rerun.
|
||||
|
||||
An independent differential script, `/tmp/dune-effective-comparison.ts`, compares the previous evaluator against the saved implementation using 57 canonical cards and 494 legal same-side pairs. All 865,580 effect comparisons, 216,395 explosion comparisons and 3,364 single-weapon comparisons agree. This is regression evidence for existing legal behavior, not independent proof of complete printed rules. Root reviewed the new helper, tests and integration; the independent review also checked that AI receives no new hidden-hand inputs.
|
||||
|
||||
Malformed Mirror-marked saved cards fail closed with a plain error from the pure evaluator; that can surface as a generic API failure rather than a recoverable rules message. Valid physical inventory does not produce this path. Complete corrupted battle recovery, including event/source validation for existing Poison Tooth answers, remains follow-up work and is not certified by this foundation.
|
||||
Malformed Mirror-marked saved cards fail closed in the pure evaluator; authoritative saved-battle integrity now also validates canonical physical Mirror custody and copied-choice source/event. The full historical-save compatibility audit remains final polish, not a claim made by this bounded runtime.
|
||||
@@ -1,5 +1,42 @@
|
||||
# Dune implementation status
|
||||
|
||||
## 28 September 2026 — Ecaz Duke revival and bounded Mirror Weapon
|
||||
|
||||
The user chose two explicit product interpretations after bounded publisher
|
||||
source review: a successfully revived Duke returns alive to the shared area,
|
||||
unclaimed until later acquisition; a victorious physical Mirror may be kept
|
||||
even when its copied attack activates Poison Tooth or Artillery. Neither is
|
||||
presented as an official GF9 clarification. Ecaz's separate five-spice
|
||||
ordinary Duke revival and Ghola now use the same physical disc, with first
|
||||
five-in-Tanks cohort eligibility, frozen discount/payment and Tleilaxu
|
||||
stop/cancellation continuation, owner controls, minimal legal AI and JSON/
|
||||
isolated SQLite recovery. Repeated six-disc native cycles, exceptional
|
||||
shared-disc custody and Advanced Harkonnen remain guarded.
|
||||
|
||||
Canonical Mirror now occupies the actual weapon slot in bounded Basic/Advanced
|
||||
CHOAM/Richese-deck classic/CHOAM/Richese battles. Revealed opposing attacks,
|
||||
copy-first independently saved Tooth/Stone choices, Stone's public casualty
|
||||
feasibility, physical-card retention/custody, Carthag's effective-poison
|
||||
defense, named Voice, human controls and four-profile legal AI are connected.
|
||||
Combined modules, changing card roles, complete Richese starts and release
|
||||
acceptance remain gated. Read-only local desktop browser fixtures showed the
|
||||
selectable Duke at five spice with strength six/set-aside guidance and the
|
||||
Mirror weapon selector, copied-attack explanation and updated hand guide;
|
||||
no real room was written. The verified live image remains `c9a3625`.
|
||||
|
||||
Independent read-only reviews found and prompted fixes for concealed foreign-
|
||||
ghola death-count privacy, Mirror Voice compulsion deadlock, reordered saved
|
||||
copy decisions and incorrect Stone scoring of ordinary Mirror copies. The
|
||||
reviewed focused run passed **66/66**; the frozen full offline suite passed
|
||||
**5,643/5,643** across 714 files, live development-server HTTP integration
|
||||
passed **52/52**, scoped oxlint and the app build passed. Project TypeScript
|
||||
still reports only the unrelated in-progress Fremen Nexus draft's missing
|
||||
`Player.fremenNexusMovementBlockedTurn`; the required full `npm run check`
|
||||
cannot be claimed green until that draft is resolved. Browser proof also
|
||||
showed the actual copy-first revealed Tooth decision and physical Mirror/
|
||||
opponent Tooth card faces. Production deployment remains blocked by the
|
||||
OS-locked host Apps session, not by a local reset or game migration.
|
||||
|
||||
## 27 September 2026 — Bounded Emperor Nexus bank-auction purchase
|
||||
|
||||
[The separate Secret Ally purchase alternative](NEXUS_EMPEROR_SECRET_ALLY_RUNTIME.md#bank-auction-purchase-alternative)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# Mirror Weapon: source and engine integration audit
|
||||
|
||||
Audited 6 September 2026. This is a proposed implementation contract, not activation or verification of Mirror Weapon gameplay. No runtime file was changed by this audit. Richese and combined expansion starts remain gated.
|
||||
Audited 6 September 2026 as a proposed contract. The 28 September bounded runtime now admits canonical Mirror in CHOAM/Richese-deck classic/CHOAM/Richese battles without optional combined modules; the hook map and former blockers below describe the earlier audit, not current inactive status. Richese expansion starts remain gated.
|
||||
|
||||
**7 September follow-up:** Portable Snooper and Stone Burner now have runtime foundations, superseding the historical absence noted below. A shared physical/effective weapon resolver and ordinary attack/explosion integration are recorded in [EFFECTIVE_BATTLE_WEAPONS.md](EFFECTIVE_BATTLE_WEAPONS.md). Mirror plan admission remains disabled; copied choices, full outcome and cleanup integration are unfinished. Fresh bounded publisher retrieval did not settle the pending copied-disposal question.
|
||||
**28 September ruling and runtime:** the user selected ordinary winner retention for the physical Mirror even when its copy activates Tooth or Artillery. This is an explicit product interpretation, not a located GF9 clarification. `game/effective-weapons.ts` keeps physical identity apart from copied attacks; the engine now connects copied Tooth/Stone choices, Stone comparison, custody, battle controls and legal AI in the bounded configuration.
|
||||
|
||||
## Primary evidence and a retention correction
|
||||
|
||||
@@ -12,7 +12,7 @@ Mirror Weapon is one physical **Weapon / Special**, canonical ID `richese-mirror
|
||||
|
||||
The [CHOAM & Richese rulebook](https://www.gf9games.com/dune/wp-content/uploads/2021/11/CHOAM-Rulebook-low-res.pdf), pp4–6, establishes replacement Tooth/Artillery cards, one separate ten-card cache, and normal Treachery discard routing. Local publisher-text mirror: `/tmp/dune-rules/choam-lelekan-mirror.pdf` and `.txt`. Direct GF9 retrieval returned 403; fresh official indexed excerpts corroborated p4. Bounded official-domain Mirror searches yielded no card-specific clarification.
|
||||
|
||||
**Do not infer compulsory winner disposal from that footer alone.** The [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf), p8, gives winning battle cards a general keep option even without printed retention wording. Page1 expressly makes used Tooth and Artillery exceptions, including when their player wins; an unactivated winning Tooth can be kept. The 2021 Mirror face adds no explicit winner exception. Recommended ordinary composition is that a winning Mirror can be retained; copying a disposable weapon raises a separate inheritance question below. This corrects the earlier inventory's overly definite mandatory-discard interpretation without claiming a new Mirror erratum. Losing and mutual-loss cleanup still discard played cards normally. A traitor-decided battle preempts weapon effects under the [base rules, pp10–11](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf).
|
||||
**Winner disposal interpretation.** The [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf), p8, gives winning battle cards a general keep option even without printed retention wording. Page1 names used Tooth and Artillery as exceptions, including when their player wins; an unactivated winning Tooth can be kept. The printed Mirror face says “Discard after use” without a winner exception. The user chose to treat the copied attack as an effect, not a change of the physical Mirror’s identity: a victorious Mirror may be retained even after copying activated Tooth or Artillery. This is a product interpretation, not a GF9 erratum. Losing and mutual-loss cleanup still discard the physical Mirror.
|
||||
|
||||
## Weapon matrix
|
||||
|
||||
@@ -27,9 +27,9 @@ Here “copy” means an effective attack belonging to the Mirror player, evalua
|
||||
| Weirding Way in the weapon slot | Copy its projectile weapon role. |
|
||||
| Chemistry in the weapon slot | Copy its poison weapon role. The opponent's pair must already be legal. Do not retroactively require the Mirror holder to possess the other defense that made the original Chemistry legal: Mirror is the committed weapon, and copies a card which already counts as a weapon. |
|
||||
| Weirding Way or Chemistry in the defense slot | Do not copy that defense. Inspect the opponent's actual weapon slot instead, which may contain another valid weapon or nothing. |
|
||||
| Poison Tooth | Copy the optional post-reveal attack, not the original owner's eventual answer. The Mirror owner chooses activation first, then the original owner chooses. Persist two separate choices. Reuse the established self-and-opponent attack evaluation; do not apply deaths between these declarations or count a leader death twice. Copy-related physical-card retention remains unresolved below. |
|
||||
| Artillery Strike | Copy the attack on both leaders, suppression of surviving leader strength, and no-bounty battle effect. Apply battle-wide suppression once, not twice. No extra mode choice is created. Copy-related physical-card retention remains unresolved below. |
|
||||
| Stone Burner | The copied effect has its own post-reveal choice, made before the original user's choice. Both effects replace ordinary leader/dial comparison with the same undialed-token comparison. A kill choice cannot be undone by the later ignore-strength choice. Underlying Stone Burner outcome/casualty implementation is not present, so do not silently reduce this to ordinary weapon kills. |
|
||||
| Poison Tooth | Copy the optional post-reveal attack, not the original owner's eventual answer. The Mirror owner chooses activation first, then the original owner chooses. Persist two separate choices. Reuse the established self-and-opponent attack evaluation; do not apply deaths between these declarations or count a leader death twice. An activated copy does not make the physical Mirror a Tooth for winner disposal. |
|
||||
| Artillery Strike | Copy the attack on both leaders, suppression of surviving leader strength, and no-bounty battle effect. Apply battle-wide suppression once, not twice. No extra mode choice is created. The physical Mirror retains the ordinary winner option. |
|
||||
| Stone Burner | The copied effect needs its own post-reveal choice before the original user's choice. Both effects use the existing undialed physical-token comparison. Either kill choice kills both leaders; one ignore choice cannot reverse that. Share the existing Stone casualty-feasibility and mode logic rather than substituting ordinary weapon kills. |
|
||||
| No weapon, or Worthless in place of a weapon | No effective attack. Mirror remains its physical committed Weapon / Special; an occupied slot alone is insufficient evidence of an opposing weapon. |
|
||||
| Reinforcements or Harass & Withdraw in place of a weapon | No effective attack from those cards. The [Ecaz/Moritani rulebook p11](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf) explicitly says they do not count as a weapon or defense. Their other effects are independent. |
|
||||
| A second Mirror | Not a reachable legal physical inventory: the verified collection has exactly one. Reject duplicated physical custody. A future variant adding another copy needs a cycle rule; do not invent an infinite recursion or pretend two copies become an ordinary attack. |
|
||||
@@ -52,8 +52,8 @@ The existing FAQ-backed defense distinctions must survive copying: Chemistry def
|
||||
| `game/battle-cards.ts`: kind arrays, pair/Voice helpers | Introduce strict identity-aware weapon admission and declared-role matching. Existing `WEAPON_KINDS.includes(card.kind)` cannot recognize a canonical Mirror transported as `special`. Avoid changing every Special's role. |
|
||||
| `engine.ts`: `validatePlan`, `findReachableBattlePlan`, `feasiblePrescience` | Use the same legal weapon admission. Preserve physical IDs and promised slots in all plan searches; a selector-only change would leave authoritative plans impossible. |
|
||||
| `nextRevealedDecision` | Currently detects physical `poisonTooth` and iterates storm order. It misses a copy entirely and orders it incorrectly. Replace or extend with a persisted effective-choice queue. |
|
||||
| `resolveBattle`: explosion and `battleCardEffects` | Explosion currently checks physical `kind === 'lasgun'`. Both explosion and normal effects need the same effective descriptor, including own-side attacks and global suppression. |
|
||||
| `canRetainBattleCard` and Moritani cleanup | Keep a shared physical cleanup policy. Do not turn the Mirror into a disposable physical Tooth by mutating its kind. Resolve the copy-disposal question before enabling affected pairings. |
|
||||
| `resolveBattle`: explosion and `battleCardEffects` | The existing effective descriptor already feeds explosion and ordinary attacks. Extend Stone comparison, copied mode ownership and full outcome through that same descriptor; never substitute a physical copied card. |
|
||||
| `canRetainBattleCard` and Moritani cleanup | Keep a shared physical cleanup policy. Do not turn the Mirror into a disposable physical Tooth: the user selected ordinary winner retention even for an activated Tooth or Artillery copy. |
|
||||
| `game/bots.ts`: plan candidates, `weaponKills`, `battleCardEffects`, Tooth decision | Use legal physical candidates and effective attacks only from legitimately known plans. A hidden opposing hand is not an AI input. Handle ordered post-reveal copy decisions with the same effect evaluator. |
|
||||
| Battle plan, revealed components and Rules presentation | Name and inspect the original Mirror. An additional public description can name the copied revealed weapon after both plans reveal. No extra acknowledgement is needed for a deterministic copy. |
|
||||
|
||||
@@ -65,23 +65,22 @@ Portable Snooper is concurrently being integrated by the parent. Consume its fin
|
||||
but cannot alone open a genuine setup. CHOAM's Treachery deck supplies Poison
|
||||
Tooth and Artillery even without Ix, while the full Richese cache supplies Stone
|
||||
Burner. A public configuration gate therefore cannot isolate ordinary copies.
|
||||
Rejecting according to a concealed opposing hand/plan would leak information;
|
||||
rejecting after commitments could strand the battle. Do not remove physical
|
||||
cards or manufacture a restricted deck to claim complete-game support. Mirror
|
||||
remains gated pending the existing copied-disposal ruling and copied-choice work.
|
||||
This qualifies the earlier ordinary-slice recommendation below; it does not
|
||||
invalidate the existing focused arithmetic evidence or answer the user question.
|
||||
Do not remove physical cards or manufacture a restricted deck to claim
|
||||
complete-game support. The user's copied-disposal interpretation removes that
|
||||
specific blocker. The bounded engine now admits Mirror with physical-card
|
||||
custody, public Stone feasibility and copied-choice event checks; it does not
|
||||
certify combined expansion modes or complete Richese starts.
|
||||
|
||||
- **Copied compulsory disposal:** the FAQ names physical Tooth/Artillery, while Mirror copies a weapon. The retrieved primary sources do not explicitly say whether their disposal exception also applies to the physical Mirror. Separate combat effects from cleanup and obtain a ruling before certifying those pairings. This does not justify blocking ordinary projectile/poison/Lasgun/Poison Blade/selected-role copies.
|
||||
- **Stone Burner foundation:** the full effect is presently unsupported. Basic undialed counts follow physical forces minus dialed losses; ties use ordinary aggressor priority unless overridden. Advanced mixed/support-dependent dials can permit different physical casualty allocations, which now affect who wins; the present engine chooses those only for an already determined winner. Stone's original choice and allocation timing must be implemented/audited before its copied form. This is an underlying special-outcome problem, not uncertainty over whether Mirror copies a valid weapon.
|
||||
- **Copied compulsory disposal:** the physical Mirror follows ordinary winner retention even if it copies activated Tooth or Artillery, by the user's selected product interpretation. Keep physical identity separate from the effective attack and do not present this as a publisher ruling.
|
||||
- **Stone Burner composition:** the original Stone effect has a runtime foundation with a public precommit casualty-feasibility guard and one saved choice. A copied Stone needs the same feasibility for the Mirror holder without inspecting the opposing sealed plan, plus separate copy-first choice ownership. This is an outcome-integration problem, not uncertainty over whether Mirror copies a valid weapon.
|
||||
- **Higher modules:** inactive leader skills may modify attacks, defenses or card roles. No combined leader-skill certification follows from the matrix. Two physical Mirrors are outside the verified inventory rather than a normal supported interaction.
|
||||
|
||||
## Required verification before claiming the slice
|
||||
|
||||
Tests should cover every matrix row in both attacker/defender positions; paired defenses; no-attack copies; Mirror plus defensive Weirding Way; named Voice and physical prescience/Truth commitments; Lasgun explosion including advisors/spice and traitor preemption; copied Tooth choice order independent of storm order; once-only global Artillery suppression; exact physical retention/discard policy after its ruling; Moritani eligible-card filtering; JSON restoration between reveal and choices; stale event rejection; and identical unauthorized projections with different opposing hands. Run all four AI profiles through a complete supported battle, including a Mirror with no useful copy, without an acknowledgement or deadlock.
|
||||
|
||||
Five facets remain partial: source audit and component text are present; authoritative behavior, player controls, AI and integrated verification have not been activated by this document. Existing tests of ordinary battle cards are useful regression evidence, not proof of Mirror behavior.
|
||||
The earlier five-facet audit is superseded only for the bounded CHOAM/Richese-deck battle path. Combined expansion modules, leader-skill role changes, every historical save and full Richese-game acceptance remain outside this checkpoint.
|
||||
|
||||
## Pending user clarification (2026-09-06)
|
||||
## User-selected cleanup interpretation (28 September 2026)
|
||||
|
||||
The coordinating agent asked whether a Mirror copying an activated Poison Tooth or Artillery must inherit that card’s mandatory discard on victory, or whether the physical Mirror uses ordinary winner retention. No answer has been received at this checkpoint. The question does not concern Portable Snooper, whose ordinary winner retention follows the general FAQ. Do not infer an answer from the first preselected UI option or elapsed time.
|
||||
After a bounded source search, no GF9 passage was found that expressly applies Tooth/Artillery's named winner-discard exception to the physical Mirror. The user selected retention of a victorious Mirror regardless of those copied attacks. The original Tooth/Artillery cards retain their own mandatory-discard rules. The bounded runtime implements this physical-card distinction; it is not a publisher clarification or complete combined-mode acceptance.
|
||||
@@ -42,6 +42,8 @@ Updated 14 September 2026. This is the authoritative navigation index for existi
|
||||
| Guild Secret Ally | One explicit Guild-priced ordinary shipment; borrowed prices/routes preserve native identity. Free Fremen reinforcement remains a separate choice. | [Route contract](NEXUS_GUILD_SECRET_ALLY_RULES.md), [verified runtime](NEXUS_GUILD_SECRET_ALLY_RUNTIME.md) |
|
||||
| Homeworld custody and mobility | Physical home/visitor groups, population thresholds, tariffs and transport permissions retain distinct sources; Homeworld immunity is not universal immunity. | [Homeworld rules](HOMEWORLD_RULES.md), [benefits](HOMEWORLD_BENEFITS_RULES.md), [mobility](HOMEWORLD_MOBILITY_RULES.md), [invasion](HOMEWORLD_INVASION_RULES.md), [Guild transport](GUILD_HOMEWORLD_TRANSPORT_RULES.md) |
|
||||
| Homeworld effects | Keep original payment/revival/placement identities and qualification observations; observations alone do not choose an occupied-benefit owner. | [Payments](HOMEWORLD_PAYMENT_INCOME_RULES.md), [card economy](HOMEWORLD_CARD_ECONOMY_RULES.md), [Collection](HOMEWORLD_COLLECTION_RULES.md), [revival deployment](HOMEWORLD_REVIVAL_DEPLOYMENT_RULES.md), [victory reinforcement](HOMEWORLD_VICTORY_REINFORCEMENT_RULES.md), [replacement](HOMEWORLD_REPLACEMENT_RULES.md), [Tupile](HOMEWORLD_TUPILE_INTELLIGENCE_RULES.md) |
|
||||
| Duke Vidal revival custody | The user selected set-aside custody after Ecaz revives the shared disc: revival clears the Tanks but does not itself grant battle control. Ecaz still needs a separate Ambassador or Nexus acquisition; only Ecaz may revive Duke, including by Ghola. This resolves one post-revival product interpretation, **not** the separate six-disc repeated-cycle, exceptional capture or battle-used Ghola questions. No publisher clarification assigning a post-revival controller was located. | [Publisher Ecaz/Moritani pp. 7–9](https://gamers-hq.de/media/pdf/0f/7a/86/Dune_EcazMoritani_Rulebook_EN.pdf#page=9), [revival readiness](ECAZ_DUKE_REVIVAL_READINESS.md) |
|
||||
| Mirror Weapon copied-card cleanup | The user selected ordinary winner retention for the physical Mirror even if its effective copy activates Tooth or Artillery. The original Tooth/Artillery cards retain their named mandatory-discard exceptions. This is a product interpretation, **not** a located publisher ruling. Independent copy-first Tooth/Stone choices and physical cleanup now have a bounded CHOAM/Richese-deck battle runtime; combined modules and full Richese games remain gated. | [Printed Mirror face and source audit](MIRROR_WEAPON_ENGINE_AUDIT.md#user-selected-cleanup-interpretation-28-september-2026) |
|
||||
|
||||
Shipment-only AND/OR now follows the FAQ's whole-question truth: Yes to AND
|
||||
requires all conditions, Yes to OR requires one, and No negates the whole
|
||||
@@ -69,7 +71,6 @@ These are unresolved in the cited records. Do not infer an answer from elapsed t
|
||||
| Sandmaster / native HMS relocation | No official source located establishes that passengers remaining inside the HMS enter outside territories for this skill. Extra collection eligibility is pending a user ruling; native sector collection and ordinary force entry/exit remain available. | [Source comparison and question](SANDMASTER_MOVEMENT.md#21-september-native-hms-relocation-eligibility) |
|
||||
| Ambassador/Terror arrival priority | Both optionally react to the same entry, but no publisher/designer priority was found. The order can change Fremen relocation versus Atomics losses. A user question has been sent: keep the overlap gated pending an official ruling, or use explicitly provisional storm order. No answer is assumed; Baliset remains a separate pre-entry prevention effect. | [Reproduction and source boundary](DEFERRED_MOVEMENT_ARRIVAL.md) |
|
||||
| Sapho remaining timing | First versus unspent Advanced Guild priority, partly completed combined turns, cyclic auction duration and later battle timing stay guarded. The existing pre-plan opportunity supports [early aggressor](SAPHO_AGGRESSOR.md). Prior questions remain unanswered. | [Source audit](JUICE_OF_SAPHO_SOURCE_UPDATE.md), [battle review](JUICE_OF_SAPHO_BATTLE_REVIEW.md) |
|
||||
| Mirror Weapon | Whether copied Tooth/Artillery mandatory-discard rules attach to the physical Mirror remains unanswered. Every genuine Richese setup includes those cards and Stone Burner; an ordinary-copy-only admission gate cannot depend on concealed custody or alter the printed deck. | [Engine audit](MIRROR_WEAPON_ENGINE_AUDIT.md) |
|
||||
| Semuta Drug | Full-hand take-before-discard and the privacy-neutral immediate reaction protocol remain unresolved. Typed discard continuations already exist; they are not activation. | [Source update](SEMUTA_SOURCE_UPDATE_20260907.md), [privacy review](SEMUTA_PRIVACY_REVIEW.md) |
|
||||
| Leader Skills edge cases | Capture/replacement eligibility, Banker escrow custody, Smuggler modifier/allocation boundaries, Mentat empty-hand fallback, modified Diplomat defenses and simultaneous optional timing remain source gaps. After an online publisher/designer/tournament check found no explicit priority ruling, the bounded standalone Diplomat retreat prototype explicitly chooses printed/copied disc strength and a surviving-loser retreat before ordinary casualties; other combinations remain guarded. This is an implementation interpretation, not an official clarification. | [Material boundaries and selected retreat interpretation](LEADER_SKILLS_RULES.md#bounded-diplomat-retreat-interpretation), [Diplomat defense boundary](DIPLOMAT_DEFENSE.md#evidence-and-remaining-scope) |
|
||||
| Smuggler collection strength | A fresh primary-source check found no modifier ruling. The user was asked whether to keep affected combinations gated, use printed/copied disc value, or include leader bonuses with Stunner zero. No answer is assumed. The reveal-bound deferred receipt is supported as an explicit timing inference; unmodified lower collection is now [prototyped](SMUGGLER_BATTLE.md); modified strength, multiple positive piles and combined modules remain gated. | [Smuggler follow-up](LEADER_SKILLS_RULES.md#20-september-smuggler-follow-up) |
|
||||
|
||||
Reference in new issue
Block a user