Tag Director
Review draft. This source page has not completed website editorial and release-specific verification.
Tag Director 1.1.1 is an Unreal Engine plugin for Gameplay Tag catalogs, inventory, validation, and registry maintenance. It has a runtime data/API module and an Editor module.
Director Suite tools
Section titled “Director Suite tools”- Tag Director Analyzer — read-only inventory, usage counts, sources, statuses, references, search, and export. Open it at Tools > Director Suite > Analysis & Diagnostics > Tag Director Analyzer. It has no registry mutation action. An incompatible configured registry source is identified and skipped while other enabled sources continue scanning.
- Tag Director Editor — design-time authoring for the project Gameplay Tag registry. Open it at Tools > Director Suite > Authoring > Tag Director Editor. Registry Diff is embedded in this tab; Apply adds catalog tags and marks target tags absent from the catalog as deprecated.
Configure the catalog and project registry under Project Settings > Plugins > Tag Director. The configured registry DataTable remains the project’s registered tag source. Tag Director does not add registry entries during load or cook.
Runtime module
Section titled “Runtime module”TagDirectorRuntime provides:
UTD_TagBundle, a primary data asset containing tag rows and soft references to dependencies.UTD_TagCatalog, the project’s set of root bundles and optional DataTables.UTD_TagPolicy, project settings for allowed domains, forbidden roots, naming rules, and unknown/deprecated severity.UTD_TagRegistryBPLibrary, a Blueprint helper for reading bundle tag names.
Soft references avoid forcing all tag assets into memory at runtime. Catalog traversal occurs in Editor workflows and de-duplicates dependency visits.
Analyzer behavior and limits
Section titled “Analyzer behavior and limits”The Analyzer scans Blueprint assets under /Game and, when enabled, enabled content-bearing plugins. It inspects reflected Gameplay Tag properties, containers, graph pin defaults, and optionally actors/components in the loaded Editor world. Scans can compile Blueprints whose generated class is missing or stale. Results are read-only; they are not a proof that no serialized text, config, external data, unloaded maps, or runtime-generated values refer to a tag.
Completed inventory results are cached in memory by catalog, registry, scan options, and per-tag asset limit. Asset Registry changes, map opens, and world saves invalidate relevant caches. TagDirector.Tags.RefreshUsage forces a registry-usage rebuild. Cancelled scans discard partial results.
Registry Diff behavior
Section titled “Registry Diff behavior”Registry Diff is embedded in Tag Director Editor. It compares catalog sources with the configured registry. Apply adds missing catalog tags and marks target rows absent from the catalog as deprecated. The current Editor workflow does not delete rows or apply replacements. Apply requests a save of the target DataTable, saves Gameplay Tags settings, then refreshes Gameplay Tags so Editor pickers can observe the updated registry. This is design-time mutation and belongs only to Tag Director Editor; the current workflow does not provide transaction-based Undo.
Large project guidance
Section titled “Large project guidance”- Keep bundles cohesive by domain or feature and use dependencies for shared groups.
- Leave loaded-level scans off for routine inventory work; enable them when current-world instance data matters.
- Disable plugin-content scanning when only
/Gamematters. - Use stable hierarchical names such as
Domain.Feature.State. Replacement metadata may be recorded in catalog rows, but the current Registry Diff does not resolve or apply replacements. - Review usage counts and referencing assets before removal. Scanners currently focus on Blueprints and the optional loaded Editor world; arbitrary non-Blueprint assets, text/config, external data, unloaded maps, and runtime-generated values may not appear.
UE version support
Section titled “UE version support”This release targets Unreal Engine 5.7. Compatibility changes remain inside the plugin; no Engine source changes are expected.
Migration from KeystoneCore
Section titled “Migration from KeystoneCore”The old KeystoneTagsRuntime and KeystoneTagTools modules were recreated as TagDirectorRuntime and TagDirectorEditor. Replace old UKS_* types with their UTD_* equivalents. Recreate old profile selections as catalog bundle roots and migrate service-map tag tables into the catalog’s TagTables array. Old binary asset instances may need recreation or resaving because reflected class paths changed.
Ownership
Section titled “Ownership”Copyright (c) 2025 Tuxedo Cat Software. All rights reserved.