Skip to main content

Create GSA + STEAM blueprint

Learn how to create a blueprint for STEAM games.

In this guide, we'll walk you through creating a blueprint for Myth of Empires. While this example focuses on setting up a Windows blueprint, the same principles apply to Linux.

Intro​

For this guide, we assume you've already created a blueprint and are now on the Add version page.

Use the GSA + Steam Template

We used the GSA + Steam (Windows only) blueprint template for this guide. Using a template is recommended as it ensures most fields are pre-filled.

Blueprint - Create a blueprint - Add blueprint modal

1. Enter STEAM ID & Executable​

Steam Client & Server ID​

Enter the STEAM Client & Server ID for the game server in the appropriate fields (Learn how to find STEAM IDs).

For this example, we used:

  • Client ID: 1371580
  • Server ID: 1794810

Blueprint - Create STEAM blueprint - Find server id

Executable Path​

Enter the executable path in the Executable field and click save (Learn how to find the executable path).

For this example, we used:
C:\Users\ContainerUser\serverfiles\MOE/Binaries/Win64/MOEServer.exe

Blueprint - Create STEAM blueprint - Find executable path

2. Launch a Fresh Server with the Blueprint​

2.1 Create a New Server​

Go to the Install new game server page and start a new game server using the blueprint we just created.

Blueprint - Create STEAM blueprint - Launch new game server

Click Install game server now and wait for the installation process to finish.

caution

Before moving to the next step, please give the game server 2 to 5 minutes to boot up and initialize.

2.2 Test if It Starts​

Now, let's test whether the game server shows any signs of activity. This will help confirm that the IDs and executable path are correct.

Check Memory Usage​

If the memory usage indicator hovers above 0.5GB, it's a good sign that the game server is launching properly.

Blueprint - Create STEAM blueprint - Check server memory

Check Docker Container Logs​

If logs start appearing in the Docker container logs, it’s usually a good sign that the game server is launching. However, logs may also indicate issues preventing the server from starting.

In our example (image below), you'll see multiple lines with the text MOE (from our executable path).
The logs might show errors, but in this case, they confirm that the game server is starting up.

Blueprint - Create STEAM blueprint - Check server logs

4. Configure Settings​

Now that we've confirmed the game server is booting up, it's important to configure the remaining settings. These settings will likely vary depending on the game.

In most cases, this involves adding Launch parameters and/or Config files with the correct values for your game server.

The easiest way to determine what your game needs is to use your favorite search engine or search the game's wiki page.

4.1 Launch Parameters​

The preferred method is to use launch parameters for settings like game ports, slot limits, server name, cluster ID, etc. If your game server supports launch parameters, we recommend using them.

For Myth of Empires, we referred to IceWarden's guide, which explains the launch parameters you can use. We selected the following parameters and replaced some values (ports, server name, IDs, etc.) with variables:

LargeTerrain_Central_Main -game -server -DataLocalFile -NotCheckServerSteamAuth -PrivateServer -MultiHome=0.0.0.0 -OutAddress={machine.ip}
-SessionName={gameserver.list_name} -MaxPlayers={gameserver.slot_limit} -ClusterId={cluster.id} -Port={gameserver.game_port} -QueryPort={gameserver.query_port}
Use Variables

Since GSA automatically assigns ports for each game server, it's crucial to use variables. This prevents your game server from attempting to launch with hardcoded ports when GSA has assigned different ones.

Add New Blueprint Version
Create a new version for your blueprint, enter the launch parameters in the Launch parameters field, and save the form.

Blueprint - Create STEAM blueprint - Edit launch params

4.2 Config Files​

Learn how to find and register config files for most games, using FTP >

Test & Repeat
You can now activate the new version on the game server and restart the game server.
Give it some time (2 - 10 minutes) to boot up. Afterward, check if it came up and try joining the game server.

5. Hooray!​

If you're lucky, like us, the game server will show up, and you'll be able to join.

Finalize Blueprint Settings

Learn how to configure settings like uptime monitoring, RCON, backups, and more in the blueprint form section >.

Blueprint - Create STEAM blueprint - working server

Help​

Finding Executable Path​

Search SteamDB for the dedicated server files and click on the Dedicated server. Then go to the Configuration page, and look for Executable.

caution

It's important to ensure that the executable path is for the correct operating system, either Linux or Windows. In our case, since only Windows is supported, there should only be one executable path.

Blueprint - Create STEAM blueprint - Find executable path

In the example above, you see that MOE/Binaries/Win64/MOEServer.exe is the executable path.

Fix Paths

The executable path from SteamDB won't work out of the box.
You need to add the correct container path, as explained below:

Windows​

For Windows, prepend the following path: C:\Users\ContainerUser\serverfiles\
Combined, it should look like this:
C:\Users\ContainerUser\serverfiles\MOE/Binaries/Win64/MOEServer.exe

Linux​

For Linux, prepend the following path: /home/containeruser/serverfiles/
Combined, it should look like this:
/home/containeruser/serverfiles/MOE/Binaries/Win64/MOEServer.exe

In this article