Scene Inspect
Inspect scene hierarchy, find objects, and read component data without mutating anything. This is the read-only sibling of unity-gameobject-edit.
Use When
- The user wants to inspect the current scene before making changes.
- The user asks where a GameObject, component, or animator state lives.
- The user wants a hierarchy summary, scene inventory, or reference analysis.
Do Not Use When
- The task is to create new scenes; use
unity-scene-create. - The task is to mutate existing objects; use
unity-gameobject-edit. - The user only needs source-code navigation with no scene context; use
unity-csharp-navigate.
Preferred Flow
- Start with
get_scene_info,list_scenes, orget_hierarchyto scope the work. - Locate candidates with
find_gameobjectorfind_by_component. - Inspect targets with
get_gameobject_details,get_component_values, or animator queries. - Use
analyze_scene_contentswithincludeInactivefor broad audits.
unity-cli raw get_hierarchy --json '{"nameOnly":true}'
unity-cli raw find_gameobject --json '{"name":"Player"}'
unity-cli raw get_component_values --json '{"gameObjectName":"Player","componentType":"Transform"}'
unity-cli raw analyze_scene_contents --json '{"includeInactive":true}'
Examples
- "Show the current scene hierarchy and find the player camera."
- "Inspect the
Transformvalues onPlayer." - "Tell me which animator state the character is in right now."
References
- runtime-checklist.md: connection and instance prerequisites.
- scene-inspection-playbook.md: step-by-step inspection flow for large or duplicated scenes.