What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Randomly accepts, zones in, then instantly drops group when running Random Scenarios.

Dagarle

New Member
Joined
Oct 31, 2012
Messages
5
Reaction score
0
While running Random Scenarios with Dungeonbuddy it will randomly accept the group, zone in, and then just drop group gaining me a 30 minute debuff. It has done this on my pally, dk, and shaman. I have not been able to see a pattern really as it will run a few fine then screw up, so I'll log over to another toon, run a few fine, etc etc. It's not just a certain instance either, but a couple different ones. Anyone else experiencing this error? Have a fix? because I have already done the complete clean new install and it still does this, two days in a row. Thanks.
 
Probably not supported, submit log (or just read in the window if it says "this dungoen is not supported, blacklisting")
 
Yea I tried to find a log but I had about a dozen dated from today, opened a couple, and just lol'ed at them because I really had no idea what to look for to see if it was the one I needed. If it does it again I will just get the most recent one made? I will also keep an eye on the scrolly window to see if it says not supported, but I dont remember it saying that the time I saw it actually happen. Just accepted. zoned, and dropped.
 
Just happened. It was in the new Lions Landing scenario. This is from the scrolling window.

Enabling Check at 20:37:16Will Run Next Check At 20:42:16
[DungeonBuddy 401]: Dungeon is considered complete in 30 seconds. Reason: Completed
Not in game
Your Level 90 Draenei Elemental Shaman Build is
... running the DungeonBuddy bot in RAF 0m Party as Combat Only in Shrine of Seven Stars
DungeonBuddy Bot detected... ShamWOW fast attack targeting disabled
>>> Left/joined a group, Initializing...
^OPERATIONAL MODE CHANGED: initializing...
Your Level 90 Draenei Elemental Shaman Build is
... running the DungeonBuddy bot Solo as Combat Only in Shrine of Seven Stars
DungeonBuddy Bot detected... ShamWOW fast attack targeting disabled
[DungeonBuddy 401]: Queuing for Scenarios
[DungeonBuddy 401]: Queuing for Random Mists of Pandaria Scenario
Enabling Check at 20:38:15
Will Run Next Check At 20:43:15
[DungeonBuddy 401]: Accepting dungeon invite
Not in game
>>> Left/joined a group, Initializing...
Your Level 90 Draenei Elemental Shaman Build is
... running the DungeonBuddy bot in RAF 0m Party as Combat Only in Krasarang Wilds
DungeonBuddy Bot detected... ShamWOW fast attack targeting disabled
Your Level 90 Draenei Elemental Shaman Build is
... running the DungeonBuddy bot in RAF 0m Party as Combat Only in Krasarang Wilds
DungeonBuddy Bot detected... ShamWOW fast attack targeting disabled
[DungeonBuddy 401]: Dungeon completed. Leaving. [Reason: None]
[DungeonBuddy 401]: Left dungeon: Brewmoon Festival
Not in game
Your Level 90 Draenei Elemental Shaman Build is
... running the DungeonBuddy bot Solo as Combat Only in Shrine of Seven Stars
DungeonBuddy Bot detected... ShamWOW fast attack targeting disabled
Enabling Check at 20:39:14
Will Run Next Check At 20:44:14


Dont see anything about blacklisting.


I think this is the right log. the most recent one with my shaman in it as that's the one this just happened on
 

Attachments

Last edited:
Just got this when in the new Lions Landing scenario


[DungeonBuddy 401]: Queuing for Scenarios
[DungeonBuddy 401]: Queuing for Random Mists of Pandaria Scenario
[DungeonBuddy 401]: Accepting dungeon invite
Not in game
[Singular] Your Level 90 Gnome Frost DeathKnight Build is
[Singular] ... running the DungeonBuddy bot 3m Scenario in Krasarang Wilds
[Singular] Context changed, re-creating behaviors
[DungeonBuddy 401]: No script found for dungeonId: 590
[DungeonBuddy 401]: No profile found for dungeonId: 590


It didn't drop group though.
 
[DungeonBuddy 401]: No script found for dungeonId: 590
[DungeonBuddy 401]: No profile found for dungeonId: 590

I dont know if you mean you know this is the error or not but this is the error
:o
 
report it under DB thread plz
 
Back
Top