Renown Dedicated Server Setup Guide

A Renown dedicated server gives you a separate machine to run your world, control server rules, manage saves, and support more stable PvP sessions.

This matters because poor ports, missing EOS flags, weak hardware, or bad configuration can cause lag, crashes, connection issues, or a server that does not appear in listings.

To set up a Renown dedicated server, use SteamCMD with App ID 1512690, launch Renown_CombatServer.exe on Windows or Renown_CombatServer.sh on Linux, configure EOS correctly, and open the required ports: 7777, 27015, 9999, and 25575 if you use RCON.

This guide walks you through Renown server setup, Windows and Linux configuration, Game.ini settings, ports, troubleshooting, backups, performance tips, and hosting decisions so you can build a server that is easier to manage and more reliable for active players.

Verified Renown Server Facts

• Dedicated Server App ID: 1512690
• Supported systems: Windows and Linux
• Windows executable: Renown_CombatServer.exe
• Linux executable: Renown_CombatServer.sh
• Default gameplay port: 7777
• Default query port: 27015
• Default beacon port: 9999
• Default RCON port: 25575
• Technology: Unreal Engine and Epic Online Services

Renown Dedicated Server Requirements

Let’s discuss practical Renown dedicated server sizing recommendations. Renown’s official Steam page describes it as a PvP medieval survival game with combat, building, sieges, progression, wipe systems, and community host tools.

For active Renown communities, dedicated servers give admins more control over CPU, RAM, storage, networking, and long-term server management.

Small Server (5–15 Players)

Use case: private groups, testing

• CPU: 4 cores, 4.0 GHz+
• RAM: 8–12 GB
• Storage: SSD minimum, NVMe recommended
• Network: 1 Gbps port recommended

Behavior:

• Suitable for exploration and light PvP if the CPU and network are stable
• Performance may drop when many players cluster in one area
• HDDs can increase save and update delays, so SSD or NVMe storage is safer for active worlds

Medium Server (20–50 Players)

Use case: active communities, regular PvP

• CPU: 6–8 cores, high single-core speed
• RAM: 16–24 GB
• Storage: SSD minimum, NVMe strongly recommended
• Network: 1–10 Gbps

What changes:

• Load shifts from idle world simulation to player-driven stress
• Group fights can increase server tick pressure
• Memory usage can grow with builds, loot, active zones, and long-running world state

Large PvP Server (50+ Players, If Supported)

Use case: clans, raids, competitive servers

• CPU: high-frequency modern CPUs, verified with live monitoring
• RAM: 32–64 GB
• Storage: high-speed NVMe
• Network: 1–10 Gbps depending on player count, region, and DDoS exposure

Reality:

• A server may run normally at idle, then struggle during raids or clustered PvP
• Sieges stack:
  • player actions
  • physics updates
  • structure damage
  • AI calculations

Like many Unreal-based multiplayer servers, heavy gameplay events can be sensitive to per-core CPU performance.

When too many players fight in one area, weak per-core CPU performance may struggle to keep up.

What Actually Drives Performance

CPU Is Often the Primary Bottleneck

Renown’s real-time combat, physics, and world updates can increase server tick workload.

When players gather, the number of calculations increases fast. Weak per-core CPU performance can increase tick time, lag, and delayed combat feedback.

RAM Scales with World State

RAM usage can grow with player-built structures, stored items, and active entities.

Large bases and busy areas increase memory pressure over time.

NVMe Is Recommended for Stability

The server needs to write saves, logs, and updates reliably. Slow disks can contribute to longer save times and may worsen lag during save-heavy moments.

Network Affects PvP Fairness

High latency delays hit registration and movement sync. In melee combat, even small delays change outcomes. Public PvP servers should also consider DDoS protected dedicated servers because attacks can disrupt availability during peak activity.

Why Low-End Hosting Can Struggle

Budget shared setups may struggle when they:

• Use Low Clock-Speed CPUs
• Oversell shared resources
• Throttle performance during spikes

They may handle idle load but struggle during real gameplay spikes. For public PvP worlds, bare metal servers reduce shared-resource contention by giving one user access to the full physical machine.

Renown Dedicated Server Setup (Windows)

Let’s have a look at how to set up the Renown dedicated server on Windows.

