メニュー
Record PlayMode keyboard and mouse input to JSON. Use to capture gameplay, bug repro, or E2E input sequences for replay.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Clear Unity Console entries. Use before compile, tests, or debugging when stale logs would hide the current result.
Compile the Unity project and report errors/warnings. Use after C# edits or when a full Domain Reload compile is needed.
Control Unity Editor Play Mode. Use to start, stop, or pause Play Mode for runtime behavior checks and frame inspection.
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.
Find or inspect Unity GameObjects, especially objects the user currently selected in the Hierarchy. Use for details, components, tags, layers, or name/path searches.
Bring the Unity Editor window to front. Use when Unity must be visible for visual checks or user-facing interaction.
| name | uloop-record-input |
| description | Record PlayMode keyboard and mouse input to JSON. Use to capture gameplay, bug repro, or E2E input sequences for replay. |
Record keyboard and mouse input during PlayMode frame-by-frame into a JSON file. Captures key presses, mouse movement, clicks, and scroll events via Input System device state diffing.
# Start recording
uloop record-input --action Start
# Start recording with key filter
uloop record-input --action Start --keys "W,A,S,D,Space"
# Stop recording and save
uloop record-input --action Stop
# Stop and save to specific path
uloop record-input --action Stop --output-path scripts/my-play.json
| Parameter | Type | Default | Description |
|---|---|---|---|
--action | enum | Start | Start - begin recording, Stop - stop and save |
--output-path | string | auto | Save path. Auto-generates under .uloop/outputs/InputRecordings/ |
--keys | string | "" | Comma-separated key filter. Empty = all common game keys |
Replay injects input frame-by-frame, so the game must also be deterministic to produce identical results. If the recording will be used for E2E tests, bug reproduction, or replay verification, read references/deterministic-replay.md before designing assertions or game logic.
com.unity.inputsystem)The CLI prints JSON with:
Success: Whether the operation succeededMessage: Status messageAction: Echoes which action was executed (Start or Stop)OutputPath: Path to saved recording (nullable; populated on Stop only)TotalFrames: Number of frames recorded (nullable int; populated on Stop only)DurationSeconds: Recording duration in seconds (nullable float; populated on Stop only)The CLI output contains only these six payload fields. Internal metadata such as Ver is removed before printing. There is no RecordingId, StartTimestamp, KeysCaptured, or per-frame data in the response — frame data lives only in the JSON file at OutputPath.