isuzu-unity-cli

isuzu-unity-cli

Each command talks to the Unity Editor that has this project open and prints compact JSON. A call returns when its work is done: play_mode_play returns once play mode has started, and a call that takes long waits for its result.

Rules

• Do not list tools. The table below covers common work; for anything else run isuzu-unity-cli tools --search <words>, then isuzu-unity-cli tools <name>.
• Put every call you already know into one shell command with the template below. Do not read again to confirm a change: each reply already shows the result, and you can answer from it.
• Windows PowerShell deletes double quotes inside arguments, so never pass JSON text. Use --name value; repeat an option for a list (--paths a --paths b); --values.m_Mass 2 sets one field of an object argument; a vector is --position '1,0,2'; anything else goes in a file: --args-file args.json.
• Single-quote values with spaces, commas or @: '/Main Camera', 'error,warning', '@scene:/Boss/Enemy/health'. Unquoted, PowerShell splits 1,0,2 into three words.
• Scene paths start with /. Siblings that share a name take a 0-based index: /Audio/Speaker[1].
• Property paths are serialized names (m_Mass, m_LocalPosition.x, a script's field name); the C# name (mass) also works when it is unambiguous, and a miss lists the nearest names.

Template

function u { isuzu-unity-cli @args; if ($LASTEXITCODE) { throw "isuzu-unity-cli $args failed ($LASTEXITCODE)" } }
try {
  u call play_mode_play
  u call ui_click --text Start
} finally { isuzu-unity-cli call play_mode_stop }

A failed call throws, so the calls after it do not run on a broken state, and finally leaves play mode. Without play mode, the try/finally is not needed.

Tasks