Wreckfest 2 Dedicated Server Setup Guide 2026

Your Wreckfest 2 race night should not disappear because one host closes the game. A dedicated server keeps the session independent while giving you persistent control over events, bots, player roles, and connectivity.

To set one up, install the standalone Wreckfest 2 Dedicated Server tool through Steam Tools or SteamCMD using App ID 3519390. Launch Wreckfest2.exe with --server and a separate --save-dir. Allow UDP port 30100 through your firewall and router, then configure server_config.scnf and its linked .becl event rotation. Windows is the native deployment path, while Linux installations rely on community-supported Wine or Proton. Each event supports up to 24 human players and bots combined.

This guide walks you through installation, first launch, configuration, administrator roles, multi-instance hosting, and troubleshooting.

It also separates current Wreckfest 2 requirements from outdated Wreckfest 1 instructions, helping you build the server correctly the first time.

Wreckfest 2 Dedicated Server Quick Facts

2026 Update Note: Wreckfest 2 Content Update #8 was released on June 30, 2026. It added progression, new multiplayer race content, Random Waypoint Mode for multiplayer, performance improvements, and physics and damage tweaks. Recheck server behavior after every major Early Access update.

Wreckfest 2 Dedicated Server vs Wreckfest 1: What Changed?

Wreckfest 2 changes how you install, configure, and maintain a dedicated server. If you hosted Wreckfest 1, do not assume the workflow is identical. Here’s the precise breakdown.

Wreckfest 2 is stricter on installation, more structured in configuration, and still evolving. Treat it as a live development server platform, not a finished ecosystem.

Wreckfest 2 Dedicated Server Hardware Guidance (By Player Count)

Bugbear has not published official hardware specs for the Wreckfest 2 dedicated server, so treat the guidance below as estimated starting points, not official minimum requirements. The guidance below is based on community experience from Wreckfest 1, early Wreckfest 2 testing, and general physics-based multiplayer behavior.

Wreckfest 2 dedicated servers are likely CPU-sensitive because racing, collisions, bots, and player synchronization can increase simulation load, especially in full lobbies. Strong single-core performance usually matters more than simply adding more cores. Prioritize modern per-core performance, then test the server under your expected player and bot load.

Bot-heavy sessions can add noticeable CPU load compared to human-only sessions, so test bot count before scaling hardware.

Estimated Hardware Guidance

RAM Reality

4GB is a reasonable starting point for small lobbies. Around 6GB suits many mid-size deployments, while 8GB or more provides headroom for full fields, bots, logs, and background services.

Allocate additional memory for multiple instances or Wine/Proton deployments. Treat these figures as starting estimates, not official minimum requirements.

SSD vs NVMe

HDDs can increase load times. An SSD is a sensible baseline, while NVMe can help with faster loads, logs, and multi-instance environments.

Dedicated Cores vs Shared Hosting

Shared environments can introduce CPU contention. When another tenant spikes usage, server performance can become less consistent. Physics-based games are sensitive to jitter. Dedicated cores can help maintain steadier race simulation, especially for competitive lobbies.

Bandwidth for 24-Player Servers

A stable 1Gbps uplink is usually enough for most single-instance full-grid races. Public servers with frequent joins or multi-instance deployments benefit from higher uplink capacity, but it is not a hard requirement.

If you plan to run competitive leagues, multi-instance environments, or public community hubs, deploy on proper gaming dedicated server infrastructure with strong single-core performance and SSD/NVMe storage. Stability matters more than peak specs.

Wreckfest 2 Dedicated Server Setup via Steam Tools

Here is how to set up a Wreckfest 2 dedicated server through Steam Tools.

1) Enable Tools

• Open Steam
• Go to the Library
• Change filter to Tools
• Search for Wreckfest 2 Dedicated Server

This is separate from the main game.

The dedicated server tool uses App ID 3519390.

2) Install the Server Tool

Click Install.
Default path:

Steam\steamapps\common\Wreckfest 2 Dedicated Server

You can confirm via Browse Local Files.

3) Startup Scripts

Inside the install folder, run:

• start_community_server.bat → Supplied community-server launcher

Use this launcher for the first test. You can create separate launch commands later when configuring custom save directories or multiple instances.

