Honorbuddy 2.5.6647.521

[hatscom]

Am i the only one that has to juggle p-r-o-x-ies and jump through all kinds of hoops just to connect and download updates from this website?

Autoupdater in the client just deletes my exe, hangs for 10 minutes, then gives me a timeout error. My browser lets it download (at very low speed usually) for about 15% then goes to 0 kb/s and times out.

When I finally find a working pr-ox-y, it downloads fully in less than a minute, unfortunately the same pr-o-x-y never seems to work twice. Don't understand it, no user-uploaded files on the forums give me any trouble, nor do I have any issues browsing.

Going to internet cafe now to try there..

 

[hatscom]

don't mean to sound unappreciative though. thanks a lot for the hard work on these releases!

I do tend to eventually get ahold of them..

 

[23051602]

BTW,i run KIck profiles from 1-90,
never happen this b4 because i run this profiles for my another char,4 weeks ago

Try to find the NPC and get the quest yourself. It's King Genn Greymane that you are looking for he gives two quests.
Alas, Gilneas!
Exodus

Should be working after that I think

 

[hi1674]

What about the possible detection ?

 

[23051602]

There is fairly common very dangerous problem now in the latest release.

Once in a while the bot will run up close to a mob. Then start circling and the mob circles and bot circles without attacking this will end up with them dancing around each other for as long as I watched. This is extremely botish!

 

[23051602]

The DungeonBuddy has an insanely dangerous setting I just found out the hardway. Buy it selling my whole blue healing kit, since it's setting is vendor rare. For some extremely odd reason it starts by selling everything in your bags. Insanely annoying !!!! And no you can't buy back enough items to fix this.

 

[vita]

the word is spreading that this last version has a security breach i have been advice to shut down all my bots and many people did the same, i will not bot until i have an oficial explanation for this. So i advice you all to do the same for now SHUT DOWN YOUR BOTS.

 

[23051602]

It might have something to do with the constant DCing depending on a LUA script that is bugging

 

[starl1te]

The DungeonBuddy has an insanely dangerous setting I just found out the hardway. Buy it selling my whole blue healing kit, since it's setting is vendor rare. For some extremely odd reason it starts by selling everything in your bags. Insanely annoying !!!! And no you can't buy back enough items to fix this.

go into your account and you can restore as many items as you want from there (once per month)

 

[vita]

still no reply

 

[Nightmare]

the word is spreading that this last version has a security breach i have been advice to shut down all my bots and many people did the same, i will not bot until i have an oficial explanation for this. So i advice you all to do the same for now SHUT DOWN YOUR BOTS.

What in the hell are you talking about?

 

[vita]

What in the hell are you talking about?

well its not may fault that you just replied to this post at this time, seems like you just arrives now and you need to go and read all the ban section

 

[techgod]

you need to go and read all the ban section

There's nothing to see in the ban section. Just the usual queued bans going on. Plenty of people are still running the bot just fine, gathering, etc, and haven't been banned.

In the hope that you and other of your ilk finally understand the difference between queued ban batches and a banwave, here is a pretty simple explanation of the two:

In a queued ban batch, Blizzard flags suspected botting accounts according to reports and/or suspicious activity according to their internal criteria, then bans all the flagged accounts in one go, at a later date. This is what we are seeing right now, albeit at a higher volume than usual. This is NOT a banwave, however, because

In a legit banwave, ALL accounts that use a bot after a detection method is introduced are banned. Thus, IF we were seeing a banwave, I assure you that you would be seeing HUNDREDS (not tens) of reports and the forums would be chock full of people, if not down completely due to the number of people trying to access the forums. Clearly you don't remember the infamous Glider banwave of 2008. This has not happened to HB.

In conclusion, until the above occurs, there has been no banwave and no detection by Blizzard, so kindly shut the hell up and use some logic.

 

[tumbum]

Toon trys to buy Food/Drink but the Vendor just sell Alc. In the Log it tells to Blacklist him, but doesnt work, still stay there and try to buy.

 

[23051602]

There are a lot of disconnects now depending on LUA errors.

[string "hax.lua"] attempt to index global 'ACTIVE_TALENT_GROUP_CHANGED' (a nil value)

or

')' expected near 'Vir'

It will DC me alot so please have a look at this asap. This was not present in the latest few versions of HB.

 

[wired420]

There's nothing to see in the ban section. Just the usual queued bans going on. Plenty of people are still running the bot just fine, gathering, etc, and haven't been banned.

In the hope that you and other of your ilk finally understand the difference between queued ban batches and a banwave, here is a pretty simple explanation of the two:

In a queued ban batch, Blizzard flags suspected botting accounts according to reports and/or suspicious activity according to their internal criteria, then bans all the flagged accounts in one go, at a later date. This is what we are seeing right now, albeit at a higher volume than usual. This is NOT a banwave, however, because

In a legit banwave, ALL accounts that use a bot after a detection method is introduced are banned. Thus, IF we were seeing a banwave, I assure you that you would be seeing HUNDREDS (not tens) of reports and the forums would be chock full of people, if not down completely due to the number of people trying to access the forums. Clearly you don't remember the infamous Glider banwave of 2008. This has not happened to HB.

