Install GameLabs on a DayZ server and connect CFTools Cloud

By VYKIX

Updated 6 October 2026

Install GameLabs, add your CFTools Cloud server ID and API key to gamelabs.cfg, then check that Cloud receives new data from the correct server. A running DayZ process alone doesn’t confirm that GameLabs connected.

Use CFTools.Cloud’s GameLabs, Workshop item 2464526692, for Steam PC. This procedure uses the author’s 1.1395 source revision, commit 6d7e479, checked on 6 October 2026. Check the version reported in your startup log before using the troubleshooting details below. This is a source-based procedure; we haven’t run a player-join or Cloud-action test for this release.

Prepare the server and Cloud account

Register the intended DayZ server in CFTools Cloud. Its owner can obtain the server ID and API key under Manage → Settings → API Key. Keep both tied to that server. An RCON password or credentials from another server won’t substitute for them. See the author’s configuration instructions.

Check your Cloud edition’s available features before diagnosing a missing live map or action. Installing GameLabs doesn’t add a paid Cloud subscription.

Schedule maintenance, stop DayZ and save a recovery copy of the mission, persistence, profiles and launch settings. Keep any existing gamelabs.cfg and GameLabs-owned data with that copy. Treat API keys and reporting webhook URLs as secrets; redact them from screenshots and support logs.

Install the package with the required client files

In VXPanel Mods, search for 2464526692, check the linked author and choose Install for a client-visible binding. Review any listed dependencies before restarting. Players need the matching package for this client/server setup. The panel mod controls explain bindings and load order.

For a manual installation, follow the package and signing-key steps and add the installed GameLabs folder to your existing -mod= list. Preserve the other entries and avoid loading the same package twice.

The author requires client loading for Expansion chat transmission, in-game reporting and styled messages. If you want a server-only installation, confirm that the features you need support it before changing scope. Keep optional reporting and chat features off while establishing the basic connection. GameLabs feature requirements.

Edit gamelabs.cfg in the active profiles folder

Find the directory selected by the running instance’s -profiles argument. The file belongs directly inside it:

<active profiles directory>/gamelabs.cfg

In the checked source, GameLabs writes a template when the file is absent. Start the server once if you need that template, then stop it before editing. An Architect installation may already have created one. Avoid gamelabs.cfg.txt and don’t put the file inside @GameLabsStorage. Template and path in the author source, Architect’s configuration behavior.

Fill in serverId and apiKey in the generated JSON. Keep its other settings, use straight double quotes and save as UTF-8. Validate the JSON locally; don’t paste credentials into an online validator. Leave the author’s API endpoints unchanged.

Review connectionVerification before restarting. The checked source defaults it to true, while the author’s example sets it to 0. With verification enabled, rejected credentials can stop DayZ. Disabling it leaves authentication failures unresolved, so keep checking the log and Cloud data. Configuration defaults.

Check the connection and a normal player join

Start DayZ and inspect the GameLabs log under the active profiles directory’s @Logging folder. Confirm the reported version and server ID, then check Cloud for newly received data. Allow for your edition’s reporting interval. Join with a normal player account and confirm that the expected player appears on the intended Cloud server.

If you later enable reporting or styled messages, test that feature with its required client files. For a Cloud action that changes a character or object, use a disposable test account or object and check staff permissions first. Record the DayZ build, GameLabs version and other mods with the result.

When DayZ runs but GameLabs does not connect

For 1.1395, the author’s startup code distinguishes these cases:

Empty server ID or API key

Edit the active gamelabs.cfg and restart. The checked version leaves GameLabs disabled while DayZ runs.

Invalid credentials or wrong server

For INVALID CREDENTIALS or BAD SERVER CONFIGURATION, compare both credentials with the intended Cloud server. Don’t reuse another instance’s pair.

API unreachable

For GAMELABS API UNREACHABLE, check connectivity and CFTools service status. This revision retries transient startup failures; repeated restarts won’t repair an outage.

Outdated package

For GAMELABS OUTDATED, read the author’s release notes and update the installed package during maintenance.

Mod licensing error

Resolve the named mod’s authorization with its author. GameLabs can stop the server for this condition.

Server stays locked

Check lockServerOnStart; enabling it requires an unlock action.

If you must roll back, stop DayZ and restore the saved package, configuration and launch settings together; preserve the world and player data.