In this Unity tutorial I will demonstrate an effortless way of Validating Builds. No more making broken builds, now you'll be able to validate them ahead of time.
A must watch for all those tools programmers who seek the truth.
#Never Release a Broken Unity Game Again
river elk
dense orbit
damn that's really good
any editor script to prevent these sorts of deletion in the first place?
or throw an error message, when a reference is about to get nulled
river elk
OnValidate is your best friend here .. in my own system if a "required" field is nulled it marks the field red and all the gameobject names in the path to the component in the hierarchy are written in red. If you press play it gives you an error in the console.
I dont immediately put out an error as I found it annoying when I was changing references or adding components that didnt auto fill the fields in the Reset method.
dense orbit
OnValidate is your best friend here .. in my own system if a "required" field is...
how did you paint fields red? custom attributes for the required stuff?
river elk
I have an attribute called Required and that has a property drawer that sees if the field (object, reference, generic or string) is empty .. and if it is then it draws a red box around it.
Then in OnValidate a property IsValid on the class is marked to false. The Monobehaviour has an custom IValidate interface which a drawing routine for the hierarchy picks up and renders the hierarchy path red
This links up to the whole Validate builds system from the video and a logging system separate from the Console so that doesn't get polluted
To top it all off the Validation system logs potential fixes which are just methods I create in the MonoBehaviour, when OnValidate finds a problem it sees if a fix method is available .. then I have a button that comes up if they are available which allows the user to simply click and get the fix done