satoon101 wrote:Correct, I have designed the load/unload section so that if a script wants to load its own subscript, it will need its own API to do so. This is the correct way to handle this, imo.
I partially argee, but those subfolders can also used to structure scripts further.
For example, when working on the auth stuff I had the idea to put all auth providers in their own subfolder. Obviously each auth provider is independent from each other, but still I think this:
auth_providers/simple
auth_providers/group
auth_providers/mysql
is better compared to:
simpleauth
groupauth
mysqlauth
Another example would be the now obsolete corelib. I still see some use in having this.
satoon101 wrote:I have noticed that import error issue, as well, since I can no longer use test as an addon. I'm not sure if we even plan at any point to change that, but I doubt we do as it would likely get too complicated.
Possibly the output could be changed sightly, so it's the error + "[SP] Note: Check whether your addon has the name of an existing module". I think that might help with confusion