Build a deck without losing sight of the plan
A deck list is more than one hundred card names. It is a record of the jobs those cards perform, the restrictions they obey and the experience the brewer wants to create. Esper Forge keeps those decisions visible from the first card through later tuning.
Structure before decoration
Commander gives brewers enormous freedom, but a list still needs mana, card advantage, interaction, protection and credible ways to end a game. The Esper Forge workspace keeps quantities and zones explicit so a beautiful theme cannot quietly hide a twenty-five-land mana base or a missing draw engine. Structural signals are guidance rather than a command: the brewer remains responsible for the final list.
Cards are stored as canonical Oracle identities while their chosen printings remain available for display and printing. That separation matters for double-faced cards, localized names and reprints. It also lets the validator reason about one real card even when many physical treatments exist.
Legality is checked from the saved list
A Commander deck is evaluated against its actual command zone, combined color identity, singleton rules, banned cards and card count. Supported commander pairs are treated as a pair instead of two unrelated legendary creatures. Upcoming cards can be used when their known Oracle data already makes them legal, but preview information should always be checked again after release.
Esper Forge separates legality from power. A legal deck may still be inconsistent, and a strong card does not automatically make a list optimized. Bracket signals, mana structure and card roles are therefore presented as different kinds of information rather than compressed into one unexplained score.
Changes remain understandable
Deck history records additions and removals in paired columns. This makes manual edits and accepted AI proposals auditable: a brewer can see what changed instead of guessing after several tuning sessions. Duplicating a deck creates a fresh workspace and intentionally does not copy its private AI conversation.
Sideboard and Maybeboard are working zones, not hidden dumping grounds. Tune proposals stage incoming cards in the Sideboard and outgoing cards in the Maybeboard until the brewer accepts individual swaps or the complete proposal. Tokens remain separate because they are game pieces, not cards counted toward the deck size.
A practical build flow
- 01
Choose the command zone
Search for one legal commander or a supported pair; their color identity establishes the available card pool.
- 02
Build by role
Add lands, acceleration, draw, interaction, protection and finishers while preserving the chosen theme.
- 03
Validate and test
Review legality and structure, then playtest before changing one category at a time.
- 04
Keep evidence
Use history, Maybeboard and duplicate decks to compare ideas without losing the original list.
Deck builder questions
Does Esper Forge force a deck template?
No. Suggested role ranges are starting points. Format legality is a hard boundary; structure and power guidance remain decisions for the brewer.
Can I import an existing deck?
Yes. Lists and supported preconstructed decks can be imported, saved and edited like decks built from scratch.
Are public and private decks treated differently?
Yes. Visibility is controlled per deck. Private and testing lists are not presented as public community content.