Skip to content
Blueprint AI

Troubleshooting

Skill not installed after opening the editor

Section titled “Skill not installed after opening the editor”

Run setup manually:

Terminal window
python Plugins/BlueprintAI/setup.py

If setup runs but the skill is still missing, check that Claude is installed and that Blueprint AI can locate its .claude/ directory. Run with verbose output:

Terminal window
python Plugins/BlueprintAI/setup.py --verbose

“No CLI output” or empty response from the AI

Section titled ““No CLI output” or empty response from the AI”

The AI tried to run an operation but got no response. Common causes:

  • Editor not found — Blueprint AI could not locate the Unreal Engine installation. Make sure UE 5.7+ is installed, or set UE_INSTALL_DIR to point at the engine you want it to use (see Headless / CI Mode → Engine discovery).
  • Python plugin disabled — ensure PythonScriptPlugin is enabled in your project.
  • Port conflict — Blueprint AI uses UDP port 6776 for remote execution. Check nothing else is using that port.

Run the schema command to test basic connectivity:

Terminal window
python Plugins/BlueprintAI/Scripts/cli.py schema

Compilation errors after an operation

Section titled “Compilation errors after an operation”

The AI receives the full compiler error and usually corrects itself. If it cannot, inspect the asset manually in the editor. Common causes:

  • A referenced class or asset does not exist at the specified path
  • A function signature mismatch (parameter type changed elsewhere in the project)
  • A node was wired to an incompatible pin type

”Domain not available” for Enhanced Input / Control Rig / State Trees

Section titled “”Domain not available” for Enhanced Input / Control Rig / State Trees”

These domains require optional engine plugins. Go to Edit → Plugins and verify:

  • Enhanced Input: EnhancedInput plugin enabled
  • Control Rig: ControlRig and RigVM plugins enabled
  • State Trees: StateTree plugin enabled
  • Common UI: CommonUI plugin enabled

After enabling plugins, restart the editor.

Operations succeed but the asset looks wrong

Section titled “Operations succeed but the asset looks wrong”

Use the inspect command to verify the actual state of the asset:

Terminal window
python Plugins/BlueprintAI/Scripts/cli.py inspect /Game/MyAsset/BP_Example

Then ask the AI to describe what it sees versus what was expected. This gives the AI the context to issue corrective operations.

The editor opens but hangs during an operation

Section titled “The editor opens but hangs during an operation”

Blueprint AI runs operations in commandlet mode. If the commandlet hangs:

  1. Kill the UnrealEditor.exe process
  2. Delete Saved/Autosaves/ if the project was left in a partial state
  3. Re-run the operation

If hanging persists, check Saved/Logs/ for the last commandlet log for error details.