Automation supports play; it does not replace a judge

DM Value provides general table operations and selected guided workflows. It intentionally does not invent a ruling when card data or an unusual interaction cannot support a trustworthy automatic result. The official rules source or event organizer remains authoritative for the game rule itself.

Use a guided workflow when it clearly describes the action you are resolving. Use manual operations when the effect is unsupported, the workflow does not match the current state, or the players have already agreed on a ruling that only needs to be represented on the table.

Translate the effect into state changes

Before moving anything, identify the source, controller, affected zone, selection rule, order rule, destination, visibility, and final orientation. This turns a long piece of rules text into a short list of table changes. In online play, share that list with the other player before acting.

• Which card or rule created the action?
• Who chooses, and what information may that player see?
• Which exact cards or number of cards are affected?
• Does order, face direction, tap state, or stack position matter?
• What public result should both players confirm when complete?

Prefer small atomic operations

Move or update one logical group at a time. For example: reveal the required cards, select the destination cards, place them in the agreed order, then close the reveal state. Do not mix a later optional effect into the same batch merely because the interface allows several selections.

Atomic operations make the action log readable and reduce the amount of state that must be reconstructed if the last step was wrong. They also give the other online player a natural point to confirm before hidden information changes again.

Use undo only when the boundary is clear

Undo is safest immediately after a single mistaken operation, before either player has gained new hidden information or made a dependent choice. If a random shuffle, private selection, draw, or opponent response occurred after the mistake, mechanically rewinding one visible move may not restore the decision context.

For a complex mistake, pause. Record the last agreed public state and decide whether a full manual reconstruction or a fresh test is more honest. In a serious practice session, restarting from a documented checkpoint is preferable to guessing the contents or order of a private zone.

Write a useful limitation report

A report should explain the intended state transition, the operation used, the state actually produced, and whether the problem occurred in Solo Play or an online room. Include non-sensitive card identifiers, zone names, browser details, and concise reproduction steps. Do not include account credentials, private chat, or local image files.

The goal is not merely to name a card that lacks automation. The most useful report identifies the reusable operation that is missing, such as placing a face-down member under a face-up shield, choosing an owner-specific destination, or preserving an ordered group across a move.