Play Mode and Multiplayer Play Mode

Awesome Hierarchy remains available while the Editor is playing. Group chips, native Search intersection, expansion, selection, automatic icons, notes, guide lines, and the status bar continue to work.

Read-only behavior#

Play Mode is intentionally read-only. Group creation, marking, renaming, appearance changes, notes, setup copying, and every metadata-file mutation are blocked. Appearance popups remain available for inspection and explain why editing is disabled.

Runtime-created GameObjects can receive automatic icons and participate in the current filtered view, but they cannot receive persistent Awesome Hierarchy metadata.

Session badges#

The status bar shows the session context when appropriate:

• PLAY in the main Editor during Play Mode.
• MAIN for a Multiplayer Play Mode Editor launched as Player1.
• PLAYER N for other named Multiplayer Play Mode virtual Editors.

Filter restoration#

Each native Hierarchy window owns its active group filter. Entering or leaving Play Mode, a domain reload, or a scene reload restores that filter from the stable scene GUID and local file ID, even when Unity assigns a different transient object identity.

Multiplayer Play Mode#

Support does not require a package dependency. Virtual Editors are detected from Unity's documented -name launch argument. Player1 is treated as the main Editor; other named instances are read-only and keep their filter state inside their own Editor process. They never write to ProjectSettings/AwesomeHierarchy.