Publish a new deck version
Save a stable decklist version for history and match tracking without changing who can see the deck.
Last updated
What publishing means
Publishing a deck version records the current decklist as a stable version from a deck in Brewing. It does not mean making the deck public.
Deck visibility still controls who can see the deck: Private, Shared, or Public. Publishing and visibility answer different questions. Publishing answers which exact list is ready to reference; visibility answers who may view it.
Why versions matter
Decks change over time. A published version lets you keep the old list available after you tune the deck, swap cards, or change the commander.
Match records use published deck versions so a match points to the list that was actually played. Without a published version, the match could drift as the working deck changes.
Publish the current list
Publish after the list is accurate enough to serve as a record. You can keep editing the deck afterward and publish another version when the next meaningful change is ready.
- Open the deck from Brewing.
- Review the current cards, zones, commander, companion, and format.
- Fix import errors or missing cards before publishing.
- Select Publish.
- Use the published version for match tracking.
Result
Deckonomicon marks the current decklist as published and keeps it available as a version. The deck does not become public unless its visibility is set to Public.
FAQs
13 searchable answers
Frequently asked questions about using Deckonomicon.
- Does importing a deck publish it automatically?
- What do Public, Shared, and Private deck visibility mean?
- Does publishing a deck make it public?
- Why publish a private or shared deck?
- What do I need before tracking a match?
- Can I record a match when a player has no published deck?