Bounty Hunter Archive
Thread: Truth about kd bug and burst run bug
Look now as much as I’d like to say that the kd bug is jedi or any profession exploiting its not.
Ok for those who haven’t experienced this is the kd bug (below). It’s a bug that makes a player who is knocked down can’t get up while giving us a message saying
“cannot knockdown recover while knocked down” WOW and what was this skill supposed to be used for again lmao
OK what causes it. Well firstly its lag. IF you are KD’d and you use a skill (specially with a high cooldown timer like paralyse or something) you get KD bugged. What happens is the server thinks you are going to complete the move you tried to do while KD’d (even though you can’t) and will run the cooldown timer as normal and wont let you do any other move until this timer is completed. So you get the kd message and have to wait until the time completes its cycle until you can get up.
Burst run bug is similar. When you use burst run and try to use it again but its in cooldown stage it does nothing. BUT try to mount a bike after and you can’t. What happens is the timer is still cooling down and you can’t mount the bike till either the burst run cooldown timer expires or you attempt to use another skill then it unlags your command queue.
The problem SOE are experiencing is simple poor programming, at skill at which they seem to have ample supply of. Skills get locked up in the queue and fail to initialise because of this and you get the problems listed above.
I say again though nobody can make you kd bug. Its just that your unlucky if you are kd’d at that exact moment you use a skill or just after (eg while you are lag running stuck in one direction till you fall down) that you get the bug. Finally a lot of kd bugs are stated when indeed a person isn’t bugged but doesn’t have enough action to kd recover. Remember guys against a sapper keep some action spare lol
Hope this helps
Orran Behime
Flurry server
PS any other experiences or evidence to contradict me please feel free. I’ve been wrong many times before lol
In the case of burst run cooling down,press esc to cancel the "qued up"command and you can do everything as normal.
Laney_1uk wrote:
Look now as much as I’d like to say that the kd bug is jedi or any profession exploiting its not.
Ok for those who haven’t experienced this is the kd bug (below). It’s a bug that makes a player who is knocked down can’t get up while giving us a message saying
“cannot knockdown recover while knocked down” WOW and what was this skill supposed to be used for again lmao
OK what causes it. Well firstly its lag. IF you are KD’d and you use a skill (specially with a high cooldown timer like paralyse or something) you get KD bugged. What happens is the server thinks you are going to complete the move you tried to do while KD’d (even though you can’t) and will run the cooldown timer as normal and wont let you do any other move until this timer is completed. So you get the kd message and have to wait until the time completes its cycle until you can get up.
Burst run bug is similar. When you use burst run and try to use it again but its in cooldown stage it does nothing. BUT try to mount a bike after and you can’t. What happens is the timer is still cooling down and you can’t mount the bike till either the burst run cooldown timer expires or you attempt to use another skill then it unlags your command queue.
The problem SOE are experiencing is simple poor programming, at skill at which they seem to have ample supply of. Skills get locked up in the queue and fail to initialise because of this and you get the problems listed above.
I say again though nobody can make you kd bug. Its just that your unlucky if you are kd’d at that exact moment you use a skill or just after (eg while you are lag running stuck in one direction till you fall down) that you get the bug. Finally a lot of kd bugs are stated when indeed a person isn’t bugged but doesn’t have enough action to kd recover. Remember guys against a sapper keep some action spare lol
Hope this helps
Orran Behime
Flurry server
PS any other experiences or evidence to contradict me please feel free. I’ve been wrong many times before lol
Doesn't this work for the KD bug as well? Not sure but I've read that this is a work around currently.
Zedh wrote:
In the case of burst run cooling down,press esc to cancel the "qued up"command and you can do everything as normal.
Message Edited by Zedh on 08-24-2005 12:43 PM
Narcoleptic_LTD wrote:
Doesn't this work for the KD bug as well? Not sure but I've read that this is a work around currently.
Zedh wrote:
In the case of burst run cooling down, press esc to cancel the "qued up" command and you can do everything as normal.
Yes, works for KD recovery also.
First off I have experianced this bug, and I've dealt with this bug enough times to realize that its not always the bug.
Sometimes its just the noob player has no clue what KD recovery acctualy does. KN Recovery takes about 25% of your action to get back up. So when you're lieing on your back and you cant use KD recovery, look at your action bar.
Now if you do still experiance the bug.
Use this macro.
________________________
/dump;
/knockdownrecovery;
________________________
that should do it for you.
/dump;
/knockdownrecovery;
________________________
Thanks for info.......... NO IT DOESN'T WORK. Tried it a million times. All you /dump for is when your running a macro yourself and you can't get up because its spamming the que. Seriously this doesn't work, or not that i have found
Laney_1uk wrote:/dump;
/knockdownrecovery;
________________________
Thanks for info.......... NO IT DOESN'T WORK. Tried it a million times. All you /dump for is when your running a macro yourself and you can't get up because its spamming the que. Seriously this doesn't work, or not that i have found
Escape -> KD recovery works, though - the problem is /dump doesnt clear your combat queue.
Eskie wrote:
Laney_1uk wrote:
/dump;
/knockdownrecovery;
________________________
Thanks for info.......... NO IT DOESN'T WORK. Tried it a million times. All you /dump for is when your running a macro yourself and you can't get up because its spamming the que. Seriously this doesn't work, or not that i have found
Escape -> KD recovery works, though - the problem is /dump doesnt clear your combat queue.
I don't think this will work, buta macro with:
/pause 1;
/knockdownrecovery;
and bind it to the esc key ![]()
Message Edited by Zedh on 08-24-2005 02:34 PM