unreal-editor-automation

Design and run safe Unreal Engine 5.8 editor automation across Blueprint utilities, Python, commandlets, and MCP.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill unreal-editor-automation-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unreal-editor-automation
Source: https://github.com/steveulrich/ProjectB/tree/main/.cursor/skills/unreal-editor-automation
Command: npx skills add https://github.com/steveulrich/ProjectB --skill unreal-editor-automation-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Unreal Editor automation often fails through unsafe bulk mutations, wrong tool selection, irreversible operations, and CI jobs that silently misreport success. This Skill guides the design, implementation, execution, and debugging of editor automation so asset changes stay scoped, validated, and recoverable. ## Core Features & Use Cases - Automation surface selection: Choose between Scripted Actions, Editor Utility Widgets, Call in Editor, Scriptable Tools, Python scripting, commandlets, Data Validation, Automation/Functional Tests, and the experimental Unreal MCP server based on task shape. - Safe mutation guardrails: Enforce dry-run planning, transaction boundaries, source-control policy, idempotent reruns, and editor-API-only asset operations instead of filesystem manipulation of .uasset files. - Headless CI and testing: Build commandlet-based pipelines with Data Validation, Automation Tests, and machine-readable reports that fail correctly on crashes, timeouts, or partial processing. - Use Case: A technical artist needs to rename and revalidate 500 textures across a content tree. The Skill produces a discover-plan-apply-save-validate workflow with a dry-run report, collision checks, and per-asset failure logging before any mutation runs. ## Quick Start Use the unreal-editor-automation skill to design a safe batch tool that renames all textures in a folder and validates the results.

Frequently Asked Questions about unreal-editor-automation

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

FAQPage Schema
How do I automate Unreal Editor tasks with Python?▼

Enable the Python Editor Script Plugin and Editor Scripting Utilities, then restart the editor. Unreal 5.8 embeds Python 3.11.8, available only in the editor. Use editor subsystems like EditorAssetSubsystem and follow a discover-plan-apply-save-validate batch structure.

What Unreal Editor automation tool should I use for batch asset changes?▼

Use a Scripted Action for selected assets, an Editor Utility Widget for reviewed batch work with UI, Python for repeatable text-based pipelines, and a commandlet for headless CI. Choose the least powerful surface that fits the task.

Can I run Unreal Python scripts in a packaged game?▼

No. Unreal 5.8's embedded Python is editor-only and unavailable in PIE, Standalone Game, or cooked executables. Keep editor tool code in editor-only modules and test a Shipping cook for accidental editor-only references.

Why does my Unreal Python commandlet see no actors?▼

The pythonscript commandlet does not load a level automatically. Load the intended level explicitly through LevelEditorSubsystem, or use -ExecutePythonScript instead when the job needs the full editor with the default startup level.

Is it safe to rename .uasset files with Python os or shutil?▼

No. Never use generic filesystem operations on .uasset or .umap files, as this breaks internal package references and redirector handling. Use Unreal's Asset Tools and Editor Asset APIs for rename, delete, and import operations.

What are the limitations of Unreal MCP in UE 5.8?▼

Unreal MCP is Experimental in 5.8 with no authentication layer, so keep it loopback-only. It supports HTTP and SSE but not stdio or WebSocket, serializes tool calls on the game thread, and Live Coding does not propagate new tool UFUNCTION declarations.