What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Honorbuddy v2.5.11769.750

Status
Not open for further replies.
Worth "Stone and exit" when bags full. But there is that the bot teleports without waiting for full bags ..... fix it
Hi, Fgame, and thanks for the logs.

Neither one of these logs illustrates Gatherbuddy doing a "Hearth and Exit" due to full bags.

One log is just truncated, and the other log shows Honorbuddy is shut down because the WoWclient exited.

Since neither one of these logs illustrates a problem, there is no bug for us to capture.

cheers,
chinajade


[size=-2]Ref: Fgame's original post w/log[/size]
 
Ill try send one last log if this dosent work i dont know why my log's dont copy everything that happens to him.. This log is under the night. The bot join a battleground and afk to he get kicked out or he join and just run around and auto attack/hit targets he never uses any spells
Hi, Scenix, and thanks for the log.

Please do a "clean install", and install no third-party products.

In particular, it looks like your Combat Routine is not ready for the pre-WoD Honorbuddy. Do not install any third-party product until the author explicitly states it is ready for pre-WoD Honorbuddy.

cheers,
chinajade

[size=-2]Ref: Scenix's original post w/log[/size]
 
Same as previous release - kernel errors.

HB crashes between 1 and 5 mins with a kernel windows error.
Can be any bot base and any activity (even happens when standing doing nothing).
Happens with clean install with all streaming disabled.
Happens with clean install and only kicks streamed.
Using Singular Bot base.

Code:
Faulting application name: Wow.exe, version: 6.0.2.19034, time stamp: 0x543dfddc
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x000006ba
Fault offset: 0x0000c42d
Faulting process id: 0x3568
Faulting application start time: 0x01cfec934f38c81a
Faulting application path: E:\WOW\Wow.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 8330d486-588f-11e4-843c-6805ca2a7b49

Hi, Flyg, and thanks for the kernel error details!

We've added your data point to HB-1306 ("Reports of HB causing WoWclient crash and BSoD").

However, in your case, its the WoWclient causing the crash. Try switching the WoWclient to DX9 mode, and see if the problem persists.

cheers,
chinajade


[size=-2]Ref: Flyg's original post w/log[/size]
 
Farming a dungeon and Honorbuddy automatically stopped after the run. Character sitting (AFK) in front outside the instance.

See log

Hi, DraGoNo, and thanks for the log.

[22:30:49.449 Q] Bot stopping! Reason: Nothing more to do.

It looks like your profile executed as it was supposed to, and "got done". If you do not believe this is correct, please contact the profile's author and allow him to report the specifics of the problem he observes.

cheers,
chinajade


[size=-2]Ref: DraGoNo's original post w/log[/size]
 
WoW closes when trying to interact with "Eimer mit Süßigkeiten" (Candy Bucket), which has already been used.

This was working in 2.5.11724.749

Already reported here: https://www.thebuddyforum.com/releases/182907-honorbuddy-v2-5-11769-750-a-2.html#post1680665
wow instantly closes when I start questing. it worked fine with dungeon buddy but on both my computers it crashes on questing.

Hi, all,

First, let's reboot the machine.

Second, let's clearing the caches:

If no joy, let's try switching the WoWclient to DX9, then relaunch the WoWclient before launching Honorbuddy.

cheers,
chinajade


[size=-2]Ref: Cataphract's original post w/log[/size]
[size=-2]Ref: WTB A Noob's original post w/log[/size]
 
I have noticed that MM hunter will not use Chimaera Shot, Just uses rotation ( Steady Aim, Aimed Shot ) no Kill Shot ( I think i see it uses Kill shot at times) or any buffs (Rapid Fire, Stampede). I hope this helps! I attached log, Questing[Kicks] ( thank you Kicks awesome profiles you have) seems to work fine just a few hic ups here and there pause and do the quest or close the cinematic when it doesn't do it.

Edit: also seems to try and hurry and accept quest givers quest and opens and closes it before it accepts but ends up accepting it after a couple trys

View attachment 147035

Hi, RyanD,

As stated in the '.750 Known Bugs List, we are not collecting reports against Singular. We just need to give Bobby53 time to catch up. All Combat Routine authors have been hit really, really hard by the pre-WoD changes.

cheers,
chinajade


[size=-2]Ref: RyanD's original post w/log[/size]
 
