Cached/database entry of mod ID could show duplicate entry until rediscovery if mod id changes
Mod id changes are rare and shouldn't happen often but they can occur, most often if someone changes domain and updates their mod reverse tld to match
Having 1.1.1 installed and just removed (after the manifest got updated, but without rediscovery)
Restarting Resolute and Rediscovering mods (after adding 1.1.1 again for it to discover)
Partly related to https://github.com/Gawdl3y/Resolute/issues/128
I don't think there's much to be done about this one, since the ID is the definitive way that Resolute currently identifies a mod. If a mod's ID changes, it'd be expected for there to be temporary duplicates depending on the situation. In order to deduplicate these, there'd have to be some kind of heuristics to match two similar mods together - whether that be just seeing if all of their artifacts names and/or hashes match, or just the mod name as well, etc. I'm not a huge fan of that conceptually, however, because it seems like it'd be somewhat fragile and could potentially cause issues in the future for legitimate "duplicates".