HB ARCHIVES: Kick's Old Posts Thread--DO NOT DELETE!

Klaxxi is done minus testing.
Golden Lotus is almost done, just missing Guo-Lai.
AC and Shado-Pan are coming together.
Shieldwall has no mesh/huge path issues, and I've chosen to wait rather than hack a bad profile together on it.

 

Yes, I think so. I'll look into it.

 

hello,
i have a problem with this profile, basiclly every flight path that the char has in range, just runs to it and tries to update, but nothing is happening, it just stayes there clicking the fp untill it gets logged out for inactivity, idk if the problem is that now you dont need to discover the flight paths but you get them automaticly when you level. (atm using this profile "[A - Quest] EK 12-58 [Kick]"), havent checked the other higher level questing profiles to see if they have the same problem.
if its not a profile problem, could you let me know how to fix this .

thank you,
Coitza.

 

Hi, Coitza,

What you describe is not a profile problem, but a kinda-bug in Honorbuddy. You trigger this problem most frequently when you switch toons, or log out/in right quick, without restarting Honorbuddy.

To repair the problem...
Follow these instructions for clearing your caches, and you should be off-and-away.

Always shut down Honorbuddy any time you plan to log out, and restart it after you've logged in on your new toon. (If that's how you triggered the problem).

cheers,
chinajade

 

Eastwind rest.

PHP:

<Hotspot X="2268.778" Y="897.7495" Z="481.2404" />

Big tent, well the only tent there, the bot thinks it can walk out on the back side off the tent even if there is no opening...

PHP:

[12:08:08.576 D] Goal: Interacting with 
[12:08:08.694 D] Activity: Moving towards - <2480.478, 746.7447, 514.3858>
[12:08:17.540 D] [STUCK] Got stuck at <2276.78, 886.3036, 486.9482> on map 870
[12:08:17.567 D] [STUCK][HITTEST] LD/LU: False
[12:08:17.567 D] [STUCK][HITTEST] Left: False
[12:08:17.567 D] [STUCK][HITTEST] RD/RU: False
[12:08:17.567 D] [STUCK][HITTEST] Right: True
[12:08:17.567 D] [STUCK][HITTEST] Behind: False
[12:08:17.567 D] [STUCK][HITTEST] Behind Left: False
[12:08:17.567 D] [STUCK][HITTEST] Behind Right: True
[12:08:20.920 D] [STUCK] Strafing worked!
[12:08:21.023 D] Flushing timed movement. Direction: AllAllowed
[12:08:23.575 N] Stopping the bot!
[12:08:23.576 D] Stop called!

 

I'm sorry to say.... this isn't working at all for me anymore.

All it does is switch to the correct sub-profile, fly to the area, state "Done" and go the the next sub-profile.
It never picks up any quests, never completes any quests.
From the log I can tell that it's evaluating all statements in the profile correctly and from the profile I can tell that the code is all as it should be (at least from my own experience writing profiles) but somehow HB isn't seeing what it should be seeing.

As far as I can see from the forums there's something wrong with the cache on HB and I'm afraid that's struck me now as well.

 

Actually ya I am. However they are 2 different installs (one for DPS ui one for healer etc). And one is 64bit other obviously 32.

 

Hi again, Excelerate,

The reason why I asked about the sessions, is that both the WoWclient and Honorbuddy can have problems if multiple instances are run out of the same directory. Technically, we're supposed to have a separate WoWclient directory for each toon we run simultaneously, and a separate Honorbuddy directory for each toon that is running.

Obviously, this burns diskspace like mad, and that's why most people don't do it. But if you don't, all the running WoWclient instances share the same Cache directory (and similarly, all the HB instances share the same Cache directory), and you start to see problems like you describe. This is caused by the multiple processes writing to the same cache and corrupting it over time. Most of the time, we get lucky and its not a problem--but not always.

Just fyi,
chinajade

 

It has struck us all. You have to fix this daily. There is currently no direct workaround. Some say deleting the cache folder is sufficient. I find deleting everything except plugins, QBs, profiles, and routines (if you have custom ones). Then reinstall the bot again, overwriting the QBs and singular. You can also make a new install in a second folder, and use that for questing only. Quests are the only thing affected by this "bug".

 

In the Klaxxi daily profile, this below is spammed in my log and you see the toon just stands there:

It is referring to quest 31235 - Nope Nope Nope Nope Nope Nope - Quest - World of Warcraft

Item: Shado-Pan Dragon Gun - Item - World of Warcraft
MobID: Dreadspinner Egg - NPC - World of Warcraft (This is an object not a mob, is:
<CustomBehavior File="UseItemOn" QuestId="31235" MobId="62077" ItemId="82807" Range="6" WaitTime="5000" WaitForNpcs="False" NumOfTimes="100" CollectionDistance="1000" X="535.9993" Y="2171.962" Z="312.0496" />

The correct usage?)