Step 1: Install SteamCMD

SteamCMD downloads and updates the dedicated server.

• Download from Valve

Extract to:

C:\steamcmd

Run it once to complete the initial update.

Step 2: Create Server Directory

Create a clean folder:

C:\RenownServer

Do not mix this with your main game install.

Step 3: Download Server Files (Critical Step)

Launch SteamCMD:

steamcmd

Run:

login anonymous

force_install_dir C:\RenownServer

app_update 1512690 validate

Important:

• The Renown Dedicated Server AppID is 1512690
• A wrong AppID can download the wrong tool or fail the install
• Always confirm from SteamDB, Steam tools, or current Renown server documentation

Step 4: Verify File Structure

After installation, confirm the executable and main server folder:

C:\RenownServer

├── Renown_CombatServer.exe ← correct executable name

├── Engine\

├── Renown_Combat\

Key Paths:

• Expected Active Config After First Run: Renown_Combat\Saved\Config\WindowsServer\
• Logs: Renown_Combat\Saved\Logs\

If the executable or Renown_Combat folder is missing, validate the install. If Saved/Config is missing, run the server once.

Step 5: First Run (Generate Configs)

Before editing anything:

• Run the server once
• Let it fully start
• Then stop it

This generates the required config files. Skipping this step causes missing configs.

Step 6: Configure Game.ini

Go to: C:\RenownServer\Renown_Combat\Saved\Config\WindowsServer\Game.ini

Example:Use your server-generated section header, then apply supported values such as: MaxPlayers=50

Important Points:

• Section headers may change with updates
• Always verify changes in logs
• Do not copy configs from other Unreal Engine games

Step 7: Create Proper Launch Script (Fixed)

Create start_server.bat inside:

C:\RenownServer

Use:

@echo off

set EOS_FLAGS=-ini:Engine:[EpicOnlineServices]:DedicatedServerClientId=xyza78917DzEE5Ey0isciVt66QDm5IzM -ini:Engine:[EpicOnlineServices]:DedicatedServerClientSecret=m/mrnywFCdeA1mW3ZSvv3qcVlQlfwi1a+7Z63Q44EGU

cd /d C:\RenownServer

start "" Renown_CombatServer.exe -log %EOS_FLAGS%

Optional port overrides (defaults are shown):

-PORT=7777 -QUERYPORT=27015 -BeaconPort=9999 -RCONPort=25575

Why This Works:

• cd /d ensures correct directory
• start "" avoids Windows path issues
• Helps the script work from different launch contexts

Step 8: Configure Windows Firewall

Open required ports.

Steps:

Open required ports:

1. Open Windows Defender Firewall
2. Go to Advanced Settings
3. Click Inbound Rules → New Rule → Port
4. Add: UDP 7777 and TCP/UDP 27015 for the default setup
5. Also open UDP 9999 (Beacon) and TCP 25575 (RCON)
6. Allow Connection and apply to all profiles
7. Also allow Renown_CombatServer.exe

Microsoft’s Windows Firewall guidance explains how inbound port rules allow services to receive TCP or UDP traffic on specified ports.

Step 9: Configure Router Port Forwarding

If hosting from home:

Forward these ports:

• 7777 UDP → Local IP
• 27015 TCP/UDP → Local IP
• 9999 UDP → Local IP

Critical Points:

• Without port forwarding, outside players usually cannot reach a home-hosted server
• If using CGNAT, port forwarding will fail

In that case, use VPS or dedicated hosting.

Step 10: Run The Server

• Double-click start_server.bat
• Wait for full initialization
• Check logs for errors

First launch will:

• generate world data
• take longer than usual

Step 11: Test Server Listing And Connection

Local or LAN Test:

127.0.0.1:7777

External Test, If Direct Connection Works On Your Build:

YOUR_PUBLIC_IP:7777

If direct connection does not work, test through the public server list and confirm EOS, query port, beacon port, and firewall rules.

Renown Dedicated Server Setup (Linux)

Running a Renown dedicated server on Linux can give you better uptime, cleaner restarts, and stronger control than a manual desktop setup. For long-running Linux setups, Linux dedicated servers give admins root access, service control, and cleaner restart management.

