LurkMcGurk
BANNED
- Joined
- Jul 1, 2015
- RedCents
- 9,632¢
I decided to make a thread to point out a few of the very common issues I have found with KA, I would assume we all have them since I get them on every computer I own but I haven't seen anyone else complain about them, so I guess the chance of me being retarded is there.
Issue 1: Beneficial Group Buff + Extended Target window issue
KA refuses to use BENEFICIAL group buffs when it could possibly agro more mobs than what are current on the extended target window. This is true for group black wolf, group armor of the inquisitor and really any other beneficial group buff.
Issue 2: On Pullertank it spams self buffs

This is probably the most annoying one for me. I disable most of my tanks self buffs because KA doesn't seem to track the timer on them at all. It will literally stand up every 5 seconds while it is medding to refresh self buffs like Brells, Ardent Fury (on a paladin) and on an SK the two most common culprits are Vizat's and Shroud of the Doomscale.
It rebuffs these on my tanks between Every. Single. Pull. Despite them being 2hr + long self buffs. It slows down the tank A LOT when he is pulling having to constantly rebuff and in some cases remem spells after every mob he kills. Most of the time I have to disable my tank even buffing himself because of this and thus, gives me a MUCH crappier tank.
- I will not use another character as the puller because I do not like having a puller in a group, I feel it's a waste of a slot. That's my personal opinion, yours may be different, that's not the point here, the point is KA is doing something it shouldn't. I'm not trying to be rude, I just don't want people giving me their opinions on ways to fix the problem. I know every temporary fix I can do and the one I find most suitable is disabling my tank's buffs. I'd like a real fix though.
Issue 3: Tanks fighting out of the camp
When using a Pullertank if the tank is pulling a mob and another mob attacks him mid pull, sometimes the tank decides it would be a good idea to fight the mob where he is standing. This isn't ever a good idea. He should always return to camp before tanking/fighting a mob. Maybe my camp radius is too high or maybe this is my fault/issue but it has happened to me over the last 8months or so when I bot at least once a week on different tanks so I am less likey to assume my INI is to blame.
Issue 4: When the tank dies (or puller) and campfires back, the bot breaks.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
Is what the mq2 window gets spammed with. The only solution I can think of is when the tank campfires back, he restarts the macro
Issue 5: THIS IS A SUBJECTIVE ISSUE - but it deals with navigation pulling
First, can we get a writeup on it? I have experimented with it a lot and honestly, I dislike just about everything about navigation pulling and the addition of MQ2nav with KA and I assume for the creators to feel it was worth adding in, I must be doing something wrong.
Problem 1: The tank chooses his target BEFORE leaving the camp that is along the path of pulling. This is stupid because if he runs into another mob while pulling he stands out there along the path and fights it and dies. I couldn't use the adv path in Grelleth for this reason, I had a semi elaborate path I made to where the tank would run around a large portion of the zone but he would pick a mob 1700 yards away and yolo run to it only to die.
Problem 2: Some zones/paths even after meshing just don't work. Exalted B comes to mind, the area where Eunice spawns. I created a path for the Dealers Debt markers that works flawlessly and then I tried creating one for the Vases but the bot just won't follow it... I have tried creating/recreating it numerous times but.... doesn't wanna listen or follow the path. No idea why.
Problem 3: I tried creating a path in Chelsith but the tank would follow it through to the end and he would target a nearby mob on the other side of the wall. He couldn't pull it obviously. I turned it off/back on and... since he picks the target from the camp instead of while he is running along the path, he kept picking this target. I added it to /addignore <annoying mob> but... it didn't work. The path worked for about an hour or two each day before it would chain target this one mob and NEVER pull anything else. I had to resort to using regular KA with no adv path.
Problem 4: For normal users who make a small race do not want to mesh zones or don't know how the addition of ADV path almost completely ruins KA. The reason for this is any little hump in the terrain the bot can't pull over. Maybe it is just me who is bothered by this, but I would have been dissuaded from using KA originally if this is how the program was always designed. There are so many camps I used to have that I could pull two or three named from but I can't anymore because there's a small itsy bitsy little hump that the bot can't see over and it just turns around before reaching the mob since it isn't in LoS anymore. My DE SK doesn't have as many issues with it, but my Halfling and Gnome tanks are VERY handicapped because they can't see over jack shit.
I didn't make this thread to insult the bot, I personally love it. Please don't take anything of what i said as a personal attack against the quality of the bot as i personally love KA and don't think I could enjoy EQ without it again. I made this thread since I use the bot fairly regularly and across multiple groups/computers. I haven't seen any of these issues mentioned before and I figured either nobody has noticed them or I am retarded and am the only person with them.
If I am not retarded and they're legitimate issues, well, now you know what to fix =P
Issue 1: Beneficial Group Buff + Extended Target window issue
KA refuses to use BENEFICIAL group buffs when it could possibly agro more mobs than what are current on the extended target window. This is true for group black wolf, group armor of the inquisitor and really any other beneficial group buff.
Issue 2: On Pullertank it spams self buffs

