-scry cooldown

[-XXX-]

Description
==========
The -scry cooldown is off

Steps to reproduce
----------------------------
-scry, wait 10 RL mins, -scry again

Expected result
-----------------------
Being able to scry again

Actual result
-------------------
Scrying blocked by the cooldown


Notes
---------
Couldn't scry again after 4 RPR ticks - the cooldown stated that I had to wait for more than 5 more mins.


Sidenote: the -cd foci function does not give away any information regarding -scry or its cooldown whatsoever. It's very hard to track the cooldown without actually spamming -scry

[Blood on my Lips]

I encountered the same problem the other day. I waited two - maybe three ticks after my last scry attempt to scry again and got a message that I couldn't scry, I had 8 minutes on my cool down timer.

As -XXX- said, we get no notice on the cool down timer unless we try to scry. It's rather annoying.

[-XXX-]

Bump.

Just scried, then summonned a familiar and unsummonned it. Once the familiar cooldown elapsed I tried scrying again and it said that I still had to wait for 5 more minutes = that means the -scry cooldown is much more than 10 minutes right now!

[BronxFury]

I've also been experiencing this on and off. From my experiences, it seems to be most frequent shortly after a server change.

[neverwinternightly]

It's all over the place in my experience. Sometimes you can -scry back to back, other times it's 30+ minutes between uses. I've not really figured out any rhyme or reason behind it, but it definitely wasn't an issue until the time change.

[Blood on my Lips]

It's been about 30 RL minutes since I scried someone. I just tried to scry and got a message that said, "You have recently used scry. You can use this command in 1 minute and 8 seconds".

Something is definitely wrong.

[Batrachophrenoboocosmomachia]

Bumping this to remember to take a look soon.

[BronxFury]

Thank you for all the hard work, Bats. <3

[Batrachophrenoboocosmomachia]

Initial review is odd, things all look like they ought to work as intended. Added some better cooldown feedback behavior to scry in the meantime ('you have 8 minutes left...' 'you have 6 minutes left...') to make this easier to troubleshoot. I'm particularly interested in confirming the consistency of its misbehavior and any interactions with server transitions.

[triaddraykin]

I'm having a fair bit of trouble with scry cooldowns at the moment. I did a scry at 15 past, then checked again at 22, and was informed I had 9 minutes and 23 seconds to go. I just spent 30 minutes on Cordor server, then when I came back to Surface, have 3 minutes and 17 seconds to go.

[Batrachophrenoboocosmomachia]

Excellent. Tracked down the issue. Will be bumping thread once implemented fix.

[Blood on my Lips]

Excellent. Tracked down the issue. Will be bumping thread once implemented fix.

Thank you!

[Batrachophrenoboocosmomachia]

Status of this? Timelock implementation was updated, probably.

[Batrachophrenoboocosmomachia]

Fixed, closing.