Closed utoxin closed 5 years ago
If it matters, I use ModMyFactory to launch my game normally. I ran it from the correct path for the mods folder inside my managed instance, but it looks like maybe it tried to run Factorio from a default location?
It must have somehow found an older version of factorio. I gave it a set of default locations:
"C:\\Program Files\\Factorio\\bin\\x64\\factorio.exe",
"D:\\Program Files\\Factorio\\bin\\x64\\factorio.exe",
"C:\\Games\\Factorio\\bin\\x64\\factorio.exe",
"D:\\Games\\Factorio\\bin\\x64\\factorio.exe",
"C:\\Program Files (x86)\\Steam\\steamapps\\common\\Factorio\\bin\\x64\\factorio.exe",
"D:\\Program Files (x86)\\Steam\\steamapps\\common\\Factorio\\bin\\x64\\factorio.exe"
It traverses these in order. What im guessing has happened is that the first working path that it encountered is an outdated factorio executable. You can start auto.py
with --factorio=PATH
, or you can edit these in the auto.py
script.
Ahhh. Okay. I can work with that. I'll freely admit my setup is non-standard, so that makes sense. (But man, when you play multiple different sets of mods, ModMyFactorio is SOOOO nice. :)
I dont know, you can just create a shortcut to a factorio.exe with a separate mod folder.
By the way, you might want to also add that into the auto.py
code if you find that you need to redownload/reenable all the mods because the launcher might store the mods in a non standard folder.
It's working well for me now. :) Thanks for the help. Looking forward to playing with this.