Changed

• Rewritten README. Same mod, clearer documentation: what it does and how to install it come first, then configuration, multiplayer behaviour, compatibility and troubleshooting. Every config table was checked against the plugin's own Config.Bind calls, so the settings, sections and defaults listed are the ones actually bound. No code changed in this release.

  discuss

Fixed

• Stacks above the vanilla limit are no longer destroyed when a world loads. The load-path guard targets one exact method, and Valheim 1.0 moved the clamp onto a different overload - the string-keyed one became a two-line forwarder holding no clamp at all. So the guard silently stopped guarding, and stored stacks were clamped on load and saved clamped, which destroys the excess permanently. Retargeted, and the guard still covers only the load path, so pickup, crafting and splitting keep vanilla's rules exactly as before.

  discuss

Added

• A group carrying items no boss will ever raise is now reported at startup, once, naming the group. Deep North is the first case: nothing in ProgressionTiers names it, so its items sit at the base multiplier however many bosses fall - and the progression summary deliberately omits tierless groups, so that was the one thing nothing would have mentioned.

  discuss

Changed

• Metals wait for their own biome now, like everything else does. Ore and bars are held out of the ramp on purpose, because hauling metal is pacing rather than an oversight - but which boss lifted that was a single global switch, and it cut the wrong way at both ends. Black metal got a bigger stack the moment Bonemass died, before the Plains had been seen; copper and tin sat at their vanilla thirty through the entire bronze age with the Elder long dead. Metals were the one thing in this mod not following the mod's own rule.

  Each metal now waits for the boss of the biome it comes from: copper and tin at the Elder, iron at Bonemass, silver at Moder, black metal at Yagluth. It asks the same question the multiplier already asks of the same item, so the two cannot drift apart. The pacing survives - never a bigger stack of a metal before you are established where it is mined - and in practice only copper, tin and iron move, since Bonemass is always down long before silver is worth carrying.

  discuss

• LiftPortalRuleAt is removed. Naming one biome for every metal was exactly what was wrong, so there is nothing left for it to say. An orphan line in an existing config file is harmless.

  discuss

• The item list says metal-held instead of portal-blocked, and names that metal's own boss rather than one answer copied across all of them. The old word described the flag used to FIND the metals rather than the rule being applied, and it read as though the mod had opinions about portals. It does not: nothing here reads or writes what may go through one, and IncludeNonTeleportable now says so plainly - it is about stack size and nothing else.

  discuss

Fixed

• Stack sizes were wrong for a lot of items, permanently, and quietly. The biome index was lying three ways. BlackMetal sat in the plains while BoltBlackmetal sat in the meadows, in the same file: the bolt is black metal, wood and feathers, and on the first pass the bar had not been mapped yet - it is a blast furnace conversion rather than a drop - so the recipe answered from the wood alone. Nineteen recipe outputs were frozen that way. Separately the meadows tier carried Mistlands and Ashlands drops - carapace, charred bone, entrails, the Draugr, Seeker and Fuling trophies - because vanilla ships rows whose biome mask says Meadows and whose spawn is gated behind a global key, and the mask was read without the gate. Twelve rows do this. Both were permanent rather than transient because every writer took the earliest answer and refused every later one, so a wrong first pass could never be corrected.

  discuss

Changed

• BiomeIndex moves to Longhouse Core's shared source rather than being owned here. It is compiled into this mod, not into Core's DLL, so Core is unchanged and remains a soft dependency.

  discuss

Fixed

• 1.0.3's package contained 1.0.2's DLL. The publish zipped a stale staging folder, so the load-guard fix below never actually shipped under that number. This version is the same code, packaged from a fresh build. 1.0.3 should not be installed.

  discuss

Fixed

• Stored stacks survive loading. Seen on live: a chest holding 100 greydwarf eyes read 50/100 after a relog, the other 50 destroyed. For a moment after login - before the server's progression keys arrive - every stack limit is briefly vanilla again, the relogging player owns the chests around them, and the game's inventory loader clamps every stored stack to the limit of that moment. The clamp is now removed from the load path, and only there: an over-limit stack shows as 100/50 for a few seconds and normalises when the real limits land, where the clamped half of a stack was simply gone.

  discuss

Fixed

• The stack cap no longer shrinks items whose vanilla stack already exceeds it. It was written as a ceiling on the multiplied result, which quietly cut coins from their vanilla 999 to the default cap of 200 - the one item in the game above the cap. The cap now limits growth only; anything at or above it keeps its vanilla stack.

  discuss

Fixed

• The key hook marks rather than acts. The flag is drained in Update, which is the first moment the whole list is certainly in. As a side effect a connect's worth of keys is now one walk of the item database instead of one walk per key.

  discuss

Verified in play

