downgrade_duplicate??

Installed few new mods and then I did a generate debug out of curiousity and got this.. I played yesterday and there was no issues
Solution:
on June 8th you tried to install Mod Update Notifier which failed because you didn't update your game yet
Jump to solution
22 Replies
FICSIT-Fred
FICSIT-Fred4mo ago
Automated responses for Jevla (253238471324467200)
downgrade_duplicate
The Mod Manager is reporting an error because it's trying to modify an outdated copy of the game. This could be caused by one of two things: 1. One of the installs connected to the Profile you have selected is still running a previous version. To fix this, either uninstall it, update it, or switch to a different Mod Manager profile so that it isn't considered in the update process. 2. You have leftover files in your install directory from downgrading to play a previous version. To fix this, uninstall the game (verify files won't fix this!), delete the game install directory if it still exists (this is NOT the AppData folder, but the location where you installed the game), then reinstall the game, and reopen SMM.
Key Details for SMMDebug-2025-06-16-14-35-01.zip
SMM Version: 3.0.3
SML Version: 3.11.1
Installed Mods: 46
Game: WindowsClient CL 416835 from steam
Path: `g:\SteamLibrary\steamapps\common\Satisfactory`
Command Line: cmd /C start steam://rungameid/526870-NO_EOS_OVERLAY
SMM Version: 3.0.3
SML Version: 3.11.1
Installed Mods: 46
Game: WindowsClient CL 416835 from steam
Path: `g:\SteamLibrary\steamapps\common\Satisfactory`
Command Line: cmd /C start steam://rungameid/526870-NO_EOS_OVERLAY
sjhoward
sjhoward4mo ago
That's odd, but assuming everythings working normally (as it seems to be) you probably don't need to do anything
Jevla
JevlaOP4mo ago
its weird, I have not downgrade to previous version either, neither from Experimental. I tried switch to an empty profile to and still same thing
Robb
Robb4mo ago
{"time":"2025-06-08T22:27:00.860379+02:00","level":"ERROR","msg":"failed to install","action":{"type":"install","item":"ModUpdateNotifier","version":"2.4.0"},"install":"g:\\SteamLibrary\\steamapps\\common\\Satisfactory","profile":"Mods","error":"Because Mod Update Notifier (ModUpdateNotifier) \"2.4.0\" depends on Satisfactory (FactoryGame) \">=410840\" and Satisfactory CL385279 is installed, Mod Update Notifier (ModUpdateNotifier) \"2.4.0\" depends on Satisfactory (FactoryGame) \">=415558\".\nSo, because Satisfactory CL385279 is installed, version solving failed."}
{"time":"2025-06-08T22:27:00.860379+02:00","level":"ERROR","msg":"failed to install","action":{"type":"install","item":"ModUpdateNotifier","version":"2.4.0"},"install":"g:\\SteamLibrary\\steamapps\\common\\Satisfactory","profile":"Mods","error":"Because Mod Update Notifier (ModUpdateNotifier) \"2.4.0\" depends on Satisfactory (FactoryGame) \">=410840\" and Satisfactory CL385279 is installed, Mod Update Notifier (ModUpdateNotifier) \"2.4.0\" depends on Satisfactory (FactoryGame) \">=415558\".\nSo, because Satisfactory CL385279 is installed, version solving failed."}
FICSIT-Fred
FICSIT-Fred4mo ago
The Mod Manager is reporting an error because it's trying to modify an outdated copy of the game. This could be caused by one of two things: 1. One of the installs connected to the Profile you have selected is still running a previous version. To fix this, either uninstall it, update it, or switch to a different Mod Manager profile so that it isn't considered in the update process. 2. You have leftover files in your install directory from downgrading to play a previous version. To fix this, uninstall the game (verify files won't fix this!), delete the game install directory if it still exists (this is NOT the AppData folder, but the location where you installed the game), then reinstall the game, and reopen SMM. -# Responding to downgrade_duplicate triggered by @Robb (Busy)
Robb
Robb4mo ago
the log message causing it is from the 8th
sjhoward
sjhoward4mo ago
Looks like it's from over a week ago so safe to ignore
Jevla
JevlaOP4mo ago
im stupid, I dont understand whats the problem right now, (or what triggering the "error") more because im curious
Solution
Robb
Robb4mo ago
on June 8th you tried to install Mod Update Notifier which failed because you didn't update your game yet
Robb
Robb4mo ago
is there another error you were expecting Fred to find? there's also this message very recently but idk if it makes any popups/breaks anything
{"time":"2025-06-15T12:46:57.3926349-07:00","level":"ERROR","msg":"failed to insert mod version into local registry","mod":"SS_Mod","version":"1.1.31","err":"constraint failed: UNIQUE constraint failed: versions.mod_reference, versions.version (2067)"}
{"time":"2025-06-15T12:46:57.3926349-07:00","level":"ERROR","msg":"failed to insert mod version into local registry","mod":"SS_Mod","version":"1.1.31","err":"constraint failed: UNIQUE constraint failed: versions.mod_reference, versions.version (2067)"}
Jevla
JevlaOP4mo ago
hm alright, I cant remember it though.. 😄 Not really, I where just curious if there was any issues
Jevla
JevlaOP4mo ago
but this was yesterday? I have played yesterday after this time
sjhoward
sjhoward4mo ago
it's not anything to worry about
Jevla
JevlaOP4mo ago
alright sounds good. got little bit worried 😄
sjhoward
sjhoward4mo ago
everyone has the SS_Mod error due to a prior fuckup in versioning, and the other one was rendered obsolete by updating to 1.1
Jevla
JevlaOP4mo ago
I appreciate the info guys ❤️ 🙂 Can I remove this error file somehow so I wont get it later?
Robb
Robb4mo ago
I think if you delete the log file it will roll a new one, otherwise they roll themselves based on... file size, I think >files_logs
Robb
Robb4mo ago
the smm log file
Jevla
JevlaOP4mo ago
alright thanks 🙂
sjhoward
sjhoward4mo ago
I've seen some pretty fuckin' massive smm logs before, so I'm not sure how the limit works looks like it's 30 days or 10mb, whichever is smaller
Jevla
JevlaOP4mo ago
Confirmed it work by removing it. Deleted log file SMM folder did the work
No description

Did you find this page helpful?