Quick Answer
Sandustry officially supports modding as a product direction. The Steam page lists Steam Workshop as a feature and says dedicated modding tools support visual changes, hand-crafted maps, new buildings, and new processes. That does not automatically validate every community loader, executable, archive, or installation tutorial found elsewhere.
For the safest starting point, use the official Steam product page and its Workshop entry for the Steam version. Read the mod's current compatibility notes and keep an unmodified save for comparison. Third-party loader names, download mirrors, command-line steps, and cross-store compatibility are Pending confirmation unless their current official documentation proves them.
What Official Mod Support Covers
The official Steam and Xbox descriptions use unusually broad language about modding. They describe cosmetic tweaks and custom maps, but also entirely new buildings and processes integrated into production chains. Steam additionally exposes Workshop as a listed product feature, giving players an official discovery and distribution surface on that store.
Official support does not mean every mod is made, reviewed, or supported by Lantto Games. It means the game was built with customization in mind and provides dedicated tools, while individual community items still carry their own quality and compatibility risks. The exact tool package, documentation version, and support policy are Pending confirmation if they are not linked from the current game or official store surfaces.
| Mod category | Confirmed official scope | Main verification question |
|---|---|---|
| Visual tweak | Explicitly mentioned | Does it match the current game build? |
| Hand-crafted map | Explicitly mentioned | Does it require other items or a specific version? |
| New building | Explicitly mentioned | Does it alter saves or production dependencies? |
| New process | Explicitly mentioned | Are inputs, outputs, and conflicts documented? |
| External loader | Not validated by store copy alone | Is there current first-party or author documentation? |
A Safe Installation Workflow
Begin from the store client that owns your copy. On Steam, prefer the Workshop linked from the official product page because subscription, updates, and item provenance remain visible in one place. Do not download an executable from an unverified mirror, shortened URL, or chat attachment.
Before enabling anything, preserve a clean save and note the game version. Add one mod at a time, launch the same test world, and confirm that menus, loading, and a basic production interaction still work. If failure appears, disable the newest item first and reproduce the issue in vanilla before reporting it.
Recommended checks:
- Confirm the mod page identifies its author and recent compatible game version.
- Read dependencies and known conflicts before subscribing or importing a map.
- Back up the save outside the active save directory.
- Enable one item and test it in a disposable world.
- Recheck every enabled item after an Early Access update.
- Remove abandoned items from important saves rather than forcing them to load.
Workshop Versus Community Tooling
Steam Workshop is visible on the official Steam listing, so it has the clearest verified relationship to the Steam edition. Community tooling outside Workshop may be useful, but its existence does not make it official or safe. This page intentionally provides no executable download and no shell command because the reviewed official pages do not establish a trusted external loader workflow.
The official Xbox product page also describes dedicated modding tools, yet the reviewed page does not explain how community content is installed on the Microsoft Store version. Do not assume that a Steam Workshop item or file path works across stores. Cross-store mod parity, load order, and save portability are Pending confirmation until current platform documentation says otherwise.
Troubleshooting and Update Discipline
After a patch, test the base game before blaming a mod or reinstalling everything. Then enable previously used items one by one, starting with dependencies and ending with large content overhauls. Keep the failing combination recorded so the author can reproduce it without private account data or unrelated files.
If a world no longer opens, preserve it before removing dependencies. A mod may introduce buildings or processes that the vanilla game cannot interpret, and blindly saving after removal could make recovery harder. Exact recovery behavior depends on the mod and current build, so it is Pending confirmation; follow current author documentation when it exists.
Evaluating a Workshop Item Before Use
The official store confirms Workshop support, but each Workshop item still needs its own review. Check whether the description names a compatible game version, identifies required dependencies, explains what it changes, and provides a recent update history. Comments can reveal symptoms worth testing, but they are community reports rather than proof that the same failure will occur in your setup.
Prefer a mod whose scope is understandable before installation. A visual adjustment should not unexpectedly claim new production rules, while a new building or process should explain which saves and dependencies it affects. If the item provides no version, change summary, or removal guidance, treat its compatibility as Pending confirmation and keep it away from an important world.
| Item-page signal | Practical interpretation |
|---|---|
| Current compatible version | Useful claim to verify against the installed build |
| Explicit dependencies | Install and test those first |
| Clear change summary | Helps choose a focused disposable-world test |
| Recent author update | Better evidence than an old comment alone |
| External executable mirror | Not validated by Workshop support; avoid it |
Maintaining a Reproducible Mod Set
Keep a simple inventory of enabled items, their Workshop links, the game version, and the date the set last launched successfully. Change only one item between test runs so a new failure has a narrow cause. If a map needs a content mod, record that relationship instead of relying on the client to explain a missing object later.
Preserve a vanilla comparison world and a separate modded test world. The clean world shows whether a patch broke the base game, while the test world reveals whether dependencies load before a valuable save is opened. Cross-store identifiers, load-order guarantees, and a universal safe-removal procedure are Pending confirmation because the reviewed official pages do not document them.
For a support report, include the game version, store edition, enabled Workshop item links, and the smallest repeatable sequence. Do not attach account credentials, paid game files, or unrelated save archives. This gives an author actionable evidence while maintaining the security boundary around the installation.
Sources
Sandustry is developed by Lantto Games and published by Hooded Horse. This independent guide is not affiliated with or endorsed by the developer, publisher, Valve, Microsoft, or any mod author.