V Rising Dedicated Server Hosting Guide 2026: Windows and Linux

Your world in V Rising lives or dies on one thing: the machine that runs it. When you host your own v rising dedicated server, you control when the sun rises, how hard raids hit, who joins, and how long the world survives after you log off. 

No random wipes. No strangers griefing your progress. Just a persistent map that follows your rules. 

In this guide, you’ll see exactly what hardware you need, how to set up the server on Windows and Linux, how to fix the “server not showing up” problem, and how to protect your saves from corruption or bad updates. 

You’ll also see when a home PC is enough and when it makes sense to move your world to real bare metal with a provider like RedSwitches. If you want a fast, stable vampire world that actually lasts, keep reading.

Key Takeaways

• A dedicated server keeps your V Rising world online 24/7 and gives you full control over rules, wipes, and who joins.
• Smooth gameplay depends on strong CPU clocks, enough RAM for your player cap, SSD or NVMe storage, and a clean, stable uplink.
• You can host on a home PC, a game panel, a VPS, or true bare metal; each option trades money for control, stability, and performance.
• Setup is simple once you follow the steps: install the server, run the start script, edit JSON settings, and open the correct ports.
• Most “server not showing up” errors come from blocked ports, wrong listing flags, or filters in the browser, not from the game itself.
• Also note that the Steam Launch button does not directly start the server for normal hosting use, and newly started servers can take a few minutes to appear in the list.
• Good admins back up saves, plan updates and wipes, and tune tick rate, player caps, and castle limits to match their hardware.
• Be careful with manual JSON edits too: malformed settings files and bad latest autosaves are two of the most common causes of broken worlds and connection errors after changes or updates.
• When raids lag, players time out, or you want a long-term public world, moving to dedicated bare metal with a host like RedSwitches pays off.

What a V Rising Dedicated Server Actually Does

When you click Play → Private Game, your PC acts as both client and host. The world shuts down the second you leave. If your power, Wi-Fi, or game crashes, the session dies with you. That works for short sessions, not for a growing clan.

Official servers sit at the other end. Stunlock or a partner runs the hardware, sets the rules, and controls wipes. You get convenience, but no say over raid windows, decay rates, or when the server resets.

Your own V Rising host server sits in between. It:

• Runs the world 24/7 as long as the machine stays on.
• Stores all save data, castles, and player progress in one place.
• Enforces your chosen V Rising dedicated server settings for PvE, PvP, raids, and progression.

You decide:

• PvE, PvP, or mixed rules.
• Raid days, raid hours, and decay speed.
• Max players, clan size, and progression pace.

With the right hardware, combat feels smoother, castles load faster, and disconnects drop. You trade a bit of setup time for full control over how your vampire world runs.

V Rising Dedicated Server Requirements (Hardware & Network)

Minimum and Recommended Specs for Home Hosting

V Rising is more CPU and RAM heavy than GPU heavy on the server side. You care more about single-core speed and memory headroom than raw core count.

Use these as starting points:

CPU examples

• Entry level: Intel Core i5-8400, i5-9400F, Ryzen 5 2600.
• Strong baseline: Intel i5-12400, i5-12600K, Ryzen 5 5600X, Ryzen 7 5800X.
• High end for busy servers: Intel i7-12700K+, Ryzen 7 7700X, Ryzen 9 7900.

RAM targets by player scale

• 2–8 players:
  • 8 GB system RAM minimum.
  • 16 GB gives room for mods, Discord, and background tools.
• 10–20 players:
  • 16 GB hard minimum.
  • 32 GB recommended if the box runs other services.
• 30+ players or long-running worlds:
  • 32 GB–64 GB RAM.
  • V Rising keeps more data in memory as castles, servants, and items pile up.

Storage

• HDD works for a tiny private world, but load times and saves feel sluggish.
• Use SSD as baseline.
• NVMe shines when:
  • You host several maps on one machine.
  • You run other services or Docker containers next to the game.

