[StandAlone] Yet Another Relogger!

can help explain the new max login attempt system?
i use v0.1.9.2. Yar always restart db over and over. most of them db shows max session. sometimes db login successfully but killed by yat. it last several hour before i manually stop it.

HTML:

[2013/1/7 8:38:29] <bar3> Demonbuddy:3724: Initialized! We are ready to go
[2013/1/7 8:38:30] <bar3> Diablo:6644: Process is not running
[2013/1/7 8:38:30] <bar3> Killing Agent.exe:2640
[2013/1/7 8:38:30] <bar3> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2013/1/7 8:38:30] <bar3> Language set: Traditional Chinese : zhTW
[2013/1/7 8:38:30] <bar3> Region set: Asia : kr.actual.battle.net
[2013/1/7 8:38:41] <bar3> Diablo:4552: Found D3 Main Window (7341194)
[2013/1/7 8:38:45] <bar3> Diablo:4552: Waiting for process to become ready
[2013/1/7 8:38:47] No need to reposition: 2098998
[2013/1/7 8:38:47] No need to reposition: 4195836
[2013/1/7 8:38:47] No need to reposition: 1443994
[2013/1/7 8:38:47] No need to reposition: 2950680
[2013/1/7 8:38:47] No need to reposition: 7865582
[2013/1/7 8:38:47] No need to reposition: 1902944
[2013/1/7 8:38:47] <bar3> Diablo:4552: Process is ready
[2013/1/7 8:38:47] <bar3> Demonbuddy start delay, waiting 10 seconds
[2013/1/7 8:38:57] <bar3> Demonbuddy:3724: Found matching log: D:\game\db\Demonbuddy3\Logs\3724 2013-01-07 08.35.txt
[2013/1/7 8:39:41] <bar3> Found login time: 2013/1/7 0:38:05
[2013/1/7 8:39:41] <bar3> Checking plugin: D:\game\db\Demonbuddy3\Plugins\YAR\Plugin.cs
[2013/1/7 8:39:41] <bar3> Plugin is installed and latest version
[2013/1/7 8:39:41] <bar3> Demonbuddy:3396: Waiting for process to become ready
[2013/1/7 8:39:43] <bar3> Found Demonbuddy: MainWindow (4458238)
[2013/1/7 8:39:43] <bar3> Demonbuddy:3396: Process is ready
[2013/1/7 8:39:43] <bar3> Demonbuddy:3396: Waiting for demonbuddy to log into Diablo
[2013/1/7 8:42:26] <bar3> Restarting...
[2013/1/7 8:42:26] <bar3> Diablo:4552: Kill process
[2013/1/7 8:42:26] <bar3> Demonbuddy:3396: Failed to close! kill process
[2013/1/7 8:42:26] <bar3> Demonbuddy:3396: Initialized! We are ready to go
[2013/1/7 8:42:26] System.IO.IOException: 
   在 System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
   在 System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
   在 System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
   在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   在 System.IO.TextWriter.WriteLine(String value)
   在 YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
[2013/1/7 8:42:27] <bar3> Diablo:4552: Process is not running
[2013/1/7 8:42:27] <bar3> Killing Agent.exe:708
[2013/1/7 8:42:27] <bar3> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2013/1/7 8:42:27] <bar3> Language set: Traditional Chinese : zhTW
[2013/1/7 8:42:27] <bar3> Region set: Asia : kr.actual.battle.net
[2013/1/7 8:42:38] <bar3> Diablo:6212: Found D3 Main Window (6161480)
[2013/1/7 8:42:40] <bar3> Diablo:6212: Waiting for process to become ready
[2013/1/7 8:42:42] No need to reposition: 2098998
[2013/1/7 8:42:42] No need to reposition: 4195836
[2013/1/7 8:42:42] No need to reposition: 1443994
[2013/1/7 8:42:42] No need to reposition: 2950680
[2013/1/7 8:42:42] No need to reposition: 7865582
[2013/1/7 8:42:42] No need to reposition: 1902944
[2013/1/7 8:42:42] <bar3> Diablo:6212: Process is ready
[2013/1/7 8:42:42] <bar3> Demonbuddy start delay, waiting 10 seconds
[2013/1/7 8:42:52] <bar3> Demonbuddy:3396: Found matching log: D:\game\db\Demonbuddy3\Logs\3396 2013-01-07 08.39.txt
[2013/1/7 8:43:33] <bar3> Found login time: 2013/1/7 0:42:05
[2013/1/7 8:43:33] <bar3> Checking plugin: D:\game\db\Demonbuddy3\Plugins\YAR\Plugin.cs
[2013/1/7 8:43:33] <bar3> Plugin is installed and latest version
[2013/1/7 8:43:33] <bar3> Demonbuddy:5072: Waiting for process to become ready
[2013/1/7 8:43:34] <bar3> Found Demonbuddy: MainWindow (4917910)
[2013/1/7 8:43:34] <bar3> Demonbuddy:5072: Process is ready
[2013/1/7 8:43:34] <bar3> Demonbuddy:5072: Waiting for demonbuddy to log into Diablo
[2013/1/7 8:46:27] <bar3> Restarting...
[2013/1/7 8:46:27] <bar3> Diablo:6212: Kill process
[2013/1/7 8:46:27] <bar3> Demonbuddy:5072: Failed to close! kill process
[2013/1/7 8:46:27] <bar3> Demonbuddy:5072: Initialized! We are ready to go
[2013/1/7 8:46:27] System.IO.IOException: 
   在 System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
   在 System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
   在 System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
   在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   在 System.IO.TextWriter.WriteLine(String value)
   在 YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
