Windbrisk Heights — Allows you to hideaway a card, but will not allow you to cast it even if you have met the requireme…

[matthewevans]

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

Thread: Windbrisk Heights
Cards: none detected
Parser status: fully_parsed
Extraction confidence: 0.90

Summary

Allows you to hideaway a card, but will not allow you to cast it even if you have met the requirements.

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

No card names were detected for this report.

---

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

[mike-theDude]

Card identified as Windbrisk Heights. Verified Oracle text: "Hideaway 4 ... {W}, {T}: You may play the exiled card without paying its mana cost if you attacked with three or more creatures this turn."

The {W}, {T} activated ability parses with the correct cost, the correct "attacked with three or more creatures" condition, and without_paying_mana_cost: true — but its CastFromZone target is TargetFilter::ParentTarget, which is the ephemeral within-resolution-chain reference used for anaphora inside a single ability's sub-ability chain. Windbrisk Heights' activation is a standalone activated ability with no runtime chain linkage back to the Hideaway ETB trigger that originally exiled the card (which may have resolved many turns earlier), so ParentTarget can never resolve to the hidden-away card and the ability effectively has no valid target when activated — matching the report exactly ("will not allow you to cast it even if you have met the requirements").

The engine already has the correct persistent mechanism for this: TargetFilter::ExiledBySource, backed by state.exile_links (crates/engine/src/game/exile_links.rs), used elsewhere for cards that reference something exiled by a source across time. I confirmed this is a class-wide bug, not specific to this card — Mosswort Bridge and Shelldock Isle's identical follow-up abilities also parse to ParentTarget instead of ExiledBySource. Fix belongs in the Oracle parser's "play the exiled card" resolution for Hideaway-style activated abilities (crates/engine/src/parser), swapping ParentTarget for ExiledBySource when the reference is on a standalone activated ability rather than a same-chain sub-ability.

Status: confirmed — classifier: supported-aspect-defect