☀️ Summer Sale: get 10% off for life with code

Setting up Simple Voice Chat on your Minecraft server

Install and configure the Simple Voice Chat mod on a ServerPrism Minecraft server — step-by-step via the Mods, Console, Network and Files tabs.

Last updated July 16, 2026

Simple Voice Chat is a popular voice-chat mod for Minecraft, available on Modrinth and CurseForge. On a ServerPrism Minecraft server you can get it running in about 3 minutes from the panel — here's the full walkthrough using the dashboard tabs.

1. Install the mod on the server

Open your service in the panel and click Mods in the side menu.

  1. Search for Simple Voice Chat.
  2. Pick the build that matches your loader and Minecraft version (Fabric / Forge / NeoForge). For example, on Fabric 1.21.1 use the Fabric build for 1.21.1.
  3. Click Install — the panel drops the jar into /mods and marks it installed.

2. Restart the server

Switch to the Console tab and click Restart. Wait for the line:

Done (X.XXXs)! For help, type "help"

Simple Voice Chat generates its config files on this first boot.

3. Tell every player to install the matching client mod

This is the #1 reason people think the mod is broken: every player also needs Simple Voice Chat installed in their own Minecraft client. Without the client mod, the server mod silently does nothing for that player.

The client mod must match the server mod's loader, Minecraft version, and build number exactly. Modrinth: https://modrinth.com/mod/simple-voice-chat

4. Set the voice port to use your Minecraft port (important on ServerPrism)

By default Simple Voice Chat tries to listen on UDP port 24454, which is its own dedicated port. On ServerPrism your service is allocated a single public port (the same one you connect to in Minecraft) — so the default SVC port is not reachable from the internet, and clients will show a "voice chat not connected" icon (a plug with a red strike-through) even though everything else works.

The fix is one line of config. Open the Files tab and edit:

config/voicechat/voicechat-server.properties

Change the port line to:

port=-1

This tells SVC to bind to the same UDP port as Minecraft. Restart from the Console tab. The log should now read:

[voicechat] Voice chat server started at 0.0.0.0:<your-mc-port>

(SVC's own comment warns against port=-1 because it can clash with the Minecraft UDP query — but Paper has enable-query=false by default, so this is safe on ServerPrism unless you've explicitly turned query on.)

If you want voice on a separate port instead, go to the Network tab → Request Allocation, then set port=<new-port> (not -1) in the config.

5. Optional — tune the other settings (Files tab)

Same voicechat-server.properties file, useful knobs:

max_voice_distance=48            # max voice range in blocks (default 48)
codec=VOIP                        # VOIP for chatty servers, AUDIO for music/RP
max_voice_chat_connections=-1     # -1 = unlimited
allow_recording=false             # whether clients can record

Restart from the Console tab after any change.

6. Test it in-game

  1. Join the server with the client mod installed.
  2. Press V to open the voice-chat menu (default key — rebindable).
  3. The first time you connect, your client asks for microphone permission — allow it.
  4. You should see a small voice icon next to any other player's name who also has the mod and is in range.

Common issues

  • "Voice chat is disabled on this server" → mod isn't loaded server-side. Check the Console startup log for a voicechat banner; if it's missing, the jar is for the wrong loader or Minecraft version.
  • Plug-with-red-strike-through icon bottom-left → mod loaded but UDP can't reach the voice server. 99% of the time on ServerPrism this is the port-24454 default — see step 4.
  • "Voice not transmitting" → the other person probably doesn't have the client mod. Ask them to check their mods/ folder.
  • "Voice cutting out" → almost always a client-side UDP/firewall thing, not the server. Disabling VPNs and aggressive office/school firewalls usually fixes it.

If anything in the panel doesn't behave like described here, reply in a support ticket with a screenshot and we'll look.