Go to main menu → Change → Start New Journey, then have the host manually re-select your last checkpoint. That is the stated recovery procedure for a softlock or a game-breaking bug.
The menu label alone is not the full instruction. After choosing Start New Journey, the host still needs to select the checkpoint where you intend to resume. Coordinate that selection with your partner before continuing.
Follow the menu route
- Let your partner know that you are going to reload.
- Return to the main menu.
- Choose Change.
- Click Start New Journey.
- Have the host manually select the last checkpoint.
- Check the chosen point together before resuming.
The known route assigns checkpoint selection to the host. Do not assume that your partner independently selecting a point will replace that host step. If you need to report a failed recovery, include which checkpoint the host selected and whether the original blockage returned.
Use recovery for a blocked game state
Several confirmed launch issues explicitly direct players to the last checkpoint:
- Crouching while shrinking can leave a player unable to grow back to normal size.
- A held item can disappear if an emote is used while placing that item into a slot.
- Certain elevator problems can block progress after a player exits before the doors lock.
- Becoming stuck in collision on certain Chapter 6 plants should trigger a respawn; if it does not, checkpoint recovery is the stated fallback.
These examples explain when the recovery route is appropriate. They do not mean that every unfinished puzzle is a softlock, or that reloading replaces a required interaction or pickup.
Check what you are trying to recover
Before reloading, briefly compare both players' states. Identify whether you are unable to move, missing an item that visibly disappeared, or unable to continue after a known trigger. That makes it easier to tell whether the retry changed anything.
A checkpoint retry should not be described as an in-place repair. The available instructions do not promise that every action since the selected checkpoint will be retained. Choose the point deliberately and expect to revisit the section you load.
If the blockage repeats, avoid the known trigger where one is identified and record the sequence that reproduced it. For example, the shrinking bug identifies crouching during shrinking; the item-disappearance bug identifies an emote during placement. A repeat with those details is more informative than a report that only says the checkpoint did not work.
This procedure is recovery guidance, not confirmation that an underlying bug has received a permanent patch.