The key is to separate root tasks from server-user tasks, verify the executable name, and avoid guessing config headers.

SteamDB lists 1512690 as the Renown Dedicated Server tool, with Windows and Linux support. Current Renown hosting documentation also points users to the Renown_Combat/Saved/Config/LinuxServer folder for direct settings edits.

Step 1: Prepare The System

Run these commands from your normal sudo user, not from the renown user:

sudo apt update && sudo apt upgrade -y

sudo apt install wget tar curl lib32gcc-s1 screen nano -y

Why this matters:

• SteamCMD needs 32-bit Linux libraries.
• Missing packages can stop the server from launching.
• System setup should happen before creating the service user.

Step 2: Create A Dedicated Server User

Create a non-root user for the server:

sudo adduser renown

Do not run the server as root.

Why this matters:

• A separate user limits system risk.
• File permissions stay cleaner.
• The systemd service can run under this user safely.

Step 3: Install SteamCMD As The Renown User

Switch into the server user only for SteamCMD and server files:

sudo -iu renown

mkdir -p ~/steamcmd

cd ~/steamcmd

wget https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz

tar -xvzf steamcmd_linux.tar.gz

./steamcmd.sh

Let SteamCMD update, then type:

quit

Step 4: Create The Server Directory

Still as the renown user, create the install folder:

mkdir -p ~/renownserver

This keeps the server files separate from SteamCMD.

Step 5: Download The Renown Dedicated Server Files

Run SteamCMD:

cd ~/steamcmd

./steamcmd.sh

Install the Renown dedicated server:

login anonymous

force_install_dir /home/renown/renownserver

app_update 1512690 validate

quit

Why this matters:

• 1512690 is the Renown Dedicated Server AppID on SteamDB.
• validate checks missing or broken files.
• A wrong AppID downloads the wrong tool.

Step 6: Locate The Actual Server Executable

The correct Linux executable is: Renown_CombatServer.shSome host panels may launch the underlying Linux shipping binary directly, so follow your panel’s generated startup command if it differs from this script.

Make it executable if needed:

chmod +x /home/renown/renownserver/Renown_CombatServer.sh

Step 7: First Server Run To Generate Configs

cd ~/renownserver

./Renown_CombatServer.sh -log

Let the server fully start, then stop it. The first run creates config folders. Editing configs before first launch may do nothing.

Step 8: Locate And Edit game.ini

Expected config path:

/home/renown/renownserver/Renown_Combat/Saved/Config/LinuxServer/Game.ini

Edit with:

nano /home/renown/renownserver/Renown_Combat/Saved/Config/LinuxServer/Game.ini

Use the exact section headers generated by the server. Check logs after restart to confirm settings loaded.

Important:

• Use the exact section headers generated by the server.
• Do not copy section headers from other Unreal Engine games.
• Keep the Windows and Linux guide consistent once the correct Renown header is verified.

Step 9: Create A Start Script

Create the start script as the renown user:

nano /home/renown/renownserver/start.sh

Add this, replacing the executable path:

#!/bin/bash

EOS_FLAGS="-ini:Engine:[EpicOnlineServices]:DedicatedServerClientId=xyza78917DzEE5Ey0isciVt66QDm5IzM -ini:Engine:[EpicOnlineServices]:DedicatedServerClientSecret=m/mrnywFCdeA1mW3ZSvv3qcVlQlfwi1a+7Z63Q44EGU"

cd /home/renown/renownserver

exec ./Renown_CombatServer.sh -log -PORT=7777 -QUERYPORT=27015 -BeaconPort=9999 $EOS_FLAGS

Save it, then run:

chmod +x /home/renown/renownserver/start.sh

Now exit back to your sudo user:

exit

Step 10: Create The systemd Service

Run this from your normal sudo user:

sudo nano /etc/systemd/system/renown.service

Add:

[Unit]

Description=Renown Dedicated Server

Requires=network.target local-fs.target

After=network.target local-fs.target

StartLimitInterval=60s

StartLimitBurst=3

[Service]

Type=simple

User=renown

Group=renown

WorkingDirectory=/home/renown/renownserver

ExecStart=/home/renown/renownserver/start.sh

Restart=always

RestartSec=5

[Install]

WantedBy=multi-user.target

