Agree on the purpose of the room
Before creating the room, decide whether the session is casual practice, a feature test, or a serious matchup rehearsal. DM Value online play is an Experimental Beta and is not an official tournament environment. Some common operations are synchronized and validated, while unusual card-specific effects may still require player-confirmed steps or manual movement.
Agree on the format, deck version, who will make the final call on an unclear interaction, and whether the game should pause when a technical issue appears. This short conversation prevents a table limitation from becoming a rules dispute.
Run a pre-match connection check
Both players should enter the room before either begins setup. Confirm that the displayed names, room rule, and deck choices are correct. Make one harmless visible action, such as opening a permitted panel or confirming the setup state, and verify that both browsers agree before drawing opening hands.
- Both players are using a supported desktop browser and a stable connection.
- Each player loaded the intended checked deck version.
- The shared table shows the same turn, card counts, and setup status.
- Chat works and will be used only for game coordination.
- Neither player will share passwords, tokens, or other sensitive information in chat.
Announce consequential manual actions
For ordinary synchronized actions, the visible table and log usually provide enough context. For a manual resolution, briefly state the source card, the intended effect, the affected cards or zone, and whether the opponent must confirm a choice. Wait for agreement before moving several hidden or ordered cards.
Use the smallest sequence of operations that represents the decision. Large batches of unrelated moves are harder to verify and harder to recover if one player loses connection halfway through.
Protect hidden information
A synchronized table must distinguish information both players may see from information belonging to one player. Do not paste hand contents or private deck order into chat unless the game action intentionally reveals them. When a workflow opens a private selection, complete it through the provided player-specific view and confirm only the public result.
If the interface appears to expose information that should remain private, stop the match and report it. Do not continue testing the exposure with a real competitive deck; use a disposable test state if reproduction is necessary.
Pause first when states disagree
When the two screens disagree, both players should stop making changes. Compare the room revision, active turn, public zone counts, and the last agreed action. Refreshing or reconnecting may recover the authoritative state, but repeated clicks while the connection is uncertain can create a second problem on top of the first.
- Pause and identify the last action both players saw.
- Compare only public state first; do not reveal private cards to debug casually.
- Allow the browser to reconnect or return to the lobby once if needed.
- Continue only when both screens match the agreed public state.
- If recovery fails, end the test and submit a concise reproduction report.