Push after the loop is stable
Go deeper when bucket fills, drains, and token gains still feel efficient. A slow loop usually means the next upgrade matters more than the next depth.
Drain the Lake Depths
Use this page for depth timing, phone-progress planning, and upgrade checks before you chase a deeper run.
Depth logic
Do not push deeper with a weak loop
The standard page template turns depth intent into practical decisions: when to push, when to upgrade, and what claims still need evidence.
Use phone progress as the objective
The public objective points players toward finding the phone. Depth advice should help that goal without inventing exact hidden thresholds.
Hold exact tables
Exact depth names, badge requirements, and threshold tables need source-backed gameplay evidence before they become publishable.
Run planner
Depth decision table
Use the table before each deeper attempt, especially after updates or when code claims are circulating.
Runs are fastPush one deeper stepUse momentum while the loop still pays back quickly.
Runs feel slowUpgrade bucket or token gainA weak loop makes the next depth less useful.
Phone route is unclearCheck guides and sourcesAvoid copied walkthrough claims until they are tested.
Update just landedRe-check updatesDepth pacing can change after Roblox-side updates.
Upgrade priorities
Compare depth pushing against bucket capacity and token gain.
GuideBeginner route
Reset to the first-session guide if a depth push starts wasting time.
FreshnessUpdate checks
Check update notes when depth behavior or rewards appear to change.