[StandAlone] Yet Another Relogger!

[sinterlkaas]

I'm having issues with YAR since today. Every time it opens Demonbuddy it can't load profiles because plugins aren't detected, however if I open DB manually they are detected ok. Any idea ?
Edit: I've just noticed it only happends with keyhunting profiles, but as I said, loading DB manually doesn't cause such behaviour.

Build the latest release at: https://github.com/sinterlkaas/YetAnotherRelogger
or Wait a few hours and I will update the forum version to latest github release

Oh, strange that I couldn't find it. How do you use autostart with this relogger? I tried "-autostart" but it didn't work :S

The autostart is there but it is actually used when the relogger is added to run on windows start the commandline it uses is -winstart this will tell the relogger to start after x seconds on delay which you can find in general settings...

The "no gold gained" spam should be reduced. Only write it if action is taken because the gold-find anti-idle kicked in. Will clear things up.
Also it would be nice if it simply displayed the time the bots have been running. The way DRelog has it. I usually start/stop them by hand and I sometimes forget when I started them so a display that says e.g. "Running for 8 hours 47 Minutes" would be handy.
I really like this so far though!

Is it possible to remove the log? YAR keep spamming it.

Yes I will add a option to disable logging Coinage info and only let it log when it is kicking in to fix a problem

The time running is indeed a nice thing to add

 

[sinterlkaas]

Update version: 0.1.8.2

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

 

[barbarianos]

is it ok if I copy "settings" folders from old version to new? or I should setup everything from start?

 

[sinterlkaas]

is it ok if I copy "settings" folders from old version to new? or I should setup everything from start?

It is ok to copy old settings to new version (if you experience any problems tell me)

 

[barbarianos]

I tried both way, copying settings and making them from start..Everytime I get this on startup.

[2012-11-24 12:34:42] Yet Another Relogger Version 0.1.8.2
[2012-11-24 12:34:42] Relogger Crashed! with message Określony argument jest spoza zakresu prawidłowych wartości.
Nazwa parametru: rowIndex
[2012-11-24 12:34:42] w System.Windows.Forms.DataGridView.InvalidateCell(Int32 columnIndex, Int32 rowIndex)
w System.Windows.Forms.DataGridView.DataGridViewDataConnection.ProcessListChanged(ListChangedEventArgs e)
w System.Windows.Forms.DataGridView.DataGridViewDataConnection.currencyManager_ListChanged(Object sender, ListChangedEventArgs e)
w System.Windows.Forms.CurrencyManager.OnListChanged(ListChangedEventArgs e)
w System.Windows.Forms.CurrencyManager.List_ListChanged(Object sender, ListChangedEventArgs e)
w System.ComponentModel.BindingList`1.OnListChanged(ListChangedEventArgs e)
w System.ComponentModel.BindingList`1.Child_PropertyChanged(Object sender, PropertyChangedEventArgs e)
w YetAnotherRelogger.Helpers.Bot.BotClass.OnPropertyChanged(String propertyName)
w YetAnotherRelogger.Helpers.Bot.BotClass.SetField[T](T& field, T value, String propertyName)
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:34:42] Waiting 10 seconds and try again!

Anyway bot is running fine...Only the first time I've sarted it, it went into constant crashing loop..here is the log:

