Totems changed in patch

WoW Classic WoW Classic Bug Report
82

That’s a fix for a single addon, it doesn’t explain the change in the LUA API which broke every other addon with the same functionality.

83

I agree, but most players dont gaf about the API or how it works-- they just want a working totem timer :smiley:

84

I guess my point is we shouldn’t act like this is resolved and we really should be getting a response.

85

Why can’t we consider it resolved if there is a work around and it now works using a different approach.

86

Because the problem was the undocumented change in the API.

2 Likes
87

You mean, another undocumented change. Stealth changes are not only very Vanilla, but very very Blizzard. :smiley:

88

I don’t see how that makes a difference tbh.

89

Only that Blizz never “fixes” stuff changed by stealth.

90

So true. Everyone is eager for a blue post but let’s be real, the response will sound something like

Working as intended. /shoo

2 Likes
91

Dont know if it helps, but with some reddit research, I found one Addon for Totem Timers that work after the BG patch.

https:// www.curseforge. com/wow/addons/SamyTotemTimers

Happy gaming Shammys

92

It seems that the author of SamyTotemTimers has not released an update to fix the problem caused by the patch. So you may have gotten the fix by:

  1. You installed the latest version of NugRunning, which has LibTotemInfo embedded (or you installed any other addons with LibTotemInfo embedded).
  2. SamyTotemTimers is loaded after NugRunning, so it gets the totem API from NugRunning's embedded LibTotemInfo.
  3. SamyTotemTimers works fine.

At this point, other totem timer addons may work. Whether it works depends on the order in which the addon are loaded. Addons loaded after NugRunning basically work, and addons loaded before it may not work (because GetTotemInfo is not available before NugRunning loads, the previously loaded addons may fail).

The separate LibTotemInfo addon I released uses the directory name !LibTotemInfo, the leading! guarantees that it is always loaded before other addons.

93

Blizzard added ‘totemic recall’ in TBC because it was obvious that it was an issue for shamans to constantly be moving “pulling up” all totems each time the raid moved to avoid unwanted agro etc.

Okay so obviously it had been observed as something that needed improving in TBC BUT was NOT part of classic so therefore should not be in classic.

So as others have already said, I can totally understand why the totem destroy script was removed but toteminfo, we need totem timers, like what we supposed to do? Have a set of 3-4 stop watches on our desk and manually count each totem?

What about pulse timers, it’s nice to know when your next tremor totem will pulse without having to re-drop it every time so you can re-count to 5 to try a perfectly time breaking fears for party in a raid encounter.

Pulse timers were already sketchy, I think due to spell batching, even when pulse timers did work they were often off by as much as a few seconds.

They did fix ‘totem aura’ sparkles on party members which I was pleased to discover but a poor trade for totem timers.

94

reposting link to working totem timers

1 Like