Hi!

So this is my second post on the Test Release issues.

What ever I try to do with HB, it crashed my WoW in 3 minutes or less.

Here is my last log and a screenshot of the error.

Tauren
Paladin
Level 90
Protection
Using Singulair
Raid Bot (But wich ever bot i'm using, it crashes)

Note: I did 4 fresh install and also cleared my cache twice (as mentionned in the thread how to clear cache) and rebooted my system 3 or 4 times now.
Hi, Melcekial, and thanks for this info!

We've added this data point to HB-1306 ("Reports of HB causing WoWclient crash and BSoD "). But to chase problems like this, we really need the WoWclient crash report (its a .txt file in the WoW directory).

If the problem happen again for you, please include the WoWclient crash report in addition to the screenie and log you've already shown us.

thanks!
chinajade


[size=-2]Ref: Melcekial's problem report w/log[/size]
 
Hi there, Altec here, once again - well not here once again for the test release, once again for another posting. Anywho, I have an issue with Me.CurrentRage. I'll upload the logfile, but here is a shorthand of the issue:

Code:
[04:07:24.985 N] 07:24:985 - Rage: 86 - Enemy HP: 100% @ 4 m - Casting: Devastate!
[04:07:26.050 N] 07:26:050 - Rage: 90 - Enemy HP: 100% @ 4 m - Casting: Devastate!
[04:07:27.517 N] 07:27:517 - Rage: 96 - Enemy HP: 100% @ 4 m - Casting: Shield Slam!
[04:07:27.875 N] 07:27:875 - Rage: 397 - Enemy HP: 100% @ 4 m - Casting: Heroic Strike!
[04:07:28.733 N] 07:28:733 - Rage: 400 - Enemy HP: 100% @ 9 m - Casting: Devastate!
[04:07:29.164 N] 07:29:164 - Rage: 401 - Enemy HP: 100% @ 8 m - Casting: Heroic Strike!
[04:07:29.341 N] 07:29:341 - Rage: 402 - Enemy HP: 100% @ 7 m - Casting: Devastate!
[04:07:29.547 N] 07:29:547 - Rage: 403 - Enemy HP: 100% @ 6 m - Casting: Heroic Strike!
[04:07:29.716 N] 07:29:716 - Rage: 403 - Enemy HP: 100% @ 6 m - Casting: Devastate!
[04:07:29.918 N] 07:29:918 - Rage: 404 - Enemy HP: 100% @ 6 m - Casting: Heroic Strike!
[04:07:30.095 N] 07:30:095 - Rage: 405 - Enemy HP: 100% @ 6 m - Casting: Devastate!
[04:07:30.309 N] 07:30:309 - Rage: 405 - Enemy HP: 100% @ 6 m - Casting: Heroic Strike!
[04:07:30.483 N] 07:30:483 - Rage: 406 - Enemy HP: 100% @ 6 m - Casting: Devastate!
[04:07:30.683 N] 07:30:683 - Rage: 407 - Enemy HP: 100% @ 6 m - Casting: Heroic Strike!
[04:07:30.858 N] 07:30:858 - Rage: 407 - Enemy HP: 100% @ 6 m - Casting: Devastate!

Clearly, the bot thinks that Me.CurrentRage is higher then any possible max rage allowed for warriors - don't get me wrong, I'd love to have 400+ rage at anytime. The log output is as follows:

Code:
if (SpellManager.CanCast(spellName, u))
                {
                    iCR = Me.CurrentRage;
                    SpellManager.Cast(spellName, u);
                    StyxWoW.SleepForLagDuration();
                }
                else { return; }
if (LastCastUnit != u || LastCastSpell != spellName || LastCastTime + TimeSpan.FromMilliseconds(500) < DateTime.Now)
                {
                    Logging.Write(Lc, "{0} - Rage: {1} - Enemy HP: {2}% @ {3} m - Casting: {4}!", DateTime.Now.ToString("mm:ss:fff"), iCR, Math.Round(u.HealthPercent), Math.Round(u.Distance), spellName);
                }
                else { return; }

Thoughts?

View attachment 147056
Hi, Altec, and thanks for all those details.

We've opened HB-1338("HB API reporting inappropriate LocalPlayer.CurrentRage values") against the issue.

cheers,
chinajade


[size=-2]Ref: Altec's problem report w/log[/size]
 
@chinajade

Still no workee. Changed DX to 9, cleared HB and WoW caches. Nothing.
Hi, Cataphract,

Thanks for trying all that. I'm at a loss on this one other than to say something is seriously not right with your machine/installation.

[06:23:54.390 N] (Singular) -22.7 days since Windows was restarted

k, this is a time in the future. Very bad.

[Ref: "UnknownProfile" @line 59]

We've no clue what profile we're running.

At this point, all I've got for you is to suggest a "clean install":

cheers,
chinajade


[size=-2]Ref: Cataphract's original post w/log[/size]
 
Hi, Melcekial, and thanks for this info!

We've added this data point to HB-1306 ("Reports of HB causing WoWclient crash and BSoD "). But to chase problems like this, we really need the WoWclient crash report (its a .txt file in the WoW directory).

If the problem happen again for you, please include the WoWclient crash report in addition to the screenie and log you've already shown us.

thanks!
chinajade


[size=-2]Ref: Melcekial's problem report w/log[/size]
Hi, Melcekial,

Just a follow-up with info from MaiN...

HB-1306 has been closed as "Won't fix" with the following message:
"The WoW crash log contains no traces of anything Honorbuddy would touch, but it contains a DLL that I have seen on previous reports of crashes (4-5 reports in 5 months): rlls.dll. This is some spyware:
http://deletemalware.blogspot.dk/2011/04/remove-relevant-knowledge-uninstall.html"

After explicitly addressing the "Relevant Knowledge" spyware, you may also want to run a Spyware-detection tool, like:
Spybot - Search & Destroy (we are not endorsing this product)
or another one​

cheers,
chinajade
 
Last edited:
Hello!
I just run an empty profile with "UseItemByName(0000)" and my client+HB getting critical and closes immediately.
Here's is my log files for that issue.
View attachment 147076View attachment 147077
Did a clean install, ran CCleaner, restarted PC - Same result.

Hi, All,

We've opened HB-1342 to monitor this situation. Whenever the WoWclient crashes, we'll need you to also attach the WoWclient crash log (a .txt file in the WoW directory).

You should also thoroughly check your computer for Spyware.

cheers,
chinajade


[size=-2]Ref: FadetoGrey's original post w/log[/size]
[size=-2]Ref: Cataphract's original post w/log[/size]
 
Last edited:
PB + Grind bot :

Grind profile :
<MinDurability>0</MinDurability>

But bot ignoring Durability option and trying to repair even if repear NPC not set in profile.

[07:58:35.724 N] ::::::::: LowestDurabilityPercent is 0.24
[07:58:35.802 D] Updating repair cost for current equipped items. New value: [49g82s68c]
[07:58:35.849 D] Activity: Loading Tiles
[07:58:35.849 D] Loading HawaiiMainLand_29_28
[07:58:36.098 D] [Mount] Flying Carpet is known, but we don't have the skill to use it!
[07:58:36.098 D] [Mount] Flying Machine is known, but we don't have the skill to use it!
[07:58:36.114 D] [Mount] Frosty Flying Carpet is known, but we don't have the skill to use it!
[07:58:36.176 D] [Mount] Magnificent Flying Carpet is known, but we don't have the skill to use it!
[07:58:36.301 D] [Mount] Turbo-Charged Flying Machine is known, but we don't have the skill to use it!
[07:58:36.348 D] Changed POI to: Type: Repair, Name: Merchant Tantan
[07:58:36.379 N] Moving to Type: Repair, Name: Merchant Tantan

( tested <MinDurability>0.1</MinDurability>, still ignoring )

P.S
In my PB profile repair set to 0.2
Code:
    <If Condition="Me.MapId == 870 && Me.FreeBagSlots >= 20 && Me.LowestDurabilityPercent >= 0.20" IgnoreCanRun="False />
but bot trying to repair at 0.24, he just run to closest repear NPC. ( even it not set in grind profile )

Since PB monitoring his grind position, and moves him back if he to far from start point..... its dead end.

View attachment 147081

UPDATE :

Moved

<MinDurability>0</MinDurability>
<MinFreeBagSlots>0</MinFreeBagSlots>

to top line ( just after <HBProfile> tag ) and now it works. Before it was inside <GrindArea> tag.

Hi, DevAnse,

Indeed, the profile was what was in error. The <Min*> tags have never been supported inside a GrindArea.

cheers,
chinajade


[size=-2]Ref: DevAnse's original post w/log[/size]
 
Bot broken:
txt
Hi again, Unk2, and thank you for the log.

Even with a log, "Bot broken" is not enough information with which to write up a report. What are your observations? Was the toon moving to the hotspots where the quest mobs were located on the map? Were there any mobs at those locations?

cheers,
chinajade


[size=-2]Ref: Unk2's log[/size]
 
Running ArchaeologyBuddy for a whole, when toon was close to the point, it will try digging near place without pausing, which will fail by GCD. Then the toon will circle around since it can never succeed in digging at that point.

Hi, Ksmaze, and thank you for log.

We've opened HB-1346 ("ArcheologyBuddy failing for Druid") against this issue.

cheers,
chinajade


[size=-2]Ref: Ksmaze's problem report w/log[/size]
 
Archeologybuddy worked for me. Learned arch. in Ogrimmar and fired up the bot which flew straight to the closest dig site and finished the excavation there (see attached log). Only did a single test, since the toon had just hit lvl60 and lowspeed flying sucks. ;)

