hello,
Where can I get the API Reference list for WOW Classic ?
I’m trying to fix some addons and can’t register
UNIT_THREAT_LIST_UPDATE and UNIT_THREAT_SITUATION_UPDATE for example.
thanks in advance.
If the events have been taken out because they didn’t exists in vanilla then you will have to find some other way to identify what those events signified. There is no documentation that will tell you to replace this event with that event because there is no reason to have duplicate events for the exact same thing.
I should have mentioned that if the name had just been changed at some stage then that would likely be noted on it’s Wowpedia page…
https://wow.gamepedia.com/UNIT_THREAT_SITUATION_UPDATE
event names have been, for the majority, extremely stable since vanilla.
That said, you can find change listings here:
https://www.wowinterface.com/forums/showthread.php?p=332165#post332165
1 Like
It’s a bit tedious to do so, but you can also use the source repository at https://www.townlong-yak.com/framexml/live to hunt down changes in things.
I wouldn’t be supprised if the threat APIs were removed from classic. They weren’t added until 3.0.
Here’s a bit about how the omen threat meter addon worked prior to 3.0.
Omen2 used what we called the Threat-2.0 library. This library was responsible for monitoring the combat log, spellcasting, buffs, debuffs, stances, talents and gear modifiers for calculating each individuals threat. Threat was calculated based on what was known or approximated from observed behaviors. Many abilities such as knockbacks were just assumed (to be a 50% threat reduction) as they were mostly impossible to confirm.
The Threat-2.0 library also included addon communication to broadcast your threat to the rest of the raid as long as they were also using Threat-2.0. This data was then used to provide a raid wide display of threat information.
https://www.curseforge.com/wow/addons/omen-threat-meter
https://www.wowace.com/projects/threat-2-0
Uh what? I can imagine refinements and changes/adjustments happening to the threat API as recent as 3.0, but I can assure you, there was a threat API in game by the time that Black Temple came out, which wasn’t very far into TBC’s run.
I’m honestly somewhat surprised they didn’t keep the threat API in the game, as the biggest reason for them baking it into the client was that widespread use of Omen and addons like it, and all the in-game communications that went with it, were directly attributed to as causing server instability.
Granted, with the more advanced combat log that now exists(assuming they didn’t also pare that back), the need for much in terms of near-real-time communication between players should be greatly reduced(as it can parse the log instead), but still…