Book Image

Game Development Patterns with Unity 2021 - Second Edition

By : David Baron
Book Image

Game Development Patterns with Unity 2021 - Second Edition

By: David Baron

Overview of this book

This book is written for every game developer ready to tackle the bigger picture and start working with advanced programming techniques and design patterns in Unity. Game Development Patterns with Unity 2021 is an introduction to the core principles of reusable software patterns and how to employ them to build components efficiently. In this second edition, you'll tackle design patterns with the help of a practical example; a playable racing game prototype where you’ll get to apply all your newfound knowledge. Notable updates also include a game design document (GDD), a Unity programming primer, and the downloadable source code of a complete prototype. Your journey will start by learning about overall design of the core game mechanics and systems. You’ll discover tried-and-tested software patterns to code essential components of a game in a structured manner, and start using classic design patterns to utilize Unity's unique API features. As you progress, you'll also identify the negative impacts of bad architectural decisions and understand how to overcome them with simple but effective practices. By the end of this Unity book, the way you develop Unity games will change – you’ll adapt a more structured, scalable, and optimized process that will help you take the next step in your career.
Table of Contents (22 chapters)
1
Sections 1: Fundamentals
5
Section 2: Core Patterns
16
Section 3: Alternative Patterns
20
About Packt

Reviewing alternative solutions

Even if the Command pattern was perfectly suited for our use case, there are some alternative patterns and solutions we could have considered:

  • Memento: The Memento pattern provides the ability to roll back an object to a previous state. This was not our first choice for our replay system because we are focusing on recording inputs and queuing them for replay at a later time, which is very compatible with the design intention of the Command pattern. However, if we implemented a system with a rollback to the previous state feature, the Memento pattern will probably be our first choice.
  • Queue/Stack: Queues and stacks are not patterns, but data structures, but we could simply encode all our inputs and store them in a queue directly in our InputHandler class. It would have been more straightforward and less verbose than using the Command pattern. The choice between implementing a system with or without conventional design patterns is very contextual. If...