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

My mage was stuck there till i went in a did it myself

 

attach a log

 

[10:20:29:689] [FlyTo-v217(debug) @line 522]: Flying to 'Pickup Quest': <7801.285, -2430.893, 487.5896>.
[10:21:00:256] [Flightor]: Unstuck attempt 30
[10:21:01:713] [Flightor]: Unstuck attempt 31
[10:21:03:129] [Flightor]: Unstuck attempt 32
[10:21:04:577] [Flightor]: Unstuck attempt 33
[10:21:06:026] Loading Kalimdor_36_19
[10:21:06:127] Loading Kalimdor_36_17
[10:21:06:226] [Flightor]: Unstuck attempt 34
[10:21:07:741] [Flightor]: Unstuck attempt 35
[10:21:09:188] [Flightor]: Unstuck attempt 36
[10:21:10:635] [Flightor]: Unstuck attempt 37
[10:21:12:080] [Flightor]: Unstuck attempt 38

in the air over winterspring

 

sigh

i said attach a log, not copy / paste the log window
How To Attach A Log [Kick]

 

There u go

 

then you didn't look... at all
--
thoroughly
read
the
first
post

(or at least the first line of the first post?!)

 

in the SVN in kicks sig -> https://kicks-scripts.googlecode.com/svn/trunk/

 

and what is the problem kick? HB???
I dont know rly why but only do that, if i go to the portal, try to fly but he cant only "open" the travel map, then i click manually and he return to the portal =( tell me what can i do.

 

restart hb

 

Hellfire Peninsiula not using optimal path for questing



In Hellfire Peninsiula this profie is not usig the optimal path for questing.
It waist hudge amount of time going the long way round (marked as Red arow)
Instead of using a much shorter path (marked as Blue)
If the bot need to do quests in the area (marked as Yelow), it will always take the red path instead of the blue one.
after it pickes up the quest, it will always use Red path to get to the questing area, and use Red again to get back to quest giver.

leveled alot of chars 20+, and all of them do thesame thing nomater ali or horde.
hawe the lates profiles form swn, lates honorbudy etc.
as i can recal it is a old problem the first char i leveled ~8month ago, had these isues, and it stil continues to this day.
so today i decided to report it.

 

I'm having trouble with my farmer toons stopping after zoning into mount hyal.

HB 5800
PB updated, multiprofile.

It takes portal to Mount Hyal, then move to this spot and just stops: <Hotspot X="1914.707" Y="-520.1742" Z="230.7821" />
If I move the character it will resume.

Report to HighVoltz: http://www.thebuddyforum.com/honorb...-multi-profile-farming-gb2-34.html#post483518

Reply from HighVoltz: http://www.thebuddyforum.com/honorb...-multi-profile-farming-gb2-35.html#post483555

 

Greennunu, Thanks for the post! The issue described regarding AutoEquip is an AutoEquip issue. You will want to post regarding that in the HonorBuddy Support Issues forum. The issues pertaining to the CC's described are specific to each of those you use, so you would want to post in the CC authors thread about the problem you encountered. Thanks for the post and good luck with your toon, Bobby53

 

*NEW* LazyRaider 2.0.0 available for download!

New version includes a number of bug fixes and the following new features:

• 
  [*=1]Auto Targeting - will assist the tank the you select. Thanks to Raphus uses the same base logic present in InstanceBuddy.
  [*=1]Sticky Tank Selection - no longer switches tanks when tank dies or goes out of range. Will remember the tank you selected and automatically clear/set the RaFHelper.Leader property (accessed by CC's and plugins) based upon the tank being in or out of range
  [*=1]Performance Options - inspired by Apoc's RaidBot. You may control each of the performance elements independently as needed to accommodate the CCs and setup you use
  [*=1]Max DPS button - sets the Performance options based upon your system and CC in use
  [*=1]Tank Selection window - now grouped by role with Tanks always appearing first for quicker selection

Note: I expect changes and possibly more control over target selection to occur based upon user feedback after a period of usage. If you are soloing or don't have a tank selected, you will have to select a target yourself.

Also, a couple nagging bugs are gone. The tank select message spam is fixed, it will now corrrectly reinitialize Singular if you start before entering a Raid group, and most (if not all) of the exceptions caused by a tank leaving group or leaving your zone should be handled.

See Post #1 in this thread to download. If you encounter significant issues, you can rollback to LazyRaider 1.1.1 which is still available for download from the same post.

 

nice!

 

This is extremely nice Bobby!

Will test this later in a 5 man group and see if my followers stick to my manualy played tanks target

 

Hey Kick, great profiles! I had a little issue on the Borean Tundra quests and my toon got stuck on the edge of one of the D.E.H.T.A. tents around <Hotspot X="3192.299" Y="5280.832" Z="51.34206" />. It's one of those places where your HB doesn't realize it's stuck and it looks like it's just sitting there humping the tent. It was on it's way to do the quest "unfit for death". Check around 4:30 on my log. It was stuck there for about 30 min till I moved it. I've attached a picture also of where it was stuck.

 

get me a good hotspot to runto that's outside of the camp and i'll fix it

 

Kick --

I don't know if I posted this before, but for some reason my bot is getting hung up on this quest (Our Mortal Enemies - Quest - World of Warcraft). He's at "Dead Eye" but he has no quest to give me. I've re-SVNed just to be sure that I have the most recent version of your file. I've also restarted the bot by stopping, closing, reopening, and restarting the bot. It still gets stuck on this quest.

Edit: I went into the profile and removed that quest completely after I looked it up on wowhead. It doesn't seem to be part of a chain, nor does it seem to have and prereqs. I'm running the bot now with it removed to see if that has any impact at on on the everything after it.

 

did you DC?

 

I DC'd before I got to this quest, if that's what you mean, but it was several quests before. I've been running it for a little less than an hour now since I started back up from the DC.