← Duel Masters English

PLAY'S · Rules · 1 Oct 2026

Six ways to make a card stop existing, all patched on 1 October

The publisher keeps one running notice of known issues and edits it in place. It was updated on 30 September with twenty-four issues — six days after set 37 arrived — and again on 1 October to record that the fix for all twenty-four went live at about 18:30 that evening. One of them could lock the new story chapter. One cancelled an attack made with the set's own keyword. Six of them removed a card from the game altogether.

What the notice says

24
addressed in this round — the notice records the fix going live at about 18:30 on 1 October.
10
listed separately as already fixed before this round.
7
still open — five are display problems, two change what happens in a game.
Rewritten 3 October This page first said the twenty-four issues were newly confirmed and not yet fixed, that no fix date was given, and that five of them made a card stop existing. Read again on 3 October, the notice heads that list — the issues addressed this round — records the fix reaching the game at about 18:30 on 1 October, and contains six "ceases to exist" cases, not five. The still-open list has grown from four to seven.

Whether the notice was reworded or whether this page read it wrongly cannot be checked now. The publisher edits this one notice in place and no earlier copy is archived — which is the first thing this page said about it.

The notice now carries one date: it says the fix was reflected in the game at about 18:30 on 1 October. This page describes the ones that connect to what this site has already written about; it does not reproduce the list.

The pattern worth naming

Six of the twenty-four end the same way. The Japanese is — "ceases to exist in any zone".

Not destroyed, not removed, not shuffled away. The card is no longer in the battle zone, the graveyard, the hand, the deck, the mana zone or the shields. It is gone from the game. Six separate bugs, six different routes to the same end

They are reached by different routes — a field card moved while its destination zone is full, a creature put into play by a spell and then destroyed, gods moved after a mass summon, a spell revealed by a creature that then leaves, the bottom card of a face-up shield stack, and a Twinpact card the opponent sends to the graveyard with a replacement effect as you cast its spell half. Different cards, different triggers, same result.

The ones that touch this site's coverage

All four were in the patched batch Every issue described below is one of the twenty-four, and the notice records the fix for all twenty-four reaching the game at about 18:30 on 1 October. They are kept here as a record of what the first week of the format actually contained, not as a list of live problems.
Story · can stop the game EPISODE 37, chapter two. In that duel, when the CPU opponent casts using the ability, the game can reach a state where it cannot proceed.

EPISODE 37 is the story chapter released with the set on 24 September. It is the newest thing in the game and it can soft-lock.
Keyword · J Change Attack with a creature that has J Change, swap it for , then use that creature's on-play effect to stack a Jokers NEO evolution creature on top of it — and the attack is cancelled.

J Change is one of the keywords this site documented when the set was revealed. This is the first confirmed bug in it.
Ceases to exist · the Magic Tools field with cards stored under it, turned into a shield or returned to hand while that destination zone is already at its limit, ends up in no zone at all.

This is the field card the Magic Tools decks are built on — the family that won the Grand Prix and led the new format for its first three days.
Ceases to exist · Clanvia Clanvia appears twice. If it leaves the battle zone between its on-play ability triggering and that ability resolving, the spell it revealed ends up in no zone. A second, smaller bug leaves the opponent's mana zone display stale until the next turn begins.

What this is, and what it is not

A digital card game publishing a bug list after a set is normal. Twenty-four issues listed six days after the set shipped, and patched the day after the list went up, is a number without much meaning on its own — there is no baseline here to compare it against, and the same notice records ten fixes.

What was worth reporting is which ones they were. The story chapter written for the set could stop. A keyword introduced by the set had a confirmed interaction that cancelled your attack. And the engine card of the most-played deck family could be removed from the game by a zone-limit edge case. All three were in the batch fixed on 1 October.

None of this is a balance change Four cards had their text changed at the release maintenance; that was deliberate and announced separately. The list described here is the publisher saying things do not work as written, which is a different kind of notice and carries no compensation.

Sources

Corrections and questions

If something here is wrong, please say so — that is the most useful thing you can do with this page. Comments use GitHub, so you will need an account, and everything posted lives in this site's own repository rather than on a third-party service. No tracking, no ads.