Many game servers require start parameters, these are command-line options that are set with the server executable when the server starts.

Predefined Parameters

LinuxGSM often uses predefined parameters that can be edited. This makes adjusting common settings easier and allows them to be displayed in ./gameserver details.

## Predefined Parameters | https://docs.linuxgsm.com/configuration/start-parameters
defaultmap="map_name"
gamemode="game_mode"
maxplayers="42"
port="27015"
sourcetvport="27020"
clientport="27005"

Additional Parameters

Additional command-line parameters can be added to the startparameters setting.

Anything added will be appended to the server executable binary.

Basic Example

Full Example

## Server Parameters | https://docs.linuxgsm.com/configuration/start-parameters#additional-parameters
startparameters="-game nmrih -strictportbind -ip 91.121.72.41 -port 27015 +clientport 27017 +tv_port 27016 +map nmo_broadway +servercfgfile nmrih-server-1.cfg -maxplayers 8"

Parameters reference

• 7 Days to Die

• Gold Source Servers

The command-line tool for quick, simple deployment and management of Linux dedicated game servers.

Welcome

Welcome to the LinuxGSM documentation covering various topics related to the project.

Contributions to this documentation are welcome and can be submitted via GitHub.

Game server config files are the configuration files used by the game server to store various game server settings, such as the server name, maximum players, map cycle, etc. These settings can be edited to customise a game server. Different game server configs can use different syntax and work slightly differently, but all do the same basic job of editing a game server settings.

Config file's location

The details command will provide you with some config file information. However, some servers do use multiple config files.

Command

./gameserver details

Sample output example

./gmodserver details

gmodserver Script Details
==================================================================================
Service name:        gmod-server
gmodserver version:  170110
User:                ultimatebyte
GLIBC required:      2.15
Email alert:         off
Pushbullet alert:    off
Update on start:     off
Location:            /home/gmodserver
Config file:         /home/gmodserver/serverfiles/garrysmod/cfg/gmod-server.cfg

LinuxGSM Custom Config's

Whenever possible, LinuxGSM provides basic easy-to-use game server configuration files. A dedicated repository has been made so all server admins can benefit, even Windows admins.

This configuration file is automatically downloaded upon server installation.

Config file naming

Example

For source servers, the default server.cfg is not used with LinuxGSM. Instead if you're running ./csgoserver, then the config file will be called csgoserver.cfg.

Missing configuration file handling

LinuxGSM will always check a config file is present when starting a server. If a config file is missing, it will re-download the default one or give a warning.

Where are the settings I'm looking for?

One of the goals of LinuxGSM is to make managing these as easy as possible, by providing all important settings out of the box, wherever they are. There is no general rule about where config files are set. It is a good idea to look for the official documentation of the game server that you're trying to run in order to find relevant information about settings.

I found missing settings or an error with config files?

If you found settings that are absent from the default configuration file provided by LinuxGSM that would be a useful addition, then you can open an issue or a pull request.

Once the installation is complete a working game server will be available. Use the various LinuxGSM commands available to manage the game server.

Read through this documentation to ensure you understand how to configure your game server.

The configuration of LinuxGSM is handled through several config files, which are loaded in a specific order. Understanding this process is crucial to ensure that settings are appropriately placed within the correct config files.

Config Files Location

Relative to your installation directory, config files are located in:

Configuration Mechanism

The LinuxGSM configuration mechanism is intentionally designed to provide users with several advantages. These include the ability to access new features, retain default settings, effectively handle multiple instances, and allow LinuxGSM to update the configuration when necessary.

Configuration files

_default.cfg

_default.cfg is the template config, this file is a base of all available default settings. It can not be edited and is updated by LinuxGSM when using ./gameserver update-lgsm. This config is loaded first.

common.cfg

common.cfg is used for common settings that apply to all game server instances of the same installation. This saves having to apply the same settings multiple times.

instance.cfg

instance.cfg is the configuration file used for each individual game server instance. Settings here will only apply to this specific game server instance. This config file takes the same name as the game server instance name ./gameserver. For example, if ./csgoserver is used the instance.cfg will be called csgoserver.cfg. This config is last to be loaded.

Secret Configs

Secret configs serve as a designated space for storing sensitive information, such as steam login details, separately from the main config files. This separation allows server administrators to back up their configurations while excluding sensitive data, enhancing security and privacy. It proves especially valuable for administrators who wish to create a version-controlled skeleton configuration using git that might eventually become publicly accessible.

It's essential to understand that the secret config is not encrypted or inherently more secure than other config files. However, it provides a convenient way to keep sensitive information isolated from the rest of the configurations.

To distinguish secret configs from others, their names are typically prefixed with the word "secrets." This naming convention aids in identifying and managing these specific files.

Config Load Priority

When the configuration files are loaded by LinuxGSM, they adhere to a specific order. Initially, settings are fetched from _default.cfg, followed by common.cfg, and finally instance.cfg. As a result, any setting specified in instance.cfg will take precedence over the same setting in common.cfg, which, in turn, overrides the setting in _default.cfg. This hierarchical loading ensures that settings become increasingly specific, with instance configurations having the highest priority.

LinuxGSM config load order

How to Use

Simple Configuration

This configuration fits most scenarios, where you have a simple installation with only one instance.

1. Browse to the config-lgsm directory

1. Use ls to list the directory contents and find the name of your instance.cfg.

2. Use cat or nano to see the contents of _default.cfg .

1. Copy the individual settings you want to change to instance.cfg

Multiple Instances Configuration

1. Browse to the config-lgsm directory

1. Use ls to list the directory contents.

2. Use cat or nano to see the contents of _default.cfg .

3. Copy any settings you want to apply to all instances to common.cfg.

1. Copy any settings you want to apply to a specific instance to its instance.cfg.

Examples

Example 1

Load de_nuke as default map on csgoserver:

Example 2

Load cs_office as default map on csgoserver:

Example 3

Load de_dust2 as default map on csgoserver:

Example 4

Load de_nuke as default map on csgoserver instance and de_inferno on csgoserver-2 instance:

Example 5

Load de_nuke as default map on csgoserver instance and cs_office on csgoserver-2 instance:

The test-alert command is used to send a test alert that is used to ensure that configured alerts are functioning and being recieved.

Commands

Standard: ./gameserver test-alert

Short: ./gameserver ta

Using systemd

systemd is the default init system for most modern distros.

You need to create a service file in /etc/systemd/system/

Example ts3server.service

