What's new
  • 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.
i gave this a try..how do u schedule profiles i put in more profiles but i think it just repeats the first one
also how do you add a timer between games . seems it starts the next immediately the current one finishes
 
I'm new to YAR, been using Arelog all along. YAR, is so awesome!! It practically everything I need....well, apart from being able to choose Trinity combat routine. Although Giles Trinity is on the list, it doesn't match the name of Trinity plugin (its for the old one, which is no longer supported). I really hope that the dev will add Trinity ASAP =)
 
i think the main problem is - author of the YAR gone and no updates provided.... we need new fresh developer for YAR
 
yeah, I always get this error
"ProfileOrderManager.OnGameJoined, Reloading profile."
when I start a new session. If I close DB YAR will restart it and everything is working fine (2nd time). The problem is if D3 crashed DB will restart as well and producing this error again so the bot is not working -.-
Fresh install without kickstart
 
I'm new to YAR, been using Arelog all along. YAR, is so awesome!! It practically everything I need....well, apart from being able to choose Trinity combat routine. Although Giles Trinity is on the list, it doesn't match the name of Trinity plugin (its for the old one, which is no longer supported). I really hope that the dev will add Trinity ASAP =)

use the experimental build and the "trinity" routine

and yes - so sad.

sinter seems to be finally gone.
 
I am not gone ;) the problem is that I bought a new home and need to do some rebuilding so the relogger is on really low priority and I will continue after the rebuilding is done .. of there are some critical bugs I will fix them
 
I am not gone ;) the problem is that I bought a new home and need to do some rebuilding so the relogger is on really low priority and I will continue after the rebuilding is done .. of there are some critical bugs I will fix them

heyyy man :)
can you add the authenticator support please... its one of the main problem for me i need to manually do it every two days....
 
after a complete internet connection lost - it doesnt kill all d3 and db processes and spams delayed start failed while trying to restart bot instead of killing all processes

Code:
[20:26:45.441 N] [YetAnotherRelogger] Error: Could not read bytes from 00000000 [299]!
[20:26:45.441 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.Internals.Service.BnetHero.()
   at Zeta.Internals.Service.BnetHero.get_BattleTagName()
   at GilesTrinity.Technicals.FileManager.get_LoggingPath()
   at GilesTrinity.ItemRules.Interpreter.reset()
   at GilesTrinity.ItemRules.Interpreter.readConfiguration()
   at GilesTrinity.GilesTrinity.TrinityBotStart(IBot bot)
   at Zeta.CommonBot.BotEvent.Invoke(IBot bot)
   at Zeta.CommonBot.BotMain.Start()
   at YARPLUGIN.YARPLUGIN.HandleResponse(String data) in c:\DB\*\DB300_T1.7.2.1\Plugins\YAR\Plugin.cs:line 432
   at YARPLUGIN.YARPLUGIN.Send(String data, Boolean pause, Boolean xml, Int32 retry, Int32 timeout) in c:\DB\*\DB300_T1.7.2.1\Plugins\YAR\Plugin.cs:line 399

if u find some time... ;-)

if it just would kill the db processes everything would be fine again, when i kill db manually it starts working

this, and that the idle timer restarts bot instead of logout are the only real problems i have.
restarting often results in re-running cleared maps, logout would be nice
 
I am not gone ;) the problem is that I bought a new home and need to do some rebuilding so the relogger is on really low priority and I will continue after the rebuilding is done .. of there are some critical bugs I will fix them

Best news.....ever xd
 
So is YAR not working at all?
I think QuestTools is trolling YAR or the other way around. I can't run DB with yar (even with experimental built and fresh Trinity install on .302).
Any help with that?
 
Good luck with your new home! pm some in-work pics if you feel like it.
For all having issues, make sure you've updated your d3-starter to newest and are using the latest experimental build on github.
 
My YAR stuck and log file looks like this:

D [2013-02-18 13:50:53] Exception: [Potok jest przerwany.]
System.IO.IOException: Potok jest przerwany.
w System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
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)
N [2013-02-18 13:50:55] <D3> D3Starter: Process ID 2876 started.
N [2013-02-18 13:50:55] <D3> D3Starter: Patching process 2876
N [2013-02-18 13:50:56] <D3> D3Starter: Patching file access at address: 81CF4D
N [2013-02-18 13:51:01] <D3> D3Starter failed!
N [2013-02-18 13:51:02] <D3> Stopping
N [2013-02-18 13:51:02] <D3> Diablo:2876: Kill process


What should i Do to prevent this bug?
 
