Rune Dice updates
Rune Dice Update Tracker
This page turns patch notes into route decisions: what to retest, which guide to open, and when a class, relic, rune, or boss plan needs to change.
Quick Answer
After a Rune Dice patch, do not change class or route just because the version changed. First ask whether the patch touched merge reliability, rune timing, relic support, class safety, boss progression, or Hard Mode routing. Retest the affected job before rewriting the whole build.
Patch Impact Guides
What to Recheck After a Patch
Patch Triage Route
- Keep one stable test route. Do not test a patch with a brand-new class and three new support choices at once.
- Retest the changed job. If merge behavior changed, retest merge chains. If relics changed, retest support jobs.
- Compare board state, not only damage. A route can feel weaker because the board is less stable, not because the class is bad.
- Update one guide path at a time. Boss prep, merge planning, and class starts should not all change from one vague patch note.
When an Update Should Change Your Route
A patch should change your route when it touches the system that was carrying your run. If your route depended on reliable merge chains, any dice behavior fix matters immediately. If your route depended on a support relic, retest that support before judging the class. If the patch only improves readability or save behavior, the build may not need a route change at all.
The safest post-patch habit is boring: repeat a known route, watch where the board starts failing, then change the guide path that solves that failure.