Field guide ยท 11 minute read
Valheim Base Defense and Raid Events Guide
A raid tests the systems around the walls: spawn control, sightlines, exits, food access, repair materials, livestock placement, portals, and whether every valuable function occupies one fragile room. Defense should delay, separate, and recover rather than promise that no enemy ever crosses the perimeter.
Choose terrain that supports visibility
Open approaches reveal threats earlier and reduce hidden attacks against walls. Avoid deep valleys, dense trees against the perimeter, and shorelines where enemies can reach structures while players cannot move easily. The perfect scenic position can require more defense work than a modest readable site.
Use terrain carefully. Raised earth and trenches can delay ground enemies, but steep edges may trap players, carts, or tame animals. Preserve gates and walking routes that work during combat. A defense that blocks every friendly exit converts the base into its own hazard.
Use layered zones instead of one wall
The outer layer should provide warning and delay. The inner layer protects portals, beds, food, and critical production. Workbench or other player-base coverage reduces nearby spawning but does not replace walls, repairs, or active response. Check gaps after expanding buildings and farms.
Keep a clear fighting lane between layers. Random decoration against the wall can block attacks and repairs. Place stairs or platforms where players can see outside without falling into the event. Multiple gates reduce the chance that one occupied entrance controls every movement.
Separate irreplaceable functions
Do not place all portals, premium food, crops, breeders, metal, and beds in one central room. Split storage and maintain at least one recovery portal or bed outside the most valuable compound. A raid that reaches one zone should not erase every way to respond.
Protect seed crops and breeding stock separately from routine harvests. Keep replacement tools and food in an inner chest. The goal is to resume production after damage without rebuilding the entire account from raw resources.
Respond to events with a prepared loop
Eat and restore Rested before long base projects so an event does not begin with empty food slots. Keep arrows, a shield, and the primary weapon repaired. When the event begins, identify enemy type and choose a fighting area away from crops, portals, ships, and weak roofs.
Pull enemies into readable groups instead of opening every gate. Repair only from a safe position; staring at a damaged wall while surrounded can create a player death and a breach together. In multiplayer, assign one defender to high-priority enemies and another to watch structures or ranged threats.
Audit and rebuild after the timer
The end message does not guarantee every enemy vanished. Walk the full perimeter, shoreline, roofline, crops, livestock, and remote production. Repair structural damage, replace workbench coverage, close gates, and restock the response chest before sorting ordinary loot.
Record the actual breach point and improve that layer only. Adding a second wall everywhere may cost more than fixing one blind shoreline or uncovered spawn area. A base becomes resilient through measured corrections after real events, not through endless fortification before the first attack.
Before you leave
Expedition checklist
- Approaches are visible and friendly exits remain usable.
- Spawn-suppression coverage reaches all critical zones.
- Walls, terrain, and inner protections form separate layers.
- Portals, crops, livestock, beds, and premium storage are not concentrated together.
- A protected response chest contains food, weapons, arrows, hammer, and repair materials.
- The entire perimeter is checked and restocked after every event.
Sources and scope
This independent guide is reviewed for the public game version shown above. Strategy recommendations are practical defaults, not official rules. Preview-build details stay excluded until they reach the public release and pass review. Report a problem through the corrections page.