The wierd thing is that I only seem to have issues for the most part with classes that actually HAVE some ranged attacks, singular just doesn't use them... go figure. There were some issues with the boards yesterday, thats why it was showing you as a guest, but your posts show up as you now.
Yeah, I noticed they have been applying some fixes. Seems to be fine(ish) now. You're right, singular is a bit stupid. I've actually figured out which part of the singular code causes that behavior but I have no idea (yet) on how to fix it. It thinks the mob is just too far away and tries to pull it (provoke/taunt), CC it (paralysis) and then rotates ranged abilities (including c.rackling jade lightning) to bring the mob closer. The problem is that it's moving around at the same time, cancelling the (channeled) ranged cast before it does any actual damage. I even fixed the code so it actually stands still for c.rackling jade lightning, but that interferes with the regular mob-pull ability. If I figure out a way to detect whether a mob is actually reachable (i.e. it's just too far away or out of los) or unreachable (because it's flying), I could fix the code. Well, maybe next week... By the way, today the profile skipped 2 quests: "The Edge of Winter" and "A Leg Up". Also, it tries to do the "Gormok Wants His Snobolds" quest but never throws the net. After a few seconds it just flies back up to the tournament grounds. I restarted the profile after it had completed all the other quests but it only flew to the snobold place and then back up to the tournament grounds. EDIT: seriously? the forum is censuring *****ling jade lightning?
Yeah, for the second try I cleared the cache. It's now always the first thing I try It skipped the Edge of Winter for the Exodar quests.
I'll take a look at the Exodar valiant quests, they are the only ones I haven't been able to test myself. Gormok has always been a bit buggy for me, but I will take a look. My only other suggestion is re-install HB, I have had to re-install mine recently when it went all wonky on me.
I'll try again tomorrow and let you know. Exodar is the last set that's missing for me. After that, it's only 400 more Champion's Seals -.-
I felt your pain, which is why I made this profile set... of course I have 11 Alliance 90's and a horde 90, so for me it was almost a must. 400 seals would only take me 4 or so days, lol. (I'm guessing you are buying mounts though, so I could buy 10 mounts in 8 days or so.)
Humm... I could also run it on 5 more level 90s. But then I would have to get to exalted with the right faction to buy the mount... meh. I'll just run it for 3 more weeks. Less hassle.
Don't forget you only have to be exalted to buy the mount for a specific faction if it is not your "home" faction. IE, you could buy the stormwind mount on a human without being exalted.
Yeah I know. But the missing mounts are the ironforge+gnomeregan+exodar mounts. And I have no level 90 of any of those factions. Do you know if the Argent Hippogryph has any reputation / quest progress requirements?
Just delete the file c:\Users\*\Documents\Hbuddy\Quest Behaviors\ArgentTournament\BattleofTheCitadel.cs (or move it to the Desktop, temporarily).
Greetings, as also sent in PM, soon after the update via svn i get this error: Starting the bot! Currently Using BotBase : Questing Can not start quest bot - this profile does not contain a quest order!
You need to copy the quest behaviors from the SVN repo to this folder: c:\Users\Paolo\Documents\Honorbuddy\Quest Behaviors\ArgentTournament\ Make sure the contents of the c:\Users\Paolo\Documents\Honorbuddy\Quest Behaviors\ArgentTournament\ folder look like this EXACTLY: A-AtTheEnemysGates.cs A-BattleofTheCitadel.cs A-TheGrandMelee.cs TheGrandMelee.cs AtTheEnemysGates.cs GetKraken.cs SpecialTurnIn.cs Right now you have them in a subfolder called "Nuova cartella" (new folder?). Make sure that folder doesn't exist and that ONLY the files listed above exist.
That goes beyond my humble HB expertise Oo I'd do a complete reinstall of HB (uninstall, delete folder, install) and try again. It looks like you have a lot of outdated quest behaviors in your installation.
