Sandustry Mods: What the Collected Sources Confirm
The collected sources document a manual demo-era Mod Loader workflow: place the loader with the demo, let it create its folders, then add mods or custom maps. Current Early Access compatibility is not confirmed by those sources.
What the collected Sandustry mods information covers
The collected Sandustry mods material documents community modding for the demo period. It describes a manual Mod Loader workflow, a custom map loader, and several example mods shown in community videos. It does not provide a complete current Early Access compatibility list or a guaranteed one-click installation method.
Treat every package as version-specific. The source tutorial itself warns that its Mac loader may be out of date, while the video workflow targets the Sandustry demo. The official Discord, the mod author’s instructions, and the package README should take priority over an older transcript when their steps differ.
Install the documented demo loader
The Windows demonstration starts by getting the Mod Loader from the community resources linked through the Sandustry Discord. The loader executable is copied into the Sandustry demo folder, which the transcript identifies as the regular Steam installation directory. A desktop shortcut can then be made so the loader becomes the normal way to start the demo.
On first launch, the loader opens and closes, then creates a mods folder and a configuration folder. That first run is part of the documented setup rather than evidence that the loader failed. Close the game and inspect the generated folders before adding another package.
The collected Mac tutorial describes a different package and a terminal-based setup. It tells the player to unzip the downloaded Sandustry Mac folder, install Node.js, open a terminal in that folder, install the listed dependencies, make launch.sh executable, and start the loader with node index.js. Because the tutorial is explicitly short and may be outdated, do not assume these commands apply to Windows or the current Early Access build.
Add a mod or custom map
After the loader has created its folders, the video places a custom map loader file in the mods folder. A downloaded custom map is extracted and moved into the loader’s Maps location. Relaunching the loader then exposes the installed map in its map selector before a new game is created.
The safest order is loader first, map-loader second, and one map or gameplay mod third. Launch between stages so an error has a clear cause. If a map does not appear, check archive extraction, folder nesting, loader version, and the author’s required dependencies before changing unrelated files.
The collected source also says that ordinary community mods can be added through the same mod folders. It does not confirm a universal directory for every operating system or every release. Use the package’s own installation note whenever it conflicts with the older demo workflow.
Examples shown by the sources
The community material mentions a custom Oasis map with effectively unlimited Sand, Water, and Redsand for that modded map experience. It also shows an additional Refinement modification intended to support heat-based production loops, plus an Industry mod. These examples change the available rules and should not be used as evidence for the behavior of a normal generated world.
The video lists quality-of-life and presentation changes such as Some QoL, Bigger Grabber, Portals, Pixelated, Auto Save Slow Down, No Fog Overlay, a Void King skin, and movement or reload adjustments. Some of these are personal selections from the creator’s mod list, not recommendations or official features. The source also notes that a special refinement mod shown in the video had not yet been released at the time of recording.
A mod can change resource availability, progression, movement, visuals, or factory convenience. That flexibility is useful for experiments and custom-map showcases, but it also changes what a guide or achievement result means. Record which packages are active before comparing a modded save with an unmodified playthrough.
Avoid common version mistakes
Do not assume demo mods work on the Early Access release. The collected official Steam material describes Workshop support for the game, but the keyword-specific installation evidence here is a manual demo-era loader process. A Workshop item, a community loader package, and a custom map archive can follow different update and dependency rules.
Back up saves before changing loaders or map files. Add one package at a time, start a fresh test world when a mod changes progression, and remove a failing package before diagnosing the base game. If the game stops launching, return to the author’s current instructions and the official Discord rather than copying more files at random.
The reliable conclusion from the collected sources is narrow: Sandustry has a documented community modding path, and the demo loader can create folders for mods and custom maps. The exact current installation process, compatibility, and available packages must be verified against the active release. This page therefore avoids inventing download guarantees, mod counts, folder paths, or universal support claims.
Source notes
This guide consolidates only the collected official, developer, Steam Community, video transcript, and community material available for this keyword. Version-specific or community-observed behavior is identified in the text; unsupported details are omitted.