The Server::exec() call starts the server loop, which runs until the server is shut down. More...
Collaboration diagram for Core Processing Loop:
|
The Server::exec() call starts the server loop, which runs until the server is shut down.
Anything happening here will have immediate (and painful) impact on all connected clients (lag times, etc.). So make sure only core tasks are here, and that they happen quickly.
Here is what should happen in the loop:
- handle any UDP updates from clients (this is quick game state updates).
- update all loaded maps (next time tic)
- send state update back to all interested clients (UDP)
Some examples of things that should NOT happen in this loop:
- opening/reading/writing to files or sockets (so for instance, saves + loads must happen elsewhere)
- calculations that crunch all state (except tics, above)
- TCP request handling
