"No Skill Drain" Resetting On Dedicated Server — Valheim Wiki

"No Skill Drain" world modifier appears to reset on a dedicated server

A recurring frustration on the Valheim subreddit: a player enables "No Skill Drain" on their character through the world modifier panel, joins a dedicated server, dies, and loses skill levels anyway. The modifier appears to have been "reset." It was not — but the behavior is genuinely confusing and the fix requires understanding how Valheim layers modifiers between client and server.

The mechanism in one sentence

On a dedicated server, the server's world modifier configuration is authoritative. The client-side modifier panel that you see when picking a world in single-player has no effect when joining a dedicated server. Skill drain happens or doesn't happen based on the server's death penalty setting, not your local setting.

Why it looks like the modifier "reset"

You click "Start Game" in the main menu. You see the world modifier panel with "No Skill Drain" checked. You join a dedicated server. You die. You lose skill levels. The natural conclusion: "the server reset my modifier."

What actually happened: the modifier panel you clicked was for your own world (if you were to host single-player), not for the dedicated server you joined. The dedicated server has its own setting, and that setting is what applied to your death. The client UI does not surface this distinction clearly, which is why it surprises players.

Confirming the server's actual setting

You need to look at the server's startup arguments or admin console output, not the client UI.

If you have shell access to the server

cat start_server.sh | grep -i modifier
# example output
# -modifier deathpenalty hard
# -modifier combat veryhard
# -setkey nomap

If deathpenalty is set to hard, veryhard, or hardcore, skills WILL drain on death. Only casual and veryeasy remove skill drain. If the line is missing entirely, the server is using the default (skills drain).

If you only have client access

Become admin on the server (add your Steam ID to adminlist.txt, then restart). Press F5 in-game to open the console. Run:

getworldmodifier deathpenalty

This prints the active value. Reproduce for combat, resources, raids, portals. The output is the truth; the world modifier UI you saw on your client is not.

The fix: change the server, not the client

Once you confirm the server's setting is not what your group wanted, fix it on the server side:

Method 1: Edit startup arguments (clean restart)

Stop the server. Edit start_server.sh to set -modifier deathpenalty casual. Start the server. All future deaths use casual death penalty (no skill loss, no item drop).

Method 2: Admin console while server is running (no restart)

As admin in-game, press F5 and run:

setmod deathpenalty casual

Applies immediately. Persists across server restarts because Valheim writes the modifier into the world metadata. No need to restart the server.

Restoring already-lost skill levels

The modifier change applies forward. Skills already lost to deaths under the old setting do not come back automatically. For affected players, an admin can manually restore their levels:

raiseskill jumping 5
raiseskill sneak 10
raiseskill blocking 7

The raiseskill command adds levels to the current player only, not other players. To restore another player's skills, they need to be on the server and admin connects to them, or you grant them admin temporarily and have them run it themselves.

Other modifiers with the same client/server confusion

The exact same trap exists for these modifiers — the client UI shows your local preference, the server's setting is what applies:

• Combat difficulty — server's value is authoritative
• Resource rate — server's value is authoritative
• Raid frequency — server's value is authoritative
• No Map / No Portals — server's setkey values are authoritative
• Passive Mobs / No Build Cost — server's setkey values are authoritative

If a setting "isn't working" on a dedicated server, check the server's actual configuration first. Nine times out of ten the answer is there.

The one case where it really is a bug

If the server's getworldmodifier deathpenalty returns casual and players still lose skills on death, the rare actual cause is a save-file metadata corruption where the modifier flags in the .fwl file got reset by an interrupted save. To fix:

1. Stop the server.
2. Restore the most recent .db.old and .fwl.old backup from worlds_local/.
3. Start the server.
4. Run setmod deathpenalty casual via admin console to re-write the metadata.

This is uncommon but real. If you suspect it, look at your .fwl file's modified timestamp against the last reported death — if they're seconds apart, you probably had a save-interrupt corruption.

Related articles

• World Modifiers reference
• Hardcore no-map no-portal server setup
• Granting admin permissions on a dedicated server
• Using devcommands for admin tasks

Looking for managed Valheim server hosting? Supercraft runs Valheim dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.