--- name: inputsystem-controlscheme-add description: Add a Control Scheme (with optional required / optional device requirements) to a `.inputactions` asset, then save it. metadata: generated-by: mcp-plugin-dotnet --- # InputSystem / Add Control Scheme Add an `InputControlScheme` to an InputActionAsset. A control scheme groups bindings by a set of devices (e.g. a 'Keyboard&Mouse' scheme and a 'Gamepad' scheme), letting the same Actions support multiple input setups. ## Inputs - `assetPath` — required. Path to the existing `.inputactions` asset. - `schemeName` — required. Unique control-scheme name. - `requiredDevices` — optional device control paths that MUST be present (e.g. ``). - `optionalDevices` — optional device control paths that MAY be present (e.g. ``). ## Behavior Loads the asset, adds the control scheme via `AddControlScheme`, registers each required / optional device requirement, saves and re-imports the asset. Runs on the Unity main thread. ## How to Call ```bash unity-mcp-cli run-tool inputsystem-controlscheme-add --input '{ "assetPath": "string_value", "schemeName": "string_value", "requiredDevices": "string_value", "optionalDevices": "string_value" }' ``` > For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool inputsystem-controlscheme-add --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool inputsystem-controlscheme-add --input-file - <<'EOF' > {"param": "value"} > EOF > ``` ### Troubleshooting If `unity-mcp-cli` is not found, either install it globally (`npm install -g unity-mcp-cli`) or use `npx unity-mcp-cli` instead. Read the /unity-initial-setup skill for detailed installation instructions. ## Input | Name | Type | Required | Description | |------|------|----------|-------------| | `assetPath` | `string` | Yes | 'Assets/'-rooted path to the existing '.inputactions' asset. | | `schemeName` | `string` | Yes | Unique name of the new control scheme. | | `requiredDevices` | `any` | No | Optional required device control paths (e.g. ''). All must be present for the scheme to be usable. | | `optionalDevices` | `any` | No | Optional optional-device control paths (e.g. ''). | ### Input JSON Schema ```json { "type": "object", "properties": { "assetPath": { "type": "string" }, "schemeName": { "type": "string" }, "requiredDevices": { "$ref": "#/$defs/System.String-1" }, "optionalDevices": { "$ref": "#/$defs/System.String-1" } }, "$defs": { "System.String-1": { "type": "array", "items": { "type": "string" } } }, "required": [ "assetPath", "schemeName" ] } ``` ## Output ### Output JSON Schema ```json { "type": "object", "properties": { "result": { "$ref": "#/$defs/com.IvanMurzak.Unity.MCP.Editor.API.Tool_InputSystem-ControlSchemeAddResponse" } }, "$defs": { "com.IvanMurzak.Unity.MCP.Editor.API.Tool_InputSystem-ControlSchemeAddResponse": { "type": "object", "properties": { "assetPath": { "type": "string", "description": "Path of the modified asset." }, "schemeName": { "type": "string", "description": "Name of the added control scheme." }, "requiredDeviceCount": { "type": "integer", "description": "Number of required devices registered." }, "optionalDeviceCount": { "type": "integer", "description": "Number of optional devices registered." }, "controlSchemeCount": { "type": "integer", "description": "Total number of control schemes in the asset." }, "success": { "type": "boolean", "description": "Whether the operation succeeded." } }, "required": [ "requiredDeviceCount", "optionalDeviceCount", "controlSchemeCount", "success" ] } }, "required": [ "result" ] } ```