TagSet Tags (Professional)

J2 Tag Manager builds on top of Unreal Engine’s native tag system. The plugin does not introduce a separate runtime storage format for tags. Instead, TagSet Tags are still stored directly on actors and components using Unreal Engine’s standard Actor Tags and Component Tags.

This is an important part of the system design. J2 Tag Manager is not meant to replace Unreal’s native tag handling. Its purpose is to make tag workflows easier to organize, easier to maintain, and more scalable for larger projects.

TagSet Tags

TagSet Tags are the managed tags used by the structured tagging workflow in J2 Tag Manager.

A TagSet Tag is intended for structured, long-term use. It belongs to a managed system and carries additional metadata that can be used throughout the editor.

Tag Structure

A TagSet Tag follows a hierarchical path structure using . as a separator.

A simple example looks like this:

J2.Test

In this example:

J2 is the TagSet prefix
Test is the actual tag

A more structured example looks like this:

J2.Hello.Test

Here, the path is interpreted as follows:

J2 is the TagSet prefix
Hello is the group
Test is the actual tag

The final segment in the path is always treated as the tag itself. Any preceding segments are treated as part of the hierarchy.

Prefixes and Parent TagSets

Each TagSet defines its own prefix. This prefix is automatically applied to all tags created inside that TagSet.

If a TagSet has a parent TagSet, the final tag path can effectively contain multiple prefix levels. This allows larger projects to build more structured naming hierarchies without losing consistency.

For example, a tag path can become more deeply nested when parent-child TagSet relationships are used to build a broader namespace.

Tag Metadata

In addition to the full tag path, each TagSet Tag stores a set of metadata that is used by the plugin throughout the editor.

Full Tag

The Full Tag is the complete tag path, including prefix and groups.

Example:

J2.Hello.Test

This is the value that is ultimately stored on the actor or component.

Display Name

The Display Name is a user-friendly name for the tag. It can be set when the tag is created and later edited in the Tag Manager or Level Tag Manager.

This allows the editor UI to display a more readable label without changing the actual stored tag path.

Highlighting Color

Each tag can define a Highlighting Color. This color is used by the Viewport Overlay system when visualizing tagged objects in the level.

This makes it possible to quickly identify specific tags directly in the viewport.

Usage Override

The Usage Override defines in which context a tag can be used.

A tag can be configured for:

Actor Tags
Component Tags
Both
or to inherit the default usage defined by the TagSet

If a TagSet defines a global usage mode, all contained tags follow that rule unless they explicitly override it.

A tag can also define a Tooltip. This tooltip is shown wherever the tag is hovered in the editor and is intended to provide a short description or hint about the tag’s purpose.

This is especially useful in larger projects where tags may not be self-explanatory from the path alone.

Behavior Assets

TagSet Tags can reference Behavior Assets as part of the structured automation workflow in J2 Tag Manager Professional.

Behavior Assets can be assigned directly to an individual tag, but they may also come from higher levels of the hierarchy such as the owning group or TagSet. This allows behavior to be defined either locally for a specific tag or more broadly for a larger part of the tag structure.

Multiple Behavior Assets can be assigned to the same tag, and individual Behavior Assets can be reused across different TagSets, groups, or tags.

Some Behavior Assets also expose configurable rule input values. When supported, these values can be adjusted directly in the Tag Manager panel for the specific reference.

Behavior Assets are documented separately because they represent a larger system with their own concepts, event flow, and logic model.

TagSet Tags and Long-Term Use

TagSet Tags are designed for long-term project organization. They are structured, maintainable, and much easier to scale than ad-hoc tag lists.

For small experiments or temporary workflows, Quick Tags may be the faster option. For production-ready organization, TagSet Tags are the recommended approach.

15 März 2026