Factorio Forums

Converted a 0.12.35 save to 0.13 and whenever my friend tried to join my Headless MP Server he gets a deserialisation error and if I leave to rejoin I get the same error with a different ID, same if I restart the server, same thing happens to both the "save" and the autosaves, but usually with different IDs.

The last error message I got from my server log was:
4.959 Error MultiplayerManager.cpp:129: MultiplayerManager failed: "Deserialisation error, target with id 9977 doesn't exist"
4.960 Info MultiplayerManager.cpp:999: networkTick(0) mapTick(-1) changing state from(CreatingGame) to(InitializationFailed)
4.962 Error Main.cpp:442: Couldn't load the game for MP: Deserialisation error, target with id 9977 doesn't exist

I have two mods, Larger Inventory 1.0.1 which was updated for 0.13 along with the Rail Tanker Mod which was also updated for 0.13, I had other mods in 0.12.35 but I removed them and resaved the map for 0.13 with only these two mods on my PC, then copied it all to my headless server. I don't have any Blueprints in my hand as I haven't researched them or rails either. I'm not sure whether it happens at a set time or if I craft something in particular.

Hello, i got exactly same error with >30h savegame in 0.13.0 and no mods (started in 0.12.29) :/ i tried with an older 0.12.35 save version and placed some chests around me and after that the error occurs (seems to be an older issue that now happens again with 0.13.0) please provide a fix for that as soon as possible..

see:
viewtopic.php?t=19209
viewtopic.php?t=20865

No one else having issues with that? I would really appreciate if i could get my savegame fixed

If you update to 0.13.1 and use the 0.12 save file it should be resolved. Any corrupt saves created in 0.13.0 are lost.

Rseding91 wrote:If you update to 0.13.1 and use the 0.12 save file it should be resolved. Any corrupt saves created in 0.13.0 are lost.

Thankfully I had the sense to keep the 0.12.35 saves separate from the 0.13.0 versions of the same. Thanks for letting me know it was fixed in 0.13.1