Systems pages answer the questions that sit outside a single contract: which version is this save using, what does Steam Workshop support, how do Map Editor and Mod Manager fit together, and which settings make the interface or performance easier to read? Quasimorph’s 1.0 release added or changed several of these systems, so a reliable guide must separate official release facts from community configuration advice.
Version boundary
Record base game, branch, public version, and date before using a save or patch guide.
Workshop tools
Distinguish subscribing, enabling, load order, map packs, and authoring from ordinary play.
Readable play
Use current controls, FPS, shader, and interface settings to remove a known obstacle, then retest.
Treat the version as a game fact
Write the date, public version, branch, and platform at the top of a troubleshooting note. The official news page records Quasimorph leaving Early Access at 1.0 on 2026-07-31, a 1.0.561 hotfix on 2026-08-01, another 1.0.562 hotfix on 2026-08-04, and 1.0.1 quality-of-life and balance changes on 2026-08-07. A guide from before those posts may still explain a concept while showing the wrong menu, value, or save expectation.
The same discipline applies to beta or unstable branches. Do not move a console, workshop, or save recommendation from one branch to another without a compatibility note. If a problem disappears after returning to the public branch, report the branch difference rather than declaring a universal fix.
Save and branch safety
The 1.0 launch announcement explicitly says saves from the default branch were not compatible with version 1.0, while Unstable Beta saves were compatible. This is a release-specific warning, not proof that every future patch will invalidate saves. Before updating or changing branch, back up what Steam and the game currently expose, note the old branch, and confirm whether the new version can read it.
Do not use a save-compatibility article as a reason to delete a save. First identify the exact AppID, branch, version, and error or behavior. Steam Cloud can synchronize the wrong state if it is used without understanding the current copy, so pause and verify before replacing local progress. When asking for help, include the public version and whether mods were active.
Workshop, Map Editor, and Mod Manager
The Steam store lists Steam Workshop as a feature, and the 1.0 notes describe a Map Editor for Custom Map Packs and an in-game Mod Manager that can set load order, enable or disable mods, and display map-pack collisions. These are different layers. Subscribing obtains a Workshop item; enabling determines whether the game loads it; ordering can change interactions; authoring a map pack is a separate workflow.
Start with one known-compatible item. Confirm that the game launches, the item appears in the manager, and the expected map or content loads. Add the next item only after the first is stable. If a collision or load-order warning appears, preserve the text and test one change at a time. Do not copy a developer-console command into a normal player guide without a clear mod or troubleshooting scope.
Controls and performance settings
Use the current Options screen for controls, FPS limit, V-Sync, window mode, and shader settings. The 1.0 notes added an FPS limit setting and an option to disable the black hole shader for players with performance problems in Pleroma. The 1.0.1 notes also mention interface and readability improvements. These facts support a troubleshooting path, not a guarantee that one setting fixes every device.
When a problem appears, change one setting, restart if the game requests it, and reproduce the same scene. Record device, resolution, display mode, frame limit, and whether mods are enabled. A performance report without those details cannot distinguish an asset issue, a shader cost, a mod conflict, or a branch-specific bug.
Keep ordinary play and content creation in separate checklists. A player who only wants to subscribe to a map pack needs the Workshop item, the manager state, and a compatibility check. A creator needs a reproducible authoring workflow, a manifest, a thumbnail, and a way to update the item. Mixing the two routes can lead a new player to run a developer command or mistake a creator’s setup note for a required game setting. The safest systems page explains what the player should see and where a more specialized workflow begins.
This separation also makes debugging safer. Start with the unmodified base game and a known save when possible. Confirm that the issue still occurs, then add one Workshop item or setting and repeat the same action. If the result changes, the last variable is a lead, not a proof; test it again and preserve the version details. A short reproducible report saves more time than a long list of guesses copied from different branches.
Player setup
Use the Workshop subscription and in-game manager, then test a single item before building a collection.
Creator setup
Use the official/community mod workflow and keep authoring instructions separate from everyday mod activation.
Troubleshooting
Record version, branch, platform, settings, mods, and reproduction steps before changing more variables.
Keep a systems checklist
Before following a systems guide, confirm base game versus DLC, AppID 2059170, public branch, version, platform, active mods, and save backup status. After changing one variable, record the result. This prevents advice for the Supporter Pack, prologue, or an old beta from silently becoming a base-game rule.
Open Save Compatibility for the release warning and branch checklist. Then use Updates to see which official change may explain a menu or behavior difference.
Recommended articles
Choose the guide that matches what you want to do next.
All Systems articles
1 focused articles with steps, checks, and current caveats.