I found myself trying to write code for navigating in hierarchy like manner in Unitys Inspector (RuleSet -> Entity -> Component -> More To Come) today. First thought I had: Just put a reference field into every single scriptable object and your done ... well no.

Some times you write classes, inherit from them and create properties to cast things from base class to your known types.

Based on these two threads on Unity Forums and my research on my final project I just tried to get my async scripts memory footprint down to nearly zero (3 Byte per Frame?) which is impossible with Unitys Coroutines because they are generating 17 Byte per Frame with just a single yield return n...