← all posts site ↗

multiplayer without the server headache

the thing that always stopped me on multiplayer is the technicality of it, server authority, physics rollback, state sync, all the words that sound like work. then it clicked that the newer friend games are not doing any of the heavy physics interaction stuff, and the ones that throw objects around and share them are running client logic with rpc calls and trusting the client to behave.

the plan is to keep trusting the client. physics stays local to each player's movement, and everything else is just messages, someone pressed something, something changed, everyone else gets told. for a play with friends game that is not a compromise, it is the architecture. no server authority, no rollback, just functional and low key.

the build order is to make the driving prototype real first, a test scene with a working vehicle controller, and then wire the netcode in as a package around it, a transport layer plus the shared interaction bits that the car plugs into. the hard part was never the physics, it was believing the simple version was allowed to exist.