Search results

Seems like pausing the bot avoids it from moving ... you should just FORCE it to move to the globe :)

It was not my intention to make you sad ;) it could indeed be useful .. would be nice to have it monitor the logs directory and to detect when max sessions happen and use the log before that to get the session time :)

Indeed looks like it ... and why use sendkeys for this you could just use http library to create a connection and kill the sessions

hmm yes I will take a look at it :) bot it is time for me to go to bed right now ..

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...

so easy and yet so useful :) thanks for this ;)

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

hmm ok I dont worry about my own setup but I am just curious if it would improve allowing even more to run :)

sounds nice how is fps in those small windows ? better than the usual small window ?

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...

When testing with stopping DB then closing D3 ... DB kicks in and closes and it does not cause a session to be eaten .. public static void Close(bool forceD3 = false) { try { if (BotMain.IsRunning) BotMain.Stop()...

When I just close D3 it does close DB aswell but it is not a clean exit it is causing some exception errors... could this be related to bot still running + DB stats ? anyway this is eating sessions

working on a complete rewrite now ..

no that is just a comment for your self

ofc you can .. DB logs that message so you could open the log it is using and read it out :) will pm you example on how I did this

Update to version 0.6.2 * Added: Minimize DB window when AntiIdle gets enabled (this will also happen when DB gets restarted. By default this is disabled edit config file to enable) * Bug fix: Sometimes DB did not close when D3 gets frozen / crashed while AntiIdle tried to close it and caused...

From what I can reproduce on this is ... I made it run a 1 profile 2 times and loop this ARelog closes DB + D3 without any problems then it starts both again causing it have Max session error I think this is because ARelog just kills the process and not calls the mainwindow to close leaving...

I'm a bit confused now ... You tell me after ARelog did the frist schedule (2h run) it does not close DB + D3 ? if so look at DB logs what causes it to not close.. but it is still strange that D3 does not get closed this can not be caused by AntiIdle

Yes I understand this but what do you use to schedule your runs ?

thats why you should use DB ;) its playing for you while you code ...