Remaining time display

[Sabo]

Hello,

I was wondering if the countdowns are working properly (retail-like I guess).

Since it rounds the remaining time display down, when it comes to seconds, the number shown is always 1 lower than the actual remaining time. So when for example it shows 10s left, it's actually 11. And when it says 0 it's actually 1 more second.
Wouldn't it be more logical if the buff disappeared 1s after showing 1s left, therefore never even showing the 0 (unless there's lag I guess)? Same for cool-down timers on the quick bar; you need to wait 1 more second after it shows 0.

I'll stress again: It's not an issue with duration, just the display.

[Zoey76]

I think it's client side, I don't remember any changeset where we added support for that.

[jurchiks]

Not sure but wasn't there a server packet required for the buffs to actually be removed? Afaik unless the server says so, the icon will remain there even the timer is 0 so that could possibly be a server-side timer issue.

[Stake]

If we rounded it up, then it would count from 1 minute 0 second, that the client can't display, instead of 59 seconds. I think it's better, since we round down values for an incrementing timer too.

[Zoey76]

Not sure but wasn't there a server packet required for the buffs to actually be removed? Afaik unless the server says so, the icon will remain there even the timer is 0 so that could possibly be a server-side timer issue.

For shorcuts is client side, maybe is possible to do a better synch but that would require to rewrite part of the code that sends the reuse time.