Loothing

Fixed

• Council members and Master Looter settings now refresh immediately when the raid leader / Master Looter is passed from one player to another, even outside an active session. Previously, when leadership transferred, every observer kept seeing the previous Master Looter's council, MLDB settings, and observer list until the new Master Looter happened to broadcast — and even then the council UI didn't always repaint. Loothing now (1) clears the previous Master Looter's cached council and observer roster on every leadership change, (2) wires the Council Table to repaint on roster updates, and (3) detects the handover server-side and accepts the new Master Looter's MLDB / SESSION_INIT broadcasts even if observers' cached ML identity hadn't yet caught up to the new leader.

Added

• "Continue or Start Fresh" handover prompt for the new Master Looter. When a different player passes Master Looter to you, a modal asks whether you want to inherit the previous Master Looter's session, council, and MLDB settings, or discard them and start fresh with your own.
  • Continue keeps the previous Master Looter's council (promoted into your local roster), MLDB, and any in-flight items, and rebroadcasts a single bundled SESSION_INIT so observers re-anchor to you as the authoritative session owner — including the live items list so council members who joined after the handover see the same item set.
  • Start Fresh ends any orphaned session, restores your own pre-session settings snapshot, clears the previous Master Looter's council / observer rosters, and broadcasts a clean state to the raid as a single bundled SESSION_INIT.
  • Shows on every true handover (a different player previously held ML in this session), regardless of your ml.usageMode preference. After your decision, the existing "use Loothing for loot distribution?" usage-mode flow runs as before.

Hardened

• Observer-side MLDB acceptance now recognizes a new group leader as authoritative even when local cached ML identity is stale. Previously, if your explicitMasterLooter was still pinned at the previous Master Looter (set by their MLDB push), the new Master Looter's first MLDB broadcast was rejected as "from non-ML" — leaving you stranded on the previous Master Looter's settings until something else cleared the pin. Loothing now accepts an MLDB broadcast when the sender is the strict group leader (rank 2 in raid, UnitIsGroupLeader in party), and clears the stale explicit pin so subsequent ML resolution agrees with the leader.
• SESSION_INIT is similarly accepted from a strict group leader on handover. The bundled session-state broadcast applies the same leader-override rule so observers can't get wedged on stale ML state for the duration of the new Master Looter's first push.
• SESSION_END accepts the current group leader as a third authority path. Defense-in-depth so a "Start Fresh" handover always lands on observers — previously the receive handler relied on either the current ML or a recent MLDB sender being the originator, both of which could be stale during handover.
• SessionPanel now repaints fully on MLDB or council changes instead of only refreshing its footer. Several buttons in that panel gate enable / show on HasMasterLooterVisibility(); without a full refresh, button state could remain stale through a handover.
• A previous Master Looter's late farewell messages still authenticate after handover. When you accept or decline a handover, Loothing seeds the previous Master Looter into the recent-MLDB-senders table so a STOP_HANDLE_LOOT or SESSION_END queued under combat restrictions on their end doesn't get silently dropped on yours.
• Re-entries into the ML check while the handover modal is open are now suppressed, so roster churn (resurrects, vehicles, joins/leaves) can't race with AcceptMLHandover / RejectMLHandover mid-flight and clobber state.