Base Raids Stopped Triggering — Valheim Wiki

Why base raids stopped happening on your Valheim dedicated server

A common Valheim community thread: a returning solo player or small group reports that early in the campaign they got "a lot of raids" (Greylings, boars, trolls), but later in the game raids stopped firing entirely. They worry it's a server bug. Usually it isn't — the raid system has clear rules, and what looks like "no raids" is almost always one of a handful of base-design or modifier conditions blocking the event from finding a valid spawn or trigger. This page walks through what's actually happening and how to fix it.

How Valheim raid triggering actually works

Raids fire when all of these are true:

1. Time: at least 46 in-game minutes since the last event ended (roughly 46 real minutes in active play, since active play loads the day/night clock).
2. Location: a player is in a zone that contains a "base" — defined as containing certain crafted structures (workbench, forge, etc.) tied to the player.
3. Progression: the world has progressed past the boss tier required for the raid type. Early raids require no bosses; later raids require Eikthyr, then The Elder, etc.
4. Spawn space: the game can find walkable, unobstructed ground near the base to spawn the raid enemies.
5. Raid modifier: the world's raid modifier is not set to none.

If any one of these fails, no raid. The most common silent failure is #4: the base became too dense or too walled-in for the raid system to find a spawn point.

Diagnosis: which condition is failing?

Check 1: Is the raid modifier set to none?

As admin, F5 console, run:

getworldmodifier raids

If it returns none, that's the answer. Set it to more or back to default:

setmod raids more

This case is most common when a player toyed with modifiers in their local UI and the actual server setting got changed. See the No Skill Drain article for related modifier confusion.

Check 2: Is the base spawn-blocked?

The most common silent cause. Raid enemies need to spawn near the base, on walkable terrain, in a position not already occupied by structures or terrain features. If your base is:

• Built on a small island surrounded by water
• Built on top of a mountain with steep cliffs all around
• Walled in with stone for hundreds of meters in every direction
• Has raised terrain that fills every nearby clear patch

... the game cannot find a valid spawn point and silently skips the raid. The raid clock still resets, so to the player it looks like raids "stopped."

Fix: leave a few open clearings within 50 meters of the base. Doesn't have to be undefended — just clearable terrain where the game can place a mob. You'll start seeing raids again within an hour of play.

Check 3: Have you used setkey playerevents?

This setkey changes raid triggering from "world progress" (default) to "individual player progress." On a multiplayer server where players are at very different progression levels, the world-progress default means everyone gets endgame-tier raids even if they're new. Player events solves that, but has a side effect: brand-new players in their fresh base trigger only their personal-progress tier of raids, which can be misleadingly low.

If you wanted both: set playerevents on, accept that lower-tier players get lower-tier raids. Or turn it off and accept all players get the same raids.

Check 4: Are you the only player who has been online recently?

The raid clock is per-world, not per-player. If a player logs off and the world stays loaded, the clock still advances. But if the server has been empty for hours, the clock effectively pauses on most server configurations. When players come back, raid timing may be unintuitive but not broken.

Check by running:

events

From the F5 console. Lists the eligible events for the player. If the list is empty, no events are eligible for this player at this location.

Check 5: Have you progressed past all raid tiers?

Once you kill Yagluth, you've unlocked the highest-tier "world progress" raids. If your base location doesn't qualify for any of them (e.g., a Meadows base after Yagluth — see the Meadows base endgame article), raids drop in frequency because most of the rolled events are biome-mismatched.

Fix: build a forward base in the biome that matches the raid tier you want. A Plains base after Yagluth gets Fuling raids. A Mistlands base post-Queen gets Seeker raids. The raid type depends on where you are, not just what bosses you've killed.

The "I want more raids" admin actions

If you want raid frequency cranked up for the campaign:

The event command is the diagnostic tool that confirms raids CAN fire at all — if you can force-trigger a raid via event and it works, the issue is your modifier or spawn conditions, not a server bug.

Edge case: post-Ashlands campaign with raids off

One specific reddit thread observed: solo player, only mod was Seasons, played to Ashlands, raids stopped firing. The likely cause: the Seasons mod can interact with the day/night cycle the raid clock uses. The clock advances oddly when seasonal time effects are in play, and the raid event window can be skipped repeatedly. Disable the mod for a play session to test; if raids return, the mod is the cause and you can re-enable it knowing the cost.

Verify with a force-trigger

If you've checked everything and want to confirm raids work at all on your server:

1. Become admin, F5, type devcommands.
2. Stand at your base.
3. Type event army_eikthyr.
4. You should hear "You are being hunted." and Greylings should arrive within a minute.

If they don't, your base is spawn-blocked. Clear a 20m radius of open terrain on the most accessible side of the base and retry.

Related articles

• World Modifiers reference
• Meadows base endgame viability
• When modifier settings appear to reset
• Using devcommands for diagnosis

For a managed Valheim server with rolling backups so you can test raid changes safely, see Supercraft plans.