Then Run:

sudo systemctl daemon-reload

sudo systemctl enable renown

sudo systemctl start renown

Do not use daemon-reexec here. daemon-reload is the correct command after creating or editing a unit file.

Step 11: Configure Firewall And Ports

Allow the main gameplay and query ports:

sudo ufw allow 7777/udp

sudo ufw allow 9999/udp

sudo ufw allow 27015/udp

sudo ufw allow 27015/tcp

sudo ufw allow 25575/tcp

sudo ufw reload

Also forward these ports in your router or cloud firewall.

Important:

• If port forwarding is missing, the server may work locally but fail online.
• If your ISP uses CGNAT, home hosting will not work without a tunnel, VPS, or dedicated server.

Step 12: Monitor The Server

Check service status:

sudo systemctl status renown

Follow live logs:

sudo journalctl -u renown -f

Restart after config changes:

sudo systemctl restart renown

Renown Game.ini Configuration Explained

Renown configuration can vary across self-hosted installs and host panels, so do not assume one universal file layout.

Self-hosted Renown documentation most consistently points to Unreal-style .ini files under /Renown_Combat/Saved/Config/. Some host panels may expose server settings through panel fields or provider-specific files, so treat JSON-style settings as host-specific.

First: Find The Active Config File

Before editing, search the generated config folders and any host-panel-specific paths.

Linux:

find /home/renown/renownserver \( -iname "game.ini" -o -iname "engine.ini" \)

Common Nodecraft-style path:

/Renown_Combat/Saved/Config/LinuxServer/game.ini

Host-panel-specific path, only if your provider confirms it:

C:\RenownServer\Config\ServerHostSettings.json

Use the file your server actually reads. If both exist, change one setting, restart, and confirm it applies.

Server Identity And Access Settings

Hosted panels may expose these settings differently, but self-hosted installs should prioritize the generated .ini files.

ServerName

Controls how the server appears in the list.

Host-panel JSON example, if your provider uses JSON settings:

"ServerName": "My Renown Server"

Use a short, readable name. Avoid symbols and long spam-style names.

MaxPlayers

Controls the player limit.

Host-panel JSON example, if your provider uses JSON settings:

"MaxPlayers": 50

Safe values:

• 10–20 For Private Servers
• 20–50 For Community Servers
• 50+ Only If Your Server Build, Config, And Hardware Support It

A higher cap can increase CPU pressure during raids and clustered PvP.

ServerPassword

Controls private access.

ServerPassword may appear in generated .ini files or host-panel fields depending on your setup. Treat the exact location as host-dependent.

Host-panel JSON example, if your provider uses JSON settings:

"ServerPassword": "StrongPrivatePassword"

INI example:

ServerPassword=StrongPrivatePassword

After setting it, restart the server and test with a non-admin account.

Gameplay Configuration Settings

Many gameplay and server settings are stored in generated .ini files, but exact sections should be verified from the server-generated config and logs.

If your server build or host panel exposes these values, they may appear in a generated Game.ini structure like this:

[/Script/Renown.GameMode]

DayNightCycleSpeed=1.0

ResourceRespawnRate=1.0

NPCSpawnRate=1.0

[/Script/Renown.Combat]

PlayerDamageMultiplier=1.0

NPCDamageMultiplier=1.0

DayNightCycleSpeed

Controls how fast the day and night cycle moves if this setting is exposed by your server build or host panel.

Safe value:

DayNightCycleSpeed=1.0

Aggressive value:

DayNightCycleSpeed=2.0

Use higher values for event servers, not serious survival worlds.

ResourceRespawnRate

Controls how quickly resources return if this setting is exposed by your server build or host panel.

Safe value:

ResourceRespawnRate=1.0

Fast progression:

ResourceRespawnRate=2.0

High values reduce grind but speed up raiding and gear recovery.

NPCSpawnRate

Controls NPC spawn frequency if this setting is exposed by your server build or host panel.

Safe value:

NPCSpawnRate=1.0

Higher values increase PvE activity and CPU load.

PlayerDamageMultiplier

Controls player damage if this setting is exposed by your server build or host panel.

Safe value:

PlayerDamageMultiplier=1.0

Hardcore PvP:

PlayerDamageMultiplier=1.25

