How to install mods on a V Rising server?

Ready to supercharge your V Rising server with mods? We’ll install BepInEx and your plugins step by step, clean and safe. In minutes, your Oxygenserv server will run your favorite features.

Prerequisites

• Access to the Oxygenserv panel (your login and password)
• V Rising server created and started at least once
• An SFTP client (e.g., FileZilla) or the panel “Files” tab
• BepInExPack_V_Rising (x64) downloaded locally
• Thunderstore Mod Manager (r2modman) to fetch mods easily
• 10–20 minutes to stop/start and verify logs

Detailed steps

1. Stop the server cleanly
   Log into your Oxygenserv panel and open your V Rising service. Go to the “Console” tab and click the red “Stop” button. Wait until logs stop scrolling and the process fully exits. If the button seems stuck, refresh the page and confirm the server PID is gone. Don’t proceed until it’s completely stopped.
2. Download the correct BepInEx for V Rising
   Grab BepInExPack_V_Rising from Thunderstore (architecture x64). Download the ZIP to your PC and extract it: you should see a BepInEx folder, plus winhttp.dll and doorstop_config.ini. Keep those ready to upload. Avoid generic BepInEx packs not tailored for V Rising. If you see a 32-bit pack, don’t use it.
3. Upload BepInEx to the server root
   In the Oxygenserv panel, open “Files” and navigate to the server root (where the executable is, e.g., VRisingServer.exe). Click “Upload” and drop the BepInEx folder plus winhttp.dll and doorstop_config.ini directly in the root. You should end up with /home/container/BepInEx/, /home/container/winhttp.dll, and /home/container/doorstop_config.ini. If you uploaded a ZIP, extract it on the server, then delete the ZIP. Without winhttp.dll at the root, BepInEx won’t inject.
4. Start once to generate BepInEx structure
   Go back to “Console” and click the green “Start” button. Watch the logs: you should see BepInEx 5.x - Initialized and Chainloader started. On first run, BepInEx creates /home/container/BepInEx/plugins and /home/container/BepInEx/config. If there’s no BepInEx mention, files are misplaced or winhttp.dll is missing. Stop again before continuing.
5. Fetch server-compatible mods
   On your PC, open Thunderstore Mod Manager (r2modman), pick the game “V Rising”, and create a profile. Go to “Get Mods”, pick a mod and confirm it’s server-friendly (check the description). Click “Download” and locate its .dll files (often under the profile’s BepInEx/plugins). If a mod requires dependencies (e.g., HookGenPatcher), download them too.
6. Install mods into BepInEx/plugins
   Back on Oxygenserv, open /home/container/BepInEx/plugins in the Files tab. Click “Upload” and send the mod .dll files (you can create one subfolder per mod to stay organized). Don’t upload raw ZIPs here: place the extracted .dll and any provided files. If the mod ships a patchers folder, put it in /home/container/BepInEx/patchers. Double-check you didn’t nest folders accidentally (e.g., plugins/plugins).
7. Configure your mods
   Open /home/container/BepInEx/config to tweak each mod’s .cfg. For example, enable a feature by adding or editing EnableFeature=true exactly like that. Click “Save” after each change. Some configs only appear after the first run with the mod installed—restart once if a file is missing. Keep copies of these .cfg files for easy rollback.
8. Restart and verify mods are loading
   Hit “Restart” and watch the console. You should see lines like [BepInEx] Loading [ModName] 1.2.3 for each plugin. Join the server and test the mod features (commands, messages, gameplay changes). If the server loops or crashes, remove the last added mod from BepInEx/plugins and try again. If players can’t join, they often must install the same client-side mod versions via Thunderstore.

Tips & optimization

– Add mods in small batches (2–3), test, repeat: you’ll spot bad actors fast.
– Freeze a stable pack: note exact versions and update one mod at a time.
– Back up your entire BepInEx folder before big changes.
– Need a quick off without uninstall? Rename a mod to .dll.disabled.
– Keep it lean: 10–20 well-picked mods beat a heavy 50+ pack for stability.
– Read startup logs every time: ERROR/EXCEPTION lines usually point to the faulty mod by name.

FAQ

The server starts but no mods load. What now?

Ensure winhttp.dll and doorstop_config.ini are in the server root (e.g., /home/container/) alongside the BepInEx folder. Check for BepInEx 5.x - Initialized in logs. If missing, re-upload BepInExPack_V_Rising (x64), stop, and start again. Don’t use 32-bit builds.

Players can’t join after adding a mod. Why?

Many mods require the same client and server versions. Ask players to install identical mods via Thunderstore Mod Manager. If it still fails, remove the last added mod from BepInEx/plugins, restart, and re-test. Logs usually show a clear incompatibility hint.

A mod mentions “patchers” or special dependencies. Where do they go?

Place patcher contents in /home/container/BepInEx/patchers. For dependencies (e.g., HookGenPatcher), follow the mod author’s instructions precisely. Missing dependencies can cause silent failures or console MissingMethodException errors.

You’re set to push your server to the next level. Move step by step, test often, and you’ll keep a stable, fun modded experience 24/7. Need help? We’ve got you.

Related articles

• How do I add mods to a Euro Truck Simulator 2 server?
• How do I install mods on a Palworld server?
• Installing Mods on a Satisfactory Server: A Guide