[Release] Honorbuddy 1.9.6.2827

[Poison Ivy]

They fail at it now it wont get fixed...26 threads and no fix..I don't want to even know how hard they will fail at 4.0 patch.

Ok.. remove your subscription and leave. Post helpful information here. For your information they are working on fixes and whatnot but it isn't of their top concern since it is usable right now. Me and plenty of other people have this running fine so it means its a decent release. On another note they have been working on the new patch and cataclysm in the background via Retail Beta.. People like you need to learn to be freaking thankful and if it isn't working don't make another post saying "wow its not working wth" because I am PRETTY sure they know some people have the exact same issues.

EDIT: sorry this sounded like a hate message. Just I hate people like that..

 

[Lockwood]

Avoid mobs and blackspots work fine.

Can you give me a profile to test, that can reproduce it failing?

Done.

Both run right through Andorhal in WPL. A whole area blacklisted. It also does not avoid Lord Malazzar (avoid mobs list). (level 55+).

This has been stated in a number of posts in these relevant threads.

Also Ungoro Devilsaurs are a prime example. Outland Fel Reavers.

Even Mord agrees with his Breakneck profile when i reported that it went right into a blackspotted farm house.

Shall I go on. I'm sure enough people on here have a number of examples.

 

[chinajade]

Also Ungoro Devilsaurs are a prime example. Outland Fel Reavers.

I won't argue with the rest of your points, but I think you misunderstand AvoidMobs. The tag is a substantial misnomer. Honorbuddy doesn't actively avoid the mobs listed--instead, Honorbuddy will just not be the initial aggressor to the listed mobs (i.e., they won't show up in the target list).

You can read more about its current behavior here.

My guess is that as Honorbuddy matures, it will actively Avoid the mobs listed in the future. To do this will require situational awareness of the battlefield--which Honorbuddy does not currently possess. Sadly, that is not how it operates today.

cheers,
CJ

 

[hiddenlol]

Have to agree with some others, i cannot run this bot in PvP mode as it constantly crashes. Will try grab a log next time if i bother opening it again

 

[bbj]

It also does not avoid Lord Malazzar (avoid mobs list). (level 55+).

The avoid rule does not mean the the bot wil run away form it. All it means is the bot wont pick a fight with it. If it moves close enough for the mob to aggro it will still fight it.

 

[DaSoul]

Have to agree with some others, i cannot run this bot in PvP mode as it constantly crashes. Will try grab a log next time if i bother opening it again

It's really strange how different the problems are, that people have with this. Used my shaman as a healer in pvp for 10 hours yesterday without one single error. The mage i am leveling at the moment gets a lot of "sync failed" but still continues..sometimes hb crashes but still keeps running as long as i don't close the crash message window.

 

[Apoc]

Done.

Both run right through Andorhal in WPL. A whole area blacklisted. It also does not avoid Lord Malazzar (avoid mobs list). (level 55+).

This has been stated in a number of posts in these relevant threads.

Also Ungoro Devilsaurs are a prime example. Outland Fel Reavers.

Even Mord agrees with his Breakneck profile when i reported that it went right into a blackspotted farm house.

Shall I go on. I'm sure enough people on here have a number of examples.

Alright, the reason you're not seeing any Blackspots working, is because we don't support the Blackspots tag within a GrindElement tag. Period.

I know someone said we did a while ago, but they were mistaken.

Tip: Use my profile editor to validate your profiles. If it refuses to load it, then it's an issue with the profile structure.

The following is the error message given by my editor;

 

[Lockwood]

Right.....

Just looking through Hawkers quest profile (had issues with both profiles) and all the blackspots are not within grindarea tags.

So not sure how to go about editing this profile to make sure it obeys blackspot rules. Everything seems to be in order. Will try out your profile editor and see where that leads.

 

[Apoc]

Right.....

Just looking through Hawkers quest profile (had issues with both profiles) and all the blackspots are not within grindarea tags.

So not sure how to go about editing this profile to make sure it obeys blackspot rules. Everything seems to be in order. Will try out your profile editor and see where that leads.

The following link is the corrected version of the Alliance 1-60 (Dwarf-Gnome) profile.

http://pastie.org/1207347

Simply move the blackspots out of GrindArea tags, and ensure they are within a SubProfile tag (or the main HBProfile tag)

 

[Lockwood]

Many thanks mate. I know you say ur profile editor does not support quest but will it still identify any issues with them?

 

[Apoc]

Many thanks mate. I know you say ur profile editor does not support quest but will it still identify any issues with them?

Yes. There's a small bug in the current version with CollectItem tags. (I have it fixed locally, just have to fix some other bugs before I release a new build)

 

[hiddenlol]

within hours of starting... never do i get to bot for more then 1 hour at a time, i return to my pc to find wow just frozen no error or anything just frozen. HB will say sync error. This at this point seems only to affect PvP... i have done 48hours without a crash leveling.


Log attached.

 

[craig9096]

have you guys ever considered releasing an auto-updater? Would be a very welcome addition =)

