DayZ FriendConsole focused management
en
Server Files

init.c on console servers

Published 10/29/2026Updated 10/29/2026

Can init.c run on a DayZ console server? This guide explains the mission-file limitation and what console server owners can configure instead.

Looking for DayZ console bot setup guides?

See our feature pages for DayZ auto ban, and DayZ economy bot.

init.c on console servers

init.c is a mission script, not a Central Economy data file. It contains Enforce Script code that starts the mission and can provide a CustomMission class. The supplied vanilla missions show this directly: each dayzOffline mission has an init.c at the mission root, with a main() function, a CustomMission : MissionServer class and CreateCustomMission().

Can I put it in custom?

No supported loader is shown for that on console servers.

The custom folder can be registered through cfgeconomycore.xml for supported Central Economy XML files such as types.xml, events.xml and cfgspawnabletypes.xml. That registration does not compile or execute .c script files.

mission/
├── init.c                 ← mission script entry point
├── cfgeconomycore.xml     ← Central Economy registration
└── custom/
    ├── types.xml          ← supported CE data file
    ├── events.xml         ← supported CE data file
    └── init.c             ← not loaded by cfgeconomycore.xml

Adding custom/init.c, or trying to register it as a <ce><file> entry, will not make its code run. cfgeconomycore.xml expects supported CE file types; it is not a general-purpose script loader.

Where does vanilla init.c run?

The supplied mission files place it at the root of the mission folder:

dayzOffline.nasdara/
├── init.c
├── cfgeconomycore.xml
└── ce/
    └── ...

The file is part of the mission script contract. In the supplied examples, main() creates and initializes the offline Hive, while CreateCustomMission() returns the mission's custom mission object. The Nasdara example also changes starting equipment and player starting stats inside StartingEquipSetup(); that is script behaviour, not an XML or JSON setting.

What would be needed to change it?

The server platform must expose and load mission scripts, and must accept the edited init.c at the mission entry-point location. The supplied console configuration files do not expose a script compiler, a custom script-folder registration, or a supported init.c include/import setting.

That means a console mission edit can use the supported XML and JSON loaders, but it cannot add new script behaviour such as custom callbacks, new commands or code-driven spawn logic. A PC server or mod-capable deployment may support mission-script changes, but the exact deployment mechanism is outside the supplied console configuration material and should not be assumed from cfgeconomycore.xml.

What can be done from custom instead?

Use cfgeconomycore.xml to register supported CE XML files, then keep those files under the registered mission folder:

<economycore>
    <ce  folder="custom">
        <file  name="types.xml"  type="types" />
        <file  name="events.xml"  type="events" />
        <file  name="cfgspawnabletypes.xml"  type="spawnabletypes" />
    </ce>
</economycore>

Use the supported mission JSON files for settings they actually provide, such as cfggameplay.json, cfgeffectarea.json, object-spawner data and spawn-gear presets where the relevant loader and mission reference are available. These files can change exposed configuration data; they cannot turn a custom .c file into an executable mission script.

Bottom line

Based on the supplied files, there is no console-side switch that enables custom/init.c. The reliable rule is:

  • CE XML in a registered mission folder: supported when the host exposes the file and the loader supports its type.
  • Mission JSON: supported when the corresponding loader is enabled and the file is referenced or discovered as documented.
  • init.c or other Enforce Script: requires a platform that actually loads mission scripts; placing it in custom is not enough.

Editable on console: XML and JSON only where the host exposes the matching mission file and the vanilla loader consumes it. init.c is not enabled by cfgeconomycore.xml.

Console Bot Quick Links

Explore DayZ console-focused pages for PlayStation, Xbox and Switch 2 server owners:

Attachments

(0)
No attachments for this page yet.