Hoard

A hoard for your enchanted gear, shown as a list you can sort and filter instead of a chest grid. A Hoard inside your ward opens your ward's own store, shared with the players on that ward. A Hoard outside any ward opens a store the whole server shares (or, if the server chooses, each player's own). Stores grow as you beat bosses. A second piece, the Rune Cache, is a labelled shelf for runestones, shard stones and enchanting materials.

Requires EpicLoot. The Hoard only takes enchanted equipment.

The Hoard

• Build it with the hammer (Misc) near a workbench: 20 Wood, 10 Stone, 5 Resin.
• Items are kept on the server, not in the piece, so removing a Hoard with the hammer loses nothing. Nothing damages it: raids, fire, weather and losing its support all leave it alone.
• It takes identified EpicLoot magic equipment, from any mod. Plain gear, unidentified items and materials are refused with a message.
• You have to stand within 5 m to use it.
• An item from a mod you removed stays in the Hoard as "Unknown item" until the mod is back.

Which store a Hoard opens

• Inside a player's ward: that ward's own store. Only the ward's owner and the players on its list can open it. Every Hoard inside the same ward opens the same store. A new ward starts with an empty store.
• Outside every ward: the shared store, which every such Hoard opens. A server can set this to each player's own store instead (UnwardedHoards); then the shared store can't be opened until it's set back.
• Several wards over one Hoard: the ward whose store was set up first wins. If none has a store yet, the nearest ward.
• A switched-off ward: its store still opens, for the players on its list. While a ward is off, anyone can add themselves to its list at the stone, so the window warns you. A server can make it owner-only (OffWardAccess).
• A ward that's gone or switched off: its store is kept for its owner. Place a new ward and open a Hoard inside it: the window offers Claim. Claim before depositing there, because a deposit starts a new store for that ward instead.
• The window's title always says which store you're in: Shared, Yours, or someone's ward.

Only the base game's wards count, and mods that use them (such as ProtectiveWards). Wards from WardIsLove, ArcaneWard or LegacyWard aren't recognised: Hoards near them open the shared store. If a mod changes the ward range only inside the game (ValheimPlus, BetterWards), set WardRange to the range it uses.

Tiers

Every store starts at 40 slots and upgrades on its own. You can upgrade at any Hoard of that store, one tier per boss. The boss has to be dead in the world. The materials come from your inventory, or with AzuCraftyBoxes also from nearby chests, as crafting does. The chest's look changes as it grows, and coin piles appear around it.

The window

• To deposit, drag gear onto the list or Ctrl-click it in your inventory. To take, click a row or drag it out.
• Deposit all magic gear leaves your hotbar, equipped items, AzuExtendedPlayerInventory's slots and your QuickStackStore favourites where they are.
• Filters: name, rarity, type, biome, upgrade level, set pieces, enchantments (all or any, with minimum values), and up to three stat rows like "damage >= 120". Click a column to sort by it, and again to reverse.
• Hovering a row compares the item with what you have equipped.
• History tab: the store's recent deposits, takes, upgrades and claims, with who and when. Anyone who can open the store can see it.
• Taking needs a free inventory slot. If your inventory fills up before the item arrives, it waits until you make room.
• The game saves your character before a deposit when the item isn't in your last save exactly as it is now (picked up, crafted, enchanted or taken from the Hoard since). That save is what lets Hoard recover from a crash without losing or duplicating anything.
• Gamepad: the stick moves through the list, A takes, X deposits all, Y changes the sort, LB moves to the list (press it again to switch between Items and History), RB goes back to your inventory, and B closes. A on a Claim row claims it. Filters and the Upgrade button need a mouse.

The Rune Cache

A wardrobe with a shelf inside: one labelled slot for each material, rows Magic to Ancient, columns Dust, Essence, Reagent, Shard and Runestone. Empty slots show the material's faded icon. Shard stones and etched runestones go in the loose cells beside and below the shelf.

• Build it with the hammer (Misc) within 10 m of an enchanting table: 10 Fine wood, 8 Iron.
• It only takes runestones, shard stones and enchanting materials.
• Each material has exactly one slot, holding one normal stack. A material always goes to its own slot, however you add it (drag, quick-stack, Store All, MultiUserChest). When its slot is full, the add is refused with a message.
• QuickStackStore's Sort tidies it: every material back to its slot, everything else into the loose cells.
• Recycle_N_Reclaim's Reclaim all does nothing on a Rune Cache.
• Anyone can open it, and wards apply. It can't be damaged, and the hammer only removes it once it's empty.
• With AzuCraftyBoxes, enchanting pays from a nearby Rune Cache. Its contents can't be sacrificed.
• RuneCacheShelfView (a per-computer setting) turns the labels and icons off; the slots and rules stay the same.

Installing

Install Hoard on the server and on every client, all on the same version.

If you use these mods, add the Rune Cache to their exclusions:

• AzuAutoStore, in the server's Azumatt.AzuAutoStore.yml, so auto-store doesn't fill it:

  hoard_runecache:
    exclude:
      - All
  

• PlanBuild: add hoard_runecache to Excluded plan prefabs, or a planned Rune Cache can be finished away from an enchanting table.

Updating from 1.0

• Take a backup of the world folder first.
• On its first start, 1.1 converts the Hoard's files and keeps a copy of the 1.0 files next to them (see "Going back to 1.0" below).
• Everything already in the Hoard stays in the shared store, at its tier. A Hoard that stands inside a ward now opens that ward's new, empty store, at tier 0. To move your items, take them out at a Hoard outside every ward, then deposit them at your ward's Hoard. With UnwardedHoards on its default Shared, an admin can instead turn WardStores off for a moment: every Hoard then opens the shared store. Move the 1.0 items before switching UnwardedHoards to Personal: the shared store can't be opened while it's set to Personal.
• Rune Caches become wardrobes where they stand. The first time each one is opened, it moves its items into the new slots; nothing is removed. If a cache held two stacks of one material, the second goes to a loose cell: drag it onto the material's slot to merge them. The wardrobe is bigger than the old chest, so it can clip into walls; moving it means emptying it first.

Settings

BepInEx/config/helix.hoard.cfg. The server's values apply to everyone. Admins can change them in game with a configuration manager, and a hand edit on the server is picked up within a few seconds.

Turning a setting off never moves or deletes items. With WardStores off, ward stores keep their items until it's back on. With UnwardedHoards switched, the other kind of store keeps its items until it's switched back.

For admins

The stores live in the server's worlds_local folder, next to the world:

• <World>.hoard with .old and .old2 backups
• <World>.hoard.journal*, a record of every change
• <World>.hoard.<date>, a copy taken at every world save (the newest 10 are kept)

Players' games keep a small recovery file in a Hoard folder in their local save folder. Don't delete it.

Admin commands, in the console or in chat with a leading /:

To roll the world back, stop the server, then:

1. Restore the world backup.
2. Move every <World>.hoard* file, including the journal, into another folder. If the journal stays, the server replays it and undoes the rollback.
3. Copy the <World>.hoard.<date> taken at the same world save back as <World>.hoard.

Characters don't roll back with the world, so items taken or deposited since can end up doubled or missing, the same as with any chest.

forcedelete on a Rune Cache deletes everything in it. Empty it first. A Hoard piece is safe to remove.

Going back to 1.0

1.0 refuses the files 1.1 has written and changes nothing, so the Hoard stays off until you reinstall 1.1 or restore the copy 1.1 kept when it converted them.

What a restore loses: the Hoard goes back to exactly what it held at the update. Items deposited since, including everything in every ward store and personal store, are gone. Items taken out since are back in the Hoard while the players still have them.

To restore:

1. Stop the server.
2. In the server log, find the newest [store] migrated … 1.0 copy v1-<stamp> line. That stamp's set, the one with the newest <World>.hoard.v1-<stamp>.done file, is the one to restore. An older complete set is an older state, and a set without a .done file is incomplete: never restore it.
3. Move every other <World>.hoard* file out of the worlds folder.
4. Check each file the .done lists: its size and its CRC-32 (the checksum zip uses), for example python3 -c "import sys,zlib;d=open(sys.argv[1],'rb').read();print(len(d),format(zlib.crc32(d),'08x'))" <file>.
5. Rename each listed copy back to the original name it lists (drop .v1-<stamp>).
6. Move the .done file itself aside, then start 1.0.

Limitations

• If your game crashes, an item you took comes back only if it was still in your inventory. One you had already moved into a backpack or an AzuExtendedPlayerInventory loadout is lost, as with a chest.
• A crash within a frame of an item leaving your inventory can duplicate it.
• With MultiUserChest:
  • An item you took and then put in a chest another player's game is handling can be lost, if that chest refuses it in a rare race and your game crashes before the next save.
  • If someone sorts a Rune Cache, or it converts on its first open, at the same moment another player drags an item into it, that item can be lost. MultiUserChest has the same race on any chest someone sorts.
• After a crash mid-transfer, log back in on the same computer. The recovery file doesn't travel with your character.
• A store belongs to a character, not an account. A new character doesn't see an old character's personal store or ward stores (an admin can hand them over with hoard reattach … transfer).
• A ward rebuilt by the same player at exactly the same spot gets its old store back; anywhere else it's a new ward, and the old store waits to be claimed.
• While a ward is switched off, anyone can join its list at the stone, and the ward's owner can't remove them. This is how the base game's wards work.
• With AzuCraftyBoxes, upgrade materials taken from a chest another player's game is handling can come back, as with any AzuCraftyBoxes craft.
• Range checks trust the positions players' games report, like other chest mods.

Uninstalling

Empty every Rune Cache first. The Hoard's items stay in <World>.hoard and come back if you reinstall 1.1.