If you plan to take your V Rising dedicated server hosting public, treat these as bare minimums, not dream specs. The more players and castles you allow, the more headroom you need.

Sizing by Player Count and Server Type

You size a V Rising server by active players, not just total slots. A “40-slot” server with 8 regular players behaves very differently from a raid server that fills every weekend.

Use this simple map:

2–8 friends (home server)

• CPU: 4 cores / 8 threads with strong single-core speed.
• RAM: 16 GB.
• Storage: 250 GB SSD or NVMe.
• Use case: chill PvE or light PvP, no heavy mod packs.

10–30 players (small public or community)

• CPU: 6–8 cores with good boost clocks.
• RAM: 32 GB.
• Storage: fast SSD/NVMe, separate drive for backups if possible.
• Use case: active clan, regular raids, weekend events.

30–60+ players (busy PvP or event server)

• CPU: 8–16 cores with high clocks and strong per-core performance.
• RAM: 64 GB+.
• Storage: NVMe only, with enough space for several worlds and backup sets.
• Network: high, stable uplink and low-ping routes.

What pushes requirements up

• Mods and BepInEx plugins.
• Long uptime without restarts.
• Huge castles, lots of servants, and many active bases.

This is where bare metal from a provider like RedSwitches starts to make sense. You move from “can we run the server?” to “can we keep 40+ players stable on raid night with low ping and clean ticks?”.

Network, Ports, and ISP Limits

A strong CPU means nothing if your uplink chokes. Your V Rising server setup needs three things from the network: enough upload, low ping, and low jitter.

• Upload speed
  • 2–8 players: at least 10 Mbps upload.
  • 10–30 players: 25–50 Mbps upload.
  • 30+ players: 50 Mbps+ with no strict data cap.
• Ping vs Jitter
  • Ping is how long a packet takes to reach the server and come back.
  • Jitter is how much the delay swings up and down.
  • Players feel jitter as rubber-banding, skipped hits, and weird movement even when ping looks “fine”.
• Ports you must open and forward

Open the exact game and query ports defined in your ServerHostSettings.json. In the current official 1.1 examples, these are 27015/UDP for game traffic and 27016/UDP for the query port. If you change them, make sure your firewall, router, and server config all match.

If your router, ISP, or data cap fights you, a home v rising dedicated server windows build will always feel fragile. That is the point where hosted options start to pay off in both time and sanity.

Choosing How to Host Your V Rising Server

You can run a V Rising private server on your own PC, rent a game panel, spin up a VPS, or move straight to bare metal. Each path trades money for control and stability in a different way.

Hosting Options at a Glance

V Rising Dedicated Server Setup on Windows (Steam Tools)

This is the fastest path for most players who want a V Rising dedicated server Windows instance on a home PC or simple Windows box.

Install the V Rising Dedicated Server from Steam

Use the built-in Steam tool:

1. Open Steam, go to Library → Tools, and install V Rising Dedicated Server.
2. In the top menu, go to Library → Tools.
3. Search for “V Rising Dedicated Server” in the list.
4. Right-click it → Install.
5. Pick an install path with enough free space (SSD preferred).

After installation, keep the path handy. You will edit files in this folder in later steps.

First Run and Folder Structure

Before you touch configs, let the server create its own structure:

1. In the install folder, find start_server_example.bat.
2. Double-click it.
3. Let the console window run until it stops spamming messages, then close it.

This first run gives you the default server structure and settings templates. By default, V Rising stores server data under the user profile path. 

If you set -persistentDataPath in your custom start script, your saves and settings will instead live under that custom folder, which is the cleaner option for long-term hosting and for running multiple worlds on one machine.

You need these folders present before you copy or override any settings.

Create Your Own Start Script

You want a clean start script so you can:

• Name the server.
• Point saves and logs to clear locations.
• Run multiple worlds on the same machine.

Do this:

1. Copy start_server_example.bat in the same folder.
2. Rename the copy to something like Start_VRising_MyWorld.bat.
3. Right-click → Edit.

