V Rising

V Rising

Nicht genug Bewertungen
UNRAID Private Server Guide
Von [P$] McCloud
This is a well-documented guide for running a private V Rising server on the UNRAID platform. This guide will touch on the initial Docker setup, server configuration and game settings configuration.
   
Preis verleihen
Favorisieren
Favorisiert
Entfernen
Introduction

This guide will walk you through the steps required to set up a V Rising server on UNRAID. UNRAID is a popular operating system for managing virtualization and Docker containers, making it ideal for hosting game servers.

Requirements
  • UNRAID server with Docker installed.
  • Access to the V Rising server files.
  • Basic understanding of Docker and server management.
  • Basic understanding of routing and port forwarding.
Installing SteamCMD and V Rising Server (Docker)
Enable Docker
Your UNRAID server instance should come pre-packaged with Docker functionality. If you still need to configure your basic Docker settings, please reference the official Docker knowledgebase from UNRAID.[docs.unraid.net]

Install Docker Image for V Rising
The docker image we will be using has been graciously provided by ich777. This Docker image will automatically install SteamCMD alongside the V Rising server files. Here is the official Docker Hub page of the project for reference.[hub.docker.com]

To install the image, navigate to the Apps tab in your UNRAID server navigation menu. You will be presented with the Community Apps page; enter V Rising in the search bar.



In the search results, locate the Docker image provided by ich777 and select the installation option.
Configuring V Rising Docker Image Template
After selecting the Docker image from the Community Apps sections of your UNRAID server, you will be prompted to configure your instance of the Docker image.


The Docker image template should automatically fill in the appropriate SteamCMD and ServerFile directories (both should be located in your appdata directory). The appropriate GAME_ID parameter should be pre-filled by the template.

The Settings
The required parameters are marked by red asterisks. These are the settings that are required to successfully launch the server.

SERVER_NAME
Enter the desired name of your server. This is the name that will appear when others search for you in the in-game server list.

WORLD_NAME
Enter a unique name for your world. This will be used to differentiate game save data based on the map generation.

UDP - Game Ports
These are the required ports for discovery and connection to the server. These can be adjusted based on your own network requirements. Most people can leave the default ports.

These ports will need to be forwarded to your server in your router before anyone else will be able to connect to you

Click DONE to submit the template for installation.
Configuring Server and Game Settings
Modifying server and game settings is done via changes to ServerHostSettings.json and ServerGameSettings.json, respectively. These files are located in your installation directory.

DOCKER CONTAINER MUST BE STOPPED BEFORE MODIFYING THESE SETTINGS

Server Settings
{ "Name": "TEST SERVER", "Description": "Test server hosted by McCloud.", "Port": 9876, "QueryPort": 9877, "MaxConnectedUsers": 40, "MaxConnectedAdmins": 4, "ServerFps": 200, "SaveName": "testworld", "Password": "TEST", "Secure": true, "ListOnSteam": true, "ListOnEOS": true, "AutoSaveCount": 20, "AutoSaveInterval": 120, "CompressSaveFiles": true, "GameSettingsPreset": "", "GameDifficultyPreset": "", "AdminOnlyDebugEvents": true, "DisableDebugEvents": false, "API": { "Enabled": false }, "Rcon": { "Enabled": true, "Port": 25575, "Password": "ADMINPASSWORD" } }
Game Settings
{ "GameDifficulty": 1, "GameModeType": "PvP", "CastleDamageMode": "Never", "SiegeWeaponHealth": "Normal", "PlayerDamageMode": "Always", "CastleHeartDamageMode": "CanBeDestroyedByPlayers", "PvPProtectionMode": "Medium", "DeathContainerPermission": "Anyone", "RelicSpawnType": "Unique", "CanLootEnemyContainers": true, "BloodBoundEquipment": true, "TeleportBoundItems": false, "BatBoundItems": false, "AllowGlobalChat": true, "AllWaypointsUnlocked": false, "FreeCastleRaid": false, "FreeCastleClaim": false, "FreeCastleDestroy": false, "InactivityKillEnabled": true, "InactivityKillTimeMin": 3600, "InactivityKillTimeMax": 604800, "InactivityKillSafeTimeAddition": 172800, "InactivityKillTimerMaxItemLevel": 84, "StartingProgressionLevel": 0, "DisableDisconnectedDeadEnabled": true, "DisableDisconnectedDeadTimer": 60, "DisconnectedSunImmunityTime": 300.0, "InventoryStacksModifier": 1.0, "DropTableModifier_General": 1.0, "DropTableModifier_Missions": 1.0, "MaterialYieldModifier_Global": 1.0, "BloodEssenceYieldModifier": 1.0, "JournalVBloodSourceUnitMaxDistance": 25.0, "PvPVampireRespawnModifier": 1.0, "CastleMinimumDistanceInFloors": 2, "ClanSize": 4, ... }

These settings can be modified to customize your server in whatever way you like. Here is a list of each parameter and what it changes in-game.[techraptor.net]
Updating Server Version
When a new V Rising patch is released, you can easily update your server to the latest version by simply restarting the docker container; it will pull the latest version from Steam on startup.