"Tanking is only supported in party mode with 4 other bots that belong to you"
Is this literal? What if the target dungeon is something that can be 2-4 manned and running as an exclusive party - will it restrict that functionality because there isn't a formal 'self managed' 5-man group?
It looks like you're having a combat routine issue.Really cant get db work! The pg is queing but when it enter my warlock think is a dps and dont follow the group! I have already tried with mani CC but same resoult! Dunno what to do! Heres the log hope someone can help meView attachment 82895
HB release still uses the DB version with that bug, same with HB BetaPriest still queueing wrong at least for LFR. Fresh Install of 535.
I re-worded it to "Tanking is only supported in party mode when all other group members are listed as followers and group size is the max allowed for the content queued for e.g. 3 for Scenarios, 5 for dungeons and 25 for LFR"
This restriction is only in place for the LFG system.
I'm, not sure if this issue was updated in the scripts before the "No Script Found" ordeal, but heres the issues I had today
Arena of Annihilation
All three bots attempted to move to the gong, but instead of running to it, the ran to the closed door, and continuously pathed into it. If I manually started the Arena fight, the bots wouldn't engage in combat.
Scarlet Halls
Class: Dk (tank), Paladin (Holy), 3 dps (mage, feral druid, lock)
CustomClass: Singular, TuanHA, CLU, Superbad, PureRotation
Role: All
Queue Type: Random Heroic
Party Mode: On full group
Issue: The bots for some reason could not get passed the Houndmaster. They continuoulsy targeted the hounds, and never the Houndmaster. Must have wiped a million times before I noticed. It was reported before, but on Armsmaster, they had trouble with the whirlwind.
I re-worded it to "Tanking is only supported in party mode when all other group members are listed as followers and group size is the max allowed for the content queued for e.g. 3 for Scenarios, 5 for dungeons and 25 for LFR"
This restriction is only in place for the LFG system.
I see. Thanks for the info on Arena.Arena of Annihilation has mesh issues caused by invisible walls. I am told this is fixed but must not be on mesh server yet.
Do the dps target the hounds that are not attacking group? If so that shouldn't be happening. Make sure targeting is disabled in your combat routines.
For the Armsmaster I had issues getting caught in the whirlwind if my latency was high (700ms+). I'll see if I can make some changes to script so it can avoid whirlwind even with high lag.
I have a confusing question to ask if anyone knows what might be going on and what the difference might be.
My laptop will run dungeonbuddy without a problem, but my desktop will give me "[DungeonBuddy 435]: Warning: There was a 2.2089844.208 second delay after last pulse" this all the time, and whenever this happens, my CC stops and the bot doesn't freeze as in the program has frozen, but rather the bot just stops doing something until the next few seconds. This can happen for up to a whole minute at a time of doing nothing and it pulses for 2-10 seconds.
I'm currently running, out of my 5 man group, my heals and tank and one dps on laptop just so they can survive. It's impossible to even get to a boss running all 5 bots on my desktop, as the healer doesn't heal the tank. The two dps on my desktop are of no use.
Anyone know why dungeonbuddy would pulse so often, and why it would only happen on my desktop and not my laptop. Both laptop and desktop are running the latest HB build and dungeonbuddy auto update scripts are enabled.
EDIT: I'm not sure if this was a bug report or improper configuration or what, so I didn't fill out a bug report form.