Added

• /title command (chat) and title command (F5 console): pick which of your earned titles the server shows with your name in its Discord narration, Chronicle log and web dashboard on servers running TheRavensCall 1.7.0+ — nothing changes on your in-game nameplate. title alone lists what you've earned and which one is active, title <name> (multi-word titles supported, e.g. title Wolf Hunter) sets it, title clear shows no title (and on TheRavensCall 1.7.0 it stays that way: titles you earn later are listed, not shown, until you pick one). The server has the only say on which titles you've actually earned — this mod just sends the request and prints whatever TheRavensCall answers.
• RavensCall_EventReport_V2 Event Type 13 (TitleRequest): the wire packet /title sends — schema version 2, op 1 = list, 2 = set, 3 = clear. See HANDOFF.md §2.2 for the full layout.
• RavensCall_TitleReply_V1: a new server → client routed RPC, registered once per world session the same way TheRavensCall registers its own listeners. TheRavensCall sends the reply text directly to the requesting player; this mod prints it back into whichever window (chat box or F5 console) the command was typed in, prefixed [WhereTheCrowFlies]. The reply now also carries the requesting player's full earned-title list and active title, so the title panel below is always fresh after any op with no second round trip.
• The title panel (/titles chat, titles F5 console, or the new TitlePanelKey config): a small window, on the family's shared gilt-frame theme (vendored from ValkyriesCargo, MIT, by Wubarrk), listing every title you've earned as a button — click one to set it, "No title" to clear it, Esc or Close to leave. It asks the server on open and refreshes after every click over the same wire the title command uses. While it's open your character holds still — movement, attacks, the map and chat are paused, the same way the game's own sign-text dialog pauses them.
• ravenscall title <player> [<title>|clear]: the existing admin routing stub's description now mentions the matching admin subcommand TheRavensCall 1.7.0 adds — no wire change on this mod's side, the stub only ever routes the raw command text to the server.

Compatibility

• Pairs with TheRavensCall 1.7.0+ for /title to get an answer, and needs AcceptClientReports on (it disables the player /title path the same way it disables every other client report; the admin's ravenscall title still works). On an older TheRavensCall, or a 1.7.0+ server with AcceptClientReports=false, the request still sends (Event Type 13 is just another RavensCall_EventReport_V2 payload) but nothing replies, so after 5 seconds this mod prints a one-time hint naming both possible causes. An older TheRavensCall with LogCombatReports enabled will additionally log an "unknown eventType 13" line server-side — harmless, just noise.
• Every other event type, and every server this mod already worked with, is unchanged.

Fixed

• Harvests were credited to the zone owner, not the picker. The pickable hook was a prefix on Pickable.RPC_Pick, which runs only on the client that owns the pickable's zone, so every berry another player picked in that zone was reported under the owner's name, and a second player picking an already-picked bush produced a phantom harvest. The hook is now a postfix on Pickable.Interact, which runs on the picking player's own client, and it skips a pickable that was already picked, plus any repeat of the same pickable within two seconds, because a non-owner's picked flag only updates when the owner's reply lands and holding Use re-runs the interaction every 0.2 s. The amount uses the same drop-scaling formula the owner uses; the rare skill-bonus yield is rolled inside the interaction on the picker's own client into a local a postfix cannot read, so it is not counted (the owner adds whatever value the picker sent, unvalidated).
• Failed crafts were counted, multi-crafts were undercounted. InventoryGui.DoCrafting returns early (max quality, missing requirements, inventory full, missing DLC, upgrader resource missing) with the recipe still selected, and it fires when the craft bar completes, so "inventory filled while the bar ran" is ordinary play; the old postfix reported all of those as crafts and sent the recipe amount, ignoring multi-craft and the station bonus. The item is now counted at its target quality before and after: zero difference means nothing was made, and the difference is the real amount. An upgrader that fails or breaks the item no longer reports an upgrade.
• Absolute stats double counted every full-sync cycle. The full snapshot never cleared the pending delta window, and both timers reset to zero instead of subtracting their interval, so they drifted and the snapshot landed inside a delta window; the next delta flush was then added on top of the snapshot on the server. Pending deltas now go out before every snapshot (the spawn backfill included), and both clocks subtract their interval.
• ravenscall season start | end can now be typed from a client. A routing stub registers the name flagged server-only and remote, so the game sends it to the server, which checks the admin list and runs TheRavensCall's real command (any TheRavensCall that registers the command, confirmed back to 1.2.2; the server-side flags added in 1.2.4 do not gate a routed command). Non-admins get "You are not admin" from the server.
• Docs said 105 vanilla stats. Valheim 1.0 has about 205; the handoff and README now say so.

Fixed

• Player deaths were never reported. The death hook was a Harmony patch on Character.OnDeath, but Player.OnDeath is a full override that never calls base, so the patch only ever ran for creatures and SendDeath was dead code from the first release. Death narratives, death_history, PvP killer attribution and the Discord death post have all been silent on every server. Player deaths now have their own Player.OnDeath patch, which runs on the victim's own client only (the method itself returns early for every non-owner). Creature kills were never affected. No wire change: the V1 type-2 death packet is the one every TheRavensCall since 1.1.0 already credits; the V2 Death packet is additionally understood from TheRavensCall 1.2.0, which first registered the V2 receiver. Pairs with any TheRavensCall 1.1.0 or newer; 1.2.3 additionally binds every self-report to the sending peer, which a 1.1.2 client passes unchanged.