HB ARCHIVES: Processed Issues from Honorbuddy Release threads

- deleted -

 

Chinajade can you say something to this problem? Because many users got it.

 

Farming a dungeon and Honorbuddy automatically stopped after the run. Character sitting (AFK) in front outside the instance.

See log

 

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

 

Taking mails :

Proffbuddy :
Bot spend 326 sec near mailbox even if there no mails at all.
See log line 841

Buying from AH not working, same as posting. He just scaned AH and closed it.
Line 883

View attachment log.txt

 

wow instantly closes when I start questing. it worked fine with dungeon buddy but on both my computers it crashes on questing.

 

do we know if we are getting an ubrs profile or should i retire my dungeon farmers until wod?

 

MM Hunter Spells/questing

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 6252 2014-10-20 18.07.txt

 

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.

 

Me.CurrentRage?

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 7648 2014-10-20 23.06.txt

 

awe, the Ref is the wrong link

 

Hi!

Thanks for answering me !

This is the WoW log crashing info.

I'm going to link the last couple I had because they were ALL related to HB ...

View attachment 2014-10-19 22.45.47 Crash - 44148.txt
View attachment 2014-10-20 15.31.58 Crash - 7456.txt
View attachment 2014-10-20 22.37.43 Crash - 3540.txt

 

@chinajade

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

 

after update to latest version HB, now HB always use mount! in dungeon too... how to turn it off?
HB use mount in dungeon even distance to next target lower then 200...
please remove it... or say how to remove it manualy
This feature brake my plans.... it couse no errors, at the moment i'm solve it by downgrade my HB to previos version.

 

Misc/RunLua Killing the client plus the HB itself immediately

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 15280 2014-10-21 09.53.txt View attachment 15264 2014-10-21 09.51.txt

 

Did a clean install, ran CCleaner, restarted PC - Same result.

 

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 &amp;&amp; Me.FreeBagSlots &gt;= 20 &amp;&amp; Me.LowestDurabilityPercent &gt;= 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 new 1.txt

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.

 

trash

Dunno if it was already reported :

Code:

[09:55:41.044 D] Activity: Flying to '<-310.4844, 2636.552, 147.8022>' (<-310.4844, 2636.552, 147.8022>)
[09:55:41.060 N] Mounting: Green Wind Rider
[09:55:43.509 N] (Singular) (Singular) info: BehaviorFlags changed to [Death, Combat, Vendor, Roam, Rest, FlightPath] by ProfessionBuddy, Plug-in or Profile
[09:55:45.911 N] (Singular) [WoWRedError] Can't do that while moving
[09:55:45.911 N] (Singular) (Singular) [CombatLog] SPELL_CAST_FAILED Green Wind Rider#32245 failure: 'Can't do that while moving'

Cant mout at first try. Easy to reproduce. Every time he have to mount twice because first try fails "Can't do that while moving"

no log.

 

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.

 

The bot will always pause 5 seconds after interacting a node. Tried disabling all plugins, canceling hardlock, doesn't help.