01Two machines, one mod list
r2modman Valheim profiles configure the machine you play on, and a profile export never contains world or character data. Valheim 1.0 moved worlds from a WorldName.db plus WorldName.fwl pair to a folder named after the world, so back up the whole world folder rather than individual files — a partial copy is rejected on load. Worlds and characters live under worlds_local and characters_local inside the Valheim folder, and the game’s main menu → Manage Saves shows each world and moves it between local storage and Steam Cloud, which is the only way to tell which of the two currently holds it. If your world runs on a dedicated server, that server keeps its own copy under its own worlds_local folder and its own set of packages, and the manager on your desktop cannot reach either. Start by deciding which packages belong on the client only, which must exist on the server, and which need to be on both at matching versions; community READMEs and the server's own rules are the reference. A successful local modded launch proves your client works. It says nothing about the server's packages, ports, or configuration.
02Verify the install path before anything else
Select Valheim, then open Settings → Directories and compare the detected directory with the folder Steam opens from right-click → Manage → Browse local files. Valheim installs commonly live in a second Steam library on another drive, and on Linux or a Steam Deck the Proton prefix adds another layer to check. Settle this before you install a single package. When the path is wrong, every symptom looks like a mod failure — no loader output, no in-game change — even though the profile itself is complete and correctly built.
03Back up worlds and characters first
World and character files are not part of a mod profile, so a profile export will not restore them. Copy the whole world folder out of worlds_local, and the .fch character files out of characters_local, before you install or remove content, building, inventory, or world-generation packages — Valheim 1.0 splits a world across many files in one folder, so a partial copy cannot be loaded. Both folders sit inside the Valheim save directory, which the game's main menu → Manage Saves opens for you; worlds kept in Steam Cloud are not there at all until you choose Move to Local. Removal deserves the same care as installation: packages that add objects can leave data a vanilla or older version does not know how to read. Test risky changes on a copied world instead of the one your group has been playing in for months, and write down which packages the world was created with.
04Give the group the same exported profile
Open Settings → Profile → Export profile and share the code or the .r2z file with everyone who plays on the world. Each player imports it from the profile selection screen and then verifies their own Settings → Directories, because the export carries packages and versions but not machine paths. Manually installed and locally imported mods are not included on import, so anything the group installed by hand needs separate instructions and a stated version. Ask every player to launch once and reach the main menu before the session begins.
05When one player cannot join the world
Compare the client and the server as two separate configurations. On the client, confirm the correct profile is active, that Start modded was used, and that the package list matches the group's stated versions. On the server, check its own installed packages, versions, and configuration, and read the server's logs rather than the client's, because a client-side log cannot show why the server rejected a connection. Reduce the client to the loader plus one shared package and retry to see whether the problem sits in the pack or in the connection path.
06Recover a working profile after an update
Export the profile your group plays on before updating anything, import it into a second profile, and test the update there. Game updates can move faster than loaders and packages, so if that profile fails, the original export still gives you an exact version set to return to. Update one layer at a time — loader first, then shared dependencies, then content — and launch between each layer. Downloads are cached and shared across profiles, so testing a second profile does not re-download the same packages; the cache sits under r2modmanPlus-local/mods/cache, reachable from Settings → Directories → Data and profile folders → Browse.
✦ Frequently asked questions
Common questions, answered directly.
Do Valheim clients and the server need the same mods?
It depends on each package. Server-authoritative and content-changing mods normally need matching versions on both sides, while interface and camera mods are usually client-only. Check the README for each package and the server's rules, then write the split down so the group is working from the same list.
Can removing a Valheim mod damage my world?
Packages that add objects or change generation can leave data that vanilla or older versions cannot read. Back the world up before removing anything, test the change on a copy so you can compare, and follow the package's own uninstall instructions where they exist.
Can r2modman manage a dedicated server?
It manages the packages on the machine where it runs, so it can help you assemble and export the set. Starting the server, pointing it at a world, and opening ports remain separate tasks, and the server's own logs are where you look when it fails to start.
Why does Valheim start without my mods?
The common causes are launching from Steam instead of Start modded, a path in Settings → Directories that does not match the real install, or a missing loader pack. Fix the path first, then launch once and read the first entry in the loader log — Settings → Debugging → Copy log to clipboard copies it out.
How do I keep the group on the same versions?
Export the working profile and share the code or the .r2z file rather than a list of mod names, because the export carries exact versions. Re-export whenever the pack changes, and have players import into a new profile instead of updating packages individually.
r2modman manages a game once its Thunderstore community and a compatible loader exist, so the supported list grows with Thunderstore. Packages install per profile, which keeps two different mod sets for the same game apart.
Next: open the Online tab, install the community's loader pack with Pinned beside its name, then add the packages tagged for the game version you are on.