Basic file configuration

Before we can run the server, some basic files have to be configured.

These file are normally spread out over de installation folders of factorio, as listed below.

Original File locations:

server-settings.example.json
- ..\Factorio\data\
config.ini
- ..\Factorio\config\
- Or
- ..\AppData\Roaming\Factorio\config\
Multiple files
1. server-adminlist.json
2. mods & saves folder
- ..\AppData\Roaming\Factorio\
factorio.log
- ..\Factorio\data\
- Or
- ..\AppData\Roaming\Factorio\

As we use the Zip package, all the needed files will be in one location for easy use and access. *

Now that Factorio is Installed, we can start on setting it up the headless server.

When you used option 1, Go to the Zip package and extract/move its content into the factorio installation folder. **
When you used option 2, Just move the extracted folder "named Server" into the factorio installation folder

Now you should get something like c:\factorio\server

The server folder contains all files we are going to need to setup the server.

It is also possible to collect all files, from their respective locations, as mentioned above

Notes:

* This is only possible because of the batch file we will be using.
** The zip package can be found here

File Configration

Lets start with the server-settings.json in the server folder.

This file contains the most information about the server.

The following manditory items will need to be filled-out / checked:

name
- Name of the game as it will appear in the game listing
max_players
- Maximum number of players allowed, admins can join even a full server. 0 means unlimited
Username & Password or/and Username & Token
- Your factorio.com login credentials. Required for games with visibility public
- Authentication token. May be used instead of 'password', this can be found on your factorio.com account
afk_autokick_interval
- How many minutes until someone is kicked when doing nothing, 0 for never.

Advised, but optional items are:

game _password
- If you want the game to be private, to a select amount of players
tags
- like "ENG only", "private", "Bobs Mods"
autosave_interval
- Autosave interval in minutes
autosave_slots
- server autosave slots, it is cycled through when the server autosaves.
max_upload_slots
- optional, default value is 5. 0 means unlimited,
max_upload_in_kilobytes_per_second
- optional, default value is 0. 0 means unlimited

server-settings.example.json

Next up is the Config.ini (this is only necessary if you have read/write problems with more then one instance on the same machine )

With this file you can control a few things that are not available in the server-settings.json and many setting that have no impact on a server like graphics settings that are not used by a headless server.

In the pre modified file, the mandatory change has already been made. You can see all the active items in Black text or leave as is. (the green text is the inactive code)

Its mandatory to change the following:

enable-new-mods : This just a precaution to make sure the server will add mods you might add to the mod folder.

The following is recommended when running multiple instances and running into an error as below:

As you can see in de Example the read-data and write-data has been changed, "this is not mandatory"

The original code is:

read-data=__PATH__system-read-data__
write-data=__PATH__system-write-data__

This is a change that had to be made, as I ran into the following error. Files "A to Z" are already in use by an other program, which in turn crashed the server boot up process.

The program that was using the files was the first headless server.

By making changes to use a dedicated path, I was able to avoid this problem.

The example solution code is:

read-data=C:\Factorio\data
write-data=C:\Factorio\data

Google Sites

Report abuse