Sandustry Map Guide: Custom Maps and Loader Limits
The collected material documents a demo-era custom-map workflow using a mod loader, a map-loader mod, and extracted files placed in a Maps folder. Treat those steps as version-specific and do not apply a custom map’s rules to normal worlds.
Understand the source scope
The collected Sandustry map material focuses on custom maps and a loader demonstration from the demo period. It does not provide a complete atlas of generated biomes or fixed coordinates for a normal world. Generated terrain and resource positions should not be inferred from one showcase save.
A second collected video demonstrates a custom map called Oasis with modified resource behavior. Those conditions belong to that map and its supporting modifications. They are not evidence that ordinary Sandustry worlds contain the same infinite resources or progression rules.
Follow the documented demo-era workflow cautiously
The demonstration begins by obtaining the mod loader from the community resources linked through the official Discord. Its executable is placed with the Sandustry demo files and launched so the required mods and configuration folders are created. A custom map loader is then placed in the mods folder.
Extracted map files go into the loader’s Maps location in the documented setup. Folder nesting matters because placing an archive or an extra parent directory in the wrong level can prevent discovery. These names and locations are version-specific and should be checked against current loader instructions.
Select the custom map at launch
In the collected demonstration, the modded launcher exposes a map choice before starting a new game. The player selects the installed map from that control and then creates the world. A map that does not appear usually indicates an installation, extraction, or version mismatch rather than a vanilla setting.
Back up relevant saves before changing loaders or map files. Use the loader build and map version named by the map author. The collected source does not confirm compatibility between old demo packages and the current Early Access release.
Separate custom-map rules from the base game
Oasis is shown with special resource behavior and an additional refinement modification. Its infinite Sand, Water, and Redsand presentation is explicitly part of that custom experience. Do not carry those assumptions into a standard generated map or another creator’s map.
Factory layouts can also depend on the custom terrain’s fixed geometry. A compact route designed around an Oasis chamber may not paste safely into a normal cave. Evaluate available space, resources, research, and mod dependencies independently for every map.
Install community content safely
Use links and instructions supplied by the loader or map author rather than an unrelated repost. Read the required version and dependencies before adding files. If the package includes a README, its current instructions take priority over the older video sequence summarized here.
Change one component at a time: loader first, then the map-loader mod, then one map. Launch between stages so a failure has a clear cause. Avoid assuming a custom map is broken until archive extraction and folder nesting have been checked.
This page intentionally does not invent a modern one-click Workshop workflow. The collected evidence supports an older manual loader process and a custom-map example only. Current Early Access players should verify the present community documentation before using those exact paths.
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.