メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.)
Quick check that the Unreal editor remote-exec channel is live. Use before driving the editor, or when in-editor calls seem to hang.
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).
| name | deploy |
| description | 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. |
| argument-hint | <mod-name> |
| disable-model-invocation | true |
Deploy the mod named in $ARGUMENTS as a smart process: get it built and verified, adapting on failure rather than just reporting one. $py = bpkit.config.BUNDLED_PYTHON (or $env:BPKIT_PYTHON).
& $py ue_run.py bpkit/ops/ping.py (ENGINE_VERSION printed). If dead, point the user at /setup.ABORT: Play-in-Editor is running, ask the user to stop Play, then re-run.& $py ue_run.py bpkit/ops/deploy.py $ARGUMENTS
This reads mods/$ARGUMENTS/manifest.py, imports any source ASSETS, then runs each BUILD step (an ordinary editor-side payload) in order in one editor session. Each step prints its own result (e.g. BUILD OK). Ends with === DEPLOY <mod>: OK === or N STEP(S) FAILED.
& $py ue_run.py bpkit/ops/compile_errors.py (wildcard / bOrphanedPin / ErrorMsg), fix the offending node in that step's builder, re-deploy. Remember "compiled" ≠ "no errors".NOT DEPLOYABLE: no manifest.py: the mod folder needs a manifest.py declaring BUILD = [...] (ordered step files) — model it on mods/mounted-followers/manifest.py.-> FAILED: check the src path in the manifest (relative to the mod folder) and that the source file exists; UE import factories are picky about extensions.Mod name → output package, which steps ran, asset imports, and the final verdict. If you fixed something to get it green, say exactly what.
/deploy only authors into the editor (/Game/<Mod>) for PIE testing; it does NOT package. The real game runs a separate cook → pak from the Dev Kit mod tool (e.g. ...\UE4\Saved\Mods\<Mod>\Output\<Mod>.pak). If the user says "works in editor but not in the real/packaged game," it's almost always packaging, not the graph:
mods/*/02_manager-style logic) must cook as a (Mod Asset) — i.e. be authored under /Game/Mods/<ModName>/ — or the packaged game culls it as [1]Invalid class (works in PIE, dead packaged). Confirm in the cook dialog. (bRequiresLoadOnStartup is NOT required — verified in the cooked game 2026-06-10.)UnrealPak.exe <Mod>.pak -List → extract → UnrealPak.exe <Mod>-Windows.utoc -List for the inner asset list (IoStore .ucas is Oodle-compressed — use -List, never grep). Shipping strips PrintString/GetAll; use HUDShowFIFO / ClientHUDShowNotification for visible diagnostics. Full write-up: docs/CONAN-NOTES.md §Packaging.