Fixing Unity’s tendency to object coupling: The MessageBus

Hi everyone, Francisco from Nastycloud here.
I've been working on an article explaining our take on solving object coupling with Unity.
I'd love to hear your thoughts on this and if you have different approaches to this problem it would be awesome if you could share them!

Hope you enjoy the read!

http://nastycloud.com/2015/04/18/fixing-unitys-tendency-to-object-coupling-the-messagebus/

 

Good message. But hardly worth tackling in roll a ball.

While you are picking at the tutorials and coding practice you should also look at Unity's encouragement to break encapsulation by making everything public.

 

Interesting read. However, I don't understand why you would need to necessarily make all of your scripts inherit from MessageHandler, wouldn't an simple IMessageHandler interface be enough? That way I could give some random objects that do not inherit from MonoBehaviour also the ability to subscribe and handle messages. Otherwise, good work!

 

The pattern is similar, but I found that adhering to the Observer Design Pattern has worked very well... and I don't have to be concerned with extension limits nor be concerned with a singleton.

it's a fire and forget for the Provider, scalable, very little that requires cleanup... allows multiple providers with one-to-many, many-to-one, or many-to-many relationships.

observers can parse provider messages and choose to ignore or handle message in a custom manner...