[2012-11-24 11:56:24] Relogger Thread Starting!
[2012-11-24 11:56:25] Yet Another Relogger Version 0.1.8.2
[2012-11-24 11:56:38] <Matt> We are scheduled to start
[2012-11-24 11:56:38] <Matt> Next scheduled stop: 25-11 3:14
[2012-11-24 11:56:38] PingCheck: Ping -> Google
[2012-11-24 11:56:38] PingCheck: 173.194.35.176 -> 45ms
[2012-11-24 11:56:38] <Matt> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2012-11-24 11:56:38] <Matt> Killing Agent.exe:5512
[2012-11-24 11:56:38] <Matt> Language set: Polish : plPL
[2012-11-24 11:56:38] <Matt> Region set: Europe : eu.actual.battle.net
[2012-11-24 11:56:58] <Matt> Diablo:6068: Starting diablo timed out!
[2012-11-24 11:56:58] <Matt> Restarting...
[2012-11-24 11:56:58] <Matt> Diablo:6068: Kill process
[2012-11-24 11:56:58] <Alfa> We are scheduled to start
[2012-11-24 11:56:58] <Alfa> Next scheduled stop: 25-11 3:26
[2012-11-24 11:56:59] PingCheck: Ping -> Google
[2012-11-24 11:56:59] PingCheck: 173.194.35.176 -> 45ms
[2012-11-24 11:56:59] <Alfa> Killing Agent.exe:5348
[2012-11-24 11:56:59] <Alfa> Language set: Polish : plPL
[2012-11-24 11:56:59] <Alfa> Region set: Europe : eu.actual.battle.net
[2012-11-24 11:57:19] <Alfa> Diablo:5724: Starting diablo timed out!
[2012-11-24 11:57:19] <Alfa> Restarting...
[2012-11-24 11:57:19] <Alfa> Diablo:5724: Kill process
[2012-11-24 11:57:20] <Apollo> We are scheduled to start
[2012-11-24 11:57:20] <Apollo> Next scheduled stop: 25-11 3:39
[2012-11-24 11:57:20] PingCheck: Ping -> Google
[2012-11-24 11:57:20] PingCheck: 173.194.35.176 -> 45ms
[2012-11-24 11:57:20] <Apollo> Killing Agent.exe:4640
[2012-11-24 11:57:20] <Apollo> Language set: Polish : plPL
[2012-11-24 11:57:20] <Apollo> Region set: Europe : eu.actual.battle.net
[2012-11-24 11:57:40] <Apollo> Diablo:6020: Starting diablo timed out!
[2012-11-24 11:57:40] <Apollo> Restarting...
[2012-11-24 11:57:40] <Apollo> Diablo:6020: Kill process
[2012-11-24 11:57:41] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:57:41] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:57:41] Waiting 10 seconds and try again!
[2012-11-24 11:57:51] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:57:51] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:57:51] Waiting 10 seconds and try again!
[2012-11-24 11:58:01] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:01] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:01] Waiting 10 seconds and try again!
[2012-11-24 11:58:11] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:11] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:11] Waiting 10 seconds and try again!
[2012-11-24 11:58:21] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:21] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:21] Waiting 10 seconds and try again!
[2012-11-24 11:58:31] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:31] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:31] Waiting 10 seconds and try again!
[2012-11-24 11:58:41] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:41] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:41] Waiting 10 seconds and try again!
[2012-11-24 11:58:51] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:58:51] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:58:51] Waiting 10 seconds and try again!
[2012-11-24 11:59:01] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:01] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:02] Waiting 10 seconds and try again!
[2012-11-24 11:59:12] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:12] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:12] Waiting 10 seconds and try again!
[2012-11-24 11:59:22] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:22] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:22] Waiting 10 seconds and try again!
[2012-11-24 11:59:32] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:32] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:32] Waiting 10 seconds and try again!
[2012-11-24 11:59:42] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:42] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:42] Waiting 10 seconds and try again!
[2012-11-24 11:59:52] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 11:59:52] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 11:59:52] Waiting 10 seconds and try again!
[2012-11-24 12:00:02] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:02] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:02] Waiting 10 seconds and try again!
[2012-11-24 12:00:12] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:12] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:12] Waiting 10 seconds and try again!
[2012-11-24 12:00:22] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:22] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:22] Waiting 10 seconds and try again!
[2012-11-24 12:00:32] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:32] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:32] Waiting 10 seconds and try again!
[2012-11-24 12:00:42] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:42] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:42] Waiting 10 seconds and try again!
[2012-11-24 12:00:52] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:00:52] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:00:52] Waiting 10 seconds and try again!
[2012-11-24 12:01:02] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:02] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:02] Waiting 10 seconds and try again!
[2012-11-24 12:01:12] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:12] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:12] Waiting 10 seconds and try again!
[2012-11-24 12:01:22] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:22] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:22] Waiting 10 seconds and try again!
[2012-11-24 12:01:32] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:32] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:32] Waiting 10 seconds and try again!
[2012-11-24 12:01:42] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:42] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:42] Waiting 10 seconds and try again!
[2012-11-24 12:01:52] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:01:52] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:01:52] Waiting 10 seconds and try again!
[2012-11-24 12:02:02] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:02] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:02] Waiting 10 seconds and try again!
[2012-11-24 12:02:12] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:12] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:12] Waiting 10 seconds and try again!
[2012-11-24 12:02:22] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:22] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:22] Waiting 10 seconds and try again!
[2012-11-24 12:02:32] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:32] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:32] Waiting 10 seconds and try again!
[2012-11-24 12:02:42] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:42] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:42] Waiting 10 seconds and try again!
[2012-11-24 12:02:52] Relogger Crashed! with message Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
[2012-11-24 12:02:52] w YetAnotherRelogger.Helpers.Bot.DemonbuddyClass.get_IsInitialized()
w YetAnotherRelogger.Relogger.ReloggerWorker()
[2012-11-24 12:02:52] Waiting 10 seconds and try again!
[2012-11-24 12:02:55] Closed!

 

