Valheim Server Settings Explained: The Best Config for Your Group

For most mixed-experience groups, the best Valheim dedicated-server setup is a private Normal world with a password, -public 0, the Steam backend, automatic saves, and rolling backups. Add -modifier resources more if players have short sessions, then adjust raids, portals, combat, or death penalties only after the group agrees on the trade-off. Put the preset first in the launch arguments, followed by modifiers and other overrides.

That baseline keeps exploration and progression recognizable while reducing the two biggest sources of friction: finding the server and losing a long evening to a preventable outage or death. The sections below explain every important argument, the Steam-versus-Crossplay networking choice, safe modifier combinations, backup timings, administration files, and recovery steps.

What are the best Valheim server settings for a group?

A private Normal server is the safest starting point for a mixed group. Set a password, hide the listing with -public 0, retain the default save and backup cadence, and use the Steam backend unless players need Crossplay. If the group usually plays brief sessions, increase resource output rather than changing several difficulty systems at once.

This approach keeps the core Valheim progression intact. It also gives the group a clear way to change one pressure point at a time: gathering time, raids, combat danger, death consequences, or portal restrictions. The values below are recommendations, not mandatory defaults.

Recommended launch command

-name "Viking Group" -port 2456 -world "Dedicated" -password "replace-this" -public 0 -saveinterval 1800 -backups 4 -backupshort 7200 -backuplong 43200 -preset normal -modifier resources more

Replace the password and world name before starting. The command uses the default Steam port, saves every 1,800 seconds, retains four automatic backups, creates the first backup after 7,200 seconds, and uses a 43,200-second interval for later backups. The resources more override is optional; remove it if the group wants the standard gathering pace.

How do Valheim dedicated-server arguments work?

Iron Gate’s dedicated server reads startup arguments for the server identity, world, access rules, networking, persistence, backups, and world modifiers. Arguments are evaluated in order, so the order is part of the configuration rather than cosmetic formatting.

Identity and access arguments

Argument	Purpose	Group-world guidance
-name	Sets the name shown in the server list.	Use a recognizable group name, such as Viking Group.
-world	Creates or selects the named world.	Keep the name stable so the server reopens the intended world.
-password	Sets the join password.	Use a private password shared only with players who should join.
-public 1	Lists the server in the browser.	Use only when a public listing is intentional.
-public 0	Hides the server from the browser while still allowing joining by address.	Recommended for a known group.

A password is still useful on a hidden server because it adds a second access control. For stricter membership, Iron Gate documents a permitted-list file that limits access to listed users; adding one permitted user changes the server from an open-by-password model to an allowlist model.

Why must the preset come before modifiers?

A preset can overwrite earlier modifier choices. Start with -preset normal (or another preset), then append each desired -modifier and -setkey override. This ordering is valid:

-preset normal -modifier resources more

Putting a preset after a custom modifier can reset that modifier and produce a server that does not match the command you intended. When troubleshooting an unexpected world rule, inspect the complete command line first and move the preset to the beginning.

Should a group use Steam or Crossplay?

Use Steam when every player can connect through Steam and someone can forward ports on the host’s router. Add -crossplay when players need the relay backend or broader platform reach; the official guide says that Crossplay does not require internet port forwarding.

Backend	Internet setup	Important limitation	Best fit
Steam (default)	Forward UDP ports 2456 and 2457 and allow the server through the host firewall.	Players and the host must be able to use the Steam networking path.	A group that can configure its router and plays through Steam.
Crossplay (-crossplay)	Uses a relay backend; router port forwarding is not required.	Local-IP and loopback joining are unavailable through this backend.	A group that needs Crossplay or cannot change the router.

How do I configure Steam port forwarding?

1. Reserve or note the host computer’s local IP address so the router rule continues pointing to the same machine.
2. Forward ports 2456 and 2457 to that local IP using the router’s UDP forwarding controls. Iron Gate describes the server as using the specified port and the next port; the documented default range is 2456–2457.
3. Allow the dedicated-server executable through the host operating system’s firewall for the same network profile.
4. Start the server and wait for the console message Game server connected. Iron Gate’s guide says that message means the server is up and ready to accept connections.
5. Have a remote player test joining while outside the host’s home network. A local test alone cannot prove that the router and firewall are configured correctly.

If the server works locally but not for remote players, check the forwarding destination, whether the rule is UDP, the host firewall, and whether the internet connection uses carrier-grade NAT. If the router cannot accept inbound forwarding, Crossplay is the practical alternative.

What changes when Crossplay is enabled?

Add -crossplay to the same command line and remove the assumption that a forwarded port is required. Players should join through the supported server-browser or invite path rather than trying to connect to the host’s local address, because local-IP and loopback joining are not available through the relay backend.

How should I set Valheim saves and backups?

Keep automatic saving and rolling backups enabled for a persistent group world. Iron Gate’s April 11, 2024 guide documents a 30-minute save interval and the following backup arguments; the example command uses those values explicitly so the policy is visible rather than left to an unnoticed default.

