/unstuck cool-down timer
issueid=1484 02-03-2012 07:41 AM
Xsyon Citizen
/unstuck cool-down timer
system message reporting incorrect cool-down time

I logged in this morning and used the /unstuck command a few times. The first time I was stuck on the terrain. I did not noticed the command worked the first time and I had type /unstuck three times in a row, receiving 2 system messages stating I had to wait 79 seconds and then 75 seconds. Much shorter than usual. I was very happy and I thought you had reduced the cool-down timer in yesterday's patch.

About 30 seconds later I was mobbed by a pack of critters (love the animal spawns btw, tyvm) and I put up a good fight, but it ended in a failed attempt to /unstuck on to a tall terraformed mound of dirt on my homestead. Instead I received the system message stating I needed to wait 90-some seconds. Erm... huh?

I died, respawned, rested to full health and took another go at the pack. Again had to retreat and tried the /unstuck command when I received a new system message stating I had to wait 194 seconds. Whoa... again this is after a death, respawn, rest to full health and a 30 - 45 seconds of melee combat.

Very weird..

To test this I logged out and back in and /unstuck worked. I typed it again receiving the system message I needed to wait 160 seconds. Typed it 20 seconds later and it gave me the system message of 29 seconds. LOL
I typed it once more about 30 seconds later and it work.

I'd appreciate it if you could take a look at this. Thanks.
This issue is closed. No more replies may be made.
Issue Details
Issue Number 1484
Project Bugs Reports
Category Unknown
Status Fixed / Resolved
Priority Unknown
Affected Version Unknown
Fixed Version (none)
Users able to reproduce bug 0
Users unable to reproduce bug 1
Assigned Users (none)
Tags (none)

02-03-2012 10:29 AM
Xsyon Citizen
Working as intended.
Combat resets the timer.

02-03-2012 02:21 PM
Xsyon Citizen
They why did it drop from 160 seconds down to 30 seconds, after a 20 second pause? See my last paragraph. I was not in combat during that test.

02-03-2012 02:51 PM
Xsyon Citizen
I'm not sure. Its not doing that for me, all the other cases were caused by combat or relogging.

All I can say is that maybe that you missed some time or there was a bug. Ive not hurt of this always comes from people saying that the timer goes up, but because they were in combat like you said.