uloop-control-play-mode

Control Unity Editor play mode via command line with JSON state output.

500|44|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-control-play-mode-hatayama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uloop-control-play-mode
Source: https://github.com/hatayama/unity-cli-loop/tree/main/.agents/skills/uloop-control-play-mode
Command: npx skills add https://github.com/hatayama/unity-cli-loop --skill uloop-control-play-mode-hatayama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill lets developers and automation agents control the Unity Editor play mode from the command line so testing, debugging, and inspection can run without manual editor interaction.

Core Features & Use Cases

  • Start, Stop, Pause: Perform play, stop, or pause actions through a single action parameter to manage runtime execution.
  • Project targeting: Optionally operate on a Unity project outside the current directory using a project path argument.
  • Automation-friendly output: Emits JSON with IsPlaying, IsPaused, and Message fields for integration with CI pipelines and test harnesses.
  • Use Case: Automate starting play mode before integration tests, pause for frame-by-frame inspection during debugging, and stop when tests complete.

Quick Start

Run the uloop control-play-mode command to start, stop, or pause the Unity Editor play mode in the current project.

Frequently Asked Questions about uloop-control-play-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control Unity Editor play mode from the command line?

Control Unity Editor play mode from the command line by passing an --action parameter with start, stop, or pause values. The Skill returns JSON fields IsPlaying, IsPaused, and Message for integration with automation scripts.

Can I automate Unity play mode for CI pipelines and integration tests?

Yes, automate Unity play mode for CI pipelines by running start before integration tests and stop when tests complete. The JSON output containing IsPlaying and IsPaused fields allows test harnesses to verify runtime execution state.

How do I pause Unity Editor for frame-by-frame debugging?

Pause Unity Editor for frame-by-frame debugging by passing the pause action to the command. The Skill emits a JSON response with IsPaused set to true, allowing inspection of runtime state without manual editor interaction.

Does this Unity play mode controller work on projects outside the current directory?

Yes, it works on projects outside the current directory by passing the optional --project-path argument. This targets a specific Unity project path for play, stop, or pause actions during automated testing workflows.

What is the best way to programmatically stop Unity play mode after tests finish?

Programmatically stop Unity play mode after tests finish by passing the stop action to the command. The Skill outputs JSON with IsPlaying set to false and a confirmation Message for CI integration.

Why does my automated Unity testing workflow need programmatic play mode control?

Automated Unity testing workflows need programmatic play mode control to start, pause, and stop runtime execution without manual editor interaction. This enables fully automated CI pipelines and debugging sessions to run unattended.