Valheim world modifiers: choose presets, sliders and rules

Valheim world modifiers let the world owner combine a preset, individual slider choices and checkbox rules into a shared campaign profile. Start with the experience your crew wants, then choose the controls that support it. This guide gives you a verified catalog of the documented choices, the questions to settle before changing them, and a way to record your agreement. It covers choosing rules, rather than installing a server or performing a save rollback. The identifiers below were checked against the manual shipped with public dedicated-server build 25390671 on September 21, 2026; that documentation check is not a gameplay test.

Read Valheim world modifiers as three different controls#

Treat a preset as a bundle, a slider as an individual choice, and a checkbox as a separate rule. Keeping those categories apart makes the configuration easier to explain to friends and easier for the owner to maintain.

The official dedicated-server manual documents these as three argument families. Its list matches page 3 of the distributed manual checked for this guide. A hosting panel may present the same underlying choices differently, so use the game’s names to describe your requirements before looking for a particular button.

Do not mix the campaign profile with operational settings. A password answers who can enter; a modifier answers how the shared world is configured. Similarly, being an administrator does not mean every preference becomes an individual player setting. Ask the world owner to coordinate changes.

A useful first check is to read your proposed profile aloud without mentioning the provider. If the description is only “the third dropdown in the panel,” another operator cannot reliably reproduce it. Record the game control and its value, then add the panel location as a separate note.

Choose a preset before agreeing exceptions#

Choose the starting preset first, inspect its resulting settings, and then write down the exceptions your crew actually wants. The manual recognizes these seven names:

These questions are a selection worksheet, not a specification of every value inside each bundle. Read the current game’s description and resulting controls before accepting a preset. The shipped server manual enumerates valid names but does not provide a complete composition table or every gameplay multiplier.

Avoid choosing from the name alone. Two friends can both request “harder Valheim” while meaning different things: one wants demanding fights, the other wants a longer recovery after mistakes. Agree on those separately instead of assuming that a single label communicates the whole campaign.

For an existing world, record its current profile before experimenting. Choosing Normal is a settings decision; it is not evidence that previous losses, construction or character changes have been reversed. A configuration record and a recoverable save serve different purposes. Keep both when the established campaign matters.

Match combat and death penalties to the crew#

Decide how challenging encounters should feel separately from what the group accepts after a death. This keeps a difficult fight from quietly becoming an agreement about a much longer recovery session.

The checked manual lists the following individual argument values:

Use those identifiers when matching a server control to the documentation. They are not a promise of particular damage or skill-loss percentages. For the detailed effect of a selected position, read the description in the current game before the owner applies it to the campaign.

Consider a crew with one experienced fighter and two new players. The experienced player may be comfortable with a difficult encounter, while the others still need time to learn it. Ask whether the group’s priority is practicing fights, making steady progression, or accepting severe setbacks together. That conversation gives the owner a reason for each choice.

Also agree who helps after a death. A setting can change the rules, but it cannot make an absent friend available for a recovery trip. If you usually have short sessions, discuss how much of one evening the crew is willing to spend getting back to where it started.

Check the proposal with the least experienced regular participant before approving it. If that person cannot explain what happens after a mistake, the profile is not ready. Use a separate test campaign for unfamiliar choices rather than learning their consequences through the only copy of a long-running world.

Agree resource, raid and portal tradeoffs separately#

Set gathering pace, event pressure and travel rules as three decisions. A crew can want slower exploration while also wanting less repetitive material collection; there is no requirement to push every slider in the same direction.

For resources, start with a concrete frustration. “We cannot finish the dock during our weekly session” is a more useful input than “make everything faster.” Identify the gathering activity that consumes the time, read the selected resource setting’s description, and check whether it addresses that activity. Do not assume one rate changes every source or process identically.

For raids, distinguish the event setting from the broader danger of the world. If the complaint is about interruptions at home, record that as the problem to evaluate. Do not translate a relative slider label into an invented guarantee such as one raid every other night, or assume the choice removes every ordinary threat.

For portals, agree on the travel experience before a distant expedition. Friends should know whether the chosen rules fit their plan for transporting supplies and returning home. The manual lists accepted tokens but does not explain every item restriction associated with each position. Confirm the current in-game description instead of guessing from hard or veryhard.

Finally, give the profile a review point: after the next shared session, ask whether the dock progressed, interruptions were acceptable, and travel matched expectations. Those observations help the owner adjust the relevant category instead of replacing the whole preset because one part disappointed the crew.

