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.
Use this page for depth timing, phone-progress planning, and upgrade checks before you chase a deeper run.
The standard page template turns depth intent into practical decisions: when to push, when to upgrade, and what claims still need evidence.
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.
The public objective points players toward finding the phone. Depth advice should help that goal without inventing exact hidden thresholds.
Exact hidden thresholds and route tables still need source-backed gameplay evidence before they become publishable, even though official badge names are now verified.
Use the table before each deeper attempt, especially after updates or when code claims are circulating.
The official Roblox badge API confirms these milestone names. They are useful checkpoint labels, but they are not enough to publish exact layer formulas, route maps, or hidden requirements.
Current badge demand is rising across YouTube and guide sites, so this page now publishes the expanded public badge checklist from the official Roblox badge API. The newly visible Lost Trident, Power Surge, Master Plumber, and Deposit Mogul badges are safe to name here, but not to pad with copied ending walkthroughs or hidden reward math.
Compare depth pushing against bucket capacity and token gain.
GuideReset to the first-session guide if a depth push starts wasting time.
FreshnessCheck update notes when depth behavior or rewards appear to change.