At the bottom, you will see a line that launches VRisingServer.exe with flags. Edit the key ones:

• -persistentDataPath “.\save-data\myworld”
• -serverName “My V Rising Server”
• -saveName “world1”
• -logFile “.\logs\myworld.log”

Example:

start “” VRisingServer.exe ^

 -persistentDataPath “.\save-data\myworld” ^

 -serverName “My V Rising Server” ^

 -saveName “world1” ^

 -logFile “.\logs\myworld.log”

Create a desktop shortcut:

• Right-click your custom .bat → Send to → Desktop (create shortcut).
• Use that shortcut every time you want to bring your server online.

Quick Test: Join Your Own Server

Now confirm the server actually accepts connections:

1. Run your custom .bat and wait for the console to settle.
2. On the same PC, launch the V Rising client.
3. Click Play → Online Play.
4. Click Show All Servers.
5. Search by the name you set in -serverName.

If you do not see it in the list:

• Use Direct Connect with 127.0.0.1:<gamePort>, using the game port defined in your ServerHostSettings.json.
• Or add the server in Steam: View → Game Servers → Add a server.

At this stage, the server usually works for:

• You on the same PC.
• Other devices on your LAN if they use your local IP.

Friends over the internet still cannot join until you open ports on your router and firewall (covered earlier in the networking section).

V Rising Dedicated Server Setup with SteamCMD (Windows and Linux)

SteamCMD gives you more control and lets you script updates. On Linux, V Rising hosting currently works by downloading the Windows dedicated server build and running it under Wine, since there is no native Linux dedicated server binary at this time.

This is also where the V Rising dedicated server download happens in a clean folder.

Install SteamCMD on Windows

Set up SteamCMD once and reuse it for other games:

1. Create C:\steamcmd.
2. Download SteamCMD for Windows from the official Valve page.
3. Extract steamcmd.exe into C:\steamcmd.
4. Open Command Prompt as admin.
5. Run:

cd C:\steamcmd

steamcmd.exe

SteamCMD will update itself and drop you at a Steam> prompt.

V Rising Dedicated Server Download Command

Now install the V Rising dedicated server SteamCMD build into its own folder:

Inside the SteamCMD prompt:

login anonymous

force_install_dir C:\VRisingServer

app_update 1829350 validate

quit

• force_install_dir sets the target folder.
• app_update 1829350 validate the dedicated server files.

After this, C:\VRisingServer contains VRisingServer.exe, start_server_example.bat, and the usual data folders. This is your clean base for scripted updates and automation.

Windows Startup Script for SteamCMD Build

Create a simple script to start the server with clear paths:

1. Go to C:\VRisingServer.
2. Copy start_server_example.bat to Start_VRising_Public.bat.
3. Edit the file and make the launch line explicit:

@echo off

cd /d C:\VRisingServer

start “” VRisingServer.exe ^

 -persistentDataPath “.\save-data\public” ^

 -serverName “RedSwitches PVP Test” ^

 -saveName “public_world” ^

 -logFile “.\logs\public.log”

You can also keep a tiny update script next to it:

@echo off

cd /d C:\steamcmd

steamcmd.exe +login anonymous ^

 +force_install_dir “C:\VRisingServer” ^

 +app_update 1829350 validate +quit

Run the update script before patch days, then start the server. This pattern works well on any Windows host.

Linux Hosting (SteamCMD + Wine for the Windows server binary)

V Rising only ships a Windows dedicated server binary right now, so V Rising dedicated server Linux setups run that binary under Wine. SteamCMD on Linux handles the download.

Basic pattern:

1. Create a system user (for example, steam).
2. Install SteamCMD on Linux (package or manual download).
3. Pick an install directory, such as /home/steam/V-Rising-Server.
4. Run:

steamcmd +@sSteamCmdForcePlatformType windows \

 +force_install_dir ‘/home/steam/V-Rising-Server’ \

 +login anonymous \

 +app_update 1829350 validate +quit

