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

Hi, MaxMuster,

We went with a slightly different stop-start friendly change that looks like this:

<While Condition="HasQuest(12058) &amp;&amp; !IsQuestCompleted(12058)">

<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="3"

MobId="188289" CollectionDistance="10"
X="4952.656" Y="-4705.741" Z="219.8488" />​

<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="1"

MobId="188264" CollectionDistance="10"
X="5007.675" Y="-4734.232" Z="219.4391" />​

<CustomBehavior File="InteractWith" QuestId="12058" QuestObjectiveIndex="2"

MobId="188288" CollectionDistance="10"
X="5006.924" Y="-4790.667" Z="219.4593" />​

<CustomBehavior File="WaitTimer" QuestId="12058" WaitTime="10000"

GoalText="Waiting for quest to complete {TimeRemaining}" />​

</While>​

We did this such that the Alliance-side and Horde-side quest would have the same (simplified, but stop-start friendly) profile code. If you feel that this was the wrong approach, please let us know.

The changes are folded into v3046.

cheers,
chinajade


[size=-2]Ref: MaxMuster's Horde problem report w/recommended repair[/size]
[size=-2]Ref: MaxMuster's Alliance problem report w/recommended repair[/size]

 

Hi again, John1337,

We thank you for double-checking the work.

From your screenshot, it appears that the disagreement is in the name of the quest to be turned in. In the pane showing "Theirs", we have the quest name as "Learning the Word". In the pane showing "mine", you have the quest name as "Healing the Wounded".

Looking up Quest Id 26919 on WoWhead yields this: Learning the Word - Quest - World of Warcraft

We believe the changes in the repository are correct as is. Are we somehow missing your point?

cheers,
chinajade


[size=-2]Ref: John1337's follow-up problem report w/screenshot[/size]

 

Hi, Zeppse7en,

If you need assistance, please attach your full log so we can analyze the problem.

Ref: [Guide] How to attach your log​

Ikuti is not a vendor in the Alliance or Horde BC profiles. Our guess is that your profiles are horribly out-of-date, or you have edited them in the past, and forgotten about it.

cheers,
chinajade

 

<waves at MaxMuster>

The landing zone has been updated in v3047.

cheers,
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended repair][/size]

 

Hi, Ought, and thank you for the log!

Toon: 26.4 Pandaren Hunter (Female, Horde)

[21:10:00.177 D] Goal: Grinding to level 27​

It looks like the profile is functioning correctly. Your toon is 26.4, and it wants to grind to 27 before proceeding. This article should explain further:

HelpDesk: Grinding while executing a Questing profile​

And, just to be safe, let's make certain your caches are not corrupt. This article will help you clear them:

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Hi, MaxMuster,

We made the refinements you suggested in v3048.

However, the second refinement is very disturbing. I would've expected to see something like:

<Objective QuestName="Just the Tip" QuestId="27176" Type="CollectItem" ItemId="60865"

CollectCount="1" X="-9277.324" Y="-1760.133" Z="67.87192" Nav="Fly" />​

Are you saying that Nav="Fly" does not work for this (or possibly other) <Objective>s? If so, we need to submit a bug report against this.

cheers,
chinajade


[size=-2]Ref: MaxMuster's problem report w/recommended repair[/size]

 

Hi, Kandiman, and many thanks for the log.

Indeedy, The Grimtotem Weapon - Quest - World of Warcraft is on our Known Bugs List: Classic 1-58. For now, please do the quest manually, turn it in, and start Honorbuddy again.

Sorry for the inconvenience.

cheers,
chinajade


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

 

Sorry if this is not the right place to ask, but are there any plans to update the vashj leveling profile so that it works again? I didn't know it existed until this morning and when i tried to use it, it didn't seem to be able to do alot, i can give a log if it's meant to be working, i'm just assuming it's not as it's abit hidden away from the other pofiles.

 

Hi, Avalarion23, and many thanks for the log.

[21:02:19.497 D] Goal: Kill Verrottender Schrecken x 8
...
[21:02:26.434 D] [Sharp Messenger] Reading location failed with 'System.Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen, at addr: 6C6C69F3, Size: 4
bei GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
...
[21:02:27.015 N] Not in game​

Your log shows you were performing the objective for The Night Watch - Quest - World of Warcraft of killing 8 "Rotting Horrors". Then one of your plugins started having problems with communicating with the WoWclient which caused the crash.

This log does not show you getting to the objective of In A Dark Corner - Quest - World of Warcraft, yet.

I'd try disabling the Sharp Messenger plugin if the problem persists.

cheers,
chinajade


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

 

Hi, Benh1337,

