Confirm with your password

Wonderland

Strictly server-side Valheim 1.0 mod: automation, world governance, status effects, Discord notify, Zero client install, NOW WITH VANILLA CLIENT ENFORCEMENT! Full crossplay. See README.

Changelog & versions

· Website · 💗 Donate

Stars
1
Downloads
86
Version
1.12.1
Updated
Author
Wubarrk
Virus scan
✓ Scan successful
Runs on
Server-only

Compatibility

Required 1

Install these too — Gale pulls them in for you.

Pairs well with 4

Not required, but they work well together.

Description

🌐 Wonderland

Valheim Mod Multiplayer Compatible Framework Crossplay Valheim 1.0

No client install needed. The server does the work. Built and live-tested on Valheim 1.0.

Wonderland is a strictly server-side automation and world-governance mod: every feature below runs entirely on the dedicated server, operating on the world's raw ZDO data instead of live game objects — which is what makes it work on a real headless server at all, with nobody connecting needing to install a thing. Steam, Xbox, PlayFab, and full crossplay parties all get the identical experience.


👑 Automatic World Progression Ledger & Anti-Twink Security

[!IMPORTANT] "The world levels up when the boss falls, and the head is hung on the stones. That is our ledger."
Wonderland dynamically ties server gear progression ceilings, equipment surveillance, and anti-cheat kicking directly to Valheim's persistent boss defeat registry (defeated_<boss>). No more players connecting with endgame gear (twinking) to bypass your server's survival milestones.
🛡️ Admin Freedom: Authenticated admins on adminlist.txt are 100% exempt from all checks (EquipmentGuardAdminBypass = true) — an admin can wield, wear, spawn, or store whatever they want, whenever they want!

How Progression Works

  1. The World Level-Up Record: In Valheim, when a boss falls and its trophy is hung at the sacrificial stones, the dedicated server permanently registers an authoritative world global key (defeated_gdking, defeated_bonemass, etc.). Wonderland reads these keys in real time to establish the active allowed tier.
  2. Baseline: Starting at Black Forest (Skipping Eikthyr): Because Wonderland's Starter Grant equips arriving Vikings with Bronze tools and a Karve on day one, the baseline world tier begins at BlackForest. Eikthyr is bypassed for tier gating.
  3. Defeating The Elder Unlocks the Iron Age: Until The Elder falls, Iron armor, banded shields, and swamp weapons are prohibited — Vikings equipping Iron are kicked or flagged. Defeating The Elder immediately unlocks the Swamp tier.
  4. Real-Time Live Unlock & Zero False Positives: The instant a boss dies anywhere in the world, the server steps up the world tier, proclaims the milestone across the server and Discord, and flushes all player violation caches so players crafting new gear are never falsely warned or kicked.
  5. Dual Enforcers:
    • EquipmentGuard: Continuously monitors equipped visual weapons, shields, armor, capes, and magic staves & robes on player character ZDOs, plus impossible upgrade levels (gear upgraded past its base cap at Valheim 1.0's upgrader stations is recognized and exempt). Wielding prohibited gear logs to wonderland_security.log, and optionally auto-kicks the violator (EquipmentGuardKick = true).
    • ItemSanityGuard: Sweeps player-built chests to detect and optionally purge smuggled endgame gear or developer cheat items stashed ahead of progression.
  6. Admin Immunity: Authenticated server administrators on adminlist.txt completely bypass all equipment, quality, and progression tier checks (EquipmentGuardAdminBypass = true). Admins can do whatever with whatever!
  7. Raw Drops Are Free, Processed & Crafted Is Gated: Wonderland does not guess tiers from item names. At world start it reads the game's own recipes, smelter and cooking conversions, and crafting station build costs, and an item's tier is simply the highest boss-gated ingredient or station anywhere in its crafting chain: The Elder unlocks the crypts and therefore iron, Bonemass leads you to silver, Moder's tear builds the artisan table and everything downstream of it (black metal, linen, barley flour), the Mistlands stations gate Mistlands gear, and flametal gates the Ashlands. Anything that drops straight into your bag with no recipe behind it is unrestricted: the scrap, pelts, needles, barley, and mushrooms you carried home from a biome you dared to visit are never confiscated. The derived table is written every boot to BepInEx/config/Wonderland.ProgressionTiers.txt (one line per item with the tier and the reason), and any item can be pinned to a different tier, or freed entirely, with ProgressionItemExemptions (Prefab:Tier or just Prefab) live with zero server restarts.

Progression Unlock Matrix

World State / Boss Defeated Global Key Unlocked Max Tier Allowed Gear & Materials Gated / Blocked Ahead of Progression
Baseline (Day 1 / Pre-Elder) (None) BlackForest Every raw drop from any biome, Bronze weapons/armor/tools, Troll hide, Root armor, Chitin, everything from the cauldron Iron, Silver, Black metal, Linen, Eitr, Flametal and all gear made from them
The Elder slain defeated_gdking Swamp Iron armor & weapons, Banded shield, Huntsman bow, Iron pickaxe, Iron nails Silver, Black metal, Eitr, Flametal
Bonemass slain defeated_bonemass Mountain Silver weapons, Wolf armor, Drake helm, Frostner, Fang spear, Lox cape (silver-trimmed) Black metal, Eitr, Flametal
Moder slain defeated_dragon Plains Black metal weapons & shields, Padded armor, Porcupine, Linen, Bread and every windmill/oven food Black forge & galdr table gear, Eitr, Flametal
Yagluth slain defeated_goblinking Mistlands Carapace gear, all Eitr magic staves & robes, Krom, Mistwalker, Feather cape, refined Eitr Flametal, Ashlands gear
The Queen slain defeated_queen Ashlands Flametal weapons & armor, Ashlands armor sets, Ashlands staves Bloodgold gear, Frost Foundry casts, Timberwood, Nornathread
Fader (Ashlands boss) slain defeated_fader DeepNorth Bloodgold weapons, armor, shields and staves, everything cast at the Frost Foundry - fully unrestricted end-game tier None

Raw drops - scrap, ore you cannot yet smelt, pelts, needles, barley, flax, mushrooms, sap, black marble, yggdrasil wood, trophies - are never gated, whatever biome they came from. The exact placement of every item, with the reason, is in BepInEx/config/Wonderland.ProgressionTiers.txt after each boot.


📜 Contents

🌱 Features

🧲 Vacuum & Auto-Harvest

Containers and carts quietly pull in matching ground items within a configurable radius — match-required, so a chest only tops up an item type it already holds and never has a new one sprout inside it. Mining spoils, harvest drops, anything on the ground near a linked container just walks itself home — within a couple of seconds of landing near you. What you are reaching for stays yours: a chest claims a stack for a moment before it takes it and steps aside the instant a player asks for it, so a pickup and a vacuum never both win. When unclaimed items settle, a subtle physics wakeup vector is applied so vanilla client physics immediately wakes the item's Rigidbody, ensuring it drops naturally under gravity rather than floating in mid-air. Swimming fish, a feast on the table and an egg warming by the fire are never touched. This includes ship cargo — a docked or beached Karve or VikingShip vacuums nearby matching items exactly like a chest does. A visual liquid splash and splash sound (vanilla's own fermenter effect vfx_fermenter_add and sfx_fermenter_add) play at the container on a successful pull via vanilla's native routed SpawnObject RPC, so it is clearly visible and audible to nearby players with nothing installed client-side; turn it off with VacuumEffectEnabled or customize the prefabs via VacuumEffectPrefab / VacuumSoundPrefab. Paired with this: pick one and the rest follow — press E on a single berry bush, mushroom or carrot and every ripe one of the same type within the radius is harvested with it, each drop landing exactly where its plant grew so a matching chest in range pulls the lot straight in — one keypress can put a whole carrot patch in the chest beside it. Ores, tar and dungeon loot are never swept. Exclusion lists (containers and items) keep this out of anything you want left alone.

🌊 All Items Float

All dropped items — ores, raw metals, scrap, tools, weapons, armor, trophies, and serpent scales — float on water instead of sinking to the ocean floor. Genuinely 100% server-side: vanilla clients see them bobbing and resting on the water surface, readily collected while swimming or sailing past, with zero client mods installed. Vanilla only attaches buoyancy components to wood, fish, and tombstones, while clients simulate physics on objects they own; Wonderland enhances server item prefabs, maintains surface elevation and server ownership on waterborne items, and immediately grants ownership when a player presses E or walks into auto-pickup range so pickup is instant. Items resting on coastal banks or river shores are verified against dry ground elevation so land items are never falsely lifted into the air. Configurable toggle (AllItemsFloatEnabled, default on), sweep interval, and surface elevation offset in 2 - Vacuum & Auto-Harvest.

⚖️ Carry Capacity

Scale player max carry weight completely server-side via Valheim 1.0's native World Modifier system (Game.m_carryWeightRate). Stock vanilla clients receive the rate via the vanilla GlobalKeys network channel, display the increased limit directly in their inventory GUI (e.g. 0 / 600), and enforce encumbrance and auto-pickup against that higher ceiling with no client mods. Configurable via CarryWeightMultiplier in 15 - World Modifiers & Capacity (default 2.0 = 600 lbs base / 900 with Megingjord; 1.0 is vanilla). Live config changes broadcast to all connected players immediately without a server restart.

🏃 Stamina Regen Rate

The same native World Modifier mechanism as Carry Capacity above, targeting Valheim's own Game.m_staminaRegenRate instead. StaminaRegenRateMultiplier (default 3.0) scales passive stamina regeneration for every connected player — completely server-side, arbitrary multiplier, zero client mods, live-updating the moment the config changes. Configurable in 15 - World Modifiers & Capacity. Note: this stacks multiplicatively, not additively, with any Status Effect Roster entry below that also boosts stamina regen — see that setting's own in-file description for the exact math before combining both.

🧪 Status Effect Roster

