Kick's Mega Profile Packs 1-90

Hi, Maikelvanv,

The attachment is invalid for some reason. To help us chase problems, we need to see the log that captures the problem.

Ref: [Guide] How to attach your log​

But, from your problem description it sounds like an issue of cache corruption. Please try the remedy listed here:

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Hi, Perfn, and many thanks the log.

Such problems are usually caused by a new install of Honorbuddy. You can find more information about the problem, and how to repair it, here:

HelpDesk: Honorbuddy can't find the quest-giving NPC​

cheers,
chinajade


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

 

Hi, Toney001, and many thanks for the log.

Here is your problem:

[14:00:36.308 D] UseNativeFlying: True​

You can find more info about it here:

HelpDesk: Honorbuddy and flying​

cheers,
chinajade


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

 

Hi, Toney001, and thanks for the log.

[14:49:50.225 D] Goal: Moving to <902.4197, -1902.526, 57.98389>
[14:49:50.391 D] Flushing timed movement. Direction: AllAllowed
[14:50:02.630 N] Stopping the bot!

This looks like a problem with Honorbuddy itself. Honorbuddy has just decided to stop executing the profile directives. Please report this to the Release thread or the Support forum.

I'm not aware of a work-around for this issue, but they log should assist the responsible developer in chasing the problem.

cheers,
chinajade


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

 

Hi, Toney001, and many thanks for the log.

It looks like you are on A Seemingly Endless Nuisance. It also looks as of v2652, the quest is no longer part of the profile pack. My guess is that the multi-mob encounters were just too dangerous for the squishie classes.

Sorry the problem wasn't actually solved, but it should no longer be a problem for the Community.

cheers,
chinajade


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

 

Hi again, Tigerlady3012, and many thanks for the log and details!

[15:56:34.015 D] Changed POI to: Type: QuestPickUp
[15:56:34.092 D] Targeting quest npc
[15:56:34.725 D] InteractDebug:1043021020
[15:56:34.749 D] Interact Done:1043021020
[15:56:36.909 D] Cleared POI - Reason Failed to open quest window. Trying again.
[15:56:36.909 D] Cleared POI
[15:56:37.097 D] Changed POI to: Type: QuestPickUp
[15:56:37.305 D] InteractDebug:1043021020
[15:56:37.327 D] Interact Done:1043021020
[15:56:37.739 D] Targeting quest npc
[15:56:39.578 D] Cleared POI - Reason Failed to open quest window. Trying again.
[15:56:39.578 D] Cleared POI
[15:56:39.739 D] Changed POI to: Type: QuestPickUp​

It looks like you are suffering from cache corruption. Please try the remedy here:

HelpDesk: Cache corruption problems​

cheers,
chinajade


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

 

Hi, Pexus, and thanks for the update.

In v2684, we've added this new hotspot for Tiger Mastery (Tiger Mastery - Quest - World of Warcraft). It looks like this quest is only available to the Alliance. Next time, please also attach your log so we can verify all necessary corrections have been made.

cheers,
chinajade


[size=-2]Ref: Pexus' original post, no log[/size]

 

Hi, Trashmaster. Thank you for the report, log, and many details!

Alas, the last third of your log contains this:

[17:50:01.195 D] System.AccessViolationException: Could not read bytes from 00E6C84E [299]!
at Styx.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)​

This means Honorbudy is having serious problems communicating with the WoWclient. That is why the mob count was wrong, and Honorbuddy prematurely attempted to turn in the quest.

The only known work-around for this issue is to restart the WoWclient and Honorbuddy. Sometimes, a reboot is required. I've no answer as to why this problem happens occasionally for some people.

cheers,
chinajade


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

 

Hi, Obbi, and many thanks for the log.

The bot is trying to pick up The Theramore Docks. The quest requires level 30, and is recommended at level 35. I would think a level 38 could easily handle it.

Let's try clearing your caches just to make certain Honorbuddy understands the correct quest state:

HelpDesk: Cache corruption problems​

Your problem may be gear or combat routine related. This article may be some help regarding that:

HelpDesk: Dying too much while questing​

I'd highly recommend Singular while questing. It is built for PvE encounters (and consequently more survivable). Your current Combat Routine choice may be designed for better DPS performance or other considerations that are at direct odds with survivability in a PvE environment.

cheers,
chinajade


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

 

Hi, Pexus,

Thank you for the report, but this belongs in the Navigation thread. Over there, they will also need a screenshot to see how you are getting stuck. I would've moved it for you, but without a screenshot, the report will be useless for effecting repairs.

cheers,
chinajade

 

Hi, Cevaps.

First, MANY kudos for doing the search for a solution! Also, thanks for the log.

[12:45:44.595 D] Changed POI to: Type: QuestPickUp
[12:45:44.964 D] Targeting quest npc
[12:45:45.932 D] InteractDebug:687467780
[12:45:45.964 D] Interact Done:687467780
[12:45:48.842 D] Cleared POI - Reason Failed to open quest window. Trying again.
[12:45:48.842 D] Cleared POI
[12:45:49.373 D] Changed POI to: Type: QuestPickUp
[12:45:49.699 D] Targeting quest npc
[12:45:50.733 D] InteractDebug:687467780
[12:45:50.766 D] Interact Done:687467780
[12:45:53.637 D] Cleared POI - Reason Failed to open quest window. Trying again.
[12:45:53.637 D] Cleared POI
[12:45:54.165 D] Changed POI to: Type: QuestPickUp​

