HB ARCHIVES: Honorbuddy Profile Pack--DO NOT DELETE!

Hi, Tumbum, and many thanks for the logs and screenshots.

Here is the problem:

[13:46:23.305 D] Changed map(s) to StormwindGunshipPandariaStartArea, Azeroth
[13:46:23.360 D] Activity: Waiting for port 1s
...
[13:46:27.884 D] Changed POI to: Type: Fly, R: Learn
[13:46:28.016 N] Moving to Type: Fly, R: Learn​

Honorbuddy decides to immediately go learn the wingstop upon arriving in Twilight Highlands. This action throws off the MyCTM directives and causes Honorbuddy to get irrecoverably stuck, so MyCTM terminates the profile.

We should have this problem repaired in v3133.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log and screenshot[/size]

 

Hi, Tumbum, and thanks for the log and screenshot.

After looking at the way the quest is instrumented in the profile, it needs to be completely redone. There is no way we an make a blind fix for this kind of problem, so we've captured your issue to Known Bugs List: Cata 80-85.

cheers & thanks,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]

 

Hi, Tumbum, and thanks for another report,

In v3134, we have switched out pursing the goal from UseItemOn (which is deprecated and unreliable) to InteractWith. We believe this will rectify the issue.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log and screenshot[/size]

 

Hi again, Tumbum,

This looks like another issue with usage of the deprecated UseItemOn behavior. In v3135, we've switched the mechanics to InteractWith.

The quest may still be somewhat unpredictable since it occurs in the water.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log and screenshot[/size]

 

Hi, Bazzer,

The first few posts of this thread contain all the information you need to download, and start using the profile pack. Please be sure to read all the front matter. It contains a wealth of information to make your journey smooth.

cheers,
chinajade

 

Hi, Tumbum, and thank once again.

This set of quests has multiple issues, and there is no way we can address this with a blind fix. As such, we've recorded the issue to Known Bugs List: Cata 80-85.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]

 

Hi, Ash23,

Thank you for the report, but we are unable to act without the full log that captures the issue. In the future, please don't forget to include it.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, Tumbum, and thanks once again for the log and screenshot!

The profile was trying to get clever and pursue the goals of Total War and War Forage in parallel. Unfortunately, the profile did not instrument the solution for this correctly. In v3136, this has been corrected.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log and screenshot[/size]

 

Hi, Oresal,

What you ask is equivalent to pursuing the Loremaster achievement. You can find more information about how to get as close to that as possible in this article:

HelpDesk: Questing profiles and the Loremaster achievement​

cheers,
chinajade

 

Hi, Tumbum, and thanks again.

In v3137, we've added the Thundermar War Gryphon to the AvoidMobs list. This should prevent future problems with them.


As far as the Untamed Gryphon, we believe what you observed. Unfortunately this log doesn't appear to reflect the issue:

[16:29:56.631 D] Goal: Collect Fresh Gryphon Carcass x 1
[16:29:56.656 D] Changed POI to: Type: Hotspot, Loc: <-3909.546, -5235.441, 23.92769>
..
[16:29:56.808 D] Changed POI to: Type: Kill, Name: Untamed Gryphon
[16:29:56.907 N] (Singular) YourCurrentTarget: changed to: Untamed Gryphon.5B54 h=100.0%, maxh=70946, d=23.6 yds, box=2.6, trivial=False, player=N, attackable=Y, neutral=Y, hostile=N, entry=46158, faction=15, loss=Y, facing=Y, blacklist=N, combat=N, IsBotPoi=Kill, TargetIndex=1
[16:29:57.034 N] (Singular) <<< PULL >>> CurrentTarget now: Untamed Gryphon.5B54 h=100.0%, maxh=70946, d=23.7 yds, box=2.6, player=N, hostil=N, faction=15, loss=Y, face=Y, agro=N, pagro=N, IsBotPoi=Kill, TargetIndex=1
[16:29:57.037 N] (Singular) .... [Pull] h=100.0%/m=100.0%, fury=200, metamor=False, mcore=0, darksoul=False, aoecnt=0, enemy=100% @ 23.7 yds, face=Y, loss=Y, corrupt=0, doom=0, shdwflm=0, ttd=-1
[16:29:57.038 N] [Singular] [Pet] Casting Attack
[16:29:57.039 N] [Singular] [Pet] Casting Attack
[16:29:57.040 N] [Singular] [Pet] Casting Wrathstorm
[16:29:57.042 N] [Singular] Casting Corruption on Untamed Gryphon.5B54 @ 100.0% at 23.7 yds
...
[16:30:09.952 N] (Singular) [WoWRedError] Your target is dead
[16:30:09.952 N] (Singular) [CombatLog] SPELL_CAST_FAILED Shadow Bolt#686 failure: 'Your target is dead'​

