Sandustry Mods: Install Mods and Maps

Sandustry mods are official policy and community tradition at once — and as of August 15, 2026 there are two parallel routes. The official path is Steam Workshop plus the built-in modding support that shipped with Early Access. The community path is the Fluxloader toolchain built during the demo era. This page explains what each path covers, how to install Sandustry mods without breaking a save, and how to troubleshoot when something silently fails to load.

Path 1: Steam Workshop and the official modding tools

The Steam store describes Sandustry as "built with modding in mind," with support for visual tweaks, hand-crafted maps, plus new buildings and processes that slot into production chains — backed by dedicated modding tools for customizing, sharing, or overhauling the game. Steam Workshop is listed as a platform feature, and as of August 15, 2026 the game's Workshop page is live under the tagline "Mods and maps for Sandustry." For most players, that page is where Sandustry mods should come from.

The catalog is days old, so judge items by their descriptions and version notes rather than ratings — at our check, every "Most Popular" entry still showed "Not enough ratings." Sandustry mods surfaced in the Workshop's "past week" view on August 15, 2026 included:

• From the developer and community creators — Drill Test (lantto), Wired Pyro (Electric), Trim's Infinite Factory and Trim's Rocket Dispenser (TrimBarktree).
• Gameplay tweaks — Laser Overcharge, Precision Caulk, OBS Video Fix (Steejo), Electric Thermal Buffers, Flow Meter (uolkx).
• Utilities and quality of life — Mod Inspector, Power Monitor, Debug Toggle (uolkx), Sandperf Boost (Dimava), Multiple Action Bars, Clearable Keybindings (ZyniX).

Installing from Workshop is the low-risk route: open the item page, read its compatibility notes, and click Subscribe — Steam handles the download. Keep expectations calibrated, though: no Workshop item is guaranteed to work on every Early Access build, so check the item's update history after each game patch. Subscribed Sandustry mods also update through Steam: when an author patches for a new game build, the fix reaches you automatically.

Path 2: the community toolchain (Fluxloader)

During the demo period, before official tools shipped, the community built its own Sandustry mods stack, and it is still actively referenced:

• Fluxloader (formerly called "modloader") — a Node.js tool that keeps a mods folder and starts the game with those mods enabled, distributed via the fluxloader-team GitHub project.
• corelib — a shared library from the same team that mods build against.
• Custom Map Loader (Electric131) — runs on top of Fluxloader and handles building and picking player-made maps, so map files install through the same folder flow as any other mod. Its GitHub wiki was current as of v4.1.3 at our check.

Community Sandustry mods install by hand: files go into the loader's mods folder, and nothing auto-updates — you manage versions yourself.

Install Fluxloader (community route)

This walkthrough installs the community route for Sandustry mods, combining the loader's documented behavior with the community video walkthrough recorded against the demo build:

Running from source instead of a release build is documented as npm install followed by npm start.

What the community mod API can and cannot do

Fluxloader mods apply changes by patching game files — documented patch functions include addPatch (standard file modification), addMappedPatch (file mapping with a transform), and setPatch (tagged patches for organization). The API also covers messaging across the Electron, game, and worker processes, lifecycle hooks like scene loading, plus configuration-schema handling.

What the docs do not cover is a query API for reading game data — there is no official interface for pulling materials, recipes, or building statistics out of the running game. In practice that skews what Sandustry mods attempt: retextures, terrain edits, and interface tweaks are far more practical than rebalancing production chains, and when documentation falls short the game code itself settles questions no guide can.

Compatibility check before you install

Five checks decide whether Sandustry mods load cleanly or fail silently:

• Game build — know your Early Access patch level or demo version and whether the mod explicitly supports it.
• Loader version — match the mod's required Fluxloader/Custom Map Loader version; the loader wiki warns that mismatches cause silent load failures.
• Dependencies — install shared libraries such as corelib first; a missing dependency can make a mod vanish without an error.
• Map vs mod — a map file is terrain data, not gameplay code. Map-loader instructions do not install mods, and the loader's Mod API is a developer interface, not map scripting.
• Paper trail — record the source URL, release version, install date, and whether the save was tested. You will want all four if you ever report a bug.

Safe installation checklist

Use the same order every time you change Sandustry mods, and a bad install never costs you a factory:

Take the backup step seriously: the pinned save-file topic on the official Steam discussions hub shows where your save folder lives — copy the whole folder, not a single file. A dated backup plus a dated list of installed Sandustry mods turns any failure into a two-minute rollback. Sandustry has save versioning — its 0.0.3 devlog noted that introducing it forced a fresh start for old saves — so treat any mod that touches save data as a risk to an existing base.

Troubleshooting

Most Sandustry mods fail quietly, so work the list in order:

• Mod not visible in game — wrong folder depth, or the loader never generated its mods folder; re-extract keeping the archive's structure and relaunch the loader.
• Crash or load error on startup — usually a version mismatch or two mods in conflict; update the game, loader, and mod, then re-enable one at a time.
• Mod loads but content is missing — suspect a missing dependency; the game can silently skip a dependent mod.
• Map not listed — file placement, file extension, or an outdated loader; map-specific fixes live on the custom maps page and in the loader wiki's FAQ (Installing Maps).
• Save corruption after removing a mod — restore your backup, and disable the newest addition first; a map can be valid while one of its dependencies is not.

Which path should you pick?

New to Sandustry mods entirely? Start on the Workshop route — subscribing is reversible in one click, and Steam keeps items updated as authors patch them. Reach for the community route when you specifically need something Workshop does not carry, such as a demo-era custom map pack or a Fluxloader-only project. The two routes can coexist on one install, but treat them as separate worlds: an item's Workshop page says nothing about a Fluxloader mod's requirements, and vice versa. Whatever you pick, Sandustry mods are version-sensitive content, so recheck both catalogs after every game patch.

Two boundaries for this site: we never host or re-upload Sandustry mods ourselves, and debug/cheat utilities (such as the Debug Toggle Workshop item) are a separate topic covered on the cheats page, not part of the normal installation flow.