To install mods on a Windows V Rising dedicated server, place BepInExPack V Rising in the server’s game-root folder, launch the server once so BepInEx creates its directories and log, then copy compatible mod files into BepInEx/plugins. Restart the server and use BepInEx/LogOutput.log to diagnose failures. Whether players must install anything depends on each mod’s Thunderstore tags: server-only packages stay on the server, while client and client-server packages can require matching files on every player’s computer.
The procedure is different for a host-and-play session, a rented server, and Linux. The guide below separates those cases so you do not put the loader in the wrong process or assume that a server installation automatically covers clients.
What do I need before installing V Rising mods?
Start with a working V Rising server and a clear understanding of which process you are modifying. A separately installed dedicated server has its own game root, while a host-and-play session launches a bundled server as a separate process. The files and loader must reach the process that actually hosts the world.
- A V Rising Dedicated Server installation. Stunlock Studios’ hosting guide identifies the dedicated-server application; launching it once creates a server with default settings.
- BepInExPack V Rising. Obtain the V Rising package from Thunderstore and extract it outside the game directory before moving its contents into the server root.
- Compatible mod files. Read each package page for dependencies, supported game or loader versions, and whether it is tagged
ServerMods,ClientMods, orClientServer. - Access to the server root. On your own Windows machine this is normally the folder named
VRisingDedicatedServer. A rented host must provide FTP or a file manager that can reach that folder. - A way to inspect logs. A successful first launch creates
BepInEx/LogOutput.log, which is the first place to look when a plugin does not load.
Back up the world and server configuration before adding or replacing plugins. A mod can change gameplay or save data, and a backup gives you a recovery path if a package is incompatible.
How do I install BepInEx on a Windows dedicated server?
Install the loader before installing any plugins. The important detail is location: BepInEx belongs directly in the dedicated server’s game root, not in a nested archive directory.
- Install and launch the official server once. Run the V Rising Dedicated Server application and let it create its normal files. Stop it after the initial startup has completed.
- Extract the BepInEx archive outside the game directory. The package’s manual instruction is: “Extract the archive into a folder. Do not extract into the game folder.” This prevents an extra archive folder from being left in the wrong place.
- Open the package folder. Inside the extracted
BepInExPack_V_Risingdirectory, select the package contents rather than copying only the outer folder. - Move those contents into the server root. For a normal Windows dedicated server, that root is typically
VRisingDedicatedServer. The root should contain the BepInEx loader files alongside the server’s existing executable and data. - Boot the server again. Give BepInEx time to initialize and generate its folders. A correct installation produces BepInEx output and creates
BepInEx/LogOutput.log. - Stop the server after the first successful initialization. Plugins should be copied while the process is stopped so files are not partially read or locked during upload.
How can I verify that BepInEx is in the right folder?
Look for a BepInEx directory directly under the server’s game root after the first boot. If you instead see a path such as VRisingDedicatedServer/BepInExPack_V_Rising/BepInEx, the archive was copied one level too deep. Move the contents of BepInExPack_V_Rising up into VRisingDedicatedServer, then start the server again.
The first launch is a deliberate test, not an optional step. BepInEx must create its own folders and log before you can tell whether a later plugin problem is caused by the mod or by the loader placement.
Where do V Rising server mods go?
After BepInEx has initialized, place server-compatible plugin files in the BepInEx/plugins directory under the same server root. Most packages provide a DLL and may include additional files or folders; follow the package’s readme for anything beyond the DLL.
| Item | Correct location or action | Why it matters |
|---|---|---|
| BepInEx loader | Contents of BepInExPack_V_Rising moved into VRisingDedicatedServer |
The loader must start with the dedicated-server process. |
| Plugin DLL | VRisingDedicatedServer/BepInEx/plugins |
BepInEx scans this directory for plugins. |
| Required dependency | The location specified by the mod’s package instructions, usually alongside the plugin files | A plugin can fail if a dependency is absent even when its own DLL is present. |
| Generated diagnostic log | VRisingDedicatedServer/BepInEx/LogOutput.log |
Shows whether BepInEx and individual plugins initialized. |
Do not leave a plugin compressed in a ZIP file and do not invent a folder structure based on the archive’s name. Open the package, read its instructions, and copy the files into the paths it specifies. Some packages include configuration files, asset bundles, or dependency DLLs that must remain in a particular subfolder.
What is the safest order for adding several mods?
Add one package, start the server, and inspect the log before adding the next when you are setting up a new server. This is not required by BepInEx, but it gives you a clear cause-and-effect trail: if the log changes immediately after one package is added, you know which package to investigate. Once the base installation is known to work, you can upload a tested set together.
How do I choose server-compatible mods and dependencies?
Thunderstore distinguishes packages with ServerMods, ClientMods, and ClientServer tags. Use those labels as a starting point, then read the package page because a tag does not replace the dependency list or installation notes.
| Thunderstore tag | Typical placement | Player impact |
|---|---|---|
ServerMods |
Install on the dedicated server in BepInEx/plugins. |
Usually no client copy is needed, although the package page remains authoritative. |
ClientMods |
Install on each player’s game as instructed by the package. | A server-only installation will not provide the client-side code. |
ClientServer |
Install the required release on the server and on clients. | Players may be unable to connect or use the feature unless versions match. |
Check dependencies before copying the main DLL. A package can require another plugin, a shared library, or a specific release. Install every required component in the location named by the package, then restart the server so BepInEx loads the complete set together.
Never assume that a mod marked for one side is harmless on the other. A package’s readme and tags describe its intended placement; using a client-only DLL on a dedicated server can produce load errors, while omitting a required server component can make a client-side feature appear broken.
Do players need to install the same V Rising mods?
Sometimes. Server-only mods generally remain on the server, but client and client-server packages can require players to install files themselves. One package rule explicitly requires the same release on the dedicated server and every connecting player, so check the individual package instead of relying on the server installation alone.
Use a simple compatibility checklist
- Read the package’s client/server tag.
- Read its dependency list on Thunderstore.
- Note whether the instructions demand an identical release on server and client.
- Give players the exact package version and any required companion files.
- Keep the server and client copies synchronized after updates or rollbacks.
If only some players can connect, compare their installed packages and versions with the server’s list before changing unrelated settings. A mismatch is especially likely when a package is tagged ClientServer or explicitly says that the same release must be installed everywhere.
How do I install mods for a host-and-play session?
Host-and-play is not the same as running a separately installed dedicated server. The game launches its bundled server as a separate process, and that process does not inherit your client mods by default.
Use ServerLaunchFix for this bundled host process. It copies the mod loader to the bundled server and creates a BepInEx_Server directory for server state. Install and configure the fix according to its package instructions, then place server plugins in the BepInEx server location it creates. Your client-side plugins still belong to the client installation when a package requires them.
This exception does not change the dedicated-server procedure. If you installed the V Rising Dedicated Server separately, put BepInEx in that installation’s VRisingDedicatedServer root and use its BepInEx/plugins directory. Do not copy the host-and-play workaround into a separate dedicated server unless its documentation specifically calls for it.
How do I install mods on a rented V Rising server?
A managed host normally gives you FTP access or a web file manager rather than local access to the machine. The workflow is the same, but you must confirm that the provider permits BepInEx and exposes the server root before purchasing or uploading files.
- Confirm access and support. Ask whether BepInEx is allowed and whether FTP or the file manager can reach the V Rising server’s game root.
- Connect by FTP or open the file manager. Locate the folder containing the dedicated-server files, not a general account or backup directory.
- Upload BepInEx correctly. Extract the package outside the game directory first, then upload the contents of
BepInExPack_V_Risinginto the server root. - Start the server once. Let BepInEx create its folders and
LogOutput.log. Start the client once as well when the package instructions require client initialization. - Stop the server. Upload the desired plugins and dependencies into
BepInEx/pluginswhile the process is stopped. - Restart and inspect the log. Confirm that the plugins initialize before inviting players. If a package requires client files, distribute the same release to players.
File managers can hide extensions or place uploads inside an extra directory. After uploading, browse the remote tree and verify that the loader is directly under the game root and that plugin DLLs are directly under BepInEx/plugins or the subfolder specified by the package.
Can I run a modded V Rising dedicated server on Linux?
There is no official Linux dedicated-server build of V Rising. Linux operation therefore requires running the Windows server through Wine in a Docker container, and the container may need a WINEDLLOVERRIDES setting. Treat this as a compatibility project rather than a normal native installation.
The Windows folder rules still describe where BepInEx and plugins must end up inside the emulated server installation, but the container, Wine version, environment variables, storage mounts, and startup process determine whether the server can launch. Document the exact Wine and container configuration you use so it can be reproduced after an image update or migration.
If you need a predictable first setup, validate the dedicated server and BepInEx on Windows before troubleshooting Linux-specific issues. On Linux, a missing log can indicate a container or Wine startup problem rather than a bad plugin, so check the container’s process output as well as BepInEx/LogOutput.log.
Why is my V Rising server not loading mods?
Most failures can be narrowed down by checking the path, the first-launch log, package compatibility, and dependencies in that order. Make one correction at a time and restart the server after each change.
| Symptom | Likely cause | What to check |
|---|---|---|
| No BepInEx folder or log | The loader is in the wrong directory, still nested inside the archive folder, or the wrong process was launched. | Move the contents of BepInExPack_V_Rising into the dedicated-server root and boot that server once. |
| BepInEx starts but a plugin is absent from the log | The DLL is outside the plugins directory or the package uses a different path. | Confirm BepInEx/plugins, file extensions, and the package readme. |
| A plugin reports a missing assembly or dependency | A required companion package was not installed or is in the wrong location. | Re-read the dependency list and install every required file before restarting. |
| Server starts but players cannot use a feature | The package needs client files or matching versions. | Check the client/server tag and install the exact required release on each client. |
| Server fails after adding a package | The package is incompatible with the current game, loader, or another plugin. | Stop the server, remove the newly added package, compare its stated requirements, and review BepInEx/LogOutput.log. |
| Host-and-play has no server mods | The bundled server is a separate process and did not receive the client loader. | Use ServerLaunchFix and its BepInEx_Server directory rather than treating the session as a dedicated-server install. |
Keep the complete log from the failed boot. The first error is often more useful than the final shutdown message, and a package author or host support team can act on the exact exception and file path.
How should I update or remove V Rising mods?
Plan updates as a controlled file change. Record the current package versions, back up the world and server settings, stop the server, and replace or remove the plugin files according to the package instructions. Start the server and inspect the log before allowing players to reconnect.
- Write down the installed package names, releases, and dependencies.
- Back up the world and configuration files.
- Stop the dedicated server or rented-server process.
- Remove the old DLL and any files the package says should be replaced; do not delete shared dependencies that other plugins still need.
- Upload the new release and its required dependencies.
- Start the server and verify initialization in
BepInEx/LogOutput.log. - For client-server packages, distribute the same release to every player before they join.
If an update prevents startup, restore the previous plugin set from your backup and confirm that the server works before attempting another version. Keep a separate record for host-and-play installations because their server-side files live under BepInEx_Server, not necessarily in the normal client plugin directory.
What is the final pre-launch checklist?
- The official V Rising Dedicated Server launches without mods.
- BepInEx contents are directly in
VRisingDedicatedServer, not insideBepInExPack_V_Rising. - The first boot created
BepInExandLogOutput.log. - Each plugin is in
BepInEx/pluginsor the path specified by its instructions. - All listed dependencies are installed.
- Every package’s
ServerMods,ClientMods, orClientServerrequirement is understood. - Players have matching client files where required.
- The server was restarted after file placement, and the log contains no unresolved load errors.
- A current world and configuration backup exists.
Frequently Asked Questions
Can I install a V Rising mod while the server is running?
Stop the server before uploading, replacing, or removing plugin files. A stopped process avoids locked or partially read files and makes the next log represent one complete plugin set.
What should I back up before changing mods?
Back up the world data and server configuration, and keep a copy of the previous plugin files with their versions recorded. That lets you restore a known-working combination if an update changes behavior or prevents startup.
Why does a mod work for the host but not for another player?
The package may be client-side or require identical client-server releases. Compare the player’s installed package and dependency versions with the server’s instructions rather than reinstalling the server loader.
Can I move my modded server to another Windows machine?
Copy the dedicated-server installation together with its BepInEx directory, plugin files, dependencies, and server data, then launch the server once on the new machine and inspect the generated log. Recheck paths after the move because an extra parent folder can leave BepInEx nested incorrectly.