Closed ConteAlmaviva closed 5 months ago
Tried the same with Burning Blade a moment ago, it came up as Diaga.
Recast timers are directly sourced from the games' timers in memory, so that sounds like a very much Horizon issue. I'd be interested to see if the recast addon shows the same.
I'll try and hop on tonight to see if Recast shows the same. Thanks!
Following up to see if this was ever verified to be a horizon issue or not, unable to reproduce on retail.
I am sorry this took so long to report back on, I kept spacing it when I've had time to play, but your suspicion was correct - Recast shows the same behavior. Using Shield Break when too far away is somehow resulting in a Paralyze II recast timer:
Attached is the log file from a packet capture I was running while capturing this screenshot. I'm guessing there's something in here where it's incorrectly supplying back the recast ID of Paralyze II (I believe that's recast ID 80/0x50).
Yea, definitely a Horizon issue then. The action packet they are sending is setting spell recast on something entirely unrelated.
Not sure if this is maybe a private server (Horizon) specific issue, but I jumped the gun hitting a WS macro (Fast Blade) when I was out of range a bit ago, and it triggered a recast timer for Banish V. Going to try with ~Flat Blade~ a different WS in a moment to see if I get the same or similar behavior.