Read the date
Reviewed 2 November: 1.0 remains scheduled for 4 November, not a claimed tested release.
Cobalt Games/VOID/BREAKER/Field guide
04 / LAUNCH WATCH
Demo Progress & 1.0 Launch Guide
The official announcement promises demo progress transfer and sets a 4 November launch date. Keep those confirmed statements separate from unknown migration details, future balance changes and screenshots whose capture build is unspecified.
EARLY ACCESS SOURCE REVIEW1.0 scheduled / 04 NOV 2026
THE DECISION IN ONE LINE
Progress transfer is promised. An exact manual file-copy procedure is not documented here.
Record the starting point
Note the edition, displayed version and progression you expect to find.
Use published instructions
A transfer statement does not justify guessing a save path or overwriting unfamiliar files.
REASSESS WHEN
Stop an improvised migration when you cannot identify the file or instruction it would replace.
FIELD NOTE 01
Read the date as an announcement, not an installed build
This guide was reviewed on 2 November 2026. The publisher has announced 1.0 for 4 November, and the Steam listing still describes the game as leaving Early Access on that date. We therefore label 1.0 as upcoming. A release announcement establishes the plan; it is not evidence that we played the final build or checked every changed item and encounter.
When release arrives, compare the developer’s actual launch notes with the version shown in your game before reusing a precise Early Access claim.
FIELD NOTE 02
What the demo transfer statement actually confirms
The official demo listing and the publisher’s launch announcement both say demo progress transfers to the full game. That is useful if you want to learn the movement and shooting before deciding whether to continue. It does not, by itself, document a manual folder-copy procedure, every operating-system scenario or the behavior of old experimental branches.
Use the official Steam listings to identify the demo and full game. We do not provide a guessed save path, a registry edit or a file deletion routine disguised as a required migration step.
FIELD NOTE 03
Keep the transition simple and observable
Before changing editions or builds, note which version and Steam account you are using and what progression you expect to see. This is a practical troubleshooting record, not a claim that an account setting controls transfer. Avoid mixing several changes at once. If something appears absent afterward, a clear description of the starting state is more useful to support than a sequence of undocumented fixes.
Read any new in-game or developer instruction first. If none exists, do not interpret silence as permission to overwrite unfamiliar files or repeatedly start a replacement save.
FIELD NOTE 04
Keep ownership policy separate from game mechanics
The October announcement says people who bought the game during Early Access will receive the Supporter’s Pack at the 1.0 launch. That is an ownership policy, not an extra combat mechanic or evidence that a gameplay feature is restricted to a soundtrack purchase. Review the live Steam listing for the package details rather than infer them from a gameplay image.
We would choose whether to continue based on the game you can actually evaluate. No recommendation here depends on an invented launch discount, future price movement or a claim about guaranteed store visibility.
FIELD NOTE 05
Audit old advice before treating it as a launch build
Early Access changed meaningful systems. Wallrunning arrived in Hard Reset; later releases altered modules and combat readability. The store’s older description of three playable biomes should not override subsequent released updates that added later zones. Use dates to understand what an article describes rather than combine every historical statement into one supposedly current rule set.
The same applies to official gallery screenshots. They are authentic publisher images, but their capture build is not specified. A visible number or interface panel is not automatically a verified 1.0 value.
FIELD NOTE 06
Make the first continued run a verification pass
On the version you actually have, start by reading the current controls, tutorial prompts and familiar module cards. Choose one understandable combat objective instead of immediately reconstructing an elaborate old build. Check whether the expected progression is present, then investigate any difference with a precise description of what you saw. This preserves a useful distinction between an observed change and a rumor about the patch.
Use our movement guide for the encounter plan and the weapon lab for a small equipment question. Neither requires an account, an uploaded save or access to your installed game.
BEFORE THE NEXT ATTEMPT
Your field checklist
- Distinguish the 4 November plan from the installed version.
- Use the official demo and full-game listings.
- Record the starting version and expected progression.
- Follow published migration instructions if the developer adds them.
- Keep ownership bonuses separate from combat-system claims.
- Review current cards and controls before rebuilding an older setup.
QUICK ANSWERS
Keep the limits clear.
Where should I manually copy my demo save?
No exact manual copy procedure was established by the reviewed primary sources. The transfer promise is confirmed, but we will not invent a path or recommend overwriting a save. Follow the current official instructions if a specific transition requires them.
Have you tested the 1.0 release?
No. This page is explicitly reviewed before the scheduled release. Its purpose is to separate confirmed announcements from assumptions and help readers check their own current game without presenting a source review as a playthrough.
REVIEWED 02 NOV 2026
Sources for this briefing
- Playstack — 1.0 announcement, 1 October
1.0 scheduled for 4 November; demo progress transfer and Early Access Supporter’s Pack policy. Announcement, not a released 1.0 build.
Reviewed 2 November 2026 - Official VOID/BREAKER demo
Official demo listing and progress-transfer statement. No unverified save-file procedure is supplied.
Reviewed 2 November 2026 - Stubby Games — Hard Reset, 17 February
Released Early Access wallrunning, shielded enemies, progression and schematic-readability changes. Later updates can supersede details.
Reviewed 2 November 2026