Wreckfest 2 Dedicated Server Setup Using SteamCMD

Here is how to set up a Wreckfest 2 dedicated server using SteamCMD.

Step 1: Download SteamCMD

Download SteamCMD from Valve’s official site. Extract it to a dedicated folder, such as:

C:\steamcmd

Run steamcmd.exe once to initialize.

Step 2: Log In

Try anonymous installation first:

steamcmd +force_install_dir C:\Wreckfest2Server +login anonymous +app_update 3519390 validate +quit

If SteamCMD returns a subscription or entitlement error, start SteamCMD interactively, run login your_steam_username, complete any Steam Guard prompt, and then run the installation commands. Do not store your Steam password or Steam Guard secret in a batch file.

Step 3: Install the Dedicated Server Tool

Use App ID 3519390.

Example structure:

force_install_dir C:\Wreckfest2Server
app_update 3519390 validate

This installs the dedicated server tool into your specified directory.

Step 4: Understand Folder Structure

Inside your install directory, you’ll usually find:

• Server executable
• Launch scripts
• Logs and save directories

Keep this folder clean. Avoid mixing it with game client files, and remember that config files may be created in LocalAppData or inside your active --save-dir path.

Step 5: Launch Flags Explained

To start the server manually, use:

Wreckfest2.exe --server --save-dir="C:\Wreckfest2Server\Save"

--server starts the executable in dedicated-server mode.--save-dir defines where configurations, logs, privileges, and other persistent server data are stored.

Critical Rule: Save Directory Must Exist

If the specified save directory does not exist, the server may fail to initialize configuration files correctly.

The --save-dir folder must already exist before first launch.

Create it manually before starting the server. Do not rely on the server to auto-create it.

After Installation

Once installed:

• Steam does not need to remain open.
• The server runs independently.
• Update regularly using SteamCMD to maintain version parity.

Wreckfest 2 Dedicated Server Config File (server_config.scnf)

If you run a Wreckfest 2 dedicated server, this file controls core server behavior.

Where server_config.scnf Actually Lives

Location depends on how you launch the server.

If you use --save-dir

<save-dir>\server_config.scnf

Example:

C:\Wreckfest2Server\Save\server_config.scnf

If you do NOT use --save-dir

The file defaults to:

%LocalAppData%\Wreckfest 2\server_config.scnf

This is why many users think the config is “missing.” They check the install folder instead of LocalAppData.

When the File Is Created

• On a fresh installation, the configuration files appear after the server completes a successful first launch. Create the specified --save-dir, start the server, wait for initialization to finish, and then stop it before editing the generated files.
• save_default_event generates a default event configuration; it is not required to create or persist server_config.scnf.

Understanding the Structure

Current server_config.scnf files use JSON. The main sections are net server config and game server config. Event rotations and rules are stored separately in .becl files, cup configurations use .ccnl, and persistent roles and bans use server_privilege.sprv.

Older examples may use different schema versions. Do not remove `bbmeta` metadata or reject a configuration solely because it contains `ncnf` or `gcnf`. Use the files generated by the current build and preserve all property names and schema metadata exactly.

Network or Server Config: Identity & Connection Settings

This section controls the server’s identity and network settings.Typical parameters include:

• name
• password
• description
• log file name
• game port

If the server does not appear publicly, verify its configured UDP game port, Windows Firewall rule, provider firewall, router forwarding, public IP, and current server version.

Game Server Config: Core Environment Settings

This section controls settings such as the selected cup, event-loop reference, countdown time, voting time, and moderation defaults.

The participant limit is configured per event through `max number of participants` in the active `.becl` file. Wreckfest 2 supports up to 24 human players and bots combined, not 24 players plus additional bots.

Event or Rotation Settings: Track & Session Flow

Controls:

• Track order
• Event progression
• Session transitions

Early Access note:

• Rotation behavior had limitations in earlier Early Access builds.
• Always verify current behavior after major updates.

If rotation fails, confirm that event loop name in server_config.scnf matches the .becl filename without its extension. Use save_default_event only when you need a fresh default event file, and then reconfigure that generated file.

Rules: Gameplay Enforcement

This block controls race behavior.

Key areas:

Damage

Damage Level Changes:

