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

bug: "addObject" function doesn't seem to do anything #102

Open
1 task done
ArcanoxDragon opened this issue Dec 21, 2023 · 0 comments
Open
1 task done

bug: "addObject" function doesn't seem to do anything #102

ArcanoxDragon opened this issue Dec 21, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@ArcanoxDragon
Copy link

Describe the bug

Calling the addObject function with a directory path doesn't seem to do anything at all - custom object modules are not required.

It looks like all this function does is add the provided path to newObjects in main.lua, but newObjects is only ever visted when main.lua is first evaluated (i.e. when the module is required, before the addObject function can even be called).

To Reproduce

Steps to reproduce the behavior:

  1. Add a custom object module to a folder that has a debug print or something at the top
  2. Pass the folder to basalt.addObject("...") in a test program
  3. Run the program and observe that the custom modules are not imported

Expected behavior

The custom object modules would be imported and registered as object types in Basalt.

Checklist

  • I am running the latest version.
@ArcanoxDragon ArcanoxDragon added the bug Something isn't working label Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant