DropNSpawn

DropNSpawn

Customize Valheim's drops, loot, spawners, world spawning, and raids with YAML. Use generated references to find prefab names and values, then edit only what you need.

| Character drops | Object loot | Spawners | | --- | --- | --- | | | | |

What you can change

| Domain | Controls | | --- | --- | | character | Creature drops, quantities, chances, level scaling, and stacked loot | | object | Chests, pickables, fish, trees, rocks, destructibles, and their loot | | spawner | SpawnArea and CreatureSpawner tables, intervals, limits, levels, and location rules | | spawnsystem | World spawn tables, biomes, time of day, and progression requirements | | events | Raid definitions, spawn lists, conditions, and scheduling |

Install

Install the same DropNSpawn version and its dependencies on the server and all clients. A mod manager is the simplest option; for manual installation, place DropNSpawn.dll in BepInEx/plugins/.

Requires BepInExPack Valheim 5.4.2351. Expand World Data is optional: DNS's basic drops, spawners, world spawning, raids, and native faction overrides work without it. Install EWD 1.71 or newer on the server and clients to use spawn data/fields/objects, event startCommands/endCommands, or EWD custom biomes. Without EWD, nonempty extension settings reject the affected domain's configuration update and retain its previous accepted configuration; they are not silently ignored. Empty extension fields are allowed.

Character-drop handling has been updated for Valheim 1.0.20. See the earlier compatibility notes for reviewed EWD builds and existing-YAML update notes. Restart after changing the installed mod set; mixed EWD capability between peers is not supported for EWD-dependent configurations.

Quick start

1. Start the game or server and load a world once to generate the configuration files.
2. Open BepInEx/config/DropNSpawn/ and find the relevant DNS_<domain>.reference.yml.
3. Copy the entries you want to customize into DNS_<domain>.yml, or a supplemental file such as DNS_character_wolves.yml.
4. Save. Loaded YAML files reload at runtime; on a multiplayer server, edit the server's files.

For example, put this in DNS_character.yml to replace Lox loot:

- prefab: Lox
  characterDrop:
    drops:
    - item: LoxMeat
      amount: 4~6
    - item: LoxPelt
      amount: 2~3
    - item: TrophyLox
      chance: 0.1
      levelMultiplier: false

Global options live in BepInEx/config/sighsorry.DropNSpawn.cfg. All five domains start enabled; toggle them under 4 - Domains. Loot scaling, stacked drops, trophy scaling, and event scheduling have their own settings; most server-facing settings sync from the server.

Character drops support levelMultiplierNotAmount (default false). With both levelMultiplier: true and levelMultiplierNotAmount: true, stars increase the drop chance without multiplying its amount. Original prefab flags are preserved; YAML overrides use their configured flags.

Under 2 - Character, chance-only drop chance scaling controls these drops regardless of item type, including original game drops when Character Overrides is disabled. The default Linear uses chance-only drop chance increase per star (%) (integer 0–100, default 50). Each star adds that percentage of the base chance: with a 10% base, 50 gives 10%, 15%, 20%, while 25 gives 10%, 12.5%, 15%. Zero keeps the base chance at every star level. The final chance is capped at 100%. Select Vanilla to ignore this increase setting and keep the game's exponential chance scaling: 10%, 20%, 40%, 80%. These settings change no amounts and are independent of character loot system, the additional-loot amount percentages, and global trophy level multiplier. The existing CLLC handoff disables DNS chance scaling when CLLC is loaded. Changes apply to subsequent drop rolls and are synchronized from the server; the same rate applies to creatures and bosses.

If multiple rows share a drop prefab and any row has both flags true, DNS retains its existing policy of excluding all those rows from amount scaling. Only the chance-only rows use the selected chance mode; ordinary rows retain their original chance and amount rules. This exception also applies to global trophy scaling and custom stacked/limited drops; other drop prefabs keep their configured DNS scaling. Resource multipliers, onePerPlayer, amount limits, and stacking still apply. Update the server and all clients together when using this build.

For dropInStack, omitted/null inherits global drop in stack, explicit true enables stacks, and explicit false keeps separate drops. The stack blacklist always wins. An explicit YAML levelMultiplier: false also opts a trophy row out of global trophy amount scaling; it no longer gets overridden by that option. Original game rows without a YAML override retain their global eligibility. See the override guide for defaults, domain switches and blacklist exceptions.