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

[Apoc]

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)

BGBot already has profiles you can edit. (Check the Default Profiles folder. The "full" named BG ones are BG bot profiles. See AlteracValley.xml for an XML spec)

[Lindariel]

All - With more then one HB bot in the same BG they tend to stack up on the exact same spot, perhaps make it (when out of combat) always move atleast 5 yards away from other players?
AV Alliance - At the start, it stops in the chokepoint at the first tower before Belinda, pretty much forcing it into a defensive game all the time.
IOC Alliance - In my battlegroup, we always go for left gates on the horde keep. Bot always goes for center gate and humps it for some time before giving up and heading to workshop. Perhaps there is any way to read the current HP of the gates and make it head to the lowest one?
AB Alliance - Bot tends to go defend spots with more then 3 people at them, something wich has resulted lately in people telling me to go someplace else, perhaps change the density check to make sure it helps defend where there are only 1-2 players?
Twin peaks and IOC Alliance - Bot stands still at the spawning location until gates open (sometimes up to 10 seconds after gates are opened) before it moves. Perhaps make it run to the gate like it does in AV and WSG?
SoTa Alliance - Bot seems to have problems with navigating over broken walls, also, when defending it does not attack demolishers. Is the targeting logic only CC-based or is it possible to make it focus attack demos while defending?

Also, a way to either force it to or for the bot to randomly choose to play defensive/offensive would be great. Makes it feel a little bit more humanlike

[Lohva]

call out incomming in AB and EOTS at the given base.

[surfer999]

AB. Bot often run and fall from cliff near LM Flag. I found this glitch on last weekend.

WSG Bot again often run in wall near GY.

[Bigbadwolf]

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.

Have to agree here with the poster i run 3 healers and in bgs they look kinda stupid. dps classes look more Player like running up and killing stuff while healers run up in the face of a target and starts to heal himself...

if any logic could be inplemented it would be really nice.

[Severance]

Would it be possible to have it randomize its path a bit? It's pretty obvious for others to spot you botting when there are others running the exact same path.

Edit: Bot always seems to fall off the edge at the starting area in EotS. Dunno if this has been mentioned already.

[Paddy]

Edit: Bot always seems to fall off the edge at the starting area in EotS. Dunno if this has been mentioned already.

^ that.

[peanutbird]

Oh yeah, something I remember:

It would be cool if BGbot could parse the BG-chat and prioritize it's own behavior when someone mentions a certain objective.

Like "LM", "Mine", "BS", "ST", "Farm" in AB, "BE", "Draenei", etc in Eots and so on.

[no1knowsy]

Reporting Issue: EU WoW Only (apparently) & BG Bot Que

Description: Bot is set to que 2 BGs. One of the BGs pops. HB does not accept, it actually locks up, until you click it yourself.
QuickFix: Set the bot to only que for 1 BG, or for random. This will work for now, but it's still an issue.

Did some quick testing.
Following is a just a simple 2 line public void() I threw into a plugin.

            Log("Index0: ",Styx.Logic.Battlegrounds.GetQueuedBattlegroundInfo(0).EstimatedWaitTime.ToString());
            Log("Index1: ", Styx.Logic.Battlegrounds.GetQueuedBattlegroundInfo(1).EstimatedWaitTime.ToString());

Following log will show info for when 1 BG was que'd, when 2 were que'd, and when none were que'd.
I have replaced my username with xxxxxxxxxxx, and added in ///////Comments///////
Basically I qued for 1, ran plugin, added another to que (2 total), ran plugin, left both (zero que'd up), ran plugin.

EDIT: An Index of 2 is not allowed. Out of paramaters or something... can't remember.
EDIT: and yet the following code gets rid of both BG Ques. Inconsistency.

Styx.Logic.Battlegrounds.AcceptBattlefieldPort(2, false);
Styx.Logic.Battlegrounds.AcceptBattlefieldPort(1, false);

Also reported in release thread: http://www.thebuddyforum.com/release...tml#post402640

-Thanks

[xf-1]

When i respawn in Warsong Gulch it keeps running into the cliff/wall. I think the bot still thinks its the old WSG mesh where the graveyard was on the same level but now its not. Can u update it please so i dont look like a bot standing in the graveyard