Wood at 100 and blueberries at 50 on a world with Eikthyr down, with copper ore still portal-blocked. The biome index, the tier ramp, the portal rule and the retune when a world's keys arrive were all confirmed on a real client.

Not yet seen: a boss dying mid-session and the stacks moving without a restart. The path is exercised on every world load; what is unproven is that one arrival.

Hoard is now Yoke

• The plugin GUID is now ezomic.valheim.yoke, so the config file is renamed with it. Hoard's config is adopted automatically on the first run under the new name, before anything binds, so settings carry over unchanged. That matters more than it sounds: BiomeOverrides runs to about a hundred entries, and a silent reset would drop the mod back to derived-only placement with nothing in the log to explain why the ore stopped stacking.

  discuss

• The assembly, namespace and plugin class follow the name.

  discuss

• The icon is redrawn: two stacks under a notched bar, rendered through the suite's shared icon script so it sits correctly beside the others.

  discuss

Everything is placed

• Spawners. A greydwarf nest, a surtling geyser, the skeleton piles in a crypt: the creature is not in the world's spawn table, the thing that makes it is. Walking SpawnArea finds them, which is where most of the missing trophies were.

  discuss

• Bosses place their own drops. A boss stands in a location so nothing else can see it, but the boss prefab knows the global key its death sets and the tier table knows which biome that key belongs to. Moder's trophy is a Mountain item because Moder's key is the Mountain's key, since neither side names an item, and a modded boss added to ProgressionTiers brings its drops with it.

  discuss

• BiomeOverrides now ships the roots that live inside locations: ore deposits, dungeon loot, dvergr and charred material, fish, and the trophies of creatures that only appear in a location. Roots, not a full list: the recipe pass turns each one into everything made from it, so cooked fish, chicken, spices and meads all placed themselves from these.

  discuss

A boss raises the biome it guards

• ZoneSystem.m_vegetation: a copper deposit is Black Forest and the deposit says it drops copper ore, so copper ore is Black Forest.

  discuss

• The spawn tables plus CharacterDrop: Fulings are Plains, so black metal scrap is Plains.

  discuss

• Recipes, smelters, cooking stations and fermenters, where a made thing takes the biome of its latest ingredient. Barley is Plains, so flour is, so dough is, so bread is, across a mill, a recipe and an oven. Every mead lands off the fermenter the same way.

  discuss

• BiomeOverrides, for what none of that reaches.

  discuss

Fixed

• The index rebuilt once per item while incomplete, walking every prefab in the scene a thousand times per pass. It is built once per pass now.

  discuss

• SpawnSystem.Awake fires more than once in a loaded world; the rebuild is guarded so it happens on the first one only.

  discuss

• Overrides were applied after the conversions, so copper bars came out unplaced. The smelter pass went looking for copper ore before the override had put it on the map. They are applied before the derivation as well as after.

  discuss

• Conversions and recipes ran in sequence, which left bread unplaced whatever the pass count, because the step it waited on lived in the other list. They interleave until it settles.

  discuss

Progression finishes at Bonemass

• Ten percent is imperceptible. Wood going 100 to 110 is not a reward anyone feels, and it lands at the moment a boss dies, when there is a great deal else to notice.

  discuss

• The numbers read as a bug. Vanilla stacks are round: 20, 30, 50, 100. Compounding produces 121, 133, 146, 177, which look like a fault rather than a design.

  discuss

• It drifts past the honest amount. Building ended at 3.54x, well beyond the flat 2x this mod ships and defends. A narrow table that quietly widens forever is the x10 mod taking the long way round.

  discuss

Every later boss adds ten percent (off by default since 0.11.1)

• ProgressionOrder is new, because "later" needs an order and the tier table never had one. A key that is not listed still unlocks its own group; it simply never counts as before or after anything, which is the honest answer for a modded boss key somebody added to the tiers and not the order.

  discuss

• A group still at the base multiplier does not compound. Untouched is untouched, not "unlocked at zero percent".

  discuss

The table is shorter on purpose

• The portal rule now says when it lifts. Ore read portal-blocked, which is a half-truth once a metal tier exists. It now reads portal-blocked until defeated_bonemass. Tallies match on the rule, so a qualified note still counts under it.

  discuss

• "Earned so far" lists only groups a tier can reach. Printing the others at 1x read as a promise that some boss would come for them, and with this table none will.

  discuss

Each boss raises one kind of stack

• The groups are read off the game's own systems. Building material is whatever appears as a build cost on the Hammer's piece table, crops are the Cultivator's, metal is whatever a portal refuses. So an item a content mod adds lands in the right group by itself, and there is no list here to go stale.

  discuss

• An earned metal tier lifts the portal rule. The haul is real pacing during the first copper runs and paid off by the boss that hands you the iron age. IncludeNonTeleportable stays for anyone who wants it sooner.

  discuss