[2013/1/7 8:46:28] <bar3> Diablo:6212: Process is not running
[2013/1/7 8:46:28] <bar3> Killing Agent.exe:2124
[2013/1/7 8:46:28] <bar3> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2013/1/7 8:46:28] <bar3> Language set: Traditional Chinese : zhTW
[2013/1/7 8:46:29] <bar3> Region set: Asia : kr.actual.battle.net
[2013/1/7 8:46:39] <bar3> Diablo:3812: Found D3 Main Window (4655654)
[2013/1/7 8:46:41] <bar3> Diablo:3812: Waiting for process to become ready
[2013/1/7 8:46:43] No need to reposition: 2098998
[2013/1/7 8:46:43] No need to reposition: 4195836
[2013/1/7 8:46:43] No need to reposition: 1443994
[2013/1/7 8:46:43] No need to reposition: 2950680
[2013/1/7 8:46:43] No need to reposition: 7865582
[2013/1/7 8:46:43] No need to reposition: 1902944
[2013/1/7 8:46:43] <bar3> Diablo:3812: Process is ready
[2013/1/7 8:46:43] <bar3> Demonbuddy start delay, waiting 10 seconds
[2013/1/7 8:46:53] <bar3> Demonbuddy:5072: Found matching log: D:\game\db\Demonbuddy3\Logs\5072 2013-01-07 08.43.txt
[2013/1/7 8:47:34] <bar3> Found login time: 2013/1/7 0:46:05
[2013/1/7 8:47:34] <bar3> Checking plugin: D:\game\db\Demonbuddy3\Plugins\YAR\Plugin.cs
[2013/1/7 8:47:34] <bar3> Plugin is installed and latest version
[2013/1/7 8:47:34] <bar3> Demonbuddy:6532: Waiting for process to become ready
[2013/1/7 8:47:35] <bar3> Found Demonbuddy: MainWindow (7472266)
[2013/1/7 8:47:35] <bar3> Demonbuddy:6532: Process is ready
[2013/1/7 8:47:35] <bar3> Demonbuddy:6532: Waiting for demonbuddy to log into Diablo
[2013/1/7 8:50:26] <bar3> Restarting...
[2013/1/7 8:50:26] <bar3> Diablo:3812: Kill process
[2013/1/7 8:50:26] <bar3> Demonbuddy:6532: Failed to close! kill process
[2013/1/7 8:50:26] System.IO.IOException: 
   在 System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
   在 System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
   在 System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
   在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   在 System.IO.TextWriter.WriteLine(String value)
   在 YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