[boter]

Awesome reloger!
Please add auto start only checked bots

 

[dhdhdh]

Can we have an option, to select the profile, that will be loaded on DB start? Say, if i don't want my bots to resume chapion hunting profiles from the profile whe D3 got crashed, and i want to load _START_HERE profile every time YAR reloading D3 and DB? Thanks for your time!

 

[sinterlkaas]

Awesome reloger!
Please add auto start only checked bots

Sorry this is a bug and is fixed on github already

 

[sanerrr]

Sorry, anyway some clients were staying and then can not load DB
5 computers, each 5 bots
1 computer works well for some reason

 

[StefanKFG]

Yes, same to me but only for one bot and only the wiz. Dont know if this is important.

After I start YAR, it logs in the wiz as intended, starts DB etc. When the game should begin, there is an error message



After that, YAR makes DB start/stop/start/stop/start/stop all the time and I get this error by YAR (watch attachment)

I made a test to newest YAR 1.8 and YAR 1.7. Both not working ... And its always only one char and always the wiz.

When I start the bot manually without a relogger, everything works fine.

Sinterlkaas, do you need additional info to help me out?
Sorry, I cant translate this in english.

 

[Geckoz]

I'd really love someone with insight to comment on the proper use of processor priority and affinity? Advantages, disadvantages

 

[brbbX]

Can somebody explain to me how can I make the relogger close db and start it again every 3 hours? Thank you

 

[Crown]

on my Computer i can run 3 Diablos + 3 DB without a problem, if i try the 4. diablo is starts normaly but demonbuddy freezes after "attached to diablo III" why is that?

if i start manualy it works flawless.

edit: if i disable kickstart its working too.

edit 2 : ok its not working if i disable kickstart

 

[1337PIKE]

I don't know if this has been answered yet or not, but it works fine and everything up until login (it stats db perfectly, reduces diablo III window size and stuff), but when it has to login it doesn't put in the password even though I have put it in the relogger options. Tried starting as adminstrator, still doesn't work. And no, my password does not contain any weird letters.


This is what it keeps saying: [24-11-2012 20:53:19] <Barbar> Diablo:5828: has focus. Bring attached Demonbuddy to front
This is what it keeps saying: [24-11-2012 20:53:19] <Barbar> Diablo:5828: has focus. Bring attached Demonbuddy to front

And it keeps going like that until it automatically closes DB and tries to start it up again, with no luck.

 

[Crown]

i found a solution, if i manualy choose the "kickstart" profile it creates in the relogger as "my profile" than it works even if i start all 4 bots with the relogger.

 

[barbarianos]

how to compile version from github into working plugin?? Do I need visual studio?

 

[ezpwnd]

Thanks for the runtimecounter

Another suggestion that just came up to my mind which should be easy to implement but would greatly increase ease of use: Let it save something like "defaultsettings". Some settings (e.g. db-directory) hardly ever change. Whenever setting up a new bot after an initial one let it fill out those fields automatically.

Isn't exactly a must have but still a nice to have

 

[ezpwnd]

Also I found a bug thats easy to recreate:

I sometimes use it to just log into the account and not actually bot, for example if I'm using the auctionhouse/muling gold etc. Its easier to just let it start all the clients and log in automatically then to do this by hand. I will usually press demonbuddys "stop"-button as soon as its logged in and in main-menu of the game.

Now as soon as I run a second instance while the first instance is "stopped" demonbuddy will be closed and this exception is thrown into the YAR-Log:

System.IO.IOException: Unterbrochene Pipe. (Pipe is Broken)
bei System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
bei System.IO.Pipes.PipeStream.BeginWriteCore(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state)
bei System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
bei System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
bei System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
bei System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
bei System.IO.TextWriter.WriteLine(String value)
bei YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)

This is quite annoying, as usually when you are running, lets say 9 bots and you stop one of them to do something and during that time another one crashes things will get messed up.

 

[Icaros]

Just updated to 1.8.2, and it seems like window resizing stopped working?
I've tried setting manually, and restarting, as well as using the auto position settings, and clicking "reposition now" - still nothing.

Also, is it intentional that the demonbuddy autoposition options are greyed out?

 

[Waga]

Really enjoying it so far.
Authenticator support will make this perfect with the scheduler.