The Mod Ecosystem After 1.0 — What Is Adapted, What Is Not

1.0 was a bigger-than-usual update — a Unity engine upgrade, a new biome (Deep North), and a new networking layer — so the mod ecosystem took a real hit at launch and then recovered at different speeds per mod. This page is the map of where things landed: which categories of mods adapted quickly, which are still catching up, and how to check any specific mod before you build a save around it.

Honesty note (what we have and have not verified): the general pattern below (QoL mods update fast, big overhauls slow, networking-touching mods lag furthest) is stable and well observed. We deliberately do not publish a fixed “mod X is adapted / mod Y is not” list, because the specific status of any mod flips within days of each patch. The reliable thing to do is check the mod’s own page at the time you install — and we explain exactly what to look for below. For the crossplay angle and the Valheim Plus succession, see mod-ecosystem-1-0.

What adapted quickly

Quality-of-life mods touch less game code, so they are usually the first back. If you mainly want convenience tweaks, the 1.0 ecosystem is healthy:

• Inventory / slots (e.g. ExtraSlots) — back to normal.
• Planting / foraging (e.g. PlantEverything) — back to normal.
• Crafting convenience (e.g. Craft From Containers) — back to normal.
• Building camera / plan (e.g. Gizmo, PlanBuild) — back to normal, and arguably better now that Deep North gives you more to build.

What lags behind

Bigger mods hook into more of the game, so they take longer to re-release:

• Combat / progression overhauls (damage, health, new difficulty curves) — typically slower; some remain un-adapted for a while after a patch.
• Loot / economy overhauls (EpicLoot-style changes) — depend on the game’s drop tables, which the engine upgrade touched, so they can lag.
• Anything touching networking or low-level systems — the PlayFab networking change means mods that assume the old Steam networking behave differently or not at all; these are the slowest to stabilise and the ones most likely to cause desync in a group (see server-side vs client-side mods).

The old monolithic package (Valheim Plus) is the clearest marker of the shift: it is deprecated, with maintenance continuing through the Grantapher fork, and its features largely absorbed by the standalone plugins above.

How to check a specific mod before you commit

Three signals on a mod’s page, in order of importance:

1. The Side field — Client, Server, or Both. For a group session this decides who has to install it (see who has to install what).
2. The compatibility / version note — look for a “1.0” or “Deep North” marker and the date of the latest release. A recent release dated around the 1.0 window is the strongest signal it is adapted.
3. The issue tracker / comments — for a mod you are about to build a save around, a quick scan of recent issues tells you whether it is actively maintained right now.

If a mod you need is not yet adapted, the safe play is to test on a copy of your world before running it on your main save — an un-adapted mod touching world state can corrupt a save you care about.

The durable takeaways

• Standalone BepInEx plugins have largely replaced the single-package era; pick the QoL plugins you actually want.
• Crossplay is the hard blocker for any modded session — no amount of adaptation changes that.
• The per-mod “is it adapted yet” question is a moving target; check the page, not a static list.

Links

• mod-ecosystem-1-0 — the crossplay tradeoff and the Valheim Plus succession
• bepinex-setup — the loader and a starting list of plugins
• server-vs-client-mods — who has to install what
• multiplayer-compatibility — troubleshooting a modded group session
• valheim-plus-intro — the old all-in-one and its replacements