The document discusses game programming patterns, focusing on design patterns like command, flyweight, observer, prototype, singleton, and state. It provides examples of how each pattern can be used in game programming, such as using commands to configure inputs and give directions to actors, using observers for notifications between objects, and using the state pattern to allow objects to change behaviors based on internal state changes.

1. @agatestudio
Game programming
Restya
Producer
Agate Studio

2. GAME PROGRAMMING PATTERNS
Restya – TDS Agate Oktober

3. Why?

4. Chapters
Design Patterns Revisited
Sequencing Patterns
Behavioral Patterns
Decoupling Patterns
Optimization Patterns

5. We’ll be focussed on
Design Patterns Revisited
Command
Flyweight
Observer
Prototype
Singleton
State

6. Design Pattern

7. Design Pattern?
general reusable solution to a commonly occurring problem within a given context in software design

8. Command
Commands are an object-oriented replacement for callbacks

9. Command: Configuring Inputs

10. Command: Directions for Actors
Pass the object that we want to order

11. Command: Undo and Redo

12. Flyweight

13. Observer
An object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods.

14. Observer: The Observer

15. Observer: The Subject

16. Prototype

17. Not Using Prototype

18. Using Prototype

19. Using Protoype

20. Prototype: Spawn Function

21. Prototype: Templates

22. Prototypes for Data Modelling

23. Singleton
Ensure a class has one instance, and provide a global point of access to it.

24. Singleton +/-
It doesn’t create the instance if no one uses it
It’s initialized at runtime
You can subclass the singleton
It’s a global variable
They make it harder to reason about code
They encourage coupling
They aren’t concurrency- friendly
It solves two problems even when you just have one
Lazy initialization takes control away from you
Why we use it
Why we regret using it

25. State

26. State Pattern
Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.

27. State Pattern (2)

28. Static State

29. Instantiated State

30. Enter and Exit Actions
But we want each state to control its own graphics

31. Enter and Exit Actions (2)

32. Source: http://gameprogrammingpatterns.com/
Udah Gitu Aja