Anyone having problems with the cooldowns not working right?

[kwestro]

... cannot be used now.

[Liminality]

... cannot be used now.

UI issue. Restart the game is the only way to fix it (I know of). Displays that an ability is available before it actually is.

[kwestro]

UI issue. Restart the game is the only way to fix it (I know of). Displays that an ability is available before it actually is.

.
.
thanks, It's been happening to me a lot since patch 1.19a. Battling seems unreliable when the cooldown resets before the timer ends. I'll try relogging, though.

[Arximiro]

It's been a bug since like Beta and they still haven't addressed it. :/

[Misteyes]

It seems to be an issue with the client actually assigning the wrong number to it, for example, Stoneskin has a 30 second recast, but after casting it, it says "22 seconds" and not 30.

[Dirzech]

I've been having this issue forever. I wonder when it's getting fixed. ;/

[RethDaron]

I get it time to time too. Have they said anything about it or sweeping it under the rug?

[Jin_]

PS2 limitations.... i mean server rebuild for 2.0

[Xenor]

I've noticed more people saying they have the problem recently, which is good because then it's more likely to be fixed.

I've a theory that R0ing causes it.

Earlier I was doing the Ifrit runs, porting to Grid to turn the quest in etc. and I R0ed in Gridania. This took me to the character select screen. So I logged back in, returned to Broken Water and found my timers were about 8 seconds off. So either zoning into BW caused it or the R0ing. I'm going for the latter since I can often port to Gridania and return to BW all night and not have timers go off.

[AndrewN]

I get it.

It happened once or twice before 1.19, but I get it about 50% of the time since 1.19. Its quite annoying.