Bertrand
Active Member
- Joined
- Aug 8, 2012
- Messages
- 1,249
- Reaction score
- 9
I mean hands down to giles and the db's random dungeon exploration (which is still in a so-so phase), but how come we dont have a solution to d3 crashes ?
I am not sure if i should take this here or in some sub-section forum but i'd be really nice if we can have an option to kill d3 window and relog back again, after which it should load the first profile that db started before crash. I am not much into programming but i am sure there is a way to detect unresponsive window (when d3 crashes it is not responding). This might not sound such a big deal to someone that is babysitting their bots, and although this crashes usually happen once in 2 days per account, they do happen.
Any way, if i sound too nooby to someone that is already using certain re-logger with this option available, share the load brother
I am not sure if i should take this here or in some sub-section forum but i'd be really nice if we can have an option to kill d3 window and relog back again, after which it should load the first profile that db started before crash. I am not much into programming but i am sure there is a way to detect unresponsive window (when d3 crashes it is not responding). This might not sound such a big deal to someone that is babysitting their bots, and although this crashes usually happen once in 2 days per account, they do happen.
Any way, if i sound too nooby to someone that is already using certain re-logger with this option available, share the load brother
