Skip to content
J2 Tags

Working with TagSets

Pro

TagSets are Pro Data Assets for defined, structured tags. They are the recommended source of truth for tags that should remain stable across a project.

J2 Tag Set asset with prefix, tags, groups, scopes, redirects, and tooltips

When to Use Them

Section titled “When to Use Them”
SituationUse TagSets when
Tags are shared across levels or teamsThe tag name needs stable project meaning.
Tags need validationScope, definitions, and Diagnostics matter.
Tags need Asset scopeContent Browser assets should carry J2 metadata.
Tags may be renamedRedirects should preserve old references.
Tags drive automationBehaviors should be mapped to tags, groups, or TagSets.

Concept

Section titled “Concept”

A TagSet has a prefix. Each tag inside the TagSet has a local name. The full tag is built from the prefix and the local name.

TagSet Prefix: AI
Local Tag: State.Patrol
Full Tag: AI.State.Patrol

TagSet Fields

Section titled “TagSet Fields”
FieldPurpose
Display NameUI label for the TagSet.
Tag PrefixShared prefix for all tags in the TagSet.
DescriptionExplanation for users and tooltips.
ScopeDefault scope when groups or tags do not override it.
Local Policies / Behavior SectionsBehaviors that apply at TagSet level.
Behavior Input OverridesValues that can be customized at mapping level.
TagsConcrete tag definitions.
GroupsStructural groups and scope/behavior inheritance.

Tag Fields

Section titled “Tag Fields”
FieldPurpose
NameLocal tag name without prefix.
Display NameUI label in pickers, inspector, and overlay.
Scope OverrideOptional scope for this tag.
TooltipExplanation for users.
Highlighting ColorColor used in overlay and UI highlights.
Redirect FromOld full tag names that redirect to this tag.
BehaviorsLocal behavior assets or sections.
Behavior Input OverridesValues that can be customized at mapping level.

Groups

Section titled “Groups”

Groups structure local tag names, for example State, State.Combat, or Interaction. Groups can inherit or override scope and behaviors.

Section titled “Recommended Practice”
  • Use short, clear prefixes.
  • Use groups for meaning, not only visual organization.
  • Add tooltips for tags other people will use.
  • Use redirects when renaming instead of untracked bulk replacement.
  • Add Asset scope deliberately so Content Browser metadata stays meaningful.
  • Use the Tag Manager for daily editing; use the raw Data Asset view mainly for inspection.
Section titled “Related Pages”