server

This isn’t just for MMO’s all multiplayer games today run everything on the server side the server side basically runs a client that is the single source of truth. To improve the experience and compensate for lag player clients run a simulation and can update their state based on their player actions directly before the action is registered or acknowledged by the server client then they only get a confirmation from the server or they get a forced update if the action they performed wasn’t in agreement with the server. As for other things like give mentioned you don’t usually have to run a full model on the server side of your world, you however hold a representation of it in the form of maps, these are usually huge arrays of coordinates with various properties they basically transform the 3D game world into a board game board. For MMO’s s

This situation makes me think of the video game industry and people recreating self hosted World of Warcraft servers by reversing the client code. Blizzard was able to shut down the private servers. https://github.com/mangoszero/server https://www.google.com/amp/s/arstechnica.com/gaming/2017/07/...

My understanding was that WoW would do essentially what's described here for the player's character and entities in the immediate area (simulate them for the next few frames), but the server also maintained a view of the world. The client would occasionally sync with the server, and that's when you would see the blinks. If you're curious, this[0] is an actively maintained implementation of a WoW server. [0] https://github.com/mangoszero/server