Set up Simple Voice Chat (proximity voice)

What is Simple Voice Chat?

Simple Voice Chat is a mod/plugin that adds proximity voice chat to Minecraft. Players hear each other based on distance: closer = louder, farther = quieter. It also supports voice groups, whispering, and audio recording.

It's compatible with Fabric, NeoForge, Forge, Quilt (as a mod) and Bukkit/Spigot/Paper (as a plugin). Players need the mod installed on their client to use it.

Requirements

• Server running Paper/Spigot/Purpur (plugin) or Fabric/Forge/NeoForge (mod)
• An additional UDP port open (default 24454)
• Players must have the mod installed on their client (Fabric, NeoForge, Forge or Quilt)

Step 1: Install on the server

As a plugin (Paper/Spigot/Purpur)

1. Download Simple Voice Chat from modrinth.com/plugin/simple-voice-chat
2. Upload the .jar to plugins/ on panel.baires.host
3. Restart the server

Config file location: plugins/voicechat/voicechat-server.properties

As a mod (Fabric/NeoForge/Forge)

1. Download the version matching your loader from modrinth.com/mod/simple-voice-chat
2. Upload the .jar to mods/ on panel.baires.host
3. Restart the server

Config file location: config/voicechat/voicechat-server.properties

Step 2: Configure the UDP port

This is the most important step. Simple Voice Chat uses a separate UDP port from Minecraft's TCP port to transmit audio.

Assign an additional port in Pterodactyl

1. Go to panel.baires.host → your server
2. Navigate to Network or Allocations
3. Click Create Allocation or Add Port
4. Note the new assigned port (e.g., 24454 or whatever the panel assigns)

If you can't add ports from the panel, contact support to get an additional UDP port assigned.

Configure the port in Simple Voice Chat

Edit voicechat-server.properties:

port=24454

Replace 24454 with the port assigned in the panel.

Can I use the same port as Minecraft?

Technically yes, by setting port=-1. However, the official documentation strongly recommends NOT doing this because:

• Minecraft's UDP port is used by default for the server query
• Using the same port can cause server crashes
• It creates protocol conflicts between query and voice chat

# NOT RECOMMENDED - may crash the server
port=-1

Correct solution: Always use a dedicated port different from Minecraft's. If your Minecraft server runs on port 25565, use another one like 24454 or whatever the panel assigns.

If you don't have another port available

If your plan only includes one port and you need to use the same one, follow these steps:

First, disable server query in server.properties:

enable-query=false

Then, configure Simple Voice Chat to use the same port in voicechat-server.properties:

port=-1

Finally, restart the server to apply both changes.

Note: While this may work, it's a last resort. Ideally, request an additional port from support.

Step 3: Configure voice_host (important for hosting)

If players can't connect to voice chat, you likely need to configure voice_host:

voice_host=your-server-ip:24454

This tells clients which address to connect to for audio. Use the same IP players use to connect to the Minecraft server, followed by the voice chat port.

Example:

voice_host=game1.baires.host:24454

Step 4: Full server configuration

voicechat-server.properties file with all options:

# UDP port for voice chat (do NOT use -1 if possible)
port=24454

# IP to bind voice chat to (leave empty to use server-ip)
bind_address=

# Maximum voice distance (in blocks)
max_voice_distance=48

# Whisper distance (in blocks)
whisper_distance=24

# Audio codec (VOIP, AUDIO, RESTRICTED_LOWDELAY)
codec=VOIP

# Maximum audio packet size (bytes)
mtu_size=1024

# Packet rate limit per player per second
tcp_rate_limit=16

# Keep-alive frequency (ms)
keep_alive=1000

# Allow voice groups
enable_groups=true

# Host clients use to connect
voice_host=

# Allow audio recording
allow_recording=true

# Spectators can talk to players
spectator_interaction=false

# Kick players without the mod
force_voice_chat=false

# Timeout to check if player has the mod (ms)
login_timeout=10000

