[BGBot] Gettin' some lovin'. Post your issues here so I can get them fixed.

See it is WSG weekend I started up BGBot to get some honor to buy gear so when I hit 85. I play Horde. Some times right after I res at the graveyard it runs into the mountain just south and sits there. Other times it will jump down and turn right in mid air like it missed a hot spot, but stop when it hits ground.

I wish there was a way to run mid field then right to flag room to flag and try to pick it up.

 

Update it so user can update it.

 

I'm sure these are obvious and some of them have been mentioned before but I'll go through some ideas anyways...

As far as the chat stuff goes it doesn't have to go where they tell you to go right away. It weights each destination based on a number of factors - the chat hints could be one of those factors.

The bot if it's the only one at a base under our team's control in AB,etc -shouldn't leave the flag alone.

Hot spots if possible should be semi random (ie: stables flag within 5 steps in any direction) or maybe just choose one out of 10 hotspots (or more for that matter). It would be nice if the bot came to the conclusion that the current node was the best to move after a random amount of time (ex: rand()*60 seconds go to the other side of the flag)

Slightly different weighting depending on whether its a healer or a dps. If a healer is played for an example more often go to where there are more people on your team.

Customizable weighting so that each person's bot may make a slightly different decision. ex: rate 1-10 on the following behaviours: defend, kamikaze, etc

Is it possible to get a new version off of svn or something?

 

shit is broken and i want the updated version right now pls!

 

This may sound crazy and un-implementable. But it sounds good.

A unique ID linked to a set of attributes which is generated based on class, level etc etc. The attributes include things like Navigation (Scale of the distance the bot will cover over the BG, such as taking the long route to a main area), Pack (Tendency to follow the pack or go alone). Just a few examples. This was just a thought I got from a popular bot maker on another game which uses the same type of thing. This would add a nice amount of randomness, so it looks a bit less botlike.

 

:cries:

can we get the latest puh-puh-pleasssse!

Given that it is WSG CtA I'm having to use Pirox to run it so I don't hump the wall in the GY. So sad.

 

Hey bro apoc, love what your doin' can't wait
is it possible to get an update on an ETA or how far along you are on this new verson cant wait !!!!!

Stoked!

 

I turn the bot on and it ques up for WSG and Arathi Basin, but it never accepts the teleport to get into the BG. it was working perfectly before on alot of my lvl 80s and 85s who i farmed honor on for gear.

 

could you add option to stop pvp when 4000 hornor or buy selection gear when cap plz ?

 

http://www.thebuddyforum.com/honorb...in-mr-honorcap-plugin-buys-honorgear-you.html is the plugin you are looking for decerte.

 

In WSG at least for Horde he dies and just tries to run up the hillside near the BG. Very botlike behavior and I have been booted because of this from the BG.

 

This. It's when it sets your own base as "prio" and tries to run to it via GY, resulting in you standing there doing nothing. Also, halfway down the hill from Allience GY, it just stops sometimes and spams "cannot find route", which results in the same, unless someone attacks you. Really looking forward to new targeting system/whole new BG bot. It's been horrible to farm honor on 3 chars, while on the other hand HB does gathering/grinding mobs just perfect, love it. Thanks!

 

Alterac Valley, alliance side. Bot runs trough hordes @ the Stoneheart Outpost. Everyone else on the alliance side runs from Right side ( West side of the tower ), but the bot decides its better idea to not follow the group, and run from Left Side (East side of the tower) trough the horde, trough the lake. This gets the bot killed 90% of the time.

I know it makes sense when you are dead and respawn to the graveyard, but at the start the bot could run trough pattern till some point.

Also, Stonehearth Graveyard, Alliance side. Bot runs towards Stonehearth Bunker, but then starts humping a wall for a moment before honorbuddy corrects it. Its the first building after the graveyard, this issue has been for months unfixed.

I wish there was custom routes / hotspots like Kick has made for "Pvp Bot". Anyone know any BGBot custom routes that ppl could use, unless they fix the stock ones? And is there any info on, how regularly this bot is even updated?

 

When it comes to targeting and preferring to take down the enemy healers, keep also in mind that you should defend your own healers if possible.
So if you detect them being in heal spec and quite heavily attacked try to focus on those people that go after your healer.

Not sure how much info you can read on enemy players, but if you are able too, try to focus on people in pve gear without much reslience.

 

I'm not sure if this is the kind of thing you are looking for, but when my friend and i play he has issues where his bot (he's a rogue) just does not stealth fast enough. if the rogues could be set to stealth on resurrect it could fix it. And in WSG i was still rezzing and running back into the wall in the graveyard.

 

Apoc any chance this is available for testing yet? Love to help with it if possible.

 

Apologies in advance if this is something which could be fixed in other places.

Im noticing several "tried to move to x for 45 seconds, blacklisting" messages, if that could be lowered or changed somehow would be great.
Just looks bottish if a toon just stands there, thats the behaviour i see most of the time with that message.
Ty.

 

It seems as if Bgbot got pushed aside for other priorities /cry.

 

Quick question for the experienced? Maybe I'm just newb to BGBot.. How do you get your toon to repair when needed after 8000 runs in AV or WSG or whatever? Specific plug in or something? Thanks in advance.

 

Should auto repair when the Durability level hits a low enough level to trigger it.