SnaveSutit
commented
1 month ago I will allow the user to configure the animated_java: namespace, however I don't like the idea of removing the namespacing layer entirely by moving the export namespace up a layer. It makes it too easy to make conflicts between unaffiliated packs.
At least with the default AJ namespace it's only conflicts between AJ packs.
I'll also be implementing the ability to have folders in the export namespace, so you can compartmentalize even more.
Current:
- Export namespace:
ghost - Result:
animated_java:ghost/summon
Proposal:
- Export Namespace:
spooky:models/ghost - Result:
spooky:models/ghost/summon
Without intermediary folder:
- Export Namespace:
spooky:ghost - Result:
spooky:ghost/summon
Feel free to ask questions or suggest alternatives
I'd like to be able to customize the name of the root namespace, which currently is always set to "animated_java". Although you can specify a namespace for a blueprint, currently this takes the form of "animated_java:". My proposed change would simply eliminate the "animated_java" namespace and go straight to the blueprint namespace.
The change would be: animated_java:blueprint_namespace/ -> blueprint_namespace:
This would allow for more advanced customization as well as much shorter function names for ease of typing.