Here's a small snippet of the changelog for the next build - note: it's nowhere near complete. (I'm still trying to remember my changes!)
FIX - You should no longer be booted out of HB when an auth server is having 'issues'.
FIX - WoWMovement.MoveStop() should properly stop you from moving forward/backward again.
FIX - Plugins/CCs/Bots using the AddRef compiler option will no longer try to load the same assembly twice.
FIX - Quests with item collection requirements should work properly again.
FIX - MountHelper should no longer throw exceptions when a mount return value is poorly formatted - WoW Lua related.
FIX - WoWObject.WorldPosition will now return a proper position. - Resolves issues with units/players on transports or vehicles.
FIX - WoWPartyMember.Role will now return a correct role.
FIX - BG Bot banner logic fixed.
FIX - BG Bot will now pay attention to the "Target Mounted Players" option.
FIX - Removed some debugging messages from BG Bot, and moved others to the actual Debug log.
FIX - BG Bot will now go to the opposing factions flag in WSG by default.
FIX - BG Bot - WSG has 3 new areas - in front of each base, and mid-field.
FIX - BG Bot - should properly try to attack the enemy flag carrier again.
FIX - BG Bot will now mount while waiting at a gate to open.
FIX - BG Bot target selection logic should work properly again.
FIX - BG Bot hotspot range has been increased to 30 yards, up from 5. This should solve attacking incoming players -> running back to the hotspot instead.
FIX - BG Bot can now queue for 2 BGs again. (Excluding if you have checked Random Battleground, of course)
ADD - LocalPlayer.PartyMemberInfos - to compliment RaidMemberInfos. Use PartyMemberInfos when you only need information about your current party.
ADD - BG Bot will now capture banners in AB and BFG.
Btw EU Servers have the patch now also!
Unlike most other bots on the market, we take the time to do our research before giving out builds.
We have roughly 3000 offsets to update each patch. Which roughly 200 or so require us to manually find/verify as correct.
On top of that, we also need to verify that structures haven't changed, and more importantly; implementations haven't changed.
After all thats done, we make sure Blizz didn't sneak something into the client under our noses.
Updating for a new patch takes ~3hrs or so (assuming its not a big patch).
Ensuring nothing is broken, and nothing sneaky has changed, takes about another 3-4hrs.
With that said; we had a few bugs in the last release, which we figured we'd get fixed before releasing a new build. And truth be told; they were required.
It's not that we *want* the bot to be down, trust us, we don't. But it's better for everyone if we're not releasing crappy builds because of a patch.
Do you have a log from when this happened? And at which FP?
Apoc keep your Time I rather wait 1 Day and keep my Account and do not loose it in a Bannwave.
BTW a want to add 1 request I want a Mixed Mode = Questing and PVP Beta...please!!
And gathering/PvP![]()
ask and you shall receive.![]()
Ask and you shall receive.![]()
Ask and you shall receive.![]()
This is a little random but it being battle of gilneas weekend I tried it out using bg beta and as horde I kept getting stuck right outside the gate on what I think was some sort of wooden boat on the right side until someone comes over and kills me. I think the path just needs to be set so he runs forward at the beginning.