path: root/factorio-init.conf
diff options
authorVöjket2021-05-08 18:10:31 -0400
committerVöjket2021-05-08 18:10:31 -0400
commit030140e377ecf331eb9074e28ce5193f68dbb297 (patch)
tree1d916c1fe0bd2464b789f18df202092ad22f8b9c /factorio-init.conf
parentd3d4ac1a37bf02c496988426ca85ebcdbc45d412 (diff)
Updated to 3.1.0, modified configs significantly
Diffstat (limited to 'factorio-init.conf')
1 files changed, 58 insertions, 15 deletions
diff --git a/factorio-init.conf b/factorio-init.conf
index a7f3d0b19ed..5d31eea8f8c 100644
--- a/factorio-init.conf
+++ b/factorio-init.conf
@@ -4,8 +4,15 @@
# this script is not behaving the way you expect it to do
+# Enable alternative glibc directory for systems using older glibc versions ( ie RHEL CentOS and others )
+# Put the Absolute path to the side by side glibc root here
+#Version of alt glibc goes here (i.e 2.18)
# What do you want to call this service?
# Which user/group is running factorio?
# Running any public service as "root" is generally not recommended
@@ -13,28 +20,43 @@ USERNAME=factorio
# The absolute path to the factorio directory
-# Server settings file, see data/server-settings.example.json
+# Server admin settings
+# Server admin list file, must be in the following format:
+# [
+# admin1,
+# admin2,
+# adminX
+# ]
+# If the file does not exist in ${FACTORIO_PATH}/data, a blank copy will be created.
+# The whitelist file is in the same format as the admin list file.
+# If the file does not exist in ${FACTORIO_PATH}/data, it will not be used.
+# The banlist file is in the same format as the admin list file.
+# If the file does not exist in ${FACTORIO_PATH}/data, it will not be used.
# Port on which you want to run the server
-# Save the command/chat/log on server start? Default location /opt/factorio/server.out
+# Save the command/chat/log on server start? Default location /opt/factorio/server.out
# Setting this to 0 will cause the script to erase the log file on each start
# If you set this to 1 you might want to apply logrotate on the log or it will eventually fill your disk
-# Factorio comes packaged in a tarball containing the directory named "factorio"
-# when using this scripts update/install command we expect to see this very
-# directory. If you want to supply your own update/install tar other than what you can download
-# from you can use this option to tell the script this is ok.
-# If you place your factorio install within a directory named "factorio" and you update/install
-# with the official tarball you can safely ignore this option.
+# Delay starting the game server until the we confirm the pingpong servers are reachable.
+# This makes sure that game server detects the correct external IP in a NAT setup.
+# Useful for Cloud providers where VMs may start faster than their Internet connectivity is plumbed.
+# Using install, it's possible to cache the tarballs fetched from Wube
+# set this to a directory where you allow this script to create a 'factorio-install' directory
# narcotiq made a sweet update script for factorio and by cloning into this
@@ -52,7 +74,28 @@ HEADLESS=1
+# set this to a directory where you allow this script to create a 'factorio-update' directory.
+# The directory ${UPDATE_TMPDIR}/factorio-update will be used by the updater to store patches for factorio.
+# If you set UPDATE_PERSIST_TMPDIR=1 this script will not try to clean up the directory.
+# This will effectively cache the patch files for later use but be aware that you need to handle eventual clean-up
+# of the ${UPDATE_TMPDIR}/factorio-update directory yourself.
+# prevent the script from restarting factorio during updates by setting this to 1
+# (note! This also means that you will be prevented from applying updates with the
+# script if the server is running)
+# There is also integration with Tantrisse's Factorio-mods-manager
+# Uses UPDATE_USERNAME and UPDATE_TOKEN for mod management
+# Access is exposed under the mod subcommand
+# To install:
+# git clone
+# absolute path to the Factorio-mods-manager script
# Extras
# Additional binary arguments, these will be sent to the binary when issuing the "start" command