Kick's Mega Profile Packs 1-90

Hi, Ergosum,

This is a problem with the HBcore <Objective> directive. The profile is issuing the correct directives, but Honorbuddy is ignoring being attacked while pursuing the objective. The Objectives are lines 757-759 of the v2652 Valley of Four Winds profile.

<Objective QuestName="Lupello" QuestId="29917" Type="KillMob" MobId="56357" KillCount="1" />
<Objective QuestName="Piercing Talons and Slavering Jaws" QuestId="29916" Type="KillMob" MobId="56034" KillCount="5" />
<Objective QuestName="Piercing Talons and Slavering Jaws" QuestId="29916" Type="KillMob" MobId="56106" KillCount="6" />​

I'll see if I can bring the problem to the attention of the appropriate developer. The problem is not actually with the profile or your Combat Routine, but with HBcore.

The fix will not be quick, so please do the "Piercing Talons and Slavering Jaws" quest manually, turn it in, and start Honorbuddy again.


cheers,
chinajade


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

 

Hi, Thickchesthair, and thanks for the log.

Different quest, but you've got the same problem as Ergosum. Line 4361 of v2691 of the Horde 12-58 profile is a kill objective in which Honorbuddy is ignoring your mobs.

<Objective QuestName="Between a Rock and a Thistlefur" QuestId="216" Type="KillMob" MobId="3925" KillCount="15" />​

It may have something to do with recent target filter changes. I'll see if I can get this in front of the responsible developer. The problem is neither with the profile, nor the Combat Routine.

To work around in the meantime, please do the quest manually, turn it in, then start Honorbuddy again.

cheers,
chinajade


[size=-2]Ref: Thickchesthair's original post w/log, Post 2[/size]

 

Hi, Jsl1994321, and thank you for the log.

Your installation of Honorbuddy is damaged, and you should do a 'clean install'. Instructions here:

HelpDesk: "Clean installing" Honorbuddy​

If no joy, please follow up to the Support forum with a fresh log. Your problem is not related to Kick's profile pack.

cheers,
chinajade


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

 

Hi, PanYama,

The profile defines a list of vendors which are acceptable to use for the area. Honorbuddy supplements this with additional ones it has 'learned' along the way.

Honorbuddy itself, not the profile, selects the closest vendor that meets whatever selection criteria (sell, repair, train) that initiates the movement.

Without a log, we will be unable to see if something is interfering with this process. (E.g., exceptions being thrown, a malfunctioning plugin, etc.)

cheers,
chinajade

 

Hi, Blinkpoolz2, and thank you for the report and log.

This an yet another problem with the HB <Objective> directive:

<Objective QuestName="In Case of Emergency..." QuestId="10161" Type="CollectItem" CollectCount="30" Name="Zeppelin Debris" ItemId="28116" />​

It apparently doesn't blacklist items after being unable to reach them within a reasonable amount of time. This is not an issue with the profile, but with HBcore. I'll see if we can get this in front of the responsible developer.

The fix will not be quick. As a work-around in the meantime, please do the quest manually, turn it in, and start Honorbuddy again.

cheers,
chinajade


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

 

Hi, Epru0,

Woofie is spot on with this--your Honorbuddy installation is damaged. Please follow the instructions here for a 'clean install':

HelpDesk: "Clean installing" Honorbuddy​

cheers,
chinajade

 

Hi, Ogsrebirth,

The instructions for getting the profile pack downloaded and running are contained in the first post of this thread. Each author's profile pack is unique, so you should read the first few posts of any thread for which you'd like to use a profile.

cheers,
chinajade

 

Hi, Tefyx,

Questions like this belong in the Honorbuddy general forum. You might find this article helpful:

HB Usage: How do I keep from getting banned? - Buddy Wiki​

Then, follow up to the Honorbuddy general forum with any additional questions you may have.

cheers,
chinajade

 

A better way (which I used with the quest involving 'Billy Goat') is to stop before casting on the mobs location, I used a plugin for this and WoWMovement.Stop();.. this addresses the dropping off the cliff issue, and yes I know that it should be meshed but it's not .

 

Hi, Ruinit, and thanks for the log.

v2689 of the profile pack should contain a fix for the issue. The problem is that Flightor believes the destination is 'indoors', and that confuses it.

cheers,
chinajade


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

 

Hi, Ricdec, and thank you for the detailed report and log.