• Collision intensity
• Mechanical failure likelihood
• Competitive realism

Higher damage can make races more chaotic; test performance after changing damage rules.

Countdown

Countdown controls how much time players get before the race starts. Keep it long enough for players to load in, ready up, and settle before the first corner chaos begins.

Grid size controls how many vehicles can start the event. Match it to your player count and bot count instead of maxing it out blindly. A bigger grid can create better action, but it also adds more vehicles, collisions, and server load.

If the server starts stuttering, reduce bots or grid size before upgrading hardware.

Bot Configuration: The Hidden CPU Multiplier

Bots are not lightweight.

Bots can add AI, vehicle, and collision-related simulation load. Bot-heavy sessions can add noticeable CPU pressure.

If your server stutters:

Reduce bot count before upgrading hardware.

Editing the File Safely

A JSON-aware editor such as VS Code or Notepad++ is recommended because it makes syntax errors easier to identify.

Use:

• VS Code
• Notepad++

Incorrect formatting can prevent server startup.

If editing causes errors, use console commands instead.

Console Management: Professional Control Layer

The console is often safer than manual file edits. You access it from the server window.

Command Categories

Player Management

name "Server Name"

password "Password"

description "Description"

Role Assignment via Steam ID

Roles include:

• Default
• VIP
• Moderator
• Admin

Persistent roles and bans are stored in server_privilege.sprv inside the active save directory. If this file is deleted, replaced, or loaded from a different save directory, stored privileges may be lost.

Bot Control

Adjust bot presence via config or console.

If performance drops:

Lower bot count first.

Event Control

Important Commands:

• grid_size
• countdown
• damage

These commands affect race parameters. Check the current help output for accepted arguments and whether a restart or file update is required.

Server Control

• status → Check server state
• shutdown → Stop the process cleanly
• help → Display the current command list

Use the current build’s help output as the authority for available commands and arguments.

In-Game Lobby vs Dedicated Server Console

In-game host controls:

• Temporary
• Limited
• Session-bound

Dedicated server console:

• Persistent
• File-backed
• Role-aware
• Better suited for persistent server management

If you run a public or competitive server, use console + config.

Authority-Level Operational Advice

If your server:

• Doesn’t appear → Check UDP 30100, firewalls, NAT, CGNAT, and version parity
• Has role issues → Verify the active server_privilege.sprv file and SteamID64
• Loses settings → Confirm that the intended --save-dir is active
• Fails to load config → Verify the config path and validate the JSON
• Stutters → Reduce bots before scaling hardware

Wreckfest 2 Dedicated Server: Steam ID Roles & Privilege System

If you run a public or competitive Wreckfest 2 dedicated server, you must understand how privileges persist.

This system is file-backed, not session-based.

Role Hierarchy Explained

Wreckfest 2 uses role tiers linked to Steam IDs.

Current documented roles include:

• default
• vip
• moderator
• admin

admin is the highest listed administrative role. Exact permissions and available commands can change during Early Access, so verify them through the current console help output and SERVER_CONFIG_GUIDE.pdf.

Automatic Administrator Assignment Behavior

Current builds can automatically grant administrator privileges to the Steam account used to launch the server. This is different from automatically promoting the first player who joins.

Persistent assignments are stored in server_privilege.sprv. Deleting the file or changing the active save directory can remove previously stored roles.

Race Director Role

Race Director is an available server-management function, but its exact scope and accepted command syntax have varied between builds. Check the current console help output before assigning or documenting Race Director access, and do not treat it as equivalent to admin unless the current build confirms that behavior.

Assigning Roles Manually via Console

• Assign the administrator role with the player’s SteamID64:
• role STEAMID64,admin
• Do not add spaces around the comma.
• Use roles or the current help output to verify the assignment and available role commands.

Where Privileges Are Stored

Persistent roles and bans are stored in server_privilege.sprv.

With --save-dir, the file is stored inside that active directory. Without a custom save directory, check %LocalAppData%\Wreckfest 2\.

Back up this file to preserve roles and bans across reinstalls or save-directory changes.

Common Privilege Mistakes

Roles Not StickingCause:

• The wrong --save-dir is active
• server_privilege.sprv was deleted or replaced
• The SteamID64 or role command was entered incorrectly

