Hi, Snakemetal, We'll toss one guess... Dungeonbuddy is going for repair or to unload bags. If that is not your issue we'll need to see the full log the next time the issue happens for you. Ref: [Guide] How to attach your log cheers, chinajade
Hi, Askperk, and welcome aboard! To diagnose problems like this, we need to see the full log that captures the event. Please be certain to attach the log, the next time the issue happens for you. Ref: [Guide] How to attach your log cheers, chinajade
So I am using the singular profile and its still completing the dungeon, going to the exit, and just sitting at the exit. If I have it go outside it goes back in and starts the dungeon over again but it does just go out its self.
Hi, Tigerlady3012, We run the Temple of the Jade Serpent all the time, and don't have this problem. A Tank may initially engage the mob in the water to get enough threat, then the tank pulls it to the solid ground in front of the closed door behind the boss. Ranged toons may occasionally move through the water, but they tend to stay on solid ground. Our guess, is that you are using a (non-Singular) Combat Routine that doesn't handle some of the details required in of a PvE combat routine. If that is not the case, we will need to see the log, please. Ref: [Guide] How to attach your log cheers, chinajade
Restarted it and everything just to make sure it was a clean file attached. Here you go. View attachment 48264 2014-06-16 12.13.txt
Hey Chinajade, I'll toss in my wild guess - maybe Deathsmind meant the toon is actually stopping at the exit location, not the Honorbuddy? If that is the case, I'd add Stratholme and Mana-Tombs to that list as I've noticed the toon stops just a single yard from where the instance portal is being triggered. That means tapping the up arrow key a little will successfull port the toon out and bot continues as usual. In other words, some instances need to get the exit portal location fine tuned. Sometimes the portal graphics location is misleading, and you need to make a couple of steps forward to get actually through. Edit: Log from Mana-Tombs, here you go!
Hi, Deathsmind, and many thanks for the log. From this log, we see Dungeonbuddy exit the dungeon, then it appears you stopped Honorbuddy. [19:19:05.011 D] Activity: Dungeon completed. Moving to Portal. [Reason: Completed] ... [19:19:05.077 D] Activity: Dungeon completed. Moving to Portal. [Reason: Completed] ... [19:24:09.909 Q] Bot stopping! Reason: User pressed the stop button [19:24:09.918 N] [DungeonBuddy]: Left dungeon: Scarlet Monastery [19:24:09.923 D] Changed map(s) to ScarletMonasteryCathedralGY [19:24:09.925 D] Activity: Honorbuddy Stopped ...<log effectively stops here>... So according to this log, Dungeonbuddy made no attempt to re-enter the dungeon because you stopped it as it was exiting the Dungeon. Basically, we can't help you because this log does not capture the problem you describe. Of course, you're welcome to try again. cheers, chinajade [size=-2]Ref: Deathsmind's follow-up post w/Singular log[/size]
Hi, Junk, We appreciate your hypothesis. But this log shows you exiting the dungeon: [20:22:56.114 N] [Singular] *Battle Shout on Me @ 100.0% [20:27:08.412 N] Stopping the bot! [20:27:08.413 Q] Bot stopping! Reason: User pressed the stop button [20:27:08.478 N] [DungeonBuddy]: Left dungeon: Mana-Tombs ...<log effectively stops here>... Will try to do some Mana Tombs farm runs soon, and see if the problem can be replicated. We've also opened a Draft bug report HB-932 ("Not exiting some dungeons in "Farm" mode"). cheers, chinajade [size=-2]Ref: Junk's original post w/log[/size]
Ill try and upload a video. It never exits. It sits at the exit but never moves forward. I have to manually move it forward before it starts up the next dungeon. You can see by the log it sat at the exit for 4 minutes before I turned it off.
Hi, Deathsmind, Your offer to make a video is kind, but please don't bother. We've already written a bug report to have this issue investigated. Thanks for pointing out that timing issue, I missed it and will supplement the bug report with it. cheers, chinajade
Hey Chinajade, thanks for your response. You've cited the correct part of the log, but the color highlight went to the wrong part, please see this: Code: [[COLOR="#00FF00"]20:22:56[/COLOR].114 N] [Singular] *Battle Shout on Me @ 100.0% [[COLOR="#FF0000"]20:27:08[/COLOR].412 N] Stopping the bot! [20:27:08.413 Q] Bot stopping! Reason: User pressed the stop button [20:27:08.478 N] [DungeonBuddy]: Left dungeon: Mana-Tombs In between the two lines there's ~4 minutes difference where the bot was doing literally nothing, so I stopped him manually to post the log. Deathsmind's log shows the very same thing - he stopped the bot after it was doing nothing for 5 minutes. Thanks!
Indeed, the bug report has the correct information highlighted. Once again, VERY sorry for missing that timing detail when reading the log. cheers, chinajade
When I was in Unga Ingoo Scenario, the bot wouldn't do what it need to do to put the brew in the pot. It just stood around. I know this stuff worked yesterday. So i dont know what has changed. Any help would be great. Also there are 2 more logs added, because some of the scenarios it would start the fights but out of no where stop moving and wont even attack mobs.
Thanks for the update! I will give a fresh install a try as the machine has been rebooted several times...thanks!
Hey everyone, I am wondering if people have quests turned on with RAF toons. I remember a while back sometimes they would turn the quest in while they are not together or one will do the quest and the other will not then their levels will get far away from each other.
DungeonBuddy DungeonBuddy stops on last pull in Lost City of the Tol'vir and will not go out just sets there
Using .742 release, noticed this in Stratholme first and now in Blackrock Depths.I did not follow the bot closely, might have happened in other places too.It seems that when there are no mobs in target distance, it pauses long enough for it to be a nuisance, an exception occurs and then it resumes. Attached is a rather huge log...At line 56420, for example, the logs shows such an exception.