Higher damage shortens fights and makes raids more punishing.

NPCDamageMultiplier

Controls NPC damage if this setting is exposed by your server build or host panel.

Safe value:

NPCDamageMultiplier=1.0

Harder PvE:

NPCDamageMultiplier=1.25

Do not change player damage and ignore NPC damage. That creates lopsided balance.

Network Settings

MaxPing

MaxPing limits high-latency players. Some Renown admin guides list it as a configurable server value, but exact placement can vary by host panel or config layout.

Competitive PvP:

MaxPing=150

Casual server:

MaxPing=200

Loose access:

MaxPing=250

Lower values can improve combat quality by limiting high-latency players. Higher values allow broader access but can increase desync risk.

Region

Do not invent a Region key unless your host exposes it.

Region is usually controlled by:

• Physical Server Location
• Ping Limit
• Host Panel Metadata
• Server Browser Routing

For PvP, host close to your main player base.

Admin And RCON Settings

AdminPassword

AdminPassword may be set in the generated .ini files or exposed through your host panel, depending on the setup.

AdminPassword=UseALongAdminPassword

After setting it:

• Restart The Server
• Join The Server
• Open Settings
• Enable Admin Settings
• Enter The Admin Password

RCON Settings

RCON is documented for Renown, but host panels may expose it differently. Do not assume raw Game.ini keys always work.

Typical host-panel values may look like:

ENABLE_RCON=true

RCON_PORT=25575

RCON_PASSWORD=UseADifferentStrongPassword

Use your host’s panel first. If self-hosting, confirm RCON is enabled and bound to the expected port in logs.

Renown Server Not Showing

Renown servers usually fail to appear or connect because of a small number of common setup issues. Current SteamDB data and Renown community documentation confirm the main ports, launch flags, and binary names. If those are wrong, nothing else matters.

Critical First Check (Do This Before Anything Else)

If your server is not showing:

Check EOS Credentials → Check Ports → Check Firewall → Check Logs

From current SteamDB and Renown community setup references:

• Game Port: 7777
• Query Port: 27015
• Beacon Port: 9999
• RCON Port: 25575

Missing gameplay, query, or beacon ports can break visibility or joining; RCON is only needed for remote admin.

Troubleshooting Matrix

EOS Configuration (Common Root Cause)

Renown requires Epic Online Services (EOS) credentials. Epic Online Services sessions documentation explains how dedicated servers can update session state and support multiplayer discovery.

If these are missing or incorrect:

• The server may not appear
• The server may fail to authenticate
• The server may run but remain invisible in listings

Launch examples commonly include EOS flags:

-ini:Engine:[EpicOnlineServices]:DedicatedServerClientId=xyza78917DzEE5Ey0isciVt66QDm5IzM

-ini:Engine:[EpicOnlineServices]:DedicatedServerClientSecret=m/mrnywFCdeA1mW3ZSvv3qcVlQlfwi1a+7Z63Q44EGU

These must be included in every server launch. Check your logs for EOS authentication messages to confirm they are working.

Server Binary (Critical Fix)

Using the wrong binary:

• The server may start incorrectly
• Ports may not bind properly
• Listing may fail or logs may show startup errors

NAT And CGNAT

• NAT → normal router mapping
• CGNAT → no public IP

Detect CGNAT:

• Router WAN IP ≠ public IP

Fix:

• request public IP
• or use VPS/dedicated server

Firewall And Ports (Default Requirements)

Open the required ports for your use case:

Log-Based Debugging

Look for:

Server Crashes, Restarts, And Early Access Stability

Renown stability can depend on load, server configuration, and Early Access update cycles.

Crash Patterns

Hardware Reality

• Strong per-core CPU performance often matters most
• Player clustering can spike load
• Large PvP fights often create maximum server stress

Memory Behavior

• RAM usage may increase over long sessions
• Performance may degrade
• Scheduled restarts may help

Restart Strategy

• Every 12–24 hours for busy servers, if testing shows long-session degradation
• After updates
• Before peak hours

Why Early Access Affects Stability

Updates can change:

• Configs
• Networking
• Save structure

Always back up before updating.

MaxPing, Latency, And Performance Optimization

