V Rising BepInEx Server Hosting

Plugins add overhead to a game that already likes memory. Six gigabytes at $15.00 handles a small clan comfortably, 8 GB at $20.00 is the tier most modded servers settle on, and 16 GB at $40.00 with 5 cores suits a busy public world running a long plugin list alongside several large castles.

It depends on the plugin. Server-authoritative mods that adjust drop rates, decay, or admin commands run entirely on our side, and clients connect normally. Anything drawing interface elements, adding map markers, or replacing models needs the matching version locally. Publish your plugin list with version numbers, and rejected connections stop being a mystery.

Take a manual backup, then use the one-click version changer to hold the server on the build your plugins support while authors update. A rollback leaves the save itself untouched, and automatic daily backups keep ten rolling copies regardless. Once the plugin set catches up, switch forward and watch the console for load errors on that first start.

FSH does not meter slots, so the number comes from the connected-user limit in your own settings file. Most operators run somewhere between ten and forty depending on map pressure and how much castle space is left. Plugins that add territory management or extra hearts affect how many people the world realistically supports more than the raw cap does.

Yes. Stop the server, upload your save directory through the file manager or SFTP, and copy your settings files alongside it so the world loads with identical rules. Put your plugins and their config files in place before the first start so nothing regenerates defaults over your tuning, then check the console once and the clan logs into the same castles.