What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

R-YAR - rrrix's YAR fork

Hey, I've got a question. YAR is working for me however when I first loaded it up it opens diablo3 like its supposed to but hangs on the Authenticator login portion. I manually put it in and it went to work just fine. But I was wondering if there is anyway around this or if I missed a step setting it up.
I set it up using the quick guide several pages back. Also is there a more detailed guide out there??

Edit:
I managed to figure out the authenticator, but now it won't even log me in. It attempts to but it's putting my password into the login id field. not sure what to do, can anyone help?
couple pages back it said somthing about leaving your login and pw blank not sure might be what your talking about
 
couple pages back it said somthing about leaving your login and pw blank not sure might be what your talking about


Thanks for the feedback but unfortunately i cant seem to uncheck the remember my login ID option on the D3 login screen. What i mean is i can uncheck it, but once i exit D3 and go back in with YAR it still has my ID and box checked :(
 
Weird

N [5/15/2014 3:55:42 PM] <Leveling> Continue normal schedule
N [5/15/2014 3:55:42 PM] <Leveling> We are scheduled to start
N [5/15/2014 3:55:42 PM] Relogger Crashed! with message Could not load file or assembly 'Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
D [5/15/2014 3:55:42 PM] Exception: [Could not load file or assembly 'Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.]
System.IO.FileNotFoundException: Could not load file or assembly 'Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null'
at YetAnotherRelogger.Helpers.Bot.DiabloClass.Start()
at YetAnotherRelogger.Relogger.StartBoth(BotClass bot)
at YetAnotherRelogger.Relogger.ReloggerWorker()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

N [5/15/2014 3:55:42 PM] Waiting 10 seconds and try again!
 
Not at all sure. Its stuff with the reg, but i dont need to enable logging...
 
so with the section for it to log into the auth site and kill max sessions, is that broke or does it just spam in DB for a while and eventually fix it
 
I suspect it's ok to post the old version for others? If not, I'd ask that the mod please delete this post and accept my apologies; I'm just trying to help out the guys that accidentally deleted the older version...

PS: Always back up EVERYTHING!


Yar version 1.1.5239.21281 works great for me still

View attachment YetAnotherRelogger-master.zip
 
Thanks for this :)

I suspect it's ok to post the old version for others? If not, I'd ask that the mod please delete this post and accept my apologies; I'm just trying to help out the guys that accidentally deleted the older version...

PS: Always back up EVERYTHING!


Yar version 1.1.5239.21281 works great for me still

View attachment 129306
 
Hi i all the time get:


V [17.05.2014 09:05:01] Relogger Thread Starting!
N [17.05.2014 09:05:02] rrrix's Yet Another Relogger fork Version
N [17.05.2014 09:05:17] <hammersmash> We are scheduled to start
N [17.05.2014 09:05:18] Relogger Crashed! with message Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
D [17.05.2014 09:05:18] Exception: [Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.]
System.IO.FileNotFoundException: Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null"
bei YetAnotherRelogger.Helpers.Bot.DiabloClass.Start()
bei YetAnotherRelogger.Relogger.StartBoth(BotClass bot)
bei YetAnotherRelogger.Relogger.ReloggerWorker()

WRN: Protokollierung der Assemblybindung ist AUS.
Sie können die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler führt zu einer gewissen Leistungseinbuße.
Sie können dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.

N [17.05.2014 09:05:18] Waiting 10 seconds and try again!
N [17.05.2014 09:05:28] Relogger Crashed! with message Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
D [17.05.2014 09:05:28] Exception: [Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.]
System.IO.FileNotFoundException: Die Datei oder Assembly "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: "Authenticator, Version=2.0.10.190, Culture=neutral, PublicKeyToken=null"
bei YetAnotherRelogger.Helpers.Bot.DiabloClass.Start()
bei YetAnotherRelogger.Relogger.StartBoth(BotClass bot)
bei YetAnotherRelogger.Relogger.ReloggerWorker()

WRN: Protokollierung der Assemblybindung ist AUS.
Sie können die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler führt zu einer gewissen Leistungseinbuße.
Sie können dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.

N [17.05.2014 09:05:28] Waiting 10 seconds and try again!




Any idea? its windows 8.1 .
 
Last edited:
"Stopping the bot. Reason:YetAnotherRelogger -> Load new profile"
and my Chars die, because in fight -.-
how can I prevent that?
 
Same error as 2 weeks ago any word yet, this is on the newest version and older version of YAR, same message
3 hours in
************** Exception Text **************
System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
at System.Runtime.InteropServices.Marshal.AllocCoTaskMem(Int32 cb)
at System.Windows.Forms.UnsafeNativeMethods.GetWindowText(HandleRef hWnd, StringBuilder lpString, Int32 nMaxCount)
at System.Windows.Forms.Control.get_WindowText()
at System.Windows.Forms.TextBoxBase.get_WindowText()
at System.Windows.Forms.TextBoxBase.ScrollToCaret()
at YetAnotherRelogger.Forms.MainForm2.richTextBox1_TextChanged(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.WmReflectCommand(Message& m)
at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
at System.Windows.Forms.RichTextBox.WmReflectCommand(Message& m)
at System.Windows.Forms.RichTextBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
Code:
N [5/17/2014 23:42:50] ####[ Detecting Screens ]####
N [5/17/2014 23:42:50] - Primary Screen 0: X:0,Y:0,W:1440,H:900 Enabled:True
N [5/17/2014 23:42:50] Name: \\.\DISPLAY1
N [5/17/2014 23:42:50] Device: NVIDIA GeForce GTX 580
N [5/17/2014 23:42:50] WorkingArea: X:0,Y:0,W:1440,H:870
N [5/17/2014 23:42:50] ######################
V [5/17/2014 23:42:51] Relogger Thread Starting!
N [5/17/2014 23:42:52] rrrix's Yet Another Relogger fork Version 
N [5/17/2014 23:44:21] Adding new bot: ghom
N [5/17/2014 23:44:42] <ghom> Stopping
V [5/17/2014 23:44:42] Relogger Thread Starting!
N [5/17/2014 23:45:01] Editing bot: ghom
N [5/17/2014 23:45:03] <ghom> We are scheduled to start
N [5/17/2014 23:45:03] <ghom> Language set: English (Brittain) : enGB
N [5/17/2014 23:45:03] <ghom> Region set: Europe : eu.actual.battle.net
N [5/17/2014 23:45:22] <ghom> Diablo:3992: Found D3 Main Window (328506)
N [5/17/2014 23:45:27] <ghom> Diablo:3992: Waiting for process to become ready
N [5/17/2014 23:45:29] <ghom> Diablo:3992: Process is ready
N [5/17/2014 23:45:29] <ghom> Demonbuddy start delay, waiting 10 seconds
N [5/17/2014 23:45:39] <ghom> Current profile: "Instant Leave.xml" Runs:0 Time:0 mintues (C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\Instant Leave.xml)
N [5/17/2014 23:45:39] <ghom> Generate new Kickstart profile: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:45:39] <ghom> Using Scheduled Profile C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:45:39] <ghom> Installing latest plugin: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Plugins\YAR\Plugin.cs
N [5/17/2014 23:45:39] <ghom> Demonbuddy:3744: Waiting for process to become ready
N [5/17/2014 23:45:42] <ghom> Found Demonbuddy - BETA: MainWindow (394282)
N [5/17/2014 23:45:42] <ghom> Demonbuddy:3744: Process is ready
N [5/17/2014 23:45:42] <ghom> Demonbuddy:3744: Waiting for demonbuddy to log into Diablo
N [5/17/2014 23:45:53] <ghom> Demonbuddy:3744: Process is not responding, Closing main Window!
N [5/17/2014 23:45:54] <ghom> Diablo:3992: Process is not running
N [5/17/2014 23:45:54] <ghom> Language set: English (Brittain) : enGB
N [5/17/2014 23:45:54] <ghom> Region set: Europe : eu.actual.battle.net
N [5/17/2014 23:46:08] <ghom> Diablo:804: Found D3 Main Window (263598)
N [5/17/2014 23:46:12] <ghom> Diablo:804: Waiting for process to become ready
N [5/17/2014 23:46:16] <ghom> Diablo:804: Process is ready
N [5/17/2014 23:46:16] <ghom> Demonbuddy start delay, waiting 10 seconds
N [5/17/2014 23:46:26] <ghom> Demonbuddy:3744: Found matching log: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Logs\3744 2014-05-17 23.45.txt
N [5/17/2014 23:46:28] <ghom> Demonbuddy:3744: Failed to find login time
N [5/17/2014 23:46:28] <ghom> Delete old Kickstart profile: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:46:28] <ghom> Generate new Kickstart profile: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:46:28] <ghom> Using Scheduled Profile C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:46:28] <ghom> Installing latest plugin: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Plugins\YAR\Plugin.cs
N [5/17/2014 23:46:28] <ghom> Demonbuddy:4012: Waiting for process to become ready
N [5/17/2014 23:46:30] <ghom> Found Demonbuddy - BETA: MainWindow (394042)
N [5/17/2014 23:46:30] <ghom> Demonbuddy:4012: Process is ready
N [5/17/2014 23:46:30] <ghom> Demonbuddy:4012: Waiting for demonbuddy to log into Diablo
N [5/17/2014 23:46:41] <ghom> Demonbuddy:4012: Process is not responding, Closing main Window!
N [5/17/2014 23:46:42] <ghom> Diablo:804: Process is not running
N [5/17/2014 23:46:42] <ghom> Language set: English (Brittain) : enGB
N [5/17/2014 23:46:42] <ghom> Region set: Europe : eu.actual.battle.net
N [5/17/2014 23:46:56] <ghom> Diablo:2572: Found D3 Main Window (394670)
N [5/17/2014 23:47:00] <ghom> Diablo:2572: Waiting for process to become ready
N [5/17/2014 23:47:01] <ghom> Diablo:2572: Process is ready
N [5/17/2014 23:47:01] <ghom> Demonbuddy start delay, waiting 10 seconds
N [5/17/2014 23:47:11] <ghom> Demonbuddy:4012: Found matching log: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Logs\4012 2014-05-17 23.46.txt
N [5/17/2014 23:47:12] <ghom> Demonbuddy:4012: Failed to find login time
N [5/17/2014 23:47:12] <ghom> Delete old Kickstart profile: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:47:12] <ghom> Generate new Kickstart profile: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:47:12] <ghom> Using Scheduled Profile C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Profiles\Three Musketeers 0.8\Ghom\Face-to-face\YAR_Kickstart.xml
N [5/17/2014 23:47:12] <ghom> Installing latest plugin: C:\Users\Administrator\Desktop\DemonbuddyBETA_1.1.1882.407\Plugins\YAR\Plugin.cs
N [5/17/2014 23:47:12] <ghom> Demonbuddy:3920: Waiting for process to become ready
N [5/17/2014 23:47:15] <ghom> Found Demonbuddy - BETA: MainWindow (263570)
N [5/17/2014 23:47:15] <ghom> Demonbuddy:3920: Process is ready
N [5/17/2014 23:47:15] <ghom> Demonbuddy:3920: Waiting for demonbuddy to log into Diablo
N [5/17/2014 23:47:25] <ghom> Demonbuddy:3920: Process is not responding, Closing main Window!
N [5/17/2014 23:47:26] <ghom> Diablo:2572: Process is not running
N [5/17/2014 23:47:26] <ghom> Language set: English (Brittain) : enGB
N [5/17/2014 23:47:26] <ghom> Region set: Europe : eu.actual.battle.net
N [5/17/2014 23:47:31] <ghom> Stopping
N [5/17/2014 23:47:31] <ghom> Demonbuddy:3920: Closing window
N [5/17/2014 23:47:31] <ghom> Demonbuddy:3920: Failed to close! kill process
N [5/17/2014 23:47:31] <ghom> Diablo:2764: Kill process
V [5/17/2014 23:47:31] Relogger Thread Starting!
N [5/17/2014 23:47:41] Editing bot: ghom
N [5/17/2014 23:47:44] Closed!

