Want mods on your Valheim server without the grind? Import your Thunderstore/r2modman profile in minutes using a .r2z
file. Follow along and let BepInEx load every plugin server-side.
Prerequisites
- Access to your Oxygenserv panel (login and password)
- Thunderstore Mod Manager or r2modman installed on your PC
- Valheim profile exported as a
.r2z
file - Valheim server installed on Oxygenserv and stopped
- BepInEx (Valheim) enabled/present on the server
- Valheim client using the same modpack to join
- Optional: SFTP (FileZilla/WinSCP) if you prefer FTP upload
Step-by-step
-
Export your modpack from Thunderstore/r2modman
Open Thunderstore Mod Manager (or r2modman) and select your Valheim profile. Click “Settings” then “Export profile as a file”. If available, include dependencies, and save the.r2z
file (e.g.,MyValheimPack.r2z
). This archive contains the server-side plugins and configs. If you use multiple profiles, export the one you actually play with. -
Upload the .r2z file to the server
Log in to your Oxygenserv panel and open “Files”. Upload the.r2z
to the server’s root folder (same level asstart_server.sh
orvalheim_server.x86_64
). You should see it appear in the file list (e.g.,MyValheimPack.r2z
). Via SFTP, drop it in the server root so the installer can detect it. If upload fails, check file size and your connection. -
Enable/install BepInEx for Valheim
In the panel, go to the “Startup” or “Mods” tab. Toggle BepInEx (Valheim) to Enabled or click “Install BepInExPack”. Save, start the server once to generate folders, then stop it. You should now seeBepInEx/
withBepInEx/plugins
andBepInEx/config
. If BepInEx doesn’t show in logs, re-enable it and restart. -
Install the modpack (.r2z) with the built-in importer
Open the “Mods” or “Startup” tab > “R2Z Import” section. Depending on the UI, pick your file from a dropdown or paste the exact filename (e.g.,MyValheimPack.r2z
). Some installers ask for the name without extension — then enterMyValheimPack
(without.r2z
). Click “Install”: mods go toBepInEx/plugins
and configs toBepInEx/config
. If you see “Invalid archive” or nothing happens, re-export your profile and rename the file with simple ASCII characters. -
Start and verify everything works
Click “Start”. Watch the console: you should see BepInEx lines (e.g., “BepInEx 5.x
loaded”) and plugins being loaded. In the file manager, confirmBepInEx/plugins
contains your mods. Join from your client using the same Thunderstore/r2modman profile. If you get a “mod mismatch” or crashes, align versions and remove the last-added mod.
Tips & optimization
– Keep it reasonable: 20–60 mods is a sweet spot. Too many = longer loads and more conflicts.
– Back up before imports: copy BepInEx/
and your world. It saves headaches.
– Memory: 4–6 GB RAM for modded servers with 10+ players. Monitor RAM/CPU in the panel and scale up if needed.
– Update via profile: re-export a clean .r2z
when you add/remove mods, then reinstall. Avoid manual plugin mixing.
– Consider “ServerSync” when available: it syncs BepInEx/config
to players and reduces client-side errors.
FAQ
Do players need to install the mods client-side too?
Yes. Most Valheim mods require both client and server. Easiest fix: have players use the same Thunderstore/r2modman profile you exported. Launch the game from that profile.
BepInEx isn’t loading on the server, what now?
Make sure BepInEx (Valheim) is Enabled in Startup/Mods, restart the server, and check that BepInEx/
exists. If logs show nothing, reinstall “BepInExPack (Valheim)”, then start and stop once to generate folders before installing mods.
.r2z import fails (“Invalid archive”) or no mods appear
Re-export using “Export profile as a file” (don’t zip it yourself). Rename to simple ASCII (e.g., VhPack.r2z
), upload to the root folder, and try again. Also make sure the server is stopped during installation.
Your Valheim server is now modded and stable. Keep iterating: export, import, test. Fast, clean, controlled.