Menú
Quick check that the Unreal editor remote-exec channel is live. Use before driving the editor, or when in-editor calls seem to hang.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | bp-channel |
| description | Quick check that the Unreal editor remote-exec channel is live. Use before driving the editor, or when in-editor calls seem to hang. |
Run & $py ue_run.py bpkit/ops/ping.py (where $py = bpkit.config.BUNDLED_PYTHON or $env:BPKIT_PYTHON) and report whether the channel is up — an ENGINE_VERSION line means live. If it prints no editor node found, point the user at /setup (editor not running or Remote Execution off).
Setup / health check for bpkit — verify the editor channel, Python, Remote Execution, AND that the native ctypes bridge resolves on THIS editor build. Adaptive: diagnose and self-heal, don't hard-fail. Run after pulling the repo.
Drive Unreal Engine 5 Blueprint graphs from outside the editor with bpkit — read, author, edit, inject and compile K2 node graphs over the remote-exec channel. Use for ANY UE Blueprint node-graph task: authoring nodes, fixing pins, mod authoring, reading a graph — AND for answering "how does this game mechanic work?" by reading the game's own shipped Blueprints. (Windows + an editor build with Remote Execution on.)
Build and deploy a mod from this repo into the live Unreal editor — import its source assets, run its Blueprint build steps in order, then verify. Argument is the mod folder name under mods/ (or a path), e.g. mounted-followers.
Read an Unreal blueprint's node graphs and show a dense, navigable outline. Use when inspecting or understanding a Blueprint's logic. Argument is the asset path, e.g. /Game/Foo/BP_Bar.
Run the bpkit test suites — the offline library tests (no editor) and, if the editor is up, the in-editor authoring tests.
Install the bpkit slash-commands into your personal ~/.claude/skills so they work from any project directory, not just this repo. Run once after pulling the repo (and again after repo updates).
