🛠️ 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 countdown expired

Staged changes wait for your approval on a countdown. If the countdown expires 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.