DocumentationBot: Version 1

2026-10-01T04:13:05Z

Version 1

New page

{{ANEURISMNav}}

A dedicated server runs the world without a player occupying the host computer. This guide uses a Linux x86-64 machine, Bash, and [https://developer.valvesoftware.com/wiki/SteamCMD SteamCMD]. Run the server under a normal Linux user account that owns its installation and data directories.

The examples install the <code>preview</code> branch for version <code>20-preview1</code>. Players can select <code>preview</code> in Steam under '''ANEURISM IV → Properties → Betas'''.

== Install the server ==

Install SteamCMD using Valve's instructions for your Linux distribution. Then create separate directories for the game files and saved data:

<syntaxhighlight lang="bash">
umask 077
mkdir -p "$HOME/aneurism/server" "$HOME/aneurism/data"
steamcmd +force_install_dir "$HOME/aneurism/server" \
+login anonymous +app_update 2832030 -beta preview validate +quit
</syntaxhighlight>

If Steam reports that the account has no subscription, replace <code>anonymous</code> with your Steam account name and complete the Steam Guard prompts. Leave your Steam password out of the command.

The dedicated-server download uses Steam App ID <code>2832030</code>. The installed <code>steam_appid.txt</code> must contain the game's App ID, <code>2773280</code>. These IDs have different purposes. If that file is missing or has another value, validate the installation again.

== Set the owner and startup settings ==

Create <code>~/aneurism/server.env</code>:

<syntaxhighlight lang="bash">
cat > "$HOME/aneurism/server.env" <<EOF
ANIV_COMMUNITY_OWNER_STEAM_ID=YOUR_STEAM_ID64
ANIV_SERVER_NAME='My ANEURISM server'
ANIV_MAX_PLAYERS=32
ANIV_MAP=aneurismiv
ANIV_ROTATION=persistent-world
ANIV_SERVER_PASSWORD=''
ANIV_DATA_ROOT='$HOME/aneurism/data'
EOF
chmod 600 "$HOME/aneurism/server.env"
</syntaxhighlight>

Open the file in a text editor and replace <code>YOUR_STEAM_ID64</code> with your personal 17-digit SteamID64. Use your account's numeric ID, not a profile nickname or a server's Steam ID. You can find your Steam ID in [https://store.steampowered.com/account/ Steam account details].

The owner is recorded when the database is first created. Keep the same owner setting on later starts. Changing the environment variable doesn't transfer ownership.

Set <code>ANIV_MAP</code> explicitly. <code>aneurismiv</code> selects ANEURISM IV; <code>misery</code> selects Misery. The [[ANEURISM IV/Server configuration|configuration guide]] explains the remaining settings.

== Start and join ==

Load the environment file and start the server in the foreground:

<syntaxhighlight lang="bash">
set -a
. "$HOME/aneurism/server.env"
set +a
cd "$HOME/aneurism/server"
./aniv_server.x86_64 -batchmode -nographics -logFile -
</syntaxhighlight>

The log appears in the terminal. Steam login and relay allocation can take up to three minutes. Wait for the map to load, then open ANEURISM IV on your gaming computer, refresh '''Community''', and join your server.

A running process alone doesn't confirm that the server is ready. If it never appears or exits during startup, check the log and the [[ANEURISM IV/Troubleshooting|troubleshooting guide]].

== Keep it running with systemd ==

After the foreground launch works, press Ctrl+C and wait for the process to exit before starting a service. The following user service uses the same files and sends logs to the system journal.

Create the directory:

<syntaxhighlight lang="bash">
mkdir -p "$HOME/.config/systemd/user"
</syntaxhighlight>

Save this as <code>~/.config/systemd/user/aniv.service</code>:

<syntaxhighlight lang="ini">
[Unit]
Description=ANEURISM IV community server
StartLimitIntervalSec=300
StartLimitBurst=3

[Service]
Type=simple
WorkingDirectory=%h/aneurism/server
EnvironmentFile=%h/aneurism/server.env
ExecStart=%h/aneurism/server/aniv_server.x86_64 -batchmode -nographics -logFile -
Restart=on-failure
RestartSec=15
TimeoutStopSec=120
SendSIGKILL=no
UMask=0077

[Install]
WantedBy=default.target
</syntaxhighlight>

Start it with:

<syntaxhighlight lang="bash">
systemctl --user daemon-reload
systemctl --user enable --now aniv.service
systemctl --user status aniv.service
journalctl --user -u aniv.service -n 100 --no-pager
</syntaxhighlight>

To keep the user service running after logout and start it at boot, have a machine administrator enable lingering for your Linux account:

<syntaxhighlight lang="bash">
sudo loginctl enable-linger "$USER"
</syntaxhighlight>

Use these commands for routine operation:

<syntaxhighlight lang="bash">
systemctl --user stop aniv.service
systemctl --user start aniv.service
systemctl --user restart aniv.service
journalctl --user -u aniv.service -f
</syntaxhighlight>

The service waits for shutdown without forcing a kill. If stopping times out, inspect the process and log before updating files or making a backup. A manual stop keeps the server stopped even though crash recovery is enabled.

== Network access ==

Allow the server to reach Steam and HTTPS services. Community gameplay uses Steam Relay; leave unsolicited inbound traffic blocked. You don't need to forward UDP <code>7777</code>, <code>27015</code>, or <code>27016</code>.

Steam uses local UDP ports <code>27015</code> and <code>27016</code>. They must be free for this process. For multiple servers on one machine, give each instance a separate network namespace or virtual machine, as well as its own data directory. Changing a gameplay port doesn't change these Steam service ports.

Community administration happens through the connected game client.

== Optional persistent Steam identity ==

Anonymous Steam login works for normal hosting. Its server identity can change after a restart. To use a persistent identity, create a game server login token at [https://steamcommunity.com/dev/managegameservers Steam Game Server Account Management] for App ID <code>2773280</code>. Use a separate token for each server that runs at the same time.

The executable accepts <code>-gslt</code>. For a foreground launch, load <code>server.env</code> as above, then enter the token at a hidden prompt:

<syntaxhighlight lang="bash">
cd "$HOME/aneurism/server"
read -r -s -p 'Steam game server login token: ' ANIV_GSLT
printf '\n'
./aniv_server.x86_64 -batchmode -nographics -logFile - -gslt "$ANIV_GSLT"
unset ANIV_GSLT
</syntaxhighlight>

This keeps the token out of shell history, but the running process's arguments can still expose it to users with sufficient machine access. Keep tokens out of shared logs, screenshots, and configuration examples. The systemd example above uses anonymous login.

A rejected or malformed token stops startup. The server won't retry that launch anonymously. The login token controls the server's Steam identity; your personal <code>ANIV_COMMUNITY_OWNER_STEAM_ID</code> still controls ownership.

[[Category:ANEURISM IV]]

ANEURISM IV/Dedicated servers - Revision history

DocumentationBot: Version 1