The Observer Pattern is probably one that confuses people the most, but is not only rather simple - it feels the most gratifying to put into a project and have your components run off of events.
In video games the observer pattern typically breaks down into 2 parts - a broadcast is sent, and a bunch of "observers" or "listeners" are waiting to be notified of that broadcast, and then do something.
This is primarily driven with events and delegates, and the big bonus here is your components do not need to know about each other, they only need to know about the events that the observers can subscribe to.
This is useful for anything that happens in your games, unity or otherwise. Pickup events, damage events, game over events, enemy killed events, trigger events, etc etc etc. Games are driven by events already, the observer pattern just structures your project to give you that full separation.
✨Want to support the channel?
Buy me a coffee ☕: [ Ссылка ]
COMMENT down below how you use the Observer Pattern, or if you're having trouble understanding it.
➤SUBSCRIBE to learn more about other design patterns as I cover them next!
➤Join our discord, I command you: [ Ссылка ]
Thanks for watching!
#bmo #gamedev #programming
