Domain Definition
The first step in setting up a planning domain is to create a domain definition. To begin, create a new asset of type "Domain Definition" via the asset creation menu (Create -> AI -> Domain Definition) or the Create menu from the project window.

You can edit the domain definition in the authoring pane, which is used to define enumerations, traits, and aliases.
Enumerations
The trait-based domain language supports most basic data types, such as int, float, bool, and enum. For the latter, the authoring tool allows you to define custom enumerations to be used by properties in your domain's traits.

Traits
Traits are the fundamental data which represents your game/simulation. Each trait specifies a quality which objects can possess, such as the ability to be carried or to be used as a weapon. Each trait is composed of properties which reflect attributes specific to each trait. For example, consider creating a trait "Consumable" which marks objects that can be consumed. Such a trait may possess a property "Consumable Type" (an enumeration) which denotes if the consumable is food or drink. In this way, traits are defined by:
- A name
- A list of typed properties

Aliases
As an authoring shorthand, aliases provide a means of referring to established sets of traits on an object. Such aliases can be used when specifying constraints in the plan definition.

Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.