PUBLIC BETA CHANGELOG

What changed—and why it matters.

This log summarizes user-facing changes to DM Value. It is not a promise that every card interaction is automated; current boundaries remain documented on Known Limitations.

UPDATE 04

Practical guide library published

Added a public, no-login knowledge base with eight original workflows for deck review, Solo Play, Online Beta preparation, local assets, manual resolution, proxy data, multi-card state, and troubleshooting.

  • Every guide identifies its audience, intended outcome, boundaries, and related reading.
  • The sitemap and permanent navigation now expose the guide hub, individual articles, and this update log.
  • The content separates service operation from official game rulings and does not distribute official card artwork.
UPDATE 03

Modern card and composition workflows expanded

Improved the way the table represents modern multi-face, mode-specific, shield, and multi-card composition state while keeping player ownership and hidden information boundaries explicit.

  • Mode-specific proxy information can reflect the active card state more accurately.
  • Shield and composition operations gained clearer insertion and ordering choices for layered objects.
  • Online composition changes use validated shared commands instead of trusting a client-only result.
UPDATE 02

Public service information and safer match recovery

Published the About, How It Works, FAQ, Known Limitations, Privacy, Terms, Disclaimer, and Contact pages while strengthening online result, undo, and shared-state recovery paths.

  • Service purpose, unofficial status, Local Asset Mode boundaries, and Experimental Beta limitations became readable without signing in.
  • Public discovery files and canonical routing were aligned with dmvalue.app.
  • The gameplay board remained free of advertising placements and official card artwork.
UPDATE 01

Authoritative shared operations broadened

Moved more online choices through player-confirmed, server-validated workflows so that both browsers can agree on a public result without exposing unnecessary private information.

  • Shared zone search, ordered movement, random discard, and manual-cost summaries received stricter validation.
  • Attack transitions and special-object setup gained reusable guided paths.
  • Unsafe or stale requests fail closed instead of silently mutating an uncertain table state.
WHERE TO GO NEXT

Use a workflow, then report the boundary

Choose a task-specific article from the Practical Guides. If the current build behaves differently from the documented workflow, collect the smallest reproducible example and use the Contact page.