42.19.0 is live on the unstable branch, and the multiplayer work in it is the direct follow-on to what we shipped in 42.18. The Indie Stone has positioned this one as another foundational update — performance, stability, bug fixing, with some controller-usability work added in — and the multiplayer section is where most of our cycle landed. Two foundation passes back-to-back is the kind of pace you only get to when the architecture work has settled enough to actually go fix things.
The most visible thread is the second half of the anti-cheat work. In 42.18 we cleared out the redundant Fire, Smoke, and XP passes that had been producing more noise than signal; with that cleanup done, this build adds the coverage that was actually missing — additional protections around commands, XP, permissions, and safehouses. It is much easier to put up the right fencing once you have torn down the wrong fencing. Ban IP functionality has been restored for Steam servers using direct connections, and we have closed another batch of exploits: item duplication, an endurance exploit, and one that exposed server-side map data to a client that should not have had it. None of these are flashy. They are the bugs you find when you stop treating the client as a trusted party.
The rest of the cycle is the long stability-and-desync tail, and a few of these were satisfying to finally track down. Weapon magazines were disappearing after reload on MP — the kind of bug that does not surface until specific player flows are exercised on a real server with real network conditions. Audio from 3D-placed walkie-talkies and radios was sitting silent until the chunk reloaded around it. Vehicle-engine audio is now properly audible to remote clients at long range, which means an approaching truck once again sounds like one. Sprinters no longer play the shambler audio set in multiplayer. Performing a medical check several times no longer breaks the UI window. The list runs on through the smaller items — zombie duplication and spawn-timing issues, animal syncing, trailer interactions, relog edge cases, safehouse settings, chat channel and server option behaviour, and a handful of server-side exceptions thrown by the anti-cheat triggers themselves while we were tuning them. Each one is small on its own. Together they are the difference between a server that feels solid and one that does not.
The unstable branch is open for testing. With 42.18 and 42.19 both landing as foundation passes, the multiplayer layer is in noticeably better shape than it was at the start of the year — and that is largely the point of work like this. The headlines come later.