Fix:

• Confirm the active save directory
• Verify that server_privilege.sprv exists
• Reassign the role with the correct SteamID64 and verify it with the current role commands

Admin Lost After Update

Cause:

• Save folder wiped
• Wrong save-dir used

Fix:

• Restore the backup of server_privilege.sprv
• Or reassign elevated roles through the current console workflow

Wreckfest 2 Dedicated Server: Ports, NAT & Static LAN IP Setup

Ports, NAT, and LAN IP setup determine whether your Wreckfest 2 dedicated server is visible publicly or only reachable locally.

Default Wreckfest 2 Server Port

The default game port is:UDP 30100Allow UDP 30100, or the alternative UDP game port configured in server_config.scnf, through your firewall and router before testing public connectivity.

Why Correct Port Forwarding Matters

If players cannot connect, verify the configured port, firewall rule, router forwarding, provider firewall, and public IP route.

Internal IP vs External IP

Your server machine has:

• Internal IP (LAN address, example: 192.168.x.x)
• External IP (public internet address)

Players outside your network connect to your external IP.

Your router must forward traffic from:

External IP → Internal Server IP

Router Port Forwarding (Conceptual Process)

1. Log in to your router
2. Find Port Forwarding
3. Create rule:
   • External Port: 30100
   • Internal IP: Your server machine
   • Internal Port: 30100
   • Protocol: UDP
4. Save and restart the router if required

Without correct forwarding, public players may not be able to connect.

Static LAN IP or DHCP Reservation Is Strongly Recommended

If your internal IP changes after a reboot, your port-forward rule can point to the wrong machine.

Use a static LAN IP on the server machine or a DHCP reservation in your router.Otherwise, your server may disappear from public access after local IP changes.

CGNAT Problem (Carrier-Grade NAT)

If your ISP uses CGNAT:

• You do not have a true public IP
• Port forwarding will not work

Symptoms:

• Server works locally
• Public port checkers fail

Fix:

• Request public IP from ISP
• Or host on dedicated infrastructure

Localhost vs LAN vs Public Testing

Test correctly.

• 127.0.0.1 → Same machine only
• 192.168.x.x → LAN testing
• Public IP → External players

If it works on LAN but not public, the issue is router or ISP.

Running Multiple Servers (Port and Save Directory Strategy)

Each server instance must use:

• Unique configured port
• Unique save directory

Example:Server 1 → 30100/UDPServer 2 → 30101/UDPServer 3 → 30102/UDPForward each configured UDP port separately.

Do not reuse the same configured port across active instances.

Multi-Instance Deployment: Run Multiple Wreckfest 2 Servers Properly

Here is how to run multiple Wreckfest 2 dedicated servers on one machine while reducing port conflicts, save conflicts, and CPU contention.

Rule 1: Unique --save-dir Per Instance

Example:

--save-dir=server1
--save-dir=server2
--save-dir=league_server

Each instance should have its own folder.

Otherwise:

• Config conflicts
• Role conflicts
• Log corruption

Rule 2: Unique Configured Port Per Instance

Launch example:

Wreckfest2.exe --server --save-dir="server1"
Wreckfest2.exe --server --save-dir="server2"

Set each instance’s unique game port inside its active server_config.scnf file.

Forward each configured port separately.

Rule 3: Separate Process Behavior

Each instance runs as:

• Independent process
• Independent memory usage
• Independent CPU load

If one instance crashes, other instances may continue running if they are separate proceses.

CPU Allocation Advice

Physics-heavy games can perform poorly when CPU cores are heavily shared.

If running multiple servers:

• Prioritize high clock speed
• Ensure enough threads for parallel instances
• Reduce bots before scaling hardware

Two stable 12-player servers often perform better than one overloaded 24-player server.

Folder Duplication Strategy

Safer Practice:

• Install once
• Use separate save directories
• Assign different --save-dir values
• Assign different configured ports
• Keep logs separate.

Vertical vs Horizontal Scaling

Vertical Scaling

Upgrade:

• CPU
• RAM
• NVMe

Use when running many small instances.

Horizontal Scaling

Use separate machines when:

• Running competitive leagues
• Running full 24-player grids
• Want maximum isolation

