Detections, review and enforcement
What is collected, what the detectors look for and where they can be wrong, how your team reviews a finding, what automatic punishment may and may not do, and how a case restricts a player.
Read this first. No detector here has a measured false-positive rate yet. Automatic punishment is on for every new game (you can switch it off), and it is capped per detector: today at most a temporary suspension, and only the speed detector with strong evidence reaches that. No detector can ban automatically.
Separate stages
| Stage | Who or what does it | What it can do |
|---|---|---|
| Collection | Your game server and the session service | Store an event from the list below. Nothing else. |
| Detection | A versioned rule, while Automatic detection (Highly recommended) is on | Create a finding with a reason, severity, evidence strength (0-100, from the rule's own margins; not a measured probability) and the thresholds it used. |
| Automatic punishment | Only while Automatic punishment (Highly recommended) is on | Automatically applies your configured penalties to verified cheating detections. Uncertain cases are sent for review. Each detector has a ceiling (below); settings are read at the moment of acting. |
| Review | A member with the review permission | Confirm, dismiss or reopen a finding, with a written reason. Dismissing a finding automatic punishment acted on reverses its case (owner or admin). |
| Case | An owner or admin, or automatic punishment | Remove the player from their session, or suspend or ban the account together with the identifiers the game's identifier level covers (below). Always reversible. |
Pausing automatic detection stops new findings only: events are still stored, and authentication, admission and existing restrictions continue.
Billing states, platform requirements and build checks are admission results. They are never events, never findings and never a reason for a restriction.
Events collected
This is the complete list. Fields not named here are discarded on receipt.
| Event | Reported by | Meaning | Fields |
|---|---|---|---|
movement.rejected |
Your game server | Your game server rejected a move because it exceeded the speed your rules allow. | measured: Distance the client tried to move, in your game's units.allowed: Distance your rules allowed at that moment. |
rate.rejected |
Your game server | Your game server rejected an action performed faster than its cooldown allows. | action: Your name for the action, for example "fire" (up to 32 letters, digits, dots, dashes or underscores). |
session.signature_invalid |
The session service | A request made in this session's name was not signed with the session's key. | none |
session.replayed_request |
The session service | A correctly signed request for this session reused a sequence number. | none |
join.token_reused |
The session service | A join token of this session was presented to your game server again after it had been redeemed. | none |
join.player_mismatch |
The session service | A join token of this session was presented for a different player than the one it was verified for. | none |
Nothing is read from a player's PC for these events: no files, processes, windows or input. Each session stores at most 2000 events, and each game can switch reports and detections off under Features.
Reporting from your game server
curl https://obscurity.ac/api/v1/sessions/ps_.../events \
-H "Authorization: Bearer obs_sk_your_key_here" \
-H "Content-Type: application/json" \
-d '{"events": [{"type": "movement.rejected", "data": {"measured": 21.4, "allowed": 6.9}}]}'
Reject the action on your server first; that is what protects the game. Then report it. Up to 100 events per call. The answer lists any detections for the session, for your logs: do not remove a player because one appeared.
Detectors
Sustained movement above the speed limit speed.sustained v1
Many rejected moves close together, most of them well beyond what the rules allowed.
| Reads | movement.rejected |
| Fires when | window_seconds = 60, min_events = 8, min_strong_events = 5, min_ratio = 1.5 |
| Can be wrong when | Depends entirely on the limits your game server applies: a limit set too low, a server-side teleport that was not registered with the validator, or severe packet loss followed by a burst can all produce rejected moves from an honest player. It sees only what your server rejected, so it cannot notice speed changes your server accepts. |
| Automatic ceiling | Temporary account suspension with evidence strength 80 or more; one step lower below that |
Sustained actions faster than a cooldown rate.sustained v1
The same action rejected for breaking its cooldown many times in a short period.
| Reads | rate.rejected |
| Fires when | window_seconds = 30, min_events = 15 |
| Can be wrong when | Key-repeat, macros your game permits, or a cooldown shorter on the client than on the server can produce bursts of rejected actions without any cheating. It cannot tell an automated input device from fast hands. |
| Automatic ceiling | Remove from the session |
Requests forged or replayed in a session's name session.forgery_attempts v1
Repeated requests for one session that were not signed with its key, or that reused a sequence number.
| Reads | session.signature_invalid, session.replayed_request |
| Fires when | min_invalid_signatures = 5, min_replays = 5 |
| Can be wrong when | This shows that someone tried to speak for the session. It does not show who: it can be a third party attacking the player, a broken proxy repeating requests, or a modified client. It is not, by itself, evidence against the player. |
| Automatic ceiling | Review only |
Join token passed between accounts or reused join.token_misuse v1
A session's join token was presented for a different player, or presented again several times after use.
| Reads | join.player_mismatch, join.token_reused |
| Fires when | min_player_mismatches = 1, min_token_reuses = 3 |
| Can be wrong when | A game server that retries its own verification call, or a bug that sends the wrong account's token, produces the same signal. Check your integration before drawing conclusions about the player. |
| Automatic ceiling | Review only |
A rule that changes gets a new version number, and every detection records the version and thresholds that produced it. Once a detection has been reviewed its evidence is frozen, so the record shows what the reviewer saw.
Review
- Open a game's Detections page. Each finding shows the events behind it, the session it came from and where its detector can be wrong.
- Confirm or dismiss it with a note saying what you looked at. A judgement can be reopened.
- Confirming restricts nobody. It records that a person agrees the evidence shows what the detector describes.
Cases
- One case per decision. Opening it associates every identifier seen in that player's verified sessions of this game in the last 30 days, restricts the ones the case calls for, ends the player's running sessions and spends their unused join tokens. Each step and its result is recorded on the case.
- The account restriction applies when your game server verifies the player:
POST /api/v1/sessions/verifyanswers"valid": false, "code": "player_restricted". - Platform accounts your server verified (send
platform_accountswith the verify call) follow the player: a new game account signing in with a restricted Steam account is refused the same way. - Device and network restrictions apply when a session starts: the client is told
device_restricted. An attested TPM, a platform account or a network address restricts on its own. Hardware identifiers the PC reports restrict only when two different kinds match; one match is logged for your review. - Each game has one identifier level for account and PC identifiers, used by automatic punishment and as the default for your team's cases. There is no switch per identifier:
- Low. The game account, the platform accounts your server verified, and the PC's TPM where platform verification proved it. Enough for most games, with almost no risk of catching the wrong person.
- Normal. Low, plus the PC itself: the installation and the hardware identifiers the SDK reports. Stops most players from returning on a new account from the same PC.
- IP bans have their own switch, off until you turn it on. A suspension or ban also restricts the network addresses the player used in the last 30 days (IPv6 as its /64), for the number of days you choose, at most 30. Addresses shared with more than two other players are skipped, but someone else behind the same address, such as a housemate, may be refused for that time. Your team can include or leave out IP bans on each case it opens.
- Anti-VPN is a feature switch, off until you turn it on. It refuses sessions from VPNs, proxies, Tor exits and hosting providers with
vpn_not_allowed, a compatibility result that tells the player to disconnect and try again; it is not a finding about the player. The address is checked on our servers against Obscurity's own list and is not sent to anyone else. In Monitor mode a match is recorded and the player is admitted. - At every level, a device seen with other players (a shared PC) is listed for review instead of restricted, and a network address seen with more than two other players is skipped.
- The player is told the developer took action and that the decision can be reviewed and reversed. Give them a way to reach you.
- Reversing a case lifts exactly what rested on it; restrictions another case justifies stay. A faulty detector release: reverse all its automatic cases at once from the game page.
- A case belongs to one game of one studio. Identifiers are stored as keyed hashes that differ per game. Nothing is shared with other studios unless the game takes part in the Global Ban Network (below).
Global Ban Network optional add-on, $20 per game per month, in development
Restrict access for players with an active, verified cheating ban from another participating Obscurity-protected game. A game takes part when the add-on is on its subscription (Plan and billing) and the Global Ban Network switch is on (the game's page, on by default). The switch never charges anything; the add-on stops with the game's subscription.
- What is shared, automatically. Every ban or suspension: the ones your team opens on a confirmed detection and the ones automatic punishment opens (unless someone dismisses the finding). Session removals are never shared. The switch is on for every new game and takes effect once the add-on is paid.
- Turning it off. Switch the network off for the whole game, tick "Don't share this ban" when you restrict a player, or press "Stop sharing" on a case. The ban in your own game stays.
- Unbanning removes it. Lifting the player's account restriction, reversing the case, dismissing the finding or the ban expiring removes it from the network at once. Lifting only a platform account or TPM restriction removes that identifier from it.
- Validation. A submission does nothing anywhere until Obscurity staff validate it. Each studio may submit up to 50 cases a day, and how often a studio's submissions are rejected or reversed is monitored.
- What links games. Only platform accounts your game server verified (
platform_accountsin the verify call) and TPMs proven in platform verification, and only the ones the original case actually restricted. Hardware the PC reports, installations, network addresses and your own player IDs never link games. The value that links them is a keyed hash kept only while a game takes part. - Receiving. A matching player is refused with
"code": "network_restricted"at verification, when platform verification finishes, or at the next heartbeat of a running session. A match through a TPM other players of your game also used is not refused: it is listed on the game page for review. - Correcting. Reversing the original case, or its expiry, ends the shared ban everywhere at once. You can allow a shared ban in your own game (after an appeal, for example); that changes nothing elsewhere. Switching the network off stops all checks immediately.
- What studios see. A receiving studio sees that a shared ban exists, its kind and its dates, never the game or studio it came from or that studio's evidence. A shared ban never becomes a case in the receiving game, so it is never shared again.
Retention
Events and detections are deleted with their session after the evidence-retention period of the game's tier, except while a restriction that rests on them is in force: a decision about a player has to stay reviewable. A restriction record is deleted a year after it ends.