Download Sentinel Enforcer

Sentinel Enforcer is the server-side mod that reports your server's activity to dayz.fyi. The Steam Workshop is the normal way to install it — subscribe and your servers stay up to date on their own. Use it if you can.

Sentinel Enforcer on Steam Workshop

The files below are the same signed build, for servers where the Workshop isn't an option: a Linux host with no Steam client on it, a control panel that only takes an uploaded zip, a firewalled machine, or a server you want pinned to one exact version. Each file has a SHA-256 checksum so you can confirm what you downloaded before you run it.

The trade-off: a Workshop subscription updates itself. A file you downloaded does not. If you install this way, updating is on you — come back here when you want a newer build, and keep the version number you installed written down somewhere.

Files

Version 0.38.3, published 2026-10-19. Take the complete bundle — the core mod and every add-on in one zip — or pick the individual files: the core mod plus an add-on for each third-party mod you actually run. An add-on folder that isn't on your launch line does nothing; a mod with no add-on is simply invisible to us — the server keeps running and everything else keeps reporting, so there's no error to notice.

Install

From your server's root directory — the folder holding DayZServer and keys/:

unzip SentinelEnforcer-0.38.3.zip
cp @SentinelEnforcer/keys/*.bikey keys/
-serverMod=@SentinelEnforcer

• unzip … — puts the @SentinelEnforcer folder where the server expects to find a mod. Repeat for each add-on zip you took — or unzip SentinelEnforcer-Complete-0.38.3.zip once instead, which puts the core mod and every add-on folder there in one go.
• cp …bikey keys/ — the mod is signed; the server checks that signature against the key in its own keys/ folder and refuses to load the mod without it. Every zip carries the same key, so copying it once is enough.
• -serverMod=@SentinelEnforcer — add this to your server's launch line. -serverMod=, not -mod=: this is server-only code, and -mod= would make the engine expect players to have it too. Add-ons go on the same line, separated by semicolons: -serverMod=@SentinelEnforcer;@SentinelEnforcer_Expansion.
• Only list an add-on if you run the mod it's for. Each add-on needs that mod in order to load: started without it, the server stops at boot on a “requires addon” message and waits for someone to dismiss it. An add-on folder that is on disk but not on the launch line is never loaded, which is why the complete bundle is safe to unzip whole.

Then follow the setup guide to paste your server's token into config.json and start it up.

Check what you downloaded

Put the zips and SHA256SUMS in the same folder, then:

sha256sum -c SHA256SUMS

Every file you downloaded should print OK. Add --ignore-missing if you only took some of them. On Windows:

Get-FileHash .\SentinelEnforcer-0.38.3.zip -Algorithm SHA256

…and compare the hash against the matching line in SHA256SUMS. A mismatch means the download was corrupted or altered in transit — delete it and fetch it again rather than installing it.

The checksum proves the file reached you intact. It's separate from the mod's own signature: the .bikey you copied into keys/ is what your DayZ server itself checks on every boot, and it will refuse to load a PBO that doesn't match.

Always fetching the newest

If you build server images or scripts, these URLs always point at the current release:

/downloads/sentinel-enforcer/latest.json
/downloads/sentinel-enforcer/latest/SHA256SUMS
/downloads/sentinel-enforcer/latest/SentinelEnforcer-Complete.zip

• latest.json — names the current version, so your script can print it or decide whether it already has that build.
• latest/… — redirects to that version's real file. Everything under a version number stays exactly as published and never changes, so once you know the version you can pin it and get identical bytes every time.

Full description of what the mod does, what it records, and how to configure it: the Sentinel Enforcer guide.