[StandAlone] Yet Another Relogger!

Can it be run in the background? Or do I need to have all the d3 windows on top or something?

 

Yes it is possible to run multiple windows in the background ... right now I am running 2 bots with this relogger for testing and they are not set as foreground window

 

In profile settings, what if I just want to run the same profile over and over again? Should i just leave runs and minutes at zero?

 

yes just set them to 0

 

A few things I noticed:

The scheduler is awesome! however, it could be improved by making it so that you can drag and select more than one box at a time.

Next up is the window placement. I think this could be made more intuitive. There needs to be a way to make tiling easier without having to do the math or go get a mouse coordinate program. Maybe something like a "Tile all Diablo's" button on the main form.

Lastly, I noticed that D3 seems to crash a fair bit on opening. Not a real issue just need to make sure it closes the "demonbuddy has stopped working Dialogue"

Great job man, I really like the work you have done =)

 

Made an account just to thank you for this amazing program.

 

sinterlkaas

Thank you, as i said i was developing one of my own this the same features, but your gui is very well made. good thinking.
Allow me to make a sugesting that i was implementing on mine as well..
its about invalid Sessions that sometime bot gives and make us just stand in menus.
thats easy to detect and you could just make DB restart.
how do you detect? under DB folder there is log.txt files.. sort for newer parse the file for the last 2 minutes or so.. looking for "invalid sessions" string.
thats it.

GJ

 

I like the look of this relogger. I am currently using Drelog and am thinking about switching to this one. I noticed that this all runs off 1 instance of DB. My question is if I have 2 barbs (1 WW and 1 rend) and I want them to have different trinity settings is it possible?

Do you plan on implementing buddyauth?

 

Thanks dude! It's awesome ! <3

 

By far the easiest relogger to set up and run.

Running fine for me for the past 8 hours with Apoc D3Starter unchecked. Window resizer is perfect (except maybe for the lack of a tiling feature as suggested by a poster above), starts up diablo and demonbuddy fast, recovers from crashes fast. Will report in on the scheduling feature soon.

 

great job..

and i got this error...what i need to do..?

[2012-10-31 10:50:57] <254466> Checking plugin: E:\Game\D3\DB\liu254466\Plugins\YAR\Plugin.cs
[2012-10-31 10:50:57] <254466> Plugin is installed and latest version
[2012-10-31 10:50:57] Relogger Crashed! with message “No application associated with the specified file for this operation are associated”
[2012-10-31 10:50:57] at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.Start()
at YetAnotherRelogger.Relogger.ReloggerWorker()

 

Just tested, it work amazing as every compliment have made.
Suggestion
1. Option to enable/disable the resizer build in your relogger.
2. I hope you can make your relogger generate a report or webstat for monitoring purpose. I prefer monitor your relogger more than others monitoring.
3. Resize and positioning for DB will make your relogger close to prefect...

 

Great job sinterlkaas!
Can you add autostart after bluescreen\restart? And start selected bot button?

 

you should make your own copies of DB for each bot example:
Bot1: C:\Demonbuddy_Bot1\demonbuddy.exe
Bot2: C:\Demonbuddy_Bot2\demonbuddy.exe
Bot3: C:\Demonbuddy_Bot3\demonbuddy.exe
Locate to them in the new bot wizard... this way you can fully customize your bots and decide what plugins you need with the settings of your needs...

And Yes I am planning to support buddyauth session killing when Demonbuddy crashed

1. You can already disable it by entering 0 as value but I will add a simple checkbox to make it easier
2. Webstats / remote control is on my todo list
3. I will add this soon

This is also on my todo list to have a autostart feature that will start all the bots that are checked in the main form

 

You sure you entered both Diablo path and Demonbuddy path?

 

gonna test it soon.. awsome stuff!

 

ya. sure...

it just doesnt work at my windows2003 system

but working perfect with my win7 PC..

net 2.0-4.0 all done

 

I do have the same problem. Relogger opens my D3 session until the part where he should login and then the following error appears. (Demon Buddy has no been started to this point) I do have demon buddy path and D 3 path update in the relogger (they are not in the same folder)

[31.10.2012 13:29:45] Yet Another Relogger Version 0.0.0.2
[31.10.2012 13:29:45] Relogger Thread Starting!
[31.10.2012 13:29:47] <Act 3 XP> We are scheduled to start
[31.10.2012 13:29:47] <Act 3 XP> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[31.10.2012 13:29:47] <Act 3 XP> Language set: English (Brittain) : enGB
[31.10.2012 13:29:47] <Act 3 XP> Region set: Europe : eu.actual.battle.net
[31.10.2012 13:29:47] <Act 3 XP> Diablo:5932: Waiting for process to become ready
[31.10.2012 13:29:55] <Act 3 XP> Diablo:5932: Found D3 Main Window
[31.10.2012 13:29:56] <Act 3 XP> Diablo:5932: Process is ready
[31.10.2012 13:29:56] <Act 3 XP> Diablo III
[31.10.2012 13:29:58] <Act 3 XP> Diablo:5932: Resizing window W:320 H:200
[31.10.2012 13:29:58] <Act 3 XP> Diablo:5932: Moving window to X:0 Y:0
[31.10.2012 13:29:58] <Act 3 XP> Diablo:5932: Process is ready
[31.10.2012 13:29:58] <Act 3 XP> All profiles are done resetting cycle
[31.10.2012 13:29:58] Relogger Crashed! with message Der Index lag au?erhalb des Bereichs. Er muss nicht negativ und kleiner als die Auflistung sein.
Parametername: index
[31.10.2012 13:29:58] bei System.ThrowHelper.ThrowArgumentOutOfRangeException()
bei System.Collections.Generic.List`1.get_Item(Int32 index)
bei YetAnotherRelogger.Helpers.Bot.ProfileScheduleClass.get_GetProfile()
bei YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.Start()
bei YetAnotherRelogger.Relogger.ReloggerWorker()
[31.10.2012 13:29:58] Waiting 10 seconds and try again!
[31.10.2012 13:30:08] Relogger Crashed! with message Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
[31.10.2012 13:30:08] bei YetAnotherRelogger.Relogger.ReloggerWorker()
[31.10.2012 13:30:08] Waiting 10 seconds and try again!
[31.10.2012 13:30:18] Relogger Crashed! with message Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
[31.10.2012 13:30:18] bei YetAnotherRelogger.Relogger.ReloggerWorker()
[31.10.2012 13:30:18] Waiting 10 seconds and try again!
[31.10.2012 13:30:28] Relogger Crashed! with message Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
[31.10.2012 13:30:28] bei YetAnotherRelogger.Relogger.ReloggerWorker()
[31.10.2012 13:30:28] Waiting 10 seconds and try again!
[31.10.2012 13:30:38] Relogger Crashed! with message Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
[31.10.2012 13:30:38] bei YetAnotherRelogger.Relogger.ReloggerWorker()
[31.10.2012 13:30:38] Waiting 10 seconds and try again!
[31.10.2012 13:30:44] <Act 3 XP> Stopping
[31.10.2012 13:30:44] <Act 3 XP> Diablo:5932: Kill process

 

Everything working fine as far I can tell.
However, there is a weird problem for me, the tool will open a game according to the profile set, then it will stop and start the bot while in loading screen (why?).
This however does something bad to the bot or the profile and it just won't move at all.

I will post a log once I get access to the VM where the bot is running on

 

Does it run Diablo ?
Double check the path to Demonbuddy.exe again pls cause the error message tells me that there is no Application associated to run the EXE file? and because in the log it did get passed the diablo start procedure which is almost identical to the one for demonbuddy ...