Public community hubs benefit from horizontal scaling.

Wreckfest 2 Dedicated Server on Linux: Experimental Wine Status

Wreckfest 2 does not currently provide a documented native Linux dedicated-server binary. Linux deployments run the Windows server through community-supported Wine or Proton configurations and should be tested against the current build before production use.

Why Xvfb May Be Required

Some Wine-based server attempts may require a display or console workaround on launch. On a headless Linux machine, a virtual framebuffer such as Xvfb may help Wine initialize Windows-style console behavior.

For experimental Linux testing, a possible stack is:

• Current Wine build
• Xvfb
• Proper 64-bit Visual C++ runtime
• Correct DISPLAY environment variable

Without Xvfb or another display workaround, some headless Wine setups may not run reliably.

Test this before using Linux for production.

Unofficial Docker and Wine Containers

Framing Linux as “Wine or don’t bother” is incomplete.

A practical experimental method is

Docker Container (Debian/Ubuntu Base) + Wine + Xvfb

Why this can help:

• Dependencies are isolated
• Wine version is controlled
• Display environment can be handled cleanly
• Deployment can become more repeatable

For some Linux hosts, Docker can reduce dependency conflicts, but it remains unofficial unless tested against the current Wreckfest 2 server build.

If you use Linux, treat Docker + Wine + Xvfb as an experimental structure and test it before production.

Performance Reality: Compatibility Risk and CPU Overhead

Wine may work for some users, but it adds compatibility risk.

One common difference can be CPU overhead.

Older Wreckfest and Wine community experience suggests:

• CPU usage can increase noticeably under Wine
• CPU load may increase noticeably on low-end hardware

That does not prove universal instability, but it does require testing.

It means:

• Wine can introduce overhead through API translation.
• On strong hardware, this overhead may be manageable after testing.
• On borderline CPUs, it becomes visible quickly.

So the correct framing is:

Wine can add CPU overhead.Under heavy load, that overhead becomes more apparent.

Proton vs Wine: Important Clarification

Neither Proton nor Wine is a native or officially documented Wreckfest 2 server platform. Current community deployments use either method, commonly with Xvfb or another headless wrapper.

Use a maintained Wine or Proton version, avoid outdated distribution packages, and test startup, memory use, console access, and player connections after every major server update.

SetThreadDescription & VC++ Redistributable

An Entry Point Not Found or SetThreadDescription error can indicate an outdated Windows or Wine environment, missing API support, damaged server files, or a runtime dependency problem.

Update Windows, Wine, or Proton as appropriate and validate the server installation first. Install or repair the Microsoft Visual C++ 2015–2022 Redistributable x64 or DirectX components only when the error or log indicates a related missing runtime dependency. Installing Visual C++ alone will not fix a Wine build that lacks the required Windows API.

Final Practical Deployment Advice

Use Linux if:

• You understand Wine
• You are comfortable configuring Xvfb
• You can troubleshoot runtime dependencies
• You accept higher CPU overhead

Use a Windows dedicated server for production if:

• You want the safest documented production path
• You run competitive servers
• You host public lobbies
• You manage multi-instance setups

Wreckfest 2 Dedicated Server: Troubleshooting Matrix

Use this table to diagnose issues by symptom and fix them logically.

Deploying Wreckfest 2 on RedSwitches High-Performance Dedicated Infrastructure

A dependable Wreckfest 2 dedicated server begins with the right foundation: App ID 3519390, UDP port 30100, a separate --save-dir, and correctly configured .scnf, .becl, .ccnl, and .sprv files. Since the game remains in Early Access, keep server and client builds aligned, back up custom files, and retest important settings after major updates.

Once the setup is complete, consistent CPU performance, low-latency networking, reliable storage, and sufficient resources become essential for smooth races. These requirements matter even more when running full 24-participant events, bot-heavy sessions, or multiple server instances.

RedSwitches dedicated servers provide dedicated resources, NVMe storage, high-speed networking, global deployment locations, and complete server control for public communities and competitive leagues.

This removes common limitations such as shared CPU contention, CGNAT, and unreliable home connectivity. Configure the server carefully, test it under real player load, and keep every race focused on the action rather than the infrastructure behind it.