Skip to content

Simple Voice Chat

Jump to bottom
pjscruggs edited this page Nov 8, 2026 · 2 revisions

Raknetify2 can share its server UDP listener with Simple Voice Chat on Fabric, Forge, NeoForge, Spigot, and Paper.

Install Simple Voice Chat on the server and on each client that wants voice chat. Follow its server setup guide for the rest of its configuration.

Use the server's top-level config directory for Raknetify2's file, including on Spigot/Paper. Simple Voice Chat's own file remains in the platform-specific location below.

Share the gameplay port

  1. Create config/raknetify2-voicechat.json in the server directory with this content:

    {"enabled": true}

  2. Set port=-1 in Simple Voice Chat's server configuration. On modded servers, this is config/voicechat/voicechat-server.properties. On Spigot/Paper, it is plugins/voicechat/voicechat-server.properties.

  3. Leave bind_address empty when there is one matching RakNet listener. If the server has multiple listeners on that UDP port, set it to the local address of the listener you want to share.

  4. Restart the server and run /voicechat test <PLAYERNAME> for a connected player.

If the RakNet listener uses a different port from Minecraft, set the voice port to that local UDP port explicitly instead of using -1. For example, a RakNet listener on local UDP port 25570 needs port=25570.

Set voice_host when clients need a different public address or port. For a router forwarding public UDP 25580 to local UDP 25570, use port=25570 and voice_host=play.example.com:25580. The public address belongs in voice_host. The bind_address setting selects a local listener.

Raknetify2 supplies the shared UDP socket through Simple Voice Chat's API. Simple Voice Chat handles voice authentication and encryption. Players can use voice chat with either TCP or RakNet gameplay connections.

Other UDP services and proxies

Keep Query and Geyser on separate UDP ports. The shared socket integration supports Simple Voice Chat only.

The integration does not share a voice-proxy socket on Velocity or BungeeCord. Follow Simple Voice Chat's proxy setup guide and give the voice proxy its own UDP port. With the official voice proxy plugin, set any public voice_host override in the proxy's voice configuration. That plugin ignores backend servers' voice_host settings.

For a generic UDP tunnel, set voice_host to the public hostname and UDP port that forwards to this server.

Disable sharing or resolve a socket conflict

If the log reports No RakNet listener matches the voice bind address and port, confirm that RakNet started successfully and that the voice port and bind address match its local listener.

If it reports Multiple RakNet listeners match the voice bind address, choose a specific matching local address in bind_address and restart.

Only one Simple Voice Chat plugin can supply its UDP socket. If startup reports that another plugin already supplies a socket, choose which socket integration to use.

To disable Raknetify2's integration, set {"enabled": false} in its voice configuration or remove that file. Give Simple Voice Chat a separate UDP port, update its firewall or forwarding rules, and restart the server.

Clone this wiki locally