This is probably the most annoying one for me. I disable most of my tanks self buffs because KA doesn't seem to track the timer on them at all. It will literally stand up every 5 seconds while it is medding to refresh self buffs like Brells, Ardent Fury (on a paladin) and on an SK the two most common culprits are Vizat's and Shroud of the Doomscale.
It rebuffs these on my tanks between Every. Single. Pull. Despite them being 2hr + long self buffs. It slows down the tank A LOT when he is pulling having to constantly rebuff and in some cases remem spells after every mob he kills. Most of the time I have to disable my tank even buffing himself because of this and thus, gives me a MUCH crappier tank.
- I will not use another character as the puller because I do not like having a puller in a group, I feel it's a waste of a slot. That's my personal opinion, yours may be different, that's not the point here, the point is KA is doing something it shouldn't. I'm not trying to be rude, I just don't want people giving me their opinions on ways to fix the problem. I know every temporary fix I can do and the one I find most suitable is disabling my tank's buffs. I'd like a real fix though.
Issue 3: Tanks fighting out of the camp
When using a Pullertank if the tank is pulling a mob and another mob attacks him mid pull, sometimes the tank decides it would be a good idea to fight the mob where he is standing. This isn't ever a good idea. He should always return to camp before tanking/fighting a mob. Maybe my camp radius is too high or maybe this is my fault/issue but it has happened to me over the last 8months or so when I bot at least once a week on different tanks so I am less likey to assume my INI is to blame.
Issue 4: When the tank dies (or puller) and campfires back, the bot breaks.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
I am in the same zone as my campfire.
Is what the mq2 window gets spammed with. The only solution I can think of is when the tank campfires back, he restarts the macro
Issue 5: THIS IS A SUBJECTIVE ISSUE - but it deals with navigation pulling
First, can we get a writeup on it? I have experimented with it a lot and honestly, I dislike just about everything about navigation pulling and the addition of MQ2nav with KA and I assume for the creators to feel it was worth adding in, I must be doing something wrong.
Problem 1: The tank chooses his target BEFORE leaving the camp that is along the path of pulling. This is stupid because if he runs into another mob while pulling he stands out there along the path and fights it and dies. I couldn't use the adv path in Grelleth for this reason, I had a semi elaborate path I made to where the tank would run around a large portion of the zone but he would pick a mob 1700 yards away and yolo run to it only to die.
Problem 2: Some zones/paths even after meshing just don't work. Exalted B comes to mind, the area where Eunice spawns. I created a path for the Dealers Debt markers that works flawlessly and then I tried creating one for the Vases but the bot just won't follow it... I have tried creating/recreating it numerous times but.... doesn't wanna listen or follow the path. No idea why.
Problem 3: I tried creating a path in Chelsith but the tank would follow it through to the end and he would target a nearby mob on the other side of the wall. He couldn't pull it obviously. I turned it off/back on and... since he picks the target from the camp instead of while he is running along the path, he kept picking this target. I added it to /addignore <annoying mob> but... it didn't work. The path worked for about an hour or two each day before it would chain target this one mob and NEVER pull anything else. I had to resort to using regular KA with no adv path.
Problem 4: For normal users who make a small race do not want to mesh zones or don't know how the addition of ADV path almost completely ruins KA. The reason for this is any little hump in the terrain the bot can't pull over. Maybe it is just me who is bothered by this, but I would have been dissuaded from using KA originally if this is how the program was always designed. There are so many camps I used to have that I could pull two or three named from but I can't anymore because there's a small itsy bitsy little hump that the bot can't see over and it just turns around before reaching the mob since it isn't in LoS anymore. My DE SK doesn't have as many issues with it, but my Halfling and Gnome tanks are VERY handicapped because they can't see over jack shit.
I didn't make this thread to insult the bot, I personally love it. Please don't take anything of what i said as a personal attack against the quality of the bot as i personally love KA and don't think I could enjoy EQ without it again. I made this thread since I use the bot fairly regularly and across multiple groups/computers. I haven't seen any of these issues mentioned before and I figured either nobody has noticed them or I am retarded and am the only person with them.
If I am not retarded and they're legitimate issues, well, now you know what to fix =P




