Skip to content

v1.0.2

Choose a tag to compare

@github-actions github-actions released this 05 Aug 22:29
· 8 commits to main since this release

Rune Reminder Reforged

v1.0.2 (2026-08-05)

Full Changelog Previous Releases

  • Auto-confirm rune overwrite; bump to v1.0.2
    The remaining "click Yes to overwrite" step is a native
    StaticPopupDialogs["REPLACE_ENCHANT"] confirmation, whose Yes button
    just calls C_Item.ReplaceEnchant() (confirmed in
    Blizzard_StaticPopup_Game/GameDialogDefs.lua). The original RuneReminder
    addon called this too, via the deprecated bare global ReplaceEnchant
    (itself just an alias for C_Item.ReplaceEnchant, gated behind the
    loadDeprecationFallbacks CVar) -- ported the same CastRune ->
    UseInventoryItem -> ReplaceEnchant -> StaticPopup_Hide sequence using
    the namespaced form directly, so engraving a slot that already has a
    different rune now completes in one click with no popup at all.
    Since this fully bypasses the native "are you sure" with zero visual
    confirmation, CastRuneOnSlot now also prints a chat line ("Replaced X
    with Y on your ") so a misclick in the picker is still visible
    after the fact -- per user's choice when this tradeoff was discussed.
    Traced and documented the full flow matrix for both the equip-swap
    mismatch detector (PLAYER_EQUIPMENT_CHANGED, passive, chat-only, never
    shows a popup) and the engrave-via-picker flow (active, applies
    immediately for an empty slot, single auto-confirmed replace for an
    occupied one) to make sure nothing else needed similar treatment.
  • Auto-complete rune targeting; bump to v1.0.1
    CastRune only selects the rune and enters "targeting mode" -- Blizzard's
    own EngravingFrameSpell_OnClick does nothing more than that either. The
    actual application to a slot happens via UseInventoryItem(paperdollSlot)
    (confirmed against a community macro: "/click /use ", e.g.
    slot 5 for Chest, matching our paperdoll numbering), which is the
    "click on gear" step the user had to do manually after picking a rune
    from our flyout. Since the picker already knows exactly which slot was
    clicked, CastRuneOnSlot now calls both in sequence -- one click in the
    flyout now fully applies the rune. The native overwrite-confirmation
    popup still appears when relevant (untouched, still a safety check).
    Also made the "no rune / had X before" chat notification actionable:
    mentions clicking that slot on the widget to re-engrave the old rune,
    rather than adding a new prompt/auto-reapply UI (per user's choice --
    simplest option, no new UI surface).