This is classic cache corruption, and the only solution I know to repair the problem is cited in the article you referenced:

HelpDesk: Cache corruption problems​

If you are unable to get this solution to work for you, please make a post into the Support forum with a fresh log. Your problem doesn't seem to be profile-related, as the correct directives are being issued in accordance with Honorbuddy's understanding of your quest state.

cheers,
chinajade


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

 

Hi, Movotyler, and many thanks for the logs!

Kick's profile is issuing the correct directives, so its not a profile problem.

Let's try first clearing the caches. Instructions here:

HelpDesk: Cache corruption problems​

If that doesn't get you going, the please make a post into the Support forum with a fresh log. Effecting the turnin/pickup is the responsibility of Honorbuddy, and there is nothing the profile can do to assist with this.

cheers,
chinajade


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

 

Hi, Hi1674,

Yes, we will eventually clean up these messages. However, there is no pressing need to prioritize them above other, more important work. The messages clearly state the behavior still works correctly, and they should be emitted infrequently enough that log size isn't an issue.

cheers,
chinajade

 

Hi, <Weischbier>

Alas, the log was truncated and didn't provide sufficient information for analysis.

As a guess, we'll say your cache is corrupted. You can find the instructions for clearing it here:

HelpDesk: Cache corruption problems​

cheers,
chinajade


[size=-2]Ref: <Weischbier>'s original post w/log[/size]

 

Hi, Woofie,

Unable to find quest givers is usually caused by a fresh Honorbuddy installation. You can find the full explanation and remedy in this article:

HelpDesk: Honorbuddy can't find the quest-giving NPC​

As you know the Deepholm 'boat quests' are special, in that, if the bot stops for any reason, it will be unable to re-establish the correct quest state. This means you'll need to do the 6 or so 'boat quests' manually, put your toon back on the ground, then restart the bot.

Next time, please provide a full log, and not a truncated one.

Ref: [Guide] How to attach your log​

cheers,
chinajade


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

 

Hi, Pefra, and thanks for the log.

Your Honorbuddy installation is damaged, and you need to do a 'clean install'. You can find the instructions here:

HelpDesk: "Clean installing" Honorbuddy​

If you have no success with this, please follow up to the Support forum with a fresh log.

cheers,
chinajade


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

 

Hi, CulverMA,

In v2686, the issue should be repaired. In the future, please do not truncate your log, but Zip it if its too big.

cheers,
chinajade


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

 

Hi, Glitchingbot, and thanks for the log and report!

@Kick, it looks like the code to remove the Murloc Suit is not running because this user is running a Russian WoWclient:

From "[Fly][A - Quest] 68-80 [Kick] ($Rev: 2680 $)" ~line 3897:

<CustomBehavior File="RunMacro" Macro="/cancelaura King Mrgl-Mrgl's Spare Suit" NumOfTimes="1" WaitTime="1000" />​

and the log

[13:21:04.598 D] Goal: RunLua: In Progress
[13:21:04.598 D] Activity: RunLua: UseItemByName(34620) 1 number of times while waiting 1000 inbetween​

We need to find a language-independent way of achieving the aura canceling.


cheers,
chinajade


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

 

Hi, Tiic, and many thanks for the log!

[17:40:58.842 N] Moving to Type: QuestPickUp
[17:41:02.021 N] WoW cannot be minimized while running Honorbuddy!
[17:41:05.317 D] InteractDebug:708854356
[17:41:05.346 D] Interact Done:708854356
[17:41:09.439 D] InteractDebug:708854356
[17:41:09.440 D] Interact Done:708854356​

First, please try one more time to clear the cache--instructions here:

HelpDesk: Cache corruption problems​

If you are trying to play another game while using Honorbuddy, temporarily stop this activity, and see if that cures the problem. There are some games that simply interfere with Honorbuddy, and you may be trying to use one of them. There is no master list of which games play nice and which don't. Its a "try it and see" proposition. No matter what, you *must* play the other game in windowed, not full-screen mode

If that fails, please follow up to the Support forum with a fresh log. The problem is not profile-related as the profile is issuing the correct directives given the quest state.

cheers,
chinajade


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

 

Hi, Mgssidley, and thanks for the log.

[17:59:14.882 D] System.NullReferenceException: Object reference not set to an instance of an object.
at Honorbuddy.Quest_Behaviors.PerformTradeskillOn.PerformTradeskillOn.GetTradeSkillIndex() in c:\Users\*****\Desktop\Rogue Dailies COPY FIRST - Copy\Quest Behaviors\PerformTradeskillOn.cs:line 186
...<error continues>...​

Your Honorbuddy is having issues communicating with the WoWclient. The only known remedy is to restart both the WoWclient and Honorbuddy. Sometimes, even a full system reboot is required.

If you continue to suffer from this problem, please post a fresh log into the Support forum.

cheers,
chinajade


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