How scalespeeder/dayz-chernaurus-zapad-underground-bunker-custom-json-file-for-pc-and-console works
1. This repository is not an application codebase; it is a DayZ map-content package. Its purpose is to define and deploy a custom underground bunker into a Chernarus server.
2. There are two main artifacts:
- ZAPADbunker.json: the deployable server-side object spawner definition.
- ZAPADbunkerproject.dze: the editable DayZ Editor project/source file used to modify the bunker layout visually.
3. The runtime boundary is the DayZ server. The server does not run custom logic from this repo; it reads the JSON as static world-geometry/object-spawn data through cfggameplay.json.
4. The configuration flow is:
- Edit the bunker in DayZ Editor using the .dze file.
- Export or place the resulting JSON into the server mission’s custom/ folder.
- Reference that JSON in cfggameplay.json via objectSpawnersArr.
5. The repo’s content is therefore split between authoring and deployment:
- .dze = source asset for map editing.
- .json = production asset consumed by the game server.
6. The main functional payload is a structure spawn at fixed world coordinates near West of Myshinko on Chernarus, specifically around 584.66 / 8094.18. That makes the bunker location part of the data model, not dynamic gameplay logic.
7. The server integration boundary is important:
- On PC, enableCfgGameplayFile = 1; must be enabled in serverDZ.cfg.
- On console/Nitrado, cfggameplay.json must be enabled through server settings.
This repo depends on that external server configuration being active.
8. The repo assumes a mission-folder based content pipeline. The JSON is not meant to be loaded directly from the repository; it must be copied into the server’s mission custom/ directory and then referenced from gameplay config.
9. The architecture is intentionally minimal: there are no scripts, binaries, or dependencies in the repo itself. All behavior is driven by DayZ engine support for object spawners and editor-importable map data.
10. Operationally, the bunker has a couple of gameplay constraints noted in the README that affect testing and placement expectations:
- players cannot climb out normally and must relog to surface,
- dropped items may disappear from the bunker space.
These are runtime effects of the placed geometry rather than separate code paths.
11. The external tooling boundary is DayZ Editor, which is used to author or revise the structure. The repo serves as a portable distribution of that authored content, not as a mod framework.
12. For an architecture diagram, the key nodes are: authoring tool (.dze), deployable content (.json), DayZ mission config (cfggameplay.json / serverDZ.cfg), and the DayZ server/runtime that instantiates the bunker in the world.
Main entry points: readme.txt README · ZAPADbunkerproject.dze Bunker project · ZAPADbunker.json Bunker JSON
Components 9
Authoring
Editable source content used to place and revise the bunker layout
- DayZ Editor · Visual editor used to author and revise the bunker layout
- Bunker project · Editable DayZ Editor project file for the bunker layout
ZAPADbunkerproject.dze
Deployment
Server-side content packaging and config wiring
- Bunker JSON · Deployable object-spawner definition for the underground bunker
ZAPADbunker.json - custom folder · Mission-folder location where the JSON is copied for server use
- Gameplay cfg · cfggameplay.json entry point that references object spawner definitions
- Server cfg · Enables cfgGameplay loading on PC via serverDZ.cfg
- README · Operational notes covering deployment, editor workflow, and runtime constraints
readme.txt
Runtime
DayZ engine and server-side world instantiation
- DayZ server · Game server/runtime that reads the object spawner data and places the bunker
- Bunker build · Static underground bunker structure instantiated in Chernarus near Myshinko
Connections 11
- DayZ Editor → Bunker project: edits · The bunker is authored visually in DayZ Editor through the project file
- Bunker project → Bunker JSON: exports · The editor project is exported into the deployable object-spawner JSON
- Bunker JSON → custom folder: copy to · The JSON must be placed in the mission custom folder on the server
- custom folder → Gameplay cfg: referenced by · cfggameplay.json points at the deployed object spawner definition
- Server cfg → Gameplay cfg: enables · serverDZ.cfg must allow cfgGameplay loading on PC
- Gameplay cfg → DayZ server: loads · The DayZ server reads the configured object spawners at startup
- DayZ server → Bunker build: spawns · The runtime instantiates the bunker as static world geometry
- README → DayZ Editor: documents · The README explains the authoring workflow and external tooling
- README → Gameplay cfg: documents · The README describes the gameplay config integration path
- README → Server cfg: documents · The README notes the server setting required to activate cfgGameplay
- Bunker build → DayZ server: lives in · The bunker exists as a runtime placement managed by the server