TLDR: A useful proxy Vintage Cube test needs two things before anyone opens a pack: every card must be indistinguishable face down, and every session must follow a recorded draft protocol. Build a complete first version, audit the sleeved pool, document how the draft works, log more than match wins, and make narrow revisions between versions. The goal is not to prove that your Cube is “balanced” after one dramatic evening. It is to create repeatable drafts that reveal patterns over time.
A proxy vintage cube test lets you evaluate Moxen, dual lands, fast mana, narrow combo pieces, and other expensive cards without turning list design into a referendum on everyone’s collection. That makes proxies especially useful here: the environment can be tested as an environment, rather than as a mostly complete Cube with several suspiciously budget-shaped holes.
This guide concerns transparent playtest cards used with the consent of a private, casual group. It does not cover cards intended to pass as authentic, and it does not make those cards legal in sanctioned events. Wizards distinguishes visible playtest cards used outside sanctioned competition from counterfeits or reproductions presented as genuine; sanctioned-event policy generally requires authentic cards except for limited judge-issued proxy circumstances. Read Wizards’ policy discussion on playtest cards and sanctioned events.
Define what your proxy Vintage Cube test is testing
“Vintage Cube” can describe several different projects. You might be recreating a named list, building a general powered singleton Cube, or maintaining a personal environment that uses cards legal in Vintage. Those are related ideas, not interchangeable specifications.
Write down the project’s baseline before choosing the final card pool. If you are recreating a published list, record its name, source, and revision date. A live list can change, so “the Vintage Cube list” is not enough for later comparison. If this is your own powered Cube, state that directly and describe its intended experience: explosive games, broad archetype support, combo density, nostalgic cards, or whatever actually guides inclusion.
- Cube name and version number
- Reference list and revision date, if applicable
- Total card count
- Singleton or duplicate policy
- Included power, fast mana, conspiracies, or other unusual components
- Draft method and expected player count
- House rules, mulligan rules, and any special errata
- Cards or archetypes this version is specifically intended to test
Wizards describes Cube as a selected card pool from which draft packs are created, with the construction itself remaining customizable. Its introductory Cube guidance also emphasizes repeated play and revision rather than a single final build. Wizards’ Cube-building overview provides a useful official starting point for that basic structure.
Build a complete draftable version first
Testing only the expensive substitutions can answer a narrow question such as whether Black Lotus is exciting in your existing list. It cannot show what happens when fast mana, premium fixing, efficient interaction, reanimation targets, and combo support all occupy seats in the same draft.
Start with a complete version that can support your chosen draft format. This exposes interactions that isolated substitutions hide. A powerful card may be fine by itself but oppressive when the Cube also supplies abundant acceleration and protection. A narrow payoff may look weak when its support cards are missing, or look dominant because too many redundant enablers were added at once.
For broader guidance on making themes visible and decks functional, use the MTG proxy Cube drafting guide. For this first test version, resist polishing every speculative slot. The initial list is a hypothesis. It only needs to be coherent, draftable, and documented well enough that the next version can be compared with it.
Protect hidden information before the draft
A proxy can be readable and attractive while still being a marked game piece. If one card is shorter, stiffer, more curled, or backed differently, a player may identify it in a pack or library without seeing its face. That corrupts the test even when nobody intends to exploit the difference.
Magic’s Comprehensive Rules classify libraries and hands as hidden zones. The rules do not prescribe a physical proxy-audit method, but they explain why face-down consistency matters once the cards enter gameplay. Drafting creates another practical hidden-information problem: players should make picks from card faces and draft context, not from a recognizable edge or bend.
Sleeve the complete drafted pool in one sleeve model and batch, then perform a blind audit. Do not assume that a specific paper, card stock, insert, or printing method is automatically indistinguishable. Test the assembled game pieces at the table where they will be used.
Blind face-down audit
- Shuffle authentic cards and proxies together, if the Cube mixes them, then place samples face down under normal lighting.
- Look across the top and side edges for height, width, corner, color, or sleeve-fit differences.
- Gently handle randomized samples without looking at their faces. Check for stiffness, thickness, raised insert edges, curl, and unusual surface feel.
- Cut and shuffle small test piles. Watch for cards that separate, cling, bow, or repeatedly move to an identifiable position.
- Ask a second person who does not know the arrangement to identify suspected proxies. Any repeatable success is a failure to investigate, not a clever party trick.
- Replace inconsistent sleeves or components, then randomize and repeat the audit. Do not merely rotate the suspicious card to a different pack.
Authentic cards and proxies can coexist in a casual Cube if the group agrees and the finished, sleeved pieces pass the table’s face-down audit. The relevant gameplay question is not whether the fronts were produced in the same way. It is whether hidden cards can be distinguished by sight or touch. The accidental marked-card checklist offers a deeper audit for visible, tactile, and shuffle-based tells.
Double-faced cards need an explicit handling rule as well. A visible reverse face can reveal a pick or library card immediately. Use one consistent solution across the pool and explain it before drafting; the guide to handling double-faced proxy cards compares practical options.
Use repeatable draft logistics
A 360-card Cube exactly supplies eight players with three 15-card packs each: 8 × 3 × 15 = 360. That makes 360 a clean baseline for a full eight-player draft, not a mandatory Cube size or proof that the environment is well designed. Larger Cubes and alternative draft methods are valid, but they change which cards appear together and how often archetypes receive their support.
Before the first pack, record the variables below. Reusing the same protocol reduces noise between sessions. When a variable changes, label it rather than pretending the results are directly comparable.
| Variable | Record before play | Why it matters |
|---|---|---|
| Pool | Cube version and cards included | Connects observations to an exact list |
| Pod | Player count and player experience | Small or unfamiliar pods may draft archetypes differently |
| Packs | Pack count and cards per pack | Changes card exposure and pick pressure |
| Seats | Seating order and pass directions | Helps identify neighboring-color and signaling effects |
| Build | Deckbuilding time and minimum deck size | Keeps preparation conditions comparable |
| Rules | Mulligans, house rules, and special cards | Prevents rule changes from masquerading as list results |
| Matches | Round count and pairing method | Defines what a session result represents |
| Basics | Supply and access method | Avoids artificial mana constraints |
| Reset | Sorting, counting, and randomization process | Reduces missing-card and pack-construction errors |
Small-pod testing is still useful. A four-player draft can expose unreadable cards, broken interactions, dead sideboard material, or an archetype that never assembles. Label it as a four-player session with its actual pack structure. Do not pool its numbers uncritically with an eight-player, three-pack draft because card availability, signaling, and competition for colors all changed.
Record what happened, not just who won
Match records are useful, but Cube design is not a miniature professional league table. A deck’s result reflects its pilot, draws, pairings, draft seat, pack distribution, and the list itself. “Blue went 3–0” is an observation. “Blue is overpowered” is a conclusion that usually needs more evidence.
After deckbuilding, capture each deck’s main plan and major secondary package. You do not need a forensic transcript of every pick. A photo or exported list plus a short label—such as blue-red spells, mono-white initiative, or green ramp splashing reanimation—is enough to preserve the basic evidence.
- Which archetypes were attempted, completed, and abandoned
- Cards that wheeled repeatedly or remained in sideboards
- Payoffs drafted without enough support, and support cards without credible payoffs
- Fixing that was contested, ignored, or insufficient for the decks attempting to splash
- Early plays that decided games before meaningful interaction
- Cards that were powerful only in ideal situations
- Rules confusion, illegible text, or unclear custom treatments
- Match results and notable game patterns
- Player comments, attributed to the relevant deck or seat rather than treated as universal truth
Ask focused questions after the draft. “Was reanimator good?” invites a vague verdict. Better questions include: Did the drafter see enough discard outlets? Were the targets useful outside the reanimation deck? Did graveyard interaction appear in the pod? Did fast mana cause the deck’s wins, or did its core plan function without it?
Separate patterns from draft noise
One failed archetype does not prove that its cards should be removed. Its drafter may have moved in too late, opened the support in the wrong order, fought a neighbor for the same pieces, or built the deck incorrectly. Likewise, one spectacular combo finish does not establish that a package is too strong.
Look for repeatable friction across sessions: cards that consistently fail to make decks, an archetype whose support is consumed by stronger decks, fixing that cannot support advertised color combinations, or games repeatedly decided before most decks can interact. Wizards’ own Cube guidance treats balancing as a process of repeated play-throughs and change over time.
Pod composition also matters. Experienced powered-Cube drafters may value lands, cheap interaction, and flexible cards differently from first-time players. Record that context. The list may have a discoverability problem rather than a raw power problem, which could call for clearer archetype support instead of simply adding stronger cards.
Revise with a versioned change log
There is no universal number of drafts that proves a Cube is balanced, and no fixed number of swaps that is correct after every session. The practical rule is to change narrowly enough that you can explain what the revision was supposed to accomplish.
Give each revision a number and date. For every swap, record the outgoing card, incoming card, observed problem, and expected effect. “Cut card A for card B” preserves inventory. “Replace a narrow five-mana payoff with a flexible two-mana enabler so the archetype can develop before fast decks close the game” preserves the hypothesis.
- Freeze the current list as a named version.
- Summarize the strongest repeated observations.
- Choose the smallest coherent batch of changes that addresses one or two problems.
- Write the expected result before the next draft.
- Keep draft logistics as consistent as practical.
- Compare the next session with the stated hypothesis, not with a vague memory of how the old Cube felt.
- Retain the prior list so you can roll back a change that creates new problems.
Avoid replacing a large section after one strange draft. Pack distribution and player decisions can produce extreme nights, and broad changes erase your ability to attribute improvement or decline. Bootleg MTG’s broader Cube guidance likewise recommends checking physical consistency and avoiding sweeping conclusions from a single session.
Use a short disclosure before every session
Even among friends, spend thirty seconds establishing what everyone is drafting. This is both etiquette and test control.
- This is a casual, non-sanctioned Cube session.
- The pool contains transparent playtest proxies and, if applicable, authentic cards.
- The group has checked the sleeved pool for face-down consistency.
- The Cube version and intended test questions are identified.
- House rules, mulligans, special card treatments, and the draft method are stated.
- Players know how to report physical tells, unreadable cards, and gameplay observations during or after the session.
If the draft takes place at a store, venue permission remains separate from pod consent and sanctioned-event policy. Confirm the store’s rules before arriving with the Cube; the LGS proxy etiquette guide explains those separate layers.
The useful next step
Build version 0.1, sleeve the entire pool, and run the blind face-down audit before scheduling the draft. Then write one sentence naming the question the session should answer. A fair proxy Vintage Cube test is not defined by how accurately it imitates an expensive collection. It is defined by hidden information staying hidden, logistics staying comparable, and every revision teaching you something about the environment.