HonorBuddy does not respect BlackSpots or AvoidMobs

[Bot]

I am setting up blackspots and HonorBuddy just ignores them. It just moves to the blackspot area anyway.

I am also using a profile with AvoidMobs and the bot attacks the fucking mob anyway. The mob didn't attack it first; the bot went out of its way to attack the mob.

Using this profile for the second problem: http://www.buddyforum.de/showthread.php?9377-Fishing-Pool-Sea-Turtle

 

[Pedo Bear.]

this happend to me2.

 

[Bot]

Any fix coming? Mesh is also corrupt in so many places. Making/using profiles is becoming a pain in the ass with all of these problems.

 

[dayloon]

Yep, had this also

 

[Stammi]

Have the same problem.

 

[Bishop]

Yep, had this also

^

*Filler*

 

[Bot]

Its too bad that a fix will almost never come.

Why would any of the HonorBuddy developers feel the need to fix these things? The majority of HonorBuddy users don't know what the fuck these things are. They just know that HonorBuddy is a bot and it works (although imperfectly).

Whenever you make a thread or post complaining about a broken feature of HonorBuddy or about authorization failures, you will immediately meet with at least 3 flaming HonorBuddy fanboys, arguing in one-liners and insults. While appreciation is definitely to be given to the developers of HonorBuddy, too much asskissing results in a lack of progress. I understand that the authorization issues have delayed fixes but problems like the SotA mesh have been around for MONTHS...

 

[lofi]

I had this same problem. Took me a while to figure it out, but it's actually a problem with the profile. You need to use a more up-to-date template for creating profiles. AvoidMobs and BlackSpots have be placed inside a <SubProfile> or <GrindArea> I believe. I can put up an example when I get back from work. However if you just use a newer template to include AvoidMobs and Blackspots you shouldn't have this problem.

 

[chinajade]

Indeed, Lofi has it right--that profile is not written correctly.

It appears to be a grinding profile, yet there is no <GrindArea> in it. Also, the <Factions> and <TargetMinLevel> tags will be completely ignored by Honorbuddy because they are used incorrectly. This behavior is required by the XML standard.

That Profile also places the <AvoidMobs> element below the <Hotspots>. This will cause <AvoidMobs> to be ignored. <AvoidMobs> should be placed nearer the top--its position within a profile is important. The same goes for <Blackspots>, if you're adding them.

I suggest you take that profile, and make it fit the form of the Grinding Starter Profile from the Wiki. If you need information about individual profile elements, here are the places that your cited profile missed or used incorrectly:

• <AvoidMobs>
• <Blackspots>
• <Factions>
• <GrindArea>
• <TargetMinLevel>

To be fair to the Profile Writer, he admits that it is his first profile. It does take some experience and skill to get them right, beyond the "it works for me" crowd. You can't blame Honorbuddy, if the Profile is written incorrectly. Honorbuddy may indeed have bugs, but we have to eliminate the Profile as a source of error before we can make that determination.

cheers,
CJ

P.S. - Lofi was incorrect when he said the other elements had to be contained in a <SubProfile>. It is perfectly fine to use the other elements without one.

 

[Bot]

Its not really a grind profile. Its just a profile to move from hotspot to hotspot while Autoangler detects pools.

So how about blackspots then? How come when you set them while using HonorBuddy, the bot still goes to the blackspotted area?

 

[chinajade]

Its not really a grind profile.

I agree--that confused me too. However, that appears to be its intent due to the inclusion of <Factions> and <TargetMinLevel>. If you believe it is more of a 'farming profile' (as I initially thought it would be, too), then model it after the Wiki's Starter Farming Profile, instead.