Let’s discuss how MaxPing and latency actually affect your server and how to do performance optimization.

Suggested MaxPing Values

PvP Impact

High latency causes:

• Delayed hits
• Desync
• Inconsistent combat

Regional Hosting

Host near players.

Why Global Servers Can Feel Unfair

Mixed latency can create unfair-feeling fights. Use regional servers when most players are concentrated in one area.

Performance Optimization

Renown may expose some advanced Unreal network values in Engine.ini, but most admins should avoid changing them unless they understand the impact and can test safely.

Many hosting providers limit access to low-level optimization settings.

Self-hosted installs on Linux give you OS-level control, such as CPU affinity and process priority using tools like taskset or nice. Some engine/network settings may exist, but they are advanced and should not be treated as simple performance fixes.

Real performance improvements come from:

• Keeping server files updated
• Avoiding unstable or extreme config values
• Aligning player count with hardware limits
• Monitoring logs for errors
• Restarting servers regularly

Backups, Wipes, And Server Data Strategy

Let’s discuss how to protect your server data, manage wipes, and reduce the risk of irreversible loss.

Why Backups Matter

Your Renown server depends on saved world, player, and configuration data.

Lose it, and you may lose:

• Player Progress
• Bases And Structures
• Long-Term World State

Without backups, reliable recovery may not be possible.

What You Need To Back Up

Focus on these paths first:

Renown_Combat/Saved/SaveGames

Renown_Combat/Saved/Config

Renown_Combat/Config, if your install uses custom files there

• SaveGames: world and player data
• Saved/Config: gameplay rules
• Config: server identity, access, and custom server settings

Backup Workflow

Stop Server → Backup Files → Apply Change → Start → Test

Key rules:

• Stop Server Before Copying
• Never Overwrite Your Only Backup
• Always Verify After Restart

Backup Frequency

Follow a fixed schedule:

• Before Updates
• Before Config Changes
• Before Installing Mods Or Custom Files
• Daily For Active Servers
• Weekly Archive

Keep:

• Latest Backup
• Pre-Update Backup
• Fallback Copy

When To Wipe

Wipes reset the world when it becomes unbalanced.

Wipe when:

• Progression Stalls
• New Players Cannot Compete
• Map Is Overcrowded
• Updates Break Balance
• Saves Become Unstable

Why Wipes Work

Wipes fix problems that settings cannot:

• Resource Hoarding
• Abandoned Bases
• Uneven Progression

A fresh world can restore competition.

Prevent Data Loss

Follow strict rules:

• Stop Server Before Backup
• Never Edit Live Saves
• Store Backups Off-Server If Possible
• Label Backups Clearly
• Test Restore Once

Restore Validation

Stop → Replace Save → Start → Test Join

If it fails, that backup may not be usable and should not be your only restore point.

Mods, Custom Files, And Future Mod Support

Let’s discuss how custom files or mod workflows may behave when your server build or host supports them.

Current State

Mod or custom-file support may depend on:

• Hosting Provider
• Server Version
• Update Compatibility

There is no universal standard.

How Mods Or Custom Files May Be Managed

If supported, mods or custom files may be handled through:

• Control Panels
• File Uploads
• Startup Settings

Use one supported method consistently.

Risks

Safe Mod Workflow

Stop → Backup → Install One Supported Mod Or Custom File → Restart → Test

What Not To Do

Avoid:

• installing multiple mods or custom files at once
• skipping backups
• testing on live servers
• using outdated mods or unsupported custom files

How RedSwitches Supports Scalable Renown Servers

If shared hosting limits your setup, RedSwitches gives you direct control over how your Renown server runs.

Dedicated resources reduce noisy-neighbor contention, making CPU, memory, and bandwidth more predictable during peak PvP activity.

This matters when player clustering increases load and exposes weak infrastructure.

Dedicated hosting can make monthly infrastructure costs more predictable than usage-based cloud setups during high-traffic periods.

High bandwidth availability can support smoother connections during large fights and active sessions.

Full system-level access allows you to manage ports, startup parameters, backups, and server behavior without panel restrictions.

This setup is most useful for large PvP servers, custom environments, and communities that need regional deployments.

It also supports running multiple instances on the same machine, which is useful for testing, seasonal resets, or separate worlds.