During the writing of the 2nd edition of "Hands-On Game Development Patterns with Unity 2019: Create engaging games by using industry-standard design patterns with C#", I'm taking into consideration all the feedback I'm receiving from readers, including the negative reviews. And so I'm structuring the content of this new edition based on the input that I'm getting.

For example, for this new edition, each of the code examples presented in the book will be sampled from a complete code-base of a fully playable prototype of a racing game. The game in question is named "Blade Racer," and you can see screenshots of a very early demo here.

The end goal of this approach is to give the reader as much context to each code example presented and showcase how we can use individual software design patterns to structure the code-base of an entire game. This strategy will hopefully make the content of the book more practical and useful to developers that are building their games in Unity.