🐛 Export Namespace being ignored

[IAmTheRealDonCheadle]

Describe the bug
When using save-as for an already existing animated java rig that has exported to a minecraft world, a new blueprint is created. When attempting to export the new rig with a new export namespace, it attempts to overwrite the previous blueprint's export, despite the export namespace clearly being different. This will also cause the original rig in the world to become broken and the "wrong version" error message will appear, despite it being the correct version. Restarting AJ and BlockBench did not fix this.

To Reproduce
Steps to reproduce the behavior:

1. Create a rig, or use a pre-existing one, and export it to a minecraft world of your choosing
2. Create a copy of the rig by using "Save As"
3. Rename the export namespace in the blueprint settings
4. Attempt to export rig

Expected behavior
The rig should export using the written namespace.

Error Message

ENOENT: no such file or directory, open 'D:\Program Files\minecraft house\home\1.22\saves\super mario bros\datapacks\game\animated_java\data\animated_java\tags\function\goomba\as_root\post_tick.json'
Error: ENOENT: no such file or directory, open 'D:\Program Files\minecraft house\home\1.22\saves\super mario bros\datapacks\game\animated_java\data\animated_java\tags\function\goomba\as_root\post_tick.json'
    at async open (node:internal/fs/promises:639:25)
    at async Object.readFile (node:internal/fs/promises:1242:14)
    at async compileDataPack (PLUGINS/(Plugin):animated_java.js:3202:7396)
    at async actuallyExportProject (PLUGINS/(Plugin):animated_java.js:3186:44568)
    at async exportProject (PLUGINS/(Plugin):animated_java.js:3191:68)

Screenshots
Picture of rig "goomba" becoming broken after attempting to export "mushroom" rig.

Export namespace clearly written as "mushroom" and not "goomba"

Desktop (please complete the following information):

• OS: Windows 10
• Version 1909

Additional context
This issue also happens when creating a new blueprint while having block bench open.

[SnaveSutit]

This is a known issue, with a temporary workaround, that will be fixed in 1.6.5.