Make a map for Expeditions#
Saber shipped a map editor with the game and a set of official guides to go with it. The guides are accurate. They are also written field by field, in the order the software stores things, which means you can read four pages about deploy zones and still not know what a deploy zone is for.
This guide is the other way round. It explains what a thing is and what it is for, then tells you which fields to fill in. It assumes you have never opened the editor.
Read this first if you read nothing else#
Two rules save more time than everything else on this site combined.
-
Get a map that loads before you make it pretty. A map needs a shape, one deploy zone and one expedition. That is it. Build that on your first day, pack it, and drive around an empty landscape. Now you have a foundation. People who spend three weeks sculpting a canyon and then try to make it load spend the next three weeks finding out why it does not.
-
Your map exists in three places at once, and they drift apart from each other constantly. Almost every “I fixed it and nothing changed” story comes from editing the wrong copy. Read that page early.
Where to start#
- What you needThe editor, the folders, and roughly how long things take.
- Where everything livesThree copies of your map, and which one to edit. Read this one early.
- Make a map that loadsThe shortest path from nothing to driving around your own terrain.
- Something is brokenSymptom to cause. Start here when the game misbehaves.
- Your own 3D modelsDownload, build or generate a model, import it in one command, and make the map load.
- Porting a SnowRunner truckThe meshes just work. The textures do not, and that is the whole story.
- Every base moduleAll twelve FOB modules, one page each: screenshots, models and every image slot.
- DownloadsEvery tool, template and pack the guide mentions, in one place.
- Using AI with the editorThe scripts and agent skills, what they are good at, and what they must not be trusted with.
Maps, and everything else#
Most of this guide is about building maps, because that is the biggest surface. Two other parts of the editor get the same treatment: bringing vehicles over from SnowRunner, and the tooling β a set of plain Python scripts plus agent skills that automate the work the editor structurally cannot do. Both are written to be read by someone doing it by hand; the automation is optional throughout.
How this guide marks what it knows#
Modding an engine you did not write means some things are documented, some are discovered, and some are still guesses. This guide labels which is which, on every claim where it matters.
documented Stated in Saber's official guides.
schema only Found in the editor's own type definitions and in the shipped game code, but missing from the official guides. Real, and usually untested by anyone.
unverified Worked out from evidence but not yet proven in a running game. Test it before you depend on it.
Pages still being written are marked in the sidebar. Nothing is padded out with guesses to look finished.
What this guide is not#
It is not a replacement for the official reference, which remains the place to look up an exhaustive field list. It is the thing you read first so the reference makes sense.
It is also not affiliated with Saber Interactive. It is written by people who build maps, and it includes the mistakes.