Moving some assets is not working as expected (bonemaps?)

[solodeveloping]

Tested versions

• Reproductible in: Godot Engine v4.4.1.stable.official.49a5bc7b6

System information

Godot v4.4.1.stable - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+)

Issue description

Hello,

A few days ago I've started creating a third person shooter controller for Godot 4.

At some point, I wanted to move the files into the "addons" directory.

At first, I moved everything at once, and it failed, some files were corrupt.

So I did it manually,, file per file, in the commit history selgesel/godot4-third-person-controller@main...solodeveloping:godot4-third-person-shooter:main you can look at Sep 1, 2025 ("addons: moving player directory to addons and creating the addon") for instance), there is a bunch of commits made for this.

I thought it had worked and stopped thinking about it.

Yesterday, I wanted to use the controller in another project, and it did not worked, some files were corrupt when copying the addon's content to the other project.

When copying the files from one project to another, there are only yellow errors, and then when starting the game, the referenes are broken.

The warnings were quite unclear, I had the presence of mind of cloning the project in another directory.

There, I had a red error "file not found".

So I fixed it by editing the file manually in a text editor, and it worked, in the 2nd clone and in the other project.

What it looks like now:

"PATH:Armature/Skeleton3D": {
"retarget/bone_map": Resource("res://addons/ThirdPersonShooter/assets/Mixamo BoneMap.tres")
}

And the commit: selgesel/godot4-third-person-controller@ea3fea7

What I think is happening, since I could work on the project even though the reference was broken, is that there is a UID in the cache, which allowed me to work on it, but when moving the content to another project, the cache is not present, so it fails.

Note that I was lucky to have a red error, because the original fork owner had commit the .godot/ folder to Git, and I could have done that.

Issues:

• Moving some assets (bonemaps?) fails
• When doing it slowly (?) it works but some references/UIDs are broken
• Godot, when importing the folders in another project does not provide a clear error

Error when opening the clone project:

Error when opening the file:

Error after reloading the project:

What the scene look like normally:

Steps to reproduce

I guess you can fork on my last commit without the addons directory and move the content of the project in an addon, and it should reproduce it, last commit without the addons directory should be selgesel/godot4-third-person-controller@18d212d

For the other issues, just copy the content of the addons folder in another project, a version before I fixed the reference.

Minimal reproduction project (MRP)

This should do it selgesel/godot4-third-person-controller@18d212d

[AThousandShips]

These are the outputs of imported projects right? They don't generally support being moved like this AFAIK, see:

• When folder is renamed the use_external and save_to_file paths in import files are not updated  #108334
• glTF files with separate .bin break when moved #105966

[solodeveloping]

I'm not sure of what you mean, but the asset is a .tres (bonemap) and the reference is inside a scene.

So it's not a GLTF file issue, I thinks.

I used the "Move / Duplicate to" feature to move the files / folders.

See my fix for an example of the problem. I changed the path reference:
"retarget/bone_map": Resource("res://addons/ThirdPersonShooter/assets/Mixamo BoneMap.tres")

[AThousandShips]

So you manually created the bonemap?

[solodeveloping]

The original repository owner did something.

I'm not sure of what he did.

But the fact remain that I would expect to be able to move it using the move feature, if it's badly done, I would expect an error, and when transferring the files to another project, I would expect a clear error.

[AThousandShips]

I don't know where the original bone map is from, but it's referenced by name so moving it would require the editor to detect it, but if it's extracted from the imported file it is probably the same problem as the bugs linked above

But will see what the asset pipeline team say about this since I don't know how this is supposed to work