How to configure DayZ Expansion global, party and vehicle chat

By Niko Catarino

Updated 5 October 2026

Install Expansion Chat for the Steam PC server and joining clients, then edit ChatSettings.json in the active profiles directory. Keep EnableExpansionChat separate from the global, party and transport channel switches. A usable party channel also needs Expansion Groups and a party membership.

Configure invitations and retained memberships through Groups guide, and native scheduled announcements through server messages. This guide configures text channels; enabling one does not create a group or alter voice transmission.

Install Chat and its dependencies

Use Expansion installation to prepare the test instance and recovery files. The original Chat item 2792982897 requires CF 1559212036, Dabs Framework 2545327648 and Core 2291785308. Apply their current migration instructions and keep the client files matched.

Use this argument for the manual folder names shown:

"-mod=@CF;@Dabs Framework;@DayZ-Expansion-Core;@DayZ-Expansion-Chat"

Retain required mods already in the load list and supply each signing key. In VXPanel, check Workshop IDs and Installed mods before starting the test. If Bundle is installed, configure its Chat feature without layering a duplicate individual Chat module over it.

Party messaging adds Groups and its required Book package to the client/server installation. The EnablePartyChat flag supplies no missing module. For transport chat, test a supported vehicle carrying multiple clients; a vanilla vehicle test does not establish a general requirement to add the Vehicles package.

Edit the active generated file

Locate the profiles directory from the service’s -profiles argument. The reviewed constants assign Chat settings to this file:

<active profiles>/ExpansionMod/Settings/ChatSettings.json

Let the isolated instance generate the file, then stop and save a recovery copy. The inspected schema is version 4. Preserve m_Version and fields outside your change. The release source adds EnableExpansionChat and BlacklistedWords beyond the fields documented in the author wiki. Its conversion from an older schema sets EnableExpansionChat from all three channel switches combined with AND. If any was disabled, inspect this interface flag after conversion before applying your intended channel policy.

Merge this settings patch into the generated file. It keeps party chat disabled for the initial test while enabling the interface, global chat and transport chat. Preserve fields omitted from this block:

{
  "EnableExpansionChat": 1,
  "EnableGlobalChat": 1,
  "EnablePartyChat": 0,
  "EnableTransportChat": 1
}

Save, restart and join with matched files. Read the selected channel and current DayZ/Expansion control bindings on the client. Custom presets and older tutorials can use different switch keys.

Test recipients before calling a channel private

The reviewed delivery code gives these channels different audiences:

Channel	Intended recipient set
Global	All connected players on the server
Party	Connected players belonging to the sender’s Expansion party
Transport	Crew sharing the sender’s supported vehicle
Direct	Players within the inspected whisper/talk/shout range
Admin	Player broadcast permitted by the sender’s permission check

Scroll to see all columns →

Use two party members and an outsider to check the audience. Send a harmless test identifier and inspect all three screens; the outsider should receive no party message. Repeat after a member leaves. A settings switch alone does not verify your installed combination’s recipient boundary.

Put two clients in one vehicle and the observer outside it or in another vehicle. Send transport messages, then repeat after a crew member exits. Inspect vehicle support, crew state, channel selection and the transport switch before changing network settings.

The inspected Direct delivery uses 9 metres for whisper, 30 for talk and 60 for shout. Use those source values to choose near/far tests, and record the client’s selected voice level. They do not prove distances in your installed release, and global delivery needs its own check.

Configure colors and a harmless filter test

ChatColors fields are strings. Eight hexadecimal digits without # express RRGGBBAA, with alpha last. The source converter converts that format to DayZ color values; it differs from the integer ARGB fields used by Name Tags.

Add this entry inside the existing ChatColors object without removing other colors. For a controlled filter test, add the harmless token to the current blacklist:

{
  "ChatColors": {
    "GlobalChatColor": "30B5FFFF"
  },
  "BlacklistedWords": [
    "trainingword"
  ]
}

The example is R=48, G=181, B=255, A=255. Read it against the actual chat background and client UI options. A single-channel change should preserve the generated system, admin, direct, transport and party colors.

The inspected server delivers *** for configured blacklist matches in Expansion messages. Try the harmless token, changed case, embedded text and the channels in use to establish the installed filter’s behavior. Remove the temporary token when finished. The example does not supply a complete moderation policy or replace staff review.

Check administrator permissions and log exposure

Sending through the inspected Admin channel requires Admin.Chat. Neither a message color nor a passwordAdmin login proves that permission belongs to the Expansion identity. Follow the administration tool’s permissions procedure for your installed administration tool, assign the intended staff role and compare an ordinary client with the administrator.

Admin chat broadcasts to players. Establish that audience before sending moderation notes. Party/transport restrictions describe player delivery; the server operator can still have access to logged messages.

With Chat logging enabled in Expansion log settings, the inspected code writes the original message text to both Expansion and admin logs, even when the delivered text is masked. Masking visible messages does not scrub the logs. Restrict access and keep credentials and private staff notes out of those channels; use harmless text when testing the filter and logs.

Diagnose a missing channel

Symptom	First check
Expansion UI missing	Match client/server packages and inspect generated EnableExpansionChat
Global send refused	Inspect EnableGlobalChat, active file and selected channel
Party channel missing or refused	Check Groups/Book, membership, EnablePartyChat and selected channel
Transport message absent	Confirm supported vehicle/crew, EnableTransportChat and recipient state
Admin send denied	Check the precise Expansion identity and its Admin.Chat permission
Log differs from filtered display	Original text is retained in the inspected log path
Color missing or altered	Inspect string format/alpha and the retained ChatColors object

Scroll to see all columns →

When only one client misses a message, inspect its mute/ignore and visibility options. Retain new session logs and repeat the smallest failing channel with fewer test mods. Saved Groups files do not need deletion to repair the chat interface.

Repeat the recipient tests after a stop/start. For a failed policy edit, stop, keep the failure logs and restore ChatSettings.json. Roll a package back with compatible dependencies and the saved-state recovery set as well.

Source and verification scope

This guide used AI-assisted research and drafting. The 3 October 2026 review covered the original listing, September release declarations and channel, permission and logging paths, plus JSON patches. No DayZ process was started. We have not compared the current package with that source or tested multiplayer audiences, installed filtering, client mute options or administrator behavior.