[PAID] BGFarmer - An Advanced Battleground Bot Base

Bot always trys to mount up, when he get the orb.. any ideas?

[BGFarmer] We've got an orb. Moving to the middle of the BG zone.
[BGFarmer] Lvl 90 Alliance Priest is holding an orb. Let's get them!
Mounting: Todesstreitross von Acherus

 

I'm not sure if you have fixed this already as I turned the feature off for now, but can you set a limit of like 4 to the inc calling chat feature. The other day I was in AB and my toon called an inc of 10 on the farm. No human is going to call an inc from 2/3 of the team to a specific number, I'd suggest maybe if the number of incoming is over, say 4, replace the number with a variable that the user can define in the GUI, like "Huge", or "Large", "many", "tons", depending on how the user words his inc message to include the number before or after the word incoming.

That way the inc call would be "Large inc Farm", or "Huge inc Farm", or "Inc Farm lots", instead of "inc 10 Farm" which looks inhuman to say the least.

Thanks,
- Jon

 

Millz,

For Horde side on Strand of the Ancients, bot runs to green gate sometimes and gets stuck there before game starts. I either have to move the bot myself or wait until the game starts then it actually moves out onto beach.

 

Hi Millz,

I dont know why but I cant upload the new version of the Botbase. I'm still at revision 83 with no chat etc etc. SO strange.... Last update appears to be (i the bot config windows) :

[20/Jul/2014 - Update #2]
- Fixed BGFarmer breaking initialization of Honorbuddy.

???

 

You can not update by svn anymore but only by buddy store through streaming. Millz is not updating his svn.

 

Hey - It happens when you don't have an Honorbuddy key attached to the buddyauth account you're logged in with attempting to make a purchase.

Is it doing this after every BG or just intermittently? Can you try Singular to see if it happens with that?

Couldn't be further from the truth. The bot is superior to BGBuddy in every single way. I suggest before you make wild outlandish statements, you provide some more detail as to what you think doesn't work.

Have you got a log file for picking up the flag? I know about the BfG issue - it's a problem with Honorbuddy's navigator. Will look into it.

 

Hey millz, a couple of suggestions:

-Chat function is great but let us insert a couple of different lines (entrane: hi all, hey everyone, hi guys etc) , I have never seen a human spam te same line over and over again. Also shorten the place names to abreviations, humans also never say BLOOD ELF TOWER but something like belf tower etc...

-Put the flag carrying on a lower priority when someone else from your team is around and make it say :"take flag!" , taking the flag as a bot puts WAY to much focus on you. (I've seen a couple of matches where it could have gone wrong for my account if I wasn't there.

-Make him stay/retreat into big groups instead of yoloing solo which gets him killed fast.

-Twin peaks: if a priest pulls you with his skill (because you are the flag carrier) the bot sometimes ends up under the alliance bridge, the bot goes completely broken if that happens. No idea if there is anything to do about this.

That's all for now

 

Thanks - think I've found the cause of this. Will be fixed in next build.

Hey - I've got a build that's nearly ready, so I'll look into this after that one is finished. You can just change it to remove the %enemies% tag though - "incoming %base%!" etc. It will only call incoming if it actually needs help.

Thanks for that - It looks like it updated the gate to show it couldn't be walked through, and then reset it again after that. I'll push a fix for this.

You need to switch to the store. www.millz.biz/claim/

Cheers

 

Hey

The opening greeting I'm going to change to make it so you can put "hey|hi|hello|hi guys|hey all", and it'll split the messages at the | character and pick a random greeting.

The incoming thing - you're better off making it look like a macro. {skull} Incoming %base%! {skull} - This was the macro that started this idea:

Code:

/run SendChatMessage(string.format("{skull} %s {skull} - INC!!",GetMinimapZoneText()),select(2,GetInstanceInfo())=="pvp" and "INSTANCE_CHAT" or GetNumWorldStateUI()>0 and "YELL" or "SAY")

This way works for all languages rather than just English clients.

Grabbing the enemy flag is the lowest priority - but you can disable that from the BG specific options. I agree its better left to a real player.

It shouldn't suicide into big groups at bases, running between bases however is a little more difficult to control. I've specifically avoided making it stay with groups of other players, because that causes bots to get tied in with each other.

 

Whatever you are doing, keep up the good work, I know these things take a lot of time

 

Okay, I am absolutely not sold on this botbase yet - that being said I will be spending a lot more time watching it, but so far I've done 3 games of AV (I do this because it's good honour and there's so many bots no one really seems to care),

but it does not seem ANY smarter than BGBuddy. For example; it went to cap a tower and got in a loop of walking up and down the ramp very quickly, which also happened to sync with someone else botting. it then just played very indecisively and when it was time to go kill Drek'Thar, the bot tried to make me walk BACK up North to try and defend the towers that were getting back capped. This is the most obvious tell for anyone botting, because when that happens all of the bots run north.

Is there a way to simply prioritise the bosses over capping/defending?

I haven't tried it on other BGs, so I will give it a go. So far, slightly underwhelmed.

 

To be perfectly honest, AV is probably one of the worst BGs in BGFarmer at the moment. The logic hasn't changed since I first released it. I'll work on it over the next few builds though - it's probably long overdue.

Running up and down a tower - I'll need a log file for this one. I suspect I know what's wrong with it though.

Cheers

 

-Strand of the ancients , he repeats the welcome line twice in a match, looks funny when he says HELLO EVERYONE when they just turned sides... ;-)

 

Can you make it so bot will stop and attack people when bots just focuses on getting flag back? It will run to its death with people just killing the bot but keeps trying to keep trying to get the flag. It totally ignores other players just going after flag.

 

Hi Millz,

I am currently using BGFarmer with Portals and have used it successfully on other toons already. Just something bit awkward that I have recognised about movement: Jumping mounted in water

This looks awkward and also makes water crossings take a lot more time. When crossing water on a mount the toon jumps all the time. Maybe this mechanic was designed not to drown - but it's still a bit weird. Also using water form on druids when movement is done by BGFarmer would be nice!

Thank you for your great work - as always!

 

View attachment 7212 2014-09-14 19.44.txt Having intermittant issues. SOmetimes it runs a BG and then recues after a win or loss, other times it logs out after a win for random BG. Did not happen last night seems to be quirky today. I'm using Tuanhas DK profile is that interfering somehow?

 

Hey - The LogMeOut plugin is causing that.

Code:

[00:25:06.071 N] [LogMeOut!]: Starting logout process...
...
[00:25:06.071 N] [LogMeOut!]: The character is in the battleground SotA. Waiting the end...

Yeah I've noticed that. It's an issue with honorbuddy's navigator and stuck detection system. It thinks it's stuck, so jumps. Will ask the core devs about it.

Can you post a log please? It should switch targets if you get attacked while moving to the EFC. Looked through the code but can't see where this would be happening.

It shouldn't be doing that, there's code in specifically to avoid it - can you post a log file please?

 

Ok i'll disable the LogMeOut and use BGFarms timer instead and see how that works.

 

Here you go think it was around 02:14 in the logs.

 

Thanks - I think I've already fixed this in the current beta build I have. Will need to test it when the store is working again. Broken for test builds at the moment