1. Copy start_server_example.bat to start_server.bat in the same folder.
2. Edit the .bat with your -persistentDataPath, -serverName, and -saveName flags, just like on Windows.

To start the server under Wine:

cd /home/steam/V-Rising-Server

xvfb-run wine start_server.bat

Key notes:

• Run it under a dedicated user, not root.
• Mount your save-data folder on fast storage if the box also runs other workloads.
• Keep your configured game and query ports open in the Linux firewall and at the provider level. If you use the current official example values, that means 27015 and 27016.

This pattern gives you a stable V Rising Linux server on a VPS or bare metal host without a full Windows license.

V Rising Dedicated Server Docker 

If you already run other services in containers, a V Rising dedicated server Docker setup can keep things tidy:

• SteamCMD, Wine, and VRisingServer.exe live inside the image.
• save-data and Settings live on mounted volumes.
• You rebuild or pull a fresh image for each major game patch.

Typical Docker layout:

• One container exposes the game and query UDP ports you configured for the server. If you follow the current official example values, that means 27015/udp and 27016/udp.
• A volume for /server/save-data so world data survives restarts.
• A volume for /server/VRisingServer_Data/StreamingAssets/Settings so you keep JSON configs under version control.

This route suits admins who already monitor and back up containers. You still follow the same config logic inside the container that you use on plain Windows or Linux: custom start script, clear persistentDataPath, and clean ServerHostSettings.json / ServerGameSettings.json.

Core V Rising Dedicated Server Settings

A V Rising dedicated server looks complex until you realise most of the logic lives in a few text files. Once you know where those files live and which keys matter, you can shape difficulty, PvP, raid windows, and even how often the world saves. This is where your server stops being “just another world” and starts matching your group’s playstyle.

Where Config Files Live

By default, the game ships “factory” configs in the install folder:

• VRisingServer_Data/StreamingAssets/Settings/ → source templates.
• Inside you’ll see files like:
  • ServerHostSettings.json
  • ServerGameSettings.json
  • adminlist.txt, banlist.txt (on many installs).

Never edit these originals.

On first run, the server creates a persistent data folder at the path you set with -persistentDataPath in your start script, often something like:

VRisingServer\

  save-data\

    Settings\

      ServerHostSettings.json

      ServerGameSettings.json

      adminlist.txt

      banlist.txt

Safe workflow:

1. Run the server once so save-data exists.
2. Copy config files from …StreamingAssets/Settings/ into save-data/Settings/.
3. Edit the copies in save-data/Settings/ only.

When you update the server, Steam overwrites the originals but leaves your save-data configs alone.

ServerHostSettings.json – Network, Identity, Visibility

ServerHostSettings.json defines who can see your server, how they connect, and which save to load. Typical keys you will touch:

• Name – Server name shown in the browser.
• Description – Short line players see in the details panel.
• Port – Game port. Use the value configured in your ServerHostSettings.json. In the current official example config, this is 27015.
• QueryPort – Server list / Steam query port. In the current official example config, this is 27016.
• MaxConnectedUsers – Player cap (1–100+ depending on build).
• MaxConnectedAdmins – Extra admin slots when the server is full.
• SaveName – Folder name under Saves to load (links to your world).
• ListOnSteam, ListOnEOS – Whether the server appears in public lists.
• Password – Optional server password for private access.
• Rcon block – Remote console access (port, password, enabled flag).

Sample trimmed block:

{

  “Name”: “RedSwitches V Rising”,

  “Description”: “PvE co-op with raid arenas.”,

  “Port”: 27015,

  “QueryPort”: 27016,

  “MaxConnectedUsers”: 40,

  “MaxConnectedAdmins”: 3,

  “SaveName”: “world1”,

  “ListOnSteam”: true,

  “ListOnEOS”: true,

  “Password”: “”,

  “Rcon”: {

    “Enabled”: true,

    “Password”: “ChangeThisNow”,

    “Port”: 25575

  }

}

Think of this file as your identity and plumbing: it links a save, a name, and a couple of ports into one running server.

