Rent and Set Up a V Rising Server – Vampire Guide

A V Rising Server is worth it if your group wants to run a permanently available world with controlled PvE or PvP rules. What matters is not having as many options as possible, but clean basic values: game mode, castle limits, siege times, admin access, backups, and a verifiable join test after every change.

Requirements

For a paid V Rising Server at game-serverhosting, plan for at least 4 GB RAM, as intended in the initial setup. You also need the SteamID64 of the admins, access to the server files or hosting panel, and a clear decision on whether the world should be more co-op, competitive PvP, or full-loot PvP.

The official server documentation from Stunlock Studios names two central configuration files for V Rising: ServerHostSettings.json for hosting values such as name, ports, password, and slots, and ServerGameSettings.json for game rules such as PvP, loot, castle rules, and progress. Stunlock also points out that local overrides should be used instead of the default files in the installation folder because default files can be overwritten during updates: documentation at github.com

If you already run other survival servers, the decisions are similar, but not identical. For a co-op focus, you can find comparable planning logic in the Rent and Set Up a Valheim Server – Co-op Guide 2026. For more conflict-oriented server rules, the Rent and Set Up a Rust Server – The Complete Guide is useful as a comparison.

Rent a V Rising Server

Order the Server

1. Go to game-serverhosting
2. Choose at least 4 GB RAM
3. The server is set up automatically

After provisioning, you should start the server once and stop it again. This usually fully initializes standard files, saves, and panel functions. Avoid changing JSON files while the server is running, because running processes can write configurations again when stopping.

Choose the Game Mode

PvE is the most stable choice for small groups that want to experience bosses, castle building, and progression without player raids. PvP needs clearer rules: when raiding is allowed, how large clans may be, how harsh the loss on death is, and how quickly a group should get back into the game after setbacks. You should only enable Full Loot if all fellow players explicitly want the consequences.

Important Settings

The gameplay rules are in ServerGameSettings.json. Keep existing valid values and only change the fields you really need. Small override files are easier to check than complete templates with hundreds of options.

{
  "GameModeType": "PvE",
  "CastleLimit": 2,
  "PlayerDamageMode": "Always",
  "CastleDamageMode": "TimeRestricted",
  "SiegeTimer": "18:00-23:00",
  "BloodBoundEquipment": true,
  "RelicSpawnType": "Unique"
}

GameModeType determines the basic mode. PlayerDamageMode and CastleDamageMode mainly affect PvP rules. BloodBoundEquipment reduces frustration because equipment remains bound on death if the server uses this rule. RelicSpawnType affects how relics are handled and should be set deliberately in competitive worlds.

Castle Limits

For PvE, two castles per player or clan are often comfortable because groups can use different regions. For PvP, a lower castle limit restricts fallback bases and reduces management effort. If your world is publicly accessible, document the castle rules before launch so later changes do not feel arbitrary.

Set Siege Timers Cleanly

A time window like 18:00-23:00 makes raids more predictable. Check your server's time zone and communicate the rule in the server description, Discord, or community note. Avoid vague wording like “evenings” when PvP is active. For small groups, a tighter window is usually fairer because nobody can defend their castle around the clock.

Admin Commands

Enable the admin console with adminlist add <steamid> and use:

adminauth         # Log in as admin
teleport <name>   # Teleport to player
give <item> <n>   # Give items
time set <stunde> # Set time

Only add people who should actually administer. Admin rights are not a convenience feature for normal players, but a tool for support cases, rule violations, lost characters, or tests after changes. After adding someone, check whether adminauth works in-game and whether admin commands were not accidentally granted to non-admins.

Join and Check the Result

1. Start V Rising → "Play Online"
2. "Search for server" or "Direct connect"
3. Enter IP and port

After first joining, check three things: the server name appears correctly, the selected mode behaves as planned, and admin rights work. For PvP rules, additionally test with two players whether player and castle damage match the selected mode. For PvE, a short test that no player damage is possible and the castle limits apply as expected is enough.

Troubleshooting

Server Does Not Appear in the List

First use direct connect with IP and port. If that works, the problem is more likely with listing, query port, or visibility. Check ServerHostSettings.json, firewall rules, and whether the server was restarted after the last change.

Changes from ServerGameSettings.json Do Not Apply

Stop the server, check the JSON syntax, and restart. Watch whether a preset or another override file is overwriting your values. The official Stunlock documentation describes that settings are loaded from defaults and local overrides; multiple sources can therefore lead to unexpected results.

Players Lose Too Much Equipment

Check BloodBoundEquipment and the death/loot rules. Especially in PvP Full Loot, loss is part of the mode. If your group prioritizes progress and boss fights, PvE or moderate PvP is usually more suitable.

Raids Happen at the Wrong Time

Check the SiegeTimer, the server time, and the communicated time zone. After changes, test not only server startup, but also the actual behavior in the relevant time window.

Checks, Limits, and a Safe Way Back

The guide “Rent and Set Up a V Rising Server – Vampire Guide” applies to the server type described in the article and the version status visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources can differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.

Before making changes to the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.

A successful single test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.

FAQ

How Much RAM Does a V Rising Server Need?

The initial value for this setup is at least 4 GB RAM. More demand can be caused by player count, world state, mods, or parallel services; you should not assume concrete performance values without measurement.

Should I Choose PvE or PvP?

Choose PvE for co-op, progress, and relaxed building. Choose PvP only if your group explicitly wants conflict, raids, and clear rules. Full Loot is the toughest variant.

Where Do I Change Castle Limits and Siege Times?

These values belong in ServerGameSettings.json. Stop the server before making the change, save valid JSON, and restart afterward.

How Do I Make Myself Admin?

Add your SteamID64 to the admin list or use the panel function. In-game, enable the console and log in as admin with adminauth.

Can I Switch from PvE to PvP Later?

Technically, you can change rules, but the switch strongly changes expectations for the world. Announce it beforehand, back up the savegame, and then check damage, castle rules, and loot behavior.