Experimental Branch and Reporting Bugs

What is the experimental branch?

The launch announcement describes a Steam branch that receives builds more frequently, including early fixes, updates and potentially new features. It is available to owners, but the developer warns that the experience may not always be smooth. It is not an additional paid edition, a promise of finished future content or a guarantee that a particular reported bug is already solved there.

Should you switch to it?

Choose based on whether you want to help test less-settled builds. If you primarily want a consistent shared session, first compare the branch and version with your friends. Read the current announcement before changing, and do not assume save compatibility between all future builds. We have not verified a universal rollback or save-recovery method for this release.

Where should technical bugs be reported?

The developer says the in-game bug-reporting tool is the route that guarantees the report reaches the team. Use Steam or the official Discord for broader feedback, while retaining technical details in the actual bug report. Record the build, steps leading to the issue, location and visible result. Avoid including passwords, account tokens or unrelated personal information.

How do experimental fixes become normal updates?

The developer says stable work from the experimental branch can be promoted to the default branch, accompanied by official patch notes. Follow those notes rather than assuming a frequently updated test branch is already the production release. Once a fix is published, record the new version when updating a guide so older workarounds do not remain presented as current instructions.

Related guides

• Co-op Multiplayer: Player Limit and Shared Bases
• Early Access Roadmap: Launch Content and Scout
• Platforms, Controllers and Supported Languages