Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.
We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.
What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.
Your mileage may vary. Batteries not included.
Part IIIa: Server-Side (Store-Process-and-Forward Architecture) of 64 Network DO's and DON'Ts for Game Engines
June 8, 2015 by • “No Bugs” Bunny
Abstract:
A Panegyric to Store-Process-and-Forward architecture
Quote:
"With proper logging, in most cases a bug can be found from one single crash/malfunction.
Filed under: On.System ArchitectureDistributed systems(Re)ActorsOn.ProgrammingNetwork Programming
Read morePart IIb: Protocols and APIs (continued) of 64 Network DO’s and DON’Ts for Game Engine Developers
June 1, 2015 by • “No Bugs” Bunny
Quote:
You shouldn't count on outsmarting all those millions of highly motivated hackers operating in an environment under their own control.
Another Quote:
Burst consisting of several million packets, may start causing observable issues for a mid-size ISP.
Filed under: On.System ArchitectureDistributed systemsOn.ProgrammingNetwork Programming
Read morePart IIa: Protocols and APIs of 64 Network DO’s and DON’Ts for Game Engine Developers
May 25, 2015 by • “No Bugs” Bunny
Quote:
While using framework is fine, forgetting about it is not.
Another Quote:
Even if you're forcing the auto-update every time the game app starts, there still are users who were online at the moment of the update, and those who found a way to bypass game updates
Filed under: On.System ArchitectureDistributed systemsOn.ProgrammingNetwork Programming
Read morePart I: Client Side of 64 Network DO's and DON'Ts for Game Engine Developers
May 18, 2015 by • “No Bugs” Bunny
Abstract:
Network support is not so trivial as it looks. Client side has quite a few things to screw up.
Quote:
We’re treating our readers as intelligent beings who can use Google and/or StackOverflow
Filed under: On.System ArchitectureDistributed systems(Re)ActorsOn.ProgrammingNetwork Programming
Read more
Six Impossible Things Before Breakfast Ltd. © 2026. All rights reserved.