The log shows Honorbuddy issuing the Kill directive against the Untamed Gryphon. In in less than half a second, Singular has issued attack command for your pet, and your toon. The target is dead within 13 seconds.

There is nothing the profile can do to address this problem. Please post again, if you see Singular fail to pull a yellow-named mob.


[EDIT 23-Feb-2014 by chinajade]: The AvoidMob will also handle this report, Tumbum.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]
[size=-2]Ref: Tumbum's Thundermaw War Gryphon problem[/size]

 

Hi Tumbum, and thanks once again.

Bliz had changed this quest slightly, and the dragon carcass is now handed to you as part of the quest (rather than having to fetch it yourself). This made an <Objective> no longer necessary, and resulted in the roaming behavior you observed.

We've repaired the problem in v3139.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]

 

Hi, Tumbum,

This is a problem with the KillUntilComplete behavior. We've opened HB-515 ("KillUntilComplete has LoS issues") against the issue.

cheers & thanks again!
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]

 

Hi, Ludiboris,

If you need assistance, we must have the full log that captures the issue. Please see the guide for Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Tumbum, and thanks for the logs and screenshots.

There were a number of problems with the handling of these quest turnins and pickups. We believe the problems to be rectified in v3141.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]

 

Hi, Threlk1984,

All botting activity involves risk. If you are not willing to lose your accounts, you should not be botting.

With that said, Questing is one of the lowest risk activities for botting.

cheers,
chinajade

 

[ProfileCompatibilityInfo-v1232(warning)] PROFILE COMPATIBILITY WARNINGS:
* Ground mount (Серый кодо) is not known to Honorbuddy. Spelling error? ItemId instead of SpellId? Mount not available on this account? No skill to use mount? Please configure ground mount correctly.
Flying mount (Зеленый вертокрыл) is not known to Honorbuddy. Spelling error? ItemId instead of SpellId? Mount not available on this account? No skill to use mount?Please configure flying mount correctly.
after 4 hours , bot crashed with this problem < sry for bad english

 

Hi, Tumbum,

We've captured the issue to Known Bugs List: Cata 80-85. This is going to take some serious consideration, and possibly a unique quest behavior to solve the problem.

In v3142, we've removed the attempt to solve the problem, and replaced it with a UserDialog. This means the quest will need to be done manually. This is how the Alliance-side has handled this problem for quite a while.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log and screenshot[/size]

 

Hi, Tumbum,

We've attached your log, and this post, as supplemental information to HB-489 ("The 28758-TwilightHighlands-BattleofLifeandDeath.cs QB does not address mobs attacking from behind").

cheers,
chinajade


[size=-2]Ref: Tumbum's additional log & screenshot[/size]

 

Hi, Tumbum, and thanks for the log and screenshot.

Thank you for confirming that Obsidia is not instanced (i.e., MobId is always 47929).

The failure mode this time, is quite different than last time. Last time, your Honorbuddy couldn't even "see" Obsidia. This time, Honorbuddy sees her, but instead chooses to run off and spank some lesser mobs nearby.

We've made some changes in v3143 that will hopefully prevent the toon from running off until Obsidia can be dealt with.

cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]
[size=-2]Ref: Our original response to Tumbum regarding this problem[/size]

 

Hi, Tumbum, and thanks for the log and screenshot!

Your problem as a bug in FlyTo that was repaired in http://www.thebuddyforum.com/archives/149952-honorbuddy-v2-5-9752-725-a.html.

HB-483 ("FlyTo should no longer get stuck trying to pursue a previously set POI, once the behavior starts.")​

Honorbuddy revisions have bumped twice since this log was made?time to update again! <smiles>


cheers,
chinajade


[size=-2]Ref: Tumbum's problem report w/log & screenshot[/size]