The Mistlands is where a Valheim group stops being able to brute-force its way forward. You cannot see, the ground goes up and down in cliffs, the enemies jump, and the biome is the most expensive thing in the game for the players' own machines. On a dedicated server the practical answer is: kill Yagluth first so wisps exist, build a wisp fountain at home and a wisplight for everyone, treat the Dvergr as neutral until you decide otherwise, clear infested mines in pairs or threes, and fight the Queen with a backup taken that morning. Most of the lag people blame on the server in the Mistlands is their own graphics card, and the rest is zone ownership.
This guide covers the order of things for a group, what is shared on a server and what is personal, the Queen fight, and the performance side - which is the part that decides whether the biome is fun or a slideshow.
What the Mistlands changes for a group#
Before the Mistlands, a group can progress mostly by having more people and better armour. The Mistlands adds three problems that headcount does not fix.
- Visibility. The mist hides everything beyond a few metres unless you carry a light that clears it. A group with one wisplight between five people is a group of four people walking blind.
- Verticality. The terrain is a maze of cliffs, giant ribs, roots and ravines. Falling is the most common cause of death in the biome, and a corpse run down a ravine at night is the most common cause of a second death.
- New systems. Eitr, magic, the Galdr table, the Black forge, sap extraction and the Dvergr all arrive at once. Somebody has to read the recipes; it is much faster if the group splits the reading.
On a server, the progression itself is shared. The Queen's kill sets a world-wide global key (defeated_queen), exactly like the earlier bosses, so one successful fight counts for everyone, including people who were not online. What is not shared is everything about a character: each player's map, inventory, skills and food are their own, and they live on that player's machine, not on the server. Server-wide boss progression goes through what a late joiner inherits and what they do not.
Wisps, the wisp fountain and the wisplight#
Yagluth drops torn spirits. One of them builds a wisp fountain, which attracts wisps when it is dark or raining in the Mistlands. The wisps are harvested by hand, and one wisp plus a silver bar at the workbench makes a wisplight - the floating light that follows you and pushes the mist back. A cheaper placeable, the wisp torch, uses a wisp and Yggdrasil wood and lights a fixed spot.
The practical points for a group:
- Build the fountain inside the Mistlands, near your landing. It needs to be in the biome to attract wisps. Put a ward and a small shelter beside it and treat it as the group's first outpost.
- One wisplight per player, before anyone goes deep. It costs one silver bar each. There is no reason to share them, and sharing means someone is always blind.
- The wisplight goes in the utility slot. That is the same slot as Megingjord, the belt that raises carry weight. You choose between seeing and carrying, which is why mining trips into the Mistlands are slower than anyone expects. Plan ore runs as two-person jobs: one carries, one lights.
- Keep spare wisps in a chest at the outpost. A player who dies loses nothing permanent, but a player whose wisplight is in a tombstone at the bottom of a ravine needs a second one to go and fetch it.
The fountain only produces a few wisps at a time, so on a group world it pays to put a second one down early. Wisp torches at the outpost, the portal and any regular path make the biome feel very different at night.
The Dvergr: neutral until you make them not#
The Dvergr are the dwarf-like settlers who live in outposts and towers across the Mistlands. They are neutral to players by default and hostile to Seekers and Gjall, so a Dvergr camp can be a safe-ish place to stand while something else is chasing you.
They stop being neutral when you take from them. Breaking their structures, opening their chests or stealing from their camp turns the group around you hostile, and Dvergr mages hit hard with fire and ice. The rule that saves arguments on a group server is simple: agree before anyone loots a Dvergr site, because one player opening a chest turns the camp on everyone standing in it.
Dvergr sites are also where a lot of the biome's materials come from - their structures and the ruins around them are a source of black marble and other building materials, and their camps often hold useful loot. Most groups end up raiding camps deliberately, with everyone ready, rather than by accident. That is the right way round.
The other inhabitants:
| Creature | Threat | Notes for groups |
|---|---|---|
| Seeker | Medium | Common, fast, drops carapace for armour |
| Seeker soldier | High | Heavy armour, knocks players off ledges |
| Seeker brood | Low | Swarms inside infested mines |
| Gjall | High | Flying, spits explosive bile, spawns ticks |
| Tick | Low but annoying | Latches on and drains health |
| Hare | None | Food |
Carapace from Seekers is the main armour material, and a Gjall's bile bag is the ingredient for bile bombs. Gjall are worth killing from range - a staff or a good bow - rather than chasing them over the cliffs.
Infested mines, black cores and the Sealbreaker#
Infested mines are the Mistlands dungeons: Dvergr-built tunnels overrun by Seekers. They hold the things that matter for progression, and they are the part of the biome where a group's size actually helps.
What you go in for:
- Black cores, the progression material for the Mistlands crafting stations and higher-tier magic gear.
- Sealbreaker fragments, which are assembled into the Sealbreaker at the Galdr table. The Sealbreaker is the key that opens the doors to the Queen.
- Soft tissue, which is half of eitr. The other half is sap, drawn from the giant Yggdrasil roots with a sap extractor. Eitr is refined from the two.
- The vegvisir inside the mines, which shows where the Queen's citadel is. Every player who reads one gets the marker on their own map, so each person who wants it should read it.
Inside a mine, the tunnels are narrow, the brood swarm, and a soldier in a corridor is a wall. Two or three players is the sweet spot. Five players in a corridor mostly hit each other's backs, and enemy scaling means the extra bodies make every Seeker tougher - how creatures scale with nearby players explains the range and the numbers. A mine is a good job for a small team while the rest of the group runs sap and builds the outpost.
Eitr, magic and the new crafting stations#
Eitr is the Mistlands' new resource bar. You get it only from food - specific Mistlands dishes made with sap, mushrooms such as magecap and jotun puffs, and the biome's meat - and staffs spend it. Without eitr food, a staff does nothing.
The two magic trees split naturally across a group:
| Role | Staffs | What it does for the group |
|---|---|---|
| Elemental | Staff of Embers, Staff of Frost | Ranged damage, good against Gjall |
| Blood | Staff of Protection, Dead Raiser | Shields the group, raises skeletons to tank |
A group with one blood magic player is noticeably safer: the protection staff's shield on everyone in range before a soldier fight or the Queen is worth more than another melee player. Blood magic costs health as well as eitr, so the player taking that job needs the right food and should not also be the person who carries the ore.
The new stations - the Galdr table, the Black forge and their upgrades - need materials from the mines and Dvergr sites. On a server, build them once, at the group base, and decide who owns the Black forge queue. Black metal from the Plains still matters here: much of the Mistlands gear needs it, so a group that skipped black metal will be sent back.
The Queen fight on a server#
The Queen sits in an infested citadel behind doors that only the Sealbreaker opens. There is no altar and no offering; the Sealbreaker is the summon. That means the group decides when the fight starts, but it also means the fight happens in her arena, which is cramped, dark and full of Seekers she calls in.
How groups usually prepare:
- Take a manual backup. Not because the fight breaks the world, but because a group wipe in the citadel leaves several tombstones in a room you cannot easily re-enter, and everyone will want a decision afterwards. Having a fresh backup turns "what if" into a choice. The boss summoning guide has the general version of this checklist.
- Build a portal outside the citadel doors. Corpse runs on foot through the Mistlands at night are miserable.
- Full food, including eitr for the staff users. Mistlands food for the melee players, eitr food for the casters.
- Bring poison resistance and frost resistance meads if you have them, and healing. Her attacks hit hard and her minions keep coming.
- Decide roles. One or two players kill the adds, the rest stay on the Queen. A blood magic player keeps shields up.
On a server, one player owns the citadel zone and simulates the Queen and her minions. That should be the player with the best connection and the most capable machine, because they are running the whole fight. Have them walk in first. If the Queen teleports or stutters for everyone, it is usually the owner's connection, not the server - see latency, jitter and packet loss for how to tell.
Each kill drops the Majestic carapace (called the Queen drop before the Ashlands update), which upgrades the artisan table and leads on to ceramic plates - and from those to the Drakkar and the trip to the Ashlands. Her trophy gives a Forsaken power that each player activates for themselves; Forsaken powers in multiplayer explains how that works on a shared world. Once she is down, defeated_queen is set for the whole world, with the trader and raid changes that come with it.
Why the Mistlands is heavy - and on whom#
This is where the biome earns its reputation. Players complain that the server lags in the Mistlands. Usually it is their own PC.
The load splits like this:
| Load | Who pays | Why |
|---|---|---|
| Mist rendering | Each player's GPU | Dense, layered fog effects everywhere |
| Terrain and giant objects | Each player's GPU and CPU | Huge ribs, roots, skulls and cliffs in view |
| Creature AI in your zone | The zone owner's CPU | Seekers, Gjall and ticks run on whoever owns the zone |
| World storage | The server | Every Dvergr piece, root and rock is an object it holds |
The server does not render anything. It stores objects and relays state, so the visual weight of the mist costs it nothing. What does reach the server is the number of objects: the Mistlands is dense with them, and every one a player loads is held in memory. A world where the group has explored a lot of the Mistlands uses more memory than the same world before it, and saves take a little longer. The performance by biome guide compares the Mistlands with the Ashlands, the Plains and the ocean.
What to do about it:
- Players with weaker machines should lower their own settings, especially shadows, vegetation and view distance. That is the single biggest fix and costs nothing.
- Keep the strongest machine and best connection in front when entering new zones. The first player in owns the zone. If that is the player on a laptop over wifi, everybody's Seekers rubber-band.
- Do not build a massive base in the Mistlands. The biome already carries a lot of objects per zone. Put the outpost there, not the main hall.
- Restart the server on a schedule. Memory climbs as more zones are visited; a weekly restart at an empty hour keeps it flat.
- Lower the save interval. A bigger world takes longer to save, and the window for losing progress to an unclean stop is the whole interval.
-saveinterval 600is a sensible setting at this stage of a world.
If memory is genuinely the limit, the dedicated server will show it - on a hosted server, look at the memory graph against the limit rather than guessing. A 10-player group in a well-explored world with the Mistlands open is usually comfortable at 4-6 GB; a modded world needs more.
Admin tasks during the Mistlands#
Vanilla admins have no cheat commands, so most Mistlands admin work is prevention.
- Backups before the Queen and before any patch. The Mistlands is late enough in a world that losing it means losing months. Schedule a daily backup and take a manual one before big fights. A backup that has been restored once is worth ten that have not.
- A clean stop before every update. Wait for
World savedin the log. - Watch the memory graph the first week the group is in the biome. If it hits the plan's limit, you want to know before an out-of-memory stop eats the last save interval.
# Launch line for a group world in the Mistlands phase./valheim_server.x86_64 -nographics -batchmode \ -name "Longship Crew" -port 2456 -world "Midgard" \ -password "herring-barrel-42" -public 0 \ -saveinterval 600 -backups 6 -backuplong 21600On RE:NODE the same values go into the Startup tab. Backup slots come with every Valheim plan and restore with one button, and the Schedules tab can run a daily backup and a weekly restart at an hour nobody plays - the guides page shows how. If a server does reach its memory limit, it is stopped and restarted clean rather than left to swap, which is exactly why the shorter save interval matters on a big world.
Troubleshooting the Mistlands#
Nothing glows and there are no wisps. Yagluth has not been killed on this world, or the fountain is outside the biome. Check the global key with an admin who has devcommands through a mod, or ask whoever killed him which world they were on.
The Seekers teleport around. Zone ownership. The player who entered first owns the zone on a poor connection. Have them step back out; ownership passes to someone else.
Frame rate collapses but the server is fine. It is the client. The server's CPU graph will be flat while someone's PC is struggling with the mist. Lower their settings.
A player cannot find the Queen. Each player has to read a vegvisir for the marker to appear on their own map, or the group shares maps at a cartography table.
The whole group died in the citadel. Portal outside, everyone respawns, food, back in for the tombstones together. If that is impossible, the admin decision is in helping players with lost tombstones.
FAQ#
Can we fight the Queen before killing Yagluth?
No. Wisps are locked behind Yagluth, and without wisplights the Mistlands is barely playable. The biome is designed to come after the Plains, and the materials chain assumes black metal.
Does the Mistlands make the server need more RAM?
A little. The server stores every object the group has loaded, and the Mistlands is dense with them, so memory grows as the group explores it. The mist itself costs the server nothing - that load sits entirely on the players' graphics cards.
Why is the wisplight in the same slot as Megingjord?
Both are utility items and only one fits. It is a deliberate trade: in the Mistlands you choose between seeing and carrying. Groups work round it by sending carriers with an escort who has a light.
Does killing the Queen once count for everyone on the server?
Yes. The kill sets a global key for the world. Each player who wants her Forsaken power still has to activate it themselves at the stone, and personal things like the vegvisir markers stay per character.
Is it safe to raid Dvergr camps?
It is safe if everyone is ready. Opening their chests or breaking their buildings makes the camp hostile to the whole group nearby, and their mages hit hard. Agree before anyone loots, so the fight starts when you want it to.
