unity-inspector

Use SerializeReference for polymorphic data structures in Unity Inspector, allowing flexible composition of derived types without fixed array allocations. This approach supports modular ScriptableObject and MonoBehaviour design when exposing complex, interchangeable serialized settings.

Use private serialized fields instead of public fields in Unity to expose values for authoring while maintaining encapsulation. This strategy prevents external scripts from modifying gameplay tuning values directly, ensuring safe defaults and controlled access during runtime.

Add validation checks for missing references by implementing OnValidate in your MonoBehaviour or ScriptableObject. This method executes in the editor, allowing you to detection null references, enforce safe defaults, and log warnings when serialized settings are incomplete.

Yes, this approach works for both MonoBehaviour and ScriptableObject scenarios in Unity. The strategies for field exposure, attribute annotations, and OnValidate validation apply equally to both for creating clear serialized settings and safe default values.

The best way to group related settings in a Unity Inspector is using Header and Space attributes. These visually separate serialized fields into logical sections, improving authoring UX by making the component configuration self-explanatory and organized.

Use RequireComponent to enforce necessary dependencies on GameObjects, preventing missing reference errors at runtime. Use CreateAssetMenu to define clear authoring paths for ScriptableObject instances, ensuring safe defaults and organized asset creation during tuning.