tehtoad
New Member
- Joined
- Jun 18, 2012
- Messages
- 88
- Reaction score
- 1
Like mentioned here is a new thread for the standalone utility autoauth that spawned from demonloader....
AutoAuth Multi Bot Supported Session Killer
Logs in to buddyauth.com website and then kills sessions as required.
[video=youtube;hab9fKtRbu8]http://www.youtube.com/watch?v=hab9fKtRbu8[/video]
Whats the point?
With the new demonbuddy patch if d3 closes then the session is killed so what is the point of this?
What if demonbuddy freezes, exits first with no warning ??
Then your session will remain until it timesout, that can be a good 5min.
To those who want to save time this is the tool for you, a session killer.
(This tool needs to be integrated into your current managing script setup, be it bat or autoit whatever... )
IE:
You have a autoit script hat loads Demonbuddy and Diablo3 and watches process's for crash, then reloads, incorporate this tool into your autoitscript/bat file/exe so it runs this before it loads demonbuddy to insure no down time...
This tool is for developers and i imagine the general public will have a hard time doing anything with it, obviously when developers incorporate it into there logger / manager applications it will be more us-full to the general public.
If that time never come i will release a update that contains a DB log file analyser to scrape the bots status and act if it sees a session limit reached error.
Multibot:
Have your applications, bat files, autoit scripts load the tool parsing it the -stamp argument:
-stamp"00:00:00"
The time "00:00:00" can be scraped / extracted from the demonbuddy log files, this time is server side, have your scripts scrape the time of the bots log and then parse it to have autoauth kill the session.
There is methods in place to account for server lag, where your start time in your log may be out from the server by a few seconds, this setting can be changed in the settings and will remain changed after a save, this method will increment the time stamp until it finds a match and then kill (up to a preset number that can be stored in settings).
SingleBot:
Simply dont parse it any arguments and run as normal.
Kill All sessions:
Same as above
________________________________
Download:
<Removed until source is provided>
Installation:
Save all above files to a location, .dll files must be in same location as autoauth.exe.
Run autoauth.exe once and enter settings, check run on load and then save.
The rest is up to your developer or you to integrate into your current demonbuddy management system.
Change Log:
Integration:
Currently integrating this project with,
Gawdz sweet Standalone Relogger and Teivovo's Awesome Batch Files.
Stay tuned to the above's respected threads for news on integration, setup.
AutoAuth Multi Bot Supported Session Killer
Logs in to buddyauth.com website and then kills sessions as required.
[video=youtube;hab9fKtRbu8]http://www.youtube.com/watch?v=hab9fKtRbu8[/video]
Whats the point?
With the new demonbuddy patch if d3 closes then the session is killed so what is the point of this?
What if demonbuddy freezes, exits first with no warning ??
Then your session will remain until it timesout, that can be a good 5min.
To those who want to save time this is the tool for you, a session killer.
(This tool needs to be integrated into your current managing script setup, be it bat or autoit whatever... )
IE:
You have a autoit script hat loads Demonbuddy and Diablo3 and watches process's for crash, then reloads, incorporate this tool into your autoitscript/bat file/exe so it runs this before it loads demonbuddy to insure no down time...
This tool is for developers and i imagine the general public will have a hard time doing anything with it, obviously when developers incorporate it into there logger / manager applications it will be more us-full to the general public.
If that time never come i will release a update that contains a DB log file analyser to scrape the bots status and act if it sees a session limit reached error.
Multibot:
Have your applications, bat files, autoit scripts load the tool parsing it the -stamp argument:
-stamp"00:00:00"
The time "00:00:00" can be scraped / extracted from the demonbuddy log files, this time is server side, have your scripts scrape the time of the bots log and then parse it to have autoauth kill the session.
There is methods in place to account for server lag, where your start time in your log may be out from the server by a few seconds, this setting can be changed in the settings and will remain changed after a save, this method will increment the time stamp until it finds a match and then kill (up to a preset number that can be stored in settings).
SingleBot:
Simply dont parse it any arguments and run as normal.
Kill All sessions:
Same as above
________________________________
Download:
<Removed until source is provided>
Installation:
Save all above files to a location, .dll files must be in same location as autoauth.exe.
Run autoauth.exe once and enter settings, check run on load and then save.
The rest is up to your developer or you to integrate into your current demonbuddy management system.
Change Log:
Code:
1.0
* Fixed incrementing bug where it crashed if it couldn't find time-stamp.
* Fixed incrementing Settings number, works as intended.
* Fixed some error handling, It should NEVER crash now.
* Corrected garbage collection, no instances remain in task manager.
* Fix to memory leak.
* Tweak to bots logic.
* Now increments both UP and DOWN until it finds stamp
* New log system, only stores 5 log files at any time in log folder
Beta
* Multi bot support with -stamp argument.
* Error handling / Logging improvements.
* Save logfile on shutdown to working directory.
Alpha
* Kill All Sessions ONLY.
* Single Bot support.Integration:
Currently integrating this project with,
Gawdz sweet Standalone Relogger and Teivovo's Awesome Batch Files.
Stay tuned to the above's respected threads for news on integration, setup.
Attachments
Last edited by a moderator:
also its interesting for other devs to see the power of it...
