What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Just wondering why it takes so much longer for HB to update VS our competition?

Status
Not open for further replies.
Apoc why don't you have dev under your name so people who are new can tell that you are a dev?
 
As much as it burns to not have my HB (D:), I don't mind the wait. I know that they are doing their best to make sure it is secure (also devs live in EU, patch went live way later over there). Hope to see new uber release soon!
 
Well shit I live about 3 hours away from Bossland and would let him use my US account for testing cause at the moment I only play my EU account.
 
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.

Should change that to 40 yards so healers can still heal at max range. I assume this was the issue that would make the bot run back and forth whilst trying to cast in a BG?
 
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.

Amen brother, tell it.... take all the time you guys need, I shall wait patiently and happily in the meantime. I as many others would agree, prefer a Stable, Safe, Undetectable Bot, as opposed to some rush hack job that's thrown together just to get it "out the door" and likely to get the banhammer. Do all the checking, rechecking, testing, and retesting you need to do, folks can wait, high quality safe undetectable software is what makes this app great, and it should stay that way, so if it takes a few days to "get it right" so be it, ya got my vote, keep up the good work.
 
Apoc -

It would happen at EVERY FP for me.

Its say 'learning new FP' itd open up the FP map, but the 'learning new FP' wouldnt change, and itd keep the map up. If i exited out of the map itd just reopen it again with 'learning new FP"

and they arent even new Fps >.>
 
Do you have a log from when this happened? And at which FP?

He's not the only one that has that trouble, I've got several logs stored currently under my profile here that has recorded that same error, feel free to look at any of the ones that are stored. If you don't have the ability to see the files, let me know and I'll post a couple more. It's pretty much any flight master that has a potential of giving that endless loop error, so not just one in particualr.
 
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!!
 
Does anybody else have serious issues with characters getting stuck under/on fences. They have really become my arch nemesis. My toon always gets stuck on them , normally it has no problems navigating between tight spaces: Between trees or going up ramps... but it tends to get stuck very often on small objects such as tables , chairs and fences!
 
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.
 
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.

I noticed this too, and honestly totally forgot to add the blackspot for it.

I'll try and get it in before we release, if not, I'll just provide a proper profile for it.
 
Status
Not open for further replies.
Back
Top