Skip to main content

Map in player view

This page explains what can appear on the map, which access rights control visibility, and what guests see.

The map is dzbot's own topographic map of Chernarus, Livonia, Sakhal and Nasdara, drawn from the game data, and goes down to buildings, fences and single trees at the closest zoom level. It is the same map as the free public map at map.dzbot.de — with its search, item spawns and points of interest — plus your server's own layers.

Data source note: live activity layers depend on imported server logs. For expected delays and freshness behavior, see Logs import concept.

Navigation path:

  • Main navigation -> Map

Access rights overview​

Required to open the map​

  • map.access

If this right is missing, you see the map the server shows to guests (see The map for guests) — or, if the server does not show one, no map entry at all.

Layers and required rights​

  • Players (all online players): map.see_players
  • Players (only your own position): map.see_own_position (used when map.see_players is not granted)
  • Bases (all bases): map.see_bases
  • Bases (limited view): without map.see_bases, only bases you contributed to are shown — and all of them, regardless of the size filter
  • Zones (No-Build / No-Kill): map.see_zones
  • Faction members: only map.access; shows the members of your own faction who chose to share their location (see Factions), and only while the server has Show faction members on the map enabled
  • Allied factions: only map.access; each allied faction is its own layer with the members who chose to share their location with allies too — only while the server also has Allow sharing locations with allies enabled
  • Bounty targets: requires bounty feature + hitman access (hitman.access). For a bounty on a faction, every online member is shown
  • My markers: only map.access; only you see them (see Your markers)
  • Faction markers: the faction member right view_markers
  • Group markers: membership in the group (see Groups); no server right needed

What can be shown on the map​

Depending on your rights and server features, the map can show:

  • Players
  • Fellow faction members who share their location
  • Members of allied factions who share their location with allies
  • Bases
  • No-Build Zones
  • No-Kill Zones
  • Bounties
  • Base Alarms
  • Base Alarm (violators) category with players inside your alarm radius who are not allowed

Notes:

  • Base Alarm overlays are shown for alarms where you are in the allowed player list.
  • Violator markers are only calculated when you do not have map.see_players.

Base size filter​

Bases are drawn according to their size: dot size grows with the base, decaying bases are dimmed, and only bases from Large upwards carry a label — a hundred overlapping labels was what made the old map unreadable.

In the layer panel, under Bases, you choose the smallest size still worth drawing. The server's own default comes from its settings (World → Smallest base size on the map); your choice only applies to your current view and is kept in the link.

The size bands themselves are absolute numbers per server, calibrated on the Bases admin page.

Your markers​

You can set your own markers on the map: a stash, your tent, a meeting point, a danger spot. Nobody else sees your markers — not other players, not the server's admins.

  • Set a marker: right-click the map (on a phone or tablet: press and hold). Pick an icon and a colour, give it a name and, if you like, a note.
  • Where it shows: on this server (the default here) or on the whole map — then it also shows on every other dzbot server with the same map and on the public map at map.dzbot.de.
  • Open a marker by tapping it. There you can edit it, copy the coordinates or delete it.
  • Move a marker by dragging it. With a mouse you can drag any of your markers straight away; on a touchscreen, tap it first, then drag it. Undo in its card puts it back.
  • Use as delivery spot saves the marker as one of your saved places, so orders can be delivered there.
  • Share with faction copies your marker into your faction's markers (needs manage_markers, see below). The copy belongs to the faction; your own marker stays.
  • Each player can keep up to 500 markers per map, each faction 500.

Faction markers​

A faction can keep markers its members share — the stash, the rally point. Two faction member rights decide who takes part:

  • view_markers — sees the faction's markers in the Faction markers layer
  • manage_markers — also sets, edits and deletes them, and copies own markers into the faction

Nobody gets these rights automatically, not even when joining: a new member does not see the stash until someone grants it. Faction admins have both. Whoever manages faction markers sees how many members cannot see them yet, with a link to the faction's rights.

Faction markers refresh every minute, so a marker a member sets shows up for the others shortly after.

Groups​

