Development And Deployment Of Multiplaye

Trying to develop your own multiplayer online game can be overwhelming, especially as information on multiplayer specifics is very scarce. The nine-volume Development and Deployment of Multiplayer Games series is an attempt to summarize a body of knowledge that is known in the industry, but is rarely published, let alone published together.

The series is highly praised by prominent representatives of the multiplayer gamedev industry. An "Early Praise" page within the book lists several testimonials by people from billion-dollar and/or AAA companies with job titles ranging from Managing Director and CTO to Backend Technical Director and Principal Software Engineer.

Genres: From Social Games to MMOFPS, with Stock Exchanges In Between. Development and Deployment of Multiplayer Online Games aims to cover pretty much all the MOG genres - ranging from social games to MMORPGs and MMOFPS. While there are certainly differences between the genres, around 80% of the discussed concepts apply across the board.

Level: Intermediate+. This series is not trying to teach very basics of the programming (and is not a book to copy-paste your MOG from). Rather, it is intended for those intermediate developers who want to progress into senior ones, and all the way up to CTOs and architects.

In particular, there is no explanation of what event-driven programming is about, what the difference is between optimistic locking and pessimistic locking, why do you need a source control system, and so on. Instead, there will be discussions on how the concept of futures fits into event-driven programming, when the use of optimistic locking makes sense for games, and how to use source control in the presence of unmergeable files.

This Volume: Vol. I Vol. I starts Part ARCH(itecture), and includes three Chapters. Chapter 1 discusses Game Design Document (GDD) - mostly concentrating on its multiplayer specifics of GDDs. Chapter 2 explores the all-important aspects of cheating - which is virtually non-existent in single-player games and games between friends, but plays an enormous role in multiplayer games; the resulting analysis leads to Authoritative Server architectures (note that discussion on implementing anti-cheating measures is much longer than it is possible to fit into Vol. I, and will take the whole Vol. VIII). The largest chapter of Vol. I, Chapter 3, is dedicated to typical multiplayer communication flows. Along the course of this discussion, it will cover lots of different topics, including such different things as Client-Side Prediction, Low-Latency Compressible State Sync, Lag Compensation and its dangers, and Inter-DB Async Transfer with Transactional Integrity

The author of this book is 'No Bugs' Hare from the warren of Bunnylore. He is known for being a columnist for the Overload Journal and for his significant contributions to the software development blog ithare.com. As 'No Bugs' is a rabbit with Lapine as his mother tongue, he needed somebody to translate the book into human language. And of course, as the book is highly technical, to translate technical details with the highest possible fidelity, he needed a translator with substantial software development experience.

This book has been translated from Lapine by Sergey Ignatchenko, a software architect since 1996. He is known for writing for industry journals since 1998, with his articles appearing in CUJ, Overload, C++ Report, and (IN)SECURE Magazine. His knowledge of Lapine is quite extensive, and he routinely translates the column No Bugs writes for Overload. During Sergey's software architecting career, he has led quite a few projects, including as a co-architect of a stock exchange for a G20 country (the same software has been used by stock exchanges of several other countries), and as the sole original architect of a major gaming site (with hundreds of thousands of simultaneous players, billions of database transactions per year, and processing hundreds of millions of dollars per year). As a kind of paid hobby, he also invents things: he's an author and co-author of several dozen patents (unfortunately, owned by his respective employers).