assets-move

# Assets / Move Move the assets at paths in the project. Should be used for asset rename. Does AssetDatabase.Refresh() at the end. Use 'assets-find' tool to find assets before moving. ## Inputs - `sourcePaths` — paths of the assets to move. - `destinationPaths` — target paths (must match `sourcePaths` length). ## Behavior Each pair is moved independently via `AssetDatabase.MoveAsset`. Per-pair failures (Unity's `MoveAsset` returns a non-empty error string) are surfaced in `response.Errors`; successful moves accumulate into `response.MovedPaths`. ## How to Call ```bash unity-mcp-cli run-tool assets-move --input '{ "sourcePaths": "string_value", "destinationPaths": "string_value" }' ``` > For complex input (multi-line strings, code), save the JSON to a file and use: > ```bash > unity-mcp-cli run-tool assets-move --input-file args.json > ``` > > Or pipe via stdin (recommended): > ```bash > unity-mcp-cli run-tool assets-move --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 | |------|------|----------|-------------| | `sourcePaths` | `any` | Yes | The paths of the assets to move. | | `destinationPaths` | `any` | Yes | The paths of moved assets. | ### Input JSON Schema ```json { "type":...