Argument	Value in the example	Meaning
-saveinterval	1800	Save every 1,800 seconds, or 30 minutes.
-backups	4	Keep four automatic backups.
-backupshort	7200	Set the first backup interval to 7,200 seconds, or 2 hours.
-backuplong	43200	Set later backup intervals to 43,200 seconds, or 12 hours.

What does the save interval protect?

The save interval limits how far the world can roll back after a crash or forced shutdown. A 30-minute interval is a reasonable balance for a group server: it avoids constant disk activity while keeping the worst ordinary rollback bounded by the time since the last save. Players should still stop the server cleanly before maintenance or moving world files.

How do rolling backups help?

Backups provide recovery points separate from the current world file. Four retained copies let an administrator step back through recent states if a save is corrupted or a player makes an irreversible mistake. The documented schedule makes the first backup more frequent than subsequent long-term backups, preserving a recent recovery point without creating unlimited files.

Keep an additional copy on storage separate from the server machine when the world matters. The official guide documents save locations, but an on-disk backup cannot protect against every storage failure, accidental deletion, or filesystem problem. Copy the world and backup files only while the server is stopped or after a confirmed clean save.

Which combat, death, resource, raid, and portal settings should I use?

These systems are independent trade-offs. Change one axis at a time, tell every player what will change, and record the command line so you can reverse a decision without guessing. The modifier names below are the official argument keys; effect descriptions marked as Valheim.tools data are from an unofficial reference whose publication year is not stated and were accessed in 2026, so re-check them after major Valheim updates.

Combat difficulty

Use the combat modifier with veryeasy, easy, hard, or veryhard. The normal setting is the least disruptive starting point. Valheim.tools lists Very Hard as creatures taking 70% damage while players take 200% damage from creatures, making it a deliberate challenge rather than a small increase.

For a group with new players and veterans, leave combat at normal first. If experienced players want more danger, raise combat after the group has tested its equipment and base defenses; increasing combat and death penalties together can turn a learning problem into a recovery problem.

Death penalties

The deathpenalty modifier accepts casual, veryeasy, easy, hard, and hardcore. Avoid Hardcore unless every player explicitly accepts its loss model. Valheim.tools lists Hardcore as destroying carried items and resetting every skill to 0 on death.

A less severe death setting is usually better for groups with uneven schedules, because one player’s connection failure or rushed solo expedition does not impose a long recovery session on everyone else. If the group chooses a harsher setting, agree in advance on corpse-recovery rules and whether an administrator may restore a damaged world from backup.

Resource gathering

The resources modifier accepts muchless, less, more, muchmore, and most. The editorial baseline for short sessions is more. Valheim.tools lists more as 1.5x and most as 3x for drops, loot, pickables, honey, and sap.

Resource output is the cleanest first adjustment when players have limited time but still want normal combat and exploration. If the group values scarcity, leave it normal and use shared storage and scheduled gathering instead of increasing the multiplier.

Raid frequency

The raids modifier accepts none, muchless, less, more, and muchmore. Keep raids at normal or less until the group has a defensible base. If repeated attacks interrupt building or overwhelm new players, use -modifier raids muchless or -modifier raids none.

Valheim.tools lists none as no raids and muchmore as a raid roll every 13.8 minutes at 66.7%. That extreme setting is best treated as a challenge mode, not a default for a cooperative progression world.

Portal restrictions

The portals modifier controls logistics rather than enemy strength. casual allows all items through portals; hard blocks portals to or from an active boss dungeon; and veryhard disables portals.

Keep portals normal for the least logistical friction. Choose Casual when the group’s main goal is building and exploration with minimal transport chores. Choose Hard or Very Hard only when everyone wants shipping and route planning to be a central part of the game.

Checkbox-style world keys

Iron Gate also documents keys such as nobuildcost, playerevents, passivemobs, and nomap. These are separate from the named combat, death, resource, raid, and portal scales. Add them only after the group understands the specific rule each key changes, and keep a written copy of the final command for later troubleshooting.

Which preset should a group choose?

Iron Gate lists Normal, Casual, Easy, Hard, Hardcore, Immersive, and Hammer presets. Normal is the best neutral starting point because it changes fewer expectations for players coming from ordinary Valheim worlds.

Preset choice	Use it when	What to watch for
Normal	The group wants familiar progression and room for selective tuning.	Individual friction points still need separate modifiers.
Casual	The group prioritizes relaxed progression and lower punishment.	Players should agree that reduced pressure is intentional.
Easy	New players need a gentler overall challenge.	Do not assume it changes every logistics rule the group wants.
Hard	Everyone wants a more demanding survival world.	Deaths and raids can compound for inexperienced players.
Hardcore	The group explicitly wants severe loss and accepts failed expeditions.	Do not use it as a surprise difficulty increase.
Immersive	The group wants a rule set centered on travel and survival immersion.	Confirm how it interacts with the group’s preferred portal and map rules.
Hammer	The world is primarily for construction and experimentation.	It is a different purpose from a normal progression server.

Because presets overwrite earlier modifiers, place the selected preset first, then add only the exceptions the group has approved. For example, use -preset normal -modifier resources more, not the reverse.

