[Stable] Honorbuddy 1.9.5.2 - Skinning fix

[Hawker]

I know that PVP botting is more of a risk, all I am saying is fix/improve the basic bot (walking, fight, and so) before working on other thing. What is the point of skinning if other players think you are a bot?

Most of the reports are random. All we really know is that they monotor the number of mobs of 1 type you kill, the number of nodes of 1 type you harvest and if you are running too few or too many auctions. In your case, its pretty clear why you got banned.

[FONT=Calibri][FONT=Tahoma][SIZE=2]7)How many auctions per day did you have?:
0

You really need to run auctions. Only bots go weeks with no auctions from the account and a lot of bans are caused by that. It worth saying that people running 100s of daily auctions almost never get banned.
[/SIZE][/FONT][/FONT]

 

[Nebon0]

I have to say you guys are really doing an awesome job. Definitely worth my 25 euros!

 

[Funtimes]

Is it intended that our level 80's will stop and kill *every* *Single* mob that aggros them. I mean damn, my guy spends more time casting lightning bolt on level 10 wolves while he farming some copper then he does mounted moving to the next node. There should be some sort of code or checkbox to ignore mobs while mounted. This would enable us to keep moving, and farming and just let the damn things de-agro.

-Utilizing HB2 to farm low level ore, keeps fighting grey npc who are of no threat or affect to his herb / mining. Character also keeps running out of combat, instead of mounting up. Attaching log

 

[Nesox]

Is it intended that our level 80's will stop and kill *every* *Single* mob that aggros them. I mean damn, my guy spends more time casting lightning bolt on level 10 wolves while he farming some copper then he does mounted moving to the next node. There should be some sort of code or checkbox to ignore mobs while mounted. This would enable us to keep moving, and farming and just let the damn things de-agro.

-Utilizing HB2 to farm low level ore, keeps fighting grey npc who are of no threat or affect to his herb / mining. Character also keeps running out of combat, instead of mounting up. Attaching log

We do have logic for that, altho it does't seem to work for you.
Please use the bugtracker to report it and i will take ? look at it when i get home.

 

[brampower]

Is it intended that our level 80's will stop and kill *every* *Single* mob that aggros them. I mean damn, my guy spends more time casting lightning bolt on level 10 wolves while he farming some copper then he does mounted moving to the next node. There should be some sort of code or checkbox to ignore mobs while mounted. This would enable us to keep moving, and farming and just let the damn things de-agro.

-Utilizing HB2 to farm low level ore, keeps fighting grey npc who are of no threat or affect to his herb / mining. Character also keeps running out of combat, instead of mounting up. Attaching log

I'm looking for this too!

 

[Nesox]

I'm looking for this too!

Report the issue on the bugtracker ty.

 

[lawr0155]

Wow guys nice job, skinning working perfect now. I have zero issues with grinding bot right now! Would love to see buying from vendors included in the core program,

 

[Ssateneth]

1.9.5.2 still exhibits the "do nothing after looting" bug, which I've reported in 1.9.5.1 and 1.9.5.0, so I guess I'll copy paste my problem as usual in hopes of it getting fixed.

I'm still getting problems where the bot will just stand there and do nothing when it should be pulling. The last line is Activity: Looting Mosshide Mongrel (new in 1.9.5.2: last lines in log may be "Interacting with lootable Mosshide Gnoll | LootTargeting.LootFrameIsOpen | Lootable isn't lootable...blacklisting." and the bottom says "Activity: Combat"). It won't do anything til something respawns close enough that it triggers something in HB to initiate another pull, or a respawn causes a body pull. Same bug as in 1.9.5.0 [and 1.9.5.1]. Was really hoping this bug would've been fixed, but my previous bug submission appears to not been looked at.

The bug occurs at...
[3:37:47 PM:600] Changed POI to: Type: None, Loc: <0, 0, 0>
[3:43:31 PM:316] Changed POI to: Type: Kill, Name: Mosshide Mongrel
in the log. It also occured at the end but there is no log when you force a stop on HB for some reason.

bug report: http://bugtracker.buddyforum.de/viewissue.php?issue_no=60

I will teamview/vnc/remote desktop/whatever so you guys can actually see the bug happening..

 

[peakaboo]

I would like to see a Hb more user friendly in the authenticating.Would like it to give a reason before shutting down, at least in some normal/ frequent situations.

As tonight my honour buddy was running all day , i was tired when i got home so i took a nap, and well i woke up and decide to check on bot , and well i could not get it to work, was very paranoid at first. I then checked forums and saw a post Tony had replied to with update the client of Hb. Which solved my problem.

 

[Nesox]

1.9.5.2 still exhibits the "do nothing after looting" bug, which I've reported in 1.9.5.1 and 1.9.5.0, so I guess I'll copy paste my problem as usual in hopes of it getting fixed.



The bug occurs at...
[3:37:47 PM:600] Changed POI to: Type: None, Loc: <0, 0, 0>
[3:43:31 PM:316] Changed POI to: Type: Kill, Name: Mosshide Mongrel
in the log. It also occured at the end but there is no log when you force a stop on HB for some reason.

