[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BVHTT1NVHJFSKGZ94VXJK7":3,"skill-same:01M6BVHTT1NVHJFSKGZ94VXJK7":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":60,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6BVHTT1NVHJFSKGZ94VXJK7","ez-mcp",null,"Drive a running ezEditor or ezPlayer\u002Fgame from an agent over MCP - launch one with a port, then call tools to inspect and change a live project. Use for ezEngine tasks that need the running app rather than files on disk. Triggers - ezEditor, ezPlayer, ezEditorProcessor, MCP server, editor-mcpport, mcpport, transform asset, asset dependencies, asset browser, open document, edit scene, build a scene, game object, component, prefab, property grid, selection, reflected types, RTTI, CVar, editor action, play the game, screenshot, inject input, press key, step frames, export project, create project, build the C++ plugin.","ezEngine\u002FezEngine","ezEngine","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7082461?v=4","01M6BVHA0EZGW8WD6GQ8G3HJV3","ezEngine Project","01M6BVHA4YBS7ZFBN8Y2GGZ5CW",2040,"MIT","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.claude\u002Fskills\u002Fez-mcp\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"ez mcp","MCP","Tools","inspect","types","port","press key","app","project","selection","files","game","open","disk","server","screenshot","browser","play","create","tasks","plugin","component","change","launch","editor","mcp server","2026-11-10 10:12:30",false,"---\nname: ez-mcp\ndescription: Drive a running ezEditor or ezPlayer\u002Fgame from an agent over MCP - launch one with a port, then call tools to inspect and change a live project. Use for ezEngine tasks that need the running app rather than files on disk. Triggers - ezEditor, ezPlayer, ezEditorProcessor, MCP server, editor-mcpport, mcpport, transform asset, asset dependencies, asset browser, open document, edit scene, build a scene, game object, component, prefab, property grid, selection, reflected types, RTTI, CVar, editor action, play the game, screenshot, inject input, press key, step frames, export project, create project, build the C++ plugin.\n---\n\n# Driving ezEditor and the game over MCP\n\nTwo hosts, same protocol, **separate ports and separate tool lists**:\n\n| Host | Started with | Answers about |\n| --- | --- | --- |\n| **Editor** (`ezEditor.exe`) | `-editor-mcpport \u003Cn>` | assets, documents, scene contents, reflected types, editor actions, the C++ plugin |\n| **Game** (`ezPlayer.exe`, or the engine process the editor plays in) | `-mcpport \u003Cn>` | what is rendered and simulated: screenshots, input, frames, the clock |\n\nNeither is a registered project MCP server: neither runs most of the time and the port is per run. Start\none, then talk to it. For anything the file system already answers, read the files instead.\n\n## Launching\n\n```shell\n# editor\nezEditor.exe -project \"Data\u002FSamples\u002FPacMan\" -unattended -editor-mcpport 7399\n# game, standalone - no editor needed\nezPlayer.exe -project \u003Cproject-folder> -scene \u003Cpath\u002Fto\u002FScene.ezBinScene> -profile Default -unattended -mcpport 7401\n```\n\nBinaries are in `Workspace\u002F\u003Cworkspace>-output\u002FBin\u002FWinVs2026Dev64\u002F`.\n\n- **`-unattended` is required for the editor, and should be passed to games as well.** Otherwise a modal dialog during startup (e.g. \"compile the C++ plugin?\") hangs it before it serves anything. Tool calls suppress dialogs themselves; startup does not.\n- Launch detached (`start \"\"` \u002F `Start-Process`); it runs until told to quit.\n- Startup takes seconds - **poll the port**, do not sleep a fixed time.\n- Pick a port other than the default 7391 so a user's own editor keeps working.\n- Without `-mcpport` the game starts **no** server at all.\n- `-editor-mcpport` and `-mcpport` are separate names on purpose: the editor forwards its whole command\n  line to its engine process, which takes `-editor-mcpport` + 1. Read that port from the editor's\n  `app_info` as `engineMcpPort` rather than computing it.\n- `-project` or `-createProject` keeps the dashboard away.\n\n## Calling tools\n\n```shell\ncurl -s -X POST http:\u002F\u002F127.0.0.1:7399\u002Fmcp -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"name\":\"project_info\",\"arguments\":{}}}'\n```\n\n`{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}` returns every tool with its full description and input\nschema. **Read that list before guessing** - the descriptions carry the argument semantics and the\nwarnings, plugins can add tools, and the two hosts do not have the same list. Results are JSON in\n`content[0].text`; failures carry `\"isError\":true` and a sentence saying what to do instead.\n\nTo register a running host for the session:\n`claude mcp add --transport http ez-editor http:\u002F\u002F127.0.0.1:7399\u002Fmcp`.\n\n## What is there\n\nBoth hosts: `app_info`, `app_ping`, `app_quit`, `app_command_line_options`, `log_read`, `log_write`,\n`cvar_list`, `cvar_set`, `rtti_find_types`, `rtti_type_info`, `rtti_type_properties`,\n`rtti_derived_types` - each answering for *its own* process.\n\n| Editor only | |\n| --- | --- |\n| Project | `project_info`, `project_export` |\n| C++ plugin | `cpp_status`, `cpp_generate`, `cpp_build` |\n| Assets | `asset_types`, `asset_find`, `asset_info`, `asset_uses`, `asset_thumbnail`, `asset_transform`, `asset_health`, `asset_history`, `asset_processor`, `asset_importers`, `asset_import` |\n| Documents | `document_types`, `document_list`, `document_open`, `document_create`, `document_save`, `document_close`, `document_focus`, `document_delete` |\n| Contents | `object_tree`, `object_properties`, `object_modify`, `object_undo`, `object_drop_asset` |\n| Scene layers | `scene_layers` |\n| Node graphs | `graph_info`, `graph_node_templates`, `graph_add_node`, `graph_move_nodes`, `graph_connect`, `graph_disconnect` |\n| Selection | `selection_get`, `selection_set` |\n| Actions | `action_list`, `action_state`, `action_execute` |\n\n| Game only | |\n| --- | --- |\n| Rendering | `app_screenshot` |\n| Time | `game_info`, `game_wait`, `game_pause`, `game_speed` |\n| Input | `input_slots`, `input_set`, `input_sequence` |\n\nStart with `project_info` on the editor (paths and asset states are relative to what it reports), and\nwith `game_info` on the game.\n\n## Editing a document\n\nNothing works on a closed document, and nothing opens implicitly:\n\n1. `asset_find` → path or guid. Its paths start with the data directory name\n   (`Testing Chambers\u002FScenes\u002FDynamicFog.ezScene`) - that is the form other tools want.\n2. `document_open` with `path` (not `document` - see below) and `focus` false, unless the user is meant\n   to look at it.\n3. `object_tree` → guids. Asset documents have one top level object, so `object_properties` with only\n   `document` already reads an asset's whole configuration. Scenes have many.\n4. `object_properties` \u002F `object_modify`.\n5. `document_save` - nothing saves on its own, and the asset system sees nothing until it is saved.\n\n**Which argument names a tool takes**, because guessing costs a round trip and they follow a rule:\n\n| Argument | Tools | Why |\n| --- | --- | --- |\n| `path` | `document_open`, `document_create`, `document_delete` | act on a file that need not be open yet |\n| `document` | `object_*`, `selection_*`, `document_save`\u002F`_close`\u002F`_focus`, and the `document` argument of the action tools | act on an already open document |\n| `asset` | `asset_info`, `asset_transform`, `asset_thumbnail`, `asset_uses` | act on the asset database, open or not |\n| `name` | `action_execute`, `action_state`, `rtti_*`, `cvar_set` | the thing named is not a document at all |\n\nSo it is `document_open` `path`, `action_execute` `name`, `rtti_derived_types` `name`. When in doubt read\nthe schema from `tools\u002Flist` rather than guessing - and note that a wrong name fails with a message that\nsays the right one.\n\nA scene's game objects and components live in the same hierarchy, told apart by the parent property they\nsit in. Building one is all `object_modify`:\n\n```\naddObject   property \"Children\",   type \"ezGameObject\"          -> child object ('object' \"root\": top level object)\naddObject   property \"Components\", type \"ezPointLightComponent\"  -> component on it\nset         property \"Name\" \u002F \"LocalPosition\" \u002F any component property\nmoveObject  newParent \u003Cguid>|\"root\" | duplicateObject | deleteObject  (each takes everything below it)\n```\n\nTo place an asset, `object_drop_asset` runs the editor's own drag & drop handler: a mesh becomes an object with\nan `ezMeshComponent`, a prefab one with an `ezPrefabReferenceComponent` (`prefabInstance` true: an editable,\nlinked prefab instance, like Shift+drag), and so on, at `position` and under `parent`. `attachTo` adds the\ncomponent to an existing object instead, `targetComponent` assigns a material to a mesh component.\n\nScenes can have **layers**, separate `.ezSceneLayer` documents in `\u003CScene>_data`, listed by `scene_layers`. Only\nthe active layer is editable, and while a layer is active the scene's objects are that layer's. The object tools\ntherefore refuse a scene or layer that is not active, and say which one is. `scene_layers` `setActive` switches\n(the user sees it), after which the scene and the layer document both reach the layer's objects. Switch back to\n`Scene` to edit the scene's own objects.\n\n`rtti_derived_types` of `ezComponent` lists component types; `rtti_type_properties` gives property\nnames, value types and enum values before writing any. Vectors and colours go in as they come out\n(`{\"x\":1,\"y\":2,\"z\":3}` or `[1,2,3]`). `selection_set` is worth calling even when it changes nothing - it\nis how the user sees which object is meant, and `selection_get` answers \"this object\".\n\n## Editing a node graph\n\nVisual scripts, materials using a visual shader, render pipelines, state machines, animation graphs and ProcGen\ngraphs are node graphs. Nodes and connections are ordinary top level objects in `object_tree`, but pins, node\npositions and connecting only exist in the graph_* tools:\n\n1. `graph_info` - nodes with position and pins (name, `dataType`, `description`, connection count), connections as\n   source node + output pin -> target node + input pin, and `otherObjects` (the asset's own settings).\n   `graphInUse` false: the document ignores its graph (a material only uses it with `ShaderMode` `Custom`), and\n   adding nodes or connections is refused until that is changed.\n2. `graph_node_templates` with `contains` - the node creation menu. Visual scripts have thousands of entries, many\n   sharing one node type and differing only in pre-filled properties, so add by `path`, not by type.\n3. `graph_add_node` (`template`, `position`) returns the node with its pins. Node properties are set with\n   `object_modify` as usual; a property can change the pins (e.g. a pin count), so re-read them afterwards.\n4. `graph_connect` goes from an output (`source`) to an input (`target`). Pins that take one connection get it\n   replaced, reported under `removedConnections`. Pin names can be empty strings.\n5. `graph_disconnect`, `graph_move_nodes`. `object_modify` `deleteObject` on a node also removes its connections.\n\nConnection objects cannot be created with `addObject` and their `Source`\u002F`Target`\u002F`SourcePin`\u002F`TargetPin` cannot be\nset - use connect\u002Fdisconnect. Other properties of a connection (a state machine transition) are set with\n`object_modify`. Lay out left to right, ~300 units apart, y pointing down.\n\n## Driving the game\n\n`gameStateActive` false in `game_info` means nothing is being played - normal for the editor's engine\nprocess until play-the-game runs, and why input does nothing and screenshots time out.\n\n- Start it from the **editor** port: `action_execute` `Scene.GameMode.Play` with the scene document;\n  `Scene.GameMode.Stop` ends it. Both are asynchronous (the editor asks the engine process), so `Stop`\n  reads as disabled for a moment and `game_info` on the game port is the better confirmation.\n- **`app_screenshot` returns a path, not the image.** Read that file. A rendered frame is the evidence a\n  change works; \"did not crash\" is not.\n- **`input_set` then `game_wait`** - input is consumed one frame at a time, so setting a slot alone does\n  nothing. `input_sequence` does a whole set\u002Fwait\u002Ftext\u002Fclear chain in one call. Injected values merge\n  with the real keyboard, larger wins, so a human is never locked out.\n- **`game_wait` takes `frames` or `seconds`** (game time on the global clock). For \"let the game play for a\n  while\" use `seconds` - a frame count lasts however long the frame rate makes it.\n- **Launch games with `-unattended`.** It prevents assert message boxes and the user's mouse and keyboard are \n  ignored and the window doesn't take the focus or capture the cursor. Only `input_set`\u002F`input_sequence` drive the game.\n\n- **`game_pause` stops the engine clock, not necessarily the game's own simulation.**\n- `cvar_list` is worth far more here than in the editor: render passes, physics and AI visualisation are\n  mostly CVars.\n\n## Editor actions\n\n`action_execute` runs global actions by name. Actions of scope `Document` or `Window` need a `document`\nargument (guid or path, already open); so do `action_list` and `action_state`, and that is the only way\nto read their per-document enabled state. Passing `document` to `action_list` also flips `globalOnly`\noff, so `{\"contains\":\"GameMode\",\"document\":\"…\",\"includeState\":true}` is the usual way to find them.\n`Window` actions additionally need a window (`document_open` with `focus` true).\n\n## C++ plugin\n\n`cpp_status` first: `hasCppProject` false means no C++ code at all and `cpp_generate` creates it;\n`compilerUsable` false means CMake will refuse and `cpp_generate` with `useSdkCompiler` is the fix.\nAfter editing sources call `cpp_build`, with `force` when files were added, removed or renamed (CMake\ncollects them at generation time). Both return the full build log - on failure it is the only place the\ncompiler errors are. Then check `pluginBinary` \u002F `pluginBinaryExists`: a build that reports success\nwithout producing the library means the plugin is not in use. Headless equivalent:\n`ezEditorProcessor.exe -project \u003Cpath> -compile` (`-recompile` forces CMake too).\n\n## Creating a project\n\nNo tool for it - a different set of plugins is loaded, so it happens at launch:\n\n```shell\nezEditor.exe -createProject \"C:\u002FProjects\u002FMyGame\" -projectTemplate \"Basic FPS\" -unattended -editor-mcpport 7399\n```\n\nThe directory must be empty or absent; the project opens right away. Without `-projectTemplate` the\nproject is blank, using `-pluginTemplate` (default `General3D`). `-listTemplates` logs the valid names.\n`ezEditorProcessor.exe` takes the same options and quits when done - better when no editor is wanted\nafterwards.\n\n## Rules that are not obvious\n\n- **Every call blocks its host.** One at a time, on the main thread. No progress, no cancel.\n- **Some calls run for minutes**: `asset_transform` over a project, `project_export`, `cpp_build`,\n  `cpp_generate`. Give curl a timeout in tens of minutes.\n- **`app_ping` tells \"busy\" from \"hung\".** It answers only when the main thread is free, so silence\n  during a long call is expected and silence afterwards is not. Take the process id from `app_info` up\n  front - a hung host must be killed by pid, and `app_quit` will not get through either.\n- **`log_read` only sees its own process.** The editor cannot see what the engine logged, or vice versa.\n  `app_info` reports `engineLogFilePattern` for when that process has died.\n- **A failed assert comes back as a tool error** with file, line and expression. That is an engine bug,\n  not bad arguments - retrying will not help. The host keeps answering but has continued past a check\n  meant to stop it, so restart it before trusting anything further, and report the text.\n- **Check `app_info`'s `buildTimestamp` before concluding a tool is missing.** A binary built before a\n  feature returns the same `tools\u002Flist` as one that never had it.\n- **`cvar_set` on a `requiresRestart` CVar does not change what the engine reads.** The response returns\n  `pendingValue` separately; re-reading keeps showing the old `value`, and that is not a failed write.\n- **Quit before rebuilding**: `app_quit` (with `discardChanges` if documents are modified), or the plugin\n  DLLs stay locked and the build fails.\n- **Nothing saves implicitly.** `object_modify` only marks the document modified; `object_undo` reverts.\n","# Driving ezEditor and the game over MCP\n\nTwo hosts, same protocol, **separate ports and separate tool lists**:\n\n| Host | Started with | Answers about |\n| --- | --- | --- |\n| **Editor** (`ezEditor.exe`) | `-editor-mcpport \u003Cn>` | assets, documents, scene contents, reflected types, editor actions, the C++ plugin |\n| **Game** (`ezPlayer.exe`, or the engine process the editor plays in) | `-mcpport \u003Cn>` | what is rendered and simulated: screenshots, input, frames, the clock |\n\nNeither is a registered project MCP server: neither runs most of the time and the port is per run. Start\none, then talk to it. For anything the file system already answers, read the files instead.\n\n## Launching\n\n```shell\n# editor\nezEditor.exe -project \"Data\u002FSamples\u002FPacMan\" -unattended -editor-mcpport 7399\n# game, standalone - no editor needed\nezPlayer.exe -project \u003Cproject-folder> -scene \u003Cpath\u002Fto\u002FScene.ezBinScene> -profile Default -unattended -mcpport 7401\n```\n\nBinaries are in `Workspace\u002F\u003Cworkspace>-output\u002FBin\u002FWinVs2026Dev64\u002F`.\n\n- **`-unattended` is required for the editor, and should be passed to games as well.** Otherwise a modal dialog during startup (e.g. \"compile the C++ plugin?\") hangs it before it serves anything. Tool calls suppress dialogs themselves; startup does not.\n- Launch detached (`start \"\"` \u002F `Start-Process`); it runs until told to quit.\n- Startup takes seconds - **poll the port**, do not sleep a fixed time.\n- Pick a port other than the default 7391 so a user's own editor keeps working.\n- Without `-mcpport` the game starts **no** server at all.\n- `-editor-mcpport` and `-mcpport` are separate names on purpose: the editor forwards its whole command\n  line to its engine process, which takes `-editor-mcpport` + 1. Read that port from the editor's\n  `app_info` as `engineMcpPort` rather than computing it.\n- `-project` or `-createProject` keeps the dashboard away.\n\n## Calling tools\n\n```shell\ncurl -s -X POST http:\u002F\u002F127.0.0.1:7399\u002Fmcp -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Fcall\",\"params\":{\"name\":\"project_info\",\"arguments\":{}}}'\n```\n\n`{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools\u002Flist\"}` returns every tool with its full description and input\nschema. **Read that list before guessing** - the descriptions carry the argument semantics and the\nwarnings, plugins can add tools, and the two hosts do not have the same list. Results are JSON in\n`content[0].text`; failures carry `\"isError\":true` and a sentence saying what to do instead.\n\nTo register a running host for the session:\n`claude mcp add --transport http ez-editor http:\u002F\u002F127.0.0.1:7399\u002Fmcp`.\n\n## What is there\n\nBoth hosts: `app_info`, `app_ping`, `app_quit`, `app_command_line_options`, `log_read`, `log_write`,\n`cvar_list`, `cvar_set`, `rtti_find_types`, `rtti_type_info`, `rtti_type_properties`,\n`rtti_derived_types` - each answering for *its own* process.\n\n| Editor only | |\n| --- | --- |\n| Project | `project_info`, `project_export` |\n| C++ plugin | `cpp_status`, `cpp_generate`, `cpp_build` |\n| Assets | `asset_types`, `asset_find`, `asset_info`, `asset_uses`, `asset_thumbnail`, `asset_transform`, `asset_health`, `asset_history`, `asset_processor`, `asset_importers`, `asset_import` |\n| Documents | `document_types`, `document_list`, `document_open`, `document_create`, `document_save`, `document_close`, `document_focus`, `document_delete` |\n| Contents | `object_tree`, `object_properties`, `object_modify`, `object_undo`, `object_drop_asset` |\n| Scene layers | `scene_layers` |\n| Node graphs | `graph_info`, `graph_node_templates`, `graph_add_node`, `graph_move_nodes`, `graph_connect`, `graph_disconnect` |\n| Selection | `selection_get`, `selection_set` |\n| Actions | `action_list`, `action_state`, `action_execute` |\n\n| Game only | |\n| --- | --- |\n| Rendering | `app_screenshot` |\n| Time | `game_info`, `game_wait`, `game_pause`, `game_speed` |\n| Input | `input_slots`, `input_set`, `input_sequence` |\n\nStart with `project_info` on the editor (paths and asset states are relative to what it reports), and\nwith `game_info` on the game.\n\n## Editing a document\n\nNothing works on a closed document, and nothing opens implicitly:\n\n1. `asset_find` → path or guid. Its paths start with the data directory name\n   (`Testing Chambers\u002FScenes\u002FDynamicFog.ezScene`) - that is the form other tools want.\n2. `document_open` with `path` (not `document` - see below) and `focus` false, unless the user is meant\n   to look at it.\n3. `object_tree` → guids. Asset documents have one top level object, so `object_properties` with only\n   `document` already reads an asset's whole configuration. Scenes have many.\n4. `object_properties` \u002F `object_modify`.\n5. `document_save` - nothing saves on its own, and the asset system sees nothing until it is saved.\n\n**Which argument names a tool takes**, because guessing costs a round trip and they follow a rule:\n\n| Argument | Tools | Why |\n| --- | --- | --- |\n| `path` | `document_open`, `document_create`, `document_delete` | act on a file that need not be open yet |\n| `document` | `object_*`, `selection_*`, `document_save`\u002F`_close`\u002F`_focus`, and the `document` argument of the action tools | act on an already open document |\n| `asset` | `asset_info`, `asset_transform`, `asset_thumbnail`, `asset_uses` | act on the asset database, open or not |\n| `name` | `action_execute`, `action_state`, `rtti_*`, `cvar_set` | the thing named is not a document at all |\n\nSo it is `document_open` `path`, `action_execute` `name`, `rtti_derived_types` `name`. When in doubt read\nthe schema from `tools\u002Flist` rather than guessing - and note that a wrong name fails with a message that\nsays the right one.\n\nA scene's game objects and components live in the same hierarchy, told apart by the parent property they\nsit in. Building one is all `object_modify`:\n\n```\naddObject   property \"Children\",   type \"ezGameObject\"          -> child object ('object' \"root\": top level object)\naddObject   property \"Components\", type \"ezPointLightComponent\"  -> component on it\nset         property \"Name\" \u002F \"LocalPosition\" \u002F any component property\nmoveObject  newParent \u003Cguid>|\"root\" | duplicateObject | deleteObject  (each takes everything below it)\n```\n\nTo place an asset, `object_drop_asset` runs the editor's own drag & drop handler: a mesh becomes an object with\nan `ezMeshComponent`, a prefab one with an `ezPrefabReferenceComponent` (`prefabInstance` true: an editable,\nlinked prefab instance, like Shift+drag), and so on, at `position` and under `parent`. `attachTo` adds the\ncomponent to an existing object instead, `targetComponent` assigns a material to a mesh component.\n\nScenes can have **layers**, separate `.ezSceneLayer` documents in `\u003CScene>_data`, listed by `scene_layers`. Only\nthe active layer is editable, and while a layer is active the scene's objects are that layer's. The object tools\ntherefore refuse a scene or layer that is not active, and say which one is. `scene_layers` `setActive` switches\n(the user sees it), after which the scene and the layer document both reach the layer's objects. Switch back to\n`Scene` to edit the scene's own objects.\n\n`rtti_derived_types` of `ezComponent` lists component types; `rtti_type_properties` gives property\nnames, value types and enum values before writing any. Vectors and colours go in as they come out\n(`{\"x\":1,\"y\":2,\"z\":3}` or `[1,2,3]`). `selection_set` is worth calling even when it changes nothing - it\nis how the user sees which object is meant, and `selection_get` answers \"this object\".\n\n## Editing a node graph\n\nVisual scripts, materials using a visual shader, render pipelines, state machines, animation graphs and ProcGen\ngraphs are node graphs. Nodes and connections are ordinary top level objects in `object_tree`, but pins, node\npositions and connecting only exist in the graph_* tools:\n\n1. `graph_info` - nodes with position and pins (name, `dataType`, `description`, connection count), connections as\n   source node + output pin -> target node + input pin, and `otherObjects` (the asset's own settings).\n   `graphInUse` false: the document ignores its graph (a material only uses it with `ShaderMode` `Custom`), and\n   adding nodes or connections is refused until that is changed.\n2. `graph_node_templates` with `contains` - the node creation menu. Visual scripts have thousands of entries, many\n   sharing one node type and differing only in pre-filled properties, so add by `path`, not by type.\n3. `graph_add_node` (`template`, `position`) returns the node with its pins. Node properties are set with\n   `object_modify` as usual; a property can change the pins (e.g. a pin count), so re-read them afterwards.\n4. `graph_connect` goes from an output (`source`) to an input (`target`). Pins that take one connection get it\n   replaced, reported under `removedConnections`. Pin names can be empty strings.\n5. `graph_disconnect`, `graph_move_nodes`. `object_modify` `deleteObject` on a node also removes its connections.\n\nConnection objects cannot be created with `addObject` and their `Source`\u002F`Target`\u002F`SourcePin`\u002F`TargetPin` cannot be\nset - use connect\u002Fdisconnect. Other properties of a connection (a state machine transition) are set with\n`object_modify`. Lay out left to right, ~300 units apart, y pointing down.\n\n## Driving the game\n\n`gameStateActive` false in `game_info` means nothing is being played - normal for the editor's engine\nprocess until play-the-game runs, and why input does nothing and screenshots time out.\n\n- Start it from the **editor** port: `action_execute` `Scene.GameMode.Play` with the scene document;\n  `Scene.GameMode.Stop` ends it. Both are asynchronous (the editor asks the engine process), so `Stop`\n  reads as disabled for a moment and `game_info` on the game port is the better confirmation.\n- **`app_screenshot` returns a path, not the image.** Read that file. A rendered frame is the evidence a\n  change works; \"did not crash\" is not.\n- **`input_set` then `game_wait`** - input is consumed one frame at a time, so setting a slot alone does\n  nothing. `input_sequence` does a whole set\u002Fwait\u002Ftext\u002Fclear chain in one call. Injected values merge\n  with the real keyboard, larger wins, so a human is never locked out.\n- **`game_wait` takes `frames` or `seconds`** (game time on the global clock). For \"let the game play for a\n  while\" use `seconds` - a frame count lasts however long the frame rate makes it.\n- **Launch games with `-unattended`.** It prevents assert message boxes and the user's mouse and keyboard are \n  ignored and the window doesn't take the focus or capture the cursor. Only `input_set`\u002F`input_sequence` drive the game.\n\n- **`game_pause` stops the engine clock, not necessarily the game's own simulation.**\n- `cvar_list` is worth far more here than in the editor: render passes, physics and AI visualisation are\n  mostly CVars.\n\n## Editor actions\n\n`action_execute` runs global actions by name. Actions of scope `Document` or `Window` need a `document`\nargument (guid or path, already open); so do `action_list` and `action_state`, and that is the only way\nto read their per-document enabled state. Passing `document` to `action_list` also flips `globalOnly`\noff, so `{\"contains\":\"GameMode\",\"document\":\"…\",\"includeState\":true}` is the usual way to find them.\n`Window` actions additionally need a window (`document_open` with `focus` true).\n\n## C++ plugin\n\n`cpp_status` first: `hasCppProject` false means no C++ code at all and `cpp_generate` creates it;\n`compilerUsable` false means CMake will refuse and `cpp_generate` with `useSdkCompiler` is the fix.\nAfter editing sources call `cpp_build`, with `force` when files were added, removed or renamed (CMake\ncollects them at generation time). Both return the full build log - on failure it is the only place the\ncompiler errors are. Then check `pluginBinary` \u002F `pluginBinaryExists`: a build that reports success\nwithout producing the library means the plugin is not in use. Headless equivalent:\n`ezEditorProcessor.exe -project \u003Cpath> -compile` (`-recompile` forces CMake too).\n\n## Creating a project\n\nNo tool for it - a different set of plugins is loaded, so it happens at launch:\n\n```shell\nezEditor.exe -createProject \"C:\u002FProjects\u002FMyGame\" -projectTemplate \"Basic FPS\" -unattended -editor-mcpport 7399\n```\n\nThe directory must be empty or absent; the project opens right away. Without `-projectTemplate` the\nproject is blank, using `-pluginTemplate` (default `General3D`). `-listTemplates` logs the valid names.\n`ezEditorProcessor.exe` takes the same options and quits when done - better when no editor is wanted\nafterwards.\n\n## Rules that are not obvious\n\n- **Every call blocks its host.** One at a time, on the main thread. No progress, no cancel.\n- **Some calls run for minutes**: `asset_transform` over a project, `project_export`, `cpp_build`,\n  `cpp_generate`. Give curl a timeout in tens of minutes.\n- **`app_ping` tells \"busy\" from \"hung\".** It answers only when the main thread is free, so silence\n  during a long call is expected and silence afterwards is not. Take the process id from `app_info` up\n  front - a hung host must be killed by pid, and `app_quit` will not get through either.\n- **`log_read` only sees its own process.** The editor cannot see what the engine logged, or vice versa.\n  `app_info` reports `engineLogFilePattern` for when that process has died.\n- **A failed assert comes back as a tool error** with file, line and expression. That is an engine bug,\n  not bad arguments - retrying will not help. The host keeps answering but has continued past a check\n  meant to stop it, so restart it before trusting anything further, and report the text.\n- **Check `app_info`'s `buildTimestamp` before concluding a tool is missing.** A binary built before a\n  feature returns the same `tools\u002Flist` as one that never had it.\n- **`cvar_set` on a `requiresRestart` CVar does not change what the engine reads.** The response returns\n  `pendingValue` separately; re-reading keeps showing the old `value`, and that is not a failed write.\n- **Quit before rebuilding**: `app_quit` (with `discardChanges` if documents are modified), or the plugin\n  DLLs stay locked and the build fails.\n- **Nothing saves implicitly.** `object_modify` only marks the document modified; `object_undo` reverts.\n",{"name":5,"description":7},"dev","fb0a2478e13846abdca29b67c73595619b27e6f3",".claude\u002Fskills\u002Fez-mcp",268,"https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine","https:\u002F\u002FezEngine.net","https:\u002F\u002Fgithub.com\u002FezEngine","A free C++ game engine","2026-11-13 20:16:13",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add ezEngine\u002FezEngine --skill ez-mcp",{"tool":70,"command":71},"bunx","bunx skills add ezEngine\u002FezEngine --skill ez-mcp",{"tool":73,"command":74},"pnpm","pnpm dlx skills add ezEngine\u002FezEngine --skill ez-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.claude\u002Fskills\u002Fez-mcp\u002FSKILL.md",true,[],[79,85,92,105,120,144],{"skillNo":80,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":84,"publishedAt":50},"01M6BVJ2JJSR8YPD6VHS3ZFHQ0","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fez-mcp\u002FSKILL.md",[83],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,25],{"skillNo":86,"name":87,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":50},"01M6BVJ0TWDRH3BGF3R9G9J4ZA","ez-ddl","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fez-ddl\u002FSKILL.md",[],[91],"ez ddl",{"skillNo":93,"name":94,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":50},"01M6BVHZ4QE8PNRVNF6Q029HWK","debug-pretty-printers","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fdebug-pretty-printers\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[103,104],"debug pretty printers","debug",{"skillNo":106,"name":107,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":50},"01M6BVHXGW8DXMB3XD3AK0GTWX","android-build-test","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.github\u002Fskills\u002Fandroid-build-test\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[114,115,116,117,118,119],"android build","build test","build","android build test","test","android",{"skillNo":121,"name":87,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":50},"01M6BVHR3WC15VYQ9QTNVN67N2","Read and edit ezEngine documents on disk - scenes (.ezScene), prefabs (.ezPrefab) and assets (.ez*Asset) are OpenDDL text. Use Utilities\u002FScripts\u002Fezddl.py to convert GUIDs ('{ xxxxxxxx-... }' \u003C-> 'u4{low,high}') and hex floats (0x0000803F), resolve asset GUIDs to paths, find which documents use an asset, print a scene hierarchy, add game objects and components, set properties, validate a document, and make the editor re-transform a hand-edited asset. Triggers - ezScene, ezPrefab, ezMaterialAsset, ezTextureAsset, DDL, OpenDDL, asset GUID, Uuid u4, asset reference, hex float, edit scene file, add object to scene, which asset is this GUID, who references this asset, HeaderV2, Types section, type version.","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.claude\u002Fskills\u002Fez-ddl\u002FSKILL.md",[],[91,126,127,28,128,129,130,131,132,133,134,48,135,136,137,138,37,35,139,140,141,142,143],"scripts","paths","re","which","hand","float","hierarchy","hex","SET","components","validate","documents","file","text","read","edit","references","objects",{"skillNo":145,"name":94,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":151,"publishedAt":50},"01M6BVHN6NHYNR7W99E1CPKJJH","Debug and develop GDB and LLDB pretty printers for ezEngine C++ types. Use this skill when working with ezEngine debugger visualizers in ezEngine-gdb.py, ezEngine.py, or ezEngine.natvis. Covers testing with VisualizerZoo.cpp, common errors, and debugging techniques.","https:\u002F\u002Fgithub.com\u002FezEngine\u002FezEngine\u002Fblob\u002Fdev\u002F.claude\u002Fskills\u002Fdebug-pretty-printers\u002FSKILL.md",[149,150],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[104,103,152,28,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"c++","gdb","use","common","develop","debugger","debugging","cpp","testing","lldb","techniques","for","when","errors","with"]