Hi again, Benh1337, Glad you got fixed up. This problem you are describing is not the responsibility of a profile, but of the Combat Routine. Its sounds like Honorbuddy is working as designed. But, you might look and see of the Combat Routine has some settings you can adjust for the behavior you seek. cheers, chinajade
Thank You chinajade for the help very fast.. i was expecting to be waiting like a couple of hours before i even got a reply. +100
Hi Benh. If you use Singluar as your CombatRoutine, click on Class Config in HB and under the tab Class Specifi, check the setting for Stealth Always... Set it to true if you want your rogue to always stealth. As for the problem with targeting, killing, running back and forth etc. Check if "Kill between hotspots" is checked in your HonorBuddy settings... If so, uncheck that, should help. You might wanna leave it checked and live with it though, since unchecking that will cause your toon to kite a lot of mobs ocationally when running to a new place.
is it possible to combine "Kick's 1-90 Mega Profile Pack" with DungeonBuddy via Mixed Mode? i tried but it did not work it always only used the questing bot base not the mixed mode base... any ideas?
Googlecode SVN seems to be down .. Happens with all the SVN links at the moment, not only Kick's. No big deal, will come back up
My character stays in the same zone for too long. i.e. it won't go to southern STV at level 31. Even with a fresh install. (of HB) Any solution appreciated.
I have an issue where the bot is stuck trying to get a quest I have already completed. Since I found an answer to a similar problem further back in the thread, I have done a fresh install of Honorbuddy and cleared all 4 caches AND kept WoW closed for more than 5min (about 15min to be exact) just like the help desk said. Is this still related to a corrupted cache or is it something else? Obligatory log. View attachment 9152 2013-12-12 18.02.txt
I don't know if this goes here, but I have a small bug report. I don't have a log either, but you'll understand what I'm talking about. When leveling from 70 to 80 the bot eventually has to go to Borean Tundra, which is does by taking the ship. As soon as the bot arrives, it goes of the ship, runs a bit on the bridge, doing some stuff - but then it decides to jump of the bridge to go in under the bridge and just chill there. It's not even stuck, it just stands there like it was intended, haha. While I was there I saw 2 other bots standing there, too. I tried starting the bot in Stormwind again, which led to the same problem. It's not really a problem if you just manually travel to Northrend.
This also happened to me in Western Plaguelands. Eventually I just leveled trough that zone manually and let the bot start in Eastern Plaguelands again. Worked almost flawless since!
My toon just finished the quests in Mount Hyjal at level 82, jumped the stormwind portal and bot stopped with the following error: Unable to evaluate/compile condition in If tag. Please check your profile. Honorbuddy stopped Edit> Started working when I manually selected to load the Deepholm profile and start again.
I've finished running my character through the Deepholm profile and there are ALOT of issues. I'd say about 90% of the instances where "FlyTo" is used and Land="true" the character arrives at the coordinates and HB begins to load tiles and lags the shit out of everything... I have seen it once or twice dismount after a long while but considering I'm at the computer and watching it while working I just click dismount myself and it'll eventually continue with the profile. This issues seems to be exclusive to the Deepholm zone. Unfortunately I do not have logs so I know mentioning this wont do much but I thought I would anyways. I have another character that will be entering Deepholm in about half a level and Ill mess with things when it gets there. If there's anything you want me to test, let me know. Just started running "[Fly][N - Quest] Uldum 83-85 [Kick] (Rev: 2934)" and I've noticed a couple things. On quest "Traitors!" (line 405) the character will not interact right away with the Neferset Frond if another player is in the vicinity. There happened to be a player there that went AFK and the bot sat there for a bit. It waits for about 45 seconds (I think, cant check anymore) and then interacts with it regardless. While not an issue that stops the bot it does look odd to be standing there for so long and fixing it just makes the profile run smoother. The debug output is from line 171 of "TargetAnalysis.cs". This is just how the quest behaviors work at the moment I'm guessing but if there was some kinda of argument or flag you can set to ignore players in the vicinity, I would add it. Second, when accepting "Escape From the Lost City" (line 464) there is a cut scene immediately after. During this cut scene the bot is spamming that it's stuck, not sure if its actually jumping around or not (I'd just be safe and assume it is). There is a commented if statement with a wait timer at line 465, don't know if its commented for a reason but 65 seconds should be long enough. Sorry in advanced for not posting logs, these issues were easy to pin point and seem too minor to even bother with logs.
While using the LK (Horde) profile, the character will not try to loot the Dead Mage Hunter bodies for the quest item for this quest: Rifle the Bodies - Quest - World of Warcraft The character will stand on top of a specific Dead Mage Hunter body every time, but does not attempt to target or loot the body. The character does not AFK out of the game, but does stand in one place indefinitely until you manually loot the quest item from that Dead Mage Hunter body, or another in the area. Upon looting the item, the profile will continue normally without an HB Stop/Start or restart.
While using the LK (Horde) profile, the character does not navigate properly to the quest kill objective. Quest attempting to complete: Marked for Death: High Cultist Zangus - Quest - World of Warcraft The character will stand outside of the pit (on the snowy terrain where all of the bears are) and not navigate properly back down into the pit and to the quest kill objective.