Hi
I am the author of a small addon called Aardavrk.
Recently there was a change to have DeleteCursorItem() only fire once on each item.
This has drastically changed the delete item function I had.
A player can physically add items to a delete item list; the delete function then loops through the player bags and deletes each item found on the player’s own curated list.
Before this change, a player would click on the destroy button to run the destroy function as it loops through the player’s bag.
Is this an intended change? and if so could I suggest that this change be rolled back.
1 Like
I’m positive this change was intended. Blizzard added three sets of protections recently:
- 9.0.2 - requires a hardware event
- 9.1.5 - no longer permitted in /run scripts such as macros, WAs, etc.
- 9.1.5 - separate hardware events required for each call
A lot of other API got protected in 9.1.5 as well (mostly limiting /run scripts).
Thanks for your answer.
Is there a place where I can see a list of these types of changes?
There’s a few options. I recommend starting with Wowpedia’s Patch 9.1.5/API changes and reading the summary section.
From Wowpedia there are also links to the community patch notes on GitHub which presents things in a different format that you might prefer.
Also, there is a “patch changes” section right on the DeleteCursorItem() page.
1 Like
