+1 for visibility
Losing out on 1.5s of a 5s proc is a huge blow to this trinket.
+1 for visibility
Losing out on 1.5s of a 5s proc is a huge blow to this trinket.
Please respond Blizzard, thank you.
Blizzard please fix. This is a huge detriment to this trinket.
+1 this is a royal pain and needs to be fixed
+1 Please consider hotfixing this bug, it’s clearly not the intended functionality for this trinket or how it behaved in original TBC. This bug greatly reduces the benefit of the trinket and consequently means Skull of Gul’dan will be even more contested than it already is.
Bump bump
Also FYI here’s an accompanying post for this bug in the WoW Classic Bug Report forum: Ashtongue Talisman not working as intended. Not applying to subsequent casts
Bump still waiting on blizzard
Any thoughts Blizzard?
This is the Bug Reports forum, where there is no interaction.
You report bug, QA forwards bug to developers, and there’s no discussion or conversation.
You would no more chat with a form you’re filling out.
Please Fix.
It’d be nice to see this fixed soon since a lot more people will be hitting exalted with Ashtongue Deathsworn over the next few weeks.
Hoping for a fix Blizzard
Please fix!
Would love to hear a blue respond to this, seems like a simple enough programming error to fix!
Please fix.
Would love this trinket to be fixed so I don’t have to wait for all the warlocks to upgrade a trinket slot
Please Fix.
This is a pretty prevalent issue, would be nice to hear any sort of feedback on it!
Wow, pretty surprising no blues have posted yet, weeks after this bug was discovered by the community. Wonder if any real humans are actually looking at these threads.
TBCC seems to be on autopilot
here’s a bit more proof that it’s not applying until after the 2nd cast, even on instant casts:
https://i.imgur.com/NH9zdaF.png
https://i.imgur.com/MbiEh63.png
Trinket clearly procs on first cast (see blue buff), but it still gives a 1.425s GCD until after the 2nd cast
… then 1.30, 1.315, 1.311, 1.316
This means that it’s not simply a problem with spellqueueing, it’s actually not applying until after the next GCD begins