UID duplicate detected between [X] and [Y] at startup

When opening an existing project, it is immediately marked as edited (tagged with a *). And if you close it immediately, without editing it, you’re asked to save.

It’s an innocuous nuisance, but it annoys me nontheless.

I expect I’m not the only one this happens to.

This is on latest version (4.4.1.stable). Can’t remember for sure if that existed before, but I do think so.

I’m using 4.4 stable. I don’t see the issue. On 4.4.1 I see momentary * but goes away. I can close the project with no prompt.

I’ve just rechecked multiple times and it’s just weird.

I opening the project–it’s maximized–look at top left and see a * appear then disappear then reappear. I then proceed to save everything (CTRL-SHIFT-ALT+S) and then close Godot and you can clearly see, in the top left, that the project is tagged as edited with a star appearing, then the whole thing close properly.

I don’t know what to say.

I’m not 100% sure, but I think this might be caused by the following warning I get after opening the project:

WARNING: editor/editor_file_system.cpp:1358 - UID duplicate detected between res://Scenes/Equipment/weapon_sword.tscn and res://Scenes/Equipment/weapon_bow.tscn.
WARNING: editor/editor_file_system.cpp:1358 - UID duplicate detected between res://Scenes/Equipment/weapon_unarmed.tscn and res://Scenes/Equipment/weapon_sword.tscn.

I think this links to the following Github issue: No fix is offered for existing duplicate UIDs · Issue #102490 · godotengine/godot · GitHub

PS: Changing the title of post to better reflect the above.

PS:
After opening the scene files in NP++, I can’t find two identical IDs so, I’m not sure what going on.

PPS:
Nevermind, I’m blind. I just woke up. The UIDs are indeed identical between the three files.

I’ll manually fix the problem, but this shouldn’t happen, regardless of the way this has happened in the first place. I don’t get why it’s not internally fixed when detected and properly saved when the affected files are saved.

Alright, well… I tried.

The warnings are gone, but the behavior still exists. :man_shrugging: