-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Two reasons:
- You don't have any quest items in your log. The button hides when there's nothing to fire. Pick up a quest with a usable item and it reappears.
-
The position drifted off-screen.
/wqk resetre-anchors it to the default location.
Run /wqk to print the currently-loaded item list. If the list is empty, that's reason 1.
It calls GetQuestLogSpecialItemInfo for every quest in your log, the same API Blizzard's auto-quest-item button uses. If Blizzard would surface an item, Wick's Quest Key picks it up. No list to maintain, no per-quest config.
Some quest items are not flagged as "special use" in their quest data, so the API doesn't return them. There's no addon-side fix; that's a Blizzard data issue. If you think it should be flagged, open an issue with the quest name and ID.
Right-click the button. Each right-click advances to the next item in the list without using the current one. The icon updates so you always see what's armed for your next press.
Currently the cycle action is right-click only. Adding a separate bind for it is a candidate feature; open an issue if you want it.
Yes. The button is a Blizzard secure action button, so it can fire in combat. Cycling between items also works in combat.
Position saves per character. If you have many alts and want a global default, you currently have to set it on each character. A shared-position toggle is a candidate feature.
TBC Classic Anniversary only (Interface 20505). Retail already has the ExtraActionButton built in.