1st beta of Vol. I-III
This category consists of posts which form “1st beta” of the Vol.I-III of the upcoming book “Development & Deployment of Multiplayer Online Games”. Please note that “2nd beta” (available on Indiegogo) has 75% of the new content compared to the “1st beta” (in particular, based on the comments here on ithare.com and on /r/programming), so please don’t hit me too hard for the quality of the “1st beta”. ToC of “2nd beta”.
Choosing Version Control System for MOG development
September 19, 2017 by • “No Bugs” Bunny
Quote:
For game development (and unlike most of other software development projects), you're likely to have binary files which need to be edited (representing so-called “assets”)
Another Quote:
for open-source games, Git does have a Very Significant Advantage™
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.DevelopmentDevelopment Processes
Read moreMOGdev: to feature branch or not to feature branch?
September 12, 2017 by • “No Bugs” Bunny
Quote:
As a rule of thumb, for gamedev we DO need to have our version control to be easily usable by non-developers.
Another Quote:
it is the second developer to commit who becomes a responsible for resolving conflicts
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.DevelopmentDevelopment Processes
Read moreScalability for MOGs
June 20, 2017 by • “No Bugs” Bunny
Quote:
Whenever Game Event is interrupted for significant time, as a rule of thumb it is better to roll back the interrupted Game Event rather than trying to restore the exact Game World State in the middle of the Game Event.
Another Quote:
Just like Scaling Up, improving performance doesn’t provide infinite scalability. However, it happens that it is all about numbers.
Filed under: Book: D&D of MOGs1st beta of Vol. I-III
Read morePre-Coding Checklist: Things Everybody Hates, but Everybody Needs Them Too. From Source Control to Coding Guidelines
February 29, 2016 by • “No Bugs” Bunny
Quote:
The basic idea behind Continuous Integration is simple: as soon as you commit something, a build is automatically run with all the tests you were able to invent by that time
Another Quote:
One thing which should be noted about agile criticisms, is that there is no real disagreement about what needs to be done; the sentiment in such criticisms is usually more along the lines of “we’re doing it anyway, so do we need fancy names and external consultants?
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.DevelopmentDevelopment Processes




