Factorio Forums

I haven't played factorio since 0.15 and have recently updated the game to the latest experimental branch but when I try to load my older world 2 mods are red in the mods list. DayPhaseAdjuster and 200 Inventory Size, these mods are no longer even activated and I've tried the sync mods with world thing but it doesn't seem to do anything.

Whenever I try to launch the world it just says "Unknown mod setting type: 50"
World version is 0.15.30-1 (img is another world)

Can you upload the save file?

Rseding91 wrote:Can you upload the save file?

Yea I've attached it to this reply

+1

I have attached my save where this happens.

Also, duplicate: viewtopic.php?f=49&t=58308

Thanks for the saves but I can't reproduce any issues with those saves?

Are you sure you uploaded the right save? In the screenshot you're selecting "HardSave" and the file is called "Hard Save".

Rseding91 wrote:Thanks for the saves but I can't reproduce any issues with those saves?

Are you sure you uploaded the right save? In the screenshot you're selecting "HardSave" and the file is called "Hard Save".

Yea the one I'm having issues with it "Hard Save" but whenever it fails to load that message shows up and just goes on the "HardSave" page

I was able to fix the issue by downgrading the game to the last 0.15 version, then upgrading the first 0.16 version and saving the world in that version. Then updating the latest 0.16 version and it works fine.

ShadowDelux wrote:I was able to fix the issue by downgrading the game to the last 0.15 version, then upgrading the first 0.16 version and saving the world in that version. Then updating the latest 0.16 version and it works fine.

Can you give me the save file and exact series of steps I need to reproduce the error? When I test with the "Hard save" file it doesn't ever give me the error - with or without mods.

Nevermind, I fixed the issue in some unrelated refactoring I did for the next version of 0.16 which is why I couldn't reproduce the error - it was already fixed

Rseding91 wrote:Nevermind, I fixed the issue in some unrelated refactoring I did for the next version of 0.16 which is why I couldn't reproduce the error - it was already fixed

Getting too efficient with the bug fixing, fixing them before they even get reported. Gonna tear a hole in space/time if you aren't careful