uloop-execute-dynamic-code

name	uloop-execute-dynamic-code
description	Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for scene, prefab, SerializedObject, AssetDatabase refresh/.meta generation, menu, or PlayMode automation.
context	fork

Task

Execute the following request using npx --yes uloop-cli@2.2.0 execute-dynamic-code: $ARGUMENTS

For basic selected GameObject discovery or property inspection, use find-game-objects --search-mode Selected before this tool. Use this tool after the built-in inspection tools are not enough or when you need to modify Unity state.

Workflow

1. Read the relevant reference file(s) from the Code Examples section below
2. Construct C# code based on the reference examples
3. For multiline snippets, write the C# statements to a temporary .csx file and execute npx --yes uloop-cli@2.2.0 execute-dynamic-code --code-file <path>
4. Use npx --yes uloop-cli@2.2.0 execute-dynamic-code --code '<code>' only for short one-line snippets
5. If execution fails, adjust code and retry
6. Report the execution result

Parameters

• --code '<code>': Inline C# statements to execute. Use this for one-line snippets only.
• --code-file <path>: Read C# statements from a UTF-8 file. Prefer this for multiline snippets, especially on PowerShell, because Windows .cmd shims can lose lines from multiline inline arguments before uloop receives them.
• Shell quoting: bash/zsh uses single quotes, for example npx --yes uloop-cli@2.2.0 execute-dynamic-code --code 'using UnityEngine; return Mathf.PI;'. PowerShell single-quoted strings can contain normal double quotes, for example npx --yes uloop-cli@2.2.0 execute-dynamic-code --code 'Debug.Log("Hello!");'.
• --parameters {} (advanced, optional): Pass an object when reusing a snippet with varying data or when keeping values outside the code. Values are exposed as parameters["param0"], parameters["param1"], and so on. Omit this flag for most snippets, and pass an object instead of a JSON string.
• --compile-only true (optional): Compile the snippet without executing it. Use this when you want Roslyn diagnostics before running new code.

Code Rules

Write direct statements only — no class/namespace/method wrappers. Return is optional.

using UnityEngine;
float x = Mathf.PI;
return x;

Forbidden — these will be rejected at compile time: System.IO.*, AssetDatabase.CreateFolder, creating/editing .cs/.asmdef files. Use terminal commands for file operations instead.

Output

Returns JSON:

• Success: boolean — overall execution success
• Result: string — value of the snippet's return statement (empty when omitted)
• Logs: string[] — execution diagnostics from the dynamic-code runner, not Unity Console entries
• CompilationErrors: object[] — Roslyn diagnostics with Message, Line, Column, ErrorCode, optional Hint and Suggestions
• ErrorMessage: string — top-level failure summary (empty on success)
• Error: string — alias of ErrorMessage
• SecurityLevel: string — dynamic-code security level active for the request
• UpdatedCode: string|null — the wrapped form actually compiled (handy when debugging using-statement reordering)
• DiagnosticsSummary: string|null — compact summary when diagnostics are available
• Diagnostics: object[] — structured diagnostics; same shape as CompilationErrors, usually populated together with it

Use npx --yes uloop-cli@2.2.0 get-logs to retrieve Debug.Log, Debug.LogWarning, and Debug.LogError messages emitted by the snippet. On Success: false, inspect CompilationErrors first. If empty, read ErrorMessage (and Logs for extra context) — the failure may be a runtime exception, security violation, cancellation, or an "execution in progress" rejection, all of which return empty CompilationErrors. Both EditMode and PlayMode are supported targets — the snippet runs in whichever mode the Editor is currently in.

Code Examples by Category

For detailed code examples, refer to these files:

• Prefab operations: See references/prefab-operations.md
  • Create prefabs, instantiate, add components, modify properties
• Material operations: See references/material-operations.md
  • Create materials, set shaders/textures, modify properties
• Asset operations: See references/asset-operations.md
  • Find/search assets, duplicate, move, rename, load
• ScriptableObject: See references/scriptableobject.md
  • Create ScriptableObjects, modify with SerializedObject
• Scene operations: See references/scene-operations.md
  • Create/modify GameObjects, set parents, wire references, load scenes
• Batch operations: See references/batch-operations.md
  • Bulk modify objects, batch add/remove components, rename, layer/tag/material replacement
• Cleanup operations: See references/cleanup-operations.md
  • Detect broken scripts, missing references, unused materials, empty GameObjects
• Undo operations: See references/undo-operations.md
  • Undo-aware operations: RecordObject, AddComponent, SetParent, grouping
• Selection operations: See references/selection-operations.md
  • Get/set selection, multi-select, filter by type/editability
• PlayMode automation (zsh): See references/playmode-automation-zsh.md
  • Click UI buttons, invoke methods, set fields, tool combination workflows for zsh users
• PlayMode automation (PowerShell): See references/playmode-automation-powershell.md
  • Click UI buttons, invoke methods, set fields, tool combination workflows for PowerShell users
• PlayMode UI controls: See references/playmode-ui-controls.md
  • InputField, Slider, Toggle, Dropdown, drag & drop simulation, list all UI controls
• PlayMode inspection: See references/playmode-inspection.md
  • Scene info, game state via reflection, physics state, raycast checks, GameObject search, position/rotation