ServerGameSettings.json – Rules, PVE/PVP, Raids

ServerGameSettings.json controls how your world behaves. The official docs list each field, its type, and allowed ranges.

Key areas:

• Difficulty/progression
  • The current settings model uses named difficulty presets such as Difficulty_Easy, Difficulty_Normal, and Difficulty_Brutal, rather than relying on old numeric shorthand.
  • You tune how punishing bosses and enemies feel.
• Mode and PvP
  • GameModeType – PvE, PvP, Merciless.
  • PvPProtectionMode – early protection behaviour.
  • ClanSize – maximum players per clan.
• Raids and castle damage
  • CastleDamageMode – Never, Always, or TimeRestricted.
  • PlayerDamageMode – same idea, for player vs player damage.
  • SiegeWeaponHealth – health tier for golems.
  • Time windows at the bottom of the file define raid and PvP hours in local server time.
• Economy and grind
  • Resource yield multipliers.
  • Craft and refinement cost multipliers.
  • Death drop rules (keep gear, drop inventory, full drop).

Best way to start:

1. Open VRisingServer_Data/StreamingAssets/GameSettingPresets/.
2. Pick a preset close to your goal, such as StandardPvE.json or StandardPvP.json.
3. Copy that file into save-data/Settings/ as ServerGameSettings.json.
4. Edit small parts at a time, then restart and test.

Treat presets as “known good” baselines. You adjust them in small steps instead of building a ruleset from scratch.

Admin, Ban, and Whitelist Files

V Rising uses simple text lists for admins and bans. The exact path can vary by host, but on most installs, you will see them either under:

• VRisingServer_Data/StreamingAssets/Settings/
• or your save-data/Settings/ folder.

Main files:

• adminlist.txt – One SteamID64 per line.
• banlist.txt – Same idea, one SteamID64 per line.

To promote yourself:

1. Grab your SteamID64 from your Steam profile (use any web-based SteamID finder).
2. Add it to adminlist.txt on its own line.
3. Join the server, open the console with ~, and type adminauth.
4. If needed, recheck the file path under your persistent settings folder.

You now have access to admin commands such as kicking players, spawning items, or gathering everyone for an event.

If you want a “whitelist only” server, you can:

• Keep a short adminlist.txt for staff.
• Turn off public listing in ServerHostSettings.json.
• Use a password and share it only with people you trust.

Ports, Firewalls, and “V Rising Dedicated Server Not Showing Up”

Most “v rising dedicated server not showing up” problems are not magic. They come down to ports, firewalls, or filters. Fix those three, and your server usually appears in the list within a few minutes.

Required Ports and Protocols

Open these ports on the machine and on the router that sits in front of it:

• Game port UDP – Use the value configured in ServerHostSettings.json.
• Query port UDP – Use the value configured in ServerHostSettings.json.
• Current official example values: 27015 UDP for game traffic and 27016 UDP for the query port.
• 25575 TCP – Common RCON port, only if you enable RCON.

Some guides also suggest opening 27031–27036 UDP for Steam’s backend. That depends on your router and host, but it can help if you still do not see your server after everything else checks out.

You can change the game and query ports in ServerHostSettings.json if another service already uses them, but keep them paired and documented.

Windows Firewall Rules

On Windows, you need rules that allow traffic in and sometimes out on the ports above.

You can do this with the GUI:

1. Open Windows Defender Firewall with Advanced Security.
2. Create new Inbound Rule → Port.
3. Select UDP, then enter the game and query ports you actually configured for the server. If you are using the current official example values, enter 27015, 27016.
4. Allow the connection on all profiles (Domain, Private, Public).
5. Give the rule a clear name like V Rising UDP.
6. Repeat for TCP if you use RCON.

Or use PowerShell / netsh if you prefer scripts, like the creators of several video guides do. The goal is the same: make sure Windows does not drop traffic meant for your V Rising host server.

Router Port Forwarding Examples

