Rune Dice updates
Rune Dice Update Tracker

Patch changes matter when they alter the board state your class depends on: merge lanes, rune timing, relic support, boss progress, or the path into Hard Mode.
Follow the Change to the Board
Keep the class and route that were working, then look at the first board state affected by the patch. A merge fix calls for cleaner landing lanes; a relic change calls for a new support choice; a boss or Hard Mode change may move preparation earlier without changing the rest of the build.

Patch Impact Guides
Where Each Patch Lands
Keep the Working Parts Still
- Repeat a familiar route. A new class and three new support choices hide the effect of the patch.
- Change the affected job. Merge behavior belongs to landing and follow-up lanes; relic behavior belongs to support.
- Compare board state, not only damage. A route may feel weaker because it leaves fewer safe merges.
- Rebuild only from the first broken layer. Boss prep, merge planning, and class identity rarely all need to change together.
When the Route Actually Needs to Move
A route changes when the patch touches the system carrying the run. Reliable merge chains make dice-behavior fixes important; support-heavy classes care more about relic and rune changes. Readability or save fixes may leave every combat decision intact.
Repeat a known route, find the first board state that now fails, and repair that layer before changing the class.