[Unit]
Description=LinuxGSM Teamspeak3 Server
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
User=ts3server
WorkingDirectory=/home/ts3server
#Assume that the service is running after main process exits with code 0
RemainAfterExit=yes
ExecStart=/home/ts3server/ts3server start
ExecStop=/home/ts3server/ts3server stop
Restart=no

[Install]
WantedBy=multi-user.target

Replace the user and paths to fit your setup.

You need to reload the systemd-daemon once to make it aware of the new service file by systemctl daemon-reload

Now you can do

systemctl start ts3server # Start the server
systemctl stop ts3server  # Stop the server
systemctl enable ts3server # Enable start on boot
systemctl disable ts3server # Disable start on boot

Crontab

    @reboot '/home/username/gameserver monitor' > /dev/null 2>&1

Using monitor command

After a reboot, any game server that has a "started" status will be started on boot. Servers that were manually stopped will remain stopped.

crontab -e
@reboot su - username -c '/home/username/gameserver monitor' > /dev/null 2>&1

Using start command

Start a game server unconditionally, even if you manually stop a server.

crontab -e
@reboot su - username -c '/home/username/gameserver start' > /dev/null 2>&1

rc.local

rc.local is another method to run scripts on boot. Any commands added to the rc.local file will run on boot.

nano /etc/rc.local
su - username -c '/home/username/gameserver start'

To automate LinuxGSM you can set scheduled tasks using cronjobs, to run any command at any given time.

Commonly used scheduled tasks are:

Crontab

To access and edit your cronjobs use crontab.

crontab -e

Cronjob as a user or root

It is possible to set up cronjobs as any user including root. The recommended way is to set up cronjobs using the game servers user account. However, If you run several game server installations on your server you may want to centrally manage cronjobs then using root.

User cronjob

* * * * * [/path/to/script] [command] > /dev/null 2>&1

Root cronjob

* * * * * su - username -c '[/path/to/script] [command]' > /dev/null 2>&1

Cronjob Timing Examples

Every single minute

* * * * *

Every 30 minutes

*/30 * * * *

Every hour

0 * * * *

Every two hours

0 */2 * * *

Every two hours at 30 minutes past the hour

30 */2 * * *

Every day at 5:10 PM

10 17 * * *

Every Wednesday at 1 AM

0 1 * * * 3

Every Five Days at 1 AM

0 1 */5 * *

Cronjob Generator

LinuxGSM Cronjobs examples

Daily cronjob

Here is an example of a user based cronjob for a daily restart at 5 am.

0 5 * * *  /home/username/gameserver restart > /dev/null 2>&1

Here is an example of a root based cronjob for a daily restart at 5 am.

0 5 * * *  su - username -c '/home/username/gameserver restart' > /dev/null 2>&1

Every X Time cronjobs

Here is an example of a user based cronjob to monitor your server every 5 minutes.

*/5 * * * *  /home/username/gameserver monitor > /dev/null 2>&1

Here is an example of a root based cronjob to monitor your server every 5 minutes.

*/5 * * * *  su - username -c '/home/username/gameserver monitor' > /dev/null 2>&1

Complete Example

Below is a recommended basic example and will do the following:

• Monitor your server every 5 minutes.

• Check for an update every 30 minutes, update and restart only if an update is detected.

• Restart and check for an update every day at 4:30 AM

• Update check and update LinuxGSM every Sunday at midnight.

*/5 * * * * /home/username/gameserver monitor > /dev/null 2>&1
*/30 * * * * /home/username/gameserver update > /dev/null 2>&1
30 4 * * *  /home/username/gameserver force-update > /dev/null 2>&1
0 0 * * 0 /home/username/gameserver update-lgsm > /dev/null 2>&1

How is the information used?

All data collected is used to provide insight into which game servers, distros, and servers are popular with game server admins. This will assist in prioritising LinuxGSM development and give me (Daniel Gibbs) a never before insight into the number of people using LinuxGSM. This is a massive personal motivator as it has previously been difficult to know how many people actually use LinuxGSM.

What information is collected?

Below is a list of types of data collected

Basic Info

• Game Server - Knowing the game server you are running gives insights into which servers are popular and can help shape development priorities.

• Distro - It is useful to know which distros LinuxGSM is being used on to help focus development.

• LinuxGSM Version - The currently installed version of LinuxGSM.

• Alert Types - The alert types that have been turned on.

Game Server Usage

Gathering game server usage helps set the minimum required hardware for each game server. This is particularly useful for resource-intensive servers.

• CPU Used - The CPU usage in MHz (rounded to the nearest 100MHz) of the game server.

• RAM Used - The memory usage in MB (rounded to the nearest 100MB) of the game server.

• Disk Used - The storage taken by the game server (serverfiles directory) of the game server.

Server Hardware

Gathering information on the server hardware being used to host a Game Server. This provides useful stats on the sorts of hardware game server admins are deciding to use.

• CPU - Gathers the CPU Manufacturer and Model.

• RAM - Total server RAM.

• Disk Space - Total server disk space.

Country of origin

The country of origin is shown identifying where in the world LinuxGSM is being used.

The country of origin is no longer working with GA-4 but might be available again in the future

How is Information collected?

LinuxGSM Stats uses Google Analytics (GA-4) event-driven API to collect information to allow Daniel Gibbs to get an idea of which game servers and distros are popular identify system requirements for game servers and know the sort of servers game server admins are using.

Is my data anonymous?

Short answer - Yes

The UUID is located inlgsm/data/uuid.txt,if this file is deleted a new UUID will be generated.

Since LinuxGSM is open-source you can also see how the data is gathered by looking at the info_stats.sh file.

How frequently is the data sent?

Data is sent every time the monitor runs as this is the only way to regularly send data.

How can I enable this feature?

To enable LinuxGSM Stats simply add the stats="on" setting to the common.cfg file. This can also be enabled on install.

Depending upon the game server you are running it is possible to run multiple game servers on the same server host.

There are two recommended ways to run multiple game servers on one physical server. Depending upon the circumstances you may choose a particular method or mixture of both.

It is best to make a proper plan for running multiple game servers at the earliest stage of your deployment. Make sure that you examine this page carefully and understand all of its content before starting.

Prerequisites

Vocabulary

You need some definitions to make this guide clear.

• Installation: An installation refers to the base directory of a game server. This is where the files required to run a game server is stored.

• Instance: Each individual game server is referred to as an instance. There might be multiple instances running per installation. An instance is started by running the ./gameserver script