Firewall rules cover your local machine. Port forwarding tells the router where to send traffic that hits your public IP.

Typical steps:

1. On the server box, open Command Prompt and run ipconfig.
2. Note the IPv4 Address, usually 192.168.x.y.
3. Log in to your router’s admin panel (often 192.168.0.1 or 192.168.1.1).
4. Find the Port Forwarding or NAT section.
5. Create rules like:
   • External Port: 27015–27016
   • Internal Port: 27015–27016
   • Protocol: UDP
   • Internal IP: the IPv4 address from step 2.
6. Make sure the same configured game and query ports are forwarded on the router and allowed in the firewall.

LAN vs Internet:

• If your friends sit on the same network, they can usually join via the server browser or by using your local IP.
• Players outside your home need the public IP + port, and port forwarding must work or they will never see the server.

Debugging “Server Not Showing Up”

Work through this checklist in order:

• Is the server actually running?
  • Check the console window or logs. Look for “Game Server Ready” or similar messages.
• Are ports open on Windows?
  • Temporarily turn off the Windows firewall as a test.
  • If the server appears, your rules were wrong or missing.
• Is port forwarding correct?
  • Double-check that the router forwards to the right internal IP.
  • Make sure the port numbers match your ServerHostSettings.json.
• Are listing flags enabled?
  • ListOnSteam and ListOnEOS should be true for a public server.
• Is the browser filtered?
  • Clear all filters in the server list UI.
  • Search by full server name, not partial fragments.

If you still cannot see it, try a direct connect:

• From your own PC: 127.0.0.1:<gamePort> if the client and server share one machine.
• From another machine on your LAN: your local server IP:<gamePort>.
• From outside: your public IP:<gamePort>, once you confirm that the port is open with an external port checker.

If direct connect works but the browser does not, the issue sits with listing flags or Steam/EOS, not your core network path.

Running a True V Rising Private Server

Sometimes you do not want random players. You just want a v rising private server for your group, with no server browser drama and no strangers camping your bosses. That is a simple switch once your base setup works.

Hide Your Server from Public Lists

In ServerHostSettings.json, flip the listing flags:

“ListOnSteam”: false,

“ListOnEOS”: false

This keeps your v rising host server out of public search results on both Steam and EOS, while still letting players connect by IP.

Combine that with a strong password:

“Password”: “Use-A-Real-Password-Here”

That gives you two layers:

• Nobody discovers you by accident.
• Even people who guess your IP cannot walk in without the password.

Direct Connect Flow for Friends

Once the world runs, share a short connection recipe with your group:

• If they sit on the same LAN:
  • Give them the server’s local IP plus your configured game port, for example 192.168.x.y:<gamePort>.
• If they join from outside your home:
  • Give them your public IP plus your configured game port, for example your.public.ip:<gamePort>.
  • Confirm port forwarding works first.

Inside V Rising they can:

1. Go to Play → Online Play.
2. Use the Direct Connect option or add the server via Steam’s View → Game Servers menu with the same IP and port.

You keep full control over who joins without relying on in-game search.

When RedSwitches Still Makes Sense for a “Private” World

Even if you only play with friends, a home server is not always enough:

• You stream and want viewers from other regions to join without ugly ping spikes.
• You run heavy mods, and your desktop struggles when you both play and host.
• Your clan wants a permanent home that stays online when you shut your PC down.

In those cases, moving your V Rising dedicated server hosting to bare metal at RedSwitches gives you:

• A fixed server in a region close to your core players.
• Strong single-thread CPU and NVMe storage for big castles and busy nights.
• High-bandwidth links and DDoS protection that home ISPs rarely match.

You still keep all the control you learned here: same JSON files, same ports, same rules. You just run them on hardware built to keep your vampire world alive 24/7.

Advanced Management – RCON, Backups, Updates, and Wipes

RCON Setup and Common Uses

RCON lets you manage your V Rising server without logging into the game.

Enable it in ServerHostSettings.json:

“Rcon”: {

  “Enabled”: true,

  “Password”: “ChangeThisPassword”,

  “Port”: 25575

}