AMEN!!
Please auto update HB.

 

[Lockwood]

I give up.

All of that for NOTHING.

No change. Still ignore the blackspot and runs right through the middle of Andorhal.

Def won't be upgrading to lifetime. This bot is broken for PVE and for PVP. So fed up with stuff not working. Sorry for the rant but it's a joke.

So now HB (even 1.9.6.1 which is meant to be so fantastic) is a suicide bot for both PVE and PVP.

 

[Apoc]

I give up.

All of that for NOTHING.

No change. Still ignore the blackspot and runs right through the middle of Andorhal.

Def won't be upgrading to lifetime. This bot is broken for PVE and for PVP. So fed up with stuff not working. Sorry for the rant but it's a joke.

So now HB (even 1.9.6.1 which is meant to be so fantastic) is a suicide bot for both PVE and PVP.

Blackspots work perfectly fine. I effectively made HB run up the side of a mountain in Northshire because I had dropped a blackspot at the gate.

Don't blame crappy profiles on the bot.

 

[Lockwood]

Blackspots work perfectly fine. I effectively made HB run up the side of a mountain in Northshire because I had dropped a blackspot at the gate.

Don't blame crappy profiles on the bot.

You checked the profile. It was made by Bossland and Hawker. So I doubt the term would be Crappy. If they can't blackspot then there isn't much hope for the rest of the profiles.

 

[silversurfer]

blackspotting works, it is not a bot problem, perhaps corrupted installation, profile, settings ... a user can mess up a lot. but if you dont have the patience i think you shouldnt be botting anyway.

 

[Danne206]

The bot keeps spitting "Memory moved for lua events (newEvents); skipped for now." whenever he tries to do anything. Would highly appreciate any support in this matter, acts slowly aswell.

 

[jetta]

for tony

[17:23:12:117] Attached to WoW with ID 592
[17:23:12:119] Loading Honorbuddy 1.9.6.2827 settings.
[17:23:12:234] Log file: C:\Users\Admin\Desktop\hb\Logs\8-10-2010_17_23 Log.txt
[17:23:13:486] Authenticating..
[17:23:15:24] Authentication failed.
[17:23:17:405] Authenticating..
[17:23:17:562] Invalid response received from HB server: N/A

 

[Ilja Rogoff]

[17:23:12:117] Attached to WoW with ID 592
[17:23:12:119] Loading Honorbuddy 1.9.6.2827 settings.
[17:23:12:234] Log file: C:\Users\Admin\Desktop\hb\Logs\8-10-2010_17_23 Log.txt
[17:23:13:486] Authenticating..
[17:23:15:24] Authentication failed.
[17:23:17:405] Authenticating..
[17:23:17:562] Invalid response received from HB server: N/A

got this message several times too, but after retrying to login a few times it worked. just don't give up