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

first!

 

alright ... now for the most common issues

WSG Mesh - there's a pike near one of the doors on horde side that we get stuck on, a lot
Insignia removal / return flag - i believe there's a plugin for this atm... but it would be nice if the bot itself had an option (ie: target mounted players?)
Something I would like seen:
Give us checkboxes for what logic *we* want our bot to do

Some people like to attack flags, some people like to stand midfield and die or farm, some people like to camp towers, or ... default logic

user requests thread:
http://www.thebuddyforum.com/honorbuddy-forum/25734-users-requests-bot-additions-fixes-etc.html

Jon310 has a good post:
http://www.thebuddyforum.com/honorb...uests-bot-additions-fixes-etc.html#post312620

Bot runs through water a lot (i've seen this) in BfG, TP, and AB. it's annoying and the bot not only runs through the water, he turns around multiple times like a re-re

my personal QQ from TP and BfG:

not switching gates in SoTA? someone said

anyways - i'm sure you'll understand the User Requests thread more than I... i've tried to keep it cleaned up since I made it

Cheers

 

Eye of the Storm:
Had multiple issues when ever you start(Alliance) the bot would run of the boulder(starting point) and on landing it would try to run up to the last known point(which is in air) and is stuck untill death or stop/start correction.

*fixes i've tried:
- reinstall mesh folder
- fresh install hb

*log:
none

 

WSG often wants to send a rez'd person back to the flag room, but with the spawn area lowered your running into the hillside. DEAD GIVEAWAY!

I tried woots BG's paths still same problem and I think woot even referenced the mesh as the problem and not the profiles that were updated.

Also the DPS just dosent seem to add up... I tried multiple CC's but I often run into other bots with no help from the other side around that just seem to be a 3 hit wonder and im dead, this goes for my DK, Pally, Rogue.

I will que for som BG's today and watch them closely and update on here what I notice.

So far
WSG -Horde-
Round starts and the bot take's the path to the ramp and meets the Alliance army solo 99% of the time
Spawn runs into hillside (MUST fix)
Jumps down and runs into logs thats on the ground

AV -Horde-
Round starts and 5 people rush to cap that farm flag... This I think very little of but it does get me going "hmm" and the 2nd or 3rd flag with people you dont know going the same way as the bot

And yeah like kick says above this. The wide mounts always seems to hook these objects where the slim mounts like horse and such dont grab it near as much.

 

From http://www.thebuddyforum.com/genera...roxbots-closing-all-aboard-thebuddyforum.html

 

AV Alliance
1) When the BG first starts the bot always stops at the bottom of the hill right before it gets to the 3rd ally bunker. It will then head up the hill, usually stopping again in an "odd" spot.
2) Make the alliance go to the right of Belinda. Currently the bot always travels to the left, which makes you stand out and puts you in direct path of the Horde. Depending on the CC.. sometimes it will stop, dismount, and try to attack them as they go by. Instant death.
3) The bot should try to capture certain graveyards / towers, depending on the faction.

Just a suggestion if it's even possible: I would love to see better logic for healers. If 5 people are at a flag fighting and 3 of them are healers.. skip it. If 5 people are fighting at a flag and none of them are healers.. that's where I need to be. This would help divide the healers up a little bit to better support the DPS.

 

Logic for healing classes, I've seen multiple times that I level up a healer, put it in BG and then bam, it start to go near enemies since its trying to be in the combat a lot but then it tries to heal his ass off in order to stay alive which is simple stupid.

 

First thing I would wish for would be some sort of fuzzy logic. More random behavior is really needed these days in BGs where more than one HB BGbot runs, because BGbot itself with a good CC looks surprisingly human-like, but two characters running the exactly same path or always standing on top of each other throws up a huge flag.

A long term solution could be user-editable .xml profiles for BGbot, where people can make their own hotspots (and paths/behavior weightings?)

Maybe you could add more hotspots and have the bot chose randomly from one of them. I would also like some insight on how BGbot decides where to go in games like BFG or AB, because the overly defensive behavior isn't always a good thing when 5 bots stand still at one flag in BFG. (it has happened to me before)

 

bots running on top of each other, due to the navigator, generating the same path from point to point, like one base to another (in AV). i know theres not a lot of information, but there's gotta be a way to make it NOT take the most direct path, and randomize the path the bot takes. one way would be to add blackspots so it forces it to take detours, and then make something to switch those up. so at least in AV it makes the path more random.

