mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 08:00:42 +00:00
`#showtooltip 1539` resolved its value through the engine's name resolver, which maps a name -- or an ID through its name -- to a spellbook SLOT. An unlearned spell has no slot, so the directive matched nothing and the button greyed with no icon and no tooltip. That constraint is right for `/cast`, which needs the slot, but an icon and a tooltip need only the spell record. A value the directive names itself is the author saying what to display, so it now falls back to `Spell.dbc` when the spellbook has no slot for it. The button still greys, because the spell still cannot be cast, which is the honest result: the macro shows what it is about and says you cannot use it. `spell:N` is accepted as the display counterpart of `item:N`, and skips the spellbook unconditionally -- nobody writes that form except to name a spell for display. A bare number skips it only for an explicitly named value; one lifted off a `/cast` line resolves exactly as far as that cast would, which keeps the bare form honest about what the macro will actually do. A spell NAME cannot be rescued either way, since 1.12 has no name-keyed spell index. The name path still runs first, so a learned spell keeps its real spellbook resolution including the pet-book flag; the record fallback only sees what the spellbook rejected, and forces `isPet = 0` there, a pet slot being exactly what just failed to resolve. The 1..19 inventory-slot rule stays ahead of it, so `#show 13` is still slot 13 rather than spell 13. A published value counts as explicit for the same reason a directive's does.