• User: Each game server installation should run using its own Linux user. Although it is possible to have multiple installations per user.

LinuxGSM Configuration

Understand ports

Single Instance per Installation

Single instance per installation is the most simple method and will fit most use cases. It keeps the server files and configs completely separate from each other.

This consists of creating a new user for each game server, repeating the install process, and edit your config files ensuring default ports are changed.

Use cases

• Running different game servers requires installation in a different directory

• Running multiple servers of the same game, but they have different content, addons or mods.

• You want your game servers to be totally separate for simplicity and reduce the chance of multiple instances breaking all at once.

Pros

• Easy to setup

• Separate installations partition the game servers from each other

• Each instance can have different maps, addons and mods rather than sharing, preventing conflicts.

• More secure, by keeping instances separate with there own user.

• Reduced risk of breaking multiple instances.

Cons

• Requires more disk space as server files can not be shared

• Each instance has to be individually setup.

Examples

The installs are separated and isolated from each other in each users home directory.

How to Install

1. Create a new user with a home directory.

2. Repeat the standard installation process using this new user.

3. Change the instance config adjusting ports numbers from the default

Single Installation with Multiple Instances

Single installation with multiple instances is the method used when base installation content, maps, addons and mods are the same. Allowing either a clone of an existing instance or using different slightly different config such as different game modes and map rotations.

This consists of creating a new LinuxGSM executable file ./gameserver-2 in the same installation as an existing instance.

Use cases

• Running cloning an existing game server by creating a new instance.

• Running the same game server with different game modes, maps etc.

• Running multiple instances even with limited disk space available.

Pros

• Uses less disk space as base installation is the same

• Less configuration required

• It is possible to use different game modes and map rotations by editing configs.

Cons

• Each instance shares the same files which may limit options to customise an instance

• Potential mod conflicts

• Should one instance break all instances might also experience the same issue

How it works

You have one game server installation, but you have multiple instances start in the same installation using different config files.

Every time a new instance is created, new default config files are created. This allows each instance to have different hostname, ports etc. The config files are by default the same name as the instance script. For example, if the script is ./gameserver-2 the config is gameserver-2.cfg. You can see the location of config files in ./gameserver-2 details (replace "instance" with your actual instance name).

Each instance is managed using its own script which gives the config file names. These can be renamed how you like, however, the default will simply have an incremental number. Some admins may choose to name them after the server port, the map or the gamemode instead.

Examples

In these examples, you can see the scripts are located in the same installation but have different names. Each instance has had its port altered in the server config to prevent port clashes.

How to install

linuxgsm.sh allows you to generate as many instances as you want by running .

It will generate a new LinuxGSM script using an incremental number.

On the first run of ./gameserver-2 a new default LinuxGSM and game config gameserver-2.cfgwill be created . These new configs will need to be altered with new ports, hostname and any other settings that are required.

Common Mistakes

Forgetting to change ports and/or IP

Installing game servers with the same script name under the same user

Installing multiple installations using the same user does work. However you must use unique script names i.e. ./gameserver. This is because tmux requires unique session name to start a session. Tmux will fail to start if another server is using the same session name. LinuxGSM uses the script name as the tmux session name.

Replace ./gameserver with the actual script name. Every command has a short version, also listed here.

Global commands list

Specific commands

Teamspeak 3

Unreal & Unreal 2 Engine Games

Rust

Developer & Debug commands

monitor checks the game server to ensure the server functioning. First checking the game server process is running then querying the game server to check the game server is responding. monitor is designed to be an automated command that frequently checks the game server, rebooting and alerting if required.

Commands

Standard: ./gameserver monitor

Short: ./gameserver m

How does monitor work?

During server start, map change, workshop downloads, the server is unable to answer queries.The monitor will wait for 60 seconds as it is common for servers to stop responding to queries during a map change. This wait prevents monitor from rebooting a server that does not require it.

Automated Monitoring

As a reminder, you can edit your cronjobs, typing :

Monitor Cronjob

Use these cron examples to setup automated monitoring.

• A user based cronjob to monitor your server every 5 minutes .

• A root user based cronjob to monitor your server every 5 minutes .

Alert Notifications

Query Delay

Game Servers do not respond to queries while the server is booting. Query delay prevents monitor from giving a false positive should it query while the server is booting. A timed delay prevents monitor from using query at all during a set time (normally either 1 or 5 minutes) after start, giving the server time to boot and become ready to accept queries. Query delay timer can be adjusted using the querydelay setting.

Monitor Activation

Starting and stopping the game server activates and deactivates monitor. This prevents the server being manually stopped only to be started again by monitor.

LinuxGSM provides an easy way to start, stop and restart your game server. LinuxGSM knows the location of the server binaries and inserts the start parameters to allow the server to start. LinuxGSM will also run various checks to prevent issues and apply any required server fixes to get the game server running.

Commands

Starting a server

./gameserver start

Stopping a server

./gameserver stop

Stop only if empty (optional)

If stoponlyifnoplayers setting is enabled LinuxGSM will only stop the server if it is empty and prevent it from stopping otherwise. This feature only works with game servers that can use gamedig.

Restarting a server

Will simply stop, and then start the server.

./gameserver restart

Commands

Standard: ./gameserver check-update

Short: ./gameserver cu

Automatic check for update

Scheduled check for updates

To edit cronjobs, type:

crontab -e

A cronjob can be run as the gameserver user or as root, this choice is down to personal preference. Remember to amend the examples to match a specific game server.

Here is an example of a user-based cronjob to check for an update once an hour.

0 * * * * /home/username/gameserver check-update > /dev/null 2>&1

Here is an example of a root-based cronjob to check for an update once an hour.

0 * * * * su - username -c '/home/username/gameserver update' > /dev/null 2>&1

The validate command will check the server files to make sure they match the SteamCMD repository. This command is useful if game server files are deleted, corrupted or SteamCMD is failing to update.

Validation will overwrite any files that have been changed. This may cause issues with customised servers. For example, if you customise mapcycle.txt, this file will be overwritten to the server default. Any files that are not part of the default installation will not be affected. It is recommended you use this command only on initial installation and if there are server issues.

Commands

Standard: ./gameserver validate

Short: ./gameserver v

Commands

Standard: ./gameserver update

Short: ./gameserver u

Update will check for any available update, taking no action if no update is available. If there is an update it will apply the update, restarting the server if already running.

Automatic update

Update on start

It is possible to update a game server on start, by editing the LinuxGSM config.