The profile names were correct for the way Bliz originally designed the zones. Since then, Bliz has bumped the zone experience a couple of times in patches. We do not go back and rename the scripts when this happens, since the profiles auto-chain from one to another. To do so would lead to unnecessary maintenance.

As far as grinding, you may find this article informative:

HelpDesk: Grinding while executing a Questing profile​

cheers,
chinajade

 

Hi, Darteagqa, and many thanks for the log.

This looks like a problem with your Combat Routine. It doesn't appear to be finishing its initialization properly.

Go back to Singular, and you should be golden.

cheers,
chinajade


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

 

Hi again, Daarno,

[20:14:25.278 N] Honorbuddy v2.5.9096.487 started.
[20:14:25.279 Q] This is a BETA build of Honorbuddy. This is not meant for general usage. Please report any issues you may have in the beta thread on our forums.
[20:14:25.279 Q] This build may have bugs, and new features which may not be fully tested. Use at your own risk!​

Once again, we do not accept reports from Beta. Beta is not ready for prime-time; otherwise, it would've already been promoted to a "Release".

For problems just like this:

[04:39:25.055 D] System.NullReferenceException: Object reference not set to an instance of an object.
at Honorbuddy.QuestBehaviorCore.UtilityBehaviorPS.MoveTo.<CreateChildren>b__91(Object context) in d:\DATA\paladin\Quest Behaviors\QuestBehaviorCore\UtilityBehaviors\Movement.cs:line 136
at Styx.TreeSharp.Decorator.CanRun(Object context)​

There is obviously a bug in Beta regarding movement that is causing your issue.

Once again, I will point you to the explanation here: Things To Know.

And any further posts you make here regarding a Beta release will be immediately archived.

cheers,
chinajade


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

 

Hi, Chunky, and welcome aboard!

We've no way to analyze your problem, unless you attach the full log that captures the issue.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

If two mobs are fighting each other and bot gets somehow in combat, it will not take any actions, will not move on, attack the mob/s that is keeping him in combat but will freeze itself and stand next to them untill they kill each other and gets out of combat and only then will move on. Since this mob fights never ends it will stay there all the time untill manualy kill the mob or get far away from them. This happened with every single mob fighting each other group from low to high lvl and i would always find him next to the mobs or if i am next to a pc will have to manualy get out of combat.

 

Hi, Daarno, and thanks for the log.

[09:18:36.087 D] Goal: SealingTheWay-vUnknown: ""Sealing the Way" (http://wowhead.com/quest=26501)"
[Ref: "[Fly][N - Quest] Deepholm 82-83 [Kick]($Rev: 3042 $)" @line 1369]​

Aye, the "Sealing the Way" behavior was damaged by the Honorbuddy re-architecture earlier last month, and it has yet to be repaired. This issue is on the Known Bugs List: Cata 80-85.

For now, please do the quest manually, turn it in, and start Honorbuddy again.

cheers,
chinajade


[size=-2]Ref: Daarno's problem report w/log[/size]

 

Hi, Slite62, and many thanks for the log.

Indeed, this is bug report #HB-282, that should be repaired in the next Honorbuddy drop. You can find more information about it in this post.

For now, your only work-around is to complete the quest manually, turn it in, then start Honorbuddy again.

cheers,
chinajade


[size=-2]Ref: Slite62's problem report w/log[/size]

 

i keep getting banned while using kicks quest profiles its getting worse when ever i quest manually with hb tyrael im fine but when ever i use quest profile im banned within a few days im done with questbotting for now.

 

Hi, Snowa,

I recall many many moons ago, an incredibly industrious Community member made a working Vashj'ir profile. However, that profile wasn't Kick's--Kick's has never worked in Vashj'ir to my knowledge. I believe it just gets you to the point of getting the Seahorse mount.

I *wish* I could locate that profile of old--it was simply amazing. But, the couple of times I've gone digging through the forums, I've never been able to locate it.

The problem with Vashj'ir is that Honorbuddy will not navigate underwater (the profile was written pre-Flightor, Honorbuddy's flying navigator). The industrious soul had painstakingly used click-to-move to complete all the quests, and it worked very seamlessly as I recall. It was truly a work of art, and I'm very sorry I don't recall the author's name, and can no longer locate that profile.

cheers,
chinajade

 

Hi, Hoper, and many thanks for the log.

The problem is not with the profile. But... please go back to Singular, and your problems should go away.

Many combat routines (especially PvP ones) do not handle the PvE environment well. Singular notices when the WoWclient has placed the toon in combat, but no NPC is attacking it, and allows Honorbuddy to go back about its business.

There are further improvements in this area that should be made available in upcoming Honorbuddy drops. However, a mis-behaving combat routine will still cause problems.

cheers,
chinajade


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

 

Okay thanks