Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beehave and LimboAI incompatibility #72

Open
peterpants2 opened this issue Mar 14, 2024 · 1 comment
Open

Beehave and LimboAI incompatibility #72

peterpants2 opened this issue Mar 14, 2024 · 1 comment
Labels
breaking-compatibility Implementing this issue would break compatibility with the current minor versions. bug Something isn't working

Comments

@peterpants2
Copy link

Godot version: 4.2.1.stable non-mono

Describe the bug
Just FYI Installing LimboAI and Beehave together in the same project do not play nicely with one another. I was hoping to compare performance/useability but no such luck. Not sure what best solution would be. It's unfortunate Godot doesn't have namespaces. Seems both addons are creating their own Blackboard class. I also posted this in Beehave just so both addon devs would be aware.

To Reproduce
Steps to reproduce the behavior:

  1. Create new project. Add LimboAI from asset store. Add latest Beehave release from GitHub.
    
  2. Enable plugin
    
  3. Attempt to run scene
    
  4. Error
    

Expected behavior
Scene runs without error

Screenshots
313004220-8b4f1cea-8d28-4ea2-9511-523313969e4d

Desktop (please complete the following information):

OS: Windows

Minimal Project with both Addons installed
testing_limbo_AI_with_beehave.zip

@limbonaut limbonaut added breaking-compatibility Implementing this issue would break compatibility with the current minor versions. bug Something isn't working labels Mar 23, 2024
@limbonaut
Copy link
Owner

We can look into some incompatibilities like this one for 2.0. I'd rather not break compatibility in 1.x unless really necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-compatibility Implementing this issue would break compatibility with the current minor versions. bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants