Known Limitations | Awesome Hierarchy

Version 1.0.0.08.26 requires Unity 6000.5 or newer and was release-validated with Unity 6000.5.9f1.
Placement inside the native Hierarchy relies on the internal SceneHierarchyWindow IMGUI layout. A future Unity update may require an Awesome Hierarchy compatibility update.
Groups must be root GameObjects and cannot be nested.
Duplicating a scene asset does not automatically duplicate its Awesome Hierarchy metadata. Use the explicit Copy Group Setup command.
The icon picker uses the built-in Awesome Hierarchy catalog backed by Unity editor icons. Importing arbitrary image files as hierarchy icons is not supported.
During a complete internal hierarchy-tree rebuild, Unity can briefly restore its default icon. Awesome Hierarchy reapplies the resolved icon on a following native row repaint.
Active group filters and collapsed group bars are session state, not project data. They are not restored after restarting Unity.
Group, appearance, and note metadata are editor-only and are unavailable in a player build.
Play Mode and Multiplayer Play Mode virtual players are read-only. Runtime-created objects cannot receive persistent metadata.
Invalid, conflicted, read-only, or newer-schema JSON remains read-only until the underlying issue is corrected or Awesome Hierarchy is updated.
Version 1.0 does not expose a supported scripting API for creating, removing, or editing groups. These operations are provided through the editor UI and Shortcut Manager.