The bot does not click resume.
You clicking resume does not indicate what the bot does.
it sounds more like you got kicked out of game for inactivity timer, and then the bot didn't remake because you're using DB's inactivity timer which is broken.
Set the DB inactivity timer to 0 and set the one in RadsAtom to 2 or 3.
Whats your inactivity timer, 30 seconds? Increase it.
There's an improperly functioning waittimer after Cydaea that will be fixed in the next verison, but it's not *that* long.
Not really, I've heard of something called profile switcher that can supposedly do it but I don't know if it's compatible with radsatom and I also would caution you because unless you know how the profiles work you wouldn't want to randomize them because there are dependencies between some of the profiles (ie, cursed tower -> cursed heart). The path you move each game is pretty randomized already, a vast majority of the points use something called path precision meaning they don't move to the same point every game. The only points that don't use it are ones where it wont work (ie, next to a portal that you have to click). I don't think randomizing the order of the profiles would do anything.
Lets all put on our thinking caps for a second:
If blizzard was coordinate matching, don't you think we would ALL be banned?
The answer is yes.
Yeah so my bot was acting up this morning before I headed out. It was stuck in Cydea area just sitting at the stairs. I accidently had both inactivity timers set to zero. 15 hours later the bot was still sitting in the same spot casting war cry lol.
Not sure why but the bot is getting stuck at cydea on a regular basis and its on the correct quest, not on azmodan like you suggested.
Any idea why it is getting stuck there? Also if my inactivity timer is set to 3 what does that mean exactly? Will I time out in this situation and start a new run? My demon buddy reads
01:04:58.096 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:04:58.096 N] [RadsAtom] - Resetting the deathcounter.
[01:05:03.131 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:03.131 N] [RadsAtom] - Resetting the deathcounter.
[01:05:08.202 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:08.202 N] [RadsAtom] - Resetting the deathcounter.
[01:05:13.232 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:13.232 N] [RadsAtom] - Resetting the deathcounter.
[01:05:18.272 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:18.272 N] [RadsAtom] - Resetting the deathcounter.
[01:05:23.312 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:23.312 N] [RadsAtom] - Resetting the deathcounter.
[01:05:28.362 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:28.362 N] [RadsAtom] - Resetting the deathcounter.
[01:05:33.432 N] [RadsAtom] - Loading next profile: D:\DemonBuddy\Acronic-A3CH-217ca6e\[A3 - Inferno]Champion-Hunting 1.3.6.3 BigRed\BigRed_CursedHeart.xml
[01:05:33.432 N] [RadsAtom] - Resetting the deathcounter.
Over and over. Is this considered inactive?
I guess what I am asking is how do I avoid this from happening for extended periods of time? I am fairly new to DB (1 day) so forgive my ignorance.