Direct answer
Voice chat usually adds a separate real-time audio networking workload; Minecraft TPS alone does not capture voice quality. Diagnose audio packet loss and voice-server UDP accessibility first.
How to check it
- Identify the voice-chat mod/plugin and the actual platform, network topology and documented UDP port.
- Ask whether users experience choppy audio, connection failure or simultaneous game TPS degradation.
- Compare host network traffic and CPU use while many users speak versus a quiet session.
- Take a spark profile only if game tick time increases, rather than treating every audio dropout as a tick problem.
What to change
- Set voice distance, group sizes or codecs only using options supported by the installed voice-chat software.
- Open the documented UDP port on relevant firewalls and avoid conflicting services listening on the same socket.
- For proxies and multiple backends, follow that voice plugin’s network routing instructions instead of assuming the Minecraft TCP port carries voice.
Software and version notes
Real-time UDP packets respond differently to congestion and firewall rules from Java TCP gameplay. Poor voice quality with stable MSPT often indicates routing, network jitter or client microphone/device issues.
Practical example: Example: voice works on the local network but not across a hosted proxy because the plugin’s UDP listener is unreachable. Opening or forwarding the documented voice UDP port may fix connection, while lowering simulation distance would not. If server MSPT rises only while audio is active, profile the voice integration separately.
Verify the result
- Test voice reception between users on separate networks.
- Confirm game TPS and chat remain healthy and recheck for dropped/garbled audio under the same speaking load.