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

Hi, Jazzman170, and many thanks for the log!

[20:15:38.771 D] [InteractWith-v1538(debug)] No viable mobs in area.
Excluded Units:
Pearlfin Aqualyte [InCompetition(1 players within 20.0, expires in 89s)]

[Ref: "[A - Quest] 85-86 The Jade Forest [Kick] ($Rev: 3301 $)" @line 1342]​

It looks like there were other players in the area while you were doing this quest. The behavior tries to "play nice", and not steal quest mobs near other players. As a result, this may have ruled out several of the mobs that otherwise could've been used to complete the quest. This conservative strategy keeps you from getting whispered at and 'reported' while questing.

As implied by the log, after 90s of waiting, you would've gone ahead and used the quest mob even if the other player was still in the area. This keeps us from getting 'gummed up' when other players are AFK, or not on the same quest.

In short, we believe things would've worked out fine for you, if you'd just been a little more patient.

cheers,
chinajade


[size=-2]Ref: Jazzman170's original post w/log[/size]

 

Hi, Metroix,

Sadly, this information is not actionable.

If you require assistance, or wish to report a problem, please see Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Zeven,

The log shows you successfully interacting with the Rainspeaker:

[19:24:40.353 D] [InteractWith-v1538(debug)] Interacting with 'Injured Rainspeaker Oracle'
[19:24:40.354 D] Interacting with Injured Rainspeaker Oracle
[19:24:41.766 D] [InteractWith-v1538(debug)] Interact with 'Injured Rainspeaker Oracle' succeeded.
...<this happens several times>...​

Then eventually, you run out of Rainspeakers to interact with, and its waiting for the interaction aura to disappear:

[19:25:24.961 D] [InteractWith-v1538(debug)] No viable mobs in area.
Excluded Units:
Injured Rainspeaker Oracle [HasUnwantedAura(51329)]
Injured Rainspeaker Oracle [HasUnwantedAura(51329)]

[Ref: "[Fly][A - Quest] 68-80 [Kick] ($Rev: 3310 $)" @line 12226]​

This occasionally happens when the WoWclient is glitchy. We also see this problem on occasion when a quest cannot be turned in or picked up. Restarting the WoWclient usually fixes the problem, although sometimes a cache clear is required also.

Ref: HelpDesk: Cache corruption problems​

As a last resort, you might do this quest manually, then restart Honorbuddy.

cheers,
chinajade


[size=-2]Ref: Zeven's original post w/log[/size]

 

Hi, Applemes,

Sadly, this information is unactionable.

If you require assistance, or would like to report a problem, please see Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Metroix,

No, the profile pack was designed to have looting enabled at all times. You may want to give a look at the Tidybags3, or MrItemRemover2 plugin.

cheers,
chinajade

 

Hi, Paraduck,

This question is answered in the FAQ.

cheers,
chinajade

 

Hi, RamGuy,

This question is answered int he FAQ.

cheers,
chinajade

 

Hi, Krew,

This is because your Honorbuddy installation is damaged, and you should do a 'clean install'. Instructions here:

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

If you are not off-and-away after this, we'll need to see your full log attached.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, ShortRound, and MANY thanks for that log!

[16:25:13.881 D] Exception was thrown in BotBase.Root.Tick
[16:25:13.881 D] System.InvalidOperationException: Cannot call Location on an invalid object.
at Styx.WoWInternals.WoWObjects.WoWObject.EnsureValid(String funcName)
at Styx.WoWInternals.WoWObjects.WoWUnit.get_Location()
at Honorbuddy.Quest_Behaviors.SpecificQuests.HostileSkies.HostileSkies.<>c__DisplayClass21.<ChooseTarget>b__1c(WoWUnit unit) in c:\HB\Quest Behaviors\SpecificQuests\30978-TownlongSteppes-HostileSkies.cs:line 393​

Your Honorbuddy is throwing a lot of exceptions that it shouldn't. This could either be a damaged installation, or your machine may need to be rebooted. (I'd start with the former).

