My deck from my Montreal Unity User Group presentation of September 2016.

1. Software Design Patterns
How I use them in Unity!

2. Me!

3. David Baron
- Professional Game Developer
- I’ve worked for Ubisoft, Eidos, Gameloft …
- Currently specialization is VR / AR

4. Goals

5. What I’m covering?
- My observations of the rise of Unity within the indie game industry.
- How developers started integrated design patterns into the scripting engine.
- Only the simplest patterns that I find useful for indie game development.

6. What I’m NOT covering?
- The exact GoF definitions.
- Source-code or how to implement them.
- There’s people that know this stuff way better than me!

7. What are design patterns?

8. History

9. GoF
Gang of Four

10. AAA

11. C++
C#
LUA
Visual Scripting
Engine
Programmer
Gameplay
Programmer
Technical Director
Level Designer /
Scripter
Core Implementations
Game System
Implementations
Exposition & Wrapping
Sequencing & Integration

13. What do I code in Unity?

14. Behaviours
Animations, cycles, UI, NPCs ...

15. Systems
Mechanics, services ...

16. Scenarios
Scene events, flow, paths,
narration ...

17. Tools
Integration, debugging,
optimization ...

18. My rule of thumb

19. If I don’t recognize it after coding it then
it’s not a pattern!

20. The Anti-Pattern

21. Spaghetti

22. Spaghetti
- Public GameObject ….
- Reference hell!
- Abusing the inspector.

23. The Patterns

24. Singleton

26. Singleton
- Anyways all GameObjects in the scene are initialized.
- Easy access to an instance.
- But not everything needs to be accessible.
- Too many singles in one room!

27. Facade

28. Hide the nuts and bolts!

29. Facade
- I see it being used in a professional contexts.
- Very good solution for exposing complex gameplay
systems to scripters.

30. Managers & Facades
- They usually synonyms but not always.
- Having too many managers is like having “too
many cooks in the kitchen”.

31. Adapter

32. Adapter
- I use when I’m in an advanced prototyping
stage but I want to avoid refactoring
interfaces to related implementations.
- Adapter makes things work after they're
designed.

33. Exploring

34. Mediator

35. Mediator
- My biggest challenge is to find elegant ways for game
systems to communicate with each other while
staying decoupled.
- The Mediator design pattern is used to handle
communication between related objects (Colleagues).
- I NEVER used in production, at least not in an explicit
way.

36. Decorator

37. Object Pool

39. References
- Derek Banas
https://www.youtube.com/playlist?list=PLF206E906175C7E07
- Decorator Design Pattern
https://sourcemaking.com/design_patterns/decorator
- Efficient WebVR Development Using the Adapter Pattern in Three.js
http://hecodes.com/2016/08/efficient-webvr-development-using-the-
adapter-pattern-in-three-js/