What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Stuck in combat, is there a solution?

Status
Not open for further replies.
Darkbound

Darkbound

Member
Joined
Oct 7, 2011
Messages
313
Reaction score
3
I've tried several different GB2 farming profiles, and each one of them gets stuck in combat at some point, it's quite occasional thingy in MoP, a lot of mots to bug out the bot.... So I am pretty sure I am not the only one with this problem, is there a solution to this? I just hate it to wake up and see that the bot did nothing for the past 12 hours because he got stuck in combat at some location...
 
Currently there is nothing that HB can do about this.
It is a WoW bug.

Maybe if you could find a plugin to help with this, but I dont think there is one released.
 
Last edited:
Darkbound said:
I've tried several different GB2 farming profiles, and each one of them gets stuck in combat at some point, it's quite occasional thingy in MoP, a lot of mots to bug out the bot.... So I am pretty sure I am not the only one with this problem, is there a solution to this? I just hate it to wake up and see that the bot did nothing for the past 12 hours because he got stuck in combat at some location...
Click to expand...

Hi, Darkbound,

Getting thrown in combat is a function of the WoWclient--and Honorbuddy just responds to that. The problem is usually caused by NPCs fighting NPCs, and you get near enough to one that you get put on their "aggro list". As soon as the other NPC dies, the mob will be coming after you.

The only recourse you have to counter this in a GB2 profile, is to add blackspots in areas that have these kinds of conditions. There is absolutely nothing Gatherbuddy can do about it, as its the WoWclient itself automatically flagging you as being "in combat".

I am kindof surprised that the bot doesn't identify the mob that has thrown you in combat and go after it, however. Perhaps, the GB2 bot isn't quite as aggressive as the Questing bot in situations like these.

cheers,
chinajade
 
Yeah, I know what is causing this and the simplies way to get out of this "combat stuck" is just to pick a way and go straight forward till you lose the mob out of sight, I seriously doubt that this is something that is hard to be implemented, or simply to find the mob and kill it, but this has been an issue for ages, really I doubt that this is something that is that hard to gets some kind of solution..
 
Darkbound said:
Yeah, I know what is causing this and the simplies way to get out of this "combat stuck" is just to pick a way and go straight forward till you lose the mob out of sight, I seriously doubt that this is something that is hard to be implemented, or simply to find the mob and kill it, but this has been an issue for ages, really I doubt that this is something that is that hard to gets some kind of solution..
Click to expand...

Hi, Darkbound,

I refer you to the information you need to write a Plugin, if you believe its a simple problem to solve.

cheers & good luck with it!
chinajade
 
There's a huge difference between thinking that it's easy and knowing how to do it, if I was able to make a Plugin, I wouldn't ask if there's a solution, I would just create it. Still from what you said I get to the conclusion that the Quest bot doesn't have that problem, which means that it is already solved, it just needs to be implemented for GB2 aswell.

I'm pretty sure that the devs have solved waaaaaaaay more complicated problems, they just never got to try to fix this one. At least that's what I think.
 
Darkbound said:
There's a huge difference between thinking that it's easy and knowing how to do it, if I was able to make a Plugin, I wouldn't ask if there's a solution, I would just create it. Still from what you said I get to the conclusion that the Quest bot doesn't have that problem, which means that it is already solved, it just needs to be implemented for GB2 aswell.

I'm pretty sure that the devs have solved waaaaaaaay more complicated problems, they just never got to try to fix this one. At least that's what I think.
Click to expand...

Hi, Darkbound,

The questbot doesn't have the problem because it has access to quest behaviors. Many of these behaviors are tailor made for running one specific quest. The profile writers use these highly-specialized behaviors to solve the problem while executing specific quests for which the entry criteria is fully known. The same is not true for a generic gathering bot that operates autonomously anywhere in the world.

HBdev has provided a solution to the problem for the gathering bot--blackspot the problematic area. If you want more than that, then it will be up to Community to provide a 'more optimal' solution.

And no offense intended (honestly!), but if you don't have the skills to solve the problem, then you are not qualified to determine whether or not the task is 'simple'.

cheers,
chinajade
 
Last edited:
chinajade said:
Hi, Darkbound,
And no offense intended (honestly!), but if you don't have the skills to solve the problem, then you are not qualified to determine whether or not the task is 'simple'.
cheers,
chinajade
Click to expand...

I somehow knew that this was coming, I am a total newbie in programming, I don't know how to "write" it in programming language, but the logic(isnt what this programming is about?) behind how it should be done, is pretty simple. Anyway thanks
 
Last edited:
only thing that will stack u with a reloger + logmeout is kick questing profile that need manual input.
And technically that is not stucking :)

EDIT

Is there anyway the dev team could consider making the logmeout plugin a default HN plugin?

I think is just to good to pass.
 
we do have a built in "Inactivity Timer" it might be worth it to give it a try.
 
CodenameG said:
we do have a built in "Inactivity Timer" it might be worth it to give it a try.
Click to expand...

I don't got a plugin named like this at all. And HB is up to date.

Can you point me to the right direction please?

regards
 
Haven't tried it yet, but I don't see how "logging out" would solve this, since when it logs back in the mob will be at the same spot, the character will be at the same spot, he will just get back into a "combat stuck". Like I said, I'm having a hard time believing that this is something hard to get "fixed" (to find a solution for it), and like I also said, I am absolutely sure that, you guyts have found solutions for way more complex problems.. It's not about "there's nothing we can do about it" it's about "we haven't tried yet".
 
Darkbound said:
Haven't tried it yet, but I don't see how "logging out" would solve this, since when it logs back in the mob will be at the same spot, the character will be at the same spot, he will just get back into a "combat stuck". Like I said, I'm having a hard time believing that this is something hard to get "fixed" (to find a solution for it), and like I also said, I am absolutely sure that, you guyts have found solutions for way more complex problems.. It's not about "there's nothing we can do about it" it's about "we haven't tried yet".
Click to expand...

It has the option to do tasks before it logs out, like using your heartstone, an item etc.
Personaly i use a heartstone and its all good.
Try it out first, if doesnt suit you dont use it.
 
its hard to get fixed because the game still thinks your in combat. its always been a problem. but there are very few area's where there is idle combat happening, if you can, id suggest you find another location to grind. ive been here for more then 3 years, getting stuck in technical combat by NPC's fighting around you is a bitch because from a programming standpoint you ARE in combat, so yea, "theres nothing we can do about it."
 
So, it's that hard to find the mob that's keeping me in combat and go there and kill it(usually the mob is within 10yd range)? Or simply pick a path and walk straight forward until it gets out of combat? This is hard? It doesn't matter what the game thinks, it matters what the bot thinks. Again I find it hard to believe that it's hard to do something about it, like "if the bot is in combat longer than 2 minutes with no results, choose a """"safe"""" path and walk until out of combat" I don't think that choosing a "safe" path or something like that is hard to be implemented, since the bot already chooses "safe spots" when reviving..
 
Status
Not open for further replies.
Back
Top