But indeed, you are right. The profile pack was not written with the ability to fly in mind. And, Flightor is faaaar from perfect at the moment. Thus, it is very likely that you are running into some issues. Alas, these cannot be easily resolved without re-flowing the entire profile pack (or fixing all Flightor problems which would take much longer).

For now, you are probably stuck with "keeping an eye on it" and "helping it out" until you get to the end.

Very sorry for the inconvenience.

cheers,
chinajade


[size=-2]Ref: ShortRound's original post w/log[/size]

 

Hi, Momoloveschina,

We are simply unable to assist with problems like this without a full log that captures the issue. Please see Reporting Problems or Seeking Assistance.

cheers,
chinajade

 

Hi, Ormazd,

If you use another profile, or run some quests manually, you can sometimes damage your toon's quest state. This article discuses the problem in further detail, and what can be done about it:

HelpDesk: Quest giver is not offering expected quest​

cheers,
chinajade

[size=-2]Ref: Ormazd's original post w/logs[/size]

 

Hi, Hell-Razor,

This article discusses the topic, and what you need to do:

HelpDesk: Questing profiles and the Loremaster achievement​

cheers,
chinajade

 

Hi, Sniklez,

You may find this article informative on the subject:

HelpDesk: Honorbuddy and flying​

cheers,
chinajade

 

Amazing profile!

 

Hi, Noobolov,

In v3331, we've updated the level as ShortRound pointed out. We've also modernized a number of the profile constructs.

These profile changes have not been tested, but we've no reason to believe there will be problems. We also know the profiles are not stop/start friendly. We'l see if we can do something about that in the next couple of days.

cheers,
chinajade

 

Proflie Issue: Specific vendor is not always friendly.
Results In: Character spam targeting and attempting to interact with the NPC indefinitely. No quest progression.
Profile Name: [Fly][A - Quest] BC 58-70 [Kick]($Rev: 3311 $)
Profile File: Kicks\1-90 Questing Profile Pack\BC\[Fly][A - Quest] BC 58-70 [Kick].xml

Information about problem

Code:

    <Vendor Name="Sparik" Id="19012" Type="Repair" Nav="Fly" X="-2541.9" Y="7364.772" Z="6.949437" />

Suggested solution

* Remove this Vendor from the available vendors list, and do not attempt to repair in Telaar. Alternatively, you can check the reputation with Kurenal is at minimum Friendly.

 

I have a level 58 druid and this profile bought a tawny wind rider and remains stuck continually trying to learn the wind rider, but it requires level 60 to do this. I have tried restarting HB and reloading the profile, but still no luck. The bot remains in hellfire peninsula and continually right-clicks on the tawny air rider to learn it. It gives an error message on the WoW screen stating "cannot learn that item" because I am level 58.

 

Hi, Hackersrage,

Many thanks for this. We've made the changes in v3337 for both Sparik and Caregiver Isel (vendors in Talaar). They are both usable at Neutral, not Friendly, and that's reflected in the modifications.

But there lingers a question...
The profile pack should've gotten you the necessary reputation back in Zangermarsh. How did that not happen for you?

cheers,
chinajade

 

Hi, Wassabi,

This is a boundary condition that the MountHook behavior does not handle

• This is the first toon on a new account to get flying skill
• The toon is a Druid

There is more information about the problem and what you can do about it in Known Bugs List: Miscellaneous (Rep, Seasonal, etc).

cheers,
chinajade

 

Stuck when running DK starting area profile :

[17:45:14.107 N] Moving to Type: QuestPickUp
[17:45:14.141 D] Activity: Downloading Mesh...
[17:45:45.316 D] Exception when attempting to download DeathKnightStart_42_27: System.TimeoutException: This request operation sent to net.tcp://eu2.auth.buddyauth.com:5031/AuthService.svc did not receive a reply within the configured timeout (00:00:30). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

Server stack trace:
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Buddy.Auth.SR.IA.Do(Byte b, Object[] args)
at ..
(String )
at ...
( )