Recast Timer Bug?

Hello!

I have noticed the existence of this issue for some time, but since a couple of weeks has become more frequent.

Sometimes the recast timer begins advance respect from its base time. I mean, if the recast is 90 seconds, it starts at 1:17 instead of 1:30 (may be more/less variation), which is quite annoying. Sometimes appears as an active skill and ready for use when it's still necessary to wait some seconds, and in "critical" situations as healing myself when i'm the tank, those few seconds of uncertainty can put you in a hurry.

The issue is solved by simply closing the game and re-enter, but it's annoying to have to do it every time you change from one class to another (I've noticed that this bug happens quite often if you go from Disciples of the Land to the Disciples of the War classes)

I've been looking into topics of this forum to inform me about it, and it seems that is a problem that has presented some time. Do you know if it will take some measure of correction? Or is it something that will be fixed for 2.0?


Thanks for your attention

http://forum.square-enix.com/ffxiv/t...certain-points.

The same thread twice in one day... we are reaching a new record.


Need more goobbue threads though.

Yup, been going on for quite some time now. Spans many patches sadly with no fixes.

Now seems to be getting more and more frequent.

When is this gonna be fixed?

I agree, I would like to know progress on this.

and as to people bashing the op, how is one supposed to link recast timers not working with "Thundara not able to be used at certain points." without reading the thread. Not everyone is going to read every single thread to see if something is related unless its obvious.

Wondering why this still hasn't been fixed. It's been happening since as far back as 1.19 at least.

It's especially annoying now because you always get the bug when changing from a class to a job. So it's impossible to play as a job with the correct timers, unless you first switch to a job and then log out and log back in afterwards.

I noticed it back in 1.19 but have not had it occur since.

I have the same problem. It's been reported on the bugs forum a few times, and supposedly the information is passed onto the devs. All I've ever seen it get is a canned response from a community manager. But, hey, maybe you should post it there, anyway. The more complaints they get, the better.

Also, logging out does not always fix the problem for me. Sometimes it even just fixes itself while I'm logged in. I have no idea what specifically causes it or what fixes it. It seems very random.