• The item list names the boss each group is waiting for, so "why is my wood still 50" is answered in the file rather than by reading the tier table.

  discuss

It hangs on the world's progress, not each player's

Stack size lives on the item prefab, so per-player stacks would mean two clients holding different item databases. One drops a hundred wood in a shared chest, the other opens it holding a slot over its own maximum, and the next move writes back through the smaller rules. Global keys are world state pushed to every client, so everyone computes the same answer with no new networking, and since keys only accumulate the multiplier only ever rises.

Read through the string global-key lookup, not the GlobalKeys enum: that enum stops at defeated_goblinking in this build, with no defeated_queen or defeated_fader member, so the enum route would have silently capped the ramp at the Plains.

Utangard decides what counts, when it is installed

Utangard opens a biome only when every member of the group was personally at that boss's death, which is not the same as the boss having died in the world. Yoke now asks it rather than reading the raw key, so stacks never arrive for a biome Utangard still has fenced off. Soft dependency; DeferToUtangard = false turns it off, and neither mod needs the other.

Changed

• The item list gained a Group column, sorts by group, and its header counts describe the state of the database rather than the last pass, so they no longer appear to contradict the Retuned n line in the log, which counts only what that pass moved.

  discuss

Added

• An item list, written beside the config on every run. ezomic.valheim.yoke.items.txt. Every item in the game, its vanilla stack size and weight, what Yoke made them, and which rule left it alone when it did nothing. Off with WriteItemList = false.

  ExcludeItems takes prefab names and prefab names are not guessable: raspberries are Raspberry and a draugr's arrow is draugr_arrow, so a per-item setting without a list beside it is a setting nobody can spell. It doubles as the answer to "why did this item not change", which is the only question a mod like this ever gets, and it answers it without asking anyone to turn on Verbose and read a log.

  The rows are built by the tuning pass as it runs rather than by a second walk over the database. A separate walk would be a second copy of the eligibility rules, and the first thing it would do is disagree with the real one.

  discuss

Fixed

• Weights are written with a decimal point on every machine. float.ToString follows the machine's locale, so on a Dutch install resin came out as 0,3, and a comma in a file whose other numbers come from a .cfg that uses points, sitting next to a column of integers. Both the item list and the Verbose log now format invariantly.

  discuss

Changed

• The pass logs three counts rather than two: changed, already at those values, and left alone. They add up to the item count now. Retuned 0 on the second setup of a session reads like a failure until you know the other items were already at the right numbers.

  discuss

Core is optional

• Core is now a soft dependency rather than a hard one. Yoke installs and runs on its own, and the Thunderstore package no longer drags Core in with it. Present, Core is used; absent, nothing here is degraded.

  discuss

• What is given up standing alone is the version gate, not the mod. Item data that differs between two ends desyncs inventories, and without Core nothing reports that. The ObjectDB.CopyOtherDB patch still puts a joining client on the server's numbers, which covers the common case on its own. Solo, none of it applies.

  discuss

• The registration call sits in its own method that is never inlined, because the JIT resolves the assemblies a method needs when it first compiles that method. A Core call written directly into Awake would drag the assembly in before the installed-check could prevent it, and the missing-assembly exception would land during plugin load, which is precisely the failure the soft dependency exists to avoid.

  discuss

Stacks

• Stacks double. Wood 50 becomes 100, with a hard ceiling of 200 whatever the multiplier says.

  discuss

• Weight is untouched by default. The carry limit still decides what comes home, which is the half of the logistics problem worth keeping.

  discuss

• Ore and metal bars are not modified at all. Metal cannot go through a portal, so hauling it by cart and boat is deliberate pacing rather than an oversight. One config line turns it on if you disagree.

  discuss

• Equipment is never made stackable. Only items with a vanilla stack size above 1 are touched, because anything that does not stack in vanilla carries per-item durability and quality, and collapsing several into a count throws all but one of those away silently.

  discuss

Why the defaults are low

The usual version of this mod ships x10 stacks and halved weight, which does not make Valheim more convenient so much as remove a system from it. The tedium and the difficulty are the same mechanic seen from two sides, so the defaults here fix the annoying half and leave the interesting half alone. Everything is a knob if you want the easy version.

Correctness

• Both ObjectDB.Awake and ObjectDB.CopyOtherDB are patched. Awake builds the database at startup and CopyOtherDB rebuilds it when a world loads, so patching only the first means untouched values quietly replace yours the moment you join a game.

  discuss

• Every value is computed from the item's original, captured the first time it is seen and never overwritten. The database is set up more than once, and a mod that multiplies whatever it currently finds squares its own multiplier on the second pass.

  discuss

• Loads on dedicated servers, and declares to Core's version gate so a host and a client cannot disagree about stack sizes.

  discuss

Known limits

• If another mod changes an item before this one first sees it, that changed value is what gets recorded as the original.

  discuss