Shipwreck, Cavern, Mineshaft, Molten, Lost City, Abyss, and the phone ending are official progression labels; treat them as checkpoints, not exact route instructions.
What the checkpoint list can safely tell you
The official badge API provides a reliable progression vocabulary. Public badge records connect Sunken Secrets with Shipwreck, Deep Dive with Cavern, The Mines with Mineshaft, Fire Below with Molten, Ancient Ruins with Lost City, Into the Abyss with Abyss, and Find My Phone with the phone ending. These labels show that the game expects movement through distinct depth milestones. They do not provide exact distances, gates, map coordinates, or time estimates. Use the list to recognize where you are in the overall objective and to organize questions, not as a substitute for the current game’s navigation.
Shipwreck and Cavern: verify the basic loop
Before treating the early checkpoints as a race, make sure filling, draining, token spending, and returning to the route feel repeatable. Shipwreck and Cavern are useful early progress labels because they let you ask whether the loop can support another step. If reaching the next area requires many slow cycles, improve the visible bottleneck first. The badge names do not prove a specific bucket, skill, or token threshold. Follow requirements shown by the current game. Keep a note of which upgrade changed the pace so you can distinguish real progress from simply becoming more familiar with the route.
Mineshaft and Molten: stop and check the build
Mid-route labels such as Mineshaft and Molten are a good point to review your skill tree and token choices. Do not assume the next depth always demands another depth-focused node; a capacity or token improvement may strengthen every future attempt. Look at the current interface and identify whether the stall comes from cycle speed, navigation, survival, or a visible unlock condition. The public badge record confirms the destinations but not the method. If a community walkthrough proposes an exact route, verify it against the current build before making it part of a permanent guide.
Lost City and Abyss: protect repeatability
Later checkpoint labels suggest deeper progression, but they are not permission to invent endgame math. At Lost City or Abyss pressure, compare the time needed for one meaningful advance with the time needed to strengthen the loop. If the advance consumes the entire session without producing a stable new cycle, return to upgrades. Keep token, bucket, and skill-tree decisions tied to visible effects. A public badge can confirm that an area exists while leaving its access and pacing undocumented. Preserve that boundary when sharing advice so another player knows what is official and what came from your own run.
Phone ending versus optional achievements
Find My Phone is directly aligned with the official description’s main objective. The badge inventory also includes alternate endings, exploration, shark encounters, treasure, crafting, and challenge-style goals. Do not combine those into the required phone route. Decide whether your current session is main progression, a challenge, or secret hunting. A route for Hidden Treasure, Frozen Throne, Atlantis-related goals, demolition, or shark badges needs its own current evidence. Keeping optional goals separate prevents a long achievement list from confusing players who only want to complete the core phone objective.
Build a checkpoint log that survives updates
Record the checkpoint label, date, current update title, visible loop bottleneck, last upgrade, and next action. Add a source note when an exact requirement comes from the game rather than memory. If an update changes the badge description or progression interface, mark the old note as historical until replayed. This log is more useful than a fixed depth table because it makes uncertainty visible and shows why you chose to upgrade or continue. It also gives future editors a precise trigger for refreshing the page without turning counter movement or an update timestamp into a gameplay claim.
What changed across observed Roblox snapshots
This is our own dated history of the same public Roblox fields. It shows observed movement, not a prediction or an explanation for why players moved.
Source: QuestSignal immutable release history · newest five observations shown
What this guide does not assume
Checkpoint names and sampled requirements are official badge records. The readiness and logging framework comes from the specialist depth page. Exact layer maps, distances, unlock thresholds, boss or shark behavior, ending routes, hidden locations, and reward math are excluded.
Refresh trigger: Refresh when Roblox changes badge names/descriptions, the depth interface or objective changes, or replayable current-build evidence supports an exact checkpoint requirement or contradicts the current sequence.