But... Questing in BC using the profile pack from the Buddy store does not work/start. Once hitting 60 I ported to Ogrimmar, learned how to fly and took the portal to the burning crusade starting area. Fired up the bot which just sat there, having path finding issues (see attached log).

View attachment 147145

Hi, Sea, and thank you for the log.

This log makes absolutely no sense. It looks like there are Navigational/Mesh errors being encountered before the profile starts executing. I can't imagine why that would happen unless Honorbuddy was trying to go reclaim your corpse.

You might try clearing your caches.

This doesn't appear to be a bug with Honorbuddy, but something awry with your installation.

cheers,
chinajade

[size=-2]Ref: Sea's original post w/log[/size]
 
The SwitchCharacter command is not working in PB. This issue appeared sometime before the last WoW patch, but I never saw an issue created to track it.


Log:
View attachment 147159

The last two lines are just log messages from a profile before calling the SwitchCharacter command.
Hi, TreeK, and thanks for the log.

We've opened HB-1347 ("ProfessionBuddy not switching characters successfully") against this issue.

cheers,
chinajade


[size=-2]Ref: TreeK's problem report w/log[/size]
 
I have bags full cost mode and teleport. But the bot uses teleport without waiting for the full shopping bags. Previously, it was good. it appeared only in the new Hb. please correct it