updateonstart="on"

This will take longer for the game server to start but can be useful for servers that are kept offline most of the time.

Scheduled updates

To edit cronjobs, type:

crontab -e

A cronjob can be run as the gameserver user or as root, this choice is down to personal preference. Remember to amend the examples to match a specific game server.

Here is an example of a user based cronjob to check for an update once an hour.

0 * * * * /home/username/gameserver update > /dev/null 2>&1

Here is an example of a root based cronjob to check for an update once an hour.

0 * * * * su - username -c '/home/username/gameserver update' > /dev/null 2>&1

It is recommended to check for updates once per hour.

LinuxGSM allows for the simple installation of game servers. The installer is designed to get a game server to a working state allowing the game server to be started right away.

The installer will:

• Create required directories

• Install/advise on required dependencies

• Download the game server files

• Load config files

• Apply any fixes required to get the game server working

Commands

Standard Install

The standard installation is the default installation method that requires user interaction.

Standard: ./gameserver install

Short: ./gameserver i

Auto Install

Auto install is useful for automatic server deployments as no user prompt is required.

Standard: ./gameserver auto-install

Short: ./gameserver ai

Installation

1. Make your script executable:

chmod +x gameserver

1. Run the install command: ./gameserver install or ./gameserver auto-install to bypass any prompts.

2. Follow on-screen instructions.

Install Dependencies

Installation of dependencies requires either sudo or root access. LinuxGSM can automatically install dependencies if the user has sudo or is root.

Dependencies as root

As root run ./gameserver install and the installer will complete a dependency installation only, ignoring the other installation steps.

Dependencies as sudo user

If a user has sudo access the installer will prompt to enter the sudo password to automatically install dependencies. If sudo is not available the installer will advise on the command required to install dependencies.

Common Installation Issues

User Permission Issues

Common faults include:

• Trying to install the LinuxGSM as root.

• Trying to install LinuxGSM in a directory not owned by the correct user.

• Not making gameserver file executable using the chmod +x command.

To check if the correct user owns the directory or gameserver file, use ls -al

Example output

If some files/directories are not owned by the correct user, use the chown command. Login as root and use the following command, changing the details to match your server

chown -R username:username /home/gameserver

chown -R csgoserver:csgoserver /home/csgoserver

Poor Network Connection to Steam servers

If the connection to the Steam servers is poor (quite common), the SteamCMD download can fail. This is why LinuxGSM will always ask you if the installation was successful allowing admins to retry the download should it fail.

./gameserver validate

If downloading is still failing it may be worth contacting your server provider to confirm Steam servers are not being blocked for any reason.

It is also worth searching the internet for issues relating to the error message you receive.

Not Enough Storage

Some game servers take up a significant amount of disk space. If you are having issues downloading check that your server has enough space available.

To check your available storage, use:

df -h or ./gameserver details

DNS Issue

Make sure you can ping using a hostname.

The details command allows access to various useful information about the game server. Details are gathered from configs, parameters and server queries.

Commands

details

Standard: ./gameserver details

Short: ./gameserver dt

postdetails

postdetails (using hastebin) is used to share server details, to help with support, while hiding sensitive information:

Standard: ./gameserver postdetails

Short: ./gameserver pd

Details Provided

Various relevant details are provided including:

• Distro Details

• Performance

• Disk usage

• Server Name

• Server IP

• Server Ports

• Passwords

• Config File

• Backups

• Server parameters

Example output

Distro Details
===============================================================================================================================================================
Distro:    Debian 7.7
Arch:      x86_64
Kernel:    2.6.32-042stab102.9
Hostname:  vps86887.ovh.net
tmux:      tmux 1.6
GLIBC:     2.13

Performance
===============================================================================================================================================================
Uptime:    0d, 17h, 36m
Avg Load:  0.00, 0.02, 0.00

Mem:       total   used   free
Physical:  1.0G    1.0G   17M
Swap:      128M    25M    102M

Disk Usage
===============================================================================================================================================================
Disk available:  5.4G
Serverfiles:     1.6G
Backups:         4.8M

Fistful of Frags Server Details
===============================================================================================================================================================
Server name:  Fistful of Frags Server
Server IP:    192.168.1.1:27015
RCON password:  rconpassword
Status:       OFFLINE

Service name:  fof-server
User:          fofserver
Location:      /home/fofserver
Config file:   /home/fofserver/serverfiles/fof/cfg/fof-server.cfg

Backups
===============================================================================================================================================================
No. of backups:    1
Latest backup:
    date:          Fri Jan 23 15:54:52 CET 2015
    file:          /home/fofserver/backups/fof-server-2015-01-23-155447.tar.gz
    size:          4.8M

Command-line Parameters
===============================================================================================================================================================
./srcds_run -game fof -strictportbind -ip 192.168.1.1 -port 27015 +clientport 27005 +tv_port 27020 +map fof_depot +servercfgfile fof-server.cfg -maxplayers 16

Ports
===============================================================================================================================================================
Change ports by editing the command-line
parameters in ./fofserver.

Useful port diagnostic command:
netstat -atunp | grep srcds_linux

DESCRIPTION  DIRECTION  PORT   PROTOCOL
> Game/RCON  INBOUND    27015  tcp/udp

The map-compressor command is used to compress maps for some Unreal engine servers, allowing for faster maps downloads to clients.

Supported Servers

• Unreal Tournament 99

• Unreal Tournament 2004

• Killing Floor

• Red Orchestra

Commands

Standard: ./gameserver map-compressor

Short: ./gameserver mc

LinuxGSM supports the installation, updating, and removing of selected mods and add-ons for some games and engines. Zip add-ons are currently the only supported installations.

Commands

Install mods

./gameserver mods-install

./gameserver mi

Update mods

./gameserver mods-update

./gameserver mu

Remove mods

./gameserver mods-remove

./gameserver mr

Supported mods/add-ons

(This list was last updated on 2020-11-19)

Goldsrc Engine Games (v20.6.0+)

• Metamod

• AMX Mod X

Additional Game Specific AMX Mod X addons:

• Counter-Strike 1.6

• Day of Defeat

• Team Fortress Classic

• The Specialists

• Natural Selection

Source Engine Games

• Metamod: Source

• SourceMod

For Garry's Mod

• ACF

• ACF Missiles

• DarkRP

• DarkRP Modification

• PAC3

• UClip

• ULib

• ULX

• UTime

Unity3D Games

Rust, Hurtworld, 7 Days To Die

• Oxide Mod

