Please disclose if any significant portion of your mod was created using AI tools by adding the 'AI Generated' category. Failing to do so may result in the mod being removed from Thunderstore.
YouAreNotWorthy
Progress at your own pace in a shared Valheim world. Unlock trader goods, raids, creature spawns, gear, food, doors, feasts, and boss summons per character. Defeat enemies together for personal unlocks while everyone keeps their own journey.
| Date uploaded | a month ago |
| Version | 1.0.2 |
| Download link | sighsorry-YouAreNotWorthy-1.0.2.zip |
| Downloads | 34 |
| Dependency string | sighsorry-YouAreNotWorthy-1.0.2 |
This mod requires the following mods to function
denikson-BepInExPack_Valheim
BepInEx pack for Valheim. Preconfigured with the correct entry point for mods and preferred defaults for the community.
Preferred version: 5.4.2351README
You Are Not Worthy
Per-character progression for Valheim.
Showcase
Personal progression
Characters sharing one world can see different trader stock based on their own progression.

Item restrictions
Equipment, consumables, and feasts show their missing requirement and remain unusable until the character earns the required key.

Doors and boss summons
Personal progression also applies when using key items on locked doors or activating boss altars.


Mod integrations
Other mods can reuse YNW's personal-key checks and localized blocked message for their own interactions.

