Hi, Anwira, "Navigational issues" like you describe are not problems with the profile. I believe the particular issue has been repaired, and my guess is you are using an outdated Honorbuddy. If the problem persists, you need to report the problem to the Navigation thread. The first post in that thread describes what information is required when reporting a navigational issue. That first post also tells you how to acquire the needed information. In the future, whenever you ask for assistance, please attach your full log that captures the issue. Without it, we've no way to analyze the problem. Ref: [Guide] How to attach your log cheers, chinajade
<waves at Tumbum>, Many thanks for this, Tumbum. The problem has been rectified in v3006. cheers, chinajade [size=-2]Ref: Tumbum's problem report w/log[/size]
Profile: [H - Quest] 12-58 K-EK [Kick] Quest: War on the Woodpaw (War on the Woodpaw - Quest - World of Warcraft) Description: Better HotSpots. I make some new and better HotSpots for this Quest. Replace: Code: <Quest Name="War on the Woodpaw" Id="25363"> <Objective Type="CollectItem" ItemId="9237" Name="Woodpaw Gnoll Mane" CollectCount="10"> <CollectFrom> <Mob Name="Woodpaw Alpha" Id="5258" /> <Mob Name="Woodpaw Reaver" Id="5255" /> <Mob Name="Woodpaw Brute" Id="5253" /> <Mob Name="Woodpaw Trapper" Id="5251" /> <Mob Name="Woodpaw Mongrel" Id="5249" /> <Mob Name="Woodpaw Mystic" Id="5254" /> </CollectFrom> <Hotspots> <Hotspot X="-4761.432" Y="480.3905" Z="24.23677" /> <Hotspot X="-4787.737" Y="809.2564" Z="129.8035" /> </Hotspots> </Objective> </Quest> With: Code: <Quest Name="War on the Woodpaw" Id="25363"> <Objective Type="CollectItem" ItemId="9237" Name="Woodpaw Gnoll Mane" CollectCount="10"> <CollectFrom> <Mob Name="Woodpaw Alpha" Id="5258" /> <Mob Name="Woodpaw Reaver" Id="5255" /> <Mob Name="Woodpaw Brute" Id="5253" /> <Mob Name="Woodpaw Trapper" Id="5251" /> <Mob Name="Woodpaw Mongrel" Id="5249" /> <Mob Name="Woodpaw Mystic" Id="5254" /> </CollectFrom> <Hotspots> <Hotspot X="-4832.566" Y="178.9826" Z="55.63086" /> <Hotspot X="-4878.176" Y="221.9672" Z="51.92131" /> <Hotspot X="-4932.313" Y="376.6442" Z="16.39896" /> <Hotspot X="-5000.628" Y="363.3462" Z="24.00362" /> <Hotspot X="-4997.363" Y="407.893" Z="16.7143" /> <Hotspot X="-4965.742" Y="467.2032" Z="17.51101" /> <Hotspot X="-4876.624" Y="464.0493" Z="18.91083" /> <Hotspot X="-4906.95" Y="589.4405" Z="18.83875" /> <Hotspot X="-4840.104" Y="536.9785" Z="20.1462" /> <Hotspot X="-4795.386" Y="609.092" Z="33.71103" /> <Hotspot X="-4886.671" Y="676.9141" Z="42.29858" /> <Hotspot X="-4948.479" Y="660.5605" Z="43.26793" /> <Hotspot X="-4809.38" Y="879.075" Z="143.3025" /> <Hotspot X="-4755.33" Y="849.1094" Z="143.155" /> <Hotspot X="-4774.22" Y="913.054" Z="143.8164" /> </Hotspots> </Objective> </Quest>
Hi, SanderrNL, Thank you for the report. We've captured the issue to Known Bugs List: BC 58-70. cheers, chinajade
Profile: [H - Quest] 12-58 K-EK [Kick] Quest: Alpha Strike (Alpha Strike - Quest - World of Warcraft) Description: I added 3 more Hotspots for this Quest, to get more NPCs and so finish the quest more faster. Replace: Code: <Quest Name="Alpha Strike" Id="25364"> <Objective Type="KillMob" MobId="5258" Name="Woodpaw Alpha" KillCount="5"> <Hotspots> <Hotspot X="-4761.432" Y="480.3905" Z="24.23677" /> <Hotspot X="-4787.737" Y="809.2564" Z="129.8035" /> <Hotspot X="-4793.13" Y="838.3602" Z="144.0373" /> </Hotspots> </Objective> </Quest> With: Code: <Quest Name="Alpha Strike" Id="25364"> <Objective Type="KillMob" MobId="5258" Name="Woodpaw Alpha" KillCount="5"> <Hotspots> <Hotspot X="-4761.432" Y="480.3905" Z="24.23677" /> <Hotspot X="-4787.737" Y="809.2564" Z="129.8035" /> <Hotspot X="-4793.13" Y="838.3602" Z="144.0373" /> <Hotspot X="-4809.38" Y="879.075" Z="143.3025" /> <Hotspot X="-4774.22" Y="913.054" Z="143.8167" /> <Hotspot X="-4755.33" Y="849.1094" Z="143.1548" /> </Hotspots> </Objective> </Quest>
Hi, Daarno, and many thanks for this repair. Your recommendations have been folded into v3007. cheers & thanks again! chinajade [size=-2]Ref: Daarno's problem report w/recommended repair[/size]
Hi, Judasz, No, they are not dead?not even close. We have many responsibilities that keep us incredibly loaded?profiles, quest behavior repairs, plugin repairs, bug isolation, test bed creation, Wiki (Honorbuddy & Gatherbuddy Wiki - Buddy Wiki), article writing in the HelpDesk, responding to the Community developer forum, working with individual developers to solve problems in Skype, handling the various forums, etc. Forum duty alone consumes 4-8 hours per day. Sometimes, we can only respond to posts in this particular thread a couple of times a week. On top of the heavy load, it is Holiday season, and personal matters to attend. If you look at the profile pack's changelog (https://code.google.com/p/kicks-scripts/source/list), you will quickly discover that the profile pack is under constant improvement?much of it not 'obvious'. Many many of the improvements are thanks to Community feedback. And for that, we thank them very very much! Many kudos go to MaxMuster in particular for all of his significant improvement suggestions of late. cheers, chinajade
Hi, Ext3ndedBurs, The problem you are describing doesn't sound like a profile problem at all, but something wrong with your Honorbuddy installation. If this happens again, please attach the full log that captures the issue, so we have somethingto analyze. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Jimmypile, The only way to 'skip a quest' is to comment out the <Pickup> line in the profile, then drop the quest from your log. However, our preference is always to repair the damaged quest rather than skip it. Skipping quests can lead to further problems down the road. This article should shed some light on 'why': HelpDesk: Quest giver is not offering expected quest The next time something goes sideways for you, please attach the log that captured the issue. We'll analyze it, and try to figure out a better way to solve the problem. Testing quest profiles is thorny to say the least. Differences in whether a class is melee or ranged, has a pet or not, can shapeshift or not, uses particular WoW addons, etc. can significantly impact the 'smoothness' of the quest. Although we try to test with all categories of toons, sometimes problems only manifest for certain people--perhaps you were standing in the wrong place when another player interfered with what you were trying to do. Only a log can help us further refine such peculiarities. cheers, chinajade
Hi, John1337, Many thanks for the repairs! Your recommendation has been folded into v3008. We had to make similar changes for the Paladin recently. Bliz seems to keep tampering with those class-specific newbie quests... grrrrr. cheers, chinajade [size=-2]Ref: John1337's problem report w/recommended repair[/size]
Thanks once again, MaxMuster! Your recommendation has been folded into v3009. We agree with you regarding the quest overrides. Most are simply unneeded on the modern Honorbuddy, and need to be ripped out. Honorbuddy is very good about figuring most things out for itself using the data contained in the WoWclient. cheers, chinajade [size=-2]Ref: MaxMuster's problem report w/recommended repair[/size]
Thanks, MaxMuster! The change has been folded into v3010. cheers, chinajade [size=-2]Ref: MaxMuster's enhancements[/size]
Hi, Lasesp1999, and welcome aboard. "Not attacking" is not usually a profile problem. There is no chance of assisting you with any problem, if you don't attach the full log that captures the issue. Please see the guide for Reporting Problems or Seeking Assistance. cheers, chinajade
Hi, Mwatson2, and many thanks for the log. This is a navigational issue with Honorbuddy, and we've opened internal bug report HB-288 for the issue. The problem is that chasm is 'kinda indoors / kinda outdoors'?so, Flightor is getting confused. The next time we're through the area, we'll see if there's any tuning we can do in the profile to work around the issue. In the meantime, your work around is to do the last two objectives manually. Sorry for the inconvenience. cheers, chinajade [size=-2]Ref: Mwatson2's original post w/log[/size]
Thanks once again, MaxMuster! Your improvements have been folded into v3011. cheers, chinajade [size=-2]Ref: MaxMuster's improvement suggestion[/size]
Hi, MaxMuster, The new hotspots have been folded into v3012. cheers & many thanks, chinajade [size=-2]Ref: MaxMuster's improvement suggestion[/size]
Dunno if this is profile or HB. I was going to Twilight Highlands and got the infamous "Instance not found, Aborting Transfer" message. Logged out and back in since that is the only thing that helps usually. Once in, I got up to Twilight Highlands and started HB, all it did was say that it couldn't navigate to the flightmaster, jump on my fying mount, fly to the entrance of Blackrock Mountains instance and get stuck there. Tried clearing caches, clean install of Honorbuddy... Just did the same thing, jumped mount and headed to blackrock mountain. If I hearth to Stormwind and try to start there, it flies to the old baracks, lands at the top floor, runs straight ahead into the first room and gets stuck in the corner and just stands there. Very odd.
Hi I have a 82 rogue that I just want to level from their I cant find a link that can make me do that
Is there meant to not be a quest behaviours folder to copy over anymore ?. sorry havent used questing in a long time now.