What the system does
Official Hotfix 1 notes refer to an “unlock orbs” area and a softlock that could occur when returning there with Omni-dash. That confirms orbs are part of progression and that the area interacted with movement state. The reviewed official material does not define a Refresh Orb formula, refresh interval, value, route requirement, or reward effect.
For that reason, this guide treats Refresh Orbs as a controlled route-observation problem. It does not prescribe a collection order or claim that a specific movement sequence is optimal.
When it becomes relevant
Use this method when the current game explicitly introduces orbs, when an orb-related objective blocks progression, or when you want to compare two reachable route segments. If the system is not yet visible, continue the on-screen progression instead of searching rooms based on an unverified map.
Before the first test, record the game version, course, movement toggle, visible abilities, start point, stop point, and any displayed orb state. A screenshot of the setup is more useful than a remembered route description.
Decision checklist
- Choose one short, repeatable segment that includes only orbs already visible to your current save.
- Define an exact start and finish. Begin from rest and stop the timer at the same visible event.
- Keep the movement state fixed. Hotfix 2’s Omni-dash toggle changes movement tradeoffs, so two states are not directly comparable unless that is the factor under test.
- Record the order in which you touch visible orbs, the elapsed time, and any displayed reward or state change.
- Repeat until you have at least several clean observations. Mark falls, pauses, or missed inputs rather than averaging them silently.
- Change one route segment or movement state and repeat.
- Compare only player-observed reward and time in the route income calculator.
If the obstacle is an upgrade dependency rather than route execution, return to the upgrade-tree guide.
Common mistakes
- Assigning a numerical multiplier to an orb because a resource changed at the same time.
- Comparing routes with different movement unlocks, starting resources, or stopping conditions.
- Treating the old Omni-dash softlock as proof that the current build still has it; Hotfix 1 says it was fixed.
- Following a community path without confirming that the same orbs are visible in the current version.
- Mixing route testing with several upgrade purchases.
- Reporting a single fast attempt as sustainable farming performance.
Use the Power farming guide when the goal becomes long-run income rather than orb sequence testing.
What still needs verification
The meaning of “Refresh Orbs,” their trigger, persistence, respawn behavior, numerical effect, movement requirements, and optimal sequence remain Needs verification. The current name may also be a player search phrase rather than the exact in-game label; the game UI should take priority.
Do not spend scarce resources or reset progression based on an assumed orb rule. A publishable mechanic needs a controlled before-and-after capture in the current full release, including the displayed state and version.
Sources and verification status
Officially confirmed: Hotfix 1 mentions the unlock-orbs area and states that an Omni-dash return softlock was fixed. Officially confirmed: Hotfix 2 changed the available Omni-dash movement choice.
Needs verification: all orb values, timing, route logic, and optimization claims. The page supplies a measurement protocol around that uncertainty rather than converting community observations into rules.