Technical Details

Install

• All available mods are defined in the mods_list.sh.

• Mods hosted on github use the latest archive link available. Others are scraped through a mods download mirrors in order to find the latest version.

• If some mods are already installed, a list of installed mods shows up. If a user tries to install a mod that is already installed, there will be a warning that any custom files will be overwritten.

• A list of available mods is displayed to the user, including the developers website.

• After the user selects a mod, the file gets downloaded and extracted to a temporary directory.

• A list of the mod files is created at lgsm/mods/modname-files.txt. This list allows the mod to be removed if required. LinuxGSM developers have whitelisted important customisable files such as mod config files that will not be removed. If there are any important files that have been missed please raise an issue.

• Files and directories then get copied to the correct destination.

• LinuxGSM updates a file containing a list of installed mods lgsm/mods/installed-mods.txt.

Update

• The list lgsm/mods/installed-mods.txt is used to identify which mods are installed. If a non-referenced mod is found, the updater will stop with an error.

• Three update types are available

  • OVERWRITE will overwrite all mod files.

  • NOUPDATE will prevent this mod from being updated. Useful for a framework that is designed to be entirely customized.

  • RETAIN keeps the whitelisted files and updating everything else.

• As there is no easy way to check for mod versions, the update process will update every single installed mod every time the command is run.

• The process is pretty similar as the installation, mod gets downloaded, extracted, files get removed. Removed files go to a temp file list, then file list list built and temp file list added to it. Finaly the mod gets copied to destination using cp -Rf.

• If an admin wants to overwrite custom files, then he can either uninstall/reinstall the mod, or just install over it.

Remove

• A list of installed mods is displayed, user has to pick one to remove.

• Any file listed in lgsm/mods/modname-files.txt gets removed.

• The file list gets removed, as well as the entry in installed-mods.txt.

Adding mod support

What mods can be added

Any as long as the archive can be found online and the installation consists of extracting an archive to the serverfiles directory.

Asking to add support for a mod

If there is a mod you wish to see supported by LinuxGSM please raise a GitHub issue with any relevant info about the mod.

Developers

If you wish to create a pull-request yourself for this, please make sure you read the "Developer" section at the bottom right of the wiki.

Usually, editing mods_list.sh should be enough to add mod support. This script contains comments helping you to understand how to use it.

Basically: Add an array variable containing mod info, then add the array to the global array.

Long explanation: The list is based on arrays, used to define all mod properties. You need to make sure that every value is filled up and in the correct order, that mod commands are unique and that multiple choices values are ended with a semicolon (;), otherwise the last value will be ignored. You might need to add an entry in fn_mod_tidy_files_list from mods_core.sh in order to remove lines from mod's file list so that they do not get wrongly removed with the mods-remove command. For further assistance on developing this contact UltimateByte who developed those functions and dgibbs that reworked it should be able to help.

The update-lgsm command updates LinuxGSM to the latest version.

It will automatically update LinuxGSM including the _default.cfg config file to make sure the game server gets the latest settings.

Commands

Standard: ./gameserver update-lgsm

Short: ./gameserver ul

The force-update command bypasses the update check and runs the SteamCMD update regardless of update availability. This will run the SteamCMD update and restart the game server.

Force update is a useful feature for admins that restart their server daily. It allows LinuxGSM to check for updates while restarting the server.

Commands

Standard: ./gameserver force-update

Short: ./gameserver fu

The backup command allows the creation of .tar.gz archives of a game server. This can be used to transfer a game server to another Linux server, to backup the game server before a risky change, to save the current state of the game server.

Commands

Standard: ./gameserver backup

Short: ./gameserver b

Example Output

mumbleserver@game:~$ ./mumbleserver b
[ INFO ] Backup mumble-server: A total of 34M will be compressed into the following backup:
/home/mumbleserver/backups/mumble-server-2016-10-28-194346.tar.gz
Warning! mumble-server will be stopped during the backup.
[  OK  ] Stopping mumble-server: Mumble Port 64738
[  OK  ] Backup mumble-server: Backup created: mumble-server-2016-10-28-194346.tar.gz is 36M size

Backup Settings

maxbackups

Set the maximum number of backups with maxbackups. If the number of backups exceeds this value, the oldest backup will be removed after a successful backup.

maxbackups="4"

maxbackupdays

Set the maximum age of a backup using maxbackupdays. Any backups older than X days will be removed after a successful backup.

maxbackupdays="30"

stoponbackup

Set if the server should be stopped for a backup using stoponbackup. If the server is running it will be stopped while the backup is running and started again once complete. This is useful to prevent any file changes during compression that could result in a corrupt or failed backup.

stoponbackup="on"

Automated Backups

cronjob example

crontab -e

0 5 * * *  /home/username/gameserver backup > /dev/null 2>&1

Backups Location

By default backups are saved in the backup directory.

├── home
├── csgoserver
    ├── ** backup **       
    ├── lgsm
    ├── log       
    ├── serverfiles

backupdir="${lgsmdir}/backup"

Checking Backups

Use ./gameserver details to view information about created backups.

Backups
===============================================================================
No. of backups:    1
Latest backup:
    date:          Fri Jan 23 15:54:52 CET 2015
    file:          /home/csgoserver/backups/csgo-server-2015-01-23-155447.tar.gz
    size:          1.6G

Disk Usage
===============================================================================
Disk available:  5.4G
Serverfiles:     1.6G
Backups:         6.2G

Alternative Backup Methods

Using the backup feature is not the only way to backup a game server. There are other methods that have more features are are more powerful than the basic LinuxGSM backup feature. Below are are few applications that can be used instead of, or with LinuxGSM backups.

rsync

Duplicity

Is an incremental backup solution that allows backups to all sorts of different locations including many different cloud storage solutions like BackBlaze B2 and Amazon S3. Once configured it can be a powerful and efficient backup solution.

duplicity-backup.sh

duplicity-backup.sh is a very useful bash wrapper to help automate duplicity.

rclone

Commands

Standard: ./gameserver debug

Short: ./gameserver d

The skeleton command created a mirror of the directory structure of a game server. This allows you to create a skeleton directory of custom files, configs, maps etc.

Commands

Standard: ./gameserver skeleton

Short: ./gameserver sk

Skeleton Directory

The skeleton directory is created in skel.

/home/gameserver/skel

Use Case

change-password resets the TeamSpeak 3 server query password. The server will reboot and a new password will be generated.

Supported Servers

• TeamSpeak 3

