Upgrade when a measured improvement solves the repeated problem that threatens your run. 🍂 Clean all the leaves! officially supports tool upgrades, but public information does not reveal costs, level caps, formulas, refunds, or the best order. The useful decision is not “always buy the next level.” It is “buy when this step reduces enough passes, travel, or timer pressure to help the next area.”
Diagnose the bottleneck before spending
Watch one full clearing zone. If you cross the same open ground several times, the tool may lack effective coverage or power. If most time disappears around props and corners, the route or control matters more. If you travel between isolated misses, zoning is the problem. If a new section is much larger, saving for a stronger improvement may beat another small early step.
Write the bottleneck in one sentence. “The current tool needs three lanes over the same strip” can be tested. “The upgrade looks better” cannot. This sentence becomes the success condition for the purchase.
Run a before-and-after test
Choose a bounded patch near a landmark and clear it with the same starting position and lane pattern. Record the number of passes, rough visible time, and whether edge cleanup remains. Buy one upgrade, then repeat on comparable ground. If the game cannot restore the exact patch, use the same kind of geometry and keep the comparison cautious.
An upgrade earns priority when it produces a clear practical change. A tiny numerical increase may still matter if it removes an entire pass across every large zone. A dramatic effect may be poor value if it creates more turning or leaves edge work untouched.
Read cost as opportunity cost
The displayed price is only one part of the decision. Spending now can delay a later tool, another upgrade path, or a purchase needed after an area unlock. Keep a reserve when the current frontier is close to changing. The exact amount depends on live prices, so use the next visible offer rather than a fixed number from a guide.
If the interface shows a preview, compare it with the result. Do not assume every level scales by the same amount. Record each cost separately and avoid claiming a total path until all displayed levels have been seen in the same version.
Choose upgrades by run phase
Early upgrades should improve consistency. You need enough performance to clear the starting ground without destroying the resource balance. Mid-run upgrades should answer the geometry of newly opened areas and reduce bulk workload. Late upgrades should be judged against the actual remaining job: a broad improvement can be unnecessary when only precise cleanup and collectibles remain.
Team play changes the tradeoff. A bulk specialist may benefit from a coverage upgrade while an edge specialist keeps a controllable setup. Public sources do not establish shared purchases, so each player should read their own tool and resource state before the team plans specialization.
Avoid the max-everything trap
Public information does not say whether upgrades can be refunded or whether early tools remain relevant. Do not push every available level merely because you can. Stop when the current bottleneck has moved elsewhere. If the upgraded tool now clears bulk lanes well but you still lose time to navigation, more power is not the immediate answer.
Likewise, do not hoard forever. Resources that never improve the route provide no timer value. A measured upgrade that consistently saves a pass across every remaining area can repay itself through progress even when a later option exists.
Recover from a poor purchase
First confirm that the upgrade actually applied and that you are testing the right tool. Then redesign the route around its strongest observed job. Use broad effects on open lanes, controlled movement at edges, and teammates to cover weaknesses. If switching is supported, reserve the old or alternate option for the cleanup phase.
If a refund or resale control appears, read the live warning before using it. Public sources do not confirm either feature. Do not delete a save or reset progress based on an assumed recovery path. A suboptimal upgrade is often less costly than abandoning a well-mapped run.
Track patch-sensitive values
Record the UTC date, displayed tool name, level, price, and result. If an update occurs, recheck the same bounded patch before declaring a nerf or buff. Server age, a different area, or a different route can explain apparent change. The Updates hub records official dates without assigning unsupported patch details.
Keep official and observed facts separate. “Tools can be upgraded to go faster” is official. “This level costs a specific amount and clears a particular width” needs a current interface or reproducible run. One detailed observation can be useful as Community reported; repeated agreement is stronger.
Upgrade decision checklist
Confirm the current bottleneck, the exact displayed price, the next visible opportunity, and the patch you will use for comparison. Preserve a reserve if the map frontier is about to open. Buy one change. Repeat the test. Keep the upgrade when it solves the named problem; stop spending when the bottleneck moves to navigation, edges, collectibles, or another area.
Use Tool Index for the identity record and Tool Progression for the broader order. If the run is stuck at a boundary rather than on clear speed, move to Areas instead of purchasing blindly.
Evidence status, August 14, 2026: The upgrade system is official. Every exact cost, cap, formula, refund rule, effect, and optimal order needs current in-game testing.