Sandustry Workshop compatibility guide

Decide whether the save should be modded

Treat mod installation as a separate factory environment. Workshop entries can add or alter machines, materials, maps, and production chains, while experimental game branches can change the data read by an existing save. Do not use the only copy of a long-running factory as the first compatibility test.

Record the current game version and active Workshop items before changing anything. Copy the save using the location and backup method documented for the current release; this guide does not guess a platform-specific save path that current official references do not document.

• Record the current game build.
• Record every active mod and its version requirement.
• Create a restorable save copy.
• Close the game before changing its Steam branch.

Read the Workshop requirement before subscribing

Use the official Sandustry Steam Workshop and open the individual mod page. Check its description, required dependencies, stated Sandustry version, installation notes, update date, and known incompatibilities before subscribing.

Do not infer compatibility from a similar title or category. A layout, material conversion, or machine that appears in a modded video may not exist in the base game, and two Workshop entries can target different experimental builds even when both are recently updated.

Match the Steam branch to the mod

After subscribing, open Sandustry's Steam Properties and select the experimental branch required by that specific Workshop entry. Wait for Steam to finish updating the game before launching it. Then confirm the game build shown by the installation matches the version named by the mod author.

The official August 29, 2026 announcement described a split between entries for 0.5.2 and 0.5.5, with the mods branch remaining on 0.5.2 for older mods. That is a dated compatibility snapshot, not a permanent branch rule. Recheck the official announcement and mod page whenever Sandustry or the Workshop item updates.

• Subscribe on the official Workshop.
• Select the exact required branch.
• Let Steam complete the update.
• Verify the loaded build before opening the target save.

Test one change in a copied save

Launch a disposable or copied save first and confirm that the mod loads without an error. Inspect its new research, machines, materials, or controls before connecting anything to an existing production line.

Run one small input through the modded feature and verify the expected output, power, heat, and storage behavior. Record the result with the exact game build and mod list. Only move to the main modded factory after the same setup survives a save, exit, reload, and another production cycle.

Diagnose version and load-order problems

When the game fails to load a modded save or a machine disappears, compare the current branch with every subscribed item's stated requirement. A single older entry can keep the collection tied to 0.5.2 while a newer one expects 0.5.5.

Reduce the test to the smallest relevant mod set in the copied environment, then re-enable dependencies and other entries gradually. Do not overwrite the known-good backup during diagnosis. If a Workshop page marks the current combination unsupported, wait for an update or return the test environment to its previously recorded versions.

• Confirm the Sandustry branch.
• Confirm each mod's required version and dependencies.
• Reproduce the issue outside the only main save.
• Restore the known-good copy if serialization or factory state changes.

Keep base-game and modded guide claims separate

Label every modded Blueprint, recipe, resource loop, or factory screenshot with the game build and required Workshop item. A modded conversion should not appear on a base-game resource page unless it is clearly separated and independently reproduced in an unmodded save.

This keeps the Wiki useful after a branch update. Readers can distinguish a core Sandustry mechanic from a Workshop extension, and an outdated mod note can be revised without weakening the verified base-game route.

Use Sandkit only for mod development

Ordinary players install compatible mods through Workshop subscription and branch selection. Sandkit is the official developer API for authors building or maintaining mods, so it is not required merely to use a Workshop entry.

If you are authoring a mod, consult the official Sandkit reference for the current API rather than copying implementation details from a player installation guide. Publish the supported Sandustry version and dependencies with the Workshop item so players can select the correct branch before loading a save.