✨ Option to have Separate Data Pack and Resource Pack Namespaces

[blockerlocker]

🛑 Before you Start

• I have searched existing feature requests for my feature.
• I have read the documentation, and I am sure this feature is not already implemented.
• I am using the latest version of Animated Java.
• I will only request a single feature in this request. If I have multiple feature requests, I will create a separate request for each one.

📝 Description

I am working on a project where there are a lot of animated sequences with recurring characters interacting with each other in different combinations. The easiest way to deal with this is to create separate AJ Blueprints for each combination of characters (ie; I will use "character1.ajblueprint" for a single character, or "character1+character2+character3.ajblueprint" for a scene with all 3 characters, or "character1+character3.ajblueprint" for a scene with those two, etc.)

This works fine for the most part, and on the data pack side it makes sense to give each of these character combinations different namespaces. However on the resource pack side, this results in a lot of duplicate asset bloat, with the same models and textures repeated in separate folders.

💡 Describe the solution you'd like

To remedy this, it would be nice if I could set all of the blueprints to have the same resource pack namespace while still allowing them to have separate data pack namespaces. On the user side of things, this would mean you have to be careful to make sure you have no duplicate bone names, as that would likely result in some overwriting and corruption of assets, so an option like this would make more sense as an advanced feature.

🧪 Describe alternatives you've considered

No response

[SnaveSutit]

Planned in v2.0.0.

The Blueprint namespace will be replaced with a Blueprint ID.
e.g. animated_java:my_models/my_blueprint

[SnaveSutit]

Ah, you won't be able to configure unique namespaces for data pack and resource pack.

However, if you store all of your Blueprints reference textures in a valid resource pack, Animated Java will reference those textures instead of copying them into the exported data pack.

[SnaveSutit]

2.0.0 may eventually have a feature that allows referencing other rigs, and animating them all in the same scene without having to actually import their models directly. But that may take a while.