Read this before the other zone pages. A zone is two things that get edited separately, and once you see the split, most zone problems explain themselves.
Two halves, two programs#
Saber’s guides describe every zone as a zone locator plus its props. documented
| Half | What it is | Where you edit it | Where it is saved |
|---|---|---|---|
| The locator | The shape: where the zone is, how big, which way it faces, what it is called on screen | The map editor itself, in the properties panel after selecting the zone | _zones.xml or subgroups\Zone_<name>.xml under Media\prebuild\<level>\ |
| The props | The behaviour: what the zone does | The Zone Settings plugin, opened from the editor’s toolbar | zone_settings.json under Media\levels\<level>\ |
A locator on its own does nothing in game. A zone with an empty props list is only a named area, and Saber notes it will not be visible in the game until something refers to it, such as an objective. documented That is not a fault. Many zones exist only so an objective has a place to point at.
Adding one#
Place the locator#
In the editor, right-click the terrain (or the Zones section of the Scene View)
and choose Add Zone. It appears as no_id. Move it where you want it, then set
its Id in the properties panel. Save the map.
Give it props#
Open Zone Settings from the toolbar. Expand your map, then TERRAIN LOCATORS LIST, then your zone. Click the plus next to props, pick a property type, fill in its fields, and save with Ctrl+S.
Pack and test#
A map only loads with at least one expedition and one deploy zone, so you need those before you can test any other zone. See Make a map that loads.
The Id is the only link between the halves#
The Zone Settings plugin lists your zones under TERRAIN LOCATORS LIST by their Id, and that is how it matches a set of props to a locator in the scene. documented There is no other connection. If the two names differ by one character, the props belong to nothing, and the zone you placed has no behaviour.
This is where most zone problems actually come from: a capital letter, a stray space, a rename on one side but not the other. When a zone “does nothing”, compare the two names character by character before you look at anything else.
Saber’s rule for the Id is lowercase Latin letters, digits and underscores only,
for example test_zone_01, and no spaces. documented
Follow it from the first zone you place. A space in the Id is harmless for a plain
deploy point but breaks any zone that items pass through, as explained on
Where everything lives.
The Name field on the locator (UiName in the file) is separate from the Id.
It is what the player reads, so it can be a proper title.
Zones do not work inside References
Saber’s guide says zones can be added to a Reference, but will not work correctly on the map that the Reference is placed into. documented Place zones directly on the map.
One zone, several props#
Props combine. A single zone can carry several property types at once, and each one adds a function. documented Saber’s example is the typical deploy zone, which carries three:
ZonePropertyDeploy, so trucks can arrive thereZonePropertyInventoryStorage, for the Base module’s storageZonePropertyRecovery, so trucks can be recovered to it
So “a deploy zone that is also a store” is one zone, not two zones on top of each other. Props can also be added to or removed from a zone during play, as an objective reward. See Rewards.
The locator fields worth knowing#
| Editor field | In the file | What it does |
|---|---|---|
| Org X, Org Z | Org |
position on the map, in metres |
| Dir | Dir |
the direction the zone faces, drawn as a purple arrow |
| Id | Id |
the link to Zone Settings, see above |
| Name | UiName |
the name the player sees |
| Is Visible On Minimap | IsVisibleOnMinimap |
hides or shows the zone on the in-game map |
| Shape Type | ShapeType |
rectangle or circle |
| Length or diameter, Width | LengthDiameter, Width |
size in metres |
| Is Wall, Height | IsWall, Height |
raise the zone above the surface instead of lying on it |
| Icon 30x30, Icon 40x40 | Icon30x30, Icon40x40 |
leave empty, see below |
| Distributions group name | DistributionGroupName |
SnowRunner only. Not used in Expeditions |
Leave the icon fields empty
Expeditions assigns zone icons automatically from the zone’s props and the
objectives that use it. documented The
exception is a hidden hint zone marking a Climb, Ford or Shortcut, since all
three use the same prop and would otherwise look identical. Their icons are
exMountainAccess30/40, exRiverFord30/40 and exShortWay30/40.
Every property type, and where it is covered#
Saber lists these as the props for ordinary zones in Expeditions. documented
| Property | What it makes the zone | Covered on |
|---|---|---|
ZonePropertyDeploy |
a place trucks arrive at the start of an expedition | Deploy zones and FOBs |
ZonePropertyRecovery |
a target for truck recovery. Deploy zones only | Deploy zones and FOBs |
ZonePropertyBaseBuilding |
the interaction zone of a buildable FOB module | Deploy zones and FOBs |
ZonePropertyInventoryStorage |
a store of items, fuel, parts and wheels: air drops, loot, the Base module | Loot, storage and airdrops |
ZonePropertyObjectConstructionInZone |
a delivery point that builds something, with no objective | Construction zones |
ZonePropertyHiddenHint |
a marker for a Climb, Ford or Shortcut, seen by binoculars, drone and on the map | this page, above |
ZonePropertyNotification |
a message shown when the player arrives, once (executedOnce) or every time. Invisible in game |
not yet covered. Its message uses the same settings as objective notifications, see Stages and substages |
ZonePropertyMinigame |
a place to play a minigame | The assignment types |
ZonePropertyUpgradesGiver |
gives the player listed truck upgrades | not yet covered |
ZonePropertyGateway |
a link to another map | Gateways between maps |
Deploy, Base Building, Inventory Storage, Object Construction and Hidden Hint props
each carry a zoneDiscoverability block, which decides whether the player can see
the zone before finding it. See Hiding and revealing zones.
The Notification prop has one too, but Saber says not to use it there, since that
zone is never shown in game.
Gateways take extra work in Expeditions
Saber’s guide says custom regions of several linked maps are not supported in Expeditions; only standalone maps are. documented They work anyway, without a region. See Gateways between maps. tested in game
Props you should not add by hand#
Some prop types exist but are not for you to pick.
- Internal technical props:
ZonePropertyFakeVisitZone,ZonePropertyInventoryStorageQuest,ZonePopertyObjectConstruction(Saber’s spelling) andZonePropertyScouting. The game assigns these itself when you configure the matching objective. documented - FOB module props:
ZonePropertyFobModuleStorage,ZonePropertyWorkshop,ZonePropertyServiceStation,ZonePropertyParking,ZonePropertyDroneDelivery,ZonePropertySupplyShop,ZonePropertyTowTruckand the others. These belong inside a custom FOB module’s descriptor, never on a zone you place on a map.
FOB module props on a map zone can crash the game
Saber’s guide is explicit: these props must be used only for configuring custom FOB modules, and assigning them to ordinary standalone zones “might cause a crash”. documented To give a map a workshop or a service station, give the player a place to build the module, as described on Deploy zones and FOBs. To make a new kind of module, see Module descriptor reference.
Checking your work#
The packer validates some zone settings. Its errors are written to:
C:\Users\<username>\Documents\My Games\Expeditions\base\logs\ModMapError.txt
The editor will let you save a zone with wrong props, so read that log after a pack that misbehaves. documented
Also confirm your props survived the pack at all. Packing can regenerate the zone list with empty settings; see Where everything lives.