How to make BG Bot stop continously running into enemy node over and over to death?

[Personallord]

Hey there, I have a quick question that really I'm hoping has a fix:

I'm not too good at programming and doing tweeks with HB - but back in the day I was pretty good at messing around with Glider.

With the BG bot, no matter what pvp profile I use, (using w00t's right now) my toon will run around killing people (all well, dandy, and inconspicuous), until Horde caps a node (mostly in AB,BoG, and IoC).
From then on, my toon will continuously rez and just run straight into that node over and over and over.

It's constant - I've never really seen it just run around like in the first 5 minutes of a game for an entire bg. Once it finds that node that's been capped and is guarded it will just keep running to it over and over.

Sometimes when I check in on it, I'll see enemy players at the node just casually killing me, knowing that I'm no really threat and will just return once more. It's super obvious, really.

Right now for BoG weekend, once Horde caps the LH I'll rez at alliance starting points and just run straight into death. It's such a short walk I'll have 18+ deaths a game.

Is there anyway I can fix this? Anyone else have the same problem?
Would really appreciate any help, thanks!

(moved it here for more appropriate forum)

 

[Kickazz006]

attach the log and tell me the timestamp when it starts this behavior

 

[Personallord]

It doesn't really happen at any particular time - like I said just whenever the opposing team caps a flag (usually in the first minute of a game).
It really applies to AB, BoG, and IoC.

Let's say a game starts in AB. My character will run around for a few minutes just running over random bases and defending itself when being attacked. However, if it runs into, say the mines, and the opposing team has it capped with 4 people on defense then, of course, it gets overwhelms and dies. The problem is that from here on out my character will then rez, and no matter were he rezes he will continuously keep running to the mines over and over and over for the entire game. At the end I'll have 5x more deaths than anyone else. It will literally rez, buff, run straight to the same place, die, and start over again for 15-20 times.

Say if we cap the mine back and now our team controls it, then it will just run around until it finds another flag that's capped by the opposing team and the cycle will start over again.

I just want my bot to run around everywhere, or maybe even avoid enemy capped flags in general. It's very very suspicious the way it's going right now.

I'm surprised no one else has replied or anything - I'd imagine most everyone was having this problem unless they edit it themselves (which is what I'm trying to figure out)


Thanks for reply!

 

[Kickazz006]

weird - i'll have one of the devs look into it

 

[Personallord]

Thanks I'd really appreciate it

 

[Tony]

Hb will move your char at the area that the action is or at the area that your toon "should" be

That's it's logic

 

[Personallord]

Hb will move your char at the area that the action is or at the area that your toon "should" be

That's it's logic

I understand that is what its logic would be - but that's not whats happening.

Using my previous example; my toon would rez at stables - there could be an epic 10v10 battle happening at Blacksmith, but my toon will run straight past it to go back to mines to the 3 people defending it. Over and over.

Like I said, I end up with 20-30 deaths per BG when the next highest is 5-7. There's NO way all the thousands of people using honorbuddy are experiencing/putting up with this if it were just how the bot operates. It runs great in any BG other than AB,BoG, and IoC - everything having to deal with a flag node.

Any people using w00ts or a custom made profile chime in? I'm desperate :O

 

[fukker]

I understand that is what its logic would be - but that's not whats happening.

Using my previous example; my toon would rez at stables - there could be an epic 10v10 battle happening at Blacksmith, but my toon will run straight past it to go back to mines to the 3 people defending it. Over and over.

Like I said, I end up with 20-30 deaths per BG when the next highest is 5-7. There's NO way all the thousands of people using honorbuddy are experiencing/putting up with this if it were just how the bot operates. It runs great in any BG other than AB,BoG, and IoC - everything having to deal with a flag node.

Any people using w00ts or a custom made profile chime in? I'm desperate :O

lol ye this happens to me when i use bgbot, thats why i use PVP with w00t's profile for Alterac Valley.

 

[vitalic]

the bgbot is terrible, for me in WSG it just runs to the enemy FC every time on its own and dies.

 

[DJKid]

The BG Bot now follows the action? I know it used to just use the hotspots programed into the profiles without looking at where the players were. I havent played too much with the new BG Bot, but that would be awesome.

Does this make pluggings like Squire and SimpleFollow obsolete?

Also if this is the case, Is Personallord running the latest BG Bot with these features?

 

[Altoids]

Once again this makes me wonder why my interface can 'see' my people not only congregating at let's say the Mage Tower in EoTS, but if I'm using Carbonite, it even shows where my team is fighting others (probably by watching their health) and then pops a different icon on my mini-map. If my interface can 'see' these going on, then HB can 'see' it - and act accordingly.

So... if a node is capped by us and there is combat on it or very nearby... go there. If a node is capped by the other side, there is fighting by our team then go there BUT prioritize based on distance. Go to a closer combat area before one that's further away. If I can 'see' opposing toons on a road and attempt to avoid them using LazyRaider, there's no reason that BgBot can't do the same thing. WE KNOW that fighting on road is not good if you are trying to win - our bot should know the same...

Which brings up something that I think should be a menu option. You should get to choose your priority for your toon: 1) Attempt to win the bg... aka, do things that are good for the team - assist defending our nodes under attack, assist their nodes that our team is attacking, attack their flag, defend our flag carrier - things we know help win the Bg. 2) Max HKs - already have top tier gear and trying for your Bloodthirsty title? Then your toon should just look for the closest battle and head towards it. Sure, you're not going to be popular with your team since you are probably spending the majority of your time 'fighting in the mid' (WSG/EoTS reference) but you'll get max Hks or 3) Try to win until it becomes obvious that it's not gonig to happen and then switch to HK mode. Yea, this is more subjective, but if you're down 2-0 in flags, you're in a battle where the other team is more than 50% done and has 3x your point value as examples...

I know that the logic would start off pretty weak but if it was implemented at all - and then could be tweaked - this would literally be a game changer.

As it is now, my Ret / Holy Pally often changes a battle - As Ret he has hit a node with 3 opposing toons on it and taken all 3 out. He has also defended our nodes from 2 and sometimes 3 attackers. As Holy he has gone in to a battle where the other side has significantly higher numbers - and he's healed our side well enough that we took the field. My DK has the same effect with HB - but I always use LazyRaider (or CombatBot), not Bg Bot or PvP bot - they just don't work well enough for me.

Yes, I know that some have earned Season 25 gear on 75 toons in less than a week's time using Bg/PvP bot - but anyone who has actually watched the toons realizes that it's purely luck or the lazyness of others that kept them from being reported. Constantly running onto a opposing node that has none of your own team within 5000 yards is just plain stupid. Not following some actual logic based on actual events just makes us stick out as bots.

Sorry for the rant - didn't start off with that in mind, just wanted to point out... again... what HONORBuddy desperately needs to actualy earn HONOR as an unattended bot. I do pretty well by using LR and CB... but don't dare let it run by itself.