batihandev/unity-mcp-skills/scene

Unity Scene Skills

Overview

Control Unity scenes - the containers that hold all your GameObjects.

Common Mistakes

DO NOT (common hallucinations):

• scene_delete / scene_rename do not exist → delete scene files via asset_delete, rename via asset_move
• scene_list does not exist → use scene_get_loaded (loaded scenes) or asset_find with t:Scene (all scene assets)
• scene_find_objects is a simple name/tag/component filter; for regex/layer/path search use gameobject_find (Full-Auto)

Routing:

• For detailed hierarchy tree → use perception module's hierarchy_describe
• For scene statistics → use perception module's scene_summarize
• For screenshot → scene_screenshot (this module) uses the Scene View; for a Game Camera capture use the native Unity_Camera_Capture tool

Skills Overview

Skills

scene_create

Create a new scene.

scene_load

Load a scene.

scene_save

Save the current scene.

scene_get_info

Get current scene information.

No parameters.

Returns: {success, name, path, isDirty, rootObjectCount, rootObjects: [name]}

scene_get_hierarchy

Get full scene hierarchy tree.

Returns: {success, hierarchy: [{name, instanceId, children: [...]}]}

scene_screenshot

Capture a screenshot.

scene_get_loaded

Get list of all currently loaded scenes.

No parameters.

Returns: {success, scenes: [{name, path, isActive, isDirty}]}

scene_unload

Unload a loaded scene (additive).

scene_set_active

Set the active scene (for multi-scene editing).

scene_find_objects

Search GameObjects by name pattern, tag, or component type. For advanced search (regex, layer, path) use gameobject_find.

Returns: {success, count, objects: [{name, path, instanceId, active, tag}]}

Recipe path rule: ../../recipes/scene/<command>.md

Best Practices

1. Always save before loading a new scene
2. Use additive loading for UI overlays
3. Keep scene hierarchy organized with empty parent objects
4. Use scene_get_info to verify scene state
5. Screenshots are saved to project root by default