Keeps a curated set of existing vanilla status effects — potions, trinket effects, guardian powers — permanently active on every connected player, entirely server-side. This isn't a custom buff system: Wonderland can't invent a new status effect (nothing that isn't already compiled into every vanilla client can ever be granted this way), but it can remotely trigger any status effect a stock client already has, using the same vanilla networking channel the game itself uses for potions and guardian powers. Distinct effects genuinely stack — the server-triggered grant bypasses vanilla's usual "one potion effect per category" rule — so several roster entries combine into one compound buff.

Each roster slot is its own on/off switch in 16 - Status Effect Roster:

Slot Effect Default
GP_Moder +10% run speed, +300 carry weight, Frost Resistant, lets a boat sail against the wind On, while steering only (see note below)
Potion_hasty +15% run speed On
TrinketIronStamina +15% run speed On
Potion_swimmer -50% swim stamina cost only (run/jump untouched) On
TrinketChitinSwim -80% swim stamina cost only, +50% swim speed On
Warm Stamina + eitr regen ×2, naturally permanent Off
Potion_stamina_lingering Stamina regen +25% Off
Potion_tasty Stamina regen ×2, short-lived Off
Rested Health/stamina/eitr regen boost + faster skill gain, permanently Off
GP_Eikthyr -60% run/jump/swim stamina cost, all at once Off
GP_Bonemass Free blocking + resistance to physical damage Off
GP_TheElder +health regen, +damage chopping/mining Off
GP_Yagluth +damage all types, farming skill boost, lightning resistant Off
GP_Queen Free sneaking, eitr regen ×2, poison resistant Off

All three run-speed slots on by default stack to +40% run speed while actively steering a ship (+30% on land, since GP_Moder's +10% only applies at the helm). This matches what that guardian power is really for in vanilla — sailing against the wind — rather than being an always-on speed buff. Detection is read directly off the ship's own steering-user field (ZDOVars.s_user, the same one the game itself sets the instant you take the wheel and clears the instant you let go) — confirmed live tracking correctly across two different ships. BuffRoster_GP_Moder_RequireBoat (on by default) is what scopes it to steering specifically — standing on deck without hands on the wheel does not count — turn that setting off if you'd rather have it always-on everywhere instead. Because there's no vanilla channel to force an effect off early, disabling a slot means "stop renewing it" — it fades out on its own natural duration rather than being instantly revoked.

🔥 Production Supply

Fireplaces, hearths, torches, smelters and kilns keep themselves fed from the chests around them — fuel and ore tracked separately, so a smelter never idles on a full coal bin. It works whether or not anyone is online, never drains a chest below your reserve floor, only ever loads a charcoal kiln with the wood you allow, and any station can be switched off with an emote (see Player Controls). 0.8.0 fixes the one thing that used to go wrong: Wonderland no longer takes a station away from the player using it, so hand-feeding a smelter that is also being auto-fed just works — no more "the smelter ate my silver" — and the stations you leave behind through a portal keep working while you're away.

🗂️ Background Sort

A slow, low-frequency pass quietly merges partial stacks of the same item across a base's containers. Consolidation only — a stack that's already whole is never touched, and nothing gets relocated while you're actively looking at it.

📐 Container Rows

Every player-built container gets more rows — doubled by default, so a wood chest goes from 2 rows to 4 and a reinforced chest from 4 to 8 — on completely vanilla clients, with nothing installed on their side. This includes ship cargo holds: Karve, VikingShip and VikingShip_Ashlands grow exactly like a chest (Raft has no cargo hold in vanilla, so there's nothing there to grow). The multiplier is configurable, and total rows are capped at 32. The mechanism is vanilla's own: a 1.0 client accepts item rows beyond a chest's prefab grid when it loads the chest from the server, resizes the grid to fit them, and the chest panel scrolls. All the server does is keep one stack parked in the last row so the client keeps drawing it — a pure position move that can never add, remove or resize a stack — and since vanilla already places materials bottom-first, that anchor mostly takes care of itself. Ship cargo holds retain their expanded capacity safely without mid-voyage sailing desyncs or water impact damage: row anchoring, vacuum pulls, and background sorts are automatically paused while a ship is steered or underway, and resume seamlessly when moored. The scanner only ever visits containers that can actually grow, so a newly-filled chest gets picked up quickly and consistently rather than waiting behind every world-spawned loot chest and dungeon prop on the map. The vacuum, production supply and sort all see and use the grown rows. Width and stack sizes are not part of this: a vanilla client refuses extra columns and clamps every stack to its own maximum on load, so those stay vanilla (see below). Tombstones, treasure and dungeon chests, cargo crates and every other world-spawned container keep their vanilla size; add any player-built prefab you want left alone to the exclusion list.

Ships and carts included. A hull's cargo lives on the ship's own network object, and whoever is nearest a floating hull is the one simulating it — so rather than write over that player's game, Wonderland borrows the hull the way a second player opens someone else's chest (vanilla's own request, which the player's game refuses while the cargo is open), parks the extra rows, and hands it straight back. The hull pauses for a tenth of a second; the rows are there the next time the cargo is opened. A ship under sail is left alone until it stops; never more than one request a minute per ship.

📦 Item Cache & Overflow Guard

Wonderland does not boost stack sizes: a vanilla client — the only kind that ever connects to a server-only mod — clamps every stack to its own vanilla maximum the moment it loads a chest, so a server-side boost is invisible in play and only puts the excess at risk. (Extra rows are different — see Container Rows above.) The guard is the safety net that keeps anything a client would clamp or refuse from ever being lost:

  • Never-Lost Overflow Guard: Any items a chest cannot actually hold — a column past vanilla width, a row past the chest's grown height, a stack above vanilla max — are safely routed into nearby sibling chests, or into the persistent server-side ItemCache (Wonderland.Cache.<WorldName>.dat) if all nearby chests are full.
  • Automatic Drain: As soon as new chests are placed or space opens up, cached items automatically flow right back into storage.

Lost something to the cache? Stand where you want it back and use the /comehere emote (see Player Controls) — Wonderland drops the cached stacks at your feet.

🎮 Player Controls

Players can operate parts of Wonderland from a completely vanilla client, on any platform, with emotes — from the emote wheel or typed in chat as the vanilla command. A stock client never sends a custom slash command to a server (it runs locally and prints "not a recognized command"), and plain chat is only delivered to other players, so someone alone on the server produces no chat traffic at all. Emotes are different: every one is written into the player's character data, which always reaches the server. Wonderland answers with a normal on-screen message.

Do this Standing near Effect
/nonono a kiln, smelter or fire Auto-supply off for that station: Wonderland stops loading it, whatever is inside burns out, feeding it by hand still works. Survives restarts.
/thumbsup the same station Auto-supply back on.
/comehere anywhere Drops your cached items (see Item Cache) at your feet — the ones within 30 m, or all of them if none are nearby.

The nearest station within ControlRange (5 m by default) is the target. Every emote and the range are configurable in section 13 - Player Controls.

🌸 Alice — the optional companion

Wonderland needs nothing on the player's side, and that has not changed. But a player on PC who wants a little more can add Alice, a small separate client mod (not part of this package) that talks to Wonderland over a private channel of its own. Alice shows you what the server's automation is up to — why that smelter is not being fed, how big a grown chest really is — lets you switch a station's fuel and ore supply separately, or every station around you at once, with a key press instead of an emote, opens a chest that vanilla cannot open for you, brings your item cache home — and lets you craft, upgrade and build straight from the chests around you.

The rule it is built on: Wonderland behaves exactly the same with or without Alice. Everything Alice shows or flips is something Wonderland already does; a player without it is served identically, an Alice that cannot find the server stays plain vanilla, and a server that has the switch off never says a word to anyone. Off by default (AliceLinkEnabled, section 20 - Alice Link); console players are never asked. Chests Alice opens for you are checked first — range, privacy, the guard stone — and Wonderland keeps its hands off a chest it has just handed you until you are done with it, so nothing moved in the meantime can be lost.

Crafting and building from nearby chests is Alice's headline extra: walk up to the workbench with a base full of chests and the recipe simply works — the wood, the stone, the iron are taken from the storage next to you, nearest chest first. The server does the taking, all at once or not at all: if any ingredient is short, nothing is touched. What it takes is held in escrow — never handed to the client, never topped up into your bag — and goes one of two ways: the craft or the placement happens and the held share is spent, or it does not (you cancel, the hold runs out, you log off, the server restarts, the link is switched off) and every item goes straight back where it came from. If that chest is gone or full it goes to the one beside it, and if there is none, to your item cache. The hold is written to a small journal before the first chest is touched, so even a server crash is made good on the next start. The design chooses a duplicate over a loss every time. One honest note for admins: the server cannot see inside a player's game, so it takes the paired client's word that a craft happened — a deliberately modified Alice could keep what it crafted and report it cancelled — which is why both switches exist and can be flipped live. Only chests you could open yourself count — private ones stay private, guard stones are respected — and only plain, ordinary stacks of materials: never a sword, never an upgraded or crafted item. Craft range, hold times and both switches (crafting, building) are in section 20 - Alice Link.

A vacuum that listens. With Alice the vacuum stops guessing. When a chest wants the stack you just mined, dropped or looted, the server no longer grabs it and waits to see whether you were reaching for it — it asks your game, the only one that knows, and the stack goes into the chest the very moment your game says it is not holding it. No pause, no tug-of-war, no sliver of a chance of a stack ending up in your bag and the chest. If your game is busy, unsure, standing right beside the stack, or simply silent, nothing happens and the vacuum works exactly as it always has; the server never moves a stack on a client's say-so alone, only when its own copy of the stack proves the hand-over. Fresh drops are pointed out to the server the instant they appear, so the chest beside you fills within a heartbeat instead of at the next sweep. And every chest gets a say: switch its vacuum off, let it take only a short list of things you choose (even when it is empty), make it a sink that swallows whatever no other chest wants, or shorten its reach — from Alice's chest window, remembered per chest by the server, and quietly ignored (but kept) whenever the Alice link is off. A small line of text tells you what went where. Players without Alice get exactly the vacuum they have always had and never notice any of it. The four extras (hand-over, instant trigger, chest settings, the little text) each have a switch in section 20 - Alice Link.

⚔️ Raids & Night Spawns

Block configured high-tier raid events from ever triggering in configured biomes (defaults: Meadows, BlackForest) — genuinely server-authoritative, not a guess. A companion system destroys hostile night-spawn creatures matching a configured biome/tier list the instant the server registers them, so a Meadows base stays a Meadows base no matter how long it's been standing. Both a creature's name and its biome must be on their respective lists for a spawn to be blocked. Defaults cover Meadows/BlackForest (Draugr, Draugr Elite, Wraith, Abomination, Deathsquito, Blob, Blob Elite, Stone Golem), the full Mistlands Seeker family (Seeker, Seeker Brood, Seeker Brute, Seeker Queen), the full Ashlands Charred family (Charred Archer, Charred Archer Fader, Charred Mage, Charred Melee, Charred Melee Dyrnwyn, Charred Melee Fader, Charred Twitcher, Charred Twitcher Summoned), and the full Fenring family from Hildir's camps (Fenring, Fenring Cultist, and the Hildir variants) in their own biomes — every prefab name confirmed against a live game data dump, not guessed.

👥 Player Cap

Raises or lowers vanilla's hardcoded 10-player connection limit. Connection admission is a server decision through and through, so this is one of the few levers here with zero ambiguity about where authority lives.

⚠️ Crossplay note: -crossplay routes every connection through PlayFab, whose own lobby registration is separately hardcoded to 10 players. Raising the cap past 10 helps Steam-direct joins only — PlayFab/Xbox joins past the 10th are still rejected by PlayFab itself, independent of this or any mod. A startup warning fires automatically if this applies to your server.

Crossplay lobby guard. A crossplay server only becomes joinable once PlayFab confirms its join code is unique, and vanilla's check has a blind spot: the join code is the same after every restart, the previous run's lobby is usually still on PlayFab's books, and the moment PlayFab forgets who owned it the check crashes on a null owner and the server sits registered-but-invisible — no join code, no server list, no IP join — until the next restart. Wonderland catches that reply and takes vanilla's own regenerate-the-join-code path instead, so the server comes up findable every time. Nothing else in the registration flow is touched; CrossplayLobbyGuardEnabled turns it off, and it is inert on a Steam-only server.

🏚️ Structure Upkeep

A standing correction pass resets player-built pieces back to full health, rather than trying to intercept the (client-owned) decay tick directly — a patch that could never reliably fire on a real dedicated server. Two passes: a fast one around every connected player (decay can only happen inside a client's active area, so that is the only ground that can have lost health since the last tick) and a slow background sweep of the whole map as a backstop. Starter boats granted by the server (s_creator == 0L) are also protected: when moored or docked, starter vessels receive periodic upkeep so wave chop and weather damage don't permanently wear them down. Each repair routes vanilla's native RPC_Repair directly to the owning client alongside RPC_HealthChanged: this authoritatively commits full health into the client's in-memory ZDO, ensuring the heal permanently holds upon taking subsequent hits instead of reverting to previous damaged health. World-generated ruins are left alone by default.

Boats repair on their own schedule — at sea too. Ships are out of the structure pass and on a loop of their own (18 - Boat Upkeep): every BoatUpkeepInterval a damaged Raft, Karve, Longship or Drakkar is put back to full health wherever it is — moored, under sail, or under a serpent — with no rudder or speed condition. A boat someone is aboard or beside is repaired through that player's own game (vanilla's repair message, no hammer, no effects); a boat nobody is near is written by the server. Set the interval short for boats that are hard to sink, long for boats that merely do not rot, or switch it off to keep vanilla wear on hulls while structures stay pristine.

🎁 Starter Grant

New characters get a one-time starter kit and a labeled boat, automatically, the first time they're seen in the world — configurable kit contents, hull type, boat placement search radius, and an automatic vanilla map pin discovery. The boat is sited in open water with proper clearance, oriented seaward, rather than placed on dry land. The record is a world global key per character (wonderland_starter_<playerID>), saved inside the world file itself, so it only ever happens once per world — across reconnects, restarts, and backup restores alike.

🛡️ Security & Anti-Cheat

Wonderland enforces an authoritative, multi-layered server-side security suite designed to protect honest survival progression while remaining split honestly between what a dedicated server can enforce versus client-side blind spots:

  • Enforceable: Vanilla Client Mod Enforcement — protects pure vanilla servers by ensuring connecting clients are genuine, unmodded vanilla Valheim installs. Employs dual-vector enforcement: (1) Active Probing queries connecting clients with known framework challenges (ServerSync, Jotunn, ValheimPlus, AzuAntiCheat); vanilla clients silently ignore them while modded clients respond into the honeypot and are kicked. (2) Placement Cadence Guard (section 19 - Plant & Terrain Guard) monitors incoming entity creation to detect automated client-side planting and bulk placement mods (e.g. PlantEasily); bursts exceeding the vanilla physical placement cooldown (0.4s) immediately purge the cheated batch and kick the client. Disconnected clients receive "Failed to connect: Incompatible version" or the notice: "Vanilla enforcement enabled, connect fairly with vanilla only client". Authenticated server admins on adminlist.txt are completely exempted from mod checks based purely on the server's authoritative adminlist check.
  • Enforceable: Terrain Guard — every terrain edit a client sends is the zone's whole modification set, stamped with the game's own op counter, and the server reads it before it lands: a vanilla hoe, cultivator or pickaxe marks a few dozen 1 m vertices per op, so a write that rewrites hundreds or thousands with no op behind them (World Edit Commands terrain, an Infinity Hammer blueprint), carries an op radius vanilla never registers (an uncapped hoe), or spams ops faster than a hoe can swing (a scripted client) is put back the way it was — on every player's screen, the offender's included — the zone is held out of that client's hands, and the client is kicked (TerrainGuardKickMessage). Ops placed in a neighbour's zone are charged to the placer, not the neighbour who happens to own it, so a build party never trips it. Adminlist admins are exempt in full (TerrainGuardAdminBypass) — bring whatever client tooling you like; the edits that would have tripped the guard are logged as admin bypass, accepted so you can watch it work. The Placement Cadence Guard (bulk planting) lives in the same section.
  • Enforceable: Forged Sender Check — every message a vanilla client sends to the server names its sender, and the server used to believe it. A modded client could name an innocent player on a message the vanilla-only check does not know, and that player was the one kicked; naming nobody skipped the check altogether. A message whose claimed sender is not the connection it arrived on is now dropped before anything acts on it and the real sender goes in the security log (RoutedSenderGuardEnabled, on by default; admins exempt). Nothing changes for a vanilla client, which has always signed its own messages.
  • Enforceable: Server-Side Forced Map Visibility (ForcePlayerMapPosition) — forces all connected players to always be publicly visible on the map and minimap for all players, completely server-side. Vanilla clients display all player pins with character names at all times, overriding the client-side "Visible to other players" checkbox. Authenticated admins can be exempted (ForcePlayerMapPositionAdminBypass) for stealth spectating.
  • Enforceable: Container Integrity & Progression Sweep (ItemSanityGuard) — a periodic item-integrity sweep checks every tracked container against real item definitions, vanilla stack ceilings, cheat item blacklists, and server progression tier ceilings (MaxAllowedTier, defaulting to "Auto" to dynamically follow world boss kills), flagging (or optionally removing with ItemIntegritySweepCorrect) prohibited items. Containers placed by authenticated server admins are completely exempt. Containers only: a player's own bag is never networked to the server, so there is nothing there to check.
  • Enforceable / Detect-only: Equipment & Magic Surveillance (EquipmentGuard) — scans visual equipment hashes (VisEquipment) on player character ZDOs in real time. Flags developer cheat items (SwordCheat, SledgeCheat, ClubCheat, ArmorIronChestCheater, HelmetCheater), impossible quality levels (quality > m_shared.m_maxQuality, exempting gear whose recipe runs through Valheim 1.0's upgrader stations, which legitimately climb past the base cap), and gear exceeding the server's progression tier ceiling, magic staves and robes included. Supports optional auto-kick (EquipmentGuardKick). Authenticated server admins on adminlist.txt are 100% exempt (EquipmentGuardAdminBypass = true) — admins can wield, wear, spawn, or test whatever they want, whenever they want without interference. Anti-spam tracking ensures equipped gear logs once upon equip and resets automatically when a world boss falls.
  • Enforceable: Automatic World Progression Ledger (MaxAllowedTier = "Auto") — dynamically ties server gear progression ceilings and anti-cheat kicking directly to Valheim's persistent world boss defeat registry (defeated_<boss>). See the front-and-center Progression Ledger above for the full unlock matrix from Black Forest through Ashlands/Deep North.
  • Detect-only: Movement & Vitals — max HP above a configured ceiling, implausible current stamina, implausible movement speed, and a persistent gap between reported position and expected terrain height (likely flight/noclip) are all logged as signals for an admin to review, never auto-corrected. Authenticated server admins are completely exempt.
  • Dedicated Security Audit Log (SecurityLogEnabled, SecurityLogFileName) — writes all security events to a dedicated BepInEx/logs/wonderland_security.log stamped with UTC timestamps, player name, Steam64 / account ID, stable PlayerID, world coordinates, and infraction details, completely isolated from general BepInEx noise.
  • Structural blind spots, named honestly — max stamina, skill levels, save-file edits, and ESP-style rendering cheats never reach the server at all, on any Valheim build; no amount of server-side logic changes that. (Note: carry capacity was previously in this list, but was unlocked in 0.6.0 via Valheim 1.0's native World Modifier system). Combat hits are in the same bucket: a damage RPC goes to the victim's own client and the server only relays it, which is why there is no damage-plausibility check here.

📣 Discord Notify

Your community's Discord knows what the server is doing: online and offline, who joined and left, who died, the first time an account the world has never seen joins, the first fall of each of the five classic bosses — and, if you want it, a heartbeat with uptime and who's on. Every roster says what each player is on — Alice (PC), Bob (Xbox), Cara (Switch 2) — and so does the join, leave and welcome headline, because in a crossplay world that's half the story; {platform} is there for any other template that wants it. Each message is clean Discord markdown — a bold headline with a small grey line beneath it, the live roster where it fits — and every one of them is a template you can rewrite. Optional extras, all off by default: your own avatar, a role to ping on boss kills and newcomers, a heartbeat rhythm of its own. Nothing is ever pinged by accident — not even by a player who names their character @everyone. Paste one webhook URL and you're done; it lives on your server and is never synced to clients.

💓 Heartbeat

A single summary line — world name, uptime, and who's currently online and on what — logged periodically (every 15 minutes by default) so an admin tailing the server log can confirm Wonderland is alive at a glance, without turning on full verbose logging. The optional Discord heartbeat above shares this interval unless given its own (DiscordHeartbeatIntervalMinutes). Configurable in 1 - General (HeartbeatEnabled, HeartbeatIntervalMinutes).

🤖 BarrkBOT Export

Run BarrkBOT, the community Discord bot that answers members' questions from what the server's mods write down? Wonderland feeds it: who's online, each player's platform, sessions, time on the server, deaths and when it first saw them, world progress, the day count, the rates in force and lifetime tallies of what the automation has fed, vacuumed, cached and granted — all measured by the server itself, never taken from a client's word. A clean shutdown tells the bot the server is offline instead of leaving it guessing, and nothing private goes out: account ids stay with the admin. Harmless without BarrkBOT — it's two small files beside your config, and it can be switched off.

Three more files are there for the asking, each off by default and each its own switch in section 17 - BarrkBOT Export (a new file is something BarrkBOT picks up and reads out, so you choose when). Activity answers how far has Dagny travelled, who spends the most time at sea, who has seen the most of the world, who stood at the boss fights — measured by the server for every player, console included, with nothing installed on their side, and never a live position (nobody gets griefed over Discord). The base answers how much iron do we have, are the smelters being fed, how much has the vacuum moved today — a snapshot of what the player-built chests hold, taken in small slices every ten minutes, plus the last 24 hours of the automation and Alice's counters. And player-reported carries the figures only a player's own game knows — kills, crafts, pieces built, trees felled, boss kills, best skill — for Alice players who said yes to sharing, in a file of its own with _reported in every name, so what a player says about themselves is never mistaken for what the server saw. (Kills in particular cannot be measured by a server at all: a creature's owner credits its own kill locally, so only the player's game has the true count.)

🧬 Valheim 1.0 Native

Built against the current Valheim 1.0 dedicated-server assemblies — the same binary a live Linux dedicated server runs — and every release is booted on that server. Every game API the mod touches was verified against the 1.0 decompile — including the sector-query API that 1.0 reshaped, which is detected by parameter shape at startup (the older 0.221.x five-argument form is still bridged by reflection, best-effort). The startup log says which path it picked.


⚙️ Configuration

Settings live in BepInEx/config/wubarrk.wonderland.cfg, split into numbered sections, each entry documented with its own description, unit, and range right in the file. Edits are picked up live: the file is polled every 5 seconds and applied automatically — no server restart needed for a config change to take effect.

Server-Synced (Admin Controlled)

Section What it covers
1 - General Whether the server locks synced config against client overrides (default on); verbose logging, heartbeat, the tick profiler (slow-frame lines with a per-subsystem breakdown, 5-minute summaries) and the per-frame sweep budget.
2 - Vacuum & Auto-Harvest Enable, interval, batch size, radius, exclusion lists, pickup-effect toggle, and the All Items Float buoyancy toggle (AllItemsFloatEnabled) for ground items in water.
3 - Production Supply Enable, interval, batch size, range, reserve floor, and the kiln wood-type filter for fuel/process-material auto-supply.
4 - Sort Enable, interval, and batch size for background stack consolidation.
5 - Container Rows Enable, row multiplier, sweep interval, batch size, and exclusion list for server-side container row growth on vanilla clients (chests and ship cargo alike).
6 - Raids Enable, blocked biomes, and blocked raid-event name list.
7 - Night Spawns Enable, blocked biomes (default includes Mistlands, AshLands, and Plains), and blocked creature prefab list (default includes the full Seeker, Charred, and Fenring families).
8 - Player Cap Maximum concurrent connected players (default 10, vanilla's own limit); crossplay lobby guard toggle.
9 - Structure Upkeep Enable, interval, per-player radius, background sectors-per-sweep, and player-built-only for the no-decay correction pass.
18 - Boat Upkeep Enable and interval for the separate boat repair loop (works at sea; uses the structure pass's per-player radius).
19 - Plant & Terrain Guard The placement (bulk planting) guard and its burst limit; the terrain guard's ceilings (vertices per write, vertices / ops / zones per player per minute), revert, kick and kick message, total admin bypass, and the admin-edit log line.
10 - Starter Grant Enable, kit contents, boat hull prefab, and boat placement search radius.
12 - Security Vanilla client mod enforcement (auto-kick with notice, authoritative admin bypass), server-side forced map visibility (ForcePlayerMapPosition), automatic boss defeat progression ledger (MaxAllowedTier = "Auto"), item exemption & tier override list (ProgressionItemExemptions), equipment & magic surveillance (EquipmentGuard), vitals guard, position watch, container integrity sweep, the forged-sender check (RoutedSenderGuardEnabled), and dedicated audit log file.
13 - Player Controls Enable, target range, and which emotes switch a station's auto-supply off and on or recover cached items.
15 - World Modifiers & Capacity Multiplier for player max carry weight (CarryWeightMultiplier, default 2.0 = 600 lbs base) and passive stamina regen (StaminaRegenRateMultiplier, default 3.0). Both synced to vanilla clients in real time via Valheim 1.0's native world rate channel.
16 - Status Effect Roster Master switch, one on/off toggle per curated vanilla status effect asset (run speed, swim stamina, stamina regen, boss powers), and the boat-steering requirement for Moder.

Local to Your Game

Setting Section What it does
VerboseLogging 1 - General Verbose diagnostic logging. Security findings always log regardless of this setting.
HeartbeatEnabled / HeartbeatIntervalMinutes 1 - General The periodic "still alive" server-log summary (see Heartbeat above).
SweepBudgetMs 1 - General How much of any one server frame each world-wide sweep (vacuum round-robin, container rows, sort, production supply) may use before it yields to the next frame (default 2 ms). Coverage is unchanged — each sweep still walks its batch per interval — the work is just spread across frames instead of landing in one, so a large world never stalls the server for a chest type. Local because it is about this machine's frame time.
BarrkBotExportEnabled / BarrkBotWriteSeconds 17 - BarrkBOT Export Whether the BarrkBOT export is written, and how often. Local because it describes this server's own files.
BarrkBotActivityExport / BarrkBotBaseExport / BarrkBotReportedExport (and BarrkBotStockTopItems, BarrkBotReportMinSeconds) 17 - BarrkBOT Export The three optional BarrkBOT files above, all off by default; how many item types the chest stock lists; how often Alice players may report their own figures. Local.
TerrainGuardDiscordNotify / TerrainGuardDiscordTemplate 19 - Plant & Terrain Guard Whether a stopped terrain edit is posted to the section-14 webhook, and the line it posts.
AliceLinkEnabled and the rest of section 20 20 - Alice Link Whether the server talks to the optional Alice companion at all (off by default), which extras it offers (production switches, container help, crafting and building from chests, vacuum cooperation and per-chest vacuum settings), and the ranges, hold times and rates it allows. Local because Alice players need not carry ServerSync.
(all of section 14) 14 - Discord Notify The webhook, which events to announce, the display name, the optional avatar / mention / heartbeat rhythm, and every message template. Local because a webhook URL is a per-server secret.

Upgrading from an older release? Settings carry over automatically on first launch wherever the concept still exists. Anything tied to a removed feature is logged once as a summary and dropped. What changed between releases lives in the changelog, not here.


📦 Dependencies

⚠️ Requires: BepInEx (the Valheim 1.0 pack, 5.4.2360 or newer). Nothing on the client, ever.

Dependency Why
BepInExPack Valheim (denikson) The mod loader (also provides HarmonyX).
JsonDotNET (ValheimModding) Declared so mod managers install it; the game already ships its own copy, which is enough.

📥 Installation

Wonderland is a server-side-only mod — install it once, on the server, and every connected player benefits with nothing to download. Just install Wonderland on the server — the dependencies above are pulled in for you.

Manual install:

  1. Install BepInExPack Valheim on the server.
  2. Drop Wonderland.dll into the server's BepInEx/plugins folder.
  3. Restart the server. That's it — no client install, no client config, nothing for players to do.

A Valheim mod by Raven Iron.

Changelog

1.12.1 Latest

Changed

  • Rebuilt and checked against Valheim 1.0.21 (network version 41; world version 42, player version 47). No source change was needed. An asmdiff of the 1.0.17 and 1.0.21 server assemblies was read against every Harmony target and game call the mod makes:
    • ZNet.RPC_PeerInfo changed only its network-version constant (40 to 41), so the PlayerCapGovernor transpiler still finds the GetNrOfPlayers() call and the literal after it, and the PeerJoinLeaveHook / ModEnforcementPatches hooks still bind.
    • CrossplayLobbyGuard: ZPlayFabMatchmaking.OnCheckJoinCodeSuccess and every field it uses (m_serverData, m_retries, ScheduleJoinCodeCheck, OnSessionUpdated(State.RegenerateJoinCode), JoinCode) are unchanged. The only PlayFab changes are the network-version filters in ZPlayFabMatchmaking.ListServers, ZPlayFabLobbySearch.ToServerData and ServerListGui, which are client-side lobby-list code.
    • ZDOMan.CreateNewZDO / RPC_ZDOData / RPC_DestroyZDO, ZDO.Deserialize / SetOwner, ZRoutedRpc.RouteRPC / HandleRoutedRPC / RPC_RoutedRPC, ZRpc.HandlePackage, ZNet.Disconnect / Shutdown / UpdatePlayerList / ServerLoadWorld and the ZoneSystem / RandEventSystem hooks are byte-identical.
    • The cheat flag is now revisioned in the game (ZDOVars.s_cheated is an int that must equal 2; objects flagged under older versions count as clean). Wonderland never reads or writes s_cheated; ZDOVars.s_cheatedQueued, which the production auto-supply writes beside a queued ore, is still a plain bool exactly as Smelter.QueueOre writes it.
    • Container inventories are still read and written through the game's own Inventory.Load / Save; the item-data version moved from 109 to 110, which older stored items load through unchanged. The Alice link needed nothing: Alice 0.12.1 is the matching rebuild.
  • Website link moved to https://www.rossgilsonlabs.dev.
  • Needs BepInExPack Valheim 5.4.2360.
1.12.0

Version jumps from 0.11.2 to 1.12.0 at Rohan's request.

Added

  • The Alice link: server end of the optional PC client companion (Subsystems/Companion/CompanionLink.cs, CompanionStations.cs, CompanionContainers.cs, WardAccess.cs, CompanionSubsystem.cs new; Subsystems/Security/RoutedRpcGate.cs new; Wonderland.csproj links ..\ALICE\Protocol\*.cs in as Subsystems/Companion/Protocol/, namespace AliceLink; 20 - Alice Link, all local keys - not ServerSync, because Alice players need not carry it). AliceLinkEnabled defaults to false and with it off the server runs exactly as 0.11.2: no session, no advertise, no reply, and the two Alice RPC hashes reach enforcement like any unknown hash. On, a player without Alice is unaffected: the only thing they ever receive is an RPC their client has no handler for, which ZRoutedRpc.HandleRoutedRPC ignores (TryGetValue miss, decompile line 83725). The wire contract is ALICE/Protocol/{LinkCodec,LinkProtocol,LinkMessages}.cs (owned by the Alice project; both mods compile the same files; link protocol 1, 89 checks in ALICE/tests/LinkTests on the client side).
    • Transport: two routed RPC names, ALICE_S2C and ALICE_C2S, one ZPackage argument each; the framed message (magic 0xA1, kind byte) is that package's raw content (new ZPackage(bytes) out, ReadPackage().GetArray() in - checked against the game's own ZPackage/RoutedRPCData at every start by RoutedRpcGate.SelfTest). The server speaks first: about 3 s after a non-console peer is ready it sends Advertise (4-byte per-connection nonce), repeating at +10 s and +20 s without a Hello, then stops. Hello (nonce echoed, feature bits) is answered with Welcome (common protocol version, features = client AND server, the ParamBag); no common version = Welcome with proto 0, never a kick. Xbox, PlayStation and Switch peers (PeerPlatform.Label) are never advertised to. Requests before a Welcome are dropped unanswered.
    • Features offered: Production (needs AliceLinkProduction and ProductionSupplyEnabled), ReliableOpen (AliceLinkContainers), ContainerRows (when ContainerRowsEnabled and the multiplier is above 1), CraftFromChests (AliceLinkCrafting) and BuildFromChests (AliceLinkBuildFromChests) - see the crafting entry below. VacuumCoop (AliceLinkVacuum, see the vacuum entry below). Not offered yet: ReportedStats, EnhancedChests (the client falls back to vanilla for each). ParamBag: StationRange (AliceLinkStationRange, 12 m), AreaRadiusMax (AliceLinkAreaRadius, 32 m), AreaMaxRows (AliceLinkAreaMaxRows, 128), OpenRange (AliceLinkOpenRange, 8 m), CraftRange (AliceLinkCraftRange, 20 m), ContainerSpecs = (prefab, width, height) for every player-built container from ContainerRows.GetGridSize. Settings are re-read every 2 s: a changed bag goes out as Push Config, a changed feature set as a fresh Welcome (the client treats any Welcome as replacing its state), switching the link off sends every paired client a Welcome with proto 0.
    • Ops (every distance is from the requester's character ZDO on the server; a request never names a position): QueryStations (around the player or by id; nearest first, capped at AreaMaxRows, ids out of AreaRadiusMax reach are simply absent), SetStationPrefs (mask/values or Toggle, within StationRange), SetStationsInArea (AllOff, AllOn, KilnsOff, KilnsOn around the player; one audit line per request), OpenContainer, RecoverCache, CraftReserve / CraftCommit / CraftCancel (below). Reply bodies on Ok: station ops a StationStatus list (one entry for SetStationPrefs, the changed stations for SetStationsInArea), OpenContainer empty, RecoverCache a u16 stack count. Pushes: StationChanged (one StationStatus) to paired peers within 128 m of the station, on any change including an emote.
    • OpenContainer mirrors Container.RPC_RequestOpen (decompile line 122040) for the one case vanilla cannot answer - the chest's owner is a far-away game, nobody, or the server itself, so the routed request is dropped unanswered. Checks, in order: the container prefab, the character within AliceLinkOpenRange, the prefab's m_privacy (Public opens; Private opens for the ZDO's creator == the character's s_playerID; Group opens for nobody - Container.CheckAccess, line 121996), the guard stone when the prefab has m_checkGuardStone (WardAccess: ward ZDOs enabled/creator/permitted+pu_id<i>, prefab radius, horizontal and strictly below the radius - vanilla only checks this in the client), no pending HullBorrow. If a connected game that instantiates the zone owns the chest (ProductionSupplyEngine.PeerSimulates) the reply is Stale and Alice repeats the plain vanilla open, which that owner judges as before (in-use included); otherwise ForceSendZDO then SetOwner(requester), in that order, reply Ok. Zero item loss: from the hand-over until the new owner has opened and closed the chest (s_inUse seen at 1 then 0), disconnects, or 8 s pass, ZdoInventoryIO.IsBusy is true for it, so no engine (vacuum, supply, sort, rows anchor, integrity sweep, cache drain) writes s_items in the window where the owner's game holds an older copy and would overwrite the write on its next save.
    • RecoverCache is the /comehere claim on a key press (ItemCache.ClaimAt 30 m, else everywhere): Ok + stack count, NotFound when the cache is empty, Insufficient when nothing could be dropped.
    • Abuse limits: per-player token bucket (AliceLinkRequestsPerSecond 20, AliceLinkBurst 40), minimum intervals per op (QueryStations 0.25 s, SetStationPrefs 0.1 s, SetStationsInArea 1 s, OpenContainer 0.5 s, RecoverCache 2 s, CraftReserve 0.05 s; CraftCommit and CraftCancel are never limited), a RateLimited reply at most twice a second, every reader bounded by LinkLimits. Malformed or misdirected messages (including a client-sent ALICE_S2C) are dropped and audited at most once a minute per player ([SECURITY:AliceLink]), never a kick. Sessions end on disconnect (ModEnforcementPatches.Patch_ZNet_Disconnect prefix).
  • Crafting, upgrading and building from the chests around the player - escrow only, no top-up (Subsystems/Companion/CompanionCrafting.cs, CraftEscrow.cs new; CompanionSubsystem.cs; new local keys in 20 - Alice Link: AliceLinkCrafting true, AliceLinkBuildFromChests true, AliceLinkCraftRange 20 m (4-50), AliceLinkEscrowSeconds 30 (10-120; an upgrade at the station takes about 8 s + 1 s per target quality, less with skill, so quality 10 at low skill is ~18 s and the hold must outlast it - decompile m_upgraderDuration; the hold only matters when a client vanishes without disconnecting, a disconnect hands back at once), AliceLinkBuildEscrowSeconds 60 (20-300); all hot-reloaded, all inert while AliceLinkEnabled is false). Rohan's rules, as relayed: building and crafting from nearby containers is a must have, NO TOP-UP, and NEVER LOSE OR DESTROY AN ITEM. A player without Alice, or an Alice that does not get the feature, crafts and builds exactly as vanilla.
    • The handshake. CraftReserve (CraftReserveReq: station ref or none, CraftPurpose Craft / Upgrade / Build as a trailing byte - absent = Craft - and distinct shared-name tokens with amounts; a token must start with $) takes EVERY line out of the chests in one step and answers CraftReserveReply { Id, ExpiresSeconds, Taken }. The client never receives the items: it counts bag + escrow, spends its own bag share through vanilla when the recipe is paid, then sends CraftCommit (the escrowed share was used - forget it). CraftCancel, the expiry, a disconnect, a server shutdown or the link being switched off hand the stacks back. Commit and Cancel are answered before the character lookup and are never refused for a disabled feature (a player who died mid-craft, or an admin switching crafting off, must not strand a reservation); both are idempotent (NotFound the second time). Replies: Ok; Disabled (feature not offered; Build and Craft/Upgrade are separate bits); BadRequest (empty, non-$ token, zero amount, unknown purpose, a Build that names a station); NotFound (the station ref is not a crafting station); OutOfRange (the station is farther from the character than its own m_rangeBuild + 4 m, capped at 30 m); Insufficient with the chests' total of every line as a CraftNeed list (so the client can say "12 (+7 in chests)"); Busy when the shortfall could be a chest someone has open, or the player already has 8 tickets open.
    • Which chests. Containers within AliceLinkCraftRange of the crafting station (Craft, Upgrade) or of the character (Build, or a recipe with no station) that are player-built (ContainerRows.IsPlayerBuilt: never a tombstone, treasure, dungeon chest or cargo crate), that the player may open (ContainerAccess: privacy and guard stones, the same checks as OpenContainer), that nobody has open (ZdoInventoryIO.IsBusy, which includes a chest just handed over by OpenContainer, and a pending HullBorrow) and that are not a hull a client is simulating. Which stacks (the same on both sides): stackable, quality 1, no crafter, not cheated, no custom data, world level not below the game's - what Inventory.CountItems counts. Never a sword, never a stack a recipe could not have asked for.
    • All or nothing. Every line is planned against what the chests hold before anything is written; one short line and nothing changes. Nearest chest first, smallest stack first (a debit also consolidates). Pass 1 stops at the first chest that completes a line; pass 2 (the totals) runs only on a failure; at most 48 chest loads per request, and the names cache (VacuumEngine.KnownToHoldAtMost) skips chests it knows lack the item.
    • Zero item loss. The escrow exists in memory AND in a journal file BEFORE the first chest is written; a failure part-way hands back only what was taken: the share of every chest whose write never started is dropped from the escrow first (CraftEscrow.DropUntouched), because that chest still holds its items and a refund would add them twice; the one chest whose Save threw is kept, a duplicate beating a loss. A refund goes to the chest the stacks came from, else a sibling container within 25 m that has room AND that the ticket's player could have opened themselves (player-built, ContainerAccess privacy and guard stones - never a tombstone, a treasure chest or someone else's private chest), else the ItemCache (never refuses; /comehere or the Alice key brings it home). It never writes a chest a player has open: it waits up to 10 s, then moves on to the next place. A stack leaves the escrow only after the chest write that took it; a refund that cannot finish stays in the escrow and is retried. Expiry has a 2 s grace so a commit racing the timer wins. The ledger records CraftEscrow:Reserve.
    • Journal and crash recovery. Wonderland.CraftEscrow.<world>.dat (config folder, rewritten whole on every change through File.Replace so no instant has no journal, deleted when empty; if a crash still catches the older delete-then-move fallback between the two steps, Recover reads the complete .tmp) holds each open ticket's stacks per chest with the UTC time of the debit, stamped with the moment the latest world save began (ZNet.WorldSaveStarted). At world-ready: an entry debited at or before the stamp is in the saved world, so it is refunded; one debited after it was never saved - the restored chests still hold the items - so it is dropped, because refunding it would duplicate. A shutdown refunds everything BEFORE the world save (ZNet.Shutdown prefix, whether or not the link is on).
    • Trust model. CraftCommit and CraftCancel are the paired client's word. The server cannot see inside a client's craft, so a MODIFIED Alice could keep what it crafted and send Cancel (the materials return to the chests), and a Commit lost to a crash or disconnect duplicates one craft's escrowed share. Admins who run anti-cheat should treat AliceLinkCrafting / AliceLinkBuildFromChests like any other client-trusting feature; both switches are hot-reloaded. Per its author, Alice 0.12.0 asks the game to save the character a few seconds after a craft that used chest materials (client config SaveAfterChestCraft, default on), narrowing the exposure of a client crash - which would otherwise leave the chests short while the character forgets the craft, the same as moving the items by hand - from up to the autosave interval to about 20 s.
    • Honest limits. A crash during a world save that never finished can refund an entry the older world still holds: a duplicate, by choice, never a loss. A craft committed in the instant the connection died is refunded when the escrow is not found committed: one craft's escrowed share duplicated, logged with player and items. A client that reserves and never spends is not a loss for anyone, but 8 uncommitted expiries in 10 minutes are audited ([SECURITY:CraftEscrow]).
  • Vacuum cooperation with Alice: hand-over offers, the instant trigger, per-chest settings, "moved" toasts (Subsystems/Companion/CompanionVacuum.cs and Subsystems/ItemFlow/ContainerPrefs.cs new; VacuumEngine.cs, CompanionLink.cs, ItemFlowSubsystem.cs, WonderlandConfig.cs; new local keys in 20 - Alice Link, all hot-read, all inert while AliceLinkEnabled is false and all announced to paired clients through the existing Welcome / Push Config refresh: AliceLinkVacuum true (master switch, needs VacuumEnabled; offers Feature.VacuumCoop), AliceLinkVacuumRelease true, AliceLinkVacuumNudge true, AliceLinkContainerPrefs true, AliceLinkVacuumToasts true). Wire: ops 48-51, PushEvent 3-5, ParamKey 7-9 (ALICE/docs/M3-VACUUM-WIRE.md); server semantics and the reasoning behind every line of the failure handling: docs/ALICE-M3-SERVER-SEMANTICS.md. A player without Alice, an Alice without the feature, and a server with any of these switches off are served exactly as 0.11.2: every stack the new code does not handle takes the unchanged claim-and-settle path.
    • Owner-originated hand-over (CompanionVacuum.TryOffer, VacuumEngine.AcceptReleases). The claim-and-settle step exists because a client's pickup is entirely client-side and the server cannot veto it (VacuumEngine, "The settle step"). When the owner of a stack a chest wants is a paired Alice peer that negotiated VacuumCoop, the server instead pushes ReleaseOffer (up to 16 {offerId, ZDOID} per push, at most 24 offers open per peer) and the owner's game - the only machine that can pick the stack up - decides in one frame (it refuses when its own auto-pickup would claim the stack, when the player pressed E on it, when it cannot judge) and otherwise calls SetOwner(server) + ForceSendZDO and answers ReleaseAnswer with the OwnerRevision (u16) and DataRevision (u32) of its copy after the call. The answer is a claim, the server's own ZDO copy is the proof: the stack moves only in the frame the server's copy shows owner == the server session, OwnerRevision >= the answer's (modular compare) and DataRevision >= the answer's (CompanionVacuum.Proven). The game applies a client's ownership change only when its OwnerRevision is strictly newer (ZDOMan.RPC_ZDOData, decompile 1.0.17 ZDOMan.cs:1176-1184), so a client with a stale view produces a release that never proves and nothing moves. The answer usually arrives BEFORE the ZDO packet (the client batches ZDO sends, routed RPCs go out at once); both orders are handled, with a 1 s wait for the proof. On proof the stack is registered as an already matured hold and its chest is processed in that same frame: the existing TryTakeOwnership sees a server-owned stack with a matured hold and moves it, the existing chest-first-then-destroy order applies, LatePickupPatch stays the backstop, and a chest that cannot take it any more (full, opened, destroyed, excluded meanwhile) leaves the existing ReleaseHold -> HandBack to give it to the nearest player - never frozen. ZDO.SetOwner prefix: while an offer is open for a stack the server already owns, no passive hand-over (ReleaseNearbyZDOS) may take it before the move (a player's pickup grace still wins, as everywhere).
    • Every other ending is today's behaviour. A refusal (PlayerOnIt / Gone / NotOwner / Busy), silence for 1.5 s, a missing proof, or another player winning the stack closes the offer and the stack is an ordinary stack for the claim path; the refusal only schedules the next OFFER (PlayerOnIt 2, 4, 8, 16, 30 s escalating, reset by a release or 5 quiet minutes; Busy / NotOwner / an expiry 4 s). Three unanswered or unproven offers in a row from one peer mute offers to it for 60 s. No offer is made for a stack within 2.75 m of the owner's character (position + 1 m up: the geometry of the client's own auto-pickup, which would ask the stack straight back); one path per stack at any time; offers live at most 2.5 s; a disconnect, the link going off or a switch drops them at once; nothing is persisted, so a server restart mid-offer leaves ordinary ground stacks. The ledger and the sanity guard see the move exactly as before (Vacuum tag). Counters ([Alice] vacuum cooperation so far: ... every 10 minutes while anything happened): offers sent, answered, moved on proof, refused, expired (without proof), taken by another player, nudges.
    • VacuumNudge (op 49, min interval 0.2 s): up to 16 ZDOIDs of ground drops the client just created. A drop is accepted only if its ZDO exists (an id the ZDO packet has not delivered yet waits up to 1 s), is a loose item (not a placed feast, not a hatching egg), is owned by that peer and lies within 64 m of its character; the position the server looks at is the ZDO's, never the client's. Each accepted drop queues one VacuumAround pass (reach 3 m) in a pass of its own like the one that follows an auto-harvest sweep; at most 4 per frame and 20 per second server-wide, positions within 2.5 m coalesced. A nudge only causes a look: every vacuum rule still decides. Reply Ok + the accepted count.
    • Per-chest settings (ContainerPrefs, ops 50 QueryContainerPrefs / 51 SetContainerPrefs, min intervals 0.25 s / 0.1 s): Vacuum on/off (off = the vacuum never puts anything in that chest; every other engine still visits it), Mode MatchOnly (today's rule and the default) / Filter (only the listed $item_* tokens, at most 16, even into an empty chest) / CatchAll (a sink: anything not on VacuumExcludedItems that no matching chest in reach wants), Radius (0 = the admin's VacuumRadius, else clamped to [2, admin radius]). A sink ranks below every matching chest: VacuumAround sweeps matching chests first and sinks second, and a sink leaves a stack alone while another chest in its reach is known to want it (its filter lists the item, or its contents at their current DataRevision in the names cache include the type) and was not found full for that type within the last minute; a chest whose contents are unknown does not make the sink wait (worst case an item lands in the sink instead of its matching chest, never lost). SetContainerPrefs carries a field mask (Vacuum 1, Mode 2, Radius 4, Filter 8; All = replace) and applies only the masked fields over what is stored, so two players editing one base do not clobber each other; the reply is the record as stored (clamped, de-duplicated, sorted); a record equal to the defaults is removed. Allowed for a player who stands within AliceLinkOpenRange of the chest and may open it (ContainerAccess: privacy, guard stone); BadRequest for an empty or unknown mask, a token that does not start with $ or is over 96 bytes, more than 16 distinct tokens, a NaN or negative radius, an unknown mode. State is Wonderland.ContainerPrefs.<world>.dat (C @prefab;x;y;z V= M= R= and T @prefab;x;y;z token lines, rewritten through File.Replace, pruned of destroyed chests on every save, a .tmp left by a crash is read) - a mod-side file keyed by the chest's prefab and exact position (never its ZDOID, which is renumbered on every world load - see Fixed), because a chest an owning client has open rewrites its own ZDO and a server write there can lose. While AliceLinkEnabled, AliceLinkVacuum or AliceLinkContainerPrefs is off the stored settings are NOT in force (every chest behaves as without Alice) and the file is kept, so switching back restores them. ContainerPrefsChanged (push 5) is not sent by this build.
    • Toasts (VacuumMoved, push 4): the vacuum stages each stack it puts into a chest and releases the staged moves only after the chest write succeeded (an exception discards them); they are aggregated per chest and item for a second and sent to paired VacuumCoop peers within 30 m of the chest (distance computed per recipient, at most 8 entries, real moved counts only).
    • ParamBag: VacuumFlags (u16: Release 1, Nudge 2, Prefs 4, Toasts 8 - a bit is set only when its switch AND its precondition hold, e.g. Release only when VacuumEnabled), VacuumRadius (f32, the admin's VacuumRadius), PrefsFilterMax (u16, 16), present whenever the server offers VacuumCoop.
  • Three more BarrkBOT files, all OFF by default: player-reported statistics (Alice), server-measured activity, and the base (Subsystems/BarrkBot/BarrkBotReported.cs, BarrkBotActivity.cs, BarrkBotBase.cs new; BarrkBotStats.cs, BarrkBotSubsystem.cs, CompanionLink.cs, CompanionReports.cs new, CraftEscrow.cs, ProductionSupplyEngine.cs, VacuumEngine.cs; 17 - BarrkBOT Export, local keys: BarrkBotReportedExport false, BarrkBotReportMinSeconds 60 (30-600), BarrkBotActivityExport false, BarrkBotBaseExport false, BarrkBotStockTopItems 40 (0-100); wire ALICE/docs/R2-REPORTED-STATS-WIRE.md). New files are default off on purpose: BarrkBOT's scanner picks up every barrkbot_*.json and a new one is something it starts reading out; switching one off deletes it, and what was recorded stays in the registry. The main barrkbot_wonderland.json is unchanged (schema 3, every field where it was). Registry Wonderland.BarrkBot.<world>.dat schema 1 -> 2, purely additive (new PlayerRow fields reported, distance_metres, sailing_seconds, biome_seconds, boss_fights, chest_materials_used, client; registry fields reported_since, activity_since, owner_releases_count, chest_materials_used_count, hourly_epoch_hour, hourly); a build that predates them ignores them, so a downgrade loses nothing but the new figures. barrkbot_wonderland_reported.json, ..._activity.json and ..._base.json follow the contract's row rules (flat scalar rows with name, units and provenance in the names, *_alltime, null = not measured, single-string _notes, no online and no roster - one fact, one file - and no session_started_at, since every figure is a lifetime total or a labelled snapshot). Measured against BarrkBOT's own reader (tools/barrkbot/barrkbot-render-probe.mjs, 6.1.x): twelve players compact to 4.6, 4.9 and 3.8 kB, under the local provider's 6,000-character slice, and all four files sync as separate exports with no errors. Reader behaviour to know before switching any of them on: a mod that publishes several exports is answered with an INDEX ("too large to return together, pick the file") for a bare get_valheim_mod_data({mod:"Wonderland"}), so once an extra file exists the model asks twice (index, then the file); the words "stock", "distance", "crafts", "kills", "biome" route straight to the right file.
    • Player-reported (CompanionReports, BarrkBotReported; ops ReportStats 64 / ClearReportedStats 65, ParamKey.ReportMinSeconds 10, Feature.ReportedStats offered only while AliceLinkEnabled and BarrkBotReportedExport are on and the registry is live): an Alice player who answered yes in Alice's consent window sends DELTAS of the game's own raw per-character counters since a baseline taken when it connected here (the counters span every world), at most once per BarrkBotReportMinSeconds (a sooner report is RateLimited below 80% of it): crafts, pieces built, trees felled, boss last hits, enemy kills, boss kills (ReportedStat 1-6; a number this build does not know is ignored), plus the top skill's name and level and the sum of all skill levels. Exported per stable s_playerID as crafts_reported_alltime, pieces_built_reported_alltime, trees_chopped_reported_alltime, boss_last_hits_reported_alltime, enemies_killed_reported_alltime, boss_kills_reported_alltime, skill_top_reported ("Swords 54", null when none), skill_levels_sum_reported, reported_at. Judgement: Busy without a stable id (the client keeps its baseline); BadRequest for a delta over 1,000,000 or the same stat twice; a report over its per-minute ceiling for the window since the previous one (floor one minute: crafts 60, builds 300, trees 40, boss last hits 30, kills 200, boss kills 10 per minute) is dropped WHOLE, audited at most once a minute per player ([SECURITY:StatReport]) and still answered Ok so the client's baseline moves on - a dropped window is lost, not retried; skill names are accepted as letters, spaces, apostrophes and hyphens up to 32 bytes (anything else is stored empty and exported as null, so markup cannot reach a Discord line), levels clamp to 0-100 and the sum to 0-5000. ClearReportedStats deletes the player's block and leaves the rest of the row alone; a row otherwise survives reconnects (it is their past, not a live claim). The caps keep a leaderboard sane and are not a security boundary: a bag is client-authoritative, a cheater can fake far more than a counter.
    • Kills are not server-measurable (and are in no server-measured file): Character.OnDeath (Character.cs:2938-2953, 1.0.17) runs on the creature's owner and credits the owner's own player with a LOCAL call (Game.RPC_RegisterKill(0L, ...), line 2946); only the other attackers get the routed RPC through the server (line 2951), so a server-side count would rank players by who happened to own the creature. Kills therefore come only from the player's own game, in the reported file.
    • Activity (BarrkBotActivity, every 5 s from the existing registry sweep, tracked only while BarrkBotActivityExport is on; counters start when it is switched on, tracking_since): distance_travelled_metres_alltime (horizontal ground covered between sweeps from the character ZDO; a step over 30 m/s is a portal, respawn or teleport and is skipped), sailing_seconds_alltime (seconds as the steering user of a hull - ShipAttachment.IsSteeringShip, the s_user field), biomes_visited and most_time_biome (WorldGenerator.GetBiome under the character, seconds kept per biome in the registry), boss_fights_alltime (players within 60 m of where the boss was last seen alive when its defeated_* key is recorded: a fight, not a kill; a sweep looks for boss prefabs within 120 m of every player), chest_materials_used_alltime (items the server took from chests for that player's committed crafts, upgrades and placements - CraftEscrow.Commit; null for a player who never could), client ("Alice 0.12.0" once paired; "vanilla" for a console player or after every advertise went unanswered; null while unknown or the link is off). No position, no kills.
    • Base (BarrkBotBase, BarrkBotStockTopItems): stock = a snapshot of the player-built containers (ContainerRows.IsPlayerBuilt: chests and ship holds, never tombstones or world loot), by prefab name, most plentiful first (stock_by_item, stock_item_types, stock_items_total, stock_containers_counted, stock_measured_at = when the last FULL pass finished, null until one has). One resumable walk over every sector (ZdoSpatialQuery.PrefabSetSweeper) finds the containers; they are visited in slices of at most SweepBudgetMs per frame; a chest the vacuum's per-DataRevision names cache already knows is counted without being loaded (VacuumEngine.TryGetCachedItemCounts), any other is loaded once per pass, and reading never writes so a chest a player has open is counted too. A pass starts every ten minutes; switching the export off drops the snapshot. production: counts of the station notes the auto-supply leaves per visit within the last ten minutes (stations_visited_recently, stations_fed_recently, stations_waiting_fuel, stations_waiting_input; since the server last started) and production_items_fed_last_24h. automation_last_24h: vacuum_items_moved_last_24h, auto_harvest_items_last_24h - rolling windows of 24 hourly buckets per ledger tag, kept in the registry (the newest, still running hour included, so 23 to 24 hours of history; a different period from the lifetime totals in the main file, with different names). companion: companion_players_online (null while the link is off), chests_with_vacuum_settings, catch_all_chests, stations_customised, vacuum_owner_releases_alltime (hand-overs that really ended in the chest), chest_materials_used_total_alltime. Not built: stock_by_base (stock grouped by guard stone and owner name; it names what a player's base holds).
  • Fuel and ore supply can be switched separately (Subsystems/ItemFlow/SupplySwitch.cs, ProductionSupplyEngine.cs). SupplySwitch now holds StationFlags (Enabled / FuelOn / OreOn); a station nobody switched has no entry and is fed exactly as before. The emote OFF clears Enabled only (finer fuel/ore choices kept); the emote ON resets the station to All, so a player without Alice, who cannot see the finer switches, always gets "fed" back. A fireplace only has fuel, so Enabled off and fuel off mean the same there; a smelter with fuel off still gets ore and the reverse. File Wonderland.SupplyOff.<world>.dat: user:id = off entirely (the only line 0.11.2 and earlier read), F user:id = fuel off, O user:id = ore off; a build that predates the F/O lines skips them, so a downgrade feeds those stations as it always did. Count (BarrkBOT stations_switched_off) still counts stations switched off entirely; PartialCount is new.
  • The auto-supply leaves a note per visit (ProductionSupplyEngine.Record): Fed, Full, NoFuelSource, NoInputSource, KilnFilter, OwnerBusy, with the time; one dictionary write per visit, capped at 20000 entries and pruned with the ownership records. Alice words them in the player's language; the engine's behaviour is unchanged. Off and Blocked (engine switched off in section 3) are derived at query time.

Security

  • A forged routed-RPC sender id is dropped (Subsystems/Security/RoutedRpcGate.cs; 12 - Security / RoutedSenderGuardEnabled, default true, read at use time). Vanilla ZRoutedRpc.RPC_RoutedRPC (decompile line 83707) never compares RoutedRPCData.m_senderPeerID with the connection the packet arrived on, and three things trusted it: ModEnforcementPatches.Patch_ZRoutedRpc_HandleRoutedRPC resolved ZNet.GetPeer(data.m_senderPeerID) and kicked THAT peer for a non-vanilla hash - so a modded client could name an innocent player as the sender of an unknown hash and get them kicked while the real sender escaped; a sender id of 0 is treated as a local server RPC and skipped enforcement entirely; and WaterBuoyancyEngine (pickup requests) and VacuumEngine (auto-harvest picks) act for data.m_senderPeerID. A vanilla client writes its own session id there (InvokeRoutedRPC, line 83652), which is also the uid it sent in RPC_PeerInfo (SendPeerInfo writes ZNet.GetUID() == ZDOMan.GetSessionID(), line 80941) and so equals ZNetPeer.m_uid. One prefix on RPC_RoutedRPC (Priority.First) peeks the five header fields without allocating (message id, sender, target, target ZDO, method hash; position restored) and drops a packet whose claimed sender is not the connection's m_uid; the REAL sender is audited as [SECURITY:RoutedSender] ... routed RPC 0x... claims sender N but arrived on connection M - dropped, at most once a minute per player with the count since the last line. A drop, not a kick: a false positive costs one packet, not a session. Adminlist admins are not checked (ModEnforcement.IsAdmin, the same bypass as every other guard). It is one prefix, not two: the Alice interception and the sender check share it, so no Harmony ordering between prefixes on the same method is relied on (TerrainGuard's recorder is a void prefix on the same method and runs as before). Fail-open canary: at start RoutedRpcGate.SelfTest serializes a real RoutedRPCData with the game's own ZPackage, checks the peek reads the sender and hash back and leaves the position alone, and checks the Alice framing round-trips through ZRpc.Serialize / ReadPackage / GetArray; if either fails the gate does nothing at all (and the Alice link stays dark) and an error says so, because a wrong offset would make every routed RPC look forged. Any exception inside the gate passes the packet to vanilla and is logged once. [RoutedRpcGate] self-test passed ... is the line to look for at boot.

Fixed

  • Station switches, per-chest settings and the craft journal no longer key on a ZDOID (Core/Data/ZdoPersistKey.cs new; Subsystems/ItemFlow/SupplySwitch.cs, ContainerPrefs.cs, Subsystems/Companion/CraftEscrow.cs). ZDO.Load opens with m_uid.SetID(++ZDOID.m_loadID) (1.0.17 ZDO.cs:1295-1298; ZDOID.SetID also sets the user part to the "unknown former user" key, 1): in a chunked-save world - every 1.0 world - each ZDO is renumbered, and loses the user id it was created under, every time the world is read off disk (ZDOMan.LoadChunks, ZDOMan.cs:474-592; libs-Tools MASTER_IMPLEMENTATIONS.md, "A ZDOID is a session handle"). An id is stable while the world stays loaded and meaningless after the next restart, so a file keyed by one is orphaned, or applied to whatever ZDO now carries the number. SupplySwitch (Wonderland.SupplyOff.<world>.dat, since the emote switches shipped) wrote user:id: the live files hold 1:51759, 1:44330, 1:44452, 1:87887 ... which, after the restarts since, name other pieces of the world - a station a player switched off was fed again, one nobody touched could have been switched off, and the save pruned only ids that no longer existed at all. The first cut of ContainerPrefs (Wonderland.ContainerPrefs.<world>.dat) and the escrow journal's chest id had the same flaw (after a crash a refund written to GetZDO(oldId) could have gone into a tree, or another player's chest). All three now persist the prefab hash and the exact position (ZdoPersistKey: prefabHash;x;y;z, round-trip floats; a placed piece never moves) and match back to the live ZDO within 0.25 m once the world's sector index can be queried (ZdoPersistKey.WorldReady); the tables in memory stay keyed by ZDOID, valid for the session.
    • Files. Wonderland.SupplyOff.<world>.dat: @prefab;x;y;z (off entirely), F @... (fuel off), O @... (ore off). Wonderland.ContainerPrefs.<world>.dat: C @prefab;x;y;z V= M= R= and T @prefab;x;y;z token. Wonderland.CraftEscrow.<world>.dat: the H line still carries the chest's id (informational) and its position; Recover ignores the id and finds the container nearest to the recorded position, and a chest that is gone sends its stacks to a neighbour or the item cache.
    • Upgrading. Lines in the old user:id form (with or without the F/O letter) can no longer be matched to anything: each file logs one line saying how many it skipped, and the next save replaces the file. Stations switched off with the emote before this build have to be switched off again; chest settings and open escrows did not exist before 1.12.0.
    • Timing. Entries are matched 64 per frame once the world is up; while any are unmatched nothing is written (a save would drop them), a line whose piece is gone is dropped and the file rewritten. CraftEscrow.Recover runs from OnUpdate once the world's ZDOs are loaded, not from the world-ready hook (see the next entry). Until its lines are matched (a few frames after the world loads) a chest or station reads as unconfigured.
  • Crash recovery of the craft journal ran before the world's ZDOs were loaded (Core/Data/ZdoPersistKey.cs Hook / WorldLoaded / WorldReady; Plugin.cs; Subsystems/Companion/CraftEscrow.cs Recover). Found by a real kill -9 after a world save, restarted on the same world (../WonderlandTests/crash-test): the log read [CraftEscrow] #N <name> (Build): handed back (recovered after a server restart) - 0 item(s) to their chest, 0 to a neighbouring chest, 30 to the item cache and only afterwards [ItemCache] Restored 30x ... into container. Recover ran from the world-ready hook, a postfix on ZNetScene.Awake; ZNet.Start - which loads the world, ServerLoadWorld -> LoadWorld -> ZDOMan.LoadChunks, synchronously (1.0.17 ZNet.cs:432-464, 1956-2000) - is a separate step, and on the testbed it runs on the next frame. There, at the hook, the world held no ZDOs, so neither the chest nor any neighbour existed, and the stacks went to the item cache (never lost: the vacuum drains the cache into a container near the recorded position, which is why an end-state check passed). The order is not something to rely on: the Alice live-test rig's 15,843-ZDO world read the journal of the previous build after ZDOMan.LoadChunks done and refunded straight into the chest - the flaw depends on timing and world size, which is why it can pass on one world and fail on another, and why the cure does not assume either order. The ZDOID-keyed code before this build had the same dependence: it also asked GetZDO at the hook. Now every lookup by position and every file-to-ZDO match waits for ZdoPersistKey.WorldLoaded: a ZDO has been numbered by the load (ZDOID.m_loadID above zero) or a frame has passed since ZNet.Start began (ZNet.s_onZNetStart, hooked in the plugin's Awake; a brand-new world loads nothing), with a 20 s timer if the event never fires. The same gate protects the station-switch and chest-settings files. A refund still takes the chest, then a neighbour within 25 m, then the cache, as before; the journal now logs per ticket whether its chest is in the loaded world ([CraftEscrow] #N: the chest at (x, y, z) is in the loaded world; 1 stack(s) to hand back.). Real run on this build: the refund goes straight into the chest found under its new id (... - 30 item(s) to their chest, 0 to a neighbouring chest, 0 to the item cache), the ticket debited after the save began is dropped (the restored chest already holds it), nothing is duplicated, nothing is parked in the cache.
  • Switching the Alice link off no longer gets an active Alice player kicked (Subsystems/Security/RoutedRpcGate.cs Decide, Subsystems/Companion/CompanionLink.cs Deactivate / InEndedGrace / NoteCrossedPacket). Found by the Alice live-test rig (run 4, 2026-10-11): with the section 20 switch (AliceLinkEnabled) hot-edited off while a player held a building reservation, the server logged [Alice] link switched off - 1 paired client(s) told to go back to vanilla. and in the same second [SECURITY:ModEnforcement] ... sent unauthorized RoutedRPC hash 0x595D5E7B ... KICKING (0x595D5E7B = ALICE_C2S; the client saw "Incompatible version"). The cause is a race no client can avoid: a request Alice had already sent (while a piece is held she plans every 0.2 s) was on the wire when Welcome(proto 0) went out, arrived after the link was off, fell through the gate - with the link off both Alice hashes were deliberately left to enforcement - and ZRoutedRpc.HandleRoutedRPC's whitelist kicked a non-admin for an unknown hash. It hit 1 of the 3 rig runs that flipped the switch while she was busy. Any hot-edit of section 20 while someone builds, crafts or stands at a station could do it.
    • The window. When Deactivate ends the link it remembers every peer that had a session with a Welcome or an Advertise behind it (a Hello may be answering the Advertise) for EndedGraceSeconds = 30 s. Inside that window the gate consumes ALICE_C2S and ALICE_S2C from that peer silently (the packet is never handled as an unknown hash and never relayed): one Info line per peer ([Alice] <name>: a link packet that was already on the wire when the link was switched off N s ago arrived after it - ignored (not a violation, not a kick ...)), a count, and a summary line when the window closes. Nothing is flagged and nobody is kicked. A conforming client stops sending the moment it processes the Welcome, so the real window is a round trip plus a frame.
    • What did not change. The sender check still comes first (a forged sender id is dropped and audited, window or not). Only the two Alice hashes are covered: any other unknown routed hash from the same peer still goes to enforcement. A peer that never had a link, one connected after the switch-off, one that was never spoken to, and any peer after its half minute are judged exactly as before - a server with the link off and nobody paired behaves byte for byte as it always did. The gate also looks at the hashes while RoutedSenderGuardEnabled is off, so the window does not depend on that setting. A disconnect clears the peer's window. With the link switched back ON inside the window the live path consumes the packet as it always has (a stale one from before the re-pairing included).
    • Tests. New harness group LinkEnd (../WonderlandTests/vacuum-test, L1-L11, 16 checks): link off with no history goes to enforcement; the paired and the advertised peer are inside the window after Deactivate, a never-spoken-to peer and a stranger are not; a crossed request, a crossed Hello and a crossed ALICE_S2C are consumed; any other unknown hash is not; the window holds with the sender guard off; a forged sender is still dropped inside it; the crossing packets are counted; after 31 s the window is pruned and the same packet goes to enforcement again; a disconnect clears it; with the link ON the gate consumes. The real thing needs a client with a piece in hand and set key=AliceLinkEnabled value=false repeated (the rig's W3); confirmed live by the rig's run 7 on 2026-10-11.

Changed

  • ZdoInventoryIO.IsBusy is also true for a container the server has just handed to a player (see OpenContainer); nothing else about it changed.
  • ContainerRows gains IsPlayerBuilt(GameObject); ZdoInventoryIO gains the hand-over set (BeginHandover, OnPeerDisconnected, OnUpdate) used by OpenContainer.
  • ProductionSupplyEngine gains IsRunning, LastReason, TryDescribeStation, FindStations, PeerSimulates (read-only helpers for the link).

Verified

  • Release build, 0 warnings from the new files. Two headless 1.0 dedicated-server boots (testbed profile wl1120, throwaway world, Discord disabled, AliceLinkEnabled = true): BOOTED in 19 s, [RoutedRpcGate] self-test passed, Successfully applied Harmony patch set: Patch_ZRoutedRpc_RPC_RoutedRPC_Gate, [Alice] link ready; section 20 switch is ON, no exceptions. Harmony prefix ordering was NOT relied on and so not tested (HarmonyX 2.9.0 does not run on this machine's .NET 8; the question is moot with one prefix).
  • Escrow integration run (throwaway BepInEx test plugin in ../WonderlandTests/escrow-test/, kept out of this project so it cannot compile into the DLL; testbed profile wl1120, fresh world, Discord off, real ZDOs and Inventories, Wonderland.dll md5 as shipped): 61 of 61 checks pass - reserve, cancel (idempotent), commit (idempotent, no refund after), all-or-nothing, a shortfall writes nothing, two chests with an exact Taken echo, busy chest skipped and a busy shortfall answers Busy, someone else's private chest never used and your own private chest used, build and craft Disabled without the feature, build-with-station / non-station / empty / non-token requests refused, quality-2, cheated and crafted stacks ignored, expiry refunds, disconnect refunds, a refund waits while the chest is open, a destroyed chest is rehomed to a sibling with nothing lost, a journal that survives a simulated crash hands the debit back - also when the world was reloaded and the chest has a new id (found by position, a decoy chest that would win the neighbour logic stays empty) and when the chest did not survive (the stack goes to the item cache), a debit after the last save is dropped rather than duplicated, a failure part-way through the chest writes hands back only the written chests' shares (no duplicate), a journal caught with only its .tmp is read and cleaned up, and a refund never lands in another player's private chest or a non-player-built one.
  • Vacuum cooperation integration run (../WonderlandTests/vacuum-test/, same method as the escrow run, a fake Alice peer plugged in through the public IVacuumHost seam, the engine's own passes switched off so every move happens because a check asked for it): 159 of 159 checks pass - the proof rule including the OwnerRevision u16 wrap, answer-before-ZDO and ZDO-before-answer, no proof, a refusal leaves the claim path open, no offer within 2.75 m of the owner's character, foreign / duplicate / unknown answers, a stack another player was granted, the SetOwner shield, a chest busy or destroyed before the proof, three silent expiries mute the peer for 60 s, disconnect, a failed multi-offer send, the 24-open and 16-per-push caps, the PlayerOnIt back-off, per-chest settings inside the engine (off, filter into an empty chest, a sink ranked below a chest known to want the item, radius, not in force while disabled), every SetContainerPrefs rejection plus mask merge, defaults removal, radius clamp, privacy / range / not-player-built answers and the save/load round trip, the nudge rules, the toasts only after the chest write, and persistence - ContainerPrefs and SupplySwitch files name pieces by prefab and position, never by id, settings and switches follow a chest or station replaced by a NEW ZDO at the same place (what a world load does to every id), old user:id lines are skipped, pieces that are gone are dropped, nothing is written while lines are unmatched; and the link-end window (LinkEnd, see Fixed: a request that crossed the switch-off is consumed, a stranger and any other unknown hash still go to enforcement, the window closes and is pruned after 30 s, a disconnect clears it), and the late pickup (LatePickup, P1-P6: a client that picked a stack up in the instant the engine moved it into a chest reports its DestroyZDO one trip late, and the engine takes that stack's worth back out of the chest; a duplicate report, an unrelated destroy and the server's own session change nothing; an open chest makes the take-back wait until it is free). Three seeded conservation soaks come out exact (loose + chests + picked up at the start = chests + ground + picked up at the end): 1426 = 1255 + 171 (77 offers, 29 moved on proof, 6 refused, 30 expired), 1313 = 1268 + 45 (110 / 51 / 11 / 32), 1385 = 1292 + 93 (145 / 78 / 16 / 32); the same soaks with every pick-up delivered the way a client delivers one (through ZDOMan.RPC_DestroyZDO from the owning peer, so the late-pickup check sees it) are exact too, three runs of three rounds each. The soak counts its ground stacks by ZDOID. An earlier version walked the ZDO objects it had created at the start; a destroyed ZDO's object goes back to ZDOPool and is built into the next ZDO anyone creates, and on a freshly booted world that is the world generating its first zone - 45 of 45 objects had become _ZoneCtrl ZDOs (44) and a Leviathan, each counted as a stack of 1, a constant diff=45 (32 in one full run) in a world whose chests, ground and item cache were exact (the cross-check line SOAKALIAS prints both counts every round). Test harness only; no engine change.
  • BarrkBOT integration run (../WonderlandTests/barrkbot-test/): 64 of 64 checks pass - the player-reported file (every cap, a delta dropped whole is still Ok, the minimum gap, consent clearing, the registry round trip), the activity file (distance, portal and teleport jumps, sailing, biomes, boss fights credited from the latest sweep, chest materials, the client label, the rotating boss scan), the 24 h windows across an hour rollover, and the base file (stock pass in budgeted slices, the station census, the switch-off clearing the snapshot). The four files written for a populated registry were fed through BarrkBOT 6.1.20's own reader (tools/barrkbot/barrkbot-render-probe.mjs, and a multi-file variant): all four sync as separate exports, the three new ones at 4,553 / 4,880 / 3,807 compact characters (cap 6,000); the samples are tools/barrkbot/sample_{reported,activity,base}_populated.json.
  • Real crash test (../WonderlandTests/crash-test, two phases on a throwaway world): two chests, a reservation, a real synchronous world save (ZNet.Save(true): WorldSaveStarted fires and stamps the journal), a second reservation after the save began, then kill -9 of the server's own process and a restart on the same world and config folder. 6 of 6: the ticket debited before the save is handed back straight into its chest, found by position under its new id (30 item(s) to their chest, 0 to a neighbouring chest, 0 to the item cache), the ticket debited after the save began is dropped (the restored chest already holds it), the second chest holds exactly its 100, no escrow is left open, no journal file, nothing in the item cache. It is the test that found the recovery-order flaw above.
  • Final regression, 2026-10-11, one build: Wonderland.dll md5 d1c880fc86214afe643833a47e5f7c74 (sha256 763f28c618a31101f619138996d0d1af544f759b8c577860a644435128c83a96) - vacuum 159 / 0, BarrkBOT 64 / 0, escrow 61 / 0, crash test 6 / 0 (fresh world each, Discord off).
  • Live-test server (../WonderlandTests/live-oracle/, throwaway): the same dedicated server with the oracle plugin LiveOracle and a settings seed for the first run against a real Alice client - start.sh is ready in about 22 s, the fixtures (three chests, workbench, smelter, kiln, fire pit) survive a restart, and snapshot reconciles to the item: with production supply running and nobody online, chests + ground + stations + escrow + cache + burning fuel stayed exactly at the starting 230 Wood / 100 Coal / 60 Copper ore / 60 Tin ore / 100 Stone / 50 Flint over 45 s while the engine moved items into the kiln and the smelter. Real restarts: chest settings and station switches stored through the mod, then the earliest-loading fixture destroyed and the server stopped and started - every later ZDO id shifted by one (1:85 -> 1:84, smelter 1:87 -> 1:86) and every setting and switch was still on the same piece, matched by position.
  • Live rig (ALICE/tests/e2e, written and run by the Alice project, not by a player: a throwaway dedicated server built from this folder's Wonderland.dll with the LiveOracle ledger plugin, one headless Alice 0.12.0 client logged in as a non-admin, run directories under ~/valheim-testbed/alice-e2e-runs/). Several runs on 2026-10-11 drove the handshake and pairing, station ops, the vacuum release round trip against the real client (a pile of 20 stacks: 20 offers, 20 proofs by the server's own copy, 20 chest moves; the claim path for a stack at the player's feet), the nudge, the settings panel, the toasts, the player-reported statistics (and their removal on 'no'), crafting and building from chests with the escrow (reserve, commit, cancel), the link switched off while a reservation was held (it found the kick fixed above; its run 7 confirmed the fix live: the crossing request was ignored, the player stayed, the ledger was exact, the link was back 3.7 s later; 231 passed, 0 failed, 1 soft), a client killed with a ticket held (the stacks came back to the chest 30 s later, per-item totals exact), and a server kill -9 after a world save (journal recovery straight to the chest, totals exact). Every server-side ledger check - containers, ground, stations, escrow, item cache and the bag - was exact. Its V7 'race' round, in which a driver calls the game's Humanoid.Pickup on random stacks every frame while the server hands a pile over, first counted 10 / 15 / 5 / 10 Wood too many in four rounds. The server log showed no grant and no late-pickup in those rounds: the driver was picking up objects whose ZDO the server had destroyed in that very frame (an invalid ZNetView makes ItemDrop.CanPickup true, and Humanoid.Pickup then adds the cached item without sending anything; vanilla's auto-pickup and the E key both check IsValid() first - libs-Tools ITEMDROP sheet, section 13). With the driver limited to stacks whose view is valid, all four rounds are exact on both witnesses (the client's count and the server ledger: +150 each), with 23 to 25 dying objects per round seen and left alone. No engine change came out of it.
  • Not yet exercised: the ZNet.Shutdown refund (the crash test kills the process; a clean stop with a ticket open was not driven), and every platform other than a PC player on Steam (console peers are never advertised to).
  • What to look for on the live box after deploying (first Alice player): a [Alice] <name> (PC): paired with Alice ... line, then [SupplySwitch] ... via Alice lines when a station is switched, and for crafting [CraftEscrow] #N <name> (Craft): reserved ... followed by committed (or handed back (...)) - a reservation with no closing line is the thing to look for. For the vacuum: [Alice] sent N hand-over offer(s) to peer P, then [Alice] hand-over offer N for <zdoid> to peer P: proven by the server's own copy ..., then [Alice] hand-over ended in the chest: 40x $item_wood (stack <zdoid>) is in chest <zdoid>. - the last line is what tells a hand-over move from a claim-path move ([ItemLedger] Vacuum moved is printed for both); the tally [Alice] vacuum cooperation so far: ... is logged every ten minutes while anything happens and once when the link stops.
  • The routed-sender check rests on the decompile facts above; it has not seen a real player's traffic. It can be switched off live (RoutedSenderGuardEnabled = false) if anything unexpected shows up in wonderland_security.log as [SECURITY:RoutedSender] for an unmodded client.
0.11.2

Changed

  • Rebuilt against Valheim 1.0.16 (client build 25527674 / dedicated server build 25527701, network version 40, unchanged from 1.0.15) and re-verified: a static reference check against both the client and dedicated-server assemblies, and a headless 1.0.16 dedicated-server boot. No source changes were needed for compatibility — 1.0.16 removed only ObjectDB.GetAllFoodItems() and ButtonSfx.Start(), and this mod calls neither.
  • Dropped stale references to specific past Valheim patches (Steam build ids, network-version numbers, versioned-decompile citations) from the csproj, README and source comments; they now read version-agnostically ("Valheim 1.0", "the vanilla server decompile") since the mod targets whatever the current 1.0.x dedicated server is rather than one pinned patch.

45 older entries, full version history & downloads →

Files

5 files · 440 KB download

Loading files…

Manual download
Just this mod One .zip — Wonderland 1.12.1
Files you'll get 2

Your browser may ask permission to download several files at once. How to install these manually

Manual installation instructions
1

Install BepInExPack Valheim

BepInExPack Valheim is required to run mods in Valheim.

Download BepInExPack Valheim 5.4.2360 · View mod page

Check out the mod page for detailed installation instructions.

2

Install Wonderland

This mod only needs to be installed on the server.

Download Wonderland 1.12.1

Extract the ZIP and place the file(s) into the BepInEx/plugins/ folder inside your Valheim game folder.