This guide covers how to set up and configure your Risk of Rain 2 dedicated server hosted with Legion Hosting, including GPanel startup variables, server.cfg configuration, connecting to your server, mod support, and save management.
First Start
When you start your Risk of Rain 2 server for the first time, GPanel will automatically download and install the dedicated server files via SteamCMD (Steam App ID 1180760). This process may take a few minutes depending on network speed.
- Log in to GPanel and select your Risk of Rain 2 server.
- Click the Start button on the Console tab.
- Wait for the installation to complete. The console will display download progress as SteamCMD fetches the server files.
- Once the server is fully started, you will see a message indicating the server is ready and listening for connections.
xvfb virtual display is also configured automatically to satisfy the server's display requirements.
GPanel Startup Variables
Key server settings are configured as startup variables in GPanel. These are passed to the server process as arguments and take effect each time the server starts.
- Log in to GPanel.
- Select your Risk of Rain 2 server from the server list.
- Click the Startup tab.
- Review and adjust the variables below, then restart your server for changes to take effect.
| Variable | Default | Description |
|---|---|---|
HOSTNAME |
Risk of Rain 2 Dedicated Server |
The name displayed in the in-game server browser. Set something recognizable so players can find your server. |
PLAYERS |
4 |
Maximum number of players allowed in the lobby. Risk of Rain 2 supports up to 16 players with mods, but the vanilla game is designed for up to 4. Higher player counts increase resource usage. |
PASSWORD |
(empty) | Optional password players must enter to join. Leave blank for a public server. Passwords are case-sensitive. |
ADVERTISE |
1 |
Controls whether the server appears in the in-game server browser. Set to 1 to list the server publicly, or 0 to hide it (players must use direct connect). |
server.cfg Configuration
For settings not available in the Startup tab, you can edit the server configuration file directly. The file is located at:
Risk of Rain 2_Data/Config/server.cfg
Open this file using the GPanel Files tab or connect via SFTP. The file uses a simple key-value format. Below are commonly adjusted settings:
| Setting | Example Value | Description |
|---|---|---|
sv_hostname |
My RoR2 Server |
Server name. This is typically set via the HOSTNAME startup variable, but can also be defined here. |
sv_maxplayers |
4 |
Maximum players. Can also be set via the PLAYERS startup variable. |
sv_password |
mypassword |
Server password. Can also be set via the PASSWORD startup variable. |
heart_beat |
1 |
Whether the server sends heartbeat packets to the master server for browser listing. Equivalent to the ADVERTISE startup variable. |
steam_authentication |
1 |
Enables Steam authentication for connecting players. Keep this at 1 unless you have a specific reason to disable it. |
server.cfg, the startup variable will override the config file value. Use the Startup tab for core settings and server.cfg for additional tuning.
How to Connect
Option A — In-Game Server Browser
If your server has ADVERTISE set to 1, it will appear in the in-game server browser:
- Launch Risk of Rain 2.
- From the main menu, select Multiplayer.
- Click Find a Game to open the server browser.
- Search for your server by name (the
HOSTNAMEyou configured). - Select the server and click Join. Enter the password if prompted.
Option B — Direct Connect via Console
You can connect directly using the in-game console, which is useful for password-protected or unlisted servers:
- Launch Risk of Rain 2.
- Open the in-game console by pressing Ctrl + Alt + ` (backtick). If the console does not open, you may need to enable it by launching the game with the
--doorstep-enableflag or by installing BepInEx (see Mod Support below). - Type the following command and press Enter:
Replaceconnect "IP:PORT"IPandPORTwith your server's IP address and game port as shown in the GPanel Network tab. - If the server has a password, you will be prompted to enter it.
For details on finding your server's IP and port, see How to Find Your Server IP and Port.
Mod Support
Risk of Rain 2 has an active modding community centered around Thunderstore, a mod repository and manager. Most server-side mods require the BepInEx modding framework.
Installing BepInEx
BepInEx is the standard mod loader for Risk of Rain 2. To install it on your server:
- Download the latest BepInExPack from Thunderstore.
- Stop your server from the GPanel Console tab.
- Connect to your server via SFTP (see How to Upload Files via SFTP).
- Extract the BepInExPack archive and upload the contents to your server's root directory, merging with existing files. The key files are the
BepInEx/folder and related configuration files. - Start your server. BepInEx will initialize on the first boot and create its plugin and configuration directories.
Installing Server-Side Mods
Once BepInEx is installed, you can add server-side mods:
- Browse Thunderstore for mods. Look for mods tagged as server-side or host-required.
- Download the mod and extract it.
- Upload the mod's DLL files to the
BepInEx/plugins/directory on your server via SFTP. - Restart the server to load the new mods.
Using r2modman (Client-Side)
For managing mods on your local game client, r2modman is the recommended mod manager. It handles mod downloads, dependency resolution, and profile management. Players connecting to your modded server should use r2modman to install the same set of mods locally.
- Download r2modman from Thunderstore or its GitHub releases page.
- Select Risk of Rain 2 as the game.
- Create a profile and install the mods your server requires.
- Launch the game through r2modman to ensure all mods are loaded.
Save Management
Risk of Rain 2 dedicated servers handle run state and progression differently from single-player. Here are the key points to understand:
- Run persistence: A Risk of Rain 2 run lasts as long as the server is running. If the server restarts or is stopped, the current run ends and a new lobby is created when the server starts again. There is no mid-run save system — this is by design, as runs are intended to be continuous sessions.
- Player profiles: Unlocks and player progression (items, skins, challenges) are stored client-side, not on the server. Players retain their unlocks regardless of server state.
- Server configuration persistence: Your
server.cfgand GPanel startup variables persist across restarts. Only the in-progress run is lost when the server stops.
Common Issues
Server Not Appearing in the Browser
- Confirm the server is fully started in GPanel. The server must complete its startup sequence before it registers with the master server.
- Verify that the
ADVERTISEstartup variable is set to1. - New servers can take several minutes to appear in the browser. Try direct connect while you wait.
- Check the GPanel console for errors. If the server is crashing or failing to initialize, it will not appear in the browser.
Players Cannot Connect
- Ensure the server is running and not in a crash loop. Check the GPanel console for error messages.
- If you set a password, confirm players are entering it correctly. Passwords are case-sensitive.
- Verify that both you and your players are running the same game version. Risk of Rain 2 updates can break compatibility between mismatched versions.
- If using mods, ensure all connecting players have the same mods and versions installed. Mod mismatches are the most common cause of failed connections on modded servers.
Related Articles
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
- Scheduled Restarts
- Server Startup Guide
Need Help?
If you run into an issue not covered in this guide, our support team is ready to help. Submit a support ticket and include your server ID, a description of the problem, and any relevant console output from GPanel.