A group shares markers with friends, whatever server they play on: everyone in the group sees the group's markers and can set, change and delete them. A group belongs to its members, not to a server — its markers show on the public map and on every dzbot server with that map.

  • Create a group: in the layer panel under Markers, open Groups and give the group a name.
  • Invite: open the group and share or copy its invite link. Whoever opens it signs in with Discord, sees the group's name and member count and joins with one tap. New link makes the current link stop working; everyone already in the group stays.
  • Set a group marker: when you set a marker, choose the group under Shown on. A marker you already have can be copied into a group with Share with <group> on its card; your own marker stays.
  • Each group is its own layer on the map, with a small G on its markers.
  • Members can do everything except delete the group: share or renew the invite link, rename the group, remove members and set, change or delete every group marker. The owner can also delete the group and hand ownership to another member. Nobody can remove the owner.
  • Leaving: you no longer see the group's markers; the markers you set stay with the group. If the owner leaves, the member who has been in the group longest becomes the owner. When the last member leaves, the group and its markers are deleted.
  • Privacy: group markers are visible to the group's members only — not to server admins, not in the admin search and not to the AI Companion.
  • Limits: 50 members per group, 1,000 markers per group and map, and you can be in up to 20 groups.

Group markers refresh every 15 seconds while the map is open, so the group sees a new marker almost right away.

On the public map​

The free map at map.dzbot.de has the same markers: sign in with Discord (in the layer panel) to set and see them. Markers you set there are for the whole map.

One switch at the top chooses what you see: a Vanilla map (Nasdara, Chernarus, Livonia, Sakhal) or a server. It lists My servers — the dzbot servers where you have map access — and Public servers, which show their map to everyone; each server shows its map next to its name, and choosing a server on another map switches the map with it. Choosing your server shows the map exactly as on that server: its mod objects, every layer your rights allow, your markers for that server and your faction's markers; new markers go to that server by default. Choosing a public server shows what it shows guests. The choice is kept in the link and remembered for your next visit — the item wiki at wiki.dzbot.de shares it. A server you have no access to and that is not public falls back to the plain map.

Layers and what you click​

