Server-authoritative multiplayer has a built-in feel problem: your input takes a full round trip before the world reacts. Client-side prediction is how you hide it. Here is how it works, with the algorithm we shipped in kazap.io... #gamedev #unity3d

Our co-op-vs-5,000-enemies demo grew a level: players now battle through a castle assault while the swarm pours over the walls. Everything server-simulated and synced. #screenshotsaturday #gamedev #unity3d

Reactor 1.1.3 is out: Unity 6.5 support, built-in network stats (ksRoom.NetStats, plus a component that feeds them to your own callbacks), experimental UDP client frame syncing, and a batch of physics and spawn fixes... #gamedev #unity3d

We spent ten years building a Unity multiplayer engine because the games we wanted did not fit the tools that existed: physics-heavy, crowd-heavy, bandwidth-bound. The story, and what came out of it... #gamedev #unity3d

Three people, one Unity scene, one farm. Another speed build from @synty.bsky.social, this time building a farm level together in Scene Fusion, our real-time scene collaboration tool. Everyone edits live in the same scene, no merge conflicts... #gamedev #unity3d

Bit-packing is the simplest useful compression technique in game networking, and a few lines of C# can cut your payload by 30% or more. A quick primer... #gamedev #unity3d

Multiplayer bandwidth bills surprise people because the baseline is misunderstood: the 12-20 bytes you pay per networked entity update with standard engines is the floor, not a misconfiguration. Where the cost comes from, and what moves it... #gamedev #unity3d

Why do objects stutter in Unity even at high frame rates? It comes down to timesteps: Update runs at a variable rate, FixedUpdate on a fixed clock, and motion driven in one but rendered by the other gets sampled unevenly. A short explainer. #gamedev #unity3d

Seven people building one Unity scene at the same time. This is @synty.bsky.social assembling a demo level live in Scene Fusion, our real-time scene collaboration tool. No merge conflicts, no waiting your turn for the scene file. #gamedev #unity3d

We benchmarked our Unity multiplayer engine against Netcode for GameObjects and Photon Fusion 2. Identical scenes, same update rate, measured at the wire. Reactor moved 17x less transform data than NGO and 9.5x less than Fusion 2 in goodput, with about 5 KB/s in overhead. #gamedev #unity3d

4-player physics FPS, all physics simulated server-side. Every client stays in sync through the heaviest collisions, no drift. Built to stress-test our multiplayer engine, partly as a dogfooding exercise. Unity client, no DOTS #gamedev #unity3d #indiedev #multiplayer

It's #ScreenshotSaturday. A multiplayer world running across four physical servers. Each quadrant is a different machine. Cross a boundary and an entity takes on that region's color, handing off live to the server that owns it. Sharding / server meshing. kinematicsoup.com #gamedev #multiplayer

5,000+ enemies in a multiplayer survivors-like, all server-simulated and synced to every player. 50-70 KB/s per player, no network LOD, no hand-tuning. Built on Reactor, our Multiplayer engine. www.kinematicsoup.com/blog/multipl... #gamedev