+10 from me too! I am capping valor on 10-12 chars per week via LFR or premade (All 3x are mine) HC Scenarios, and since the last build .747, I do have the very same problem, happening in both the LFR and HC Scenarios. Hopefully, when this happen in scenario, I can invite back the character, which have left the scenario, but with LFR I have to wait 30min, obviously. Dont have accurate statistics, but the problem usually replicates around 10-20% off the time, but sometimes it happened 3 times in row on a TOT LFR queue.
My tanks don't run away from the spell Deathforce cast by Abomination of Anger in the heroic scenario Crypt of Forgotten Kings
Having similar problem with this, and other scenarios as well. It seems to be competing with the combat routine for movement. I know one of the recent Singular updates added 'moving out of bad stuff' so maybe there is a conflict? I've tried different combinations of disabling/enabling movement in the routine and the bot without much luck.
axi, you do not have permission to access this page. This could be due to one of several reasons: Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system? If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
I am getting the same too it works ok for some toons but not for others, I am just running lfr for the legendary quest line and it on my enhancement shammy it ports out as soon as i enter, while my survival hunter and monk it has no issues, going to try my feral druid next, I also noticed it on a combat rogue too, where as my main toon it works fine.
I am having trouble with my toon attacking stuff the rest of the party bypasses. How do I stop this. Also is there any way to adjust the rez acceptance time? Immediate acceptance is a problem.
It's actually 2 things, 1. it thinks im a tank and kicks myself out, 2. it kinda tryes to requeue the second it get inside and then leaves the same second.
Boss: Jin Rhock Please let Melee Classes stay near the Boss. If the Tank dont get the Boss to the Waterplace to get the Buff all Melee Classes run crazy around between the Water spawnplace and the Boss!
And the Running back and forward. If there was a Wipe. The Toon runs into the Instance and run to the Tank or the Player who is far away. But whe all other join the Instance again my Toons always run back the whole way.
Ok I deleted all the prior logs before rerunning the dungeon so i knew Id have the right log. The log doesnt appear to indicate any issues. I see where it says that It engaged Assad, tried to loot him, It says it moved to X,Y coords (although it didnt go anywhere), and then it just says "user stopped bot". In between it trying to move to the new coords and me stopping the bot though the bot just sat there for a bit saying "You do not have a valid teleport location" View attachment 6548 2014-08-30 19.33.txt
Hey all Thanks for your hard work! for some reason lately, the bot just usually sits in one spot and doesn't follow the group until they start attacking a group of mobs which could be like a 30 second head start? just curious if anyone knows why? Thank you all for the hard work! once again.. and thank you four your help..
I agree 100% with what / how Highvoltz put it. I never thought about it but yes running with the same people over and over can be a huge give away. I usually babysit the bot though as it runs through the dungeons.. from what I have seen not many people talk. If they do its usually a "hi" when they first come into the dungeon or something to complain about. What I had in my mind though was a few things though - 1) a simple wait 30 seconds and re que. People can always turn it down or accept. 2) Look at chat input from other players for words like "again?" or "re que?" - I know there are variations but I would think having the bot look in a text file that can be easily edited by the end user would make it pretty simple. 2)a. When updates occur, it could be either overwritten as people submit or have a unique name generated evertime where the user would have to update the new file with the old 2)b. could be as simple as a "if foo.old.txt exists & foo.old.txt != md5sum of foo.new.txt then foo.old.txt >> foo.new.txt && rm foo.old.txt" 3) re que should only work if the bot is the leader itself, that way there is control, if not then break group BUT to Highvoltz #3 answer This might actually be the most important reason. The more time players spend together, the less of a stranger they become to each other, the more likely they'll try to socialize. Any attempts to socialize with the bot increases the risk of being discovered a bot. Maybe I'm just being paranoid here. I would much rather have him be paranoid and do things cautiously then to waste his time adding something that may get us dungeon grinders banned
I don't know if this is where I should be posting this, if it isn't please move it to where it should be, but lately I've found that db has a slight issue with accepting invites to lfg, etc. After searching for a little while, I came across this plugin, that provides the perfect work-around. All it does is auto-accept the invite, filling the hole in db currently. Here is the link to said plugin : https://www.thebuddyforum.com/honor...cataloged/94044-alisha-autoinvite-helper.html Enjoy your use of db
Hey, i use db to level my 5/5 raf team, but there are a few instances which wont work for me Caverns of Time 1 - Bots will make the first quest, after that they rush to thrall ignoring all the trash and wipe, after the wipe they continue rushing to thrall and wiping Throne of Tides - Tank will stand in front of Lady Naz'jar and nothing happens till the Bot dcs because of inactivity Blackrock Caverns - at the first Boss the Bot will move further, ignoring the Boss and stucks because the big guy killing all the mobs wont come. The Vortex Pinnacle - Tank stucks in front of the 2nd Boss, wont move till dc. All reported Issues have been tested 5-10Times any idea to fix this?
I have the issue with bot leaving dungeons/LFR for no reason aswell. Tried this morning and the bot did do a dungeon at first but then started leaving for the next ones. Had this problem before aswell but sometimes it works fine. Must be some flaw in the bot where the bot gets false info about party or something and makes it think it has to requeue I think. View attachment 3872 2014-08-31 10.18.txt
Is there a setting for Db so it only buffs and heals inside the instance, when my teams port out they are always rebuffing and healing while queuing again. So can we get it to do it inside rather than every time it comes out.
One more recommendation --- would it be possible or doable to force lootall on (if its on BossesOnly, not off/none) and only if a quest requires the bot to loot mobs from the instance? One example would be in The Blood Furnace for the quest Make Them Bleed (requires 10x Fel Orc Blood Vials). Or by chance make an option instead of forcing it (some people may have limited bag space) in the config?