Combat Medic Archive
Thread: Ok, combat medics got hit.... I can live with that. BUT fix the cannot KD recover while KD'd
Page 1 of 1
Anarchicgorilla
Wed Aug 10, 2005 8:57 am
#1
My combat logs on average go 8-10 seconds!!! saying cannot KD revovery while KD'd.
All the stuff about cm being tamed down I can live with, but to give any player that can knock you down 8-10 seconds of free whoop azz is out-of-control.
Do the devs have any plan on fixing this!!!
Is it just me or should we fix the bugs, before we work on changing the the templetes work.
mmaness
Wed Aug 10, 2005 10:28 am
#2
Last publish and the next 3 or so are concentrating on bug fixes rather than new content.... plus although KD recovery is a problem for CMs.... its also a problem for all profession and it may be wiser to place this in the bug thread and /bug it in game.... also Profession > Core System is a better place to post something like this since its not wrecking a single profession but all professions.
BadgerSmaker
Wed Aug 10, 2005 1:03 pm
#3
mmaness wrote:
BadgerSmaker wrote:
Last update I got on the fix for this bugs was that it is "pending".
Pending? Does that mean a fix is being worked on or does that mean they are thinking about fixing it?
I wondered that too.
Quandry
Wed Aug 10, 2005 1:24 pm
#4
It almost never happens to me sence i took it out of the "all stat cure macro".
Also i bound a key to /dump I find that even if im not running a macro (and thats not to good in pvp it you use more than 2 skills... Hit dump then kd recovery and im up. If you see the message hit dump again then recovery again.
Somewere its getting cought up in your combat que. Its like you get hit with the kd. The server ses your down. Then you dont see it for half a second or more lag etc... Sence you dont know your down you keep shooting. My best guess is wile your down the combat que is wating to do the shot you did last when you thought you were standing. It may say "cannot do x ability wile kd" but it still shows the yellow qued box for it...meaning its still trying to do it. Then the kd recovery comes in and sence its trying to do a shot you cant do there is no way its going to do the kd recovery....not sure why dump fixes it maby its because im taking the extra half second pause before i do the kd recover thats realy doing it.
wonder if there is still a /command to clear the combat Q
Also i bound a key to /dump I find that even if im not running a macro (and thats not to good in pvp it you use more than 2 skills... Hit dump then kd recovery and im up. If you see the message hit dump again then recovery again.
Somewere its getting cought up in your combat que. Its like you get hit with the kd. The server ses your down. Then you dont see it for half a second or more lag etc... Sence you dont know your down you keep shooting. My best guess is wile your down the combat que is wating to do the shot you did last when you thought you were standing. It may say "cannot do x ability wile kd" but it still shows the yellow qued box for it...meaning its still trying to do it. Then the kd recovery comes in and sence its trying to do a shot you cant do there is no way its going to do the kd recovery....not sure why dump fixes it maby its because im taking the extra half second pause before i do the kd recover thats realy doing it.
wonder if there is still a /command to clear the combat Q
Anarchicgorilla
Wed Aug 10, 2005 2:09 pm
#5
Quandry wrote:
It almost never happens to me sence i took it out of the "all stat cure macro".
Also i bound a key to /dump I find that even if im not running a macro (and thats not to good in pvp it you use more than 2 skills... Hit dump then kd recovery and im up. If you see the message hit dump again then recovery again.
Somewere its getting cought up in your combat que. Its like you get hit with the kd. The server ses your down. Then you dont see it for half a second or more lag etc... Sence you dont know your down you keep shooting. My best guess is wile your down the combat que is wating to do the shot you did last when you thought you were standing. It may say "cannot do x ability wile kd" but it still shows the yellow qued box for it...meaning its still trying to do it. Then the kd recovery comes in and sence its trying to do a shot you cant do there is no way its going to do the kd recovery....not sure why dump fixes it maby its because im taking the extra half second pause before i do the kd recover thats realy doing it.
wonder if there is still a /command to clear the combat Q
First off thanks to everyone for the advice.
I thinking of trying a macro like this
/dump
/dump
/knockdown recovery
I believe the queery only holds two combat commands (not sure so if wrong let me now) this way I can dump all my commands the recover.
Think this will work?
negilum
Wed Aug 10, 2005 2:43 pm
#6
mmaness wrote:
BadgerSmaker wrote:
Last update I got on the fix for this bugs was that it is "pending".
Pending? Does that mean a fix is being worked on or does that mean they are thinking about fixing it?
i'd guess it means they're trying to figure out what causes it so they can then figure out a way to fix it.
Brainplay
Wed Aug 10, 2005 5:46 pm
#7
Quick work around.
/kneel
/stand
Always works for me and if you have room on your toolbar you might want to add those two moves on there. If not then just kneel.
BadgerSmaker
Thu Aug 11, 2005 12:53 am
#8
Last update I got on the fix for this bugs was that it is "pending".
mmaness
Thu Aug 11, 2005 12:59 am
#9
BadgerSmaker wrote:
Last update I got on the fix for this bugs was that it is "pending".
Pending? Does that mean a fix is being worked on or does that mean they are thinking about fixing it?
Ternque01
Sat Aug 13, 2005 11:03 am
#11
Brainplay wrote:
Quick work around.
/kneel
/stand
Always works for me and if you have room on your toolbar you might want to add those two moves on there. If not then just kneel.
This did not work for me.
Spookibus
Sat Aug 13, 2005 2:12 pm
#12
Me either.
I hit one of my damage specials and THEN hit KD Recover. Hasn't failed yet.
YET.
Ternque01
Sat Aug 13, 2005 2:15 pm
#13
I am trying out the /sit; /sit; /knockdownrecover; one.... it has worked so far.
Page 1 of 1