Not saying this is a fix... just a place to look.
I believe the majority of your crashes are actually lost connection errors within D3.
"There was an error. (Code 1016)"
Once your D3 client freezes, close Demonbuddy (via taskmanager if you have to). Then tab back over to D3. That error will most likely pop for you.
If you google the fix for this specific error everything tells you to reset router/modem, use wired connections, reset wireless devices, etc (anything related to your connection). I ONLY get these errors while in N-Rifts and while running DB. Never had the issue running rifts manually.
Maybe the D3 client isn't assuming the bot is an "active" session. Maybe inactivity within the D3 client works differently? Maybe i'll run a mouse macro to move the cursor (left click or something) on the D3 screen every 5 mins or so lol and see what happens.
I believe the majority of your crashes are actually lost connection errors within D3.
"There was an error. (Code 1016)"
Once your D3 client freezes, close Demonbuddy (via taskmanager if you have to). Then tab back over to D3. That error will most likely pop for you.
If you google the fix for this specific error everything tells you to reset router/modem, use wired connections, reset wireless devices, etc (anything related to your connection). I ONLY get these errors while in N-Rifts and while running DB. Never had the issue running rifts manually.
Maybe the D3 client isn't assuming the bot is an "active" session. Maybe inactivity within the D3 client works differently? Maybe i'll run a mouse macro to move the cursor (left click or something) on the D3 screen every 5 mins or so lol and see what happens.