The layer panel (on a phone: the sheet at the bottom) lists, from the top: your markers (your own, your faction's and one layer per group), the server's own layers (zones, bases, base alarms, faction members, bounties, players — as far as your rights go, with their count and the time of the last refresh) and the map's points of interest. Tap a layer to hide or show it. Only points of interest the map actually has are listed. Vehicle and boat spawns, wrecks, locked containers and game animals fold open with the arrow beside them, so you can show single types — say only the M3S trucks, the trains or the red deer — instead of all of them.

Locked containers are the coloured shipping containers that open with the shipping container key of the same colour. The layer only exists where they really spawn: in vanilla on Sakhal (blue or yellow) and Nasdara (green); on a server also wherever its mission files add them. A spot that can spawn more than one colour lists every key that may fit.

Players, bases, bounty targets and faction members fold open the same way, listing everyone by name, so you can follow single players or bases. Switch the layer off first and pick the ones you want to see only them; with the layer on, picking one hides just that one — a player who comes online later still shows up. The ones you picked stay at the top of the list; one who goes offline stays there greyed out, so you can still unpick them. A long list has a field on top to filter it by name.

Players are shown with the Discord picture of their main account, framed in the colour of that account's faction (grey without one) — an alt account shows its owner's picture and faction. Players standing close together fold into one picture with a count; tap it for a list of everyone in it (on a computer, resting the mouse on it is enough), and names appear close up. A bounty target carries a crosshair badge. Bases are dark octagons sized by the base, with a dashed rim while they decay.

On Nasdara the Radio bunkers layer shows the 23 bunkers the night radio can name. Opened from the wiki's radio bunker decoder, the map shows each heard door code beside its bunker, and a bunker's card shows its Door code with a copy button. The codes are part of the link until they expire, so a shared link carries them.

Tap a player, base or zone on the map to open its card: name, where it is, its coordinates to copy and — for admins — a link to its page.

Events, spawns and loot from your server​

The map's mission layers — heli crashes, military convoys, police cars, wrecks, locked containers, vehicles and boats, contaminated zones, animal territories, infected zones and player spawns — and the item spawns of the search are read from your server's own mission files: events.xml, cfgeventspawns.xml, cfgeffectarea.json, cfgenvironment.xml, cfgplayerspawnpoints.xml, types.xml, the loot building files, and for locked containers also the object spawner files in cfggameplay.json and init.c. What your mods changed in these files is included; spawner files hidden from the map in izurvive.json (such as mods you hid) stay hidden. The card of such a point says when the files were read.

  • Who sees them is up to the server: Settings → Map & Bases → Share loot settings (see Share loot settings). Members only shows them to the server's players, Public to everyone, guests included. With Off — the default — and for everyone the server does not share with, the map shows the vanilla layers.
  • When they are read: right after sharing is switched on, then once a week, when an admin recomputes the map on the mods page (once a day), and shortly after the server boots into another map.
  • Until then — a new server, another map, or files that could not be read yet — the map shows the vanilla layers. If reading fails later, the map keeps the last reading.
  • Item search knows the vanilla items only; items your mods add are not searchable. An item shows how rare it is as a level, never the server's exact numbers.
  • The same reading feeds the server's page in the item wiki.

Loot tiers​

In the layer panel, Loot tiers → Tier zones tints the map by loot tier — the value tier the economy paints onto every area, which decides how good the loot in a building there can be. Tier 1 stays clear; Tier 2, 3 and 4 get warmer and stronger from yellow to red, and the few Unique spots are pink. The tint is only information: it does not change what you click, and the points of interest stay on top. The switch is off by default and kept in the link.

The zones come from the same reading as the layers above — the server's areaflags.map and the tier names in its cfglimitsdefinition.xml — so a server that moved its tiers shows its own zones, under the same sharing rule. Everyone else, and map.dzbot.de without a server, sees the vanilla tiers. Where a cell carries several tiers, the highest one wins; value flags with other names are left out.

The map for guests​

A server can show its map to everyone, without login (Settings → Guest pages → Show Map to guests). Guests — and logged-in players without map.access — then see:

  • the terrain and the buildings of the server's mods
  • the zones the server marked as Visible to guests (see Zones): outline, name and colour
  • the map's points of interest, search and item spawns — from the server's mission files, as described above, when the server shares its loot settings with them (for guests: Public); the vanilla ones otherwise

Never players, bases, base alarms, bounties or live counts. While the server is paid or in its trial, its map is also offered under Public servers on map.dzbot.de.

Measuring distances​

The ruler button below the zoom buttons starts measuring. Every click (or tap) on the map adds a point, so you can lay out the route you would actually run — around a river, a hill or a military zone. Each leg shows its length and, with a mouse, a dashed leg follows it to the next spot. Backspace or a right-click removes the last point, Esc or the ruler stops measuring.

The panel shows the whole length and how long it takes to run, holding sprint without load: sprint until stamina is empty, jog until the game lets you sprint again, sprint again. The time uses the stamina of the server — its maximum stamina and sprint drain from cfggameplay.json, read with its mission files (see Events, spawns and loot from your server). A server that boosts stamina therefore shows shorter times. Where the server does not share its files with you, and on map.dzbot.de without a server, vanilla values are used; the panel says which. The time is for a straight run over the measured line — terrain and heavy gear make it longer.

Coordinates​

  • With a mouse, the corner bottom right shows the coordinate under the pointer. Ctrl+C (⌘C on a Mac) copies it, as X / Z — as long as no text is selected.
  • A click (or tap) on an empty spot pins it: its card shows where it is and its coordinates, with buttons to copy them, share a link to the spot and — signed in — set a marker there. The next click on the map closes it again.

Other map controls​

  • Search finds places, coordinates, point-of-interest categories and items — an item shows the buildings where it can spawn, how rare it is (from not rare to extremely rare) and a link to its page in the item wiki. On your server it also finds players and bases by name: picking one jumps to them, opens their card and switches them on if they were hidden.
  • Zoom +/- zooms one level in or out. The mouse wheel and a pinch on a touchpad or touchscreen zoom smoothly; two fingers on a touchpad move the map.
  • The server's layers refresh automatically every few seconds.

Persistence behavior​

The view, the layers you switched off, single players and bases you picked, the base size and a selected point live in the link: copy it to share exactly what you see, and a reload keeps it.

The map also opens the way you left it, per map and server: the view, the layers, single players and bases and the base size (not an item search or a selected point). Signed in, that follows your account to every device; as a guest it is kept in this browser. A link always wins — opening one shows what it says.