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

Benefits and drawbacks

Here are some benefits of the Facade pattern:

  • Simplified interface to a complex body of code: A solid Facade class will conceal complexity from a client while providing a simplified interface to interact with an intricate system.
  • Easy refactoring: It's easier to refactor code that's isolated behind a Facade because the system's interface remains consistent to the client while its components are being modified behind the scenes.

The following are some drawbacks to watch out for:

  • It makes it easier to hide the mess: Using the Facade pattern to hide messy code behind a clean front-facing interface will defeat the pattern's core benefits in the long run, but this pattern does offer a way to mask some code smells until you have time to refactor them. However, expecting to have enough time later to fix stuff is a trap in itself because we rarely have enough time to refactor things correctly.
  • Too many facades: Globally accessible...