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.
DIY vs Re-Use: In Search of Balance from upcoming book "Design&Development of MMOG"
November 16, 2015 by • “No Bugs” Bunny
Quote:
The biggest problem with building your game around 3rd-party game engine is that in this case, the game engine becomes your Absolute Dependency
Another Quote:
In future chapters we will keep in mind three specific game/network engines, and will discuss their pros and cons with relation to the issues we are raising. These engines are Unity 5, Unreal Engine 4, and Photon Server
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.DevelopmentDevelopment Philosophy
Game Entities and Interactions
November 2, 2015 by • “No Bugs” Bunny
Abstract:
It is still too early to start architecting your game.
Quote:
Even more importantly, you need to be reasonably sure that you have listed all the interactions which you can think of at the moment.
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.System ArchitectureDistributed systems
MOG GDD (a.k.a. Business Requirements)
October 26, 2015 by • “No Bugs” Bunny
Quote:
You don’t “make” a violin. It is barrels and benches which are “made”. And violins, just like bread, grapes, and children – are born and raised.
Another Quote:
The very first step should be to understand what exactly you're going to achieve.
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.System ArchitectureRequirement analysis
Read more