Skip to main content

🛠ïļ Troubleshooting

If you encounter a bug in the plugin, use Report Bug in the top-right corner of the plugin interface.

This page covers solutions for some common plugin issues.

If an issue persists, reach the team on Discord or email support@ludusengine.com.

"Conversation Too Long"​

The current chat thread has accumulated too much history to continue.

Start a new chat. Long-term memory persists across chats, so Ludus keeps what it learned about your project. See Planning, Memory & Sub-agents.

An approval request expired​

Staged changes wait for your approval. If the editor expires the request before you act, the change is not applied and nothing touches your project. Prompt again, or re-run the step, to stage the change a second time. See Approvals & Safety.

Project indexing is paused or stuck​

Ludus indexes your project so it can read Blueprints, C++, data structures, and actors in level files.

  • The indexing overlay has pause and resume controls. If indexing is paused, resume it.

Recovering after an engine crash​

After an engine crash, restart the editor and open the plugin. Unsaved conversations recover on startup.

A request timed out​

Transient chat failures and timeouts retry automatically from the last checkpoint. Let the retry complete before re-sending the request. If it keeps failing, start a new chat.

A C++ project will not build and says a Ludus module is undefined​

This is caused by where the plugin folder sits, not by the plugin itself. It only affects C++ projects on an engine installed from the Epic Games Launcher — Blueprint-only projects and engines built from source never see it. Clearing caches, regenerating project files, or upgrading the engine will not help on its own.

A Launcher engine ships the build rules for its plugins prebuilt and read-only, so a plugin added to that engine after it was installed is not among them and the build stops before any of your own code compiles. One location is the exception: plugins under Engine/Plugins/Marketplace get their own build rules generated when you build.

Move the plugin folder to one of these, keeping only one copy on disk:

  • <engine install>/Engine/Plugins/Marketplace/LudusAI — the plugin is available to every project on that engine.
  • <your project>/Plugins/Marketplace/LudusAI — the plugin is available to that project only.

Then right-click your .uproject, regenerate the project files, and build again.