Enjin-Unity-sample VS UniRx

If you are using Unity, I found a github repo with a pretty good starting sample.

To get a reactive properties functional you can use UniRx.

Personally I use UniRx, but there's plenty of flavours of event systems to dig into.

What paradigms & design patterns that those of you whom have more experience than I recommend? I've been advised to use things Dependency Injection (Extenject) and/or Reactive programming (UniRx), but that came from someone whose background isn't Unity. I would like to do this right the first time and make the code as maintainable as possible; we will be using it again in the future.

This is pretty cool. I wrote something similar for a narrower problem space: RolePlay Attributes. UniRx’s Reactive Properties feel like the total package but with a conceptual and dependency overhead.

Interesting, I hadn't heard of UniTask. I use UniRX in my projects which I think solves similar problems in a bit of a different way.

Sure, knowing the patterns and instead of using first order language features, you may get your own implementation of "observer" or something alike. But if you see your system becomes "event-heavy" it's maybe time to think about getting already complete solution: https://github.com/neuecc/UniRx // how to MV(R)P

The reason I'm leading things in this direction is because I highly recommend picking up UniRx. It brings reactive programming into your game development workflow and will completely change the way you look at development.