# Broadcast range (-1 = max_voice_distance)
broadcast_range=-1.0

# Reply to external pings
allow_pings=true

Step 5: Client installation (players)

Players need to install the mod on their client:

1. Install Fabric Loader, NeoForge, Forge or Quilt
2. Download Simple Voice Chat for their loader from modrinth.com
3. Place the .jar in their Minecraft mods/ folder
4. When joining the server, press V to open voice chat settings
5. Follow the setup wizard (select microphone, speaker, activation mode)

Important: The client mod must be compatible with the server version. It doesn't matter which loader the server uses — all are cross-compatible.

Default key bindings (client)

Players can change these keys in Options → Controls.

Permissions (for servers with LuckPerms)

Simple Voice Chat has permissions compatible with Bukkit and Fabric Permissions API:

To restrict voice chat to a specific rank:

lp group default permission set voicechat.speak false
lp group vip permission set voicechat.speak true

Commands

All commands are executed in-game (not from the panel console):

The /voicechat test command requires voicechat.admin permission.

Troubleshooting

Icon shows "Voice chat not connected" (plug icon)

Most common cause: The UDP port is not open correctly.

1. Verify the port is assigned in the panel (Network/Allocations)
2. Verify port in voicechat-server.properties matches the assigned port
3. If using voice_host, verify the IP and port are correct
4. Restart the server after any changes

Players connect but can't hear each other

1. Verify both players have the mod installed on their client
2. Check they're not muted (M key)
3. Verify they're within max_voice_distance range (48 blocks by default)
4. If in a group, proximity doesn't apply — they can hear each other regardless of distance

Server crashes on startup

• "Address already in use": Another program is using the port. Check for other voice chat instances or GeyserMC using the same port
• "Failed to bind to address": Leave bind_address empty if unsure
• Verify the server query (query.port in server.properties) isn't using the same port as voice chat

Constant disconnections

• Could be unstable player connection
• Mobile data or VPN users may have UDP blocked by their ISP
• Increase keep_alive to 2000 or 3000 if frequent timeouts occur

DDoS protection blocks voice chat

Some DDoS protection services block unrecognized UDP traffic. If you have this issue, contact support to create an exception for the voice chat port.

Proxy setup (Velocity/BungeeCord)

If using a proxy:

• Install the Simple Voice Chat plugin on the proxy (plugins/ folder of the proxy)
• Install the mod/plugin on each backend server
• You only need to open one UDP port on the proxy
• Configure voicechat-proxy.properties on the proxy (see example below)
• Backend servers don't need externally open UDP ports — the proxy handles the connection

Example voicechat-proxy.properties:

# Voice chat UDP port on the proxy (-1 = same as proxy port)
port=-1
bind_address=
voice_host=
allow_pings=true

Supported versions

Simple Voice Chat is actively maintained for multiple Minecraft versions. As a plugin (Bukkit/Paper), a single .jar supports from 1.8.8 to the latest version. As a mod, actively supported versions include 1.12.2, 1.16.5, 1.18.2, 1.19.2, 1.20.1, 1.21.1, 1.21.4, 1.21.5 and later.

Always check modrinth.com/mod/simple-voice-chat for the latest compatible version.

Quick setup summary for Baires Host

1. Install the plugin/mod on the server
2. Request an additional UDP port (or assign one from Network in the panel)
3. Set port=ASSIGNED_PORT in voicechat-server.properties
4. Set voice_host=YOUR_IP:ASSIGNED_PORT if clients can't connect
5. Restart the server
6. Players install the mod on their client and press V when joining

Tips

• Always use a dedicated port different from Minecraft's to avoid conflicts
• If you have connection issues, first verify the UDP port is open
• Don't change voice_host unless players can't connect to audio
• For roleplay servers, set max_voice_distance=24 for more intimate conversations
• For large servers, keep force_voice_chat=false to not exclude players without the mod
• Use /voicechat test PlayerName to diagnose individual connection issues