Reroll Logic
A reroll is not valuable by itself. It is valuable when it changes a bottleneck: movement speed, survivability, burst damage, boss consistency, farming comfort, or resource efficiency. Before spending Clan, Trait, or Race Rerolls, write down which bottleneck you are solving.
If you cannot name the bottleneck, keep the reroll. Legacy Piece codes are generous now, but code generosity often slows after launch waves. Spending every reroll on day one can leave the account weaker when an update makes a specific build path more important.
Rerolls are powerful because they can change the shape of an account, but that also makes them easy to waste. Before pressing a reroll button, decide whether you are trying to improve farming speed, boss survival, burst damage, movement comfort, or long-session consistency.
A usable result is not always a perfect result. If the current build clears the next level band and does not block boss practice, keep it until a stronger reason appears. Burning every Clan, Trait, or Race Reroll for a theoretical upgrade can leave the account weaker when a real update arrives.
| Reroll type | Use it when |
|---|---|
| Clan Reroll | Your route needs a stronger identity or passive direction. |
| Trait Reroll | Your current trait is blocking boss consistency, damage, or farming comfort. |
| Race Reroll | Movement, passive utility, or route comfort matters more than cosmetic preference. |
Build Checklist
Evaluate every build choice against three questions: does it shorten the next grind, does it improve repeated boss attempts, and does it preserve enough resources for the next update? A choice that only looks good on a short clip may be weak if it burns all rerolls without fixing the actual route.
Use Shards and Chests to strengthen the account around the route you are already following. Use Boss Tickets when you can practice. Use rerolls when a bad passive is slowing real progress.
A build checklist should be short enough to use while playing. First ask whether the build shortens the next grind. Then ask whether it makes repeated boss attempts more stable. Finally ask whether spending the reward now leaves enough resources for the next patch or code wave.
If the answer is unclear, run one more normal session before spending. A route that fails repeatedly gives better information than a guess made in the lobby. Use the failure report: damage problem, movement problem, survival problem, or reward-access problem.
Reroll Discipline
Treat every reroll as a question with a cost. Clan Rerolls should answer identity or passive-direction problems. Trait Rerolls should answer performance problems such as damage, survivability, or consistency. Race Rerolls should answer comfort problems such as movement, passive utility, or long-session flow. If the question is vague, the reroll is premature.
A player does not need a perfect build to progress. A stable build that clears the current band and lets you practice bosses is often better than chasing an ideal result with no remaining resources. The right time to reroll is after a failed route identifies the weak point, not after a video makes a different result look exciting.
Before leaving Reroll Discipline, choose one concrete next action tied to deciding whether clan, trait, and race rerolls solve a real build problem or should be saved for a later route. For Reroll Discipline, that action can be to spend, save, test, verify, or move to another page, but it should not be vague. A wiki page is useful only when it changes the next choice inside the game.
If the answer to "which bottleneck will this reroll fix: damage, movement, survival, boss consistency, or farming comfort" is weak, default to saving the resource and use the reroll table, reward priority notes, and the progression page. For Reroll Discipline, that habit protects rare rewards while still letting the account move forward with safer currency, normal grinding, and practice sessions.
How to Use Legacy Piece Abilities and Builds
Use Abilities & Builds before touching Clan, Trait, or Race Rerolls. The page is designed to slow down bad reroll habits by forcing a simple question: what problem will this reroll fix?
If the current build clears your level band, keep it unless a boss or grind route proves it is blocking progress. A usable result with saved resources is often stronger than a slightly better result with no rerolls left.
After a failed route, classify the failure before spending. Damage, movement, survival, and consistency point to different fixes. A reroll without a failure pattern is just gambling with a limited launch reward.
Final check for Legacy Piece Abilities and Builds: which bottleneck will this reroll fix: damage, movement, survival, boss consistency, or farming comfort. For Legacy Piece Abilities and Builds, if that question cannot be answered in one sentence, the account probably needs another normal session before spending anything rare.
When the session goal changes, change pages instead of forcing Legacy Piece Abilities and Builds to answer everything. ability coverage should stay honest about public source limits while still giving players a concrete build-spending method. For Legacy Piece Abilities and Builds, that keeps this page useful for its real job and keeps the route from turning into a generic checklist.