Bounty Hunter Archive
Thread: Cant KD recover while KD'ed
TheFruitThatAteAntarctica
Wed Sep 07, 2005 10:36 pm
#15
This bug is a myth. It's not actually a bug (as far as I can tell), just a poor case of error handling. This occurs when something is queued and subsequently blocked by a knockdown and immediate spamming of KD Recover. The combat queue gets backed up and reports that it cannot perform KD Recover, when it actually means "You cannot (Bacta Shot/Ranged Shot/etc) while knocked down." Hitting escape should clear the queue and let you KD Recover (at least, it works for me when I can hit it fast enough). In all likelihood, this is working as intended (as the error is actually generated by a different command). For all practical purposes, it does seem to cause an even larger congestion in the combat queue as players tend to spam KD Recovery, and this needs to be addressed somehow. Perhaps an auto-purge of the combat queue when KDed or just a fix in the way errors are handled to alleviate the frustration. Hope this makes sense.
-elpollo
-elpollo
GaladhrimOlorin
Wed Sep 07, 2005 10:52 pm
#16
AD_Maj wrote:
Spam KD recovery.
thats what causes it in the first place. spamming commands. just have some patience and plan out your attacks and you should never have this problem. or just make the macro if you cant keep your finger still for a second during the cool down.
BonoU2
Thu Sep 08, 2005 12:59 am
#17
I have had enought of this bug. A few days ago I was hunting Jedi and in each and ever battle (8) this bug rooted its ugly head and cost me dearly. I thought, well , maybe I was just having a bad day so I decided to do a little more Jedi hunting the next day and proceeded to grab missions off the terms. My first 2 were on kash, dropped .... the 3rd and 4th were on endor ... also dropped.
My next 4 missions were spread out amoung the other planets and I was 1-3 in those incounters, the only victory coming from a afk jedi at the imp outpost on dant. The other 3 all ended with the "you cant knockdown recover while knocked down" and a 1 way trip to the cloners.
Well I have decided that it is not worth the time, money and effort required to hunt Jedi if there is a bug that can turn the tide of a battle againest you. With that in mind I am now grinding out to Master Swordman - TKM and Doc 4-x-x-x
Tanks thisis a game breaking bug and it needs to be addressed before more of us get fed up with it and move on to some other profession. I am also very sure that this bug does not affect Jedi - since it seems to be triggered by using any type of healing ability other then Force Heal ... but I could be wrong on this assumpion.
-Lexica-
Thu Sep 08, 2005 1:01 pm
#19
BonoU2 wrote:
I have had enought of this bug. A few days ago I was hunting Jedi and in each and ever battle (8) this bug rooted its ugly head and cost me dearly. I thought, well , maybe I was just having a bad day so I decided to do a little more Jedi hunting the next day and proceeded to grab missions off the terms. My first 2 were on kash, dropped .... the 3rd and 4th were on endor ... also dropped.
My next 4 missions were spread out amoung the other planets and I was 1-3 in those incounters, the only victory coming from a afk jedi at the imp outpost on dant. The other 3 all ended with the "you cant knockdown recover while knocked down" and a 1 way trip to the cloners.
Well I have decided that it is not worth the time, money and effort required to hunt Jedi if there is a bug that can turn the tide of a battle againest you. With that in mind I am now grinding out to Master Swordman - TKM and Doc 4-x-x-x
Tanks thisis a game breaking bug and it needs to be addressed before more of us get fed up with it and move on to some other profession. I am also very sure that this bug does not affect Jedi - since it seems to be triggered by using any type of healing ability other then Force Heal ... but I could be wrong on this assumpion.
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won. 
So its not just BH's that get it. Fact is I have seen mobs that have not gotten up after a KD in the past few weeks. Nice little bugs....
So its not just BH's that get it. Fact is I have seen mobs that have not gotten up after a KD in the past few weeks. Nice little bugs....
KilferfUhn
Thu Sep 08, 2005 1:13 pm
#20
-Lexica- wrote:
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won.
Yep, good point. Kimo's, Aa'kuan, those little guys dressed up in white costumes saying "Halt" as i run by, they all get the KD bug aswell.
Finding bugs and why they're there is not my job, i'ts mindboggling for me to think of what coders and dev's go through to make things happen (and...not happen lol). I try to narrow it down the best i can, then something new is thrown into the mix. Basically for me, as a MBH/MCM/Pistols [FoTM] i get the bug with enhancer usage 99.99999% of the time. Others do not, and trust me i interrogate everyone everytime i see it happen, friends and strangers alike (if they'll talk lol). 
I'm not a "tester" and i don't want to know how to setup a controlled user test that you would/could all appreciate. I wish someone else would though, i'd be more than happy to assist. [Bloodfin]
KilferfUhn
Thu Sep 08, 2005 1:14 pm
#21
-Lexica- wrote:
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won.
-Lexica- were you running any "macros" for knockdown recover? A simple /dump; /knockdownRecover; perhaps? Anything?
-Lexica-
Thu Sep 08, 2005 1:36 pm
#22
Nope, did not use a macro for KD recvoer. Had saber hit set on auto. He opened with KD and I went down. Hit KD recovery and got the great mesasge "Can not Knockdown Revocery while Knocked Down". Got that about 6 or 7 times before I died.
KilferfUhn wrote:
-Lexica- wrote:
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won.
-Lexica- were you running any "macros" for knockdown recover? A simple /dump; /knockdownRecover; perhaps? Anything?
KilferfUhn
Thu Sep 08, 2005 1:43 pm
#23
-Lexica- wrote:
Nope, did not use a macro for KD recvoer. Had saber hit set on auto. He opened with KD and I went down. Hit KD recovery and got the great mesasge "Can not Knockdown Revocery while Knocked Down". Got that about 6 or 7 times before I died.
KilferfUhn wrote:
-Lexica- wrote:
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won.
-Lexica- were you running any "macros" for knockdown recover? A simple /dump; /knockdownRecover; perhaps? Anything?
See here is where hitting escape twice to clear your target (making your auto-hit icon cease auto-hitting as there is no target) or simply by clicking on another attack in your toolbar (You cannot torso shot/leg hit (whatever, any regular attack)while knocked down) which will also stop the auto-hit from auto-hitting.
This is the exception, and i do believe you could have gotten up had you tried either of the mentioned methods to "uncue" what was preventing you from getting up/using kd recover.
My, and many others' problem lies where neither of these methods (or others..) will uncue the currently selected icon.When i say "currently selected icon", i'm mainly referring to my enhancers as thats all i can reproduce 100% of the time. They can either save my life, or kill me dead.
Message Edited by KilferfUhn on 08-21-2005 01:47 PM
-Lexica-
Thu Sep 08, 2005 2:59 pm
#24
KilferfUhn wrote:
-Lexica- wrote:
Nope, did not use a macro for KD recvoer. Had saber hit set on auto. He opened with KD and I went down. Hit KD recovery and got the great mesasge "Can not Knockdown Revocery while Knocked Down". Got that about 6 or 7 times before I died.
KilferfUhn wrote:
-Lexica- wrote:
This happend to my Jedi on the first BH that showed up for me. He asked me after why I just laid there and died. I hate this bug. Cost me 450k exp. Well not sure if I would have beat the BH or not. But I like to think that I would have won.
-Lexica- were you running any "macros" for knockdown recover? A simple /dump; /knockdownRecover; perhaps? Anything?
See here is where hitting escape twice to clear your target (making your auto-hit icon cease auto-hitting as there is no target) or simply by clicking on another attack in your toolbar (You cannot torso shot/leg hit (whatever, any regular attack)while knocked down) which will also stop the auto-hit from auto-hitting.
This is the exception, and i do believe you could have gotten up had you tried either of the mentioned methods to "uncue" what was preventing you from getting up/using kd recover.
My, and many others' problem lies where neither of these methods (or others..) will uncue the currently selected icon.When i say "currently selected icon", i'm mainly referring to my enhancers as thats all i can reproduce 100% of the time. They can either save my life, or kill me dead.
Message Edited by KilferfUhn on 08-21-2005 01:47 PM
I agree with about making the auto hit stop its cycle. After testing my skills with some other Jedi in my PA, I no longer keep a skill on auto attack. I found that with auto attack going it made healing on time a nightmare and KD recovery take alot longer. I have not had this happen again after I stoped the auto attack.
KilferfUhn
Thu Sep 08, 2005 3:04 pm
#25
Considering the fact that keeping my auto attack OFF at all times during combat was one of the very first things i learned when dealing with this bug, it saddens me to say you're still going to encounter KD bugs due to other mysterious factors.
