How to install ZomBerry Admin Tools and check admin access
Install CF and ZomBerry on the server and each connecting client, then locate the administrator file that the server loads. Use a restricted test instance to check that your account can open the menu and an ordinary player cannot.
Select Vaker’s ZomBerry Admin Tools, Workshop item 1582756848. These instructions cover Steam PC servers. Xbox and PlayStation cannot load this package. The public source and Workshop update reviewed here date to October 2022; the author edited the installation FAQ in June 2024. Check your installed DayZ release rather than treating those dates as compatibility evidence.
Review administrator access before production
Section titled “Review administrator access before production”In the author’s public configuration source, the normal startup path inserts a built-in administrator identity into the in-memory list. File generation writes a sample Steam64 identity to admins.cfg. These are separate entries: deleting the sample account from the file leaves the identity inserted by code. The server access method grants access when an identity appears in that list.
The finding applies to the pinned source revision. We have not inspected the current Workshop binary or tested the built-in identity. Your admins.cfg list does not establish exclusive administrator access in this source. Review the exact package before public deployment. For a server that requires exclusive access, leave deployment pending that review; the VPP and Community Online Tools procedures provide other permission setups to assess.
Check the launch arguments for -zbryInstallMode=true and -zbryGiveAdminRightsToEveryone=true. Both grant joining identities administrator access in the reviewed method. Remove those broad-access options from a public server’s setup. The restricted rehearsal below uses the administrator file without enabling them.
Prepare a stopped backup and install the packages
Section titled “Prepare a stopped backup and install the packages”With the service stopped, back up the mission, world save, profiles, packages, signing keys and launch arguments. Adding CF to an existing world requires planning for its author’s wipe requirement. Use separate test persistence for the rehearsal and retain the community’s original save.
In VXPanel’s Mods screen, search 1582756848. Check Vaker and the Steam link before choosing Install. Review Install all required mods for CF, item 1559212036, and keep both packages in the server-and-client scope. Follow the documented VXPanel mod controls for the installation.
For a manual installation, put each subscribed package in its server mod folder and its supplied .bikey files in keys. Leave signature checks enabled. These folder names produce the following entries in the full mod argument:
"-mod=@CF;@ZomBerry Admin Tools"Retain the entries for other required packages, using folder names that match the argument. Match CF and ZomBerry releases on clients and server. The author’s installation FAQ covers that loading scope and the profiles setup. Install the Workshop release; a loose source directory cannot substitute for its PBO package.
Find the loaded admins.cfg
Section titled “Find the loaded admins.cfg”Run the restricted test service to generate files, read its RPT/script logs, and stop it before editing. Resolve -profiles from the startup arguments used by that run. Another folder named profiles can belong to a different instance. Inspect the service through Files and SFTP and server logs.
Look for ZomBerry/admins.cfg inside the active profiles directory. In version 0.6.3, the author removed the bundled Config folder and added file generation at the profiles location. An absent bundled Config directory can be expected; it does not demonstrate a failed download. Author’s change notes
The pinned source checks these locations in this order:
| Source search order | File checked |
|---|---|
| 1 | admins.cfg in the resolved mission directory |
| 2 | ZomBerry/admins.cfg in the active profiles directory |
| 3 | admins.cfg in the server working directory |
| 4 | ZomBerry/Config/admins.cfg in the server working directory |
A mission copy takes precedence over the profiles copy in that lookup. Read the log entry beginning Server ready, loading admin list from: before changing a file. Back up the duplicates, identify the loaded path and reconcile the ZomBerry copies without changing another mod’s administrator files. Use the source lookup when a profiles edit appears to have no effect.
Grant the intended account and restart
Section titled “Grant the intended account and restart”Put each intended administrator’s Steam64 ID on its own line in the loaded admins.cfg. Enter the full decimal account ID without display names, commas, quotes or a JSON wrapper. Replace the generated example entries with your intended accounts. Check the full filename: it must be admins.cfg, rather than admins.cfg.txt.
Save, restart the service and reconnect the client. The source compares list entries with GetPlainId() and GetId(); Steam64 is the format in the author’s procedure. Confirm the new run loaded the intended file. An accepted ID receives administrator access to this tool. Establish the documented permission model before offering staff restricted roles.
Find admins.cfg loaded, its path and your expected account entry in the logs. Remove account identifiers from any excerpt you share. A successful file read confirms loading; use a player session to check menu and command access. That session does not resolve the built-in identity finding in the public source.
Open the menu and test a disposable item
Section titled “Open the menu and test a disposable item”Join the restricted instance with CF and ZomBerry loaded on the client. In game input settings, check the menu binding: the author specifies O, and the source preset binds UAZBerryOpenAdminMenu to kO. Older M instructions and a server-side MenuKey edit can misdirect the check. Resolve conflicting bindings in the client’s settings.
Check access with two accounts. The intended administrator should open the menu and use its functions; an ordinary account absent from your file should be denied. Record both outcomes. Denial for that ordinary account leaves the separate built-in identity question open.
Choose a disposable vanilla item under the spawn menu’s Safe filter. Check its class and position, then remove that specific item through the tool. Stop and start the service, reconnect, and repeat the access check. The author’s Expert list can include classes whose spawning causes script or client errors; list membership is not a successful spawn test.
Limit the first deletion to the disposable item. Record the target of any teleport, healing or god-mode action, then return the account to its normal state before testing ordinary gameplay. Perform those checks in the test world, away from the community’s saved objects.
Diagnose missing menus and configuration
Section titled “Diagnose missing menus and configuration”| Symptom | Check |
|---|---|
ZomBerry files and log entries are absent |
Inspect the server mod argument, folder names and CF loading. |
Unknown type 'CallType' |
Check that matching CF releases load on server and client. |
The package has no Config folder |
Check active profiles and the 0.6.3 file-generation change. |
| A profiles edit produces no change | Read the loaded-path log; check preceding mission and root copies. |
| Your administrator menu will not open | Check the loaded identity, restart, client releases and O binding. |
| A version-mismatch or PBO error appears | Compare loaded releases and signing keys using missing-PBO checks. |
| An ordinary account gets administrator access | Inspect broad-access arguments, file entries and the exact package’s access logic. |
File creation or read failures require a check of the service account’s directory permissions. Resolve the path in the writable active profiles directory while retaining the original backups. Wiping world persistence is not a menu-access diagnostic.
Remove access or roll back
Section titled “Remove access or roll back”Revoke a listed account with the service stopped: back up the loaded file, delete that entry, and restart. Reconnect with the revoked account to check that access is denied. The edit removes a file entry; built-in package identities remain unchanged.
Restore the saved administrator file, profiles and launch settings while the service is stopped. If rollback requires removing ZomBerry, follow mod removal and keep CF where another package requires it. Save logs from both the failed run and the restored run.