Team Collaboration
Version-control files, safe writes, external refresh, and scene copies.
Files to commit
Awesome Hierarchy stores one deterministic JSON file per saved scene:
ProjectSettings/AwesomeHierarchy/Scenes/<scene-guid>.json
Commit ProjectSettings/AwesomeHierarchy to Git, Unity Version Control, or another version-control system. Do not add this directory to an ignore file. Active group chips, collapsed bars, and other workstation-only view state are not written there.
The current schema stores root-group records, optional appearance records for ordinary GameObjects, and notes for both. Records use stable Unity local file IDs. Readable object names are included as snapshots for diffs, while the scene remains the source of object names and hierarchy order. Note line endings are normalized to avoid operating-system-only changes.
External changes and safe writes
Awesome Hierarchy reloads metadata when Unity regains focus, scenes or project assets change, and after Tools > Awesome Hierarchy > Refresh Groups.
Before changing a file, the asset reloads its latest contents and applies the requested operation to that state. A temporary file is written first and then moved into place.
Files containing version-control conflict markers, invalid JSON, a newer unsupported schema, or a read-only file attribute are never overwritten. Resolve the conflict, update the asset, or check out the file, then choose Refresh Groups.
Duplicated scenes
Duplicating a scene asset does not automatically copy its Awesome Hierarchy metadata.
Use Tools > Awesome Hierarchy > Copy Group Setup From Scene..., then select the source and target scene. The operation copies group registrations and their group appearance and notes. It succeeds only when every source group local file ID exists as a root object in the target scene; otherwise nothing is written.
Ordinary object appearance records are not copied by this command.