Commands

Standard: ./gameserver change-password

Short: ./gameserver pw

LinuxGSM cannot always provide support for specific game servers. However, there are various support forums available for specific game server support that may be useful. Below is a list of useful links support forums:

Server Resources

Telnet

7 Days to Die uses telnet to admin the server. This is enabled by default with no password however will only listen on localhost.

FastDL (Fast Download) allows the client to download custom server content (maps, materials, models, particles, sounds, fonts, images) from a web server.

It is used to offload content downloads to a web server instead of relying on source servers (SRCDS) that only allows 20KBps downloads to clients. Content on the web server can be compressed to further speed up the download process. This means that custom content downloads much faster.

Valve now use steam workshop for most custom content however FastDL is still required in some cases.

LinuxGSM FastDL automatically creates the web directories and compresses the content for you.

Supported Servers

• All Source engine servers

Commands

Standard: ./gameserver fastdl

Short: ./gameserver fd

Supported file formats

• Maps (.bsp)

• Materials (.vtf, .vmt, .png, .svg)

• Models (.vtx, .vvd, .mdl, .phy)

• Particles (.pcf)

• Sounds (.wav, .mp3, .ogg)

• Fonts (.otf, .ttf)

• Images (.png, .svg)

Requirements

• Web server on the game server (Apache/Nginx).

  or

• Access to a remote web server.

Usage

Generate Compressed files

Run the FastDL command on your main LinuxGSM script. This will create a new directory /home/gameserver/public_html/fastdl

./gameserver fastdl

Create A virtual Host (local Apache web server)

If Apache2 is being used a virtual host pointing to the newly created public_html directory can be used.

Tutorial on setup of Apache2 server with Virtual Hosts

Here is an example of setting up Apache2 using a subdomain.

This works for Apache 2.4+ and when using a domain name. If you have got a different configuration, refer to the Apache2 documentation.

Firstly make sure your subdomain redirects to your game server and that Apache2 is correctly installed and started. Create a virtual host in order to be able to host a website :

nano /etc/apache2/sites-available/yourvirtualhost.com.conf

See the example below and edit the relevent details.

<VirtualHost *:80>
        ServerAdmin adminemail@domain.com
        ServerName subdomain.domain.com
        ServerAlias subdomain.domain.com
        DocumentRoot /home/gameserver/public_html
        <Directory /home/gameserver/public_html>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All
                Require all granted
        </Directory>
        ErrorLog ${APACHE_LOG_DIR}/error.log
        # Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
        LogLevel warn
        CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Enable your website by restarting Apache2

a2ensite yourvirtualhost.com.conf
service apache2 reload

Test the domain, to make sure it is working http://subdomain.domain.com/fastdl

Edit Game Server config

nano serverfiles/gamename/cfg/game-server.cfg

Make sure you have this:

sv_downloadurl "http://subdomain.domain.com/fastdl"
sv_allowdownload 1

Re-generate FastDL

If the custom server content is updated or removed re running the fastdl command is required to ensure that the webserver is in sync with the game server.

Note for addons developers : Note that clients won't download a file that they already downloaded unless you rename it.

Bzip2 Compression

Custom server content can be compressed using bzip2 which is supported by source games, allowing clients downloads will be faster. It is a must-have if you're hosting large files, as it will save you bandwidth, and speed up downloads for clients. However, using bzip2 on many small files can slow down client loading times.

Garry's Mod Download enforcer

In order for a client to download files from a FastDL in Garry's Mod, the developer of an addon must put files from the addon into lua code resource.Addfile ( "/path/to/file.ext" ). However, some addon developers do not do this. In order for clients to download the required files, an lua file needs to be generated for it to work, which is what the lua enforcer feature does. The only downside is that clients may download files that are not required on the server.

Authentication Token

Don't Starve Together server requires an Authentication Token.

3. Enter a friendly name for your server and copy the access token and paste it into the file cluster_token.txt.

You can quickly do this by running the following command, replacing [AUTHTOKEN] with your authentication token.

Clusters and Shards

A Don't Starve Together server consists of clusters and shards.

One cluster can contain multiple shards. A shard is simply a map/level. Multiple shards are connected by cave entrances/exits found on the map. These are functioning as portals to allow players to travel between actual game servers.

Single-Shard

By default, the cluster will be single-sharded. So you only need one server but you will also only have one map.

Default start parameter setting:

Multi-Shard

There are two types of shards:

1. master shard: the shard you enter when joining the server / the shard/server you have to join (one per cluster)

2. slave shard: shard that will connect to the master (arbitrary number per cluster)

In this example, we will only use two shards, one overworld shard and one cave shard, on the same machine using the same installation. If you want to use more shards or run the shards on different machines, take a look at the guides mentioned at the bottom. First of all we need two scripts:

Server #1

dstserver-1 will be the master shard with an overworld as level.

~/.klei/DoNotStarveTogether/Cluster_1/Master/server.ini

Server #2

dstserver-2 (this will be the slave shard with a cave as level):

~/.klei/DoNotStarveTogether/Cluster_1/Caves/server.ini

If you want to Caves and Overworld to display on the same server, you also to change the cluster.ini, otherwise it will run two instances, one with the Overworld and another with the Caves:

~/.klei/DoNotStarveTogether/Cluster_1/cluster.ini

Set all installation variables BEFORE running the ./dstserver-[1,2] install commands. Feel free to change these settings but make sure that you set them to the same clusters. You also should not change them afterwards.

For clarity it is recommended recommend naming the master shard Master.

Lastly you have to start both servers. The order does not matter because the slave server will auto-retry connecting to the master server which is listening.

Guides / Documentations:

Server Resources

System Requirements

Different Maps require different system requirements.

• TheIsland: 7GB RAM

• Genesis 2: 12GB RAM

Config Files

Server Settings

Common Command-Line Parameters

Common Configuration File Settings

The following options must come under the [ServerSettings] section of GameUserSettings.ini:

The following options must come under the [SessionSettings] section of GameUserSettings.ini.

The following options must come under the [/Script/Engine.GameSession] section of GameUserSettings.ini.

The section [ModInstaller] handles each extra Steam Workshop Mods/Maps/TC IDs in the Game.ini.

Alt Saved Directory Name

The altsavedirectoryname is the location where the game save will be stored. By default, this is the current map name. However, this setting can be customised if desired.

If altsaveddirectoryname is TheIsland the save is located will be:

Official Map Names

• TheIsland

• TheCenter

• ScorchedEarth_P

