Validate Using Attributes

One of the most common ways to use the validator is to add attributes to your classes and class members.

The Odin Validator plugin adds the ability to scan and fix issues across your entire project, but these attributes also work without it.

The currently supported built-in attributes are:

• RequireComponent
• AssetsOnly
• FilePath, when RequireExistingPath is set to true
• FolderPath, when RequireExistingPath is set to true
• ChildGameObjectsOnly
• SceneObjectsOnly
• DetailedInfoBox, when an error is shown
• InfoBox, when an error is shown
• Required
• RequiredIn
• ValidateInput
• MinValue
• MaxValue
• Range
• PropertyRange
• MinMaxSlider

Let's have a look at an example of how a properly validated component might look like.

public class Player : MonoBehaviour
{
    [Required]
    public string Name;
    
    [MinValue(0), MaxValue(100)]
    public int Health;
    
    [ChildGameObjectsOnly]
    public GameObject Child;
}

Using these attributes diligently throughout your project will make sure your project remains stable as it grows and will make it easier to onboard new team members.

The built-in attributes cover a wide range of validation needs, but sometimes you will still have to create custom validators to validate your components. You can learn more about creating custom validators in the following tutorials.