On this page
Key takeaways
6- Install the Paper plugin on the server and the Simple Voice Chat client mod for every player who wants voice.
- Expose the configured UDP port, default 24454, through every relevant firewall and router.
- Panel users should use the UDP port assigned by their host and match it in the voice chat configuration.
- Run /voicechat test PlayerName in game with voicechat.admin permission.
- Keep force_voice_chat=false unless you intend to kick players without the client mod.
- On Velocity networks, install voice chat on the proxy and every backend, with one external UDP port for the proxy.
Simple Voice Chat adds proximity voice chat to Minecraft, with push to talk, voice activation and private groups. This guide helps Paper server owners install it, make its UDP port reachable and test voice connections before inviting players.
Check what the server and players need
The server plugin is only half of the setup. Every player who wants to use voice chat also needs the Simple Voice Chat client mod.
- Server: choose the Bukkit/Paper plugin build for your Minecraft version from the official Modrinth listing.
- Players: install the client mod that matches their Minecraft version and mod loader.
- Networking: arrange a reachable UDP port for voice traffic. The default is
24454.
Players without the client mod can still join when force_voice_chat=false, but they cannot use voice chat. Bedrock is unsupported, so do not plan this as a voice solution for Bedrock players.
If you have not installed Paper yet, start with our Paper server setup guide. When choosing hosting, ask whether the provider can allocate and expose an additional UDP port.
Install the Paper plugin
Download the server plugin build, rather than putting a client mod file in the server's plugin folder. Use the installation route for where your server runs.
- Stop Paper through your existing server controls.
- Upload the Bukkit/Paper plugin JAR into the server's
pluginsdirectory. - Start Paper again, then locate
plugins/voicechat/voicechat-server.properties.
- Stop the server from the panel.
- Use the File Manager or SFTP to upload the Bukkit/Paper plugin JAR into
plugins. - Start the server, then open
plugins/voicechat/voicechat-server.propertiesin the File Manager.
- Stop the server from the panel.
- Use Files / FTP to upload the Bukkit/Paper plugin JAR into
plugins. - Start the server, then locate
plugins/voicechat/voicechat-server.propertiesthrough Files / FTP.
The Paper plugin uses the configuration path above. The client mod and other server platforms have their own setup, so use the project wikiSource site when preparing those installations.
Open the separate UDP port
Decide which UDP port your server will actually receive before editing the configuration. On a rented panel server, use the port assigned by the host, even if it differs from 24454.
- Allow your chosen port for UDP in the machine's firewall.
- Allow the same UDP port in the hosting provider's firewall or network panel, if one is present.
- Set the voice chat configuration's
portvalue to that port.
If the server runs on your own PC at home, allow the UDP port through the PC firewall and forward it through the router to the server machine.
- Ask the host or node administrator to assign a voice port through Allocation Management and configure the node's allocations for it.
- Make sure that port is exposed for UDP. A Minecraft TCP allocation alone does not establish that voice traffic can reach the server.
- Set
portin the voice chat configuration to the assigned port. If allocation controls are unavailable to you, ask the host to make the change.
- Ask the host to provide a reachable UDP port for Simple Voice Chat.
- Use the port they assign as the configuration's
portvalue. - Ask the host to check its firewall and network routing if the connection test fails after configuration.
The Breakdown's tutorial walks through adding Simple Voice Chat, setting voice distances and opening UDP port 24454 on a self-hosted server.
Set voice distance and joining rules
In plugins/voicechat/voicechat-server.properties, start with a small set of deliberate settings. This example uses the default port and distances. Replace the port if your host assigned another one.
port=24454
max_voice_distance=48
whisper_distance=24
enable_groups=true
force_voice_chat=falsemax_voice_distancecontrols the proximity voice distance.whisper_distancecontrols the whisper distance.enable_groupsenables the group feature.force_voice_chat=falseallows players without the voice chat mod to remain on the server.
Keep voice optional while testing. Setting force_voice_chat=true kicks players who do not have the mod installed; login_timeout controls the verification wait in milliseconds, with a default of 10000.
The bind_address setting controls where the voice server listens. When empty, it uses the Minecraft server-ip setting. The separate voice_host setting tells clients which hostname to use for voice chat. Change these only when your network layout requires it, following the server configuration referenceSource site.
After saving your configuration, restart through the controls appropriate to your server.
Stop and start Paper using your existing service, server session or management controls.
Save the file in the File Manager, then restart the server from the panel.
Save or upload the edited file through Files / FTP, then restart the server from the panel.
Test connections and fix the failing layer
Join with the client mod installed, then run the connection test in game. Replace the example name with the player you want to test.
/voicechat test PlayerNameThis requires voicechat.admin, which defaults to operators. Simple Voice Chat's commands work in game, not from the server console.
- Check the client: the player needs the client mod to use voice chat.
- Check the configured port: it must match the UDP port assigned or opened for the server.
- Check each network boundary: review the machine firewall, provider firewall and any home router forwarding that applies.
- Check permissions: a player needs permission to listen and speak, even after the network connection works.
- Test proximity: have two players speak nearby, then move apart to check the distances you selected.
A missing open voice port is a common cause of the not-connected error. Ordinary web port checkers are insufficient for this test because UDP checking needs an application that answers. Use the plugin's connection test and the official setup troubleshootingSource site instead.
Control speaking, listening and groups
Simple Voice Chat uses the Bukkit permission system on Paper. LuckPerms can grant or deny its nodes for particular groups or players.
voicechat.listen: permission to listen, enabled for everyone by default.voicechat.speak: permission to speak, enabled for everyone by default.voicechat.groups: permission to use groups, enabled for everyone by default.voicechat.admin: administration permission, enabled for operators by default.
Give connection-test access to the staff who need it. If a player connects but cannot speak or hear, inspect their effective permissions before changing network settings again. Our LuckPerms ranks guide covers organizing permissions by group.
Groups support password protection. Players can use these commands in game to invite someone, join a group or leave one:
/voicechat invite PlayerName
/voicechat join GroupName
/voicechat leaveConnect voice chat across a Velocity network
For a Velocity network, install the Simple Voice Chat Velocity plugin on the proxy and voice chat on every backend server. The proxy plugin detects each backend's voice port and provides a single external UDP entry point.
Only one UDP port needs opening externally for the proxy. It typically matches the proxy's Minecraft port, with 25577 being the default described for Velocity. Use your actual proxy configuration rather than copying that number without checking.
Stop the proxy, place the Velocity voice chat plugin in its plugin directory and start it again. Install voice chat on each backend too, and allow the proxy's chosen external UDP port through the relevant firewalls.
Stop the proxy server entry, upload the Velocity voice chat plugin through its File Manager or SFTP, then start it again. Repeat the backend installation for each game server and ask the host to expose the proxy's voice UDP port.
Use the proxy's Files / FTP access to install the Velocity voice chat plugin while it is stopped, then start it again. Install voice chat on each backend and ask the host to expose the proxy's voice UDP port.
Backend voice_host settings are ignored in this arrangement. If a voice hostname is needed, set it in the proxy's voice chat configuration. Follow the official proxy instructionsSource site for that layout.
If you are still building the network itself, follow our Velocity setup guide first. Then test voice connections on each backend before opening the network to players.
Frequently asked questions
Do players need a mod for Simple Voice Chat on Paper?
Yes. The Paper plugin provides the server side, and each player needs the Simple Voice Chat client mod to use voice. Players without it can still join while force_voice_chat=false.
Why does Simple Voice Chat say not connected?
A common cause is that the server's voice UDP port is not reachable. Check that the configured port matches the host allocation and is allowed through the relevant firewalls or router. Run /voicechat test PlayerName in game with voicechat.admin permission.
Which port does Simple Voice Chat use on Pterodactyl?
The default voice port is 24454 UDP, but your host may assign a different port. Ask the host or node administrator to configure the allocation and expose it for UDP. Put that assigned number in the voice chat port setting.
Can Bedrock players use Simple Voice Chat?
Bedrock is unsupported. The Java server plugin does not remove the requirement for a compatible client mod.
Does Simple Voice Chat work with Velocity?
Yes. Install its Velocity plugin on the proxy and voice chat on every backend server. The proxy provides one external UDP entry point, and any voice_host setting belongs in the proxy's voice chat configuration rather than the backends.