[18/02/2013 13:48:14] <Bryan> Checking plugin: C:\Users\eddy\Desktop\barb\Plugins\YAR\Plugin.cs
[18/02/2013 13:48:14] <Bryan> Plugin is installed and latest version
[18/02/2013 13:48:14] <Bryan> Demonbuddy:4000: Waiting for process to become ready
[18/02/2013 13:48:15] <Bryan> Found Demonbuddy: MainWindow (4719324)
[18/02/2013 13:48:15] <Bryan> ManualPosition window:4719324: X:340 Y:200 W:340 H:200
[18/02/2013 13:48:15] <Bryan> Demonbuddy:4000: Process is ready
[18/02/2013 13:48:15] <Bryan> Demonbuddy:4000: Waiting for demonbuddy to log into Diablo
[18/02/2013 13:51:14] <Bryan> Demonbuddy:4000: Failed to initialize more than 3 times
[18/02/2013 13:51:14] <Bryan> Stopping

same for me i always found some bot not running anymore
 
N [18.02.2013 17:31:21] <D3> Demonbuddy:1204: Delayed start failed! (3443,5156399 seconds overtime)
N [18.02.2013 17:31:25] <D3> Demonbuddy:1204: Delayed start failed! (3448,0260917 seconds overtime)
N [18.02.2013 17:31:30] <D3> Demonbuddy:1204: Delayed start failed! (3452,5209382 seconds overtime)
N [18.02.2013 17:31:34] <D3> Demonbuddy:1204: Delayed start failed! (3457,018769 seconds overtime)
N [18.02.2013 17:31:39] <D3> Demonbuddy:1204: Delayed start failed! (3461,511634 seconds overtime)
N [18.02.2013 17:31:43] <D3> Demonbuddy:1204: Delayed start failed! (3466,022082 seconds overtime)
N [18.02.2013 17:31:48] <D3> Demonbuddy:1204: Delayed start failed! (3470,5169317 seconds overtime)
N [18.02.2013 17:31:52] <D3> Demonbuddy:1204: Delayed start failed! (3475,0429562 seconds overtime)
N [18.02.2013 17:31:57] <D3> Demonbuddy:1204: Delayed start failed! (3479,5690282 seconds overtime)
N [18.02.2013 17:32:01] <D3> Demonbuddy:1204: Delayed start failed! (3484,1106751 seconds overtime)
N [18.02.2013 17:32:06] <D3> Demonbuddy:1204: Delayed start failed! (3488,5899225 seconds overtime)
N [18.02.2013 17:32:10] <D3> Demonbuddy:1204: Delayed start failed! (3493,1003727 seconds overtime)
N [18.02.2013 17:32:15] <D3> Demonbuddy:1204: Delayed start failed! (3497,6118195 seconds overtime)
N [18.02.2013 17:32:19] <D3> Demonbuddy:1204: Delayed start failed! (3502,0890685 seconds overtime)
N [18.02.2013 17:32:24] <D3> Demonbuddy:1204: Delayed start failed! (3506,5839163 seconds overtime)
N [18.02.2013 17:32:28] <D3> Demonbuddy:1204: Delayed start failed! (3511,0787644 seconds overtime)
N [18.02.2013 17:32:33] <D3> Demonbuddy:1204: Delayed start failed! (3515,6339889 seconds overtime)
N [18.02.2013 17:32:37] <D3> Demonbuddy:1204: Delayed start failed! (3520,1268584 seconds overtime)
N [18.02.2013 17:32:42] <D3> Demonbuddy:1204: Delayed start failed! (3524,6373069 seconds overtime)
N [18.02.2013 17:32:46] <D3> Demonbuddy:1204: Delayed start failed! (3529,159679 seconds overtime)
N [18.02.2013 17:32:51] <D3> Demonbuddy:1204: Delayed start failed! (3533,6533765 seconds overtime)
 
To Akr: (somehow I missed the quote button. Doh)

It seems you have a problem with the d3 starter.

Things you can do:
1) Download d3starter last version from here: http://www.thebuddyforum.com/demonb...3-starter-start-multiple-d3s-same-folder.html .First post, click download ;)
2) overwrite d3starter.exe with this new version. d3starter.exe is located at your YAR folder, inside the Third Party folder.
3) If that doesn't help, check d3starter is working properly: launch it on a command line like this: D3Starter.exe "C:\Diablo3\Diablo III.exe" 5. "C:\Diablo3\Diablo III.exe" is the path to your diabloIII executable, change it accordingly. This should launch 5 d3 windows.
4) Note you have to execute Yar as admin, or at least set on the d3 starter to be executed as admin, to work properly.

I hope it helps; though problems could be related to your OS language being Polish (it seems) . Mine is spanish and I have some similar problems too. Guess we'll have to wait for Sinterklaas to finish up his new home stuff to get him back on track.
 
Last edited:
Status
Not open for further replies.
Back
Top