Access Project Settings › Gameplay Tags to author your project’s tag vocabulary.

The panel is a single filterable tree over your whole project’s tags — there’s no separate “tag files” concept for authoring any more; every tag lives in one place. Each tag can be toggled between two states:

• Registered — hierarchy-aware, live in the runtime registry, baked into generated code. Only Registered tags support set operations (“Contains Tag”, “Is Parent”, etc.) and show up in autocomplete.
• Unregistered — still authored and saved (nothing is lost), but not in the runtime registry and not baked. A holding area for a tag you’re still deciding about, or one that doesn’t need hierarchy-aware queries. An unregistered tag can still be added to a GameplayTagCollection, but set operations against it (is parent of, contains, etc.) always return false.

Add / Edit / Delete

Click a tag in the tree to open Gameplay Tag Editor, a small popup for renaming or deleting it (and, for debugging, viewing its live interval position in the hierarchy). Type a new dot-path into the search/add box and confirm to add a fresh tag to the tree.

Tags From Other Sources

Other Heathen tools that own their own tags — an Ogham Storyteller story’s node tags, for example — register and bake those tags themselves rather than storing them in this panel. This section lists them anyway, read-only, grouped by the tool that owns them, plus a catch-all “Other (unattributed)” group for anything registered in the live tag registry that isn’t claimed by your project’s own list or a known source — so nothing in the system is ever invisible from this one screen, even tags this panel doesn’t own.

Build

Registered tags aren’t available at runtime until they’re baked to code. A Build button bakes your project’s Registered tags to a generated file on demand; a warning banner and the same button appear whenever the generated code has fallen out of date with your current tag list.