Build quality
Build stability: test the floor, not only the ceiling
Judge a build by first-cycle output, bad-draw recovery, boss coverage, and patch sensitivityânot by its best screenshot.
v0.107.1 · 2026-07-13
â Decision Guides
1
Four reliability checks
- First cycle: can the deck block and deal damage before every Power or combo piece is found?
- Bad draw: what happens when the engine and its enabler are separated by one shuffle?
- Boss coverage: can the same deck handle Artifact, card-tax, multi-enemy, and phase-change fights?
- Resource pressure: does the plan still work after a forced rest, weak shop, or missing upgrade?
2
Use a stability scorecard
- Reliable: the deck has two independent ways to stabilize and a clear damage plan.
- Conditional: powerful after one specific card, relic, or upgrade; route toward the missing piece but stop adding speculative payoffs.
- Fragile: multiple setup cards, one defensive answer, and no recovery when the first cycle misses.
3
Patch sensitivity
- Mechanic-driven builds are usually more stable across patches than builds depending on one overtuned number.
- When a Beta changes a key card, keep the main-branch plan and Beta plan labeled separately.
- Re-evaluate recommendations when card costs, token effects, enemy breakpoints, or action order changes.