Personal boss progression. On by default — read the first bullet before updating a running server.

New

• Boss progress is personal to each character. Vanilla keeps boss kills as world keys: one player beats Eikthyr and every player — including one who joined five minutes ago — gets Haldor's and Hildir's later stock, the harder spawns and the later raids. ServerGuard now keeps progress per character (SteamID + character name) in conf/progress.yaml, and each player's game only ever receives the progress their own character has earned. World modifiers (no map, damage rates, ...) stay shared.
  • Who earns a boss: every player who damaged it and was within 50 m when it died (progressionRequireDamage, progressionCreditRadius). The same goes for the troll, surtling and bat keys that unlock raids, except that a creature killed in one hit falls back to "within 50 m". Hildir's quest rewards go to the player who handed in the chest.
  • Raids follow each player's own progress: the Player based raids world modifier is switched on (progressionForcePlayerRaids) and ServerGuard makes sure every raid — not only the ones vanilla already handles per player — checks the targeted player's progress. Switching the feature off switches the modifier back off if ServerGuard was the one that turned it on.
  • Existing characters keep their progress. The first time each already-registered character logs in, ServerGuard imports the boss kills their character file records (vanilla gives those to everyone near a kill), limited to bosses this world has actually seen (progressionSeedFromCharacters). New characters, and characters brought over from single-player, start from scratch; progress the server never granted is removed from the character and reported to the admin channel.
  • Personal start temple. The boss altars show only the trophies the viewing character offered. Offering a trophy lights the altar for that character alone, a forsaken power can only be chosen from an altar you filled yourself, and a trophy only takes hold once you have defeated that boss yourself (enablePersonalTemple, personalAltarsRequireKill). A power chosen from someone else's trophy is cleared on login. Trophies already sitting on the shared altars are hidden, not destroyed — switching the feature off shows them again.
• sg progress — sg progress <player> shows a character's progress and altars; grant / revoke <player> <boss|key|all>, altar <player> <boss> [on|off] and reset <player> change it, and the player's game updates immediately. <player> is a character name, a SteamID, or steamid:name. Changes are posted to the admin channel. sg status has a new Progress line.
• Discord: a first-time boss kill is announced in the public channel ("Alice and Bob defeated The Elder for the first time!", staff left out as usual). The admin channel gets every credit with the players involved and anyone who was nearby without damaging the boss, one-time imports, and players arriving with progress the server never granted (progressionDiscordPosts).
• A ledger belongs to one world. Start a new world and the old progress.yaml is archived as progress.<worldid>.yaml.bak and a fresh one begins.
• If progress.yaml cannot be read, the feature switches itself off (shared vanilla progress) and nothing is written until the file is fixed — a bad hand edit can't wipe everyone's progress.
• The new settings are appended to an existing settings.yaml on first boot. progressionKeys decides which keys count as progress (default: every defeated_* boss, killedtroll, killed_surtling, killedbat, and Hildir's hildir* quests).

Upgrade note

• Players must update too — the altars, raid checks and character-file sync run on each player's game. As always, keep the server and your modpack on the same version.
• The feature is on by default. Set enablePersonalProgression: false in settings.yaml before starting 2.1.0 if you want to keep shared vanilla progress.

New

• sg unregister <steamid> [character]. Forgets one registered character name, or every name for that SteamID when no character is given, so the player can register fresh ones. Use it with sg pardon and sg unban to fully reset someone who tripped the character limit.

Fixed

• registrations.yaml and violations.yaml are now hot-reloaded, like the rest of conf/. They used to be read once at boot, so edits made while the server was running were ignored and then overwritten by the next strike or registration. In practice this meant sg unban on a player over characterLimit did not stick: the server still held their old names and strikes in memory and re-banned them on the next login. sg reload now re-reads these two files too, and sg help describes it accurately.

New

• Cheat-check bypass key. The console command yesiuseddevcommandsbutiwantmyachievementsanyway sets a key on the character after which Valheim marks nothing that character does as cheated — items spawned in single-player then arrive on your server unmarked, and cheat-taint detection cannot see them. ServerGuard already reported the key once per session; a new setting, cheatTaintBypassPolicy, decides what happens next: log (the default) keeps the admin-channel post, kick also disconnects the player with a message explaining why, until they log in with a character that has never run the command. No strike, nothing is written to their character, owners are exempt. The setting is appended to an existing settings.yaml on first boot, with comments; sg status shows it on the CheatTaint line.