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

[Plugin] AntiIdle

Hey is there anything specific we should put in the "comment" section of arelog??
 
Test release

Soon new official release
I redid almost everything and made the code a lot cleaner..
I am uploading it here as attachment so people can help find bugs before I release it as V1.0

Changes
I cant list all changes that I made .. simply because most I do not even remember anymore.

These are the major changes I can think of
  • Using Windows API to detect if DB is foreground window (this is still used for AntiIdle to check if user stopped it or not)
  • Moved some of the idle checks to on-pulse (where possible)
  • Moved the restarting to on-pulse (with a fail-safe when it takes to long and use a separate thread to finish the job)
  • Changed the way the batch file works (not writing a new file for every time it needs to do the fail-safe close DB)



Known issues
Eats sessions only when D3 crashed this is due to the new close Demonbuddy feature when D3 gets closed (this is a Demonbuddy bug! and hopefully will be fixed soon...)
 

Attachments

looks like this version has a restart loop but got it fixed and running for a while now and did some test to just get idle using an empty profile and it should be fixed

and the bug in db to not close the session when d3 crashed seems to be fixed by the db team in there latest release
 
Update Version 1.0

Changes
  • Added detection if D3 is frozen
  • Using Windows API to detect if DB is foreground window (this is still used for AntiIdle to check if user stopped it or not)
  • Moved some of the idle checks to on-pulse (where possible)
  • Moved the restarting to on-pulse (with a fail-safe when it takes to long and use a separate thread to finish the job)
  • Changed the way the batch file works (not writing a new file for every time it needs to do the fail-safe close DB)
 
Thank you sinterlkaas for the awesome plugin.
Personally I manage to get this working with arelog for the entire day today.
Got 7 crashes/restarts and it was handled well.

But there is 1 thing that doesn't work for me - inet/router restart crashes.
My internet connection restart from time to time and when it does I end up with diablo clients at login screen and nothing happens.
Would you mind to take a look and implement a solution for it? I would really be grateful. cheers
 
kaime said:
Thank you sinterlkaas for the awesome plugin.
Personally I manage to get this working with arelog for the entire day today.
Got 7 crashes/restarts and it was handled well.

But there is 1 thing that doesn't work for me - inet/router restart crashes.
My internet connection restart from time to time and when it does I end up with diablo clients at login screen and nothing happens.
Would you mind to take a look and implement a solution for it? I would really be grateful. cheers
Click to expand...

hmm yes I will take a look at it :) bot it is time for me to go to bed right now ..
 
So far I'm having great success with this plugin, but I have a quick simple question.
Is there a way to edit the config file where if it leaves game for being idle to restart the profile instead of loading from where it left off?
 
pjhulz said:
yeah just wanna know same thing :)
Click to expand...
If it closes db or d3 yes it will work because the relogger checks for closes if this plugin starts up with semonbuddy it will work indefinately
 
gawdz said:
If it closes db or d3 yes it will work because the relogger checks for closes if this plugin starts up with semonbuddy it will work indefinately
Click to expand...

thanks for the quick reply gawdz, time to test this AntiIdle. :D
I'll be back if I encounter any error.
 
Nesox said:
Changelog .176
  • InactivityDetector added. Can be set in the settings tab ( Inactivity Time ) how many minutes it should wait before leaving game if standing still in the same spot.
  • Added "DemonVoiceover" to the combat ignore list.
  • Will no longer attempt to attack the projection of Maghda or any of the other un-attackable units in the command outpost in the Khasim outpost
  • Monk and Witch Doctor should no longer cause extreme game lag when using Belphegor
  • Temporarily disabled the stuck handler.
Click to expand...

Looks like DB has integrated some kind of Idle checking mechanism .. I did not test this yet but we will see how it is working and if at the end this plugin becomes useless ... :)
for now it is still useful as it also can detect if D3 is frozen and do I am currently working on some unstuck mechanism to.. also added a max vendor time because I noticed DB sometimes got messed up and tried to vendor at some random NPC that was not a vendor a bot restart fixed this so added this for next release + some bugfixes and some improvements. Today I am busy maybe I can continue later this day but we will see as for now ... stay tuned
 
Ok .. I set this inactivity time on DB to 60 and it trips all the time .. restarting each time .. :/ anyway did not test any further got to now ...
 
Works now very very well :)

THIS is the solution for all fucking relog problems :) Works very well with Arelog.

BUT can u add the check a little bit more time? After load world it logout sometimes because relogtime is a little bit more when on the same pc running much wow instances too, diablo3 client need a little bit more time to load.
And i have this night on 1 pc the problem, that d3 + db freezes and plugin doenst recognize that. i must kill processes over taskmanager.
 
how to put this plugin in to work with dbrelogger? put it in plugins folder of dbrelogger or db folder?
 
tifreak said:
Works now very very well :)

THIS is the solution for all fucking relog problems :) Works very well with Arelog.

BUT can u add the check a little bit more time? After load world it logout sometimes because relogtime is a little bit more when on the same pc running much wow instances too, diablo3 client need a little bit more time to load.
And i have this night on 1 pc the problem, that d3 + db freezes and plugin doenst recognize that. i must kill processes over taskmanager.
Click to expand...

You could change the timings yourself in Config.cfg :) open it with your favorite text editor .. and the problem with DB freezing ... I can not detect this with a plugin as DB controls the plugin and if that is frozen the plugin is frozen a external program could do that .. mayb DBRelogger can do this for you :)


andyt315 said:
how to put this plugin in to work with dbrelogger? put it in plugins folder of dbrelogger or db folder?
Click to expand...
I did not use DBRelogger myself yet ask this in the DBRelogger thread sure he can help you :)
 
AntiIdle v1.1 RC1 (test release)

preUpdate v1.1 RC1
This is for those who feel like testing and help me find some more bugs..

Changelog:
  • Added: Unstucker which can be set to move in all directions or just 4 direction to try unstuck or set it to simply start a new game
    [*] Added: Memory checker (checks how much memory DB is using and close when it exceeds our specified maximum) *request
    [*] Added: Integrated a ErrorClicker when not ingame (DB does not click the errors when not ingame) *request
    [*] Added: Check if idle at login screen, this needs to be configured with your battletag + username + password in the config file (this can be disabled if you prefer to use a thirparty plugin for this) *request
    [*] Added: Compatibility for breaktaker
    [*] Added: Max vendor time (I noticed DB could not find the vendor in some rare cases and was standing at some random dude trying to vendor)
  • Bugfix: When resuming from a long pause (exceeding our maxidle time) AntiIdle did first force a restart because it did not recieve a pulse during pause
    [*] Bugfix: Debug setting did not work properly leaving it to print debug messages
    [*] Bugfix: GPH check got reset when new game joined while it should not reset
    [*] Bugfix: Laststate saver did not always save the last used profile
  • Changed: Made the compatibility more reliable to always check messages that pass through log
    [*] Changed: Made alot of improvements to the code
    [*] Changed: The config file is a bit nicer now :)
  • Removed:The active window check.. DB no longer needs to be run in background for stop detection to be working (overlooked the simple "Start/Stop Button Clicked!" message in log)
 

Attachments

You must log in or register to reply here.
Back
Top