Ember
Loading...
Searching...
No Matches
Parser Configuration

How to configure Ember to read different XML formats. Use this when your behavior tree files use a different structure than the default.

When to Use This

  • Your XML uses different element names (e.g. not BehaviorTree, Sequence)
  • You're using a custom or legacy format
  • Files fail to load and the error suggests a format mismatch

For standard BehaviorTree.CPP format, you usually don't need to change anything.

Opening Parser Configuration

Tools > Parser Configuration

Profiles

A profile is a named set of parser settings. You can:

  • Select a profile from the dropdown (e.g. "BehaviorTree.CPP v4", "Generic")
  • Create a new profile for your format
  • Edit an existing profile
  • Delete profiles you no longer need

Main Settings (User Perspective)

Setting What it controls
Root element Name of the top-level XML element (e.g. root)
Tree element Name of the element that defines a tree (e.g. BehaviorTree)
Tree ID attribute Attribute that holds the tree name (e.g. ID)
Node element How composite nodes are named (e.g. Sequence, Selector)
Blackboard format How blackboard entries are defined in XML

Built-in Profiles

Profile Use when
Default Standard BehaviorTree.CPP v4 format
Generic Flexible format for custom schemas
Legacy Older BehaviorTree.CPP v3 format

Validation Options

Option Effect
Validate structure Check that the XML structure is valid
Allow unknown nodes Permit node types not in TreeNodesModel
Preserve whitespace Keep indentation and line breaks when saving

See Also