• Ragnarok

• Aberration_P

• Extinction

• Valguero_P

• Genesis

• CrystalIsles

• Gen2

• LostIsland

• Fjordur

• PGARK

Mod Support

Adding Mods

Here is a simple mod to get started:

Edit GameUserSettings.ini, adding the following line under [ServerSettings]. To add multiple mods use a comma delimiter e.g ActiveMods=924619115,924619652.

Next, edit or create Game.ini and add the following section, this will enable the auto-download of mods. To add multiple mods add another ModIDS= line underneath the first.

For the example mod add the following to GameUserSettings.ini other mods may require their own configuration as per their documentation.

Start the server and the mods will be automatically downloaded by the server. To check that this has worked open the console ./arkserver console. In the console, you will see a message similar to the following.

If you join before the server or your client has fully downloaded the mod you might get a Mod Version Mismatch error. Simply, give the server more time to load the mods.

Once you have connected to the server you will be able to see that the mod has loaded by seeing the Mod Name in the game menu Esc.

The example mod can be activated by pressing F1.

Mod Collections

The Steam Workshop has a feature that allows mods to be grouped in collections. Currently, Steam workshop collection IDs won't work directly with ARK. Instead, you need to have all the individual IDs of the mods you want to use.

IP Addressing

Multihome

The -MultiHome parameter is used to bind the server to a specific interface. By default, LinxuGSM sets this to the ${ip} variable.

PublicIPForEpic

If you want players who use the Epic Store to connect to the server the -PublicIPForEpic parameter. By default, LinuxGSM will set this to the ${publicip} variable.

Multi-Instance

CrossARK (Clusters)

Cluster ID

The cluster ID is the global name of the cluster. Each instance that will be attached to the cluster must have the same cluster ID. Use -ClusterId=<CLUSTER NAME>to specify the cluster ID.

Cluster Directory

Each server instance must be able to access the cluster directory. The cluster directory is a shared location that allows survivor and other data to be shared between server instances.

By default the cluster directory is ShooterGame/Saved/clusters/<CLUSTER NAME>. Depending upon your configuration it may be required that instances need to be pointed to a specific shared directory. To do this use add the-ClusterDirOverride=<PATH> parameter with the directory location.

The shared directory can be any preferred location however each instance must be able to read and write to that directory.

Game Server Instance locations

It is possible to set up clusters between game server instances in the same installation directory, separate installation directory, or even separate physical servers as long as all instances can access the cluster directory.

Using multiple physical servers will require the use and configuration of a file-sharing or syncing software such as SAMBA, Syncthing, or rsync.

Adding Servers to Clusters

In the below example, 2 servers will be clustered together in the same instance. For CrossARK to work each instance must have the same cluster id and share the same cluster directory.

Change the command-line parameters for your server instances by editing the instance configs.

Server 1 (arkserver.cfg)

Server 2 (arkserver-2.cfg)

Once both server instances have been started check that the cluster directory has been created in ShooterGame/Saved/clusters/hsqCd8MR65VFRFdPcDjw.

Java Requirements

Minecraft: Java Edition required Java 16

Release Settings

Minecraft java edition splits up its release in two ways. Firstly a branch is either classed as a release or a snapshot. A release is a stable version of the game whereas a snapshot is still under development

With LinuxGSM you can specify a specific release/snapshot or the latest release/snapshot. By default, LinuxGSM will use the latest release.

Game Resources

Auto Refresh

Autorefresh can lag the server when certain Lua files are edited. This happens when the refreshing cascades. This can be unwanted behavior when editing the scripts of a large project on a live server.

To disable autorefresh, add -disableluarefresh to parms.

Loading Screen

Loading screens are added by defining a website with sv_loadingurl, which is in gmodserver.cfg by default. This file overrides other files.

Gamemode

Gamemode is changed by editing start parameters in the LinuxGSM config file.

Workshop

Mounting Game Content

Some Garry's Mod addons like TTT use content from other games. To do this the content will need to be "mounted".

This guide is for installing another game server with LinuxGSM and using that content, copying that game's files, and mounting the game to Garry's Mod. This guide is for CS:S but should work for any other game.

First install a Counter-Strike: Source server, if you already have a server installed this step can be skipped. If the server will be deleted after copying files.

Copy the cstrike the directory from the Counter-Strike: Source to the Gmod folder.

Ensure that the copied files are owned by the gmodserver user.

Open mount.cfg file.

Add game to mount.cfg

Restart the server. Check if the mount was successful by changing the level to a mounted map with console or rcon.

Server Information

Resources

Resources are a key part of Multi Theft Auto. A resource is essentially a directory that contains a collection of files - including essential script and content files, plus a meta file that describes how the resource should be loaded - and runs on a Multi Theft Auto dedicated server.

A resource can be seen as being partly equivalent to a program running in an operating system - it can be started and stopped, and multiple resources can run at once. Its worth remember though, that unlike programs on an operating system, there is no multi-tasking between resources. Resources generally contain content and Lua scripts for game modes, user interfaces and other tasks affecting the players that are connected to the dedicated server on which the resources are running.

Ports

• Game Port Default: 7777 UDP Handled by: LinuxServer-KFEngine.ini

• Query Port Default: 27015 UDP Handled automatically or handled by parameters. The formula for finding query port assigned automatically is 19238 + assigned game port.

• Web Admin Default: 8080 TCP Handled by: KFWeb.ini

• Steam Port Default: 20560 UDP Handled automatically. The formula for finding the steam port is 12783 + Game Port.

Resources

Server Config Information

LinuxGSM installations contain configSubDir=servername in the command line by default, which creates a folder for config files named after the server. The default directory is /home/user/serverfiles/KFGame/Config/kf2server . Use these files to change server settings.

Workshop

Workshop content is added in LinuxServer-KFEngine.ini in the OnlineSubsystemSteamworks.KFWorkshopSteamworks section

KFGame/Config/kf2server/LinuxGSM-KFEngine.ini

[OnlineSubsystemSteamworks.KFWorkshopSteamworks]
ServerSubscribedWorkshopItems=605633924
ServerSubscribedWorkshopItems=605551918
ServerSubscribedWorkshopItems=605549089
ServerSubscribedWorkshopItems=605532351

This will only work for Workshop items that the server downloads itself, that are listed in the [OnlineSubsystemSteamworks.KFWorkshopSteamworks] section as described above.

1. Make sure that the server is not running. If it is running, the Workshop setup will be overridden the next time you restart the server.

