What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Plugin] AntiIdle

wowcheesestick said:
If D3 freezes, but not crashed, then what? AntiIdle will just sit there?
Click to expand...

Have to say I do not know this yet but ..
my D3 actually never freezes without crashing. There are some possibilities that could happen if you use the GPH check this will drop and get below minimum and close D3 and DB after x minutes. Or the pulse would stop and it will try to fix this.. or it will detect that we are not doing anything anymore in game and it will fix this as well.. but it could also be possible that DB crashes .. I just dont know this yet
 
sinterlkaas said:
Have to say I do not know this yet but ..
my D3 actually never freezes without crashing. There are some possibilities that could happen if you use the GPH check this will drop and get below minimum and close D3 and DB after x minutes. Or the pulse would stop and it will try to fix this.. or it will detect that we are not doing anything anymore in game and it will fix this as well.. but it could also be possible that DB crashes .. I just dont know this yet
Click to expand...

A better approach is to use Gold per 10 minute. If its 0 then we know for a fact that something is wrong and therefore closing D3 and DB. I see issues that when you close DB and restart it without closing D3, it fails to attach sometimes.
 
the reason to use Gold per 10 min is because GPH can drop very slowly when you have been running for hours...
 
wowcheesestick said:
A better approach is to use Gold per 10 minute. If its 0 then we know for a fact that something is wrong and therefore closing D3 and DB. I see issues that when you close DB and restart it without closing D3, it fails to attach sometimes.
the reason to use Gold per 10 min is because GPH can drop very slowly when you have been running for hours...
Click to expand...

Gold per 10 minute would be a option indeed will add this to my todo list.

wowcheesestick said:
also when the plugin kills DB, ARelog doesnt restart DB correctly. Do you know why?
Click to expand...

What happens exactly ?
in what way does it not restart correctly ?
 
Windows shows that DB has stopped working and prompts to kill the thing but without human interaction it wont kill, therefore ARelog won't start a new DB. Either way, your plugin is extremely useful. I will provide more suggestions as I go along with it :)
 
wowcheesestick said:
Windows shows that DB has stopped working and prompts to kill the thing but without human interaction it wont kill, therefore ARelog won't start a new DB. Either way, your plugin is extremely useful. I will provide more suggestions as I go along with it :)
Click to expand...

Ah ok I see are there any plugins in your plugin list that use the configwindow ? if so there is a bug in current DB release .160 that causes DB not to close correctly when the config window is set for a plugin :( thats why I did not use the config window yet

And I indeed have a D3 freeze right now while I was AFK and the plugin actually does not detect it yet... (note that I dont have GPH check enabled right now) so I need to find a way to detect when D3 freezes. The Gold per minute thing would be 1 solution ...
 
Last edited:
sinterlkaas said:
And I indeed have a D3 freeze right now while I was AFK and the plugin actually does not detect it yet... (note that I dont have GPH check enabled right now) so I need to find a way to detect when D3 freezes. The Gold per minute thing would be 1 solution ...
Click to expand...

Another solution would be to monitor the log in DB if that does not spam any message for a while there must be something wrong so Close D3 + DB and start over again with ARelog :)
(any other suggestions on how to detect if D3 is frozen would be nice)
 
You could also check how the memory reading with the db changes if it freezes. If there's some kind of tell on when it's not doing what it should. I mean, the invalid session messages could be a helpful tell or like "last update from log is more than 90 seconds then close d3/db/relog.
 
Mammon said:
You could also check how the memory reading with the db changes if it freezes. If there's some kind of tell on when it's not doing what it should. I mean, the invalid session messages could be a helpful tell or like "last update from log is more than 90 seconds then close d3/db/relog.
Click to expand...

I was thinking about a timeout with on log messages indeed. I dont want the plugin to touch any memory reading for security reasons but you talk about invalid session ? when exactly is that message logged ?

I cant find the invalid session in my D3 freeze log
 
Nice, progress but when you made it autoupdate without re-launch it actually make no plugins but AGBloader to show up after a reboot :|
 
Hmm ok ? can you show me a log when this happens? mostly this happens when 1 of the plugins fails to compile it will only show those that are compiled at that time and stops compiling all others ...

and what exactly do you mean with autoupdate? did not add this to AntiIdle? :P
 
Updated to v0.5
* Added: Log checker (when there are no log messages for x seconds we are idle and FORCE to close D3 + DB)
* Added: If DB is foreground window and gets stopped verify with user to stop DB
* Added: Batch file generation to kill DB when closing to be 100% sure it gets closed
* Added: Logging monitor to deconflict with other plugins
* - Compatible with WebStats
* - Compatible with Unstucker
* Added: reset Restart counter after x seconds
* Bug fix: When leaving game start new will pop Party error msg
* Bug fix: Load correct profile after a forced db close
 
Last edited:
Be a cool idea to implement autonotificationok in this :)
 
You must log in or register to reply here.
Back
Top