Review checkbox rules outside the sliders#

Review the checkbox rules separately so an important choice does not disappear behind the preset name. The manual documents four keys:

These are documented key names and planning questions, not a complete model of every creature, recipe or event trigger. If your campaign depends on a specific exception, settle that exception before enabling the rule. In particular, do not infer the full raid eligibility logic from a checkbox label.

For a navigation-focused campaign, decide how friends will describe meeting points. For a group with uneven progress, discuss how much time the most advanced player will spend helping newer participants. These agreements remain useful even after the owner has selected the technical settings.

If a provider offers additional controls, ask whether they are native settings, a provider feature or a mod. Do not silently treat an extra panel option as one of these four documented keys. That distinction matters when you later move the world or change how it is hosted.

Keep the preset before its exceptions#

Apply the preset before individual modifier exceptions: the documented ordering prevents the preset from overwriting choices that came earlier. For example, this is an illustrative argument fragment, not a complete server startup command:

-preset hard -modifier raids none

Read it as a starting bundle followed by one explicit exception. Reversing those operations risks replacing the exception with the later preset. The useful lesson is the order of decisions, even when your panel generates the actual launch arguments for you.

Before applying the profile, find out which configuration really starts your server. A copied script, a service, a container configuration and a provider panel can put the controls in different places. Use the dedicated-server route comparison if you still need to choose who operates that environment.

The manual’s individual-value lists also do not include normal. Normal is listed as a preset; a familiar menu label is not enough evidence to invent an individual reset argument. Likewise, do not assume that deleting a launch argument necessarily reverses a value already saved with the world.

Check the effective profile after the owner applies it using the procedure for that hosting route. If it differs from the rule card, investigate the active configuration and ordering before editing more settings. A server starting successfully tells you the process runs; it does not by itself prove that every intended exception became the final world profile.

When you are ready to apply modifier arguments, keep the preset before its individual exceptions and verify the effective startup line.

Protect achievement goals before applying the profile#

Check achievement consequences before changing an achievement-focused campaign. Iron Gate’s 1.0 FAQ says some modifiers block certain achievements and specifically identifies hammer-mode as a temporary cheat state. It does not establish a universal safe list for every slider combination.

Ask each participant whether a particular achievement matters. “We want achievements” may mean one person wants ordinary progression credit while another is pursuing a challenge with particular conditions. Record the actual goal and read its current requirements alongside the game’s warning before making a shared decision.

The September 11 hotfix notes describe a Steam 1.0.12 opt-in for achievements after devcommands or mods, plus a notification when eligibility returns. That dated feature is not a guarantee for every platform, every achievement or every character history. Do not use it as permission to promise that a changed profile has no consequences.

The September 18 patch 1.0.15 was also reviewed for this guide; it did not announce a modifier-value change. Check later official notes when planning a future change. A previous guide’s date cannot establish the behavior of the build your crew is running tonight.

If an essential achievement condition remains unclear, leave the campaign’s current profile alone while you resolve it. The group can still discuss a proposed profile or experiment separately without treating an unanswered eligibility question as approval.

Share a rule card and choose who maintains it#

Finish with a short, dated rule card that another authorized owner can understand. The card should explain what the crew chose, why it chose it, and when the group will review the result.

1. Record the current baseline

   Note the selected world, current build, preset, individual choices and enabled checkbox rules. Identify the person with access to the actual configuration. Keep the existing record when proposing a replacement.

2. Write the proposed changes and reasons

   Attach one reason to each exception, such as reducing time spent gathering for a shared build. Include achievement goals and any behavior that still needs checking. Let every regular participant review the proposal.

3. Protect the campaign before applying anything

   Preserve the complete world data required by the current version, and relevant character data when the experiment could affect it. Use the established procedure for your hosting route; this checklist does not claim that a copied file has been successfully restored.

4. Check the result and date the review

   Have the owner verify the resulting profile against the card. After a representative shared session, collect the crew’s observations and decide whether to keep the choices or schedule another controlled change.

Self-hosted configuration remains a free option if someone is comfortable maintaining it. If repeated changes exceed that person’s appetite for administration, use the hosting selection checklist to ask about configuration access, delegated ownership and recovery controls.

For a managed world, we recommend Game Hosting’s Valheim plans with integrated world settings and free backups. Verify which changes require a restart and protect the world before altering its rules. Renting removes home-machine administration; the agreement about how your crew plays still belongs to the crew.