Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.czautoz.co.uk/llms.txt

Use this file to discover all available pages before exploring further.

The process is the same for a pack, a tier, or a single-vehicle mod — install the PBOs, sign them, and whitelist your server IP. Community Framework is not required.
1

Join the CZ Autoz Discord

All purchasing and whitelisting is handled through the CZ Autoz Discord server.

Join the CZ Autoz Discord

Click to join the CZ Autoz Discord server
2

Purchase your pack, tier or vehicle

In the Discord, head to the purchase channel and follow the bot’s instructions to buy the pack, tier, or single vehicle you want.
3

Whitelist your server IP

Use the CZ Autoz Bot in the #ip-whitelisting channel to register your server’s public IP address. On a non-whitelisted server the vehicles spawn but the engine will not start. Each CZ Autoz vehicle mod (and the helicopter mod) has its own whitelist — whitelist each one you run, or use the bot’s submit-all to do everything you own at once.

IP Whitelisting Channel

Open the IP whitelisting channel in Discord
Submit your server’s public IP, not your home/local IP. If your server IP changes (e.g. you switch hosts), return here and re-whitelist. Full details on the Whitelisting page.
4

Download the PBOs

Download the mod from the CZ Autoz Discord. Each vehicle mod ships 2 PBO files:
  • <Name>_Scripts.pbo — client and server scripts
  • <Name>.pbo — vehicle assets (models, configs, textures)
A pack/tier ships its pack PBO + scripts PBO; a single-vehicle mod ships that vehicle’s two PBOs.
5

Add the PBOs to your server mod pack

Copy both PBO files into the Addons\ folder of your server mod pack:
@YourModPack\
└── Addons\
    ├── <Name>_Scripts.pbo
    └── <Name>.pbo
6

Sign the PBOs

DayZ servers require PBOs to be signed. Use DS Utils to sign both PBOs with your server’s private key.
  1. Open DS Utils
  2. Load your .biprivatekey
  3. Sign both PBOs — this generates a .bisign alongside each
Never share your .biprivatekey. Anyone with it can sign PBOs as you. Your .bikey (public key) is safe to distribute — it’s what verifies signatures.
Copy your .bikey into the server’s Keys\ folder:
DayZServer\
└── Keys\
    └── YourKeyName.bikey
7

Publish your mod pack to Steam Workshop

Use DayZ Tools → Publisher to upload/update your @YourModPack to the Steam Workshop, then load it on both client and server.
Brand-new Workshop upload? Run a second update immediately after the first publish to generate the Workshop Publisher ID — without it the mod may not load correctly across clients and servers.
No Community Framework needed. Unlike some vehicle mods, these do not require @CF. All other integrations (DayZ Expansion, MuchCarKey, TraderPlus CarLock, VPP Admin Tools) remain optional and auto-detected.
8

Add the vehicles to your economy

Add the vehicle classnames (and their wheels/doors) to your types.xml so they spawn, or place them via your trader / events. The exact classnames for each vehicle are on its pack/tier page.
The vehicles use vanilla car parts (car battery, spark plug, radiator), so no special battery/part items are required — only the vehicle’s own classnames, wheels and doors.
9

Start the server

Start your server. On a whitelisted server the vehicles spawn and drive normally. Check $profile:\CZAutoz_Whitelist.log to confirm your whitelist status (see Whitelisting).

​
Updating

Updating is drop-in: replace the PBOs with the new versions, re-sign, and re-publish your mod pack. There are no config or types.xml changes required by the DayZ 1.29 release. Each vehicle mod has its own whitelist, so make sure every pack, tier and single-vehicle mod you run is whitelisted (submit-all covers everything you own at once).
If a vehicle appears in-game but the engine won’t start, your server IP is almost certainly not whitelisted (or the whitelisted IP no longer matches your current server IP). See Common Issues.