Hi, Tumbum, There is simply no way to help you or analyze the issue without a full log of the event. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Revrite, This is a partial log and unsuitable for chasing problems. If you have this problem again, please attach the full log of the event. cheers, chinajade [size=-2]Ref: Revrite's original post[/size]
Hi, Cowboy88340, There is a problem with this log file that makes it unsuitable for analyzsis. If the problem occurs for you again, please show us a fresh log. cheers, chinajade [size=-2]Ref: Cowboy88340's original post w/damaged log[/size]
Hi, Bart316, and many thanks for the logs! Your Singular appears to be seriously mis-behaving. I'd try updating to Honorbuddy '.744, and if the problems still persist, show us a fresh log, please? cheers, chinajade [size=-2]Ref: Bart316's Unga Ingoo problems w/log files[/size]
[11:02:52.365 D] Changed POI to: Type: Kill, Name: Iron Juggernaut Would be nice to know how you see in this log that my Toon was running a bit to much left and pulled the IRON JUGGERNAUT Boss. Just to understand the Log. At the moment i just see that my Toon get a Kill Command and dismount and start Fight. Ok think this is normal, like when the complete Raid is doing a Timer and the Tank start the Fight. But here, my Toon start the Fight because he didnt run complete on the right side. Sorry cant do a fresh Picture, next time when i run in this Raid i will Update it. But the Red Circle is the Boss starting Position. The Red Line is the correct way without pulling the Boss. But all my Toons from Tauren down to Goblin are running the Yellow Line and always pull the Boss when running to the Group. I know this was fixed and worked well some releases before.
Hi, Namednoob, and many thanks for the logs again! We've opened HB-965 ("Halls of Stone: Problems interacting with Brann Bronzebeard") against this issue. This again looks like a boundary-condition problem where the leader was trying to give other party members a chance to turn in a quest before talking to Brann to advance the encounter. We assume: Party-of-five No party members had the quest If we are wrong in these assumptions, please let us know, as it will help localize the specifics of the boundary condition. cheers, chinajade [size=-2]Ref: Namednoob's problem report w/logs[/size]
Hi, Sd6795, The party members should not be leaving the dungeon, unless you had configured it such that your DPS was the DungeonBuddy 'leader'. In fact, our observations are that Dungeonbuddy will continue clearing trash in the dungeon, even if one DPS is missing (gone to rez, sell, or repair). It is also our experience that Dungeonbuddy clears all trash to make safe a run back from the entrance. In short, what you are describing is not the way Dungeonbuddy operates. Before we can take any action, we must see the full log that captures the event, please. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Razer, This is clearly a user error. If not, you will need to attach the full log of the event that demonstrates otherwise. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Crujones, Sjd6795 is spot on—we need a full log of the event in order to analyze an issue. Please be so kind as to toss the log, the next time it happens for you. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Phasechange, This can happen if the CombatRoutine is fighting with Dungeonbuddy to "get out of the Red/Blue/Green stuff". You probably need to go into your Combat Routine settings and disable all movement. Then go into DungeonBuddy and set "Combat Movement" to true. If that doesn't have you off-and-away, please attach the full log of the event, so we can see what's going awry. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Merek, There are several places to jump down in Gnomregan, and we're unclear about the location to which you are referring. The current Gnomeregan script jumps down using the parachutes after Electrocutioner 6000 is killed. Other than that, DungeonBuddy does not in general bypass content. Such content represents experience, loot, and reputation gains, which are some of the primary goals of DungeonBuddy. DungeonBuddy also clears trash that makes a "run back from the entrance" unsafe for a party member. You can find more information about this in the Frequently Asked Questions. cheers, chinajade
Hi, Paperc07, DungeonBuddy should be hitting "OK". If not, you've probably configured something incorrectly, or damaged your DungeonBuddy installation. To provide assistance, we will need to see your full log of the event, please. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Haloman, and many thanks for that log! [17:16:48.932 N] [DungeonBuddy]: Leaving group. Reason: Completed [17:16:48.934 N] Removed blackspot for Right Entrance Steps [17:16:48.935 N] [DungeonBuddy]: Left dungeon: Tal des Ewigen Kummers It appears the DungeonBuddy believes this wing to be 'done' for you. We assume this is indeed not the case, and have opened HB-966 ("Siege of Orgrimmar, Vale of Eternal Sorrows (wing1): Prematurely detecting 'done'?") against this issue. Very sorry for the inconvenience. cheers, chinajade [size=-2]Ref: Haloman's problem report w/log[/size]
Hi, Tumbum, and MANY thanks for the log and screenshot! To answer your question, there are many clues in the log as to why a problem occurs. For instance, the stuck handler may have malfunctioned and dropped a blackspot in a VERY bad place, causing your toon to path around things. Or, the pathing could've been altered for other reasons. The team has access to the mesh tools, and there may be enough coordinates in the log to reconstruct the specifics of what happened. In any case, we've opened HB-967("Siege of Orgrimmar, Gates of Retribution (wing2): Running too close and pulling Iron Juggarnaut") against this issue. I'm sure the screenshot will be VERY helpful in identifying the problem, and figuring out what corrective actions to take. cheers & thanks again, chinajade [size=-2]Ref: Tumbum's problem report w/log & screenie[/size]
[DungeonBuddy]: Leaving group. Reason: Followers are not in group. Have a huge problem I cant fix myself. Everytime my 5 man dungeon team goes in to an instance the party leader leaves and says followers are not in group. They most certainly are! Log is attached.
Hi, Wtfmofo, and thanks for the log. Did you remember to set the names of your followers in Leader's DungeonBuddy settings? cheers, chinajade [size=-2]Ref: Wtfmofo's original post w/log[/size]
On the occasions that this has happened to me its always been with other players, where they proceed to give me the "wtf are you doing?" response Haha. I'll upload a log as soon as I get to it, currently leveling a Warrior up through the BC Dungeons which are all fine.
I have a question, whenever i do a LFR queue, when i get inside the raid it always pops up this "Dont be AFK bla bla bla" window. Can i somehow turn it off? Like an option to choose when i want it on or not.
Yes, both of my reports are party-of-five (with my bots), I could probably send you the other members log if you want, but honestly I don't recall weather or not they had the quest. [HR][/HR] Yes, full party-of-five botting this