Skip to main content
1

Join the CZ Autoz Discord

All purchasing and whitelisting runs on your Discord account — do it in the CZ Autoz Discord, or in your browser at czautoz.co.uk (log in with the same Discord). Either way you must be a member first.

Join the CZ Autoz Discord

Click to join the CZ Autoz Discord server
Everything below can also be done on the website with the same Discord login — purchasing, whitelisting and managing your servers, all kept in sync with the Discord bots.
2

Purchase CZ Autoz Helicopter Core System

Once you’re in the Discord, head to the purchase channel and follow the bot’s instructions to purchase the CZ Autoz Helicopter Core System.

Purchase Channel

Open the purchase channel in Discord

Prefer your browser? Buy on the website

Log in with Discord at czautoz.co.uk/store to browse, add to your cart and check out — same prices, same instant delivery. Buying 2+ together saves 10–15% on your first order.
3

Whitelist Your Server IP

After purchasing, navigate to the IP whitelisting channel and use the CZ Autoz Bot to register your server’s public IP address. The mod will not function on non-whitelisted servers.

IP Whitelisting Channel

Open the IP whitelisting channel in Discord

Or whitelist on the website

Set your keyword, add server IPs, declare your free test server and buy extra slots at czautoz.co.uk/whitelist — kept perfectly in sync with the Discord bot.
Make sure you submit your server’s public IP address, not your home/local IP. If your server IP ever changes (e.g. you switch hosts), return here and re-whitelist the new IP.
4

Download the PBOs

Navigate to the mod download channel in the CZ Autoz Discord and download the two PBO files.

Mod Download Channel

Open the mod download channel in Discord
You will receive 2 PBO files:
  • CZAutozHelicopter_Scripts.pbo — client and server scripts
  • CZAutozHelicopters.pbo — helicopter assets (models, configs, textures)
5

Add the PBOs to Your Server Mod Pack

Copy both PBO files into your server’s mod pack. A server mod pack is a folder containing a collection of PBO files that gets loaded by your server — it typically already exists if you run other mods.Place the PBOs inside the Addons\ folder of your mod pack:
6

Sign the PBOs with DS Utils

DayZ servers require all PBOs to be signed with a private key before they are accepted. Use DS Utils to sign both PBO files with your server’s private key.
  1. Open DS Utils
  2. Load your .biprivatekey file
  3. Sign both PBO files — this generates a .bisign signature file alongside each PBO
Your .biprivatekey must never be shared with anyone. It is your private signing key — anyone who has it can sign PBOs as if they were you. Keep it private and back it up securely.Your .bikey (public key) is safe to share and distribute — it is what players and servers use to verify signatures.
Copy your .bikey (public key) into the Keys\ folder in the root of your server:
Without the .bikey in the Keys\ folder the server will reject the PBOs and the mod will not load.
7

Publish Your Mod Pack to Steam Workshop

Update or publish your mod pack to the Steam Workshop using the Publisher tool inside DayZ Tools:
  1. Open DayZ Tools → Publisher
  2. Select your mod pack folder (@YourModPack)
  3. Upload or update the Workshop item
If this is a brand new Workshop upload: after the initial publish, you must run a second update immediately — select the same @ModFolder again in Publisher and push the update. This second upload generates the Workshop Publisher ID, which is required for the mod to function correctly across clients and servers. Without it, the mod may not be publicly downloadable, may fail to load on clients, or may not be recognised by the server correctly.
Once published and the Publisher ID is confirmed, ensure the mod pack is loaded on both client and server side. How you load it depends on your setup — if you manage your server manually, add it to your -mod= startup parameter; if you use a server management panel (e.g. Nitrado, GTXGaming, PteroPanel, or Architect Manager by CF Tools), it will have its own mod management section where you can enable Workshop mods directly.
No Community Framework (CF) needed. The helicopter mod is fully standalone — it does not require @CF or any other framework dependency.Purpose-built integrations — Survivor Animations (proper pilot pose), VPP Admin Tools, Community Online Tools, Push-a-Car and FoXy’s No Fly Zone — are optional and auto-detected: load them and they just work, with nothing to configure.Other vehicle mods such as DayZ Expansion, MuchCarKey, TraderPlus CarLock and RaG work because the helicopters are native CarScript vehicles, not because of any detection code on our side — they treat a helicopter exactly as they treat any other car.
If you are updating an existing Workshop mod pack, players will automatically receive the updated PBOs the next time they launch the game with your server selected.
8

