Game Configuration: Overview
This is the first part of the Game Configuration series — a deep dive into how game templates work in GameCP. Whether you're customizing an imported template or building a game config from scratch, this series covers every section of the editor.
What is a Game Configuration?
A game configuration (or "game config") is the blueprint that tells GameCP how to install, run, and manage a specific game. It defines everything from the Docker image and startup command to environment variables, port mappings, and monitoring settings.
When you create a game server, GameCP uses the game config as the template. The server inherits all the defaults from the config, and users can override specific values (like server name or player count) per-server.
Where to Find It
Navigate to Games in the sidebar. You'll see your game library — each card represents a game config. Click on any game to open its configuration editor.
The Editor Layout
The game config editor opens as a full-screen modal with a sidebar navigation on the left. Each section of the sidebar focuses on a specific area of the configuration:
| Section | What It Controls |
|---|---|
| Basic Information | Game name, description, category, and images |
| Execution Configuration | Startup command, working directory, and runtime mode |
| Command Lines | Startup script groups and arguments |
| Docker Configuration | Container image, volumes, and resource limits |
| Port Configuration | Network port mappings and port variables |
| Status Monitoring | Query protocol, RCON, and health checks |
| Environment Variables | Game-specific settings users can configure |
| Console Triggers | Automated reactions to console output patterns |
| Configuration Files | Editable config file templates (like server.properties) |
| Scripts | Custom lifecycle scripts for install, start, stop, etc. |
| Steam Installer | SteamCMD integration for automatic game downloads |
| Backup & Files | Backup settings and file access restrictions |
| Resource Provisioning | CPU, memory, storage, and network profiles |
| Mods & Versions | Mod manager, CurseForge, and jar management |
| Advanced Settings | Additional options and feature flags |
Each section is covered in detail in its own tutorial in this series.
Templates vs Custom Configs
There are two ways to set up a game config:
Importing a Template
GameCP provides a library of pre-built templates that you can import from the Template Store. Templates come pre-configured with sensible defaults — the Docker image, startup command, ports, environment variables, and query settings are already set up.
To import a template:
- Go to Games in the sidebar
- Click the Import button
- Browse the template store or search by name
- Click Import on the template you want
After importing, the game appears in your library ready to use. You can customize any setting by opening the editor.
Building from Scratch
If you're hosting a game that doesn't have a template, or you want full control, you can create a config from scratch:
- Go to Games in the sidebar
- Click Add New
- Fill out each section of the editor
At minimum, you need to set the name, Docker image, startup command, and port mappings. Everything else is optional but recommended for the best experience.
Exporting and Sharing
You can export any game config as a JSON file using the Download button in the editor header. This file can be:
- Shared with other GameCP users
- Submitted to the template store
- Used as a backup before making changes
- Imported on another GameCP instance
What's Next
The next parts of this series dive into each section:
- Part 2: Basic Information — naming, categorizing, and branding your game
- Part 3: Execution & Docker — how GameCP runs your game server
- Part 4: Environment Variables — the settings your users interact with
- Part 5: Ports & Networking — how ports are mapped and assigned
- Part 6: Status Monitoring — query protocols and RCON
- Part 7: Scripts & Lifecycle — custom commands for install, start, stop
- Part 8: Configuration Files — templated config files users can edit
- Part 9: Console Triggers — automated reactions to server output
- Part 10: Steam Installer — SteamCMD integration
- Part 11: Command Lines — startup script groups and custom arguments
- Part 12: Advanced — backups, resources, mods, and additional options
Start with the overview, then jump to whichever section is relevant to your game.