Hardcore Valheim — setting up a no map, no portal dedicated server
The most engaging Valheim threads of 2026 have not been about new biomes — they have been about players running "true Viking" servers: very hard combat, no map, no portal, hardcore death penalty (lose all items and skills permanently on death). The mode produces stories that feel closer to the Viking sagas than vanilla play does, and dedicated server admins have asked how to configure this properly. This page is that setup.
What "true Viking" means in 2026
The community uses "true Viking" loosely, but the consensus stack is:
- Combat: Very Hard — enemies do approximately 2x damage, take 2x damage from you (so combat is faster but lethal both ways).
- No Map — no minimap, no big map, no pings. Navigate by sun, landmarks, and memory.
- No Portals — every trip is a real journey. Karves and longships matter again.
- Hardcore death penalty — on death you lose all items on your body AND your accumulated skill levels permanently. No tombstone retrieval.
- Resources: normal — most players keep this at default. The mode is hard enough without resource scarcity on top.
The community pattern: pair it with very hard combat for the full experience, or with normal combat for a more accessible "immersive Viking" feel.
Dedicated server startup flags
On a Linux dedicated server, edit start_server.sh (or your hosting panel's startup arguments) to include the modifier flags. Stop the server first.
./valheim_server.x86_64 -nographics -batchmode \
-name "TrueViking" \
-port 2456 \
-world "Yggdrasil" \
-password "askbjorn" \
-public 0 \
-modifier combat veryhard \
-modifier deathpenalty hardcore \
-modifier raids more \
-setkey nomap \
-setkey noportals \
-saveinterval 600
The arguments break down:
| Flag | Purpose |
|---|---|
-modifier combat veryhard | +100% damage in both directions |
-modifier deathpenalty hardcore | Lose all items and skills permanently on death |
-modifier raids more | Raids fire more frequently — gives players a reason to defend bases instead of nomading |
-setkey nomap | No map for any player on the server |
-setkey noportals | Disables portals globally |
-public 0 | Private server — true Viking groups usually keep these whitelist-only |
-saveinterval 600 | Save every 10 minutes — important because crashes shouldn't lose progress in a mode where progress is already fragile |
The settings you have to decide deliberately
Two settings cause arguments in every true-Viking group. Decide before launch and document in your server description so players know what they signed up for.
Skill loss is permanent — really
Under hardcore death penalty, skills lost on death do not come back. A player who dies at sneak level 80 cannot grind their way back to 80; their personal cap is reduced by the death penalty. This is the intended behavior but it surprises new players. Most groups either:
- Embrace it: deaths matter forever, characters have history, eventually you "retire" a character and start a new one.
- Soften it: drop down to
deathpenalty hardinstead ofhardcore. Skills still drop but not permanently capped, items still drop on death.
The middle ground (hard) is what most servers actually use after one or two campaigns at full hardcore. The full mode is a niche taste.
How you handle traders without portals
Haldor and Hildir are randomly placed. Without portals, reaching them is a multi-day sail. Server admins have two patterns:
- Sail to it, build near it. Once a trader is found, the group builds an outpost nearby. Voyages become trade expeditions. Most immersive.
- Use the
-setkey playereventsalternative. Doesn't add portals back, but adjusts raids to per-player progress so newer joiners aren't constantly hit with high-tier raids the group has unlocked.
Admin tools you keep on hand
True Viking is unforgiving. As admin, you will get rescue requests. Keep these tools ready and decide in advance whether you'll use them.
| Tool | Use case |
|---|---|
raiseskill <name> <skill> <level> | Restore a player's skill after a game-bug death (NOT a player-fault death) |
spawn <item> | Replace items lost to game bugs only. Document every spawn in your admin log so the group sees fairness |
| Server backups | Daily rolling backups so a save-corruption event doesn't end the campaign. See the backup guide |
| Death recovery world coords | Players often die far from home with no map. Have them post screenshot of last landmark, you can locate them via console |
The line that keeps the group together: bug deaths get rescue, player-fault deaths do not. Stick to it.
Pacing a true Viking campaign
A solo or duo true Viking run to Bonemass takes 60-120 hours. To Yagluth, 150-250 hours. To Ashlands progression, 300+ hours. This is roughly 3x to 5x the time of a normal-difficulty server run. Plan campaign length accordingly:
- 3-month campaign: Aim for Plains / Mistlands progression. Don't promise Ashlands.
- 6-month campaign: Realistic Ashlands push if players play 4-8 hours per week.
- Open-ended: Players will run hot for the first 3 months, cool off, then ebb back. Don't force the pace.
Common questions from players joining a true Viking server
How do we find each other without portals or a map?
Pre-agreed landmarks and verbal directions. "Sail east from spawn, the big rock formation that looks like a tooth, then north past the swamp until you see smoke." Voice chat becomes essential. This is part of the appeal — players actually communicate.
Can I keep my character if I join a true Viking server with an existing high-level character?
Yes — Valheim characters are independent of worlds. But if your existing character is level 60 sneak from a casual server, they retain those skill levels on the true Viking server. Server admins typically ask players to create a fresh character for fairness. There is no enforcement mechanism; it is a social contract.
Can I add portals later if the mode is too punishing?
Yes. Change -setkey noportals to remove the flag and restart. Existing portal structures don't activate (they were dormant); players need to build new portal pairs. Existing maps remain hidden if nomap is still set. The change is one-way: re-enabling portals breaks the no-portal immersion of the campaign, so groups usually commit at start.
Related articles
- World Modifiers reference (all flags and presets)
- Why "No Skill Drain" appears to reset on dedicated server
- Pacing slow-progression community servers
- Granting admin permissions on a dedicated server
For a managed Valheim server with all modifiers exposed in a panel and rolling backups, see Supercraft plans.