Feature Description
Would be awesome if your quickstart mentioned that a common pitfall is overwritting some very common Unity Functions. Provide a little list of the most common ones to watch for:
Awake()
Start()
OnEnable()
OnDisable()
etc....
mention that they should call call the base.Awake(), base.Start(), base.OnEnable(), etc...
Then provide a link to your documentation to your uber awesome Diagnostic Tool which describes how they can look for these issue and other issue that might appear.
Love your DxMessaging
Use Case / Motivation
it is so that I can find the answer to this common issue I keep stumbling on in the documentation and do not have to keep messaging the creator, who I might say is an guy and spectacular programmer.
Proposed Solution
See above in feature description
Alternatives Considered
No response
Feature Description
Would be awesome if your quickstart mentioned that a common pitfall is overwritting some very common Unity Functions. Provide a little list of the most common ones to watch for:
Awake()
Start()
OnEnable()
OnDisable()
etc....
mention that they should call call the base.Awake(), base.Start(), base.OnEnable(), etc...
Then provide a link to your documentation to your uber awesome Diagnostic Tool which describes how they can look for these issue and other issue that might appear.
Love your DxMessaging
Use Case / Motivation
it is so that I can find the answer to this common issue I keep stumbling on in the documentation and do not have to keep messaging the creator, who I might say is an guy and spectacular programmer.
Proposed Solution
See above in feature description
Alternatives Considered
No response