Then:

• Open the RCON port on your firewall and router.
• Use a simple RCON client, point it at IP:RconPort, and log in with the password.

Typical RCON use cases:

• Broadcast restart warnings.
• Announce maintenance windows.
• Check version and time information.
• Issue controlled shutdown or restart-related commands.
• RCON support exists, but the currently documented command set is limited, so do not treat it as a full in-game admin replacement.

RCON keeps you in control even when you are not in-game.

Backup Strategy and World Migration

Your world lives under the save-data path you set in the start script. Inside you will see:

• <PersistentDataPath>/Saves/… – world data.
• Settings/ – server config overrides.

Safe backup pattern:

• Stop the server.
• Zip or copy the world folder under <PersistentDataPath>/Saves/ that matches your SaveName.
• Copy the Settings folder alongside it.
• Store backups on another disk or cloud storage.

To move a world to a new host (or to RedSwitches):

• Install the server and run it once.
• Copy the matching world folder from <PersistentDataPath>/Saves/ and the Settings folder to the new machine.
• Make sure -saveName in your start script matches that folder name.
• Start the server and test from a client before inviting players.

Safe Updates with SteamCMD or Steam Tools

Every update follows the same pattern:

1. Announce a restart window to players.
2. Stop the server cleanly.
3. Take a quick backup of Saves and Settings.
4. Run the update:
   • Steam Tools build: let Steam update the “V Rising Dedicated Server” app.

SteamCMD build:

steamcmd +login anonymous +force_install_dir ./VRisingServer +app_update 1829350 validate +quit

1. Start the server.
2. Join yourself and check that the world loads and players can connect.

Treat every patch like a small change window, not a guess.

Controlled Wipes and Seasons

PvP servers often run on “seasons” with planned wipes. Wipes keep progression fair and prevent old clans from owning every good spot.

Simple wipe process:

• Pick a cadence (for example, 4–8 weeks for busy PvP).
• Before wipe day, archive the matching world folder from <PersistentDataPath>/Saves/ into a dated folder.
• Create a new SaveName in your start script for the fresh season.
• Reset adminlist.txt and rules if needed.

Communicate wipes clearly:

• Add dates to your Discord and server description.
• Use RCON broadcasts in the final week.
• Tell players what carries over (rules, mods, house RP) and what resets (world, progression, stash).

Planned wipes feel fair. Surprise wipes kill trust.

Performance Tuning and Best Practices

Tick Rate, Player Caps, and CPU Load

V Rising servers expose a “ServerFPS” or tick rate setting in ServerHostSettings.json. A higher tick rate means more frequent updates, but more CPU use.

Safe starting points:

• Small private world (2–8 players):
  • Tick rate: 20–30.
  • Max players: 10–12.
• Busy co-op / light PvP (10–30 players):
  • Tick rate: 30.
  • Max players: 30.
• Raid-heavy PvP (30–60 players) on strong CPUs:
  • Tick rate: 30–40.
  • Max players: 40–50.

Watch CPU usage during fights and castle sieges. If cores sit near 100%, lower tick rate or player cap, or move to stronger hardware.

Castle Limits, Servants, and Heavy Features

Every extra castle and servant adds pathfinding, AI, and physics work. That load sits on your CPU, not your GPU.

To keep the world smooth:

• Cap floors per castle.
• Limit servants per player or per clan.
• Discourage giant “city” builds on low-end home PCs.
• Use stricter limits on modded servers with extra systems or loot.

On powerful dedicated machines, you can relax these limits. On mid-range home rigs, they decide whether raids feel responsive or sluggish.

Logs, Monitoring, and Restarts

Treat your V Rising dedicated server like any other long-running service.

Good hygiene looks like this:

• Schedule a daily or every-other-day restart during off-hours.
• Check the latest log file after big fights or crashes.
• Watch CPU, RAM, and disk activity with basic tools (top, Task Manager, or your provider’s panel).
• Look for patterns: spikes at raid hours, memory growth over days, repeated errors in console logs.