[2013/1/7 8:50:27] <bar3> Demonbuddy:6532: Initialized! We are ready to go
[2013/1/7 8:50:28] <bar3> Diablo:3812: Process is not running
[2013/1/7 8:50:28] <bar3> Killing Agent.exe:5052
[2013/1/7 8:50:28] <bar3> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[2013/1/7 8:50:28] <bar3> Language set: Traditional Chinese : zhTW
[2013/1/7 8:50:28] <bar3> Region set: Asia : kr.actual.battle.net
[2013/1/7 8:50:38] <bar3> Diablo:2560: Found D3 Main Window (4064990)
[2013/1/7 8:50:41] <bar3> Diablo:2560: Waiting for process to become ready
[2013/1/7 8:50:43] No need to reposition: 2098998
[2013/1/7 8:50:43] No need to reposition: 4195836
[2013/1/7 8:50:43] No need to reposition: 1443994
[2013/1/7 8:50:43] No need to reposition: 2950680
[2013/1/7 8:50:43] No need to reposition: 7865582
[2013/1/7 8:50:43] No need to reposition: 1902944
[2013/1/7 8:50:43] <bar3> Diablo:2560: Process is ready
[2013/1/7 8:50:43] <bar3> Demonbuddy start delay, waiting 10 seconds
[2013/1/7 8:50:53] <bar3> Demonbuddy:6532: Found matching log: D:\game\db\Demonbuddy3\Logs\6532 2013-01-07 08.47.txt
[2013/1/7 8:51:42] <bar6> Runs completed 8
[2013/1/7 8:51:42] <bar6> Sending MonsterPowerLevel: Level1
[2013/1/7 8:51:43] <bar3> Found login time: 2013/1/7 0:50:05
[2013/1/7 8:51:43] <bar3> Checking plugin: D:\game\db\Demonbuddy3\Plugins\YAR\Plugin.cs
[2013/1/7 8:51:43] <bar3> Plugin is installed and latest version
[2013/1/7 8:51:43] <bar3> Demonbuddy:5428: Waiting for process to become ready
[2013/1/7 8:51:44] <bar3> Found Demonbuddy: MainWindow (6031594)
[2013/1/7 8:51:44] <bar3> Demonbuddy:5428: Process is ready
[2013/1/7 8:51:44] <bar3> Demonbuddy:5428: Waiting for demonbuddy to log into Diablo
[2013/1/7 8:54:25] <bar3> Demonbuddy:5428: Initialized! We are ready to go
[2013/1/7 8:54:25] <bar3> Restarting...
[2013/1/7 8:54:25] <bar3> Diablo:2560: Kill process
[2013/1/7 8:54:25] <bar3> Demonbuddy:5428: Failed to close! kill process
[2013/1/7 8:54:25] System.IO.IOException: 
   在 System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
   在 System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
   在 System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
   在 System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   在 System.IO.TextWriter.WriteLine(String value)
   在 YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)

 

[07/01/2013 01:48:28] Editing bot: bomber
[07/01/2013 01:48:30] <bomber> We are scheduled to start
[07/01/2013 01:48:30] <bomber> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[07/01/2013 01:48:30] <bomber> Replacing D3Prefs for user: Andrew
[07/01/2013 01:48:30] <bomber> Copy custom D3Prefs file to: C:\Users\Andrew\Documents\Diablo III\D3Prefs.txt
[07/01/2013 01:48:31] <bomber> Language set: English (US) : enUS
[07/01/2013 01:48:31] <bomber> Region set: Europe : eu.actual.battle.net
[07/01/2013 01:48:33] <bomber> Diablo:5752: Process is not running
[07/01/2013 01:48:33] <bomber> Killing Agent.exe:6636
[07/01/2013 01:48:33] <bomber> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
[07/01/2013 01:48:33] <bomber> Replacing D3Prefs for user: Andrew
[07/01/2013 01:48:33] <bomber> Copy custom D3Prefs file to: C:\Users\Andrew\Documents\Diablo III\D3Prefs.txt
[07/01/2013 01:48:34] <bomber> Stopping
[07/01/2013 01:48:34] Relogger Thread Starting!


D3 seems to get stuck in a loop trying to reopen over and over giving different errors like " failed to retreive blizzard launcher properties"

 

The new experimental build works, but as soon as I enable stats, it's non-responding..
Any way of debugging this further...?

 

I've searched the thread, but still couldn't find a definite solution, so I apologize if it I missed it.

I'm currently using the option to run Diablo under a different user, but it will not use any d3prefs files. I've tried manually signing onto the user and changing it, i've checked all the other users. The only reason why I know it doesn't stick is because I have the mipbias setting at 9.999000, but it doesn't seem to apply. I've tried using the custom pref option and no errors shows in YAR, but it still doesn't apply.

"[1/7/2013 12:16:40 AM] <DH01> Copy custom D3Prefs file to: C:\Users\****\Documents\Diablo III\D3Prefs.txt" no errors

If anybody has a solution, I'd be grateful

 

Look in c:/users if there is a default user and replace its d3prefs

 

Thanks for the quick reply...i forgot to check if there were hidden folders...THANK YOU, i feel retarded now ahha

 

so i still get max session auth timed out issue on the last bot, just cant log in even with the new version and once it does log in with 10 tries of stop/start, db shows it has stopped responding after running for 2 mins, while the other 2 bots are running perfectly fine. and the last bot also can't connect to buddystats. is it db issue or yar issue? cuz my other two bots with exact same settings are running fine no problems.

 

i try 0.2.0.6. YAT still restart db over and over. it can last several hours. even if db succefully login on and ready to go, but killed by YAT

[2013/1/7 21:57:22] <bar6> Demonbuddy:5400: Waiting for process to become ready
[2013/1/7 21:57:22] <bar6> Found Demonbuddy: MainWindow (1313314)
[2013/1/7 21:57:22] <bar6> Demonbuddy:5400: Process is ready
[2013/1/7 21:57:22] <bar6> Demonbuddy:5400: Waiting for demonbuddy to log into Diablo
[2013/1/7 21:58:05] <bar6> Demonbuddy:5400: Initialized! We are ready to go
[2013/1/7 21:58:07] <bar6> Sending MonsterPowerLevel: Level1
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Is unresponsive for more than 30 seconds
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Killing process
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Process is not running
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Found matching log: D:\game\db\Demonbuddy6\Logs\5400 2013-01-07 21.57.txt
[2013/1/7 21:58:08] <bar6> Found login time: 2013/1/7 13:57:56
[2013/1/7 21:58:08] <bar6> Checking plugin: D:\game\db\Demonbuddy6\Plugins\YAR\Plugin.cs
[2013/1/7 21:58:08] <bar6> Plugin is installed and latest version
[2013/1/7 21:58:08] <bar6> Demonbuddy:6196: Waiting for process to become ready
[2013/1/7 21:58:09] <bar6> Found Demonbuddy: MainWindow (1182240)
[2013/1/7 21:58:09] <bar6> Demonbuddy:6196: Process is ready
[2013/1/7 21:58:09] <bar6> Demonbuddy:6196: Waiting for demonbuddy to log into Diablo
[2013/1/7 22:01:09] <bar6> Demonbuddy:6196: Failed to initialize 1/3
[2013/1/7 22:01:09] <bar6> Demonbuddy:6196: Forced to close!
[2013/1/7 22:01:09] <bar6> Demonbuddy:6196: Found matching log: D:\game\db\Demonbuddy6\Logs\6196 2013-01-07 21.58.txt
[2013/1/7 22:01:18] <bar6> Demonbuddy:6196: Failed to find login time
[2013/1/7 22:01:18] <bar6> Checking plugin: D:\game\db\Demonbuddy6\Plugins\YAR\Plugin.cs
[2013/1/7 22:01:18] <bar6> Plugin is installed and latest version
[2013/1/7 22:01:18] <bar6> Demonbuddy:2756: Waiting for process to become ready
[2013/1/7 22:01:18] <bar6> Found Demonbuddy: MainWindow (2688176)
[2013/1/7 22:01:18] <bar6> Demonbuddy:2756: Process is ready
[2013/1/7 22:01:18] <bar6> Demonbuddy:2756: Waiting for demonbuddy to log into Diablo
[2013/1/7 22:02:05] <bar6> Demonbuddy:2756: Initialized! We are ready to go
[2013/1/7 22:02:07] <bar6> Sending MonsterPowerLevel: Level1
[2013/1/7 22:02:07] <bar6> Demonbuddy:2756: Is unresponsive for more than 30 seconds
[2013/1/7 22:02:07] <bar6> Demonbuddy:2756: Killing process
[2013/1/7 22:02:08] <bar6> Demonbuddy:2756: Process is not running
[2013/1/7 22:02:08] <bar6> Demonbuddy:2756: Found matching log: D:\game\db\Demonbuddy6\Logs\2756 2013-01-07 22.01.txt
[2013/1/7 22:02:09] <bar6> Found login time: 2013/1/7 14:01:57
[2013/1/7 22:02:09] <bar6> Checking plugin: D:\game\db\Demonbuddy6\Plugins\YAR\Plugin.cs
[2013/1/7 22:02:09] <bar6> Plugin is installed and latest version
[2013/1/7 22:02:09] <bar6> Demonbuddy:7588: Waiting for process to become ready
[2013/1/7 22:02:10] <bar6> Found Demonbuddy: MainWindow (2163914)
[2013/1/7 22:02:10] <bar6> Demonbuddy:7588: Process is ready
[2013/1/7 22:02:10] <bar6> Demonbuddy:7588: Waiting for demonbuddy to log into Diablo
[2013/1/7 22:05:10] <bar6> Demonbuddy:7588: Failed to initialize 1/3
[2013/1/7 22:05:10] <bar6> Demonbuddy:7588: Forced to close!

 

This is for all of your bots or just that single one ? are there any plugins that could cause DB to freeze for a while?

 

I guess I have to add some more try catch to get the error will do it tomorrow

 

guys answer please, are you use d3starter in YAR (for more than 4-6 D3windows or no)?

i mean multibotting without VMware and different ip.
i got banned 2 accounts 4 days before, and now got last acc ban. :| so im start thinking with VMware is be safest botting :/

sorry for my bad english, i am trying my best hah

 

How is YAR's gold inactivity timer? Is it working properly or is there problems?

So if I have it enabled, and if the bot doesn't pick up gold for 2 minutes then YAR completely restarts D3 and DB?

 

random one. sometimes yat restart ok,sometimes restart over and over.
all of the db have same 3 plugins:GilesTrinity,RadsAtom,UnstuckMe.
i have watched clearly when yat kills db, db is not frozen.
[2013/1/7 21:58:05] <bar6> Demonbuddy:5400: Initialized! We are ready to go
[2013/1/7 21:58:07] <bar6> Sending MonsterPowerLevel: Level1
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Is unresponsive for more than 30 seconds
[2013/1/7 21:58:07] <bar6> Demonbuddy:5400: Killing process
from the log,db is succefully logon and ready to create game,but immediately killed by YAR over and over, it will never recovery except i manually stop and restart the bot.

 

can u make YAR load the profile before press the start button on DB?

so there would be no need for the "workaround" or that each profile creator starts to write his own profile for starting his profile.

would be great, in every thread they ask why the profile is not working with YAR.

 

@Crown
its a normal problem, there isn't really a way to get over it until DB finally decide to load plugins first. Based on the fact YAR logs in through DB

 

ofc there are some ways i can think off - just load the kickstarter and not try to load the original profile first like u do with the workaround.

 

Then, at this point, you should DEFINITEVLY develop an app (ios/android) that will replace buddystats (that becomes useless with all those features you implement)
You will realize good money with that and this will help you keep developing yar project/app.

 

so, can anyone answer on my question?

 

The latest edit finally works!
Great content so far!

 

I really hope you can help me with this error sinterlkass:

DB LOG:

[19:46:32.901 D] [SafeMoveTo]: distance to target: 230 questId="101758" stepId="1" x="3254" y="815" z="0" pathPrecision=50
[19:46:33.015 D] [YetAnotherRelogger] Scanned 6 log items in 0ms
[19:46:33.280 N] Diablo III Exited, Demonbuddy terminating
[19:46:33.532 N] [YetAnotherRelogger] Error: Could not read bytes from 01873414 [299]!
[19:46:33.534 N] [YetAnotherRelogger] Error: at Zeta.MemoryManagement.ExternalProcessReader.ReadBytes(IntPtr address, Int32 count, Boolean isRelative)
at Zeta.MemoryManagement.ExternalProcessReader.Read[T](IntPtr address, Boolean isRelative)
at Zeta.MemoryManagement.InProcessMemoryReader.Read[T](Boolean isRelative, IntPtr[] addresses)
at Zeta.ZetaDia.get_CurrentWorldId()
at Zeta.ZetaDia.get_IsInGame()
at YARPLUGIN.YARPLUGIN.ScanLogWorker()

YAR LOG:

N [08/01/2013 18:51:28] <*****> Diablo:****: Is unresponsive for more than 60 seconds
N [08/01/2013 18:51:28] <*****> Diablo:****: Killing process
N [08/01/2013 18:51:28] <*****> Diablo:****: Process is not running
N [08/01/2013 18:51:28] <*****> Demonbuddy:5336: Closing db
N [08/01/2013 18:51:28] <*****> Demonbuddy:5336: Waiting to close
N [08/01/2013 18:51:30] <*****> Demonbuddy:5336: Closed.
N [08/01/2013 18:51:30] PingCheck: Ping -> Google

There are no yar log entries from 18:43 till these ones at 18:51.Maybe there's a problem with the comunication between yar plugin and db, and therefore YAR thinks its not working and closes it?

Using Db #295, Trinity .14 and YAR 2.0.6(beta). It has been happening for a while now and with every bot configuration I've tried. Any ideas about it?Do you need the full log?