v0.8.2

Pandy Guild Management

v0.8.2 (2026-10-24)

Full Changelog Previous Releases

• v0.8.2: raid-night and sync fixes, Bulk Actions safety, speed, rank picker
• Profile: pick a rank and set it in one click
  Promote and Demote become a rank dropdown (ranks below yours, the current
  one marked) and a secure Set rank button carrying as many /gpromote or
  /gdemote lines as it takes, up to one macro's 255 characters. Ranks your
  rank can't move people to are greyed out, and members at or above your
  rank get no rank controls.
• Performance for big guilds
  • Activity results are kept per period and only go stale when the hours,
    the membership or someone's main change (not on every roster read);
    each hour's 'who was on' list is parsed once.
  • Roster reads are gathered into one every 3 seconds (1 when asked for);
    joins, leaves and note or rank changes bump versions other parts check.
  • Alt detection remembers each note's candidate names; alt links bump a
    version only when someone's main actually changes.
  • Keep in sync team imports only run when notes, ranks, members, alt
    links or teams changed.
  • The guild key behind every GuildDB() call is cached until the guild
    changes (at most 30 seconds).
  • Attendance answers survive roster reads that only change who's online.
  • Bulk Actions works out its list and every rule's count in one pass,
    with team spots and alt groups computed once; repaints are gathered.
  • GRM import trims History in one pass instead of one entry at a time.
  • A Guild Finder join settles its History credit (no inviter) instead of
    re-asking the event log every minute for two weeks; invites still win.
  • Roster sorting computes each row's value once.
• Bulk Actions: safer confirm, hotkey and editing
  • The Start popup carries the action and head count it confirmed; if
    either changed before accepting, nothing starts. Switching actions or
    leaving the page closes it.
  • The hotkey needs Ctrl, Shift or Alt and can't be Enter, Tab, Space or
    Backspace; capturing ends on leaving the page or entering combat.
  • Rule edit boxes write to the rule they were editing when they got
    focus, and Delete rule commits pending edits first.
  • Opening a profile puts away the page's secure buttons (disarming an
    armed run) and commits a half-typed private note.
  • A UI scale or resolution change re-places position-anchored buttons.
• Sync: catch-up that can't skip, can't be spammed, can't be undone
  • Separate 'newest record held' (decides offers) from 'caught up to'
    (what a copy asks from). Our own edits and overheard records no longer
    make a copy look caught up, and E sets how far a catch-up brought us.
  • One offer per player, so a second login doesn't cancel the first
    player's catch-up; a burst of hellos schedules one reply hello.
  • Officers only answer a catch-up request they offered, at most once
    every 3 minutes per player; empty or unknown names never match 'me'.
  • Keep in sync note imports wait until this login's catch-up is in, so
    a removal made while away isn't undone.
  • Records are retried on any send failure except a malformed message,
    and every instance type holds the queue; a quick reload keeps last
    session's unsent records.
  • 'gm' counts as an officer word only on its own (not in Sigma).
  • Activity hours from other copies are kept within possible values.
• Raid nights: no duplicates, no wrong merges, deletes stick
  • Two records are the same night only for the same raid at the same
    difficulty, overlapping in time or starting within 30 minutes (one
    rule, PGM:SameRaidNight, for local saves and sync). A Normal and a
    Heroic night, or two teams back to back, no longer merge.
  • A session that closes after another officer's record of the night
    arrived merges into it instead of saving a second copy.
  • Moving to another raid or difficulty closes the night and opens a
    new one.
  • Deleting a night deletes it under every id it's known by, says which
    raid and when so copies that matched it by time delete it too, and is
    stamped past the night's own stamp.
  • Received nights respect the 300-night cap.
• Move the lint and sync simulator into tools/
  They lived outside the repo. tools/ is kept out of the release zip;
  run npm install there once, then npm run lint and npm test.
• CurseForge description: History credits, guild window buttons