Users Requests (Bot additions / fixes / etc)

Adding more to this thread... hoping that HB staff are watching it for both easy ideas as well as more in depth ones.

I believe this is one of the 'easy ones'... When farming, I think it looks very suspicious that my toon actually lands on the mine about 8/10 times to mine it. I don't know about you, but when I mine by hand, I come in on a slope and end up next to it at least 8/10 times... I very rarely actually land on the mine... I would think it would be easy to have the bot land right next to the mine vs right on top of it... just offset the coords a little bit.

This is just one of the little things that would help to make our bots look more human-like... Please consider making it happen while you work on harder to implement items.

Thanks

 

I would appreciate a fix for druid flightform trying to fly into water and not being able to.. He simply does not dismount to be able to get into water.

Thanks.

 

Got another one... Why is the Mixed Mode so limited in options? I don't understand why you would include LazyRaider and Combat Bot in the first option but only put Automated options (IB, BG Bot and PVP Bot) for the secondary. I would think that both LazyRaider and Combat Bot would be listed as secondary options as well... so that we could use GB2 or questing for the first option and then when the BG or Instance queue comes up, join and let us use Combat Bot or LR to run what we've selected... and then return back to GB2 or Questing... or whatever we had selected...

Thanks for looking into this

 

Things that I would like to be improved:

1) Combat navigation & logic.
While in navigation mode, the bot uses mesh system and it works almost perfectly. But when engaged in combat by a ranged NPC the bot completely looses all of it's intelligence, trying to approach the target in a crow line, resulting in stucks.
For some reasons bot doesn't use meshes in combat, doesn't blacklist mobs if it cannot approach them. While using GB in Cataclysm locations it won't be that critical, cos you character will get killed eventually. But if you're running AB or you're gathering low-lvl resources, an aggro from a ranged mob behind the obstacle will result in stuck that can be resolved only manually.
2) More human-like behavior while flying\gathering.
Things that currently doesn't look human-like:
- U turns. Human cannot make a U-turn in a fraction of a second. HB\GB can. Changing direction should be much smoother.
- Dismounting in air. I imagine that was done to ensure there are fewer stuck issues, but I've never seen players dismounting in air.
- Landing precisely ontop of the deposit 4 out of 5 times.
- Noticable pause before mining\herbing cast.
- Noticable pause after mount cast & liftoff.
The list with the exception of a first point is quite specific to HB\GB, allowing to visually identify & distinguish HB\GB botter in just a few seconds.

 

For BG logic I'll chime in on AV. My main suggestion would have the bot do what a normal player does. Alliance example: Run to Galv, attack Galv, Defend Tower Point or Iceblood Tower, Run south to Frostwolf Keep. Something like this rather than running around a little haphazardly. Even something like Squire I've found often chooses a player to follow who is either alone or going to cap mines for example, ends up being buddy buddy with somebody at much too close quarters.

 

Please improve the unstuck logic! Just got a few bans today because bot got stuck in a public place (it randomly gets stuck every few runs), bot went under mailbox and couldn't mount for an hour.

Remove "stop and go" thing when using GB2, yeah i know that you need at least 20 fps o make it run without those little annoying stops while farming, but it would be very nice if you could smooth GB2 movement using lower FPS, that would dramatically increase the number of bots that could be run on one computer. And sometimes this problem appears even if wow window got 20 fps limitation.

 

I would like new BG profiles ( AV mostly ). It happened that i was doing AV with the Bot mode on, and it followed the path of 3 other buddy's that were botting. Something that includes like random paths at the start, and less tower defending. ( with random paths at the start i mean: before and when the gates open, the bot walks to a different location every new BG and runs to mid and then follows a normal path or something like that )

One that runs to galvangar/balinda, helps kill the boss, then goes stonehearth tower and then goes to end boss.

Also the flying looks botty sometimes, if i would turn more smooth in the air that would be a lot better.

Kind regards,

Phoenix

 

