I can't understand why the bot will work fine for a few minutes and then just stand still like a fucking idiot. Can someone please explain why this happens?
It would help if you could post some logs as it will show what the bot is trying to do and what causes it to stop working as expected.
I am going to make the assumption that the problem is most likely on your end, as I've never in my time using DB had problems such as yours. I will recommend installing the newest BETA DB, along with the newest Trinity and Quest tools (delete the old plugins included with DB)
Trinity is my routine.. I have been using the bot for about 2 months now.. I have updated... deleted... re-installed fresh with new plugin profiles... have watched the struggle like everyone else where everything worked fine until 2.2 messed up everything... and have deleted again, fresh install, again.. and have trinity/quest tools reinstalled.. again... Rift control doesn't work... I select only normal rifts and it still goes to trials and Grifts... Bounties are just as bad with the bot running around the objective item as if it weren't there... I'm not saying the issue is on my end, and part of it possibly could be.. .but maybe I'm doing something wrong by sitting here monitoring this bot (which defeats the purpose of using the bot becauuse I would rather be doing other things) and it runs fine and then just stops in the middle of combat and dies... then rezes... and dies again after not doing anything to defend itself or fight.. I will catch logs when it does it again for I have stopped using the bot and playing diablo for a minute because this shit didn't happen when I had a 30 day license.. only after I purchased the lifetime license... go figure
Not all the profiles have been updated yet, and some new mechs need coding into the bot to work out these new quests Blizzard added. Coding takes time, testing takes time. Play by hand if you're despite to get something up, or use the a1 profile. Hell even the rift profile works for me.
