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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[StandAlone] Yet Another Relogger!

Status
Not open for further replies.
sinterlkaas

sinterlkaas

New Member
Joined
Jan 17, 2012
Messages
536

YAR_LOGO_medium.png



Yet Another Relogger
Version: 0.1.9.2 beta

This is a BETA release! Only use it if you want to help me in improving this relogger.

​

Features:
  • Hotkeys control your bots
  • Supports Inner Space (ISBoxer)
  • Crash detection
  • Week schedule
  • Profile schedule
  • Region + Language selection
  • Buddy Auth Session killer
  • Automaticly position Diablo position and size
  • Custom Diablo & Demonbuddy position and size
  • Process CPU priority selection
  • Process Affinity selection (thanks tomasd)
  • Supports Apoc D3Starter
  • Automaticly updates Communicator plugin to latest version

Compatibility:
  • GilesTrinity: Emergency stop when stash is full
  • Atom 2.0.15 "Take a break"
  • Buddystats: Stop command

To do:
  • Full documentation on how to use the relogger
  • More randomness for week schedule by shuffling days
  • Support GilesTrinity Pause button
  • Remotly control your bots
  • Run stats for each bot
  • Support for Battle.net Authenticator
  • Update checker
  • Commandline arguments to control bots
  • Improve bot status reports in main window

Screenshots:
Relogger:
Main.webp
New bot wizard:
Wizard1.webp Wizard2.webp Wizard3.webp Wizard4.webp

Donate:



Links removed by Nesox

Github:
You can now find the source for this project on Github
...

Experimental build:
This is the build which I update more often to test with other people first
...
In the folder LatestBuild (or click REMOVED - BAM )will be latest prebuild application for those of you who do not know how to compile the source
 
Last edited:
Changelog:
Version: 0.1.9.2 BETA
  • Fixed diablo region selection when using multiple diablos on different regions and languages
  • Fixed Random profile schedule not always selection the right profile
  • Fixed BuddyAuth Session killer
  • Added Monsterpower selection in profile schedule
  • Added Advanced settings to launch diablo as a different windows user
    * Remove window frame wont be working anymore when process is launched as a different user

Version: 0.1.8.5 BETA
  • Added Hotkey bindings
  • Changed Log file extension from .log to .txt to match Demonbuddy logging
  • Improved responsiveness

Version: 0.1.8.4 BETA
  • Fixed bug where it launched Demonbuddy multiple times
  • Added New thread for stats

Version: 0.1.8.2 BETA
  • Added CrashTender now uses profile Kickstart when enabled
  • Added -autostart launch argument
  • Added Option to disable Coinage 30 second log
  • Added Bot running time
  • Added Added delays inside possible CPU consuming loops
  • Added Profile "Kickstart" (will load a profile with 1 custom profile tag to prevent DB from choking in deeply nested custom profile tags)
  • Added Random profile selection
  • Added Customize-able Diablo start time limit

Version: 0.1.7.7 BETA
  • Added Support for Atom 2.0.15 "Take a break"
  • Added Option to start with windows
  • Added Option to minimize on start
  • Added Buddy Auth Session killer
  • Added option to remove window frame on diablo
  • Added Coinage check (2 minutes w/o gold change => reset) (*tomasd)
  • Added Crash detection for demonbuddy
  • Added Demonbuddy initialize time limit
  • Added CPU Affinity support (*tomasd)
  • Changed Version numbereing to v 0.1.inc_new_features.inc_new_test_release
  • Foreground check improved the way demonbuddy is set to front
  • Fixed some issues with the profile schedule
  • Fixed Connection check IP range was not implemented (somehow forgot this sorry...)
  • Fixed Layout problems with schedule and settings on some systems
  • Improved AntiIdle system
    • Limited to 3 fixing attempts in 5 mins
    • Added a new way to fix no pulse
      • First check if plugin is enabled
  • Fixed Language support for Traditional Chinese

Version: 0.0.0.6 BETA
  • Added Internet connection check (using ping to check if internet connection is available)
  • Added External IP / Host Validation (using Current IP Check) *request
  • Added Pause button to pause the relogger (useful when doing stuff that might cause false positives and close D3 + DB) *request
  • Reincarnated the Fore ground checker (disabled by default)
  • Fixed Date and Time issues with non-English windows systems
  • Fixed crash when no profile is added in the profile schedule (it will now show a warning and launch Demonbuddy without a start profile)
  • Fixed Manifest file to force Admin rights
  • Fixed High CPU load during Diablo start ups
  • Settings will no longer reset on every update
  • Removed Autoposition Diablo Window size 400x400 limit

Version: 0.0.0.5 BETA
  • Added InnerSpace support
  • Added possibility to force start
  • Fixed WaitForInputIdle bug causing false reports about Diablo III not being ready

