Chaos Warp — Had the AI opponent cast a [[Chaos Warp]] on one of my creatures.

[matthewevans]

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

Thread: Chaos Warp
Discord thread id: 1522860024009986138
Discord message id: 1522860024009986138
Cards: chaos warp
Parser status: fully_parsed
Extraction confidence: 0.90

Summary

Had the AI opponent cast a [[Chaos Warp]] on one of my creatures.

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

chaos warp

The owner of target permanent shuffles it into their library, then reveals the top card of their library. If it's a permanent card, they put it onto the battlefield.

---

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

[mike-theDude]

Verified Chaos Warp's Oracle text against card-data.json: "The owner of target permanent shuffles it into their library, then reveals the top card of their library. If it's a permanent card, they put it onto the battlefield." At the time this report was filed (2026-07-07 08:21 UTC), Chaos Warp had no resolver support for the owner-shuffle/reveal/put-onto-battlefield sequence — that logic (plus the underlying quantity/trigger plumbing it depends on) was added later the same day in commit d9735c781 ("engine: support Mycotyrant Tidus Doom and Chaos Warp", PR #5234, merged 2026-07-07T18:08:54Z), which post-dates this report. Current card-data.json (regenerated from HEAD) shows Chaos Warp fully parsed with a ChangeZone resolver chain implementing the shuffle-reveal-battlefield sequence. This report reflects a build that predates the fix and should already be resolved on current main.

status:fixed-unreleased, classifier:unsupported-aspect — fixed by PR #5234 (commit d9735c7), merged after this report was filed.