Eldrazi Monument still sacrifices itself — I thought it worked fine before, but now, even if you sacrifice a creature a…

[matthewevans]

Reported in Discord: https://discord.com/channels/1485498006781427802/1515599653754765352/1515599653754765352

Thread: Eldrazi Monument still sacrifices itself
Cards: eldrazi monument
Parser status: fully_parsed
Extraction confidence: 0.90

Summary

I thought it worked fine before, but now, even if you sacrifice a creature as required, [[Eldrazi Monument]] still puts itself in the graveyard.

Oracle text (verified from client/public/card-data.json)

eldrazi monument

Creatures you control get +1/+1 and have flying and indestructible.
At the beginning of your upkeep, sacrifice a creature. If you can't, sacrifice this artifact.

---

_{report_id: discord:1515599653754765352:1515599653754765352:0 · discord: 1515599653754765352/1515599653754765352}

[mike-theDude]

Verified against current Oracle text: "At the beginning of your upkeep, sacrifice a creature. If you can't, sacrifice this artifact." The parsed trigger chain looks structurally correct: a mandatory Sacrifice{Typed(Creature)} followed by a sibling Sacrifice{SelfRef} gated on Not(ZoneChangedThisWay{Any}) — the same CR 608.2c "if you can't" pattern used successfully elsewhere in the engine (e.g. Roots of Wisdom's "if you can't, draw a card").

However, that gate is only exercised by regression tests where the mandatory parent effect is RemoveCounter (fading) or Bounce — there is no existing coverage for a mandatory Sacrifice acting as the parent whose success/failure needs to suppress a sibling Sacrifice. ZoneChangedThisWay reads state.last_zone_changed_ids, which is repopulated per-effect from GameEvent::ZoneChanged — Sacrifice does emit that event via the normal zone-delivery pipeline in the untouched case, but this exact "mandatory Sacrifice → gated self-Sacrifice" combination is untested, and the report describes a concrete, reproducible symptom (self-sacrifice firing even when the required creature sacrifice succeeded) consistent with that gate misfiring for this effect combination.

This warrants an engine-side investigation into AbilityCondition::ZoneChangedThisWay evaluation specifically when the parent effect is Effect::Sacrifice (not Bounce/RemoveCounter), likely in crates/engine/src/game/effects/mod.rs and crates/engine/src/game/sacrifice.rs.

Status: confirmed — classifier: supported-aspect-defect

[mike-theDude]

Reviewed against current main: the relevant continuation path was fixed in 7f0c79b54. A ZoneChangedThisWay gate is now deferred while an interactive sacrifice choice is pending, then reevaluated only after the sacrifice completes and populates the moved-object ledger. That prevents Eldrazi Monument's gated self-sacrifice from firing after a creature was successfully sacrificed. This appears resolved; please close the issue.

[matthewevans]

Closing per mike-theDude's triage above — verified fixed/resolved on current main. If this still reproduces on a current build, please reopen with a fresh repro.