2026-07-07
Refresh after Roblox description changes, code claims, skill tree changes, or new depth evidence.
Use this page as a practical priority list. It ranks visible public mechanics first and holds exact formulas until stronger evidence exists.
Refresh after Roblox description changes, code claims, skill tree changes, or new depth evidence.
Prioritize upgrades that improve each drain cycle before chasing deeper progress.
Treat official Roblox and creator-owned sources as strongest. Videos and community reports help with trends and use cases.
Compare the actions already visible in the game loop before relying on unverified depth tables or hidden formulas.
Core loop
More water per trip improves every drain cycle before deeper progress starts to slow down.
Planning note: Use this before pushing depth.
Source check: Roblox description confirms fill bucket and drain loop.
Progression
Token upgrades compound across repeated runs and are safer than rushing one narrow path.
Planning note: Spend where the benefit repeats.
Source check: Roblox description confirms draining for tokens.
Goal progress
Going deeper matters, but it should follow stable bucket and token income instead of replacing it.
Planning note: Push after the current loop feels fast.
Source check: Roblox description confirms go deeper and find your phone.
Check code status, improve bucket capacity, strengthen token gain, and push depth only when the loop is stable.
Use visible token returns and bucket speed before committing to a depth push.
Exact skill tree formulas and depth thresholds stay labelled until details are confirmed.
Drain the Lake priorities should start with bucket capacity, token gain, skill tree pacing, and depth timing. Exact formulas and late-depth tables require more evidence.
Use guides for bucket timing, code status, and first-session upgrade choices.
WikiUse wiki pages for bucket loop, tokens, skill tree, depths, updates, and source notes.
SourcesUse source notes when creator videos, wiki pages, or community reports disagree.