About this skill

Problem

Using Python in Unreal Editor for batch asset renames, material creation, actor iteration, LOD setup, and other project automation often gets stuck on API version drift and editor-context constraints: UE 4 / 5.0 leans on Library APIs, while UE 5.1+ prefers Subsystem APIs; paths must use /Game/..., edits need saves, materials need recompiles, batch jobs need progress bars, and most editor APIs do not work in PIE. The skill turns these constraints into a practical scripting SOP.

How It Works

It maps requirements to concrete Unreal Python patterns: clarify the UE version, runtime context, and whether the script runs once or integrates into an editor menu, then choose the right API such as EditorAssetSubsystem, EditorActorSubsystem, MaterialEditingLibrary, or StaticMeshEditorSubsystem. Generated scripts usually start with import unreal, keep configuration variables up front, use unreal.ScopedSlowTask for more than 10 items, wrap risky operations in try/except, and log results with unreal.log(). For asset modifications, it reminds you to enable Python Editor Script Plugin and Editor Scripting Utilities, and optionally use ScopedEditorTransaction for undo support.

Boundaries

Best for Unreal editor automation: asset import/export, Data Tables, Sequencer, editor menus, and batch setup. Not suitable for runtime game logic or PIE scenarios that rely on editor APIs. If the project path, plugin state, or UE version does not match, the script may fail silently; validate API names, path format, save calls, progress bars, and cancellation logic before delivery.