There is something peculiar about picking up the quest "Two Tents". We'll have to revisit the area and figure out what has been changed.

In the meantime, please do the quest manually, turn it in, and start Honorbuddy again.

@Kick,
Need a testbed to pick up "Two Tents" from Sullah.

cheers,
chinajade


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

 

Hi, Crowns, and thanks for the logs.

As always, issues such as this are user-errors. Looks like your machine & Honorbuddy installation is seriously messed up.

Four of your logs are filled with this:

[19:14:48.414 D] Exception when attempting to download Azeroth_30_38: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://www.buddyauth.com:5031/AuthService.svc. The connection attempt lasted for a time span of 00:00:01.5660896. TCP error code 10061: No connection could be made because the target machine actively refused it 188.165.234.190:5031. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 188.165.234.190:5031
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---​

And one of your log is filled with this:

[14:00:43.524 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent was never fired
at Styx.MemoryManagement.Executor.Execute(Int32 fromId)​

We suggest you make a post into the Support forum with a fresh log. Your Honorbuddy installation / machine needs to be cleaned up.

Your problems are NOT related to Kick's profile pack.

cheers,
chinajade


[size=-2]Ref: Crown's original post with an abusive number of logs[/size]

 

Hi, Adde95, and many thanks for the log.

It looks like you are suffering from cache corruption. You can find the explanation and the remedy in this article:

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Hi again, Ruinit,

First, you are using Beta, and Beta is buggy by definition; otherwise, it would've been promoted to a "Release".

Second, you're a couple of revs old on the profile, and things could've been repaired (I'm only looking at the latest, and not certain).

But, you've got a legitimate issue, too:

[21:17:06.816 N] Moving to Type: Interact
[21:17:59.904 D] Updating repair cost for current equipped items. New value: [2g27s90c]
[21:17:59.905 N] Moving to Type: Interact​

The [21:17:59.905 N] is the last line of your log, and it looks like Honorbuddy just quit pursuing the <Objective> (line 5460 of Alliance 68-80 v2689).

<Objective QuestName="Rescuing the Rescuers" QuestId="11244" Type="UseObject" ObjectId="186565" UseCount="8" />​

I'd report this to the Beta thread. It is most definitely NOT a profile issue.

cheers,
chinajade


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

 

Hi, Pinki104 and Garbooo,

This article should fix you up:

HelpDesk: Toon is not moving​

Next time, please attach your full logs. This time, you got lucky since we knew what the issue was.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

Hi, Elbon4life,

This is a bug we're currently working through. Please do the "Free At Last" quest manually, turn it in, and start Honorbuddy again.

Sorry for the inconvenience.

cheers,
chinajade


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

 

Hi, BubbaDad,

You can find information about Loremaster here:

HelpDesk: Questing profiles and the Loremaster achievement​

As for rep/dailies, there are other profiles that accomplish this goal. Most are located in the Submitted Profiles/Neutral forum, but you should look around for others, also.

cheers,
chinajade

 

Hi, Ganje1000,

You've made a simple mistake. You've placed Kick's profile pack inside you Honorbuddy/Quest Behaviors/ directory.

Please move the Honorbuddy/Quest Behaviors/1-90 Questing Profile Pack/ outside of the Honorbuddy directory tree, and you should be golden. Profiles are not Quest Behaviors, and placing profiles in that directory confuses Honorbuddy immensely.

If you continue to suffer installation problems, please follow up to the Support forum with a fresh log.

cheers & welcome aboard,
chinajade


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

 

Hi, Frosticus, and thank you for the rich details and the log.

The problem appears to be a target filter issue while HBcore is processing <Objective>s. Here's the appropriate profile directive (line 2046 of Alliance Jade Forest v2619):

<Objective QuestName="Residual Fallout" QuestId="30500" Type="KillMob" MobId="59417" KillCount="10" />​

I'll try to get this to the attention of the responsible developer. There are several quests like this that are broken because of this issue. The problem is neither with the profile, nor the combat routine.

The work-around at the moment is to do the quest manually, turn it in, then start Honorbuddy again. Sorry for the inconvenience.

cheers,
chinajade


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

 

Hi, Remmey,

Alas, the log you attached has been heavily edited. Important details we need to analyze the problem have been removed. If you still need help with this issue, please submit the full, unedited log and restate the problem. Then, we'll be glad to give it another look.

cheers,
chinajade


[size=-2]Ref: Remmey's original post w/heavily edited log that is unusable[/size]