ProgressGuard
Server-side progression control. Protects players from content beyond their progress and provides expanded boss-stone progression management.ProgressGuard
ProgressGuard 0.2 replaces ZenBossStone with a two-step boss progression system and protects the least-progressed connected character from advanced ambient roamers and raids.
For each vanilla Forsaken boss:
- a player must damage the boss and witness its death to earn a kill receipt;
- boss death does not set the world-wide
defeated_*key; - a receipt holder must return the matching trophy to its Forsaken altar;
- only nearby receipt holders receive personal boss credit and power access;
- the sacrifice commits the world key and releases withheld boss loot.
The altar remains a normal trophy hook: E/Use selects powers, while using the matching trophy directly on the hook makes the offering. It proceeds immediately when every connected receipt holder still needing credit is in range. A non-consuming warning appears only when someone is outside the radius; a second use within 15 seconds deliberately proceeds without them.
New players receive in-game guidance on their first two login sessions per character/world. Qualified fighters see a kill-receipt confirmation, the trophy carrier is warned to gather the group, connected receipt holders are told who has the trophy, and the altar displays personal receipt/credit status.
Existing progress is preserved additively. ProgressGuard imports every exact legacy guardian-power key, retries until acknowledged, upgrades 0.1 registry records, and never clears existing world keys or character keys. Server admins can verify connected characters with pg audit.
The current server profile's trophy behavior is built in by default: 25-metre sacrifice range, 400 weight (Eikthyr capped at 200), one-per-stack, no auto-pickup, wooden-portal restriction, and altar loot after a 12-second presentation.
The original spawn safety remains: the least-progressed online character limits managed out-of-biome roamers and raids. Event Monuments of Torment are blocked outside the Ashlands and allowed inside it.
Requires the same ProgressGuard version, BepInEx, and Jotunn on the server and every client. Remove ZenBossStone before installing 0.2; the mods are intentionally incompatible. Back up the world, character profiles, and ProgressGuard registry before the upgrade, then reconnect established characters and run pg audit.