Troubleshooting

“Unreal Editor is not running”

The bridge couldn’t reach the editor. Check that:

• The editor is open and the Direktor plugin is enabled (Edit → Plugins).
• The setup panel (Window → Direktor) shows the server listening on port 13579.

You don’t need to restart your AI client. Start the editor and retry the call — the bridge reconnects on its own and refreshes the tool list.

My client doesn’t show Direktor’s tools

• Confirm the config snippet is in the right file for your client (see Quick Setup) and that the JSON is valid.
• Fully restart or reload the client so it re-reads its MCP config.
• Make sure Node.js 18 or newer is installed and on your PATH — the bridge runs through npx. Test it directly with npx -y unreal-direktor-mcp in a terminal; it should start and wait for input.

The Direktor menu or panel is missing

• Re-check Edit → Plugins for Direktor and make sure it’s enabled.
• Restart the editor after enabling — the module loads at editor startup.

Calls hang with no response

If every call stops responding with no error, a modal dialog in the editor is probably blocking the game thread (an unsaved-changes prompt, an import dialog, a confirmation box). Bring the editor to the foreground, dismiss the dialog, and the calls resume. Suspect this before assuming a crash.

Screenshots come back blank or stale

Unreal throttles rendering when the editor isn’t the foreground window, so a screenshot taken while another app is focused can be empty or out of date. Direktor forces a best-effort render for screenshots, but for reliable captures keep the editor window visible.

A tool says it needs a plugin or a newer engine

Some tools depend on optional plugins or a minimum engine version:

• gas needs the GameplayAbilities plugin enabled.
• pcg needs the PCG plugin (UE 5.4+).
• geometry / skeletal_mesh need GeometryScripting (UE 5.4+).
• niagara and behavior_tree authoring are UE 5.3+.

Enable the named plugin (Edit → Plugins, then restart) or use a supported engine version. Version-gated tools return a guided message on older engines rather than failing silently.

A change went wrong

Most mutating calls are a single undo step. Use Ctrl+Z, or have the assistant call editor(action="undo"). Use editor(action="history") to see the stack newest-first and confirm the top entry is yours before undoing. Asset creation, saves, and run_python side effects are not transactional, which is why a version-controlled project is the real safety net.

Still stuck?

The plugin ships its own docs — ask your AI client to call docs(action="search", query="..."), or browse them from the docs tool. For anything else, reach out through the support contact on the Fab listing.