I was looking at writing a rift killer profile today and ran into some issues. I could pretty easily detect whether a rift was already open, open one if needed, and enter. However, once inside it looked like I was going to have to tailor a large number of sub profiles to cover every rift type. I also haven't been able to figure out if the DB Beta update can detect rift quests/completion like it can bounties.
Is there a way to use TrinityExploreDungeon to find ANY exit and then take it? The exit hashes progressed sequentially so I could sort of get around the problem for awhile but it wouldn't handle stopping/starting at all. I also couldn't get UsePortal to work consistently as some rifts had portals, some arch entries, etc... and the bot would definitely get in range of the exit and then just stand there and trigger the stuck routine.
Anyone have thoughts on how to make it interact with the variety of possible exit portals or to have it explore to the first exit it finds without specifying a hash?
Is there a way to use TrinityExploreDungeon to find ANY exit and then take it? The exit hashes progressed sequentially so I could sort of get around the problem for awhile but it wouldn't handle stopping/starting at all. I also couldn't get UsePortal to work consistently as some rifts had portals, some arch entries, etc... and the bot would definitely get in range of the exit and then just stand there and trigger the stuck routine.
Anyone have thoughts on how to make it interact with the variety of possible exit portals or to have it explore to the first exit it finds without specifying a hash?