logs attached
Hi, Fgame, and thank you for the log.

Once again, these logs DO NOT show Gatherbuddy2 "Hearthing and Exiting".

Perhaps it is one of your plugins that have been mis-configured:
[13:12:28.724 D] theTramper gather
[13:12:28.724 D] rndbuddy

Please do a "clean install" as described in the article below. Add NO third-party products. Repeat the problem using JUST the "clean install"—no third-party anything. Then show us the log of the problem from the "clean install".

cheers,
chinajade


[size=-2]Ref: Fgame's original post w/log[/size]
 
thanks. just tried dx9 and got about 5mins like usual before a crash.

Code:
Faulting application name: Wow.exe, version: 6.0.2.19034, time stamp: 0x543dfddc
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x000006ba
Fault offset: 0x0000c42d
Faulting process id: 0x26a4
Faulting application start time: 0x01cfed646d7c5dd6
Faulting application path: E:\WOW\Wow.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cddbc0ac-5958-11e4-9712-6805ca2a7b49

If I play manually and don't use HB game runs fine for hours and never crashes.
Hi, Flyg,

Try doing a "clean install"—no third-party products—and repeat the problem. If the problem does not manifest, its a third-party product interaction.

MaiN has also suggested Spyware can cause WoWclient crashes (and has captured several internal examples to prove it). You should also run a Spyware detection and removal tool.

And one last thing, I've personally had problems with BitDefender in 'aggressive' settings monitoring wireless connections. It could be your AV interfering, and you may want to look into that also.

At this time, we do not believe this to be an Honorbuddy bug, but interference from an external program. See HB-1306 in the '.750 Known Bugs List.

cheers,
chinajade

[size=-2]Ref: Flyg's original post w/log[/size]
 
Status
Not open for further replies.
Back
Top