Chained Together checkpoints are a Beginner Mode feature. The current Steam description specifically pairs Beginner with checkpoints, while Normal is the standard punishing climb and Lava adds rising flames. Continuing an earlier session is a separate question: a saved session, a checkpoint, and your highest position should not be treated as interchangeable recovery options.
For multiplayer, the most useful documented recovery workflow comes from a June 2024 player report: recreate the lobby with the same host, difficulty, and player count, then look for Load previous save after entering. That is historical community experience, with failure reports in the same thread. Test a short session before relying on it for an evening's progress; this site has not tested the current game build.
01
Choose the mode before you start climbing
If your priority is learning jumps while reducing the cost of a fall, choose Beginner. The current official store description confirms its checkpoint support. Do not start Normal assuming you can later recover a failed jump through Beginner's checkpoint system.
Normal and Lava serve different goals. The store currently says leaderboard scores and achievements are valid only in those two modes, so a practice session and a reward attempt deserve separate plans. Compare the options in the game modes guide before creating the lobby, particularly when your group disagrees about difficulty.
02
Understand the three kinds of progress
A checkpoint is a recovery milestone within the climb. A saved session is the state the game can potentially offer when you return after leaving. A highest-point option, when your selected mode exposes one, describes another recovery target. A menu containing one of these labels does not establish that all three preserve the same position.
This distinction explains an otherwise confusing situation: your group can enter a new lobby at the beginning even though an earlier recovery option remains available. It also explains why returning to an older milestone is different from losing every piece of recorded progress. Read the available menu choices before deciding that the save has disappeared.
03
Run a short recovery test first
Use the following as an editorial preparation routine, rather than a promise about the game's save implementation. It gives your group a chance to discover a problem while the lost time is small.
- Agree who will host, select the intended difficulty, and note the number of players.
- Start a short climb together and stop on a stable platform.
- Photograph or note the current height, mode, host, and any recovery labels visible in the menu.
- Leave through the game's normal exit interface, reading any save-related prompt carefully.
- Have the same person recreate the lobby and check the available restore choices.
- Confirm the recovered position with everyone before committing to a longer session.
If the result is unclear, investigate immediately. A successful five-minute test gives you useful evidence about your setup, although it cannot guarantee that every later exit, crash, or disconnection will behave identically.
04
The documented multiplayer restore workflow
In the Steam discussion “How to save multiplayer game?”, Dazanofoey initially reported being unable to recover a session. On 20 June 2024, the same player described a method that worked for their group: rebuild the lobby with the same host, difficulty, and number of players, enter it, then press Escape and choose Load previous save.
The player said that this restored the position occupied before leaving. Their explanation of automatic saving was explicitly an inference, however. Treat the post as a concrete historical procedure to compare with your menus, not as developer documentation of exactly when the game writes progress.
If today's interface places the restore choice before launching the lobby, read that choice there. Another participant in the thread described selecting a previous save while creating the host session. The useful principle is to inspect both the lobby setup and the in-session menu instead of repeatedly launching fresh runs.
05
What to do when you appear at the start
First check whether you have actually attempted restoration. Appearing at the opening area was part of Dazanofoey's reported workflow; entering the lobby alone did not restore their earlier location. Check for a previous-save option and compare the displayed mode and group arrangement with your notes.
If the correct option is absent or returns an unexpected position, stop experimenting with your only valuable session. Record what happened before changing host, difficulty, or player count. Those notes make it easier to distinguish an incorrect setup from a recovery problem and give a support report something more specific than “my save is broken.”
06
Where are the checkpoints?
A 23 June 2024 community post by SanCarlo reports three checkpoint heights for the original climb: approximately 576m, 1675m, and 2757m. The post links gameplay-video timestamps as its evidence. These are historical player-reported markers, not measurements verified by this site in the October 2026 build.
Use those numbers as orientation, not a guarantee that reaching the same displayed metre activates a particular recovery state. Look at the game itself and test the available recovery option. The planned November 2026 map is separate upcoming content, so this original-map list should not be assumed to describe it.
07
Why can recovery return an older position?
The original save discussion contains conflicting experiences. Some players reported that the described method worked, while others said they returned to an older checkpoint or lost more progress than expected. One July 2024 reply describes finishing a substantial section and later returning to an earlier flag.
Those reports establish a reason to verify recovery, but they do not identify one universal cause. They do not prove that every current save fails, that only the host ever retains progress, or that changing one particular setting fixes everything. Avoid turning a single forum reply into a rule for all versions and groups.
08
Protect an existing run while troubleshooting
Before starting another long climb, decide whether the previous session matters more than a fresh attempt. Do not deliberately overwrite the only known recoverable state merely to see whether a new lobby behaves differently. If you investigate local save files, preserve an untouched backup first and avoid deleting files based on an untested forum suggestion.
Keep the troubleshooting sequence small: document the current result, check that the group's game versions match, compare the lobby settings, and consult current developer information. A patch can change menus or recovery behaviour. A clean restart is easier to evaluate when you have kept the previous settings and observations.
09
Make a group plan for stopping
Agree on a stopping point before somebody has to leave suddenly. Give the host enough time to read the exit options, and have one player record the group's last stable location. A rushed disconnect is a poor moment to learn how your setup handles continuation.
For an unfamiliar group, explain the recovery test before the first serious climb. Knowing whether this is a Beginner practice run or a Normal achievement attempt prevents avoidable disagreements later. The beginner guide covers the broader preparation, while the local co-op guide helps separate shared-screen setup from online play.
10
Can you depend on saving every exact position?
The sources reviewed here do not support that guarantee. Beginner checkpoints are currently official; the detailed save-and-restore procedures above are dated community reports. A useful approach is to verify a small recovery on your own machine and group, preserve important progress, and check the current menus whenever the game updates.
If you report a failure, include the host, mode, player count, game version, last stable height, exit method, and restore result. That turns a frustrating lost climb into a reproducible description without claiming certainty about an undocumented save system.