Reply To: Reflection Description Suggestion

[Async0x42]

Yeah, for the cases where it wasn’t descriptive enough, having it made it look really nice, but there definitely are a few places where the description is making the line so long that it looks bad, I don’t have any ideas off the top of my head for a resolution to both issues.

Thanks! Your way would be good, and as you said, avoids deep nesting. Perhaps we could have inherited MonoBehaviour stuff in it’s own nested folder though, since there are so many and (I think) people would be more likely to access their components/inherited components, but even if not, it keeps Unity’s built in methods separate from user-written things.

i.e

1 2 3 4 5 6 7

EnemyComponent ->    -> Function A    -> Function B    Inherited ->        -> BaseEnemy Functions    MonoBehaviour (or Unity Inherited, or something) ->        > MonoBehaviour Functions

No problem, I’m glad you are open to listening to so many ideas!