Set up voice chat

Simple Voice Chat needs its own UDP port, separate from the port players connect to. Two steps get it running: install the plugin, then open the port.

Open the port

Go to Settings → Extra ports, pick the Voice preset (UDP, port 24454) and add it, then restart the server. The row that appears shows two numbers — the address your players' clients reach (yourserver.truetick.gg:27600 or similar) and the in-plugin port, 24454 — and, for a UDP row on this port specifically, a note reading wired into Simple Voice Chat's config once the plugin has created it.

That note means exactly what it says: wiring only happens once two things are both true.

• The row is UDP. A 24454 row added as TCP is never touched — that isn't the protocol Simple Voice Chat actually speaks, so a TCP row can't be what the setting means.
• Simple Voice Chat has already created its own config file. The plugin writes voicechat-server.properties itself, the first time it boots — not before. Until that file exists on your server there is nothing on disk for us to edit, so the start on which the plugin creates it for the first time writes nothing on our side; wiring begins on the start after that.

From that point on, every server start sets port, bind_address and voice_host in the file to values that match how the port is actually published. Every other setting in it — codec, recording, distance — stays yours; we never touch it.

Removing the UDP 24454 row hands those three keys back to you. The row is the whole trigger: with no such row on the server, we never open the file again, and whatever is in it at that moment stays exactly as it is.

If you had already edited those three keys yourself, we only correct a value that cannot work — a port that nothing published on your server forwards to, for example. If you deliberately pointed the plugin at a different UDP row of your own, we leave port as you set it and match voice_host to that row instead — the row is published, so we cannot tell that you got it wrong. One row is worth knowing about: with Bedrock crossplay on, the udp/19132 row belongs to Geyser and Simple Voice Chat cannot share it, so pointing the plugin at 19132 leaves voice silent and we will not correct that for you. A voice_host of your own with the right port is left as you wrote it, and so is bind_address left blank or set to 0.0.0.0.

Give players permission to talk

If you run LuckPerms (or any other permissions plugin), do this once — it is the single most common reason voice looks connected but nobody can be heard:

/lp group default permission set voicechat.speak true
/lp group default permission set voicechat.listen true
/lp group default permission set voicechat.groups true

Simple Voice Chat declares those permissions without a default, which a permissions plugin reads as "operators only". Until you grant them, ordinary players see You do not have permission to speak. Leave voicechat.admin to operators. If your players sit in a rank of your own rather than default, run the same three lines for that group.

We do not set these for you: it's your permissions plugin, not ours to write into.

Check that it really works

Open Console and look at the log after someone joins with the mod installed:

• successfully connected is the line to look for. It appears once a player's voice connection is actually up, and it is the line we read ourselves when we check whether a server's voice has ever worked.
• Received secret request and Sent secret are not proof. Those travel over the same TCP connection as the game itself, so they appear even when voice audio cannot get through at all — on one server we found 30 of them across its entire log history without a single successfully connected beside them.

If you only ever see the second pair, the audio path is not working — open a ticket and we will look at it with you.

Things worth knowing

• Bedrock players cannot use it. Simple Voice Chat's own FAQ answers “Does this work on Bedrock edition?” with “No. Only on Java Edition. It is impossible to implement a voice chat in Bedrock Edition due to technical limitations” (modrepo.de/minecraft/voicechat/faq, read 2026-08-21). Players who join your server through crossplay are on Bedrock, so voice chat is Java-side only.
• Everyone needs the mod. The plugin on the server is only one half — each player installs the Simple Voice Chat mod in their own client.
• On metered plans the voice port answers only while the server is awake. Voice traffic cannot wake a sleeping server, so join in Java first.