Still keeps restarting everything over cause diablo 3 supposedly doesnt respond. Yet when i manually star the bot everything works fine.
Guess ill just have to give up on this one, hasnt been working for me for several weeks now.
 
Still keeps restarting everything over cause diablo 3 supposedly doesnt respond. Yet when i manually star the bot everything works fine.
Guess ill just have to give up on this one, hasnt been working for me for several weeks now.

Uncheck this:

rjqsJp5.png
 
When I open DB with YAR it has no plugins but when I open DB manually it does. Don't know whats happening here, YAR is using the proper directory and everything
 
When I open DB with YAR it has no plugins but when I open DB manually it does. Don't know whats happening here, YAR is using the proper directory and everything

run db without yar have all the plugin enabled.
close db
go to setting/account#xxxx/charactersetthing.xml
check if the your plugins are saved and enabled:
Code:
  <EnabledPlugins>
    <Value>BuddyStats</Value>
    <Value>GearSwap</Value>
    <Value>LumberJack</Value>
    <Value>QuestTools</Value>
    <Value>Trinity</Value>
    <Value>YAR Comms</Value>
  </EnabledPlugins>
run yar with force enable plugins.

should work.
 
When I open DB with YAR it has no plugins but when I open DB manually it does. Don't know whats happening here, YAR is using the proper directory and everything

This happens to me too - it's actually a bug in Demonbuddy (if you close and re-launch it too quickly, I believe). It's hard to reproduce consistently which makes it even harder to fix. Plugins aren't compiled for some reason when this happens.
 
Back
Top