[StandAlone] Yet Another Relogger!

Quote of a friend:

HI! I am using the new Version of YAR and have a big problem.. everything starts fine until Diablo starts. If it gets in the game, the status is shown as: ? Diablo is unresponsive? and if it does for 60 seconds it starts the game new. So the game starts, I am in town and then 60 seconds unresponsive . -- close Diablo, start Diablo new??
Sometimes he starts the route but the status still is shown as unresponsive.. Anyone an idea?

Btw: I checked out if it works with db alone! It does! So its maybe a communication problem between Yar and D3?

Please help me! Thx!

 

logs?

 

logs:

[05.12.2012 09:51:44] ####[ Detecting Screens ]####
[05.12.2012 09:51:44] - Primary Screen 0: X:0,Y:0,W:1440,H:900 Enabled:True
[05.12.2012 09:51:44] Name: \\.\DISPLAY1
[05.12.2012 09:51:44] Device: ATI Mobility Radeon HD 5470
[05.12.2012 09:51:44] WorkingArea: X:0,Y:0,W:1440,H:856
[05.12.2012 09:51:44] ######################
[05.12.2012 09:51:44] Relogger Thread Starting!
[05.12.2012 09:51:44] Yet Another Relogger Version 0.1.8.5
[05.12.2012 09:52:16] <Mega run> Forced to start!
[05.12.2012 09:52:17] <Mega run> We are scheduled to start
[05.12.2012 09:52:17] <Mega run> Next scheduled stop: 5.12 9:0
[05.12.2012 09:52:17] <Mega run> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[05.12.2012 09:52:17] <Mega run> Language set: German : deDE
[05.12.2012 09:52:17] <Mega run> Region set: Europe : eu.actual.battle.net
[05.12.2012 09:52:26] <Mega run> Diablo:4776: Found D3 Main Window (721982)
[05.12.2012 09:52:31] <Mega run> Diablo:4776: Waiting for process to become ready
[05.12.2012 09:52:33] <Mega run> ManualPosition window:721982: X:2 Y:2 W:320 H:200
[05.12.2012 09:52:33] <Mega run> Diablo:4776: Process is ready
[05.12.2012 09:52:33] <Mega run> Demonbuddy start delay, waiting 10 seconds
[05.12.2012 09:52:43] <Mega run> Current profile: "00_Gnome_START_HERE.xml" Runs:0 Time:0 mintues (C:\Users\Synthie\Desktop\db287\db287\profiles\Original Alkaizer Run_1.0\00_Gnome_START_HERE.xml)
[05.12.2012 09:52:43] <Mega run> Generate new Kickstart profile: C:\Users\Synthie\Desktop\db287\db287\profiles\Original Alkaizer Run_1.0\YAR_Kickstart.xml
[05.12.2012 09:52:43] <Mega run> Checking plugin: C:\Users\Synthie\Desktop\db287\db287\Plugins\YAR\Plugin.cs
[05.12.2012 09:52:43] <Mega run> Plugin does not exist
[05.12.2012 09:52:43] <Mega run> Installing latest plugin: C:\Users\Synthie\Desktop\db287\db287\Plugins\YAR\Plugin.cs
[05.12.2012 09:52:43] <Mega run> Demonbuddy:2536: Waiting for process to become ready
[05.12.2012 09:52:44] <Mega run> Found Demonbuddy: MainWindow (590980)
[05.12.2012 09:52:44] <Mega run> Demonbuddy:2536: Process is ready
[05.12.2012 09:53:32] <Mega run> Diablo:4776: Is unresponsive for more than 60 seconds
[05.12.2012 09:53:32] <Mega run> Diablo:4776: Killing process
[05.12.2012 09:53:33] <Mega run> Diablo:4776: Process is not running
[05.12.2012 09:53:33] <Mega run> Killing Agent.exe:1740
[05.12.2012 09:53:33] <Mega run> Language set: German : deDE
[05.12.2012 09:53:33] <Mega run> Region set: Europe : eu.actual.battle.net
[05.12.2012 09:53:40] <Mega run> Stopping
[05.12.2012 09:53:40] <Mega run> Diablo:3940: Kill process
[05.12.2012 09:53:40] Relogger Thread Starting!
[05.12.2012 09:53:59] <Mega run> Stopping
[05.12.2012 09:53:59] Relogger Thread Starting!
[05.12.2012 09:53:59] <Mega run> Forced to start!
[05.12.2012 09:54:00] <Mega run> We are scheduled to start
[05.12.2012 09:54:00] <Mega run> Next scheduled stop: 5.12 9:0
[05.12.2012 09:54:00] <Mega run> Deleting: C:\ProgramData\Battle.net\Agent\agent.db

 

If you could add an option to use D3Loader instead of D3Starter it already has everything you would need to implement the custom winuser via cmdline/bat

This is how i use D3loader via .bat

Code:

xcopy /s /y "C:\D3PREFSPATH\D3Prefs.txt" "C:\USERPATH\[user]\Documents\Diablo III"

timeout /t [wait for d3prefs to copy delay]

"C:\D3\d3Loader.exe" /user "[user]" /pass "[userpass]" /x 0 /y 0 /h 540 /w 960 "C:\D3PATH\Diablo III.exe -launch"

timeout /t [wait for d3 to load delay]

d3loader /user "[user]" /pass "[userpass]" "C:\DB PATH\Demonbuddy.exe -routine=""GilesPlugin"" -profile=""C:\PROFILE PATH\PROFILE.xml"" -key DBKEY -bnetaccount ACCOUNTUSER -bnetpassword ACCOUNTPASS -noflash -autostart" 

timeout /t [delay to wait for bot to load before starting to load next d3/bot]

