17 - "Ability is not ready yet" error when using Tom
Reproducible: Not always, but often. I was in Icecrown when I tested Tom extensively.
Steps to reproduce:
1. Switch to track minerals/track fish;
2. Select any trackable target. The error triggers in automatic or manual mode (using /tom).
What is the expected output? What do you see instead?
I got "Ability is not ready yet" red error. Differently from Ticket 14 [1], I don't get any GCD triggering, so the bug is less serious (but not less irritating).
Version:
Track-o-Matique 3.3
Logs:
Combat Log:
Sweng gains Sweng's Track Undead.
Sweng casts Track Undead
Sweng's Track Undead failed.(Not yet Recovered)
Track-o-Matique debug info:
Track-o-Matique: Activating Track Undead
Track-o-Matique: Insisting on tracking Undead
Track-o-Matique: Not insisting any longer
Ask me if you need more info.
[1] http://www.wowace.com/projects/track-o-matique/tickets/14-infinite-loop-of-tracking/
- 2 comments
- 2 comments
- #2
ceztko Sun, 12 Jul 2009 15:27:02Hello, my latency varies with server congestion: most of the time is in the range 70-190ms, now is 120-150ms; I changed recenlty the dsl carrier: previously the connection had often 200-400ms latency (!). Maybe a stupid question (I don't know anything about Lua and WoW api): doesn't the tracking change routine offer a callback in case of failure so the WoW engine just says you "hey, I've failed to change the tracking ability because of this. Do something or shut up"? It would be sad if the only way to accomplish this is polling a tracking change request without actually knowing if the previous request failed or not (and the error here is that the previous request wasn't failing).
- #1
Anyia3 Sun, 12 Jul 2009 03:01:31This is interesting. It appears that what is happening is this:
1. Target changes, ToM works out it needs to change tracking.
2. ToM issues the tracking change, and starts monitoring/insisting on the desired tracking type.
3. Before the realm server acknowledges the tracking change, ToM goes "hey, I wanted to track X, but I'm not tracking X - please track X!" and issues a new tracking change.
4. The game then complains that it has not yet finished the first tracking change, and gives you a lovely "Ability not ready yet" message (for you sake I hope you have error-speech disabled ;-) ).
One thing I'd like to know is, what is your typical lag/latency? Knowing that might help me tune things to avoid this.
Thank you for taking the time to report this issue!