> ## 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.

# Setup & Installation

> How to install CZ Autoz / Callatic vehicles on your server — purchasing, whitelisting, installation and signing.

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.**

<Steps>
  <Step title="Join the CZ Autoz Discord">
    All purchasing and whitelisting is handled through the CZ Autoz Discord server.

    <Card title="Join the CZ Autoz Discord" icon="discord" href="https://discord.gg/7qWZzPUuTq">
      Click to join the CZ Autoz Discord server
    </Card>
  </Step>

  <Step title="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. Payment is via PayPal and your role is assigned **instantly and automatically** — no tickets, no waiting.

    <Note>
      **Packs, tiers and single vehicles are all self-serve**, and the bot handles the rest for you automatically:

      * **Just want one car?** Buy any individual vehicle on its own — no need to buy a whole pack.
      * **Upgrading later?** Already bought a single car and want the full pack or tier? Just buy it — the price is **automatically reduced** by what you already paid for those cars, so you only ever pay the difference.
      * **Running more servers?** Buy **extra IP whitelist slots** at any time (every customer starts with 4 live + 1 test slot).
    </Note>
  </Step>

  <Step title="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.

    <Card title="IP Whitelisting Channel" icon="shield-check" href="https://discord.com/channels/768275677480353824/1168185657672356011">
      Open the IP whitelisting channel in Discord
    </Card>

    <Note>
      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](/vehicles/whitelisting) page.
    </Note>
  </Step>

  <Step title="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.
  </Step>

  <Step title="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
    ```
  </Step>

  <Step title="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

    <Warning>
      **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.
    </Warning>

    Copy your `.bikey` into the server's `Keys\` folder:

    ```
    DayZServer\
    └── Keys\
        └── YourKeyName.bikey
    ```
  </Step>

  <Step title="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**.

    <Note>
      **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.
    </Note>

    <Check>
      **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.
    </Check>
  </Step>

  <Step title="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](/vehicles/overview#packs--tiers).

    <Note>
      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.
    </Note>
  </Step>

  <Step title="Start the server">
    Start your server. On a whitelisted server the vehicles spawn and drive normally. Check the dated log `$profile:\CZAutoz_Whitelist_YYYY-MM-DD.log` to confirm your whitelist status (see [Whitelisting](/vehicles/whitelisting)).
  </Step>
</Steps>

***

## Updating

Updating is drop-in: replace the PBOs with the new versions, re-sign, and re-publish your mod pack. Updates don't change classnames, so there are normally **no `types.xml` or server-config changes** on your side (any exception is always called out in the [Vehicles Changelog](/vehicles-changelog)). 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).

<Warning>
  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](/vehicles/common-issues).
</Warning>