Start the Server

Start your server. On the first boot the mod automatically generates its whole configuration tree under $profile:\CZAutoz_Heli\:
The per-helicopter files live in HeliConfigs\, not in the root, and each one is named after its classname — <Classname>_Config.json.
Full configuration documentation lives on this docs site — see Quick Start and the per-helicopter settings pages for every option.
9

Make Yourself an Admin

Admins and roles live in their own file — $profile:\CZAutoz_Heli\permissions_admins_config.json — generated alongside mod_config.json on that first boot. Add your Steam64 ID there with the owner role for full access, then restart the server and press F10 in game to open the Admin Panel.

Admin Panel & Permissions

Adding admins, the role system, and every action the in-game panel can perform
10

Add Items to Your Loot Economy

Add the two required item classnames to your server’s types.xml so they can spawn in the world.See Required Items for ready-to-use types.xml entries.
11

Persistence — No Setup Required

As of v0.2.1 the helicopters inherit DayZ’s CarScript base class, so they are covered by DayZ’s native vehicle Central Economy root automatically — no manual persistence setup is needed. Helicopters persist across server restarts out of the box.
Upgrading from v0.2? v0.2 was built on the Transport base class and required a manual <rootclass name="CZAutoz_Helicopter_Script" act="car" reportMemoryLOD="no" /> entry inside the <classes> block of your mission’s cfgeconomycore.xml. As of v0.2.1 that entry is no longer required — you can safely remove it. You should also wipe existing helicopter persistence once when updating, as the save format changed with the base-class migration.
12

Add Helicopters to Your Server

Add helicopter classnames to your server’s events, trader, or loot config. Every spawnable classname — all seven airframes and each of their variants — is listed on the Helicopter Overview page.For ready-to-use types.xml and events.xml entries covering every variant, door item, and wheel, see types.xml & events.xml.Example classnames:
13

Configure & Tune (Optional)

Edit the JSON files in $profile:\CZAutoz_Heli\ to tune flight physics, damage zones, fuel, and more to suit your server. The keys are grouped into nested sections:
  • mod_config.json — logging, features, featuresSimple, featuresAdvanced, gameplay, repair, refuel and extraModules. (features is universal; featuresSimple and featuresAdvanced are the per-flight-mode profiles.) Admins and roles are not in this file — they live in permissions_admins_config.json, and any legacy admin block is migrated out and removed on first boot
  • HeliConfigs\<Classname>_Config.json — flight, altitude, aerodynamics, control (with a nested response block), autorotation, tailRotorFailure, damage (with nested zones and burn blocks), fuel, battery, audio, camera and sling
See Quick Start for a full walkthrough of the configuration system.

​
Already Purchased?

If you have already purchased and just need to whitelist a new or changed server IP, skip straight to step 3:

IP Whitelisting Channel

Whitelist your server IP via the CZ Autoz Bot

​
After Installation

  • Since v0.2.3, a mod update migrates your configs in place — new keys are added, removed keys cleaned up, and all your custom values are kept (originals are still backed up first to $profile:\CZAutoz_Heli\Backups\v<oldversion>_<date>\). Only when first moving from v0.2.2-or-earlier onto a v0.2.3+ build might a one-time re-apply be needed
  • Changes made in the in-game Admin Panel apply live — they update every spawned helicopter and connected player instantly, no restart or reconnect (since v0.2.3). Only direct edits to the JSON config files need a server restart, since those are read on startup
  • If anything isn’t working, see the Common Issues page
If helicopters appear in-game but controls are unresponsive or the mod behaves incorrectly, your server IP is most likely not whitelisted or the whitelisted IP doesn’t match your current server IP.