Honorbuddy for MoP 5.0.5.16057

my lowbie cant seen to complete quests that requires him to choose a item so i cant afk, other than that is ok for now

 

yeah the main quest i have to manually do are the ones where he has to click on stuff in his bags and whatnot,

 

Some real Reports

System Info:

Windows 8 64
i7 3.9Ghz ,16gb RAM

Latest version of HB.

Ret Pally using The Saint CC http://www.thebuddyforum.com/honorb...aid-farm-quest-saint-prot-ret-paladin-cc.html

I Hand leveled using Lazy raider all the way from 85-90 inlcuding many dougens, Had ZERO HB crashes.

Great work.

 

Botted 85-90 in AV now without any problems. Only like 1 kick, but that was bcuz of server Stormscale..overpopulated, so its understandable.
I recommend everyone just bot AV, sweet exp and no bugs. Could be retarded at Drek/Vanndar sometimes.

 

AW: Honorbuddy for MoP 5.0.5.16057

If you happen to be a monk, that issue just got fixed.

 

Everything was working fine untill yesterday update. The bot wont start (Gatherbuddy). Attaching log. Will appreciate help. thanks.

 

ok so, with gatherbuddy or archbuddy,
anytime the bot brings my character in some tree branches high in the sky, the bot acts like its stuck (it flys left right pauses ect) and it just keep "unstucking" but the charactor ISN'T actually stuck, because you can fly through the branches.

i have to stop the bot and fly out of the trees, or fly over the tree tops. then it works 100% perfect till more trees (meaning i cant afk with it )

im pretty sure this was happening before the big wow patch to, is this going to be fixed or anyway i can fix it?


scroll to the end of the log,

Code:

[17:34:23.466 D] [CGSpellBook::CastSpell] Override ID: 32244, KnownIndex: -1
[17:34:27.540 D] Flushing timed movement. Direction: Forward, JumpAscend
[17:35:08.498 D] [Flightor]: Unstuck attempt 9
[17:35:22.053 D] [Flightor]: Unstuck attempt 10
[17:35:23.220 D] [Flightor]: Unstuck attempt 11
[17:35:24.381 D] [Flightor]: Unstuck attempt 12
[17:35:25.560 D] [Flightor]: Unstuck attempt 13
[17:35:26.731 D] [Flightor]: Unstuck attempt 14
[17:35:27.897 D] [Flightor]: Unstuck attempt 15
[17:35:28.971 D] [Flightor]: Unstuck attempt 16
[17:35:30.092 D] [Flightor]: Unstuck attempt 17
[17:35:31.277 D] [Flightor]: Unstuck attempt 18
[17:35:32.451 D] [Flightor]: Unstuck attempt 19
[17:35:33.611 D] [Flightor]: Unstuck attempt 20
[17:35:34.763 D] [Flightor]: Unstuck attempt 21
[17:35:36.004 D] [Flightor]: Unstuck attempt 22
[17:35:37.098 D] [Flightor]: Unstuck attempt 23
[17:35:38.249 D] [Flightor]: Unstuck attempt 24
[17:35:39.417 D] [Flightor]: Unstuck attempt 25
[17:35:40.577 D] [Flightor]: Unstuck attempt 26
[17:35:41.740 D] [Flightor]: Unstuck attempt 27
[17:35:42.915 D] [Flightor]: Unstuck attempt 28
[17:35:44.113 D] [Flightor]: Unstuck attempt 29
[17:35:45.280 D] [Flightor]: Unstuck attempt 30
[17:35:46.954 D] [Flightor]: Unstuck attempt 31
[17:35:47.956 D] [Flightor]: Unstuck attempt 32
[17:35:48.949 D] Flushing timed movement. Direction: Backwards
[17:35:48.963 D] [Flightor]: Unstuck attempt 33
[17:35:49.953 D] Flushing timed movement. Direction: Backwards
[17:35:49.959 D] [Flightor]: Unstuck attempt 34
[17:35:50.950 D] Flushing timed movement. Direction: Backwards 

 

Is there a changelog posted somewhere listing the changes/fixes for each release? It would be extremely helpful to have this information while we're helping to test the software. I've been assuming that if the first post in the thread says "X isn't working", then the devs probably aren't ready for us to test that particular piece yet. Otherwise, we haven't been given much information to go on for testing purposes.

And for all of those who keep making ridiculous statements like "they're busy working on the bot - they don't have time to do this" - I can almost guarantee they already have this information somewhere. It's kinda hard to keep track of what's working - what's not - when code changes are made - etc - without it. In any normal testing environment, those testing the software would have access to this information. It's not a luxury - it's basically a necessity.

 

you wants logs here the logs of the new released 477, null error + auth failed + max sessions+ not selected a valid instance error too i have it to run in 4 accounts this is the logs

how to get back version 465 that was the most stable release

 

Here's a monk Windwalker class I threw together for singular. I have only tested it at 87, worked exactly as I wanted it to.

Just drop it into the monk class folder for singular and start it up. Enjoy!

 

this is a pack new error first it gives alot of shitty auth fail then it logs and attach to toon start it it works after 1 min or to give not selected a valid instance error even after it attached to toon be4 it here is log and again come someone please link me fresh version 465

 

make a thread in Combat Routines under monk so people can get use of it

 

how I'm trying to bypass it ?????? i have working keys you want me to email them to you and if I'm using a ***** version or trying to ***** it how rude I'm coming and show in the forums

this is nonsense Apoc

and if servers think that i'm trying to bypass it how to fix it form me any tips .........

and why bypassing now this auth failed started for me for the version 470, 465 and down never got this and if you doubt i didn't buy the project think again and tell me to email my keys

 

[20:32:35.052 V] 127.0.0.1 is not a valid host entry address. [auth3.buddyauth.com]


nuff said lol

 

after all i'm bypassing the auth server this is what you think ....

i don't even know what this error mean anyway what is 127.0.0.1

 

with this new release the bot not attacking at all... any idea? :\ till this release all worked fine

 

After .478 toon will not attack mobs

View attachment 4064 2012-09-27 17.05.txt