You do not need a full monitoring stack to spot trouble. A few minutes of log reading per week already puts you ahead of most admins.

Signs You Need Better Hardware

At some point, tuning is not enough. The world has outgrown the box.

Red flags:

• Players report lag spikes during large raids or Rift events while their ping stays normal.
• CPU cores peg at 90–100% whenever clans clash or bosses spawn.
• People time out during saves or world events.
• You keep lowering limits (floors, servants, player cap) just to stay stable.

When these show up together, it is time to move from a home PC or small VPS to true v rising dedicated server hosting on bare metal.

Why Run V Rising on Dedicated Bare Metal with RedSwitches

V Rising is a CPU-heavy, tick-based game. Stable raids and big castles need strong single-thread performance, fast disks, and clean bandwidth. Shared VPS nodes and slot-based game panels struggle once your world gets busy.

Dedicated server with RedSwitches gives you:

• High-clock CPUs that keep tick rate stable during peak raids.
• NVMe storage, so autosaves and backups do not freeze combat.
• 10 Gbps and 25 Gbps ports with real DDoS protection and unmetered bandwidth for public servers.
• Full root access so you control every setting, mod, and restart window.

Example builds:

• Small clan server (up to ~20 players):
  • 6–8 core CPU at high clock, 32GB RAM, 1TB NVMe.
• Busy PvP realm (40–60 players, raids, mods):
  • 12–16 core CPU with strong single-core speed, 64–128GB RAM, mirrored NVMe, 10 Gbps or 25 Gbps link.

Moving your world is simple:

1. Order a server with specs that match your player cap.
2. Install the V Rising server and run it once.
3. Copy your Saves and Settings to the new machine.
4. Update -saveName, IP, and ports in your start script.

You keep control over rules, wipes, and the community. We keep the hardware and network steady so your vampires can focus on winning the night.

FAQs

Q. What is a V Rising dedicated server vs a private game?

A private game runs on your PC only while you play, and the world shuts down when you leave. A V Rising dedicated server is a separate server process that keeps the world online 24/7, stores all save data, and enforces your custom settings for anyone who joins.

Q. How to set up a V Rising dedicated server step-by-step?

Install V Rising Dedicated Server from Steam (or via SteamCMD), run the example start script once to generate config files, then copy the configs into the save-data/Settings folder. Edit ServerHostSettings.json and ServerGameSettings.json, open the required ports on your firewall and router, restart the server, and join it from Play → Online → Show all servers or by direct IP.

Q. Can I run a V Rising dedicated server on Linux?

Yes. You install the server with SteamCMD on Linux and run VRisingServer.exe under Wine (often wrapped with xvfb-run on headless hosts). Many admins also use Docker images that bundle SteamCMD, Wine, and the server in one container.

Q. Why is my V Rising dedicated server not showing up in the list?

Typical causes are closed ports, the server not finishing startup, or listing flags set to false. Check that the server is running, make sure your configured game and query ports are open and forwarded, and confirm that ListOnSteam and ListOnEOS are set to true for a public server. Then clear filters in the in-game browser and wait a few minutes.

Q. What ports does a V Rising server need?

Use the game and query ports configured in ServerHostSettings.json. In the current official example values, that means 27015 UDP for game traffic and 27016 UDP for the query port. If you enable RCON, you also need to allow its TCP port, commonly 25575. Your firewall and router forwarding should match the exact values you configured.

Q. Can I host V Rising for PS5 players?

V Rising has separate current dedicated server instructions for PS5. Use the PS5-specific server branch and settings rather than assuming the standard PC dedicated server setup applies unchanged.

Q. When should I move to a dedicated server host like RedSwitches?

You should move when raids lag, players time out during peak hours, or your home PC needs to stay on all day. If you run 20+ players, heavy PvP, or modded worlds, a dedicated bare metal with a strong CPU, NVMe storage, and real DDoS protection will give your community a more stable experience.