Version: 0.0.0.4 BETA
  • Fixed FindWindowClass (it does now find the correct window for the process)
  • Improved the way Aopoc D3Starter is used
  • Added Polish language selection
  • Added Some Logging for Anti-Idle actions
  • Added option to Force enable all plugins for demonbuddy
  • Added Autoposition for Diablo III (demonbuddy will follow soon)
  • Removed Foreground window check (will improve and make this optional in a later release)
  • Fixed stop all button to actually stop all bots
  • Small bugfixes all over the code

    Plugin 0.0.0.4
  • Changed: Version now matches YAR main app
  • Added: Force enable all plugins
  • Added: Support for Giles Emergency stop
  • Added: Support for BuddyStats stop

Version: 0.0.0.3 BETA
  • Bugfix for Windows server 2003
  • Added manifest file to force Administrator rights
  • Added Treeview in settings tab
  • Improved weekschedule editing (Hold shift key and mouse over a box to enable the box)
 
Last edited:
holy shit, this sounds awesome ! :D
will this plugin check for crashes or dc too ? or is it for pure schedule adjustments?
 
finni said:
holy shit, this sounds awesome ! :D
will this plugin check for crashes or dc too ? or is it for pure schedule adjustments?
Click to expand...

It will detect basic idle situations like:
  • no plugin pulse for x seconds (this is what drelog does)
  • no game for x seconds
and some other things that still need some tweaking..
for now it will only try to Stop and Start Demonbuddy (yes I know this is not the best solution but this is 1 of the reasons why it is still in beta) :)

And for the question about crash detection: Yes it does support crash detection!
 
sinterlkaas said:
It will detect basic idle situations like:
  • no plugin pulse for x seconds (this is what drelog does)
  • no game for x seconds
and some other things that still need some tweaking..
for now it will only try to Stop and Start Demonbuddy (yes I know this is not the best solution but this is 1 of the reasons why it is still in beta) :)

And for the question about crash detection: Yes it does support crash detection!
Click to expand...
Hi Great idea about create program but any suggestion why program don't save profile ?
When I create profile program crash mes sedge is

System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w YetAnotherRelogger.Forms.Wizard.WizardMain.button1_Click(Object sender, EventArgs e)
w System.Windows.Forms.Control.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
w System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
w System.Windows.Forms.Control.WndProc(Message& m)
w System.Windows.Forms.ButtonBase.WndProc(Message& m)
w System.Windows.Forms.Button.WndProc(Message& m)
w System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
w System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Zestawy załadowane **************
mscorlib
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.269 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
YetAnotherRelogger
Wersja zestawu: 0.0.0.1
Wersja Win32: 0.0.0.1
CodeBase: file:///E:/YetAnotherRelogger/YetAnotherRelogger.exe
----------------------------------------
System.Windows.Forms
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.278 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.282 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
fcpwsvus
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
1wx2x1dk
Wersja zestawu: 0.0.0.1
Wersja Win32: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms.resources
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_pl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Core
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
mscorlib.resources
Wersja zestawu: 4.0.0.0
Wersja Win32: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_pl_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
 
Indoor said:
Hi Great idea about create program but any suggestion why program don't save profile ?
When I create profile program crash mes sedge is

System.NullReferenceException: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
w YetAnotherRelogger.Forms.Wizard.WizardMain.button1_Click(Object sender, EventArgs e)
w System.Windows.Forms.Control.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnClick(EventArgs e)
w System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
w System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
w System.Windows.Forms.Control.WndProc(Message& m)
w System.Windows.Forms.ButtonBase.WndProc(Message& m)
w System.Windows.Forms.Button.WndProc(Message& m)
w System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
w System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Click to expand...

did you enter all the information like bot name an description ? leaving none of these blank this could give some trouble cause I did not built in any validations on this yet
 
Doesn't work for me. It starts up diablo but subsequently doesn't detect that iablo is running, kills diablo and goes into an infinite loop.

[10/30/2012 11:19:37 PM] Relogger Thread Starting!
[10/30/2012 11:19:37 PM] Yet Another Relogger Version 0.0.0.1
[10/30/2012 11:24:01 PM] Adding new bot: xxx
[10/30/2012 11:24:57 PM] <xxx> We are scheduled to start
[10/30/2012 11:24:57 PM] <xxx> Next scheduled stop: 31/10 2:16
[10/30/2012 11:24:57 PM] <xxx> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[10/30/2012 11:24:57 PM] <xxx> Language set: English (US) : enUS
[10/30/2012 11:24:57 PM] <xxx> Region set: America : us.actual.battle.net
[10/30/2012 11:24:57 PM] <xxx> Diablo:5804: Waiting for process to become ready
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Kill process
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
... infinite loop
Click to expand...
 
sinterlkaas said:
did you enter all the information like bot name an description ? leaving none of these blank this could give some trouble cause I did not built in any validations on this yet
Click to expand...
Ok Has You set need fill all information. I start test when find some trouble i write to help improve program. BTW GREAT work. Can You add Polish league to data base or how modify setting file to add this ?
 
