WhoDoesWhat

lightweight tag 30039c42338061f485ec16d79ab03498d7ad7a4d 2.0.3
Author:    jackfranzen <4414665+WallHackJack@users.noreply.github.com>
Date:    Thu Sep 17 20:45:55 2026 -0400

commit 30039c42338061f485ec16d79ab03498d7ad7a4d
Author: jackfranzen <4414665+WallHackJack@users.noreply.github.com>
Date:   Thu Sep 17 20:45:55 2026 -0400

    Cut 2.0.3: blessing training levels, tooltip ids, Forever welcome

    Paladins are gated on what they have trained: ComputePaladinBuffPlan's
    CanCast now asks PaladinKnowsBuff, which compares the paladin's roster
    level against the blessing's training level. Inferred rather than synced,
    so it holds for a paladin running no addon. Levels are memoised (the plan
    asks per paladin per blessing, and UnitForPlayer walks the roster) and
    cleared on roster changes and dings; the level joins the plan cache key,
    so a ding re-plans the same way a respec does. Forever's numbers only --
    Classic and TBC gate on talents alone until theirs are filled in.

    Unknown answers "knows it": no level data, no unit for that name, or a
    level the client hides. Refusing a blessing on a guess is worse than
    planning one that fizzles.

    Also: role change announcements default off on every client; a tri-state
    tooltipIds setting (unset = the client decides, on for Forever) putting
    spell, aura and item ids on tooltips; Peace Tea and Forever's Well Fed;
    and a once-per-character Forever welcome notice.

    Fixes: the Paladin Bar's button constructor returned early where snippets
    are unavailable, so it handed back no button; and both bars' range checks
    tested values Forever marks secret out of combat, which is an error, not a
    nil -- they now ask issecretvalue() about the value in hand rather than
    trusting the general switches.

    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>