This is how i'm currently using it, i'm sure it would be easily adaptable to fit YAR compared to apoc starter, i'm not sure if you'd have problems using it but it seems to be able to do pretty much everything to do with loading/positioning

 

[2012/12/5 21:29:34] <Diablo BOT> We are scheduled to start
[2012/12/5 21:29:34] <Diablo BOT> Next scheduled stop: 6/12 11:2
[2012/12/5 21:29:34] <Diablo BOT> Killing Agent.exe:3060
[2012/12/5 21:29:34] <Diablo BOT> Language set: Chinese : zhCN
[2012/12/5 21:29:34] <Diablo BOT> Region set: America : us.actual.battle.net
[2012/12/5 21:29:42] <Diablo BOT> Diablo:1760: Found D3 Main Window (787124)
[2012/12/5 21:29:45] <Diablo BOT> Diablo:1760: Waiting for process to become ready
[2012/12/5 21:29:47] <Diablo BOT> Diablo:1760: Process is ready
[2012/12/5 21:29:47] <Diablo BOT> Demonbuddy start delay, waiting 10 seconds
[2012/12/5 21:29:57] <Diablo BOT> Demonbuddy:1328: Found matching log: C:\Demonbuddy 1.0.1204.287\Logs\1328 2012-12-05 21.28.txt
[2012/12/5 21:29:58] <Diablo BOT> BuddyAuth: No session found.
[2012/12/5 21:29:58] <Diablo BOT> Current profile: "BigRed_START_HERE.xml" Runs:2 Time:180 mintues (C:\Linked+1.1\Linked 1.1\BigRed_START_HERE.xml)
[2012/12/5 21:29:58] <Diablo BOT> Using a already generated Kickstart profile: C:\Linked+1.1\Linked 1.1\YAR_Kickstart.xml
[2012/12/5 21:29:58] <Diablo BOT> Checking plugin: C:\Demonbuddy 1.0.1204.287\Plugins\YAR\Plugin.cs
[2012/12/5 21:29:58] <Diablo BOT> Plugin is installed and latest version
[2012/12/5 21:29:58] <Diablo BOT> Demonbuddy:2256: Waiting for process to become ready
[2012/12/5 21:29:59] <Diablo BOT> Found Demonbuddy: MainWindow (590474)
[2012/12/5 21:29:59] <Diablo BOT> Demonbuddy:2256: Process is ready
[2012/12/5 21:32:58] <Diablo BOT> Demonbuddy:2256: Failed to initialize more than 3 times
[2012/12/5 21:32:58] <Diablo BOT> Stopping
[2012/12/5 21:32:58] <Diablo BOT> Diablo:1760: Kill process
[2012/12/5 21:32:58] <Diablo BOT> Demonbuddy:2256: Failed to close! kill process
[2012/12/5 21:32:58] <Diablo BOT> Diablo:1760: Process is not running

some one can give the reason？ always Failed to initialize more than 3 times，then it stoped...

 

I don't know what it means, but I get this quite a lot. It seems that a pipe is broken ?

System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.IO.TextWriter.WriteLine(String value)
at YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)

 

at 40fps your cpu will be under a lot of load, judging from your cpu usage i think thats about right. Cut your fps by half should reduce cpu usage by maybe 1/3 or so without sacrificing bot performance

 

40fps / 40 fps is your problem, as warren said. put that down to 15/15 (i have even used 10/10 in the past) and use ISBOXER or YAR to shrink your screens down to 150x100 for each window.

That being said, you probably won't get 10 bots to run on an i7 2.8. I'd say 8 comfortably with those settings i mentioned, but not much passed that.

 

i just woke up to db crashing in a loop, yar 1.8.5

05/12/2012 8:30:18 AM] System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
at System.IO.Pipes.PipeStream.BeginWriteCore(Byte[] buffer, Int32 offset, Int32 count, AsyncCallback callback, Object state)
at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
at System.IO.TextWriter.WriteLine(String value)
at YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)

 

Same problem here. The most unpleasant when it stops at night.

 

I've personally noticed and tested that lowering your FPS below 30 really does alter your item/hour ratio.

 

I haven't had a problem in 6 months with 10-15 across 7+ bots. It might be low for some, but i still think you shouldn't need anything over 20.

After that you're going to sacrifice quantity of bots your computer can run.

 

This app is a must have. Thanks bud!

 

Hi
Want to say good job Sinterlkaas.
I have been reading the forum and found out some problems i have and found some new ones
So to my questions i have that i haven't found a answer to. I know all the questions isn't only about the plugin but i hope some can shine a light on it
1. I want to run like around 2h game. And i want my 3 profiles to random so i have set runs to 1 and min 0. Do ppl use the min and do you time a run use the plus time?
2. And i want to do a break in the 2h so i use Radsatom breaktaker but the counter restarts after one profile why is that. Do it work whit authenticator?
3. Do i need UnstuckMe or is this what i should have? Or do Yet Another Relogger have a build in?
4. I use authenticator but i haven setup Yet Another Relogger. When it shows up do it just keep trying to login? Same when the server is down. Can i setup so it dont do that?
5. buddyauth.com what is this and use for?
6. Session killer means whit what

/Heart

 

this relogger have serious issues with bot stopping. It stops 90% of the time every now and then.

 

It shouldnt especially when bot ticks 8-12 / s. Could u tell more about the test?

 

what i have to do so the db's dont pop up every time i open my inventory at client?

 

no authenticator support still?

 

I was just to post about this problem too... Happens to me very often in the last one or two days. Any solutions yet?

 

Request for resize hotkey, possible to resize it bigger than 800 600??