Great Work, i was doing something very similar with with scheduler. but you GUI is far more interesting. i will take a look at the code when i get home
 
ieee said:
Doesn't work for me. It starts up diablo but subsequently doesn't detect that iablo is running, kills diablo and goes into an infinite loop.
Click to expand...

Ignore the above, works after ticking "Use Apoc D3Starter".

Second question, do you have any idea what the below "patching" entails and if it is warden safe?

10/30/2012 11:43:13 PM] <xxx> D3Starter: Process ID 3628 started.
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching process 3628
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching file access at address: 81C29D
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching launcher startup at address: 81C29D
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Resuming process 3628
[10/30/2012 11:43:15 PM] <xxx> D3Starter: 1 game instances started! All done!
 
ieee said:
10/30/2012 11:19:37 PM] Relogger Thread Starting!
[10/30/2012 11:19:37 PM] Yet Another Relogger Version 0.0.0.1
[10/30/2012 11:24:01 PM] Adding new bot: xxx
[10/30/2012 11:24:57 PM] <xxx> We are scheduled to start
[10/30/2012 11:24:57 PM] <xxx> Next scheduled stop: 31/10 2:16
[10/30/2012 11:24:57 PM] <xxx> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[10/30/2012 11:24:57 PM] <xxx> Language set: English (US) : enUS
[10/30/2012 11:24:57 PM] <xxx> Region set: America : us.actual.battle.net
[10/30/2012 11:24:57 PM] <xxx> Diablo:5804: Waiting for process to become ready
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Kill process
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
[10/30/2012 11:25:33 PM] <xxx> Diablo:5804: Starting diablo timed out!
[10/30/2012 11:25:33 PM] <xxx> Stopping
... infinite loop

Ignore the above, works after ticking "Use Apoc D3Starter".

Second question, do you have any idea what the below "patching" entails and if it is warden safe?

10/30/2012 11:43:13 PM] <xxx> D3Starter: Process ID 3628 started.
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching process 3628
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching file access at address: 81C29D
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Patching launcher startup at address: 81C29D
[10/30/2012 11:43:13 PM] <xxx> D3Starter: Resuming process 3628
[10/30/2012 11:43:15 PM] <xxx> D3Starter: 1 game instances started! All done!
Click to expand...


Hey thanks for reporting this issue .. I fixed it so it is possible to just run without patching D3 memory and use the old trusted multiple folder d3 launches in next version (sorry for this bug overlooked some stuff while changing it to support the d3starter from Apoc)

And for answering your question the patching was done with a tool made by Apoc you can find more info here: http://www.thebuddyforum.com/demonb...3-starter-start-multiple-d3s-same-folder.html



Changelog v0.0.0.2 beta:
  • Quick fix for: Starting Diablo timeout! (only happened when not using the Apoc D3Starter)
 
Last edited:
In version 002 get error mes-sedge
w YetAnotherRelogger.Helpers.Communicator.HandleClient.<>c__DisplayClassa.<HandleMsg>b__9(BotClass f)
w System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
w YetAnotherRelogger.Helpers.Communicator.HandleClient.HandleMsg(String msg)

In demon buddy now spam mes-sedge

[YetAnotherRelogger] Unknown response! "Internal server error:
 
Indoor said:
In version 002 get error mes-sedge
w YetAnotherRelogger.Helpers.Communicator.HandleClient.<>c__DisplayClassa.<HandleMsg>b__9(BotClass f)
w System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
w YetAnotherRelogger.Helpers.Communicator.HandleClient.HandleMsg(String msg)

In demon buddy now spam mes-sedge

[YetAnotherRelogger] Unknown response! "Internal server error:
Click to expand...

sounds like you are running multiple instances ? check system tray next to you clock your will see the jar icon :) exit them both and restart the relogger

it also could be possible that you started the relogger without closing down the running bot resulting in a plugin that tries to communicate with the relogger but it cant find any matching bots that are running in the local database
 
Last edited:
I check 2 only one copy program run. What about add polish to diablo 3 league start
 
sinterlkaas said:
Hey thanks for reporting this issue .. I fixed it so it is possible to just run without patching D3 memory and use the old trusted multiple folder d3 launches in next version (sorry for this bug overlooked some stuff while changing it to support the d3starter from Apoc)

And for answering your question the patching was done with a tool made by Apoc you can find more info here: http://www.thebuddyforum.com/demonb...3-starter-start-multiple-d3s-same-folder.html





Changelog v0.0.0.2 beta:
  • Quick fix for: Starting Diablo timeout! (only happened when not using the Apoc D3Starter)
Click to expand...

Thanks, great work! Will use it a bit more and report back if I see anything.
 
Status
Not open for further replies.
Back
Top