I have a couple of suggestions that would improve BG BOT a lot, and i think they are not that hard to implement. I am a developer myself, i code in C and JAVA, and i think the conditions i want to evaluate are quite simple...
1) Multiple path system: BG BOT should choose randomly between several "path" profiles. So that it won't take the exact same route all the time. The hotspots could be the same, but the way to get there should not.
2) Smart evaluations: The bot shouldn't just run between hotpots killing enemies, there are certain conditions it should evaluate in order to decide its next movement. Here are a couple of samples:
a) IF a tower has been captured AND there are team-mates trying to re-cap it, the bot should go there.
b) IF a tower is about to be captured AND there are team-mates, the bot should go there and help DEFEND
c) IF most of the players are fighting a boss, the bot should go there.
d) IF the flag has been captured, the bot should locate and pursue the flag carrier
e) IF the enemy flag is in their base, AND most of the enemy players are fighting outside, the bot should try to capture it.
g) IF a base has been captured, or about to be captured, AND there are team-mates defending it (OR there are few enemy players around it) the bot should go there and try to capture/defend it.
All these evaluations should be made considering the on screen messages (IE: "The alliance captured the farm") and the number/location of allies/enemies.
3) Random un-stuck behavior: Currently, when the bot finds a blockade, it always behaves the same way. At first it tries to run thru it (which is impossible, by the way), then it tries to jump (again pointless), and then it walks back, it walks to the right, and continues. It should choose from a number of pre-defined behaviors, and try one different each time it gets stuck. It should also have a "timeout" for the un-stuck movement. IF it tries to un-stuck unsuccesfully for 10 times, and its still in the same place, it should use its heartstone and leave the BG. It should'nt keep trying the same movement over and over. (This last thing applies outside BGs as well).

 

^^ If this was done - even imperfectly, I would say that HONORBuddy would once again earn it's name! I mean, if my Mini-map can show me where my team-mates are, that means that my interface is being fed that info. When I have Carbonite enabled, it even shows who is in combat. If they can get that info, then HB can capture that info and direct my toon intelligently. Is it alot of code, especially for the multiple battlegrounds? Yep, I'm sure it is... BUT in the end, we'd be able to truly run BGs with our bot.

Hoping to see something like this in the future...

 

Interesting video. He demonstrates one of the things I dislike about GB2: What I call the "double-back" when the no ninja option is set. A simple solution is to temorarilly ban a node for x seconds that was skipped becase of the no ninja option.

 

What if BG bot checked for people yelling go for BOSS in battleground, checked amount of people there and go dps/heal near boss area?

 

maybe with a table for different languages, or a template so everyone can edit it buy him self?

 

I have run a lot of AV and its too bottish. Good leveling and great way to get justice points to update eq.

But running AV alliance he starts and runs to the main road, runs half way up then runs back a ways then stops and just stands there for 30 seconds.
this is the start of every run.

Runs to the left at the fork and everyone else runs to the right, hits all the horde and dies.
Does a good job trying to defend the cemetery then once that is lost he is confused as hell.
If there was a way to pick defense of main base, run in a building and defend it or offense and have a good pathing set up to get to the horde main base but then we hit the big problem.
When to go in. As now he will run in and die over and over.

this would take work but like someone posted before blacklist this area until someone says all in. Or even better detect people in and then go, since some idiots spam that all the time anyway.

 

I haven't tried running AV with anything other than LR cause my computer bogs down WAY too much when there is a major melee... once I get a faster computer I'll probably give that a shot... but I wonder if using Squire would help you since that would have the bot follow the group going forward without being too obvious... at least until it died. Once it died and it didn't have a group to follow, then it would revert back to the profile directions...

 

What i whant, is to see in HB option for run rundom heroic or specific heroic/normal for my bots ( 1 time per day ), to make somekind of "HumanLikeActivity" to gain wear/weapon and minimal achivments.
Problem with IB now it`s no option like " Run one dungeon per day" so i can`t use it in mixed mode((

http://www.thebuddyforum.com/honorb...ddymanager-bot-base-profile-zone-changer.html this must make my happy) some thing like that MUST BE(!!!!) in HB not just like plugin!!

 

I would like to see a timer in the window with the kills and xp/hr just to show how long it's been botting. Other than that, whatever...

 

What I would love to see is some logic involving repeated fail actions.
For instance, action fails 10 times > Skip action or go to action b
Last night I spent from

[1:48:05 AM:466] Changed POI to:Type: Repair, Name: Floyd Pinkus
[1:48:06 AM:284] InteractDebug:383895304
[1:48:06 AM:293] Interact Done:383895304
[1:48:09 AM:770] Cleared POI -Reason POI is not Mail

to

[2:35:46 AM:898] Changed POI to:Type: Repair, Name: Floyd Pinkus
[2:35:47 AM:630] InteractDebug:383895304
[2:35:47 AM:633] Interact Done:383895304
[2:35:50 AM:553] Cleared POI - Reason POI is not Mail

45 minutes with the bit sitting there failing because it can't understand that it's failing. Good thing I caught it or it would have gone on until 4:30 when Arelog would have shut it down.

 

I'll add to buddyhelper after I update buddymanager.

It'll just monitor POI, and if it happens 10 times in a row that it selects the same poi.Guid it'll stop HB, then press Start.
That normally fixes these problems.

 

could you add function to join BG as party ? it's help alot for me ( and for another , i think )