Observer Design Pattern

What’s the main idea behind the Observer pattern?

• Hide internal logic

• Ensure one instance of a class

• Notify multiple objects about a change

• Create objects from a base class

The object that sends updates in the Observer pattern is called the (a)   .

In Unity, what’s a common way to implement the Observer pattern?

• Coroutines

• Events and delegates

• ScriptableObjects

• GetComponent()

Why does Pixel use the Observer pattern for things like score updates or health changes?

• To play music

• To decouple logic and make updates automatic

• To manage player movement

• To detect collisions

Observers should be tightly connected to the subject class.

• True

• False

In the Observer pattern, a change in the subject triggers a (a)   in all observers.

What happens when an Observer no longer wants to listen to updates?

• The game crashes

• It unsubscribes from the event

• It gets deleted

• Nothing happens

Which of the following is NOT a good use case for Observer in games?

• UI updating health bar

• Score display updating on gem pickup

• Loading a scene

• Triggering achievements

Why should you always unsubscribe in OnDisable() in Unity?

• To save GPU power

• To prevent ghost listeners and memory leaks

• To keep sound from playing

• To avoid duplicate classes

The Observer pattern follows a (a)   -to-many relationship.