bug report: http://bugtracker.buddyforum.de/viewissue.php?issue_no=60

I will teamview/vnc/remote desktop/whatever so you guys can actually see the bug happening..

You can't expect the bot to move when you only have one hotspot defined in the profile...
I made a comment and closed the issue on the bugtracker.

<SubProfile>
    <Name></Name>
    <MinLevel>0</MinLevel>
    <MaxLevel>81</MaxLevel>
    <Factions>61</Factions>
    <GrindArea>
      <RandomizeHotspots>true</RandomizeHotspots>
      <LootRadius>50</LootRadius>
[B]      <Hotspots>
        <Hotspot X="-4064.216" Y="-2977.912" Z="11.75293" />
      </Hotspots> [/B]
    </GrindArea>
    <Vendors>
    ...
</subProfile>

Once it reaches the hotspot it won't be able to dequeue and get the next one because there are too few hotspot and simply get stuck.
Sure it will kill evrything that comes into the pull distance of where ure standing but i'd say that's not a very efficent way of farming

 

[Hawker]

1.9.5.2 still exhibits the "do nothing after looting" bug, which I've reported in 1.9.5.1 and 1.9.5.0, so I guess I'll copy paste my problem as usual in hopes of it getting fixed.



The bug occurs at...
[3:37:47 PM:600] Changed POI to: Type: None, Loc: <0, 0, 0>
[3:43:31 PM:316] Changed POI to: Type: Kill, Name: Mosshide Mongrel
in the log. It also occured at the end but there is no log when you force a stop on HB for some reason.

bug report: http://bugtracker.buddyforum.de/viewissue.php?issue_no=60

I will teamview/vnc/remote desktop/whatever so you guys can actually see the bug happening..

As I told you earlier, you need more than 1 hotspot.

 

[Ssateneth]

As I told you earlier, you need more than 1 hotspot.

Oh. I didnt get the message. I'll do that then I spose. Will update. Reason why I only had 1 hotspot is because mobs will instantly respawn within that same camp if theres only 1 or 2 left. I didn't realize that there was some sort of limitation that you had to have more than 1 hotspot. Sorry.

edit: ok I added another hotspot about 100 yards south into another gnoll camp and its still doing the bug. It has a gnoll targeted not even 10 yards away and the bot is just standing there doing nothing. Yes I made sure to save the new hotspot in the xml.
another edit: i deleted the randomize hotspots part of the profile + reuploaded. Bug happened again 15 kills in. has a gnoll targeted 10 yards away and the bot just does nothing.

I never got this bug in the versions before 1.9.5.0 and it readily chugged along all night with 1 hotspot at about 500 kills/hour; although the "running away after killing something and running back to loot it" bug was annoying, it didn't make the bot completely stop doing everything. Also I did manage to confirm that the bug happens with default paladin cc and convalesence paladin cc.

I've added a third hotspot and decreased pull distance from 40, then 30, then 20 yards. Any less and it wont really pull anything anyways, still get the bug. I'll paypal $50 if a dev -works with me- on this instead of just dismissing this bug as usual. You know, communicate. It -HAS- to be a problem with honorbuddy because, like I said, the versions BEFORE 1.9.5.0 worked perfectly fine (aside from running away from killed mob then back to loot it bug) with the original 1 hotspot profile.

yet another edit: someone thought that the class was bugged, so I got on my 66 rogue and did the same area. The rogue did the exact same "do nothing" bug with both 1 hotspot and 3 hotspots. It works just fine on 1.9.4.5 aside with the aformentioned not-so-annoying loot bug.

also another thing I noticed. when my bot is bugged, which is doing nothing while having a live mob targeted, it will stop being bugged if another mob gets closer than the one than you are currently targeting, either from a respawn or a patrol, and go towards it to kill it, loot it, and continue until the bot bugs again. also, like I said, the 1 hotspot profile worked fine before because those mobs instantly respawn if their numbers in that small area (usually 40 yards or closer from the center) reach 1 or 2 left. I could hand play it and kill the mobs faster than another person can loot them because they respawn just as fast as you can kill them.

another: its not the computer. my computer is W7 ultimate x64 with 4 core intel, 4gb ram, ati 5870, 6 drive raid, water cool, and i could replicate the bug on a computer that never seen HB before that was an old 2-core amd, 2gb ram, nvidia 8800, 500gb drive, air cool with fresh HB downloaded right from this website. someone thought again that it was how i made the profile, so i made a lvl 1 rogue (default cc, same as the one that got the "do nothing" bug on my 66 rogue in wetlands farming gnolls) and used the same wool profile but just copy pasted the right faction and 3 hotspots with looting enabled. i didnt get the "do nothing" bug so it either has something to do with those specific mobs that im farming in wetlands or the abilities available to my class. the lvl 1 wyrms in silvermoon seem to have instant respawn too just like the gnolls in wetlands

 

[Zher0]

Thanks for the quick fixes.

 

[R@D]

It worth saying that people running 100s of daily auctions almost never get banned.

This is true as far as i can tell, on my main i have botted for like 38H non stop afew times (rep farming) and never got baned but i did get a ban on a chaar that i was leveling 2 80 as a grind machine on a other account and got a ban in 4H, running a grinding profile (so it was killing the same kind of mob over and over again).

 

