Overview
Welcome back
Your VoiceSniffer servers, what they flagged, and how much they sent to the cloud processor.
Passed Flagged
Your servers
Servers on the cloud processor
Every server paired to the processor, what it is running, and when it last said anything. If something here is not yours, retire it.
No server is connected to the cloud processor
The setup page pairs one in about a minute.
Retiring is how a seat comes back. It revokes that server's cloud token straight away, so the server stops being moderated the moment you confirm, and the seat goes back to the licence for another server to use. Its moderation history and its usage stay readable here. The same server can be connected again later from the setup page, under the same name, and it picks up where it left off.
Running the processor yourself instead? A server on the built-in engine or on your own processor never pairs, so it is not in this list and nothing it hears is ever sent to us. It checks in against your licence key instead, and those check-ins are on your Sniffer Studio account along with the key itself.
Moderation
Moderation history
Every utterance the cloud processor flagged on your servers, newest first, with what was said and which rule caught it.
What the server did about it is not here. The processor works out the verdict; the plugin decides whether a mute actually lands, seconds later and on your machine, depending on your severity mapping and whether the player was still connected. Nothing tells us the outcome yet, so this page shows the rule and the severity and says nothing about the action rather than printing a guess.
No audio, ever. Voice is decoded in memory for the length of one request and is never stored. What is kept is the text above, and only for speech that fired a rule.
Moderation
Usage
How much your servers have sent to the cloud processor, how much of it was flagged, and which server it came from.
Passed Flagged
Counts only. This page is built from a feed that carries numbers and nothing else: no words, no audio, no player. It is a separate feed from the moderation history on purpose, so that one cannot quietly grow a text field.
Only cloud servers appear here. A server running the built-in engine or your own processor never talks to us about what it heard, so there is nothing for us to count.
Moderation
Moderation settings
What each server listens for, what happens at each severity, what your players are told when they join, and where flags are posted.
These are set per server, on the setup page, and sent to the server itself. Nothing here is a file you have to edit and nothing needs a restart.
A running server takes up to 15 minutes to notice. The plugin asks the processor for its settings on a timer, so a save is not instant on a server that is already running. It is not lost either: the next fetch picks it up.
Your licence key is not a setting. If a key has leaked, ask on Discord and we will issue a new one and revoke the old. Neither this page nor the setup page can do it on its own, on purpose.
Service status
Service status
What the licence service can see about itself, right now.
This is the licence API reporting on itself. For the whole platform, including the website and the cloud processor, see the status page.
Help
Help and account
Fastest first.
This page is VoiceSniffer only. Everything about the account behind it lives on the dashboard, which is one sign-in for every product rather than one per host.
Why purchases are not ours to show. We do not take payments, so there is no card of yours for us to hold and no total for us to print. Your receipt and whatever refund rights come with it live with the marketplace you bought through.
Before you ask about a licence: have the masked key from the dashboard to hand, and say which server it is on. That is usually enough to find it.