VoiceSniffer
How do you want to run it?
Two ways, and they are not a better and a worse. Pick the one that suits your server. You can change your mind later from this page.
Step 1 of 4
What you are agreeing to
Both documents in plain words, because a link nobody opened is not an instruction. Read them here, and read the full text if you want the wording.
Step 2 of 4
Connect your server
Start your Minecraft server, open its console, and paste the command below. This page notices the moment it lands.
This is what your usage and every flag is attributed to, and it is how you tell two servers apart in here later. Use 1 to 64 characters: letters, digits, dot, dash or underscore.
The code is good once, and only for the server that spends it. Nothing happens on this page until your server answers, so leave it open.
Asking for a code.
Retiring a server revokes its connection to the processor and gives its seat back. Pick the one you have finished with.
Nothing is connected on this account, so there is no seat to give back.
Step 3 of 4
Your server
The rest is up to you. The address and the credential are already done, so this is only what you want moderated and what happens when somebody is flagged.
These settings are saved to the one you pick here. Each connected server keeps its own.
Languages your players speak
What happens when someone is flagged
Severity comes from the rule that matched. Staff are always alerted; this decides what the player gets.
Telling your players
Required in many places, and the plugin will not start without a message. See how we handle data.
Step 4 of 4
Moderation is on
Your server is linked and the plugin knows where to send audio. Here is what it will do.
Come back here whenever you like. Change an answer, press Save, and your server picks it up on its own. You can switch to running the processor yourself at any point, which stops audio leaving your machine straight away.
Step 1 of 5
Where should the listening happen?
The only choice that really matters. Everything after this has a working default.
Step 2 of 5
Point the plugin at the processor
Authorises this server. Not your licence key. This one goes in
config.yml.
Only these are checked. Every extra one is another set of rules run over every sentence, and neighbouring languages collide: Czech speech checked against Polish rules will eventually mute somebody for an ordinary word.
Both are small enough to share your server's CPU, which is exactly why neither is accurate enough to rely on. There is no language setting: built-in is English only.
Nothing to configure here. The plugin will sit idle until you pick an engine.
Step 3 of 5
What happens when someone is flagged
Severity comes from the rule that matched. Staff are always alerted; this decides what the player gets.
seconds
seconds
seconds
Step 4 of 5
Telling your players
Required in many places, and the plugin will not start without a message. See how we handle data.
Every flag posts the player, the severity and what was said. Audio is never sent anywhere.
Step 5 of 5
Install the files
Three files into plugins/VoiceSniffer/. Put
license.yml in first and start the server once. The plugin writes the
other two itself, and only after your key is accepted.
- Drop
license.ymlintoplugins/VoiceSniffer/ - Start the server once, then stop it
- Replace the
config.ymlandadvanced.ymlit wrote with the ones on the right - Start again, and the console prints the mode it picked up