[Nab]

Awesome release, thanks! The fix of the skinning bug really boosted my xp / hour aswell

 

[Nesox]

Oh. I didnt get the message. I'll do that then I spose. Will update. Reason why I only had 1 hotspot is because mobs will instantly respawn within that same camp if theres only 1 or 2 left. I didn't realize that there was some sort of limitation that you had to have more than 1 hotspot. Sorry.

edit: ok I added another hotspot about 100 yards south into another gnoll camp and its still doing the bug. It has a gnoll targeted not even 10 yards away and the bot is just standing there doing nothing. Yes I made sure to save the new hotspot in the xml.
another edit: i deleted the randomize hotspots part of the profile + reuploaded. Bug happened again 15 kills in. has a gnoll targeted 10 yards away and the bot just does nothing.

I never got this bug in the versions before 1.9.5.0 and it readily chugged along all night with 1 hotspot at about 500 kills/hour; although the "running away after killing something and running back to loot it" bug was annoying, it didn't make the bot completely stop doing everything. Also I did manage to confirm that the bug happens with default paladin cc and convalesence paladin cc.

I've added a third hotspot and decreased pull distance from 40, then 30, then 20 yards. Any less and it wont really pull anything anyways, still get the bug. I'll paypal $50 if a dev -works with me- on this instead of just dismissing this bug as usual. You know, communicate. It -HAS- to be a problem with honorbuddy because, like I said, the versions BEFORE 1.9.5.0 worked perfectly fine (aside from running away from killed mob then back to loot it bug) with the original 1 hotspot profile.

yet another edit: someone thought that the class was bugged, so I got on my 66 rogue and did the same area. The rogue did the exact same "do nothing" bug with both 1 hotspot and 3 hotspots. It works just fine on 1.9.4.5 aside with the aformentioned not-so-annoying loot bug.

also another thing I noticed. when my bot is bugged, which is doing nothing while having a live mob targeted, it will stop being bugged if another mob gets closer than the one than you are currently targeting, either from a respawn or a patrol, and go towards it to kill it, loot it, and continue until the bot bugs again. also, like I said, the 1 hotspot profile worked fine before because those mobs instantly respawn if their numbers in that small area (usually 40 yards or closer from the center) reach 1 or 2 left. I could hand play it and kill the mobs faster than another person can loot them because they respawn just as fast as you can kill them.

another: its not the computer. my computer is W7 ultimate x64 with 4 core intel, 4gb ram, ati 5870, 6 drive raid, water cool, and i could replicate the bug on a computer that never seen HB before that was an old 2-core amd, 2gb ram, nvidia 8800, 500gb drive, air cool with fresh HB downloaded right from this website. someone thought again that it was how i made the profile, so i made a lvl 1 rogue (default cc, same as the one that got the "do nothing" bug on my 66 rogue in wetlands farming gnolls) and used the same wool profile but just copy pasted the right faction and 3 hotspots with looting enabled. i didnt get the "do nothing" bug so it either has something to do with those specific mobs that im farming in wetlands or the abilities available to my class. the lvl 1 wyrms in silvermoon seem to have instant respawn too just like the gnolls in wetlands

I've been running your profile for a while now and it's not a problem with the profile.
The bot doesn't set the poi to kill for w/e reason, I'm gonna debug it more tomorrow.
Sorry if we didn't believe you but at first glaze it looked like a profile issue.
Will be fixed in the next release on Friday~

Edit: Its most likley because you one shot then loot and the rapid respaw time that is causing it, nontheless it shouldn't do that.. Ta

 

[theholyone]

will there be any RaF updates for HB2?

 

[Ssateneth]

I've been running your profile for a while now and it's not a problem with the profile.
The bot doesn't set the poi to kill for w/e reason, I'm gonna debug it more tomorrow.
Sorry if we didn't believe you but at first glaze it looked like a profile issue.
Will be fixed in the next release on Friday~

Edit: Its most likley because you one shot then loot and the rapid respaw time that is causing it, nontheless it shouldn't do that.. Ta

It took some effort but I finally got through. Looking forward to it. Probably explains why the lowbie didnt get that problem. The rogue didnt get it as much because his gear sucks, but it would make sense. Thank you.

 

[w00tsauce]

Seems to be working pretty good. Im still having the same issues as I had with 1.9.5.1.

When running a herb/mining script, if it runs by a mob that aggros me, then it instantly stops and begins fighting it. Before 1.9.5.1 it would just continue running since I was always able to outrun mobs. I have "kill between hotspots" UNchecked.

 

[Funtimes]

Seems to be working pretty good. Im still having the same issues as I had with 1.9.5.1.

When running a herb/mining script, if it runs by a mob that aggros me, then it instantly stops and begins fighting it. Before 1.9.5.1 it would just continue running since I was always able to outrun mobs. I have "kill between hotspots" UNchecked.

I reported this earlier, nesox said he would look at; however, I have not heard back. It is also on the bug tracker. I am glad to hear im not the only one, makes it easier to troubleshoot for them I imagine.