Competitive duelists iterate on combo lines constantly. A line that was optimal the week a set dropped may no longer be correct two weeks later when the meta has adapted and opponents have identified the interrupt points. Tracking those iterations — and being able to revisit old lines when the meta shifts again — is a skill that separates well-prepared teams from everyone else.
The cost of undocumented iteration
Most players have experienced this: you refine a combo over several testing sessions, improve the sequencing, find a cleaner line through a hand trap — then two weeks later you can't remember exactly what the updated line was. You play the old version from memory, get hit by the interrupt you already solved, and lose a game you should have won.
The underlying problem is that combo refinement happens in working memory. You test, you adjust, you move on. Nothing gets written down because writing it down feels slower than just playing. But the compound cost of re-solving the same problems across a tournament season adds up to far more time than documentation would have taken.
Named snapshots: save before you experiment
The simplest versioning discipline is to duplicate a combo before you change it. Before a testing session where you plan to rework a line, save the current version under a descriptive name — something like 'Pure K9 Jan25 main line' — and keep it private. Then work on the new version as a separate combo.
This gives you a clean rollback point. If the new line turns out to be weaker in a matchup you didn't anticipate, you still have the baseline. It also gives you a historical record of why you made the change, since you can add a note in the description explaining the context.
Description-as-changelog
The description field on each combo is more versatile than it looks. Beyond describing what the combo does, you can use it as a lightweight changelog. A format like '[2025-02-15] Updated step 4 to avoid Nibiru window. [2025-01-20] Initial version' gives anyone reading the combo a clear sense of its history without needing a dedicated versioning system.
For team combos, prepend the author's handle to each change note so it's clear who made which decision. This is especially useful when multiple team members are contributing to the same archetype's documentation.
Tagging by format context
One pattern we see from experienced teams is tagging combos with the banlist or set release that made them viable. A combo that relies on a card that was recently unlimited plays differently from the same archetype's line from six months ago when that card was semi-limited. Keeping both versions, tagged by format date, means you don't have to rebuild old lines from scratch if the card gets hit again.
Format tags in the title are the most direct approach — 'Orcust pure [TCG Apr25]' is immediately scannable in a list. The archetype field serves a similar purpose for filtering: keeping archetype names consistent across your team's combos means everyone can find all relevant lines for a given deck without a naming convention discussion.
Private versus public sharing
YGO Combo Builder supports private combos for work-in-progress lines and public combos for finished, tested sequences you're comfortable sharing with the community. For team prep, the practical workflow is to keep experimental lines private until they've been tested in at least two different matchup contexts, then decide whether to publish.
Publishing forces a useful discipline: you have to write a description that someone who didn't sit in on your testing sessions can understand. That act of explanation often reveals gaps in the line itself — steps where you assumed context that isn't obvious from the card sequence alone.