How do I create a private server that only the group can join?

1. Choose a stable host machine and install the official Valheim dedicated-server program.
2. Pick a world name that is not already used by another world on that machine.
3. Set a strong password and include -public 0 if the server should not appear in the public browser.
4. Select Steam networking by leaving -crossplay out, or add -crossplay if the group needs the relay backend.
5. Set the save and backup arguments before adding world modifiers.
6. Put -preset normal first among the world-rule arguments, then append approved modifiers.
7. Start the server and wait for Game server connected before asking players to join.
8. Have each player verify the intended world, password, and connection path before building a permanent base.

For tighter control, use the documented administration files. adminlist.txt identifies administrators, bannedlist.txt stores bans, and permittedlist.txt restricts access to listed users when the permitted list is in use. The in-game F5 console supports kicking, banning, unbanning, and listing bans.

What should I choose: self-hosting or a managed server?

Self-hosting gives the group direct control over launch arguments, world files, backups, and the machine running the server. A managed service generally replaces command-line editing with a control panel and handles routine restarts or file operations, but its exact workflow depends on the provider and is not a universal Valheim standard.

Consideration	Self-hosted	Managed service
Configuration	Edit the startup command and server files directly.	Enter settings in a provider panel, if supported.
Networking	Steam requires router forwarding and firewall work; Crossplay avoids internet forwarding.	The provider normally supplies the internet-facing connection, but the panel’s supported backend still matters.
Backups	You choose retention and can copy files to separate storage.	Backup controls vary; verify retention and download options before trusting the world to them.
Availability	Depends on the host machine, power, and home connection.	Usually designed for continuous availability, subject to the provider’s service terms.
Control	Full access to world files and administration lists.	Convenience may come with panel limits or provider-specific file access.

Choose self-hosting when one player is comfortable maintaining a machine and wants complete file control. Choose managed hosting when continuous availability and simpler restarts matter more than direct infrastructure control. In either case, keep an independent copy of a valuable world.

How do I troubleshoot a server that does not appear or accept connections?

The server never reaches “Game server connected”

• Check that the world name, password, and argument syntax are quoted correctly where spaces appear.
• Remove recently added modifiers and start with a minimal Normal command to identify a bad override.
• Confirm that the server program is using the intended world directory and has permission to write saves.
• Look for another process already using the selected port.

The server starts but remote Steam players cannot join

• Verify forwarding for both 2456 and 2457 to the current host IP.
• Confirm the host firewall allows the dedicated-server program and the selected network profile.
• Test from a genuinely external connection, not only another device on the same home network.
• If the internet service uses carrier-grade NAT or the router cannot forward ports, switch to -crossplay.

Players join but the wrong rules are active

• Read the complete launch command from left to right.
• Move the preset before every modifier.
• Check for duplicate arguments, where a later value can replace an earlier one.
• Restart the server after changing startup arguments; editing a command does not alter a running process.

The world rolled back or a save is missing

• Stop the server cleanly and avoid overwriting the only remaining copy.
• Inspect the automatic backup set and identify the newest known-good world state.
• Restore to a separate working copy first, then verify that the world opens before replacing the live files.
• After recovery, keep an off-server copy and confirm that the save and backup intervals are still present in the command.

What is a sensible change process for an established group?

1. Write down the current command, world name, active backend, and backup policy.
2. Ask the group to identify one problem, such as excessive gathering time or disruptive raids.
3. Change one setting on a scheduled maintenance restart.
4. Announce the exact modifier and its practical effect before players log in.
5. Play long enough to judge that single change, then keep it, revert it, or adjust a second axis.
6. Copy the final command and the date of the change into the group’s documentation.

This method prevents a common failure mode: changing combat, resources, portals, and death penalties simultaneously, then being unable to tell which adjustment solved or created the problem. It also gives absent players a reliable explanation of why the world feels different.

What should the final configuration look like?

For a typical mixed group, use a password-protected private Normal world, Steam networking when port forwarding is available, -public 0, the documented save and rolling-backup values, normal raids and portals, and no Hardcore death penalty. Add -modifier resources more only when session length makes ordinary gathering a meaningful obstacle. Move to Crossplay when platform reach or router limitations outweigh the convenience of direct Steam networking.

Frequently Asked Questions

Can I change Valheim server settings after the world has already been created?

Yes. Most startup arguments can be changed by stopping the server, editing its launch command, and starting it again. Make a backup first, because changing a rule can alter how players experience the existing world and some settings may not undo past losses.

Do Valheim dedicated servers need to run all the time?

No. Players can only enter while the server process and host machine are running. A scheduled start or managed service can improve availability, but it does not replace testing saves and backups.

Can I use a permitted list and a password together?

You can configure both, but the permitted list becomes the decisive membership control once it is populated. Anyone not listed is refused even if they know the password, so maintain the file whenever the group roster changes.

Where are Valheim dedicated-server world files stored?

Iron Gate’s official guide documents the save locations for the dedicated server. Use that documented path to identify the active world and backup files, and copy them only after a clean shutdown so you do not capture an incomplete write.