Skip to content

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

Open
@ArcanoxDragon

Description

@ArcanoxDragon

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions