Simple Voice Chat 2.6.24 shipped on 20 September for 26.3 on both Fabric and NeoForge, and three days later an alpha build appeared for 26.4 Snapshot 1. That second one is the interesting part: proximity voice is usually one of the last things to reach a snapshot, not one of the first.
What is in 2.6.24
voice_hostis now ignored in singleplayer and LAN worlds.- Sound manager error messages are more informative.
- Thai translation added.
Short list, but the voice_host change fixes a real class of confusion. That setting tells clients which address to reach the voice server on, and it exists because a Minecraft server’s public address is frequently not the address its voice component is listening on – reverse proxies, NAT, container networking all cause this.
On a dedicated server that is essential. In singleplayer or on a LAN world it is nonsense, because the voice server is the same process you are already talking to. Previously a leftover voice_host in a config, copied from a server setup or a modpack, would cause the local voice server to advertise an unreachable address and voice chat would silently fail to connect in a world where it obviously should have worked.
The 26.4 snapshot alpha
The Fabric build tagged 2.6.24+26.4-snapshot-1 landed on 23 September with a one-line changelog: updated to 26.4-snapshot-1. It is marked alpha, which is the correct label for a mod built against a snapshot that itself changed the graphics default and the connection handshake.
Why it ported quickly: Simple Voice Chat does relatively little with rendering and a lot with networking, and the 26.4 networking changes so far are additive rather than disruptive. The snapshot introduced allowed connection IDs and a mod list packet, which is a server-side handshake concern rather than something that breaks an existing custom payload channel.
Voice mods have historically been sensitive to exactly that layer, so an early clean port is a mild good sign for how disruptive 26.4 will be for networked mods generally.
Why proximity voice keeps mattering
Simple Voice Chat has around seventy million downloads, which puts it in the same bracket as the big performance mods. That is unusual for something that adds no blocks, no items and no mechanics.
The reason is that it changes what a multiplayer server is. Text chat is broadcast and asynchronous; proximity voice is local and immediate. On a small SMP it turns a shared world into a shared room, which is the difference between people logging in to do tasks and people logging in to be somewhere. Server owners running a compact SMP mod list almost always include it for that reason alone.
Running it on a server
Two things trip up first-time setups, and neither is the mod’s fault.
The first is the UDP port. Simple Voice Chat uses a separate UDP port from the game’s TCP port, defaulting to the same number. Hosts that only forward the game port will see voice fail while everything else works. If your provider gives you one port, you need to ask them for a second or configure the voice port to a range they have opened.
The second is voice_host, which is exactly why the 2.6.24 change exists. On a real server you set it to the address clients can actually reach. Behind a proxy that is not the same string as your server address, and getting it wrong produces the same symptom as a closed port, which is why people spend hours on the wrong problem.
Both are worth writing into your server documentation alongside the specs and hosting notes, because new players hitting a voice failure will assume their microphone is broken rather than that a port is closed.
Client-side notes
The improved sound manager error messages in 2.6.24 target the other half of the support burden: players whose audio device changed, was captured by another application, or was never granted permission. Previously those all surfaced as a generic failure. Now the message says which stage failed.
That is a small change with an outsized effect on a server’s moderation load, because most voice problems are reported to an admin who cannot see the player’s audio settings.
Versions at a glance
- fabric-2.6.24+26.3 and neoforge-2.6.24+26.3 – 20 September, marked beta, the ones to run on a live server.
- fabric-2.6.24+26.4-snapshot-1 – 23 September, alpha, for snapshot testing only.
Do not put an alpha snapshot build on a community server. Do put it on a test instance if you run a server that will need to move to 26.4 promptly, because finding out early which of your mods survive the jump is the entire value of a snapshot cycle.
A word on the alternatives
Simple Voice Chat is not the only proximity voice option, and the main alternative takes a meaningfully different approach: a separate voice server process rather than a component inside the game server, with its own client and its own addressing.
That architecture is more flexible for large networks and more work for a small one. For an SMP with a dozen players, the in-process approach wins on setup time alone – one jar, one port, no second service to keep running. For a network with several game servers that want a shared voice space, the separate-server model is the one that scales.
Both have the same underlying requirement: a UDP port that clients can reach. Whichever you pick, that is the thing to confirm with your host before you spend an evening on config files.
Images: Simple Voice Chat project gallery.