Getting started
Get your DayZ server onto dayz.fyi in three steps: add the server to your community here, install the Sentinel Enforcer mod, and paste the one token dayz.fyi gives you into the mod's config. The server connects already linked to your account — nothing to claim, no codes to fish out of logs.
Add the server to your community
- Log in with Discord and open your community page (create one from the dashboard if this is your first server).
- Hit Add server, give it a name, and Create.
You'll get a setup page with a token (a long
sntl_v1.… string) and a ready-to-paste config.json. Keep
that page open — the token is your server's credential and is only shown there.
Install the Sentinel Enforcer mod
Subscribe to Sentinel Enforcer on the Steam Workshop and add it to your server. It's a server-side mod (pure Enforce Script); players install nothing.
Sentinel Enforcer on Steam Workshop
- Load it with
-serverMod=@SentinelEnforcer(server-only code — use-serverMod=, not-mod=, so the engine doesn't try to client-load it).
Optional: add -doLogs -adminLog if you also want DayZ's own
admin log files — not required by Sentinel.
No Steam client on the host, or a control panel that only accepts an uploaded zip? Download the mod directly — same signed build, with SHA-256 checksums. The Workshop is still the better option where you have it: it keeps your servers up to date on their own, and a downloaded copy won't.
Verified on Windows dedicated servers. Linux should work too (no native dependencies) but hasn't been maintainer-tested yet — reports welcome. Running DayZ-Expansion or VPPAdminTools? See Optional add-on mods below.
Paste the token and start the server
Create <server profile>/SentinelEnforcer/config.json (in mod terms:
$profile:SentinelEnforcer\config.json) with the content from your setup
page (or set the BootstrapToken field if the file already exists), then
start the server. That's it — the setup page flips to Connected a
minute or two after the server finishes booting, and your server is live on
dayz.fyi.
The file lives in your server's profile directory, not inside the mod folder — so re-subscribing or moving the mod never loses your token.
See Managing your server next.
clm_…) in
<server profile>/SentinelEnforcer/claim.txt and the .RPT
log — paste that at dayz.fyi/claim instead. See
Claiming a server. Both paths end in the
same place; the token flow just skips the log-diving.
steamQueryPort in your serverDZ.cfg (DayZ's default is
27016) so dayz.fyi can read your server's broadcast title. Without it,
your server shows a placeholder name — just set it yourself under
Dashboard → your server → Edit settings. Running multiple servers
on one box? Give each a distinct steamQueryPort.
Optional add-on mods
The base Sentinel Enforcer captures core server events. If your server also runs one of these frameworks, add the matching companion mod alongside the base mod to capture that framework's events too. Subscribe only to the ones matching what your server runs — each does nothing on its own and requires the base mod first.
- Sentinel Enforcer · Expansion — for DayZ-Expansion (needs at least one of Market, Groups, Hardline, or Quests). Captures market buy/sell, group membership changes, reputation (hardline) changes, and quest completions.
- Sentinel Enforcer · VPPAdminTools
— for VPPAdminTools. Captures every admin action VPP logs
(teleport, give, kick, ban, base spawn, …) as an
admin.command_loggedevent. - Sentinel Enforcer · CodeLock — for Code Lock. Captures code-lock access attempts, so lock activity shows up on the Bases page and in the logs as a raid signal.
- Sentinel Enforcer · BreachingCharge — for BreachingCharge. Captures charges placed, detonated, and defused.
Running LBmaster? There is no add-on to install — the LBmaster
suite connects over a webhook instead, with no DayZ mod change at all. Generate it under
Settings → LBmaster (groups & bases, plus admin action logging if you run
AdminTools). The old @SentinelEnforcer_LBmaster add-on was retired in favour of it.
Add-ons load after the core mod and need no config of their own — they
register with the base mod at boot. Add each with -serverMod=
(server-only, same as the core), e.g.:
-serverMod=@SentinelEnforcer;@SentinelEnforcer_ExpansionEach add-on ships the same sentinel_enforcer.bikey
as the core, so copy whatever keys are in your subscribed mod folders into the
server's keys/ directory. Folder names are
@SentinelEnforcer_Expansion, @SentinelEnforcer_VPP,
@SentinelEnforcer_CodeLock, and @SentinelEnforcer_BreachingCharge.
⚠️ Only enable an add-on on a server that actually runs the matching mod. Each declares the third-party mod as a required add-on, and DayZ blocks startup with a dialog when a required add-on is missing — the server hangs at boot rather than starting without it.