Testing Framework

Match results will not tell you whether the deck or the pilot is the problem. These fields will, and three of them are specific to this engine.

The three that matter most

• Empowers still banked at the end of the game. A high number in a loss means you built an engine the game was never long enough to use.
• Largest trash size and Rhasa’s cost at that point. This tells you whether the burning was actually paying for anything.
• The action cycle when the Legend first produced value. If that number is consistently late, the list is too slow for the field.

Match context

Opposing Legend and Chosen Champion, play or draw, the battlefield each player selected, and whether it was a pre-board or post-board game.

Opening hand

The structure, using the categories in §6, and whether it held a two-Energy body. Given that just under half of all openers do not, this field will tell you quickly whether your mulligan rule is right.

Engine and conversion

Cards played from outside the hand, how many Assault 2 activations actually changed a combat, and how many were spent on combats already decided.

Resources

Turns blocked by Power rather than Energy, reactions given up by sequencing, whether a Seal of Discord was left untapped, and whether the board was too concentrated on one battlefield.

Sideboarding

Outside-hand enabler count after boarding, dead sideboard cards drawn, and whether any Order card was stranded by Power.

Loss classification

One primary cause per loss: pilot error, sequencing, role assignment, sideboard weakness, main-deck construction, matchup structure, or variance. Role assignment deserves its own category here because this deck invites the wrong one.