Reviews
Reviews are the anomalies dzbot found that a person still has to judge. The system can tell you that two accounts share a browser, or that somebody linked a Discord account created last week — it cannot tell you whether that is a cheat, a household, or a coincidence. That decision is yours, and this page keeps it.
Navigation path:
Server Admin→Reviews
Access requirements
| Right | What it unlocks |
|---|---|
admin.reviews.view | See the reviews that touch this server |
admin.reviews.decide | Work the queue: take a case, add a note, link tickets, resolve it |
A review belongs to the organization, not to one server: it is about people, and two servers must never reach two different verdicts about the same people. You see the reviews where at least one of the accounts plays on your server, and the decision you record settles the matter everywhere.
What produces a review
Multi-account
Two or more registered accounts share a game device, a browser profile or an address. Evidence with only one registered account behind it never becomes a review — a single account cannot be somebody's second one, so a console shared by one player and four unclaimed in-game names is not a finding, it is a console.
Fresh account
Somebody linked a Discord account that was created shortly before. This is the check many teams run by hand against ban evasion: a banned player comes back with a new Discord account, links it, and carries on. The account's age comes from the Discord id itself, so it is exact and needs no lookup.
Working the queue
The list is a queue: one line per case, showing what it is, who is on it and how old it is. Opening one gives you the whole case in a panel — and its own address, so a review can be linked to from a ticket, from Discord or from a colleague.
There it shows the accounts involved with their Discord identity, what links them, and how crowded that evidence is. Selecting an account opens their page on this server, where their playtime, bans, notes and balance are. An account that belongs to the review but does not play here is marked as such and leads to their organization page instead.
Taking a case
Several people work this queue, so a case can be taken. Taking one marks it in progress under your name, and everyone else sees at a glance that it is being handled. Hand it back and it returns to the queue; take over and the history records that too. You can also set in progress or open by hand, for a case that is waiting on an answer rather than on you.
The queue shows open and in-progress cases together — taking a review must not make it disappear from the list you took it in. Unclaimed cases sort first, oldest first within that.
When a decided review reopens, its owner is cleared. Whoever settled it decided a smaller case than the one now in front of you, and a reopened case with somebody's name still on it looks handled.
Tickets
A review can produce tickets, and the link holds in both directions: the review lists them, and each ticket names the case it came from. Create one straight from the review — leave the player out and it stays internal, which is what an alt-account check usually needs to be. Existing tickets can be attached from the ticket's own page.
A ticket on another server of your organization stays visible but is not clickable from here, and a ticket in a support level you cannot see keeps its number and withholds the rest.
Resolving
A review is closed with a note, and the note is required — it is the entire record of the outcome. Write what you checked and what happened: "Brüder, gleiche Wohnung, geduldet", "gebannt, hat sich nicht gemeldet", "Ticket #412 geklärt, nichts dran".
There is deliberately no list of verdicts to pick from. An earlier version offered three per type, which assumed the reviewer already knew the answer at the moment they looked — in practice they open a ticket or ban precautionarily and only learn it later. And a growing catalogue of review types would each need its own vocabulary, with "confirmed / not confirmed" fitting almost none of them.
Everything that happens to a review — opened, taken, ticket linked, resolved, reopened — stays in its history, including resolutions that were later superseded. Resolving an already-closed review is allowed and adds a new entry rather than overwriting the old one.
When a review comes back
A decided review reopens only when an account joins it that you had not seen when you decided. The same evidence turning up again does not reopen anything, and neither does more of it about the same people — you already looked at those.
When it does reopen, the new account is marked, so you can see what changed instead of reading the whole case again.
Automating around reviews
Opening and reopening a review writes a review_opened log event, which means Actions
can react to it: ban automatically on a strong match, post to a Discord channel, whatever your team
needs. One event covers both cases — reason is created or reopened — so a single action covers
"somebody has to look at this".
Each account in the event carries is_new, so an action can act on just the account that caused a
reopening rather than the whole group that was cleared last week.
An action can also open a ticket and attach it to the review that triggered it, so automatic work lands in the same place as the manual kind:
server.create_ticket(
"Check alt account: " .. data.accounts[1].username,
"Review " .. data.review_id .. " opened (" .. data.reason .. "). " .. data.url,
nil,
data.review_id
);
If the review has since merged into another one and its id no longer exists, the ticket is still created and the action carries on — only the link is skipped, with a note in the action log.
Settings
Under Organization → General you can configure which matches produce a review, and how young a
Discord account has to be to trigger the fresh-account check (90 days by default; 0 switches it off).
Only browser matches open a review by default.
Device matches are off because DayZ no longer reports a hardware id: every device link in the data was entered by a moderator who had already worked out that the accounts belong together, so a review would hand you your own conclusion back. Switch it on if automatic device detection returns.
IP matches are off for a different reason — about half of all matches and almost never a finding, since flatshares, families and mobile networks all share addresses.
Where else reviews appear
A player's own page shows the reviews they are part of, in the moderation timeline next to notes and restrictions. That is usually where you meet one: while deciding something else about that player.