Skip to main content

​
Where Are the Config Files?

All config files are automatically generated on the first server start under:
The global files sit at the root of that folder; the per-helicopter files live in its HeliConfigs\ sub-folder. The Presets\ and Backups\ folders are created alongside them.
$profile: refers to your DayZ server profile directory — the folder that contains your BattlEye, mpmissions, and .RPT log files.

​
File List

Each helicopter variant gets its own JSON config file, named after its classname and stored in the HeliConfigs\ sub-folder:
With 29 spawnable variants across 7 helicopters, you will see 29 individual config files in there, plus the global files at the root of CZAutoz_Heli\. MD500 Civilian MH-6 Little Bird SA342M Gazelle UH-1H Iroquois MH-60L Blackhawk AW101 Merlin MH-47G Chinook Global — these sit at the root of $profile:\CZAutoz_Heli\, not in HeliConfigs\:

​
How to Edit

  1. Navigate to $profile:\CZAutoz_Heli\HeliConfigs\
  2. Open the JSON file for the helicopter you want to adjust in any text editor
  3. Change the values
  4. Restart the server — direct edits to the JSON files are read on startup, so they only take effect on the next start
Prefer not to restart? The in-game Admin Panel edits the same settings and applies them live (since v0.2.3) — every spawned helicopter and connected player updates instantly, no restart or reconnect. Only direct JSON file edits need a restart. See Admin Panel & Permissions for opening it, staff roles and every permission key.
Per-helicopter flight values (flight.liftMultiplier, control.pitchStrength, control.bankStrength, etc.) are pre-tuned by the development team and are not recommended to change. Modifying them can result in helicopters that are difficult or impossible to fly. Adjust at your own risk.
The global settings in mod_config.json (cargo modules, repair, toggles, logging) are completely safe to adjust — they don’t affect flight behaviour.

​
How to Reset to Defaults

Delete the helicopter’s JSON file and restart. It will be regenerated with all default values.

​
Config Migration on Version Update

Since v0.2.3, a mod update migrates your configs in place — both mod_config.json and all per-helicopter files. New keys are added, removed keys cleaned up, and all your custom values are kept. This keeps your configs in sync with new and changed keys without losing your tuning.
  • Your originals are backed up first to $profile:\CZAutoz_Heli\Backups\v<oldversion>_<date>\ before any migration touches a file
  • Custom values are carried over — only the schema (which keys exist) is updated, not your settings
  • Only when first moving from v0.2.2-or-earlier onto a v0.2.3+ build might a one-time re-apply be needed
Since v0.3.1, updates additionally use Smart Config Updates. On the boot where the version changes, any value you never changed adopts the new shipped default automatically — tuning improvements now reach your server without a reset — while any value you customised is kept exactly, per key, covering both the per-helicopter configs and the flight-mode profiles in mod_config.json. Files that adopt values are backed up first to Backups\smartupdate_v<version>_<date>\. Using the Admin Panel’s per-row Reset returns a key to defaults and makes it adoptable again in future updates. No extra files or fields are involved — versioning is tracked once, by the version field mod_config.json already has, and the per-helicopter files contain nothing but settings. And you’re never left guessing about the values you customised: when an update changes a default behind one of your custom values, the server log names it per row with both numbers — for example control.pitchStrength (yours 2.00, new default 2.30) — so you can decide, row by row, whether to keep your tune or reset it in the Admin Panel to adopt the new one. Admins and staff are also notified in-game: joining after an update shows an on-screen summary of what auto-adopted and what was kept, and an update-available notice appears each session whenever a newer mod release exists than the one the server is running. Regular players never see these notices.
The migration is triggered by the version field stored in mod_config.json changing. Do not manually edit it — let the mod set it.

​
Configuration Reference

The full configuration reference lives on this documentation site — see Global Settings for mod_config.json and Per-Helicopter Settings for the per-variant files.
The old in-game $profile:\CZAutoz_Heli\Guide\ reference folder is no longer generated as of v0.2 — all configuration documentation now lives here on the docs site.