This has stopped working for me, I cant see anything odd looking in the logs but now when I set it up to do my LFRs is ques for them, enter the raid and then just stands at the entrance doing nothing. If I manually move to the boss it then begins to sometimes move to certain areas but thats about it. Wont attack boss or follow the raid to the next boss etc etc. I've deleted HB and had a fresh install but still have the same problem. Its started happening since the HB update
It is no longer possible the select any specific raid in "Queue For Raids Not Completed". Same for heroics... Was working yesterday
Yeah it seems if you choose a raid in the Queue for Raids not completed, it also checks it off in the "Specific Raid" pulldown. Then you get tons of error messages where you're queueing for too many raids.
My Honorbuddy crashed every time i start DungonBuddy for LFR SOO Raids. Summary: Honorbuddy crashed after a vew min. Class: Paladin CustomClass: Singular Role: HPS/DPS Queue Type: Random Queue Party Mode: Off Dungeon: LFR SOO
Summary: toon don't move in dungeon. If I move him a bit - he runs for some time, follows tank and hits mobs, but after looting or sometimes without any visible reason he stops again. It began yesterday, everything worked great a day before. Class: Frost mage CustomClass: Singular Role: DPS Queue Type: Random Queue Party Mode: Off Dungeon: Maraudon and others (lvl 34-35)
Yeah I had an issue today as well, I wanted to farm blood furnace for some cloth with a 90, usually there is no problem, but today he wouldn't do that at all. I though may be i needed a clean HB reinstall, but since everything else work and other people got some problem it might be the bot not working properly.
Just wondering, in my dropdown box I do not have the option "Queue For Raids Not Completed" any longer. It just says select best available. Is this an extremely old option or a relatively new change?
From your log file: [16:14:34.126 D] (Singular) AllowMovement: None Change settings from none to auto... For the others with same or similar problem: 1. Check that your using a routine that can handle movement (if in doubt, use singular) 2. Check that you allow singular to handle movement. 3. Give me rep xD
Post logs, but feeling pretty confident saying you're using a CC that dont support movement or somehow movement got disabled in singular. Check both, post logs.
I've tried in Singular "None", "Auto" and "All". Toon didn't move at all with "Auto" and "All" settings. "None" - as I described, after I klick RMB once to move him manually, then he moved and took actions for some time.
Hi, Chaser, and Robbdeman, For now limit your instance selections to 5, please. The repair for this problem should be in the next drop. We've captured this problem to the Known Issues list. cheers, chinajade
Hi, Hell-Razor, This article provides your answer: Honorbuddy:HelpDesk:Using Questing with Mixed Mode - The Buddy Wiki chers, chinajade
Hi, Macatho, Highvoltz has tried and tried to replicate the Rattlegore issue, yet has been unable to cause any kind of crash. People that have this problem have not been forthcoming with logs, so that's why the problem remains. cheers, chinajade
These posts have been archived, since no logs have been provided. If you need assistance, please restate the *specific* problem, and attach the full log that captures it. cheers, chinajade
Hi, Lost Fear, In .733, the "Queue For Raids Not Completed" is present. It sounds like your Honorbuddy installation is damaged. HelpDesk: "Clean installing" Honorbuddy If this doesn't have you off-and-away, you simply must attach the full log that captures the issue. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Visermi, and thanks for the log. Three issues. First, you have not selected Random Dungeons as you believe, but you've queued for Specific Dungeons: [16:18:32.643 N] [DungeonBuddy]: Dungeon type is set to Specific [16:18:32.643 N] [DungeonBuddy]: I have selected the following dungeons [16:18:32.643 N] [DungeonBuddy]: Непроглядная Пучина [16:18:32.643 N] [DungeonBuddy]: Тюрьма Штормграда [16:18:32.643 N] [DungeonBuddy]: Ульдаман [16:18:32.643 N] [DungeonBuddy]: Мародон - Зловонная пещера [16:18:32.644 N] [DungeonBuddy]: Мародон - Оскверненный грот [16:18:32.644 N] [DungeonBuddy]: Мародон - Поющие водопады Second, when queuing for specific dungeons, please limit your list of selections to 5. This appears to be a Bliz limitation, and has already been repaired for the next (post-.733) Honorbuddy drop. And, Tomten has nailed the third issue... cheers, chinajade [size=-2]Ref: Visermi's original post w/log[/size]
Just an FYI... To prevent problems, Highvoltz has indicated that no more than 5 dungeons should be queued for. He indicated this is already repaired in the next (post-.733) Honorbuddy drop. For now, we've captured this problem to the Known Issues list. cheers, chinajade