[SOLVED] Running backup of .12 causes .13 to start instead
Posted: Sat Jul 02, 2016 2:04 am
I wanted to be able to try out 0.13 without having to uninstall it and revert to 0.12 every time I wanted to work on my existing game that I was running with a few mods, so I copied Factorio out of its location in steam apps before setting steam to update to the latest experimental version.
The expected behavior is that if I run the 0.12 executable (via a shortcut which has the working directory set to the location of the 0.12 backup copy, with its /bin/x64/Factorio.exe in the Run field), that version would start and load the 0.12 mods, while if I ran the regular steam shortcut it would launch 0.13... But regardless of how I try to start 0.12, it always somehow runs version 0.13 instead.
I set use-system-read-write-data-directories=false in the config-path.cfg file (and moved my 0.12 saves and mods into that folder) to make sure that the different versions of the game shouldn't have any conflicts, but that seems to have had no effect on the unexpected behavior.
If I tell steam to delete local content for 0.13 and then attempt to run the backup of 0.12, steam behaves as if I attempted to run Factorio through its interface and prompts me to install it. And if I manually delete the 0.13 install instead of using steam to do it, steam gives me an error launching the game.
What is going on here and how do I make this work?
The expected behavior is that if I run the 0.12 executable (via a shortcut which has the working directory set to the location of the 0.12 backup copy, with its /bin/x64/Factorio.exe in the Run field), that version would start and load the 0.12 mods, while if I ran the regular steam shortcut it would launch 0.13... But regardless of how I try to start 0.12, it always somehow runs version 0.13 instead.
I set use-system-read-write-data-directories=false in the config-path.cfg file (and moved my 0.12 saves and mods into that folder) to make sure that the different versions of the game shouldn't have any conflicts, but that seems to have had no effect on the unexpected behavior.
If I tell steam to delete local content for 0.13 and then attempt to run the backup of 0.12, steam behaves as if I attempted to run Factorio through its interface and prompts me to install it. And if I manually delete the 0.13 install instead of using steam to do it, steam gives me an error launching the game.
What is going on here and how do I make this work?
I purchased it before it was available on steam. Apparently I was misinformed, or perhaps confusing the situation with KSP on Steam. Thanks for helping me solve this though!