You Are Not Worthy (YNW) personalizes supported value-less, non-reserved
globalkey checks by using Valheim's native character unique keys. Players in
the same world can therefore have different trader stock, raid eligibility,
spawn eligibility, and item-use progression.
Value-bearing keys, reserved modifiers, seasonal keys, and other shared world state keep their Vanilla behavior.
Features
- Personalizes compatible Vanilla and modded global-key progression.
- Grants supported event keys to active players within 32 metres of a death, interaction, or requesting player.
- Adds simple creature-defeat keys through
defeatKeys. - Gates the final use of tiered items without blocking collection or crafting.
- Respects the server's actual Player based raids setting.
- Synchronizes the server's
progression.ymlto clients. - Provides admin commands for connected Steam players.
Configuration
defeatKeys is the only reserved root field. Every other root field is an item
tier, ordered from lowest to highest.
defeatKeys:
- prefabs: [Serpent]
key: defeat_serpent
Meadows:
- Wood
- Stone
BlackForest:
requiredKey: defeated_eikthyr
resources:
- HardAntler
- Bronze
- TrollHide
Swamp:
requiredKey: defeated_gdking
resources:
- Iron
- Entrails
- CryptKey
SerpentItems:
requiredKey: defeat_serpent
resources:
- SerpentMeat
- Tier names are labels, not biome checks.
- Creature and resource names are internal prefab/item names.
defeatKeysgrants its key around the defeated creature; it does not require the killing blow.- Vanilla and modded defeat global keys normally do not need duplicate
defeatKeysrules. - Items can inherit tiers through recipes, cooking, fermentation, and smelting.
- A sequence-form tier has no
requiredKeyand classifies resources without restricting them.
Item restrictions
When a character lacks an item's resolved requiredKey, YNW can block:
- equipment and ammunition use;
- food, potion, and other consumable use;
- direct boss offerings and final item-stand altar activation;
- key-item use on locked Vanilla doors;
- InventorySlots equipment routes when InventorySlots is installed.
Gathering, pickup, crafting, cooking, fermenting, building, repairing, combat, and biome movement remain unrestricted. Players may prepare an item early, but cannot perform its guarded final use until they earn the key.
Item-restriction bypass requires both server-admin status and Vanilla debug mode. This bypass does not disable global-key, raid, or spawn personalization.
Multiplayer behavior
Personalizable global-key writes are kept out of shared world progression. Supported death and interaction paths grant the same literal as a native character key to active players within 32 metres of the relevant source.
Trader and ConditionalObject checks use the local character. Raid and spawn
patches evaluate their supported key conditions against the relevant character
instead of treating every player as equally progressed. Raid instances, spawn
timers, opened doors, and spawned network objects remain shared world systems.
Mod integration API
YouAreNotWorthyApi.ApiVersion identifies the public API contract. Version 1
provides QueryLocal(key) for the current character, QueryPeer(peer, key) for
an authenticated character on the authoritative server, and
TryShowLocalMissingRequirement(key) for integrations that have already
established a missing local requirement and want YNW to own the localized
center message and its shared one-second cooldown.
Both query methods return KeyQueryResult, distinguishing personal and shared
keys, present and missing keys, invalid input, and temporarily unavailable
character or snapshot data. Integrations should treat Unavailable as
fail-closed and must not read the internal YNW_PersonalKeys ZDO payload
directly. Calls must run on Unity's main thread, and transient join or respawn
results must not be cached permanently.
TryShowLocalMissingRequirement validates and canonicalizes the key but does
not evaluate whether it is missing. It returns true only when a message is
actually displayed; invalid or unavailable requests and requests suppressed by
the cooldown return false.
Supported value-less, non-reserved keys return a Personal* result. Reserved,
seasonal, and value-bearing world keys retain Vanilla shared state and return a
Shared* result.
Remote personal-key snapshots are owned by the client character. Peer and character validation prevents accidental cross-player queries, but the API is not an anti-cheat substitute for a server-owned progression ledger.
Admin commands
Server administrators can manage the native personal keys of a connected Steam player's current character:
| Command | Purpose |
|---|---|
ynw:keys players |
List connected players and SteamID64 values |
ynw:keys list <SteamID64> |
List the character's personal keys |
ynw:keys add <SteamID64> <key> |
Add a personal key |
ynw:keys remove <SteamID64> <key> |
Remove a personal key |
ynw:items refresh |
Re-scan and update the authoritative server items.reference.yml |
Personal-key command targets must be online through the Steam backend. Character names, character IDs, crossplay identities, and offline characters are not supported.
ynw:items refresh may be requested by a connected server administrator, but
the scan and file write always run on the authoritative server. It uses the
server's currently applied effective progression.yml and loaded runtime; it
does not read the requesting client's local YAML or write a client reference.
Generated references
After the authoritative world finishes loading, YNW generates these files in the same configuration directory:
| File | Contents |
|---|---|
keys.reference.yml |
Discovered global keys, personal/shared handling, defeat prefabs, and Player based raid keys |
items.reference.yml |
Statically discovered player-facing item-use targets and their final required keys |
items.reference.yml is grouped by best-effort prefab owner and raw Valheim
ItemType. Within each type, keyless entries come first, followed by the order
in which each requiredKey first appears in progression.yml, then prefab name.
Both files are generated reference material. YNW does not read them as configuration or send them through ServerSync, so editing them has no effect.
CHANGELOG
Changelog
1.0.9
- Fix Path of Valheiman 4.10.1 world records being blocked or converted into personal keys: monolith layout, placement, reset, completion and cooldowns, plus runestone discovery, dungeon completion and legacy place records.
- Preserve PoV's native character records and YNW's personal boss progression. Only the identified world-key families are shared; no PoV dependency is added. Update YNW on the host/server and clients.
- Keep public API v2 and its existing signatures and result values. The reserved PoV keys now return shared-key results and cannot be configured as personal requirements.
- Add regression checks for PoV key families, long layouts, cooldown/total queries and similarly named personal keys.
- Existing saves are not migrated or repaired. Back up affected worlds before loading: if PoV's reset marker is missing, its own initialization can remove existing world monolith completion records.
1.0.8
- Add read-only API v2 item-use checks for the local character and authenticated server peers, allowing integrations to waive item costs while preserving progression requirements. Unavailable item or character data does not authorize use; existing key-query contracts are preserved.
- Support BossRules 1.1.2 personal first-victory Queen and inner Frozen King summons. The external Frozen King gate remains paid, and final completion uses
defeated_frozenking_p3. Install both updated mods on the host/server and clients. - Reuse the existing item-tier cache and personal-key snapshots without changing saved keys or progression YAML. The new strict item-use API does not apply an administrator/debug bypass; existing native item restrictions are unchanged.
- Add API contract and result regression checks, and update the BepInEx package requirement to 5.4.2351.
1.0.7
- Increased the personal-key grant radius from 32 to 64 metres so nearby players can receive progression credit from large or airborne enemies more reliably.
- Simplified item-reference write states and centralized console-command registry ownership checks without changing commands, permissions, or network behavior.
- Added regression checks for console-command registration, replacement safety, repeated shutdown, and client/server game-assembly compatibility.
- Rewrote the package description with concise Valheim multiplayer, personal progression, raid, spawn, item-tier, and server-sync search terms.
1.0.6
- Added compatibility with Valheim 1.0.7, including updated spawn, tooltip, item-stand, location-icon, and private Harmony targets.
- Fixed Vanilla boss progression keys being misclassified after the
GlobalKeyslayout changed. - Updated the embedded ServerSync implementation for the new
ZRoutedRpc.Everybodyconstant contract. - Kept YouAreNotWorthy active when an installed InventorySlots version fails before registering its own patches; only the unavailable optional hooks are skipped.
- Added 42 Valheim 1.0.7 resources to the default progression map, including Deep North materials under
defeated_fader, while preserving production-path inheritance and existing tier assignments. - Expanded compatibility checks to validate original client and dedicated-server assemblies, Harmony targets, transpilers, and both embedded and installed progression configuration.
1.0.5
- Reduced allocations during repeated item-tier checks and personal-key grants while preserving progression rules.
- Consolidated identical administrator RPC checks without changing authorization or network messages.
- Added a reproducible managed regression harness for item-tier resolution and spawn/death transpilers.
- Added automatic local game DLL updates after successful Debug builds with
DeployToGame=true. - Removed outdated resource counts from the progression documentation.
1.0.4
- Added per-character minimap visibility rules through the new ServerSynced
locations.yml. - Added Expand World Data location-prefab resolution while preserving custom icon, size, and animation tokens.
- Added independent validation, hot reload, and last-known-good handling for location rules.
1.0.3
- Fixed personalized GlobalKey queries for remote players on dedicated servers.
- Fixed boss and event personal keys not reaching nearby remote players on dedicated servers.
1.0.2
- Fixed dedicated-server admins being rejected by client-side ServerSync checks for
ynw:keysandynw:items refresh. - Fixed runtime peer authentication to use Valheim's public connected-peer APIs.
- Fixed
ynw:keys playersexcluding connected characters whosePlayerobject was not instantiated on the dedicated server.
1.0.1
- Fixed personal progression restrictions for ItemStand-style boss altars such as Moder and Yagluth.
- Hardened personal-key distribution and fallback handling to avoid lost progression on failed requests.
- Improved item-tier resolution, generated item references, and InventorySlots compatibility diagnostics.
- Improved startup cleanup and compatibility with modded SpawnSystem patches.
1.0.0
- Initial release.