also when its mounted, it tends to ignore players and run past them (most of the time) you might already be addressing this in your "targeting issues" but ether way.

 

2 and + HB bots running at the same time in small BGs like AB and WSG most of the time lead to awkward situation where you have them all bunched up following exact same route :/

 

In AV the bot will randomly stop, and then sometimes go back the direction it just came, regardless of where your default hotspot is. Also in AV - if you're ally - sometimes after it stops it keeps going and it will go down the wrong side of Balinda towards field of strife and get obliterated by oncoming horde.

AB, BfG, EotS: Once the node is captured the bot will leave; I would really like an option to stay and defend the node for "x" period of time, or if thats not possible code the bot to stay a *variable* amount of time before leaving.

Also, just want to check that this actually works: today I changed the default hotspots in AB by -4 for each one, to try avoid all the hb bots stacking up on top of each other. It seems to have worked, but once I was stacked - so would it be a coincidence I stacked or coincidence I didn't? I wasn't watching the whole time.

 

Line of sight issues, Bot targets player in a building (whilst bot is outside), Bot will then do the 3 step Bot shuffle repeatedly until it either manages to get in the building, the targeted player goes out of range or the Bot is engaged by another player.


Might be shooting a bit high...but, how about a logical chat function for each BG that can be edited by the user

i.e. AB, Bot recognises which Resource it is near and when it gets into a (fight) calls incomming,

Bot recognises that we are holding 3 of 5 resources and bg chats one of a list of user defined - Defend what we have, dont push out yet

and/or randomly bg chats says anyone of a user defined list i.e. call incommings, LM safe for now (if at LM and not being attacked)


Would like to see the BGFIX pluggin in the BGBot settings


Plus rep and hugs for looking at this Bot even if you ignore my suggestions


A follow the crowd option, biggest crowd (your own side) stay with it

 

Agreed bot is quite stable now, glad you are looking at it Apoc.

Maybe focus on whatever is "call to arms" this weekend so it can get a good work out ?

G

 

General:

- When at a flag location, don't stand there and do nothing like the other 3 botters. (a small location swap would already make the difference or even if it would shuffle between that location and a fight location or so)
- don't stop at random locations that aren't being used ex AV where it pauzes a lot and doesn't go via the proper way to boss 1(alliance) and thus dying as always
- make a logic where it will capture the flag maybe and try run back to base, or pick up the flag if dropped next to you and run to base
- insignia looting
- option maybe to stick as group or go spread
- group pvp??(would love to see a heavy melee, resto druid, ranged work them baddies in pvp)

If I find more relevant info of my bots ill post here.


Sent from my iPhone using Tapatalk

 

As mentioned above, just work on Fuzzy Logic and Randomness of the bot along with LOS/Targeting and avoidance situations like detecting 30 enemy players coming your direction... Don't try to fight them all by yourself... Run and get killed to look more realistic who stands there and fights 10+ enemy players at once... Let alone step into a group of them...

Rez a little slower to look less bottish... Just do what your doing and rework it to look more human... It's very easy to tell its a bot by how it runs around and cuts corners super close... no zig zagging or "player like" behaviors gives it away... Especially people who have used the bot before... Make it twist jump and zig zag more...

 

ok so i know im gunna get flamed for posting this but anyways.

when i queue for AV i can go on all night and know i wont DC or afk out or anything.
as soon as i try random BGs, i always get DC'd overnight.

my guess is i get stuck somewhere in a random BG and the thing gets reported afk and i guess he just waits for deserter and gets DC'd cuz hes afk. might not be it. but it happened today in AB, i left it on while i was shopping and playing Wii with my GF and when i came to check up on it it was DC'd (that was while i was farming AB for the call to arms weekend for conquest cap).

anyways. a simple anti afk check if we get deserter would be nice. i honestly didnt sit to see if it did that already but when i get home and leave BGs i dont notice it taking over while i buy/gem/reforge my new gear. like id see it jump or try to move in a direction if it would try to.
the random BG feature needs some love but im sorry i cant really help about specific issues. i just get DC'd everytime i run it. i will farm AB all night and ill post a new reply to this thread with the appropriate log. i just restarted honorbuddy over 20 times today for plugins so i wouldnt be able to tell wich log is the good one.