editor-application-set-state

Start, stop, or pause Unity Editor Play mode programmatically.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/lightvu25/Echoes --skill editor-application-set-state-lightvu25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: editor-application-set-state
Source: https://github.com/lightvu25/Echoes/tree/main/SKILLS/editor-application-set-state
Command: npx skills add https://github.com/lightvu25/Echoes --skill editor-application-set-state-lightvu25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated control of the Unity Editor's Play mode, letting you start, stop, or pause play and verify the current state without manual intervention.

Core Features & Use Cases

  • Play mode control: Start, stop, or pause the Unity Editor playstate programmatically.
  • State awareness: Recommend checking current state with editor-application-get-state before applying changes.
  • CI/automation integration: Ideal for automated build and test pipelines that require deterministic editor behavior.

Quick Start

Call the tool with isPlaying set to false and isPaused set to false to ensure playmode is stopped.

Frequently Asked Questions about editor-application-set-state

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

FAQPage Schema
How do I control Unity Editor playmode automatically during a CI workflow?

You can automate Unity Editor playmode by setting the isPlaying and isPaused inputs to programmatically start, stop, or pause play during automated testing and CI workflows.

Can I check the current Unity play state before applying playmode changes?

Yes, you should verify the current editor play state using editor-application-get-state before applying deterministic state changes to ensure reliable automation.

What is the best way to stop Unity playmode from a script for automated testing?

The best way to stop Unity playmode is to call the tool with both isPlaying and isPaused set to false, ensuring deterministic state changes for your test runs.

Does this playmode automation tool require any specific Unity dependencies?

No, this playmode automation tool has no external dependencies and directly controls the Unity Editor's play state using the required isPlaying and isPaused inputs.

Why do I need to provide both isPlaying and isPaused inputs for Unity editor control?

Providing both isPlaying and isPaused inputs is required to achieve deterministic state changes, preventing ambiguous playmode transitions during automated CI workflows.