Changelog

1.0.0 — Initial release

No release date was present in the source material.

Added

• Hierarchical Gameplay Tags with dot-separated paths.
• Central Game Creator Gameplay Tags settings page.
• Tag creation, rename, reparent, delete, duplicate, search, import, export, and validation workflows.
• Tag details with path, parent, description, GUID, and hierarchy information.
• Searchable tag pickers for individual tags and containers.
• GameplayTagComponent with Container and Single Tag modes.
• Runtime mutation, query, redirect, hierarchy, validation, and event APIs.
• Game Creator Actions for tag mutation, exclusive groups, object lookup, filtering, raycasts, and overlaps.
• Game Creator Conditions for tags, containers, parent branches, equality, emptiness, and object-to-object comparisons.
• Game Creator Events for tag changes, exclusive-child changes, triggers, and collisions.
• Value and property support for Gameplay Tags and Gameplay Tag Containers.
• Game Creator save memory for runtime component tags.

Runtime and production work

• Component reads return defensive copies; mutations go through component APIs.
• Enabled components are tracked for object queries.
• Registry child and descendant lookups use rebuilt caches.
• Container matching avoids unnecessary query allocations in hot paths.
• Component-backed events use direct subscriptions.
• Inspector mutations use Unity Undo and dirty handling.
• Validation reports invalid paths, duplicate paths, missing redirect targets, and redirect cycles.

Requirements recorded with the release

• Game Creator 2 Core is required.
• The development workspace used Unity 6000.3.4f1.
• Minimum supported Unity and Game Creator 2 versions were not recorded.

Upgrade notes

This was the first documented public release, so no migration from an earlier public version was required. Projects that used pre-release builds were advised to:

1. verify that the tag database loads;
2. inspect representative prefabs with GameplayTagComponent;
3. validate after tag rename, import, or redirect changes; and
4. use component mutation methods rather than changing copied read containers.

Versioning convention

Future entries should retain supplied version numbers and release dates and separate added, changed, fixed, deprecated, removed, and migration information. Do not add a date or version until it is confirmed by a release artifact.