Heres the command line arguments for my .bat file
Code: Select all
Factorio.exe --start-server "C:\Users\repub\Downloads\Factorio_x64_0.13.0\Factorio_0.13.0\saves\F1.zip"
So step one, windows OR linux
Redownload the .zip or headerless version for your os build.
From their step 2
Generate new world (it doesn't matter if its from a .zip instance, a steam install instance, or install directory instance)
Step 3
Copy that world .zip into the save folder (IE: Save/F1.zip)
Step 4
In the bin directory of your build (ill use windows for this example but linux is identical), you will create the .bat using code i provided earlier
Step 5
On windows the server should load up, all yays, technically step 5 should be to configure your ports, and your config.ini port, if thats done then step 5 should just work.
Alrighty just figured out your problem on your end. Okay throw away like 95% of what you did, and rework it as per my prior step by steps. The rest for configurations can be in the .bat file no crazy configs needed for the server file you mentioned other than your factorio.com username, password, and then from their your title for your server instance, if its public or not (if its public or hidden or password protected YOU WILL need the factorio.com username/password filled out)Bluelight wrote:If you don't have the full path in the start-server thing then it will try to load the save called F1.zip in the same dir as the bat file is..
And if you don't have the folder called save inside the "C:/Users/repub/Downloads/Factorio_x64_0.13.0/Factorio_0.13.0/" -folder it will not work either.. Sorry for messing around, I'm editing as I go.. lol
My server is running fine except for the damn port.. I can connect directly and play but not with the server browser, which I have waited weeks for to test and now it won't work.. How annoying!
The login for connecting to your server (im assuming your on the host machine playing), if your hosting the server in the background, and then you try to connect, you will need to connect under 127.0.0.1:4444 (so you connect on host machine through feedbackloop IP but your also self identifying as admin with 4444 it should prompt you for username/password) from their to login
If your connecting to the server remotely you can do the EXTERNALIP:4444 to connect as admin
If your connecting to the server on LAN (your on same network server is on same network but different machine), you can do it as SERVER LAN IP:4444 and same as prior description. PHeeewww glad i figured out my problem though, hopefully my explanation helps you, thanks to our pow wowing i was able to figure it all out now. Feel free to break it down step by step what went wrong and ill help you fix your instance to