In conclusion, until the above occurs, there has been no banwave and no detection by Blizzard, so ly se hell up and use some logic.

Honestly the cursing and insults were unneeded. I was in a Skype chat where between around 10 people both eu and us, about 25 accounts got popped in about 3 mins. All that got hit were gathering in MoP with GB. All on different servers.

Odd for that many to all get popped at once. Everyone of them using the beta.

 

[r0n3n]

You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #16357
You are currently on build #0
-------------------------------
I have the 32 bit version open not detecting wow please help

 

[Crowley]

Honestly the cursing and insults were unneeded. I was in a Skype chat where between around 10 people both eu and us, about 25 accounts got popped in about 3 mins. All that got hit were gathering in MoP with GB. All on different servers.

Odd for that many to all get popped at once. Everyone of them using the beta.

Odd...yes it is. But since i have been using GB2 to gather in MOP for the last xxxx weeks and haven't been banned yet i would have to say accounts have been flagged beforehand.
Were these people gathering 24/7? Were they selling gold? Did they buy gametime with gold? What time did they all get banned at, maybe they weren't gathering when i was which would indicate Blizzard throwing a proverbial EM bomb to catch people at that exact time? SO many variables.

And the only version i use is the Beta.

Edit: Were they using public profiles? Is someone in your skype group, 10 people all talking about botting, working for blizz? Again...SO many variables.

Edit-Edit: And this is the actual release thread so not sure why Beta is even mentioned

 

[Mame]

Hi

Toon just not moving for some reason. Log attached.

I'm using Kicks. In this log you might notice that I chose the first profile and let the rest auto-load. I'm quite certain that has nothing to do with the issue as it happens when I manually select the 12-58 profile too.

Any help would be greatly appreciated.

Thanks

I just found out why. On quest Marauders of Darrowshire, only 4 Fetid Skulls had been converted to Resonating Skulls instead of 5. All I had to do was manually convert one and the bot worked again.

Cheers

 

[23051602]

There is a bug when you are taking off and have a mob selected. It seems like the bot is trying to attack the mob in flight but instead it's just flying around it and using the "unstuck routines" which makes it circle the mob all the time.

[10:05:17.233 D] [QDBG] Done with forced behavior [ForcedQuestObjective Objective: [CollectItemObjective ItemID: 64352, Count: 10]].
[10:05:17.345 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf.
[10:05:17.345 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedIf.
[10:05:17.345 D] Compiling expression '((HasQuest(28486)) && (IsQuestCompleted(28486)))' @ line 1119
[10:05:17.919 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[10:05:17.920 D] Goal: Flying to <-10736.81, -836.5693, 91.56391>
[10:05:17.920 D] [FlyTo-v241(debug) @line 1120]: Flying to '<-10736.81, -836.5693, 91.56391>': <-10736.81, -836.5693, 91.56391>.
[10:05:18.190 D] [CGSpellBook::CastSpell] Override ID: 59569, KnownIndex: -1
[10:05:18.198 N] Mounting: Bronze Drake
[10:05:20.402 D] Changed POI to:Type: Kill, Name: Neferset Ritualist
[10:05:34.331 D] Could not generate path from {-11526.82, -576.754, 146.0656} to {-11524.72, -577.9148, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:37.394 D] Could not generate path from {-11522.49, -576.3553, 147.2273} to {-11522.72, -577.6606, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:38.283 D] [Flightor]: Unstuck attempt 8
[10:05:40.546 D] Could not generate path from {-11519.39, -579.0898, 151.5389} to {-11522.72, -577.6606, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:43.586 D] Could not generate path from {-11520.41, -575.6836, 154.5987} to {-11522.72, -577.6606, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:44.269 D] [Flightor]: Unstuck attempt 9
[10:05:46.667 D] Could not generate path from {-11520.97, -577.3281, 159.4223} to {-11523.15, -577.4672, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:53.613 D] Could not generate path from {-11518.45, -583.9206, 165.2667} to {-11519.9, -585.5459, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:56.720 D] Could not generate path from {-11516.05, -588.1721, 168.6846} to {-11518.51, -587.472, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:05:59.773 D] Could not generate path from {-11519.01, -589.3282, 172.0441} to {-11518.51, -587.472, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:06:02.783 D] Could not generate path from {-11520.83, -583.1718, 175.3542} to {-11519.63, -584.5052, 106.1215} (time used: 0 milliseconds) @ FindStartPoly
[10:06:09.956 D] Could not generate path from {-11537.17, -599.9059, 179.5721} to {-11524.87, -576.9979, 106.1216} (time used: 0 milliseconds) @ FindStartPoly
[10:06:13.657 D] [Flightor]: Unstuck attempt 10
[10:06:15.198 D] [Flightor]: Unstuck attempt 11
[10:06:20.216 D] System.NullReferenceException: Object reference not set to an instance of an object.
at Bots.Grind.LevelBot.(Object )
at Styx.TreeSharp.Action.RunAction(Object context)
at Styx.TreeSharp.Action.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Sequence.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.Decorator.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.TreeSharp.PrioritySelector.
.
()
at Styx.TreeSharp.Composite.Tick(Object context)
at Styx.CommonBot.TreeRoot.()
[10:06:20.213 D] Cleared POI