I have UseItemOn.cs in the proper location for quest behaviors, the right item in my inventory, and have tried a couple CC's and relaunches. Have cleared quest cache too.

Code:

[ATTACH]72359.vB[/ATTACH]

Edit:

Code:

 [15:13:46.714 D] [UseItemOn-v249(debug) @line 669]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.718 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.721 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.722 D] [UseItemOn-v249(debug) @line 670]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.753 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.753 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.755 D] [UseItemOn-v249(debug) @line 671]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.783 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.783 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.784 D] [UseItemOn-v249(debug) @line 672]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.820 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.820 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.853 D] [UseItemOn-v249(debug) @line 673]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.855 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.856 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:46.857 D] [UseItemOn-v249(debug) @line 674]: Behavior sees 'done'.  Skipping behavior.
[15:13:46.901 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.391 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.414 D] [UseItemOn-v249(debug) @line 669]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.448 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.448 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.481 D] [UseItemOn-v249(debug) @line 670]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.483 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.483 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.521 D] [UseItemOn-v249(debug) @line 671]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.524 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.524 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.525 D] [UseItemOn-v249(debug) @line 672]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.555 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.555 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.585 D] [UseItemOn-v249(debug) @line 673]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.587 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.587 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.618 D] [UseItemOn-v249(debug) @line 674]: Behavior sees 'done'.  Skipping behavior.
[15:13:47.654 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:47.962 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:48.007 D] [UseItemOn-v249(debug) @line 669]: Behavior sees 'done'.  Skipping behavior.
[15:13:48.029 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:48.029 D] [QDBG] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
[15:13:48.030 D] [UseItemOn-v249(debug) @line 670]: Behavior sees 'done'.  Skipping behavior.

 

Complete noob at this, but maybe UseItem.cs is more appropriate? I think there is a quest like this in Stonetalon that is basically the same quest with burning some tents, maybe I can find a parallel use case.

 

Hi, Deevoon, and thanks for all the info!

I double-checked all your IDs against WoWhead, and everything appears to be hunk-dory in the use of UseItemOn.

I've seen a couple of the authors of Daily quest profile packs saying something about cache issues and Honorbuddy at the moment. Here is an example thread of the discussion.

I don't know for certain, but I'd guess that Kick's profiles suffer from the same problem, since it appears to be an Honorbuddy problem.

cheers,
chinajade

 

Cool deal, the next quest down same thing happens. Brodie's profiles work fine, but I don't know if he uses the same behavior.

 

Full reinstall of HB still didn't fix it. I guess bot issue is correct.

 

Horde - Jade Forest
Orc Hunter
HB .518

Quest: The Threads that Stick

I dont know what my Toon did, but he is totaly wrong as you see on the Map. I restart serveral Times HB, but my Toon does Grinding there all the time and trys to get 7 times the Silk Item. Moved my Toon by hand to the right Place and it gets the Cocoons.
I give some Hotspots if you need to replace them in the profile, didnt checked it right now.

<Hotspot X="1368.275" Y="-1487.718" Z="272.6338" />
<Hotspot X="1270.06" Y="-1513.889" Z="248.2551" />
<Hotspot X="1285.718" Y="-1620.366" Z="230.9354" />
<Hotspot X="1373.419" Y="-1680.365" Z="220.4242" />
<Hotspot X="1453.32" Y="-1666.312" Z="236.9703" />
<Hotspot X="1318.763" Y="-1575.857" Z="246.2861" />
<Hotspot X="1417.934" Y="-1587.774" Z="266.3169" />

 

Horde - WOTLK
Panda Hunter
HB .518

Quest: Jun'ik's Coverup

Toon interact with the NPC Vendors, but doesnt buy the items to complete the Quest.

 

@Kickazz006, bro... Thank you so much for the Questing profiles you made... did my shammy 85 to 90 and my dk 80 to 87(atm). IT IS AWESOME!!! thank you so much!!!

 

I've been running into a problem with the Horde Jade Forest profile. Once it reaches a certain point in the hozen quests, you have to stop the bot and manually do the quests for the scout's report, which is fine. The problem arises that after I complete these quests, the bot keeps moving back to Shademaster Kirin to accept the quests you just completed, and won't move past it.

*edit* Log attached

 

Hi, Scrubbish,

Its hard to tell anything without looking at a log. As such I'll guess that your cache need cleaning out. Follow these instructions for clearing your caches.

If this doesn't get you going, post your log, and let's have a look.

cheers,
chinajade

 

heh yeah I started the post from a different machine than the bot, so i had to post it and then edit it from the other machine to attach the log. Anyhoo....cache cleaned, gonna give it a try.