Edit (missed question #2, initially):

So how about blackspots then? How come when you set them while using HonorBuddy, the bot still goes to the blackspotted area?

The previously cited <Blackspots> documentation points out some problem areas. Also, Blackspots don't prevent HB from going through an area, they just make it 'much less desirable'. Perhaps some alternate path is too long that the 'much less desirable' is actually better than the alternative?

Plugins can also override just about any part of a profile. So, it could be Auto-angler's desire to get to a pool overrides the Blackspot set up in the profile. I haven't looked at the Auto-angler code, so can't say. You should be able to quickly test this by turning off the Auto-angler plugin, then running the profile. If it doesn't go through your blackspots, then its Auto-angler that's causing the problem.

I agree, many many of the meshes are messed up. But technically, this isn't an HBcore issue. The meshes are just an auxillary data input to HBcore as a Profile is. The mesh is provided by the HBteam though, so it is their responsibility to fix them. But mesh problems aren't the same as HBcore problems. The point is that mesh problems aren't HB-release specific.


cheers,
CJ

 

[Bot]

I agree--that confused me too. However, that appears to be its intent due to the inclusion of <Factions> and <TargetMinLevel>. If you believe it is more of a 'farming profile' (as I initially thought it would be, too), then model it after the Wiki's Starter Farming Profile, instead.

Edit (missed question #2, initially):

The previously cited <Blackspots> documentation points out some problem areas. Also, Blackspots don't prevent HB from going through an area, they just make it 'much less desirable'. Perhaps some alternate path is too long that the 'much less desirable' is actually better than the alternative?

Plugins can also override just about any part of a profile. So, it could be Auto-angler's desire to get to a pool overrides the Blackspot set up in the profile. I haven't looked at the Auto-angler code, so can't say. You should be able to quickly test this by turning off the Auto-angler plugin, then running the profile. If it doesn't go through your blackspots, then its Auto-angler that's causing the problem.

I agree, many many of the meshes are messed up. But technically, this isn't an HBcore issue. The meshes are just an auxillary data input to HBcore as a Profile is. The mesh is provided by the HBteam though, so it is their responsibility to fix them. But mesh problems aren't the same as HBcore problems. The point is that mesh problems aren't HB-release specific.


cheers,
CJ

I didn't encounter the blackspot problem on an AutoAngler profile. It was with a herb gathering profile. I blackspotted a dead end that it would keep walking towards. It was a tangent from the path I set.

 

[Apoc]

As chinajade said; blackspots don't *stop* you from going to those areas. It just causes HB to try and avoid them if it can.

If you blackspot the only way in/out of an area, and HB makes sure you cannot go there, how many more issues would that cause?

 

[ShinobiAoshi]

I'm not sure if this is a related problem or not but you all seem very well-informed and helpful in this thread, so I'll ask regardless. Lately I've been noticing that Honorbuddy will get focused on a spot, and then proceed to continually run to it, jump, and away for 2 seconds, come back, jump, and then rinse and repeat endlessly. Is this an HB issue, a mesh issue, or a profile issue? If necessary I will provide a log the next time this happens to me.

 

[chinajade]

Lately I've been noticing that Honorbuddy will get focused on a spot, and then proceed to continually run to it, jump, and away for 2 seconds, come back, jump, and then rinse and repeat endlessly.

Its usually better to start you own thread and let people answer when they have knowledge. Hijacking someone's thread is frowned upon.


But since you asked here, I'll take a stab as this has happened to me a couple of times...

Usually its because I have 'mining' or 'herbalism' turned on, and Honorbuddy is trying to get to the node to harvest, but can't figure out a path. The exact behaviour your described is observed. The node is usually located up a steep hill or on a ledge when this happens. If you stop Honorbuddy, go harvest the node manually, then restart Honorbuddy, you'll find the problem 'goes away' (until the node repops).

Why does this happen? The tools used to generate the mesh are imperfect. Sometimes, to get to the harvest you need to 'jump' or fly. Definitely doable by a human, but if jumping or flying is involved, Honorbuddy cannot generate a pathing solution. Thus, it gets as close as it can. Decides it can't do it, and tries the 'jiggle algorithm' to generate an alternate path, and goes back to try the first when it finds that won't work either.

You would think Honorbuddy would blacklist the harvest node after a period of time. Either it doesn't, or my patience is thin enough I always wind up 'helping it out', first.

Edit: One other thing, Blizzard sometimes does naughty things like put a mining node or herb inside a hill or tree. This will have the same effect.


Hope this helps, and cheers,
CJ

 

[ShinobiAoshi]

@ Chinajade, thank you for the quick and informative response, that's precisely when I encountered the problem was when I was trying to level my DK's mining. It is quite frustrating when I leave the bot running for an hour or two, only to come back and realize it's been stuck on one node for an hour (not to mention that behavior looks extremely bottish. And I thought I'd post in this thread since what I was hoping to get to eventually was if there is a way to blacklist that node entirely and not have to worry about it, since after trying the built in "blacklist" feature on HB, it didn't seem to do any good at all.

 

[tubajedimr]

I have blackspots in a profile that are in no way a hinderance to the pathing of Honorbuddy yet Honorbuddy still ignores them anyway. It also isn't avoiding mobs, that are, ironically, IN THE BLACKLISTED AREA. So it's running through mobs I've set to avoid in an area I've set to blacklist which it could EASILY go around. This is not a matter of HB not having a way, it's a matter of it disregarding the code.

 

[MaiN]

Its not really a grind profile. Its just a profile to move from hotspot to hotspot while Autoangler detects pools.

So how about blackspots then? How come when you set them while using HonorBuddy, the bot still goes to the blackspotted area?

The 'Blackspot' button is just a helper button. You have to put blackspots into profiles. For more information, check the Wiki. Also, with an error like "the mesh is corrupt in many places" I'm not even going to attempt to help you.
EDIT: I now see that post is a couple of months old.

I have blackspots in a profile that are in no way a hinderance to the pathing of Honorbuddy yet Honorbuddy still ignores them anyway. It also isn't avoiding mobs, that are, ironically, IN THE BLACKLISTED AREA. So it's running through mobs I've set to avoid in an area I've set to blacklist which it could EASILY go around. This is not a matter of HB not having a way, it's a matter of it disregarding the code.

Without more info we can't determine whether it's a HB bug or a profile error. Can you please post your profile?

 

[Kickazz006]

main, any chance of a "definite blackspot" tag? where it over-rides the bot / mesh

I have blackspots in some buildings and the bot detects mobs through the buildings (ie: tyr's hand in EPL) and ignores the blackspots at the entrances, hell even if I blackspotted the whole building it would ignore it

 

[MaiN]

main, any chance of a "definite blackspot" tag? where it over-rides the bot / mesh

I have blackspots in some buildings and the bot detects mobs through the buildings (ie: tyr's hand in EPL) and ignores the blackspots at the entrances, hell even if I blackspotted the whole building it would ignore it

Blackspots have so high costs to path through that if you ever see the bot go through a blackspot, it's most likely because it doesn't know there is a blackspot. Ie. a profile error or an error in HB.