Rolling creates options; it does not complete the base. Keep enough blocks, traps, and weapons to cover front, middle, and cleanup before chasing a rare result. Current guides document Luck and Auto Roll systems, faster-roll improvements, and Index-related progression, but the exact Skill names, costs, formulas, and unlock order should be read in the live game.
The safe rolling loop is keep a working set → roll for a missing role → test one replacement → save or revert.
Protect the working set
Lock or preserve at least one contact piece and one contributing weapon before sorting new rolls. Keep a cleanup answer when it has already saved the run. A common item remains valuable until its replacement proves the same role on the same wave.
Do not remove a Wood Block, Wooden Trap, Cross Bow, Basic Cannon, or another owned baseline merely because a rarer animation appears. Those are currently documented names, not guaranteed values. Test the actual live item.
Roll for a missing job
Name the problem before rolling: front durability, group pressure, sustained boss damage, middle coverage, or cleanup. A roll is relevant when its family and behavior can answer that problem. Otherwise keep it for the Index or later testing without displacing a working role.
If enemies travel through empty space, stop rolling and fix layout. If current items cover the path but lack pressure, a stronger or different-role item becomes a reasonable target. This distinction prevents Luck spending from hiding a geometry problem.
Use Auto Roll deliberately
Current guides describe Auto Roll as a Skill that automates repeated dice use. Confirm the current name, cost, unlock, stop controls, and inventory behavior. Turn it on when you can monitor new entries and preserve keep rules; turn it off before a full inventory, resource target, or risky replacement decision.
Auto Roll can accelerate Index discoveries and option flow, but it does not evaluate placement. Review results in batches, identify the role, and test one candidate. Do not let automation remove or overwrite the only working version of a role.
Test Luck separately
Record the live Luck sources and displayed odds before buying an upgrade. Keep the base and target wave unchanged while evaluating acquisition. If the game does not display effective odds, do not derive a formula from a short session.
Current guides mention Skill, Index, friend, shop, and possible boost-related Luck. Treat each as Community reported until visible on your account. Stack nothing blindly: read duration, currency, scope, and whether the modifier affects base odds or only the result process.
Use Rarities & Odds for a clean roll record.
Compare a replacement
Save the old position, match upgrade state as closely as possible, and replace only one item. Run the same wave and record first contribution, first failure, and final outcome. Keep the new item when the target failure moves later without opening an earlier leak.
If the candidate has a different job, test it in the layer that needs that job rather than forcing it into the old slot. A mortar-like group candidate and a focused weapon should not be ranked from one mismatched position.
Rolling mistakes and FAQ
- Rolling while the current base has obvious empty coverage.
- Selling a working common item before the replacement test.
- Treating one rare pull as proof of a Luck formula.
- Leaving Auto Roll unattended without inventory or keep controls.
- Copying third-party odds after an update.
What should I roll for first?
Enough objects to complete contact and damage roles, then the role missing at the first repeated failure.
Is Luck better than item upgrades?
Luck improves future options; item upgrades improve an owned contributor. Choose from the current bottleneck and test them separately.
What does Auto Roll cost?
Check the live Skills panel. Public guides publish numbers, but this page does not freeze update-sensitive costs.
When should I stop rolling?
Stop when the current bank or attention is needed for a tested upgrade, when the working set is at risk, or when new rolls no longer address the missing role.