Satisfactory Modding•7d ago

Could not read save mod metadata

I have the problem that while me and my friend played yesterday first some item Information stopped updating and after trying to reconnect you got stuck in the loading screen. The save has a Warning Symbol before the Name and if you try to load this save to the dedicated Server it says "Could not read save mod metadata. Mod compatibility check was skipped." Any ideas how to fix it?

SMMDebug-2024-11-12-...

10 Replies

FICSIT-Fred•7d ago

SMM Version: 3.0.3
SML Version: 3.8.0
Installed Mods: 28
Game: LinuxServer CL 378208 from JoPre
Path: `sftp://user:pass@******/`

SMM Version: 3.0.3
SML Version: 3.8.0
Installed Mods: 28
Game: LinuxServer CL 378208 from JoPre
Path: `sftp://user:pass@******/`

-# Responding to Key Details for SMMDebug-2024-11-12-19-45-22.zip triggered by @Jonas W.

sjhoward•7d ago

@Robb (Busy) This sounds like something I've seen before & didn't know how to deal with - I very much doubt it's ContentLib causing it, but I did notice in both cases that something's tripping CL into debug log level, which could be a common cause? Able to give any hints?

[2024.11.12-18.42.51:268][  0]LogSatisfactoryModLoader: Error: Plugin AlternateRecipes has invalid Game Version value: : Version range cannot be empty
[2024.11.12-18.42.52:176][  0]LogSatisfactoryModLoader: Discovered 7 game instance modules
[2024.11.12-18.42.52:176][  0]LogSatisfactoryModLoader: Dispatching lifecycle event CONSTRUCTION to game instance modules
[2024.11.12-18.42.52:178][  0]LogSatisfactoryModLoader: Registering dynamic Blueprint logging category LogContentLib with default verbosity Verbose
[2024.11.12-18.42.52:178][  0]LogContentLib: Warning: [/ContentLib/CL_InitInstance]: CL Config Instance was not ready yet, so falling back to 'Debug' log level
[2024.11.12-18.42.52:178][  0]LogContentLib: Error: [/ContentLib/CL_InitInstance]: [CL] InitInstance Updated log level to Debug

[2024.11.12-18.42.51:268][  0]LogSatisfactoryModLoader: Error: Plugin AlternateRecipes has invalid Game Version value: : Version range cannot be empty
[2024.11.12-18.42.52:176][  0]LogSatisfactoryModLoader: Discovered 7 game instance modules
[2024.11.12-18.42.52:176][  0]LogSatisfactoryModLoader: Dispatching lifecycle event CONSTRUCTION to game instance modules
[2024.11.12-18.42.52:178][  0]LogSatisfactoryModLoader: Registering dynamic Blueprint logging category LogContentLib with default verbosity Verbose
[2024.11.12-18.42.52:178][  0]LogContentLib: Warning: [/ContentLib/CL_InitInstance]: CL Config Instance was not ready yet, so falling back to 'Debug' log level
[2024.11.12-18.42.52:178][  0]LogContentLib: Error: [/ContentLib/CL_InitInstance]: [CL] InitInstance Updated log level to Debug

Jonas W.OP•7d ago

Loading the save in single Player work. That's something I'm wondering about

Robb•7d ago

CL is likely unrelated. The very first access to the log level is before there is a context that the value is cached in, so it always happens. The fact that the log level changed is not actually an error, that's a hold over from Nog's stuff that I haven't changed Re: the issue, not sure what could cause this, could you send the save file here too?

Jonas W.OP•6d ago

JoPre_v2.0.1.sav

Jonas W.OP•11h ago

Anyone a idea? Or is the save dead

sjhoward•11h ago

have you tried loading the save into SCIM, downloading it, and loading that new copy? >scim

FICSIT-Fred•11h ago

https://satisfactory-calculator.com/en/interactive-map https://discord.com/invite/0sFOD6GxFZRc1ad0

[SCIM] Satisfactory - Calculator

Satisfactory helper to calculate your production needs. | Gaming Tool/Wiki/Database to empower the players.

sjhoward•11h ago

That can sometimes clean up issues in save files think it's a bit of a longshot in this case

Jonas W.OP•11h ago

I will try it. Thanks seems not working too. warning message while loading that mod meta data could not readed and the save has a warning symbol before the name Nope it's not working :/

Gaming

Programming

Could not read save mod metadata