AMP Configuration Generator

Version 2.1 - Updated by IceOfWraith
©2023 CubeCoders Limited

You can find detailed instructions and explanations on the Generic Configurations Wiki.

Basic Information

This is what will show up within AMP as the name of the application.
Useful for describing different variants/configurations of the same application.
Who are you? Take some credit for your work! Please use your GitHub username.
A link to where you can learn more about the application, such as a store listing.
What AMP's "connect" button opens. Built from the Steam query port if left blank.
The container image AMP runs the application in. Chosen from the compatibility layer if left blank.
Whether the application runs on ARM64 machines such as Oracle Ampere or a Raspberry Pi.
How finished this configuration is. Anyone using your template can see this.


Management and Console

This is in addition to the applications management type if it accepts management over methods other than Standard IO
Pass the password to the application with the {{$RemoteAdminPassword}} template item in its command line arguments or a configuration file.


Networking

AMP will automatically generate firewall rules to allow the application ports through. You may add any number of ports. Maximum of 1 Main Game, Steam Query, and RCON Port. Use 'Derived' for a port that always sits a fixed distance above another one - AMP works its number out from the port it came from and keeps the whole group together when it assigns ports to an instance.
Number Type Name Ref Description Protocol Range & options
min
+
min
No ports have been added.
One port
Which of the ports above AMP uses for each job. AMP matches these on the port's Ref, and treats a ref with no port behind it as port 0 without warning anyone.
The port players connect to. AMP builds the instance's address and connect button from it.
The port AMP connects to for the console and for running commands.
Lets AMP stop the application while nobody is playing and start it again when someone tries to connect. AMP answers for the application on the ports below while it's asleep.
Usually the port the application itself takes traffic on.
Leave as None for applications that don't use the Steam query protocol.


Update Sources

The stages AMP runs, in order, when it installs or updates the application.
Stage Name Source Type Platform
No update sources added.
Pre-Start Stages
The same kind of stages, but run before every start rather than only when updating. Use them for anything that has to happen each time the application comes up.
Stage Name Source Type Platform
No pre-start stages added.


Configuration and Settings

Display Name Field Name Default Value Command Line
No settings have been added.
Configuration Files
Select the location of any game server configuration files AMP should manage. Location relative to Base Directory.
Config File Config Type AutoMap Importable
No config files have been added.


Startup and Shutdown

Application and Parameters
Don't include any arguments that come from the Configuration and Settings section above.
Any Windows specific arguments to be used in the command line args in place of {{$PlatformArgs}}.
Any Linux specific arguments to be used in the command line args in place of {{$PlatformArgs}}.
The format to be used to add settings specified above to the command line in place of {{$FormattedArgs}}. {0} is the field name and {1} the value.
The character(s) used to separate different arguments in the command line flags generated by settings. By default this is a single space.
Where should AMP place Steam Workshop mods? This is relative to the Base Directory.
A URL to an image that AMP can use to represent the application. Taken from the Steam store instead when an update stage names a client App ID - the server App ID has no store page, so it can't be used for this.
The imported template's own image () is being kept while this is blank.
For applications that launch the real server as a child process - a regular expression matching that process's command line. AMP will report its CPU and memory usage instead of the launcher's. Linux only.
Shutdown
Used in place of the method above when the instance runs on Windows.


Server Events (Beta)

AMP uses the game server's output from either the console (standard output) or RCON to know how to handle certain events:
A successful startup, Users connecting/disconnecting, or Chat messages.

The Config Generator will attempt to create regular expressions based on your input. Paste a line from the console that uniquely represents the events. Keep all static pieces of the line and replace sections that vary with the *{misc} variable. Use as many of these variables in place of corresponding sections of the lines:

Variable Description
*{username} The Username of the player
*{userid} The User ID of the player (Typically Steam64 ID or Epic ID #)
*{sessionid} Any unique number to identify a player's Session
*{message} The chat message
*{endpoint} The IP of the player
*{misc} Any section of the line that varies

Regex101 is an excellent resource to help validate expressions. AMP uses the 'ECMAScript (Javascript)' regex flavour.

Expression - built from the line above, or type one straight in if you already have it.
Expression - built from the line above, or type one straight in if you already have it.
Expression - built from the line above, or type one straight in if you already have it.
Expression - built from the line above, or type one straight in if you already have it.


Validate and Review

This is generated assuming the default values and default port numbers, these will change based on user-specified values or assignments made by AMP.

  You have not yet validated your configuration. You will not be able to download your configuration until you have done this.

  Validation Failed - You must address the following failures before you may continue.

  Validation Passed with Warnings - You should consider addressing the following warnings.

  Validation Passed - Great stuff! You may now download the completed configuration below.

Validation Issues:
Category Issue Recommentation
Impact:
No validation issues

  Make sure to keep a backup of your configuration by using the 'Export' option at the top of the page! You will need this to make further changes even after downloading the configuration and manifest.

Using the generated configuration

You can find the steps to upload the configuration to GitHub and use them within AMP on the Generic Configurations Wiki.

 

Generated Data

Values that are calculated automatically based on your input.
No Generated Value
No Generated Value