Development and Deployment of Multiplayer Online Games, Vol. II: DIY, (Re)Actors, Client Arch., Unity/UE4/ Lumberyard/Urho3D (2) - Hardcover

Inhaltsangabe

<p>Trying to develop your own multiplayer online game can be overwhelming, especially as information on multiplayer specifics is <i>very</i> scarce. The nine-volume <i>Development and Deployment of Multiplayer Games</i> series is an attempt to <b>summarize a body of knowledge that is known in the industry, but is rarely published, let alone published together</b>.<p><b>The series is highly praised by prominent representatives of the multiplayer gamedev industry</b>. An “Early Praise” page within the book lists several testimonials by people from billion-dollar and/or AAA companies with job titles ranging from <i>Managing Director</i> and <i>CTO</i> to <i>Backend Technical Director</i> and <i>Principal Software Engineer</i>.<p><b>Genres: From Social Games to MMOFPS,with Stock Exchanges In Between</b>. <i>Development and Deployment of Multiplayer Online Games</i> 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.<p><b>Level: Intermediate+</b>. 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.<p>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 <i>how the concept of futures</i>  fits into event-driven programming, when the use of optimistic locking <i>makes sense for games</i>, and how to use source control <i>in the presence of unmergeable files</i>.<p><b>This Volume: Vol. II</b> Vol. II continues <i>Part ARCH(itecture)</i>, and includes four Chapters. Chapter 4 discusses choices between DIY elements of your game and re-using 3rd-party ones, advocating for "responsible re-use". Chapter 5 explores (Re)Actors - which can be seen as a generalization of classical game loop, and allow to handle all the kinds of games, including, but not limited to, simulations. Special attention is paid to (Re)Actor goodies such as replay and production post-factum analysis. Chapter 6 concentrates on Client-Side Architecture - both generic and (Re)Actor-based. Note that serious discussion of the graphics is beyond the scope. Chapter 7 is aimed at those development teams who want to re-use popular existing engines (such as Unity 5, UE4, Lumberyard, or Urho3D) to develop an MOG. Various 3rd-party communication libraries (including Photon and SmartFoxServer) are also discussed in this context.

Die Inhaltsangabe kann sich auf eine andere Ausgabe dieses Titels beziehen.