ARK: Survival Evolved
Last updated
Last updated
Different Maps require different system requirements.
TheIsland: 7GB RAM
Genesis 2: 12GB RAM
An example of GameUserSettings.ini can be found here.
Command line parameters take precedence over configuration files.
Below is a list of common Command-Line parameters. For a complete list see the Ark Wiki.
SessionName
-MultiHome
Enables multihoming.
-Port
-QueryPort
-AutoManagedMods
Steam only, automatic MOD download/installation/updating. Mod IDs are listed in Game.ini under [ModInstaller] section.
-CrossPlay
Enables crossplay (i.e.: EPIC and Steam) on dedicated server. Note: PublicIPForEpic must also be set.
-PublicIPForEpic=<IPAddress>
This is the public IP that EGS clients will attempt to connect to, if this option is missing and -MULTIHOME is specified, then EGS clients will attempt to connect to the multihome IP; note that if you're using multihome and specify a non-public IP address, then players will not be able to connect to your server using EGS. Make sure to set a public IP address (e.g.: WAN or external).
-NoBattlEye
Run server without BattleEye.
-ActiveEvent=
Enables a specified event or enables the event's colour palette on wild creatures. Only one can be specified and active at a time.
?AltSaveDirectoryName=<savedir_name>
-insecure
Disable Valve Anti-Cheat (VAC) system.
-MapModID=
?GameModIds=[,[...]]
Steam only. Specifies the order and which mods are loaded, ModIDs need to be separated with commas (,). Mod priority is in descending order left to right (the left-most ID is the top priority mod). It is suggested to use instead the ActiveMods under [ServerSettings] of GameUserSettings.ini.
Below is a list of common Configuration settings. For a complete list see the Ark Wiki.
The following options must come under the [ServerSettings] section of GameUserSettings.ini:
ActiveMods=ModID1,ModID2,ModID3
Value type: list of mod IDs, comma-separated with no spaces, in a single line (for example: ModID1,ModID2,ModID3)
BanListURL="http://arkdedicated.com/banlist.txt"
Value type: string with a URL Sets the global ban list. Must be enclosed in double-quotes.
RCONEnabled=True
f True, enables RCON, needs RCONPort=<TCP_PORT> and ServerAdminPassword=<admin_password> to work
RCONPort=27020
Specifies the optional TCP RCON Port.
ServerAdminPassword=
If specified, players must provide this password (via the in-game console) to gain access to administrator commands on the server.
ServerPassword=
If specified, players must provide this password to join the server.
serverPVE=
The following options must come under the [SessionSettings] section of GameUserSettings.ini.
SessionName
Specifies the Server name advertised in the Game Server Browser as well in Steam Server browser. If no name is provide, the default name will be ARK # followed by a random 6 digit number
The following options must come under the [/Script/Engine.GameSession] section of GameUserSettings.ini.
MaxPlayers=70
Specifies the maximum number of players that can play on the server simultaneously.
The section [ModInstaller] handles each extra Steam Workshop Mods/Maps/TC IDs in the Game.ini.
ModIDS=<integer>
Specifies a single Steam Workshop Mods/Maps/TC ID to download/install/update on the server. To handle multiple IDs, multiple lines must be added with the same syntax, each one with the specific workshop ID. Requires -automanagedmods in the command line.
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.
Be careful not to accidentally overwrite a save file if changing maps or using a custom save location.
If altsaveddirectoryname is TheIsland the save is located will be:
TheIsland
TheCenter
ScorchedEarth_P
Ragnarok
Aberration_P
Extinction
Valguero_P
Genesis
CrystalIsles
Gen2
LostIsland
Fjordur
PGARK
ARK server mods are managed using the Steam Workshop, this allows the auto-install and update of mods.
Firstly, you need to select the mods you want to use from the Steam Workshop.
Mods can cause your server to become unstable or may not be compatible with each other. It is a good idea to read the mods docs and/or speak with other experienced ARK admins.
Here is a simple mod to get started:
-AutoManagedMods is the required parameter to add workshop support and is added to the start parameters by default.
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.
For more config options for WBUI see this link.
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.
Large mods may take several minutes to download to the server.
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.
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.
To get individual item IDs from collections you can use the Steam Collection ID Grabber.
The -MultiHome parameter is used to bind the server to a specific interface. By default, LinxuGSM sets this to the ${ip} variable.
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.
ARK can work with LinuxGSM multi instances in the same install. However, each instance will use the same GameUserSettings.ini. To customise each server use command-line parameters as they take precedence over the configs.
A CrossARK cluster allows players to transfer a survivor, items, and tames ("objects") from one ARK to another ARK. A server admin can group all their ARK servers together in a cluster. Typically a server admin will cluster servers with different maps. There are a few different ways to configure CrossARK depending upon your configuration.
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.
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.
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.
Firstly, set up multiple ARK game server instances.
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.
If you have multiple separate installations of ARK use -ClusterDirOverride to point each installation to the same cluster directory.
Change the command-line parameters for your server instances by editing the instance configs.
Once both server instances have been started check that the cluster directory has been created in ShooterGame/Saved/clusters/hsqCd8MR65VFRFdPcDjw.
This may require you to connect to an instance first
Servers that are running on local networks sometimes have trouble traveling to other arks. A potential fix for this is adding MultiHome=0.0.0.0 to your command-line parameters.
Allows to specify a custom directory name for server world-save. Usually used to manage clusters, read more about it in the section.
Dedicated servers can now optionally load custom maps via ModID directly, rather than having to specify the map name, using this syntax (where the MapModID is the Steam Workshop ID of your custom map, and the GameModIds are the Id’s of the stacked mods you wish to use, in order). ActiveMods must also be set in .
If True, disables and enables
