VOID/BREAKER 1.0 Zone 4 and 5 Softlocks: What to Try and What’s Still Broken

Do not assume the Chaos-mode advice solves the Zone 5 barriers or the Zone 4 crashes. The developer offered it for the hub-loop report.

Developer liv says switching Chaos mode off should allow progress. That establishes developer advice, not an independently tested recovery or a released fix.

The original reporter subsequently says they can start a run from Zone 4 again, while returning to Zone 1 remains unavailable. In a November 6 follow-up, liv explains that the remaining restriction is story-related and tells them to continue onwards. Distinguish a run that will not start from a run that starts but cannot return to an earlier zone; Kingy has not tested either outcome.

An earlier player thread describes unchecking an unnamed option in the Chaos settings. The original poster reports success, while a later player says that checkbox is already unchecked and they remain stuck. That mixed evidence limits the workaround; the unnamed checkbox should not be treated as a verified menu label.

The exact menu path and controller or keyboard inputs are not established by these replies. This page shows the setting and value in text rather than inventing a screenshot or menu location.

Read the developer’s Chaos-mode advice

Read the developer’s story-progression follow-up

Read the earlier mixed player outcomes

1. Confirm the symptom: the game asks you to return to Zone 1, but forfeiting leaves you in the Zone 4 hub.
2. Check whether Chaos mode is enabled. If it is, switch it off, following the developer’s advice.
3. Try starting the run again. If it starts but you still cannot return to Zone 1, the developer tells the original reporter to continue onwards because that remaining restriction is story-related.
4. If a run still will not start with Chaos off, record that different outcome with your build number and hub state for the linked bug report. The story explanation does not establish a recovery for that case.

Before hotfix 1.0.8, three players describe being teleported onto an island and finding red barriers blocking both directions. The developer initially acknowledges the softlock and investigates solutions. The November 6 hotfix subsequently reports a fix for one Zone 5 shortcut teleporter that could softlock a run.

The original poster and another player say save-and-quit did not remove the blockage before that hotfix. Those are historical outcomes, not tests of 1.0.8. The patch notes do not establish recovery of an already blocked run, so reloading is still not a verified rescue procedure. Abandoning a run was one player’s outcome, not a way to preserve it.

Install 1.0.8, then record the blocked exits, teleport location, installed build and whether resuming changes anything if you are still affected. This reporting checklist is Kingy’s editorial advice; recovery of an already trapped run remains unconfirmed.

Read the original Zone 5 developer acknowledgement

Read the later 1.0.8 teleporter fix notice

Before hotfix 1.0.8, several PC players report stuttering followed by a crash in Zone 4 fights. Some say an encounter is complete without its reward chests after resuming; the original poster also reports missing picked-up mods. These are run-progress reports. The thread does not establish deletion of an entire save or all permanent unlocks.

One player says periodically saving and quitting let them continue a run. This is a single player’s observation, not a developer-approved crash fix or a guarantee that rewards will survive.

Hotfix 1.0.8 reports fixes for crashing in some instances in Zones 4 to 6. That limited scope does not establish that every crash is fixed, or that previously missing rewards or mods are restored. Install the hotfix and include your current build when reporting a continuing crash; Kingy has not tested it.

The developer has logged the thread for investigation. If you have crash logs, the developer asks for them at support@playstack.com with the subject “VOID/BREAKER Stutter and Crash Log”. Include your build, PC specifications, encounter and what was missing after resuming. No log-folder path has been verified here.

Read the logged crash report and developer replies

Official notes, summarised; Kingy has not tested the hotfix. The developer says a wider patch for more bugs is coming soon and asks for bug reports on Discord or through its bug report form.

The notes name a Zone 5 shortcut teleporter but not the red barriers by name, and they say nothing about runs that were already blocked before the update. This is a developer-reported fix; Kingy has not validated prevention of new cases or recovery of existing ones.

Read the 1.0.8 patch notes

1. Fixes crashing in some instances in Zones 4 to 6.
2. Fixes one of the Zone 5 shortcut teleporters creating a run softlock.

Checked November 7, 2026: the latest official Steam announcement is the 1.0.8 hotfix (November 6). It names a Zone 5 shortcut teleporter softlock and some Zone 4 to 6 crashes; it does not mention the Zone 4 hub loop. A wider patch is promised but not dated.

Separately, the developer’s November 6 hub-thread follow-up explains that the original reporter’s remaining inability to return to Zone 1 is story-related once runs can start again. That is progression guidance, not a patch fixing every failure to start a run.

A future update should name the affected issue, platform and patch version or release date, link the developer’s fix notice, and state separately whether Kingy or affected players have tested recovery. A fix preventing new softlocks does not automatically establish recovery of an already trapped run.

Until recovery is established, do not delete a save or start over on the assumption that this page guarantees preservation of upgrades or unlocks. The linked reports do not answer that question.

Check official VOID/BREAKER news