TLDR: The useful Empower Jace complexity budget design lesson is not that every custom set needs an elaborate centerpiece. It is that complexity should buy something important. Empower Jace was designed to make Reality Fracture’s antagonist repeatedly visible in gameplay, and Wizards accepted its tracking burden because the mechanic carried narrative, mechanical, and visual weight. Custom-set designers should apply the same test: if one mechanic asks players to remember more, manipulate a special game object, or learn unusual interactions, it should define the set—and simpler supporting mechanics should make room for it.
Empower Jace is interesting precisely because it is not cheap design space. It creates or develops a planeswalker token, uses loyalty counters, and introduces a persistent object with its own abilities. That is considerably more demanding than a mechanic that adds a familiar counter or grants a temporary bonus. The mechanic earns attention because Wizards has explained why the set wanted that burden, not because complexity is inherently impressive.
In Reality Check, Part 2, published September 14, 2026, Mark Rosewater wrote that Empower Jace began with an “amass Jace” concept proposed by designer Jeremy Geist. The underlying problem was narrative visibility: a set focused on a single antagonist could not rely exclusively on individual planeswalker cards if it wanted that character to appear regularly across games. Empower Jace allowed many cards to contribute to the same recurring representation of Jace.
The official mechanics explanation makes the implementation concrete. When a player empowers Jace and does not already control a Jace planeswalker token, that player creates the blue token and puts the specified number of loyalty counters on it. Subsequent instances instead add that many loyalty counters to an existing Jace planeswalker token. The token has two printed loyalty abilities: one that surveils and another that draws a card.
That structure gives the mechanic several jobs. It puts the featured character onto the battlefield, creates continuity between otherwise separate cards, establishes a recognizable visual object, and gives players a repeatable reason to care about additional empower cards. The mechanic is not merely decoration attached to the story. It turns the story’s focal character into a recurring game object.
Rosewater also acknowledged the price. He described Empower Jace as consuming substantial “complexity points” and said Reality Fracture’s other mechanics had to be less complex as a result. Wizards accepted the cost because of the mechanic’s flavor and novelty. That is the part custom-set designers should underline: approving the centerpiece also means declining complexity elsewhere.
“Complexity points” should not be treated as a numerical formula. There is no useful calculation in which a planeswalker token costs seven points and a graveyard mechanic costs three. It is a design metaphor for limited player attention.
Rosewater has divided complexity into comprehension complexity, board complexity, and strategic complexity. Comprehension complexity concerns understanding what a card does. Board complexity concerns tracking the state of the game. Strategic complexity concerns recognizing the best way to use a card. Comprehension and board complexity are especially relevant to rarity because every player must process visible cards and permanents, even when they do not control them.
Empower Jace spends from more than one part of that budget. Players must learn the create-or-grow instruction, understand loyalty, track a shared token across multiple cards, and evaluate two activated abilities. Other cards can then add further interactions. None of those tasks is automatically unacceptable, but their combined weight has to be considered across an entire booster, battlefield, and game.
This is where custom sets often get into trouble. A designer evaluates each mechanic alone and concludes that every one is understandable. During a draft game, however, those mechanics overlap. A graveyard threshold affects combat, a transforming permanent changes its characteristics, a counter type unlocks activated abilities, and a token has text that is no longer visible under a pile of dice. Rosewater has warned that interactions among individually simpler mechanics can still make a set difficult to track.
Before approving a demanding mechanic, ask what disappears if it is removed. A strong focal mechanic should answer several of the following questions at once:
A mechanic does not need to satisfy every item, but “it is novel” is not enough. Novelty fades after players learn the trick. The mechanic must keep doing useful work afterward.
Empower Jace has an unusually clear job: make the antagonist present throughout games. Its token implementation also gives that presence a stable visual form. Whether players ultimately enjoy the mechanic or whether it produces a balanced Limited environment requires gameplay evidence not provided by the design explanation. The important lesson here is narrower: Wizards articulated a reason for accepting the burden and changed the surrounding set to accommodate it.
Rosewater wrote that the team considered restricting Empower Jace to uncommon and above. It instead retained broad access because it was intended to be the major mechanic players learned. More involved cards that grant additional loyalty abilities to Jace tokens were reserved for higher rarities.
That distinction is valuable for custom-set construction. If a mechanic is central, players may need to encounter its basic form frequently. Moving every instance to uncommon can make the set’s supposed centerpiece feel incidental. The better solution is often to keep common executions consistent while moving exceptions, extra decisions, and new modes upward.
Rosewater’s broader rarity guidance supports that approach: common can carry a new mechanic when its cards teach that mechanic consistently, while comprehension and board complexity generally push more demanding executions toward higher rarities.
| Rarity role | Appropriate execution | What to avoid |
|---|---|---|
| Common | Repeat the mechanic’s standard action with familiar card effects | New token abilities, exceptions, or alternate procedures on every card |
| Uncommon | Connect the mechanic to an archetype or add one meaningful decision | Making players relearn the mechanic for each draft signpost |
| Rare and mythic rare | Explore unusual rewards, additional abilities, or build-around interactions | Using rarity as permission for text that remains ambiguous or untrackable |
For a custom mechanic built around a persistent token, the common cards might always create or advance that object in the same way. An uncommon could reward reaching a particular state. A rare could change how the object is used. The player first learns one dependable sentence; later cards elaborate on it instead of contradicting it.
Rosewater’s mechanic-layering guidance recommends starting with either the most complicated mechanic or the mechanic that most strongly embodies the set, then building around its needs for colors, slots, card types, rarities, and gameplay roles. That is a better process than designing five mechanics independently and attempting to negotiate peace between them at the end.
Suppose a custom set’s focal mechanic creates a persistent object with counters and activated abilities. Its supporting mechanics should probably not introduce two more bespoke counter types, several double-faced cards, and a graveyard state that must be checked during combat. Even if each idea is appealing, the result makes every board state compete for attention.
Simplification does not mean making the rest of the set dull. Supporting mechanics can still create depth through familiar components: creature types, combat incentives, graveyard use with visible thresholds, conventional tokens, or modal effects with clean choices. The goal is to let the centerpiece remain the set’s dominant new lesson.
This should also influence visual design. If the central mechanic depends on a special token, that token must be easy to identify and read. Its name, type line, loyalty value, and abilities should survive at final card size. A beautiful full-art treatment is counterproductive if it obscures the object players must consult repeatedly. Designers preparing a similar component can use a custom Magic token workflow to plan information hierarchy before polishing the illustration.
A mechanic can be numerically balanced and still exhaust the table. Testing therefore needs to examine how much attention the centerpiece consumes. A custom-set draft process should record usability failures alongside wins, losses, and pick orders; the custom-set draft testing guide provides a broader framework for structuring those sessions.
For a focal mechanic with a persistent token or counter system, ask testers to report:
Do not solve every problem by adding reminder text. Reminder text can reduce comprehension friction, but it also occupies physical space and cannot rescue a sprawling procedure. Sometimes the correct revision is to remove an exception, reduce the number of token abilities, or let one card refer to an existing rule rather than invent another subsystem.
Run an especially plain test version before commissioning elaborate visuals. Use a clearly labeled token, ordinary counters, and readable text. If players cannot follow the mechanic in that form, premium framing will not fix it. If the design survives repeated revisions and is worth producing physically, proof the final files at actual size before moving to a print-on-demand card service.
The strongest conclusion from Empower Jace is not “planeswalker tokens are worth the complexity.” That judgment depends on the set using them. The transferable lesson is that a demanding mechanic needs a specific, central assignment.
Choose the mechanic that best embodies the set, define what it must accomplish, and list the resources it consumes: card slots, reminder text, board space, token components, counters, rarity, and player attention. Then simplify the surrounding mechanics deliberately. A set with one demanding focal point can teach players where to look. A set with four competing focal points has no focal point at all.
The next revision question is therefore simple: if your most complicated mechanic vanished, would the set lose its character, its defining play pattern, and its clearest visual symbol? If the answer is no, the mechanic has not earned its burden. If the answer is yes, protect it by making everything around it easier to learn.
