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

Hi, Zthestardust, and thank you for the log.

From your log:

[00:53:38.497 N] Character is a level 22 Troll Druid
...
[00:57:47.733 D] Goal: Grinding to level 23​

This is normal, and you can find more information here:

HelpDesk: Grinding while executing a Questing profile​

You've also got this going on in your logs:

[00:57:21.389 N] Changing current profile to [H - Quest] 12-58 K and EK [Kick] ($Rev$)
...
[00:53:58.598 D] System.Xml.XmlException: Unexpected end of file has occurred. The following elements are not closed: HBProfile. Line 7519, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
...<repeats>...​

It looks like your copy of Kick's profiles have been seriously damaged. You should update to the latest copy from Subversion (not the crufty .Zip file). The instructions on how to do this are in the first post of this thread.


Next time, when asking for help, please use proper grammar, capitalization, and punctuation in your description. If not, your post will be immediately archived. If English is not your native language, we've a number of specific-language sub-forums where you may get better results.

cheers,
chinajade

 

why my bot dont work since 4 hours?

 

Hi, Twaved,

• This is not a profile issue, so your question is inappropriate for this thread.
  For issues like this, you should use the Support forum
  
  
• Anytime you ask for help, you must attach the full log that demonstrates the problem
  
  Ref: [Guide] How to attach your log​
  
  
• This post probably answers your question:
  HelpDesk: You have not selected a valid instance of WoW to attach to!

cheers & welcome aboard,
chinajade

 

Will post a log when I get home, at work right now.

Bot is stuck in Grizzly Hills at Conquest Hold talking to the same guy over and over.

Not sure if Kick or HB/Patch issue.

-Keith

 

Hi, Keifkeif1,

It sounds like a cache issue. If so, you can find the remedy here:

HelpDesk: Cache corruption problems​

If you are not off-and-away after applying this remedy, we will need to see the full log attached, please.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

China. You are amazing. Always so helpful. Will let you know after work how it goes!

-Keith

 

Code:

[19:43:46.732 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedWhile.
[19:43:46.735 N] Could not find quest giver NPC with ID 47366 in database.
[19:43:46.735 D] Stop called!
[19:43:46.735 Q] Bot Stopped! Reason: Could not create current in quest bot!
[19:43:46.753 D] Activity: Honorbuddy Stopped
[19:43:46.753 D] [FJ Diag] Stopping CC...
[19:43:46.753 D] [FJ Diag] Detached combat log

Getting this error when trying to quest in Felwood-H


Fresh install and still isn't working.

 

Why People dont read ... Post a FULL LOG!

Go to this NPC and restart HB - Impsy - NPC - World of Warcraft

 

Announcement: DK starter zone rework complete

Hi all,

We've just completed rework of the DK starter zone profile. To use it, be sure you properly install the quest behaviors that Kick provides.

cheers,
chinajade

 

Was just coming here to say that I noticed DK starter zone was being really weird (used kick for leveling 3 90's now) but I see that you guys conveniently fixed it at this time.

Will just updating SVN fix this?

 

Hi, Crujones,

The Subversion repository version with the fixes is v2195.

cheers,
chinajade

 

New bug found with 82-84 Deeopholm. The quest "Diplomacy First" is bugged, and I think it's cause the quest is bugged itself. Nothing spawns on the ship at all. Attached a log. Maybe make it do other quests and ignore this one?

 

Okay. There have been multiple instances like this, but this is the one I've finally decided to post on. It's not using the potion that you get for A Curse We Cannot Lift. It just kills the worgen, leaves the barn, comes back, kills it, leaves, comes back, kills it, leaves, you get the idea. I had to personally stop the bot so that it would actually use the potion to capture the worgen. And last night I was stuck running back and forth doing something similar for I suppose it was hours, I was asleep so I don't know. Here's the log of it, but there are more than just this issue. I've had to stop the bot a few times from running into elites and dying repeatedly (about 10 deaths when I got back just from the one elite) I didn't think it was a big deal so I just moved it myself, so I don't remember the name. However, these issues make me look like an obvious botter. I tried looking for the other logs, but I've already deleted them when I updated honorbuddy this morning.

 

problem with enemies at our doors in kun-lai summit
this has been here since well forever.. basically the bot sits there or runs into the fortification wall over and over... and never moved down the hill then back up it to make the raiders approach...

 

Having a problem at the beginning of the "[Fly][A - Quest]LK 68-80 [Kick]" profile. It abandons all my quests and tries to pick up a quest from Recruitment Officer Blythe in Valiance Keep, even though he ain't got no quest for me. The bot just stands there and targeting him, trying to pick up the quest and then untarget him again... and like that over and over again.

 

Hi, Ieatpork, and thanks for the log.

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

HelpDesk: Cache corruption problems​

cheers,
chinajade

 

Hi, Phyxios, and thanks for the log.

Two issues:

• Your Bowman Combat Routine has issues, and you should either update it, or switch to one that works.
  
  
• The log you attached was from a Professionbuddy session, and does not demonstrate the problem you describe.

cheers,
chinajade

 

Hi, Winzer135, and thanks for the log!

From the log we see this:

[10:08:34.404 D] Changed POI to:Type: QuestPickUp
[10:08:35.146 D] InteractDebug:761250744
[10:08:35.176 D] Interact Done:761250744
[10:08:38.052 D] Cleared POI - Reason Quest Completed
[10:08:38.052 D] Cleared POI
[10:08:38.609 D] Changed POI to:Type: QuestPickUp​

Your remedy is here: HelpDesk: Cache corruption problems

cheers,
chinajade

 

Hi, Ticky, and thanks for the log.

Each time you report a problem, its a chance for us to rectify it. Thanks much, as we're not able to chase things like this without good descriptions and a full log as you have provided.


@Kick,
Looks like a CombatUseItemOn issue, and we need to switch to CombatUseItemOnV2. About line 4877 of [A - Quest] EK 12-58 [Kick] v2195:

<CustomBehavior File="CombatUseItemOn" MobId="43814" ItemId="60206" MobHpPercentLeft="25" UseOnce="True" MaxRange="10" X="-11039.28" Y="249.6969" Z="27.65222" />​

cheers,
chinajade

 

Bug in Uldum - Gnomebliteration

Hi, found another one, but this is more of a WoW bug that could be bypassed with help of the profile.

While in the Fusion Core form, the orb sometimes disappears (happens even when manually playing), stops obliterating gnomes and it is necessary to leave the vehicle and take a new one. When this happens to the bot, it will just get stuck chasing unkillable goblins, however when I tell it to manually leave the vehicle, it correctly picks up a new orb and goes on with the quest.

I imagine this could get fixed in two ways:
a) give a timeout of, say, 60s after which it will always leave the vehicle.
b) check if any goblins have been killed in past 10-15s and if not, leave the vehicle.

Not sure how feasible it is to do either, tho.

PS: Attached the log, but there isn't anything useful in it, as far as I can tell, the pathing errors come from when the Fusion Core is jumping off that Jawa transporter thingie.