Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Design Patterns with Unity

You're reading from  Learning Design Patterns with Unity

Product type Book
Published in May 2024
Publisher Packt
ISBN-13 9781805120285
Pages 676 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Harrison Ferrone Harrison Ferrone
Profile icon Harrison Ferrone
Toc

Table of Contents (23) Chapters close

Preface 1. Priming the System 2. Managing Access with the Singleton Pattern 3. Spawning Enemies with the Prototype Pattern 4. Creating Items with the Factory Method Pattern 5. Building a Crafting System with the Abstract Factory Pattern 6. Assembling Support Characters with the Builder Pattern 7. Managing Performance and Memory with Object Pooling 8. Binding Actions with the Command Pattern 9. Decoupling Systems with the Observer Pattern 10. Controlling Behavior with the State Pattern 11. Adding Features with the Visitor Pattern 12. Swapping Algorithms with the Strategy Pattern 13. Making Monsters with the Type Object Pattern 14. Taking Data Snapshots with the Memento Pattern 15. Dynamic Upgrades with the Decorator Pattern 16. Converting Incompatible Classes with the Adapter Pattern 17. Simplifying Subsystems with the Façade Pattern 18. Generating Terrains with the Flyweight Pattern 19. Global Access with the Service Locator Pattern 20. The Road Ahead 21. Other Books You May Enjoy
22. Index

Using C# event types

Before we dive into this section, let’s remember that the Gang of Four text covered the original Observer pattern in 1994. Many languages back then didn’t have built-in events, closures, or systems to easily decouple components. This left programmers to figure out efficient and scalable solutions on their own, with the Observer pattern coming out on top. This doesn’t mean the original Observer pattern structure should be thrown out if your language has these built-in tools, which C# and Unity both have.

The original pattern is still very useful for a one-to-many relationship between subject and observers (the waterfall analogy where you want observers to know everything happening downstream), but there are many common scenarios where that’s not enough, where observers may need to observe more than one subject at a time (we’ll call this the buffet scenario). In those many-to-many cases, we’re lucky enough to have the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime