Mount Buff Info

lightweight tag 64b88c9c46b67bf938de0799c9ea5a88b1d3f4f1 v1.1.3
Author:    Pat George <pat.george@gmail.com>
Date:    Sat Aug 29 16:21:52 2026 -0400

commit 64b88c9c46b67bf938de0799c9ea5a88b1d3f4f1
Author: Pat George <pat.george@gmail.com>
Date:   Sat Aug 29 16:21:52 2026 -0400

    v1.1.3

    Ships the aura-restriction fix. Every dungeon run was throwing a tooltip
    error on each mouseover of a mounted player, so it's worth a release on
    its own.

commit 931ffc8314c66562ca30b936d7c3f8cc4b2c5f9b
Author: Pat George <pat.george@gmail.com>
Date:   Sat Aug 29 16:21:48 2026 -0400

    Stop scanning unit auras while they're restricted

    Hovering a mounted player in a dungeon raised "Auras cannot be accessed
    when secret while tainted by 'MountBuffInfo'" on every mouseover frame;
    one run produced 5342 of them. Instanced content makes a unit's auras
    secret, and GetAuraDataByIndex raises for a tainted caller rather than
    returning nil, so the issecretvalue check on the result never got the
    chance to run.

    The scan is now gated on a live restriction probe: C_Secrets.
    ShouldAurasBeSecret where the client has it, otherwise a pcall against
    the cheapest call there is. Only the restricted answer is cached, keyed
    on GetTime -- constructing the error is the expensive part, and a stale
    "clear" would walk straight back into the hard error, which is the whole
    failure being fixed. Combat lockdown short-circuits ahead of both, and
    the scan itself is wrapped in pcall so nothing slipping between probe
    and call reaches the user.

    Consequence: no mount line on unit tooltips inside dungeons and raids.
    The data isn't readable there, so that's the honest behaviour rather
    than a choice. EllesmereUI's equivalent line goes quiet in the same
    places for the same reason.

    The aura tooltip was passing data.id into GetMountFromSpell unguarded,
    which is the same error class waiting to happen. Both entry points now
    check the spell and the mount before use, which makes ElvUI's
    NotSecretValue call redundant -- ours holds whether or not ElvUI loaded.