Introduction

Overview

AC-Mod-Pack brings together modules for customizing gameplay and administering DayZ servers. Its modular structure lets you combine features and adjust server behavior to suit your gameplay goals and community’s needs.

This documentation is intended for server owners and administrators. Each module page explains its options and, where applicable, the items, commands and permissions needed to use it.

Getting started

1. With the mod loaded on the server, locate the AC folder in the profile directory configured at startup.
2. Configure your Steam ID under Permissions to define administrative access.
3. Choose the module you want to use and check its configuration file, default values and requirements. Where m_Enable is available, use 1 to enable it and 0 to disable it.
4. If the module adds items to the server economy, consult Types and the XML on the corresponding module page to configure the mission’s types.xml.
5. Apply changes as instructed on the module page. Commands explains configuration reloads with /reload; the command requires command.reload or root.

File structure and activation methods may vary between modules. Check the corresponding page before copying settings from another feature.

Modules

Use the sidebar to explore the documented modules. Each page describes the feature, its available settings and, where applicable, item types, commands and permissions.

Some features depend on settings from other modules. Check the requirements and references on the page before enabling them.

See the list of public modules. For features offered separately, visit the private modules area.

Structure

The example below assumes a server installed in DayZServer, with its profile in profiles and a Chernarus mission. Names and paths may vary depending on your server’s startup configuration and mission.

DayZServer/
├─ @AC-Mod-Pack/
├─ mpmissions/
│  └─ dayzOffline.chernarusplus/
│     └─ storage_1/
│        └─ AC/
│           ├─ DayZ/
│           └─ Players/
└─ profiles/
   └─ AC/
      ├─ Logs/
      ├─ Modules/
      ├─ Settings/
      └─ Permissions.json

Profile directory

When this documentation refers to $profile:AC/, it means the AC folder inside the profile directory used by the server. In the example above, this corresponds to DayZServer/profiles/AC/.

Path	Purpose
$profile:AC/Settings/	Module configuration JSON files.
$profile:AC/Permissions.json	Groups, players and access permissions.
$profile:AC/Modules/	Persistent data saved by modules.
$profile:AC/Logs/	Records generated by modules that support logging, when enabled.

Mission data

The mod also saves persistence data in $mission:storage_<instanceId>/AC/, within the active mission. In this path, DayZ/ stores entity-related data and Players/ stores player-related data. storage_1 is just an example instance; use the folder corresponding to your server.

Configuration care

Files in Settings control module behavior; files in Modules and mission storage contain persistent data. Back up these files before replacing or removing them to preserve player progress.

When editing JSON, preserve option names, value types and file syntax. Enable and configure features gradually, checking the result on the server before making them available to players.

To follow changes between versions, see the changelog.