Checking Your Sentinel Setup

dayz.fyi only knows what your server tells it. When a feature on your server's page is empty, there are two very different explanations: nothing happened, or we weren't told. This page is how you tell them apart, and how to fix the second one.

If you arrived here from the chip at the top right of a server page, start with the section that matches what the chip said.

The chip and what it means

The chip only appears when something needs your attention. No chip means the server is reporting and none of the checks the chip knows about found a problem. It isn't a guarantee that every feature has data.

• Not reporting. We haven't heard from the server recently. Nothing new is arriving: live players, the map, logs, alerts and reports all stop at the moment it went quiet. See The server isn't reporting.
• Data incomplete. The server is reporting, but something a feature needs is switched off, so that feature is missing information. The chip lists which features. See Something is switched off.
• Data status unknown. The server is reporting, but hasn't told us how some of its settings are configured. Those features may or may not be working. See Settings we couldn't confirm.

Every staff member who can open the server's pages sees the chip and the list of affected features. Owners and co-owners also see which setting is responsible, where to change it, and whose Sentinel account the server belongs to, because they're the ones who can fix it. If you're staff and the chip appears, tell an owner. Some features are only visible to owners, so owners can see items on the list that staff don't.

Whatever the chip says, the rule for staff is the same: an empty list on an affected feature means "we don't know", not "nothing happened". Don't clear a player, close a ticket or conclude a base wasn't touched on the strength of missing data.

The server isn't reporting

This is almost always a problem on the server itself, so it needs whoever runs the server box. Check, in order:

1. Is the server actually running and joinable? A server that's down or stuck restarting can't report. If it's been restarting over and over, the Health page will usually say so too.
2. Is Sentinel still loaded? Your launch parameters must include -serverMod=@SentinelEnforcer. A host panel update or a copied launch line sometimes drops it.
3. Does the server log show Sentinel starting? Open the newest script log (the .RPT file in your server's profile folder) and search for [Sentinel]. At every boot Sentinel prints a [Sentinel] chain-links: line. If there are no [Sentinel] lines at all, the mod didn't load.
4. Is the server still linked to your account? Sentinel's settings live in <server profile>/SentinelEnforcer/config.json. After the server is linked, that file holds the server's own ServerId and ApiKey. If the file was deleted, reset, or replaced with a copy from another server, the server can no longer report as itself. A claim.txt file appearing in the same folder is a sign it has started over as a brand-new, unlinked server.

If the server is running, Sentinel is loaded and the log shows nothing obviously wrong, ask in the dayz.fyi Discord (link in the site footer) with the server's name and roughly when it stopped reporting. Don't re-install or claim the server again before asking: that can create a second server entry instead of fixing the first.

Something is switched off

Sentinel's capture is controlled in two places, and the chip tells owners and co-owners which one applies to each feature.

1. Your own config.json switches (whoever runs the server files). The Hook... settings in <server profile>/SentinelEnforcer/config.json turn whole parts of Sentinel on or off for the server, for example HookStructureSweep (base part positions) or HookItemMoved (item moves between players and containers). They're on by default. A false here is final: nothing on any dashboard can switch it back on, by design, so only someone with access to the server's files can change it. The [Sentinel] chain-links: line in your server log lists every switch with its current ON / OFF state, which is the quickest way to check what the server actually loaded. Changes take effect at the next restart.

The full list of switches, what each one does and what it costs your server is on the Sentinel Enforcer description.

2. Per-server capture settings on the Sentinel dashboard. Individual kinds of data (kills, chat, item pickups and so on) can also be switched off per server on the Sentinel dashboard, on the server's configuration page. That page is for your organisation's Sentinel admins. A server's Sentinel settings sit with the Sentinel account of whoever added the server, so in a community with co-owners that may be a different owner from you: the chip tells owners whose account it is. If you don't have a Sentinel dashboard login, ask that owner, or ask in the dayz.fyi Discord and we'll check the settings with you. These changes reach the server within a few minutes and don't need a restart.

Switched off on purpose? That's fine. Some communities turn things off to save server resources or because they don't use a feature. The chip isn't telling you it's wrong, only that the matching features won't have data, so staff don't read an empty page as "nothing happened".

Off by default. A few kinds of data are off on every server unless you turn them on, for example the full history of item moves inside a single player's own inventory. These never make the chip appear. Owners and co-owners see them listed under "Also available" when they open the chip.

Settings we couldn't confirm

"Unknown" means the server hasn't told us how a setting is configured. We never assume it's on. The usual causes:

• An older Sentinel build. Update the mod (a Workshop subscription keeps it current on its own) and restart the server.
• The server hasn't restarted since a setting was added. Settings are reported when the server boots, so a restart clears this.
• We couldn't read the server's settings for a while. If the server is otherwise reporting, this usually clears within a few minutes.

If it doesn't clear after a restart on the current build, ask in the dayz.fyi Discord.

Add-ons and integrations

Some features depend on a community mod your server runs, and need a matching piece on the Sentinel side as well:

The chip does not check LBmaster webhooks yet. If you run LBmaster mods, owners should check the Ops -> Integrations -> LBmaster card themselves.

Add-ons install the same way as the main mod: subscribe, copy the folder into the server root, copy its key into keys/, and add it to -serverMod= next to @SentinelEnforcer. Only install the add-ons for mods you actually run. If your server doesn't run Code Lock, for example, there's no code lock data to miss.

Traps

• "The page is empty, so nothing happened." Only possibly, and only if the chip is absent or the affected feature isn't on its list. An absent chip means the checks it knows about found no problem, not that every feature has data. If the feature is on the list, the page is empty because the data isn't being collected.
• "It worked last week." A restart onto a new launch line, a host migration or a reset config.json can silently change what a server reports. Look at what the chip says today.
• "The Health dot is green, so the data is complete." The Health dot is about server performance. The chip is about which data is being collected. They answer different questions.
• Reinstalling to fix a quiet server. Reinstalling or claiming the server again can register it as a second, separate server. Ask first.