Skip to main content

🛠️ Troubleshooting

Here are solutions to the most common issues users encounter with Ludus AI.

Blueprint Generation Issues​

Problem: "Ludus won't create a Blueprint for me" or "I ask for a Blueprint but nothing happens."

Solution: This usually happens for one of three reasons:

  1. No File Exists: Ludus cannot generate a new .uasset file from scratch on your hard drive.
    • Fix: You must manually create an empty Blueprint Asset (e.g., an Actor) in your Content Browser first. Open it, then ask Ludus to generate the logic inside it.
  2. Beta Not Enabled: Blueprint generation is currently a Beta feature.
  3. Unspecified Blueprint: Ludus isn't sure which file to target.
    • Fix: It is important to point Ludus to the Blueprint you want to change. The most reliable method is to have the Blueprint open or mention its name. However, clearly describing which Blueprint Ludus should look into is also sufficient.

If the issue persists, please contact our support team via Discord or email at support@ludusengine.com
Important: To help us fix the issue faster, please include your debug info. In the Ludus Plugin, click the three dots ⋮ menu -> Select Copy Debug Info -> Paste this into your support message.

"Conversation Too Long" Error​

Problem: "I'm getting an error saying the conversation is too long."

Solution: This occurs when the current chat thread has accumulated too much history (text and code), exceeding the AI's context limit.

  • Fix: simply start a new conversation thread. This resets the context and allows you to continue working fresh.
  • You can also try removing previous checkpoints (at the end of user messages) to free up space, but a new thread is the most reliable solution.