2. Find the section [IpDrv.TcpNetDriver] in the PCServerEngine.ini config file.

3. Add the line "DownloadManagers=OnlineSubsystemSteamworks.SteamWorkshopDownload" to that section. If there are other "DownloadManagers=" lines, make sure this one is the first.

4. Do not delete anything from this section, except (optionally) other DownloadManagers= lines.

Enable Server Query

To enable server query certain permissions have to be enabled or the guest server group.

• Virtual Server

• b_virtualserver_info_view

• b_virtualserver_channel_list

• b_virtualserver_client_list

• Group

• b_virtualserver_servergroup_list

• b_virtualserver_channelgroup_list

To enable these permissions first navigate to TeamSpeak3 Options and enable Advanced permissions system.

Tools > Options > Application

Navigate to server groups server permissions and select guest.

Permissions > Server Groups

Select the values shown below and close the menu.

• Virtual Server

  • Information

    • b_virtualserver_info_view

    • b_virtualserver_channel_list

    • b_virtualserver_client_list

• Group

  • Information

    • b_virtualserver_servergroup_list

    • b_virtualserver_channelgroup_list

Enable Query on LinuxGSM

Because a user has to manually enable server query with TeamSpeak 3, LinuxGSM has gamedig query disabled by default. Enabling will allow more information to be displayed in details and enable monitor to use gamedig.

Copy the query mode settings from _default.cfg to common.cfg and change querymodefrom 5 to 3.

## Query mode
# 1: session only
# 2: gamedig (gsquery fallback)
# 3: gamedig
# 4: gsquery
# 5: tcp
querymode="3"
querytype="teamspeak3"

Connect to TeamSpeak 3 Server

You can connect to a TeamSpeak 3 server to input commands without the need for a TeamSpeak 3 client. This can be done by connecting to the query port using telnet.

Using PuTTY or equivalent select a telnet connection and enter the server IP and TeamSpeak 3 query port (default:10011).

Useful Commands

Login

login serveradmin <password>

Generating a new Privilege key

use sid=<server-id>
tokenadd tokentype=0 tokenid1=6 tokenid2=0

Note: Your server ID is usually 1

Reset your query password

TeamSpeak 3 Databases

The TeamSpeak 3 database contains all user information, groups, and statistics for your server.

SQLite Database

By default, TeamSpeak 3 uses an SQLite database file, which allows good performance for most users, and easy server transfers from one server to another. This method is recommended for most admins as it is the simplest database method to use.

MariaDB

TeamSpeak 3 also allows admins to use MariaDB (MySQL alternative) manage the database. MariaDB is entirely optional and is not required so it is recommended that admins only use if they are comfortable.

TSDNS

TSDNS is a system allowing admins to redirect a domain name to a given TeamSpeak 3 port.

If TeamSpeak 3 port is using the default port, you do not need to provide the port when you are giving your server address, you can use the IP or domain name directly.

TSDNS is useful to admins that are hosting multiple TeamSpeak 3 servers on a single dedicated server.

Further documentation can be found using the following command.

cat ~user/serverfiles/tsdns/tsdns_settings.ini.sample

Then you can copy the sample, edit it accordingly and restart your TeamSpeak 3 server to apply the changes.

cd serverfiles/tsdns/
cp tsdns_settings.ini.sample tsdns_settings.ini
nano tsdns_settings.ini
cd ~
./ts3server restart

Known issues

IPv6

Some users with IPv6 enabled might encounter a server failing to start properly. To fix this edit serverfiles/ts3-server.ini to add a standard IPv4 (voice_ip; filetransfer_ip; query_ip) and remove the , :: from IPv6. Then as the server failed to start at the installation, the privilege key hasn't been generated. So you will need to use server query (ID/Password have been generated for them) to generate a new Server Admin privilege key.

Accounting failed to register

ERROR |Accounting | |failed to register local accounting service: File exists

If you find the above in the TeamSpeak 3 log you may need to remove the following file.

/dev/shm/7gbhujb54g8z9hu43jre8

Server Crashed after a while (outdated and no licence)

If the following message appears in the log of the Teamspeak 3 Linux Server Error creating ephemeral license: EXPIRED You need to upgrade the version of the TeamSpeak 3 Server to a more up-to-date version.

Server Resources

Headless Client

Headless Client Overview

• A headless Client is used to offload AI calculations from the server.

• Headless Client is integrated into the game client and dedicated server executable (Windows and Linux, use -client parameter).

• The server does not allow arbitrary connections from headless clients if you do not define the headless clients' IPs in the server.cfg.

Headless Client Setup and Usage

Starting up a headless client and having it connect to your server is easy, Creating a mission that uses the Headless Client is not.

Edit the config file lgsm/config-lgsm/arma3server-hc.cfg.

Change the port= increasing the number by a factor of 12 e.g 2303 becomes 2314.

Update startparameters= changing it to the following.

Edit the game server config of arma3server (not the headless client) arma3server.server.cfg and add the headless client IP address to headlessClients[]=. If the headless client is on the same physical server as the ARMA 3 server then also add the IP to localClient[]=.

Navigate to your profile directory.

edit Player.Arma3Profile and add the line battleyeLicense=1;.

Start your server with ./arma3server start

Start your headless client with ./arma3server-hc start.

Only an admin can see the headless clients in the player menu on the server. The headless client will connect and automatically assume the first available headless client slot.

Mod Support

Adding Mods

Here is a popular mod to get started:

Create a directory called @cba_a3 in serverfiles/mods

Copy the contents of the mod archive to the @cba_a3 directory.

Copy the contents of the @cba_a3/keys directory to the server keys directory.

If you are adding multiple mods make sure you put a semicolon with the escape character in between each mod.

Lower Case File Names

Arma 3 server requires that mods have lowercase names. Some mods do not do this and will need to have their file names converted to lowercase.

This can be done by using the following script.

Run the script from the serverfiles/mods directory.

Server Resources

Server Configuration

LinuxGSM Server Config

port, rcon and branch configuration is set using stat parameters

## Server Start Settings | https://docs.linuxgsm.com/configuration/start-parameters
ip="0.0.0.0"
port="34197"
rconport="34198"
rconpassword="Change_Me"
# (stable|experimental)
branch="stable"

Specific verison

To use a specific version of Factorio, you can change the branch to the version you want to use :

## Server Start Settings | https://docs.linuxgsm.com/configuration/start-parameters
branch="1.1.87"

One the branch changed, do not forget to update the server :