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 said:
This is a known problem and seems like Blizzard does not like Apoc D3Starter you can use my latest experimental build and clone your Diablo installations




Experimental build:
This is the build which I update more often to test with other people first
https://github.com/sinterlkaas/YetAnotherRelogger/tree/Experimental
In the folder LatestBuild (or click here)will be latest prebuild application for those of you who do not know how to compile the source
Click to expand...

i just download you build of yar, make 3 directory of d3 and set each profile for each directory right?
 
another strange thing

[2012-12-12 16:51:12] System.IO.IOException:
w System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
w System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
w System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
w System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
w System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
w System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
w System.IO.TextWriter.WriteLine(String value)
w YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
(re-run didnt work)
and

[2012-12-12 16:57:00] Demonbuddy:5072: Delayed start failed! (13,4429815 seconds overtime)
[2012-12-12 16:57:05] Demonbuddy:5072: Delayed start failed! (17,8382329 seconds overtime)
[2012-12-12 16:57:09] Demonbuddy:5072: Delayed start failed! (22,2344843 seconds overtime)
[2012-12-12 16:57:14] Demonbuddy:5072: Delayed start failed! (26,6307358 seconds overtime)
[2012-12-12 16:57:18] Demonbuddy:5072: Delayed start failed! (31,0299874 seconds overtime)
[2012-12-12 16:57:22] Demonbuddy:5072: Delayed start failed! (35,4272389 seconds overtime)
[2012-12-12 16:57:27] Demonbuddy:5072: Delayed start failed! (39,8264905 seconds overtime)
(here stop all + start worked)

after few try abbadoned testing more yar cant run more than 3 copies dunno why and also when one of opened copies crash they wont back up.. dunno why trying to start but unsuccesfully all the time (closing at D III icon in start)
 
Last edited:
L4s3c7k4 said:
another strange thing

[2012-12-12 16:51:12] System.IO.IOException:
w System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
w System.IO.Pipes.PipeStream.EndWrite(IAsyncResult asyncResult)
w System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
w System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
w System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
w System.IO.StreamWriter.Write(Char[] buffer, Int32 index, Int32 count)
w System.IO.TextWriter.WriteLine(String value)
w YetAnotherRelogger.Helpers.Communicator.HandleClient.Send(String msg)
(re-run didnt work)
and

[2012-12-12 16:57:00] Demonbuddy:5072: Delayed start failed! (13,4429815 seconds overtime)
[2012-12-12 16:57:05] Demonbuddy:5072: Delayed start failed! (17,8382329 seconds overtime)
[2012-12-12 16:57:09] Demonbuddy:5072: Delayed start failed! (22,2344843 seconds overtime)
[2012-12-12 16:57:14] Demonbuddy:5072: Delayed start failed! (26,6307358 seconds overtime)
[2012-12-12 16:57:18] Demonbuddy:5072: Delayed start failed! (31,0299874 seconds overtime)
[2012-12-12 16:57:22] Demonbuddy:5072: Delayed start failed! (35,4272389 seconds overtime)
[2012-12-12 16:57:27] Demonbuddy:5072: Delayed start failed! (39,8264905 seconds overtime)
(here stop all + start worked)

after few try abbadoned testing more yar cant run more than 3 copies dunno why and also when one of opened copies crash they wont back up.. dunno why trying to start but unsuccesfully all the time (closing at D III icon in start)
Click to expand...

You're probably using Apoc D3 starter which is currently unfunctional, the only workaround to get multiclients (that I know of) is duplicating your Diablo folder and setting each bot up individually with it's own folder.

Ministry said:
You're probably using Apoc D3 starter which is currently unfunctional, the only workaround to get multiclients (that I know of) is duplicating your Diablo folder and setting each bot up individually with it's own folder.
Click to expand...

I doubt DemonBuddy has the class inbuilt to deal with the security question/website verification prompt. I assume this is an issue because you have a dynamic IP and occasionally it will ask you to verify?
 
sinterlkaas said:
This is a known problem and seems like Blizzard does not like Apoc D3Starter you can use my latest experimental build and clone your Diablo installations




Experimental build:
This is the build which I update more often to test with other people first
https://github.com/sinterlkaas/YetAnotherRelogger/tree/Experimental
In the folder LatestBuild (or click here)will be latest prebuild application for those of you who do not know how to compile the source
Click to expand...

thanks, it seems it work with multiple client.
 
Auth killer is not working?
I have set it up but still i have to kill sessions manually, could you take a look? Its the last thing that this wonderful relogger needs.
 
Probably stupid question but is YAR suppose to auto launch Diablo after it's started? Or I will always have to pres Start?
 
Greldon said:
Have 1 bot and YAR seems a great program for me.
I have only 1 problem: how can i set a relog after a disconnection?
Ip or ping on google seems not work for me...continue to ping and "waiting for a connection".
Someone can explain? Thanks in advance :)
Click to expand...

Help plz :|
 
I have got problem with Yet relogger.
Here is log from DB. The problem appears when my character Join the game and want to TP for the 1 spot.

[17:35:41.052 N] [YAR Kickstart] Load profile: C:\Users\Administrator\Desktop\Btestversion 1.08(Atom 2.0.16)mod\BigRed_CursedHeart.xml
[17:35:41.052 N] Failed to load profile: Path to profile element is not valid; file not found

Please help me with the problem.
 
Akr said:
I have got problem with Yet relogger.
Here is log from DB. The problem appears when my character Join the game and want to TP for the 1 spot.

[17:35:41.052 N] [YAR Kickstart] Load profile: C:\Users\Administrator\Desktop\Btestversion 1.08(Atom 2.0.16)mod\BigRed_CursedHeart.xml
[17:35:41.052 N] Failed to load profile: Path to profile element is not valid; file not found

Please help me with the problem.
Click to expand...

Remove "YAR_Kickstart.xml" from your profile folder and it should work.
 
Still can't manage to run as multiple user. The relogger fails to login in bnet any account opened that way. Great stuff apart from that!
 
I can w/o problems but new version seems to have problems with it its behave strange sometimes its minimaloze to start and u cant maxi it only stop and force start so muliple user seems bugged
 
raghathol said:
Still can't manage to run as multiple user. The relogger fails to login in bnet any account opened that way. Great stuff apart from that!
Click to expand...

the new version gets only one D3 running the other 6 D3's dont start ....
i have updatet all 7 Copies from D3 manual
 
How do I make the D3 window small after I've moved/made it bigger? Where is the resize button? If there is one?
 
I used Apoc's d3 starter before, but now it is broken and i'm trying experimental version of YAR without it.
On launching second instance of diablo I get not responding gray window.

Here is D3Debug log fragment from game installation folder:
Code: 
2012.12.12 20:52:57.878775600	Working Directory: C:\Program Files (x86)\Diablo III
2012.12.12 20:52:57.884840300	OpenMpq - opening update mpq success: Data_D3\PC\MPQs\base\d3-update-base-9558.mpq size=51634657 local=51634657
2012.12.12 20:52:57.885146900	OpenMpq - opening cache mpq failed: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq, sfilegetlasterror: 2012
2012.12.12 20:52:57.885266900	[1] err=2012 text=SFileOpenArchive - Open Failed - Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq
[0] err=4 text=Win32 Open (32) - 'Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq'
2012.12.12 20:52:57.885427600	OpenMpq - cache mpq open failed, delete failed: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq
2012.12.12 20:52:57.885538900	OpenMpq - Failed to open cache mpq: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq, 0
2012.12.12 20:52:57.886271300	OpenMpq - opening update mpq success: Data_D3\PC\MPQs\Win\d3-update-Win-9558.mpq size=110051 local=11005

This is from second instance, first one loads cache mpqs correctly. Any way to fix this?
 
unorthodox said:
I used Apoc's d3 starter before, but now it is broken and i'm trying experimental version of YAR without it.
On launching second instance of diablo I get not responding gray window.

Here is D3Debug log fragment from game installation folder:
Code: 
2012.12.12 20:52:57.878775600	Working Directory: C:\Program Files (x86)\Diablo III
2012.12.12 20:52:57.884840300	OpenMpq - opening update mpq success: Data_D3\PC\MPQs\base\d3-update-base-9558.mpq size=51634657 local=51634657
2012.12.12 20:52:57.885146900	OpenMpq - opening cache mpq failed: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq, sfilegetlasterror: 2012
2012.12.12 20:52:57.885266900	[1] err=2012 text=SFileOpenArchive - Open Failed - Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq
[0] err=4 text=Win32 Open (32) - 'Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq'
2012.12.12 20:52:57.885427600	OpenMpq - cache mpq open failed, delete failed: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq
2012.12.12 20:52:57.885538900	OpenMpq - Failed to open cache mpq: Data_D3\PC\MPQs\Cache\base\patch-base-9558.mpq, 0
2012.12.12 20:52:57.886271300	OpenMpq - opening update mpq success: Data_D3\PC\MPQs\Win\d3-update-Win-9558.mpq size=110051 local=11005

This is from second instance, first one loads cache mpqs correctly. Any way to fix this?
Click to expand...

Did you create a new clone for each bot ?
 
Reloggers working fine for eveyone? just started to mess my things up...... it starts the game but when it launches the bot it closes it very very fast and opens another one, it opens like 10 bots in 5 seconds all for the same instance of d3....
 
i tryed to use the d3 apoc also ... but it seems to then it open the login screen. it opens instead the launcher "updater" and then it cant go further then that..

"didnt happen before patch"
please help.
 
Status
Not open for further replies.
Back
Top