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.

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.

The batch modifier does nothing. The key was read with UnityEngine.Input.GetKey, and Valheim runs on the new Input System, where the legacy Input class does not reliably see a KeyCode. So holding Shift while using a smelter added one ore instead of three, with the config file holding exactly the right key and nothing in any log. Read through ZInput now, which is the game's own reader, and refused while chat, the console or a text field has focus.

A blast furnace could end up holding more ore than its capacity. Vanilla checks capacity only in OnAddOre, on the client, against GetQueueSize(); RPC_AddOre on the owner has no check at all and writes the queue entry unconditionally. On a dedicated server that queue size is a round trip behind, so pressing again before the ZDO caught up made every batch count from the same stale number, and the overfilled state then persists. The predicted level is now tracked per station across presses, with the ZDO's own value taking over the moment it catches up.

Batched ore was sent with the wrong RPC signature. Smelter registers RPC_AddOre as Register<string, bool> and vanilla sends (name, item.m_cheated); the extra adds sent the name alone, leaving the receiver to read a bool off the end of the package. Matches the game's call now.

Far sight and Weatherly, two runestones that widen what the world gives back rather than what you do to it. Far sight multiplies Minimap.m_exploreRadius by 5% a rank, so the map uncovers further as you walk, with the capstone worth another 10%. Weatherly is the sailing one: Ship.GetWindAngleFactor kills the sail inside a hard cone around dead upwind, and that cone is the only reason tacking exists, so the card puts a floor under it and lets you point nearer the wind before the sail dies. Its capstone is 20% more speed while beating upwind.

Deliberately not more move speed. That card is capped at 10% from a single source because a permanent speed buff is always on, never noticed while you have it, and a player told us Rist had made his unmodded playthroughs feel worse. Neither of these follows you home: a bigger map radius is felt only on ground you have not walked, and the wind cone only at sea with a sail up. Weatherly leaves the across-the-wind term alone and is clamped so upwind can never beat a beam reach, since raising that term would just be a flat speed bonus in a hat.

A Rist line above other players' heads - level, total XP, and days since their last death - written into the game's own nameplate rather than drawn beside it, so it inherits the plate's font, fade and distance rules. ShowPlate turns it off, PlateFormat is the whole of the presentation: fields, order, colours, and whether it wraps to a second line.

The HUD half was one postfix. The data half is why this is more than that: nothing about another player's Rist state is on the wire, since the server pushes a record to the peer it belongs to and to nobody else. Each client now publishes its own level, XP and last-death day onto its own character's network object, which every client in range already replicates. The server cannot publish them instead - a write to a network object you do not own is discarded in silence - so a modded client can lie about its own plate. Accepted knowingly: the plate is decoration and the server's ledger still decides every pick.

Days alive counts from the day the plate first saw a character, not from its creation. The game keeps no birthday, so every existing character reads 0 on the day this ships.

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.

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.

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.

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.

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.