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

R-YAR - rrrix's YAR fork

RRIX your awesome dude. I will continue to donate to your awesomeness. Now, Is there a way to set the order on profiles? I want my "main" to load first then the "slaves" so that simplefollow knows who is who. It seems to just load randomly from the list when I hit start all.

Second question.

What does "Force start" actually mean?
 
I like the relogger because it keeps my game from crashing and staying down.

Only complaint, is it intentional that if you have YAR running, you cannot edit anything in Settings > Bot within DB?
It's really annoying to stop YAR, then reload D3 and DB just to change my difficulty or protected item spots.

Even then, when I adjust protected spots. It just ignores it.
 
Last edited:
Reneza said:
Just to reinforce this issue, YAR doesn't seem to load any plugin in db since 2.1, it was working fine prior to the latest patch.
Click to expand...

Not sure why this was happening but I found a solution/partial solution to it.

MY STORY: So for me after installing a fresh copy of the newest DB since 2.1 my YAR wasn't working properly. It would start my diablo.exe and than demonbuddy.exe but my DB's plugin page would be blank and no plugins would be loaded. After messing around with it a bit I found a solution.

SOLUTION/PARTIAL SOLUTION: Terminated your DB process in YAR (Right click the specific bot you are running -> Kill Demonbuddy) YAR then reloaded my demonbuddy and it would work fine, however note that if I were to close YAR and restart it the process would be the same. The 1st time I start YAR DB's plugin page would be blank, but if I kill DB's process in YAR the next restart of DB would have the plugin's page available and working.

Each time I close YAR completely and open it again the problem would resurface.
 
quick question. What's the point of reducing the window size? for performance?
 
i unzipped the file into its own folder start up /lastestbuild/yar.exe but once the software up running, it never detects any of my D3 client/DB in the upper box, any ideas?
 
All of a sudden, YAR doesn't start. Any idea what could be causing this issue and how to fix it?
Log is below (yes, that's the entire log)

N [08-Sep-14 11:44:26 PM] System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Root element is missing. (C:\Users\Name\AppData\Local\YetAnotherRelogger\YetAnotherRelogger.exe_Url_1x4ccr4fl3ieb20zvbryfktokmselewi\1.1.5258.17114\user.config) ---> System.Xml.XmlException: Root element is missing.
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Configuration.XmlUtil..ctor(Stream stream, String name, Boolean readToFirstElement, ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.InitConfigFromFile()
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
--- End of inner exception stack trace ---
at System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
at System.Configuration.Internal.InternalConfigRoot.RemoveConfigImpl(String configPath, BaseConfigurationRecord configRecord)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
at YetAnotherRelogger.Properties.Settings.get_AutoPosScreens()
at YetAnotherRelogger.Program.Main()
N [08-Sep-14 11:44:26 PM] Closed!

I believe it has something to do with "C:\Users\Name\AppData\Local\YetAnotherRelogger\YetAnotherRelogger.exe_Url_1x4ccr4fl3ieb20zvbryfktokmselewi\1.1.5258.17114\user.config", but what? There is a config file at that location, but it seems corrupted (in a text editor it's not readable, contains a few lines of NUL)

Edit: nvm, was an easy fix - just deleting the file mentioned above.
 
YAR doesn´t start how I want it:

db version: .374
Trinity: 2.1.7
Questtools: 2.1.22

first: he doesn´t put in my password in my startaccount diablo3
second: he doesn´t start my profil: rift bot explore

Exception during bot tick.Buddy.Coroutines.CoroutineUnhandledException: Exception was thrown by coroutine ---> System.ArgumentException: bnetpassword has been specified more than once, expecting single value
bei Zeta.Common.Arguments.(String )
bei Zeta.Common.Arguments.Single(String argument)
bei Zeta.Bot.Logic.BrainBehavior.get_BnetPassword()
bei Zeta.Bot.Logic.BrainBehavior.<HandleOutOfGame>d__a1.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
bei Zeta.Bot.ActionRunCoroutine....()
--- Ende der internen Ausnahmestapelüberwachung ---
bei Buddy.Coroutines.Coroutine.CheckPostConditions(Boolean shouldBeCanceled)
bei Buddy.Coroutines.Coroutine.Resume(Boolean forStop)
bei Buddy.Coroutines.Coroutine.Resume()
bei Zeta.Bot.ActionRunCoroutine.Run(Object context)
bei Zeta.TreeSharp.Action.RunAction(Object context)
bei Zeta.TreeSharp.Action..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.Common.HookExecutor.Run(Object context)
bei Zeta.TreeSharp.Action.RunAction(Object context)
bei Zeta.TreeSharp.Action..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.Decorator..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.TreeSharp.PrioritySelector..()
bei Zeta.TreeSharp.Composite.Tick(Object context)
bei Zeta.Bot.BotMain.()


when I start everything manuel I works fine. So when I put in the password by myself and push the startbutton.
 
Anti idle for gold timer doesn't work maybe because I have 800 mill? Tried testing it multiple times and it will force restart thinking its not picking up gold. Also my Kadala plugin never seems to work when I have YAR running.
 
Last edited:
1.D3 start
2.DB start log in
3.D3 log in..........D3 crash End =,=



logs here
https://www.thebuddyforum.com/-and-...770-and-21306-/demonbuddy-/176730-yar-d3.html




141440d1410133327-yar-d3-png




V [2014/9/8 7:28:57] Relogger Thread Starting!
N [2014/9/8 7:28:57] rrrix's Yet Another Relogger fork Version
N [2014/9/8 7:30:22] Adding new bot: DD
N [2014/9/8 7:33:10] <DD> We are scheduled to start
N [2014/9/8 7:33:10] <DD> Language set: Chinese : zhCN
N [2014/9/8 7:33:10] <DD> Region set: Asia : kr.actual.battle.net
N [2014/9/8 7:33:23] <DD> Diablo:7340: Found D3 Main Window (1247186)
N [2014/9/8 7:33:27] <DD> Diablo:7340: Waiting for process to become ready
N [2014/9/8 7:33:28] <DD> Diablo:7340: Process is ready
N [2014/9/8 7:33:28] <DD> Demonbuddy start delay, waiting 10 seconds
N [2014/9/8 7:33:38] <DD> Current profile: "act1.xml" Runs:0 Time:0 mintues (D:\del\Demonbuddy\jb\box\box\act1.xml)
N [2014/9/8 7:33:38] <DD> Delete old Kickstart profile: D:\del\Demonbuddy\jb\box\box\YAR_Kickstart.xml
N [2014/9/8 7:33:38] <DD> Generate new Kickstart profile: D:\del\Demonbuddy\jb\box\box\YAR_Kickstart.xml
N [2014/9/8 7:33:38] <DD> Using Scheduled Profile D:\del\Demonbuddy\jb\box\box\YAR_Kickstart.xml
N [2014/9/8 7:33:38] <DD> Installing latest plugin: D:\del\Demonbuddy\Plugins\YAR\Plugin.cs
N [2014/9/8 7:33:38] <DD> Demonbuddy:6844: Waiting for process to become ready
N [2014/9/8 7:33:40] <DD> Found Demonbuddy: MainWindow (1705254)
N [2014/9/8 7:33:40] <DD> Demonbuddy:6844: Process is ready
N [2014/9/8 7:33:40] <DD> Demonbuddy:6844: Waiting for demonbuddy to log into Diablo
N [2014/9/8 7:34:38] <DD> Demonbuddy:6844: Process is not responding, Closing main Window!
N [2014/9/8 7:34:39] <DD> Diablo:7340: Process is not running
N [2014/9/8 7:34:40] <DD> Language set: Chinese : zhCN
N [2014/9/8 7:34:40] <DD> Region set: Asia : kr.actual.battle.net
N [2014/9/8 7:34:47] <DD> Stopping
N [2014/9/8 7:34:47] <DD> Demonbuddy:6844: Closing window
N [2014/9/8 7:34:47] <DD> Demonbuddy:6844: Failed to close! kill process
N [2014/9/8 7:34:47] <DD> Diablo:3340: Kill process
N [2014/9/8 7:34:47] <DD> Diablo:3340: Waiting for process to become ready
N [2014/9/8 7:34:47] <DD> Diablo:3340: Failed to start!
N [2014/9/8 7:34:47] <DD> Restarting...
N [2014/9/8 7:34:52] Closed!




N [2014/9/8 6:57:35] ####[ Detecting Screens ]####
N [2014/9/8 6:57:35] - Primary Screen 0: X:0,Y:0,W:1920,H:1080 Enabled:True
N [2014/9/8 6:57:35] Name: \\.\DISPLAY1
N [2014/9/8 6:57:35] Device: NVIDIA GeForce GTX 460
N [2014/9/8 6:57:35] WorkingArea: X:0,Y:0,W:1920,H:1040
N [2014/9/8 6:57:35] ######################
V [2014/9/8 6:57:35] Relogger Thread Starting!
N [2014/9/8 6:57:36] rrrix's Yet Another Relogger fork Version
N [2014/9/8 6:59:25] Adding new bot: D
N [2014/9/8 6:59:30] <D> We are scheduled to start
N [2014/9/8 6:59:30] <D> Language set: Chinese : zhCN
N [2014/9/8 6:59:30] <D> Region set: Asia : kr.actual.battle.net
N [2014/9/8 6:59:45] <D> Diablo:3832: Found D3 Main Window (2556372)
N [2014/9/8 6:59:48] <D> Diablo:3832: Waiting for process to become ready
N [2014/9/8 6:59:49] <D> Diablo:3832: Process is ready
N [2014/9/8 6:59:49] <D> Demonbuddy start delay, waiting 10 seconds
N [2014/9/8 6:59:59] <D> Current profile: "Rift Bot Common.xml" Runs:0 Time:0 mintues (D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\Rift Bot Common.xml)
N [2014/9/8 6:59:59] <D> Delete old Kickstart profile: D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 6:59:59] <D> Generate new Kickstart profile: D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 6:59:59] <D> Using Scheduled Profile D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 6:59:59] <D> Installing latest plugin: D:\del\Demonbuddy\Plugins\YAR\Plugin.cs
N [2014/9/8 6:59:59] <D> Demonbuddy:2108: Waiting for process to become ready
N [2014/9/8 7:00:02] <D> Found Demonbuddy: MainWindow (853950)
N [2014/9/8 7:00:02] <D> Demonbuddy:2108: Process is ready
N [2014/9/8 7:00:02] <D> Demonbuddy:2108: Waiting for demonbuddy to log into Diablo
N [2014/9/8 7:00:49] <D> Demonbuddy:2108: Process is not responding, Closing main Window!
N [2014/9/8 7:00:50] <D> Diablo:3832: Process is not running
N [2014/9/8 7:00:50] <D> Language set: Chinese : zhCN
N [2014/9/8 7:00:50] <D> Region set: Asia : kr.actual.battle.net
N [2014/9/8 7:01:02] <D> Diablo:2428: Found D3 Main Window (1378232)
N [2014/9/8 7:01:05] <D> Diablo:2428: Waiting for process to become ready
N [2014/9/8 7:01:07] <D> Diablo:2428: Process is ready
N [2014/9/8 7:01:07] <D> Demonbuddy start delay, waiting 10 seconds
N [2014/9/8 7:01:17] <D> Demonbuddy:2108: Found matching log: D:\del\Demonbuddy\Logs\2108 2014-09-08 07.00.txt
N [2014/9/8 7:01:17] <D> Demonbuddy:2108: Failed to find login time
N [2014/9/8 7:01:17] <D> Delete old Kickstart profile: D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 7:01:17] <D> Generate new Kickstart profile: D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 7:01:17] <D> Using Scheduled Profile D:\del\Demonbuddy\jb\yellowdoor\秘境脚本445-9.5号更新\YAR_Kickstart.xml
N [2014/9/8 7:01:17] <D> Installing latest plugin: D:\del\Demonbuddy\Plugins\YAR\Plugin.cs
N [2014/9/8 7:01:17] <D> Demonbuddy:3308: Waiting for process to become ready
N [2014/9/8 7:01:20] <D> Found Demonbuddy: MainWindow (4129878)
N [2014/9/8 7:01:20] <D> Demonbuddy:3308: Process is ready
N [2014/9/8 7:01:20] <D> Demonbuddy:3308: Waiting for demonbuddy to log into Diablo
N [2014/9/8 7:01:36] <D> Stopping
N [2014/9/8 7:01:36] <D> Demonbuddy:3308: Closing window
N [2014/9/8 7:01:37] <D> Demonbuddy:3308: Failed to initialize 1/15
N [2014/9/8 7:01:46] <D> Demonbuddy:3308: Failed to close! kill process
N [2014/9/8 7:01:51] Closed!
 
Last edited:
I found DB 377 works not so well, I use the 374, it's better now, game no crash end.
 
Do you guys have any idea why the relogger doesnt start the bot alone?
I always have to press start and that kinda ruins it for me.
Any ideas?
 
R-YAR [1.1.5258.17114] BETA.webp

How to load a profile in demonbuddy with YAR please ? Doesn't work for me
 
Last edited:
Reneza said:
Not sure why this was happening but I found a solution/partial solution to it.

MY STORY: So for me after installing a fresh copy of the newest DB since 2.1 my YAR wasn't working properly. It would start my diablo.exe and than demonbuddy.exe but my DB's plugin page would be blank and no plugins would be loaded. After messing around with it a bit I found a solution.

SOLUTION/PARTIAL SOLUTION: Terminated your DB process in YAR (Right click the specific bot you are running -> Kill Demonbuddy) YAR then reloaded my demonbuddy and it would work fine, however note that if I were to close YAR and restart it the process would be the same. The 1st time I start YAR DB's plugin page would be blank, but if I kill DB's process in YAR the next restart of DB would have the plugin's page available and working.

Each time I close YAR completely and open it again the problem would resurface.
Click to expand...

Thanks for this. your partial solution worked...partially.

I am running 2 instances of DB. The first instance loads all the plugins just fine, even after a crash,etc.
My second instance was not loading any plugins at all. However I tried your trick and it loads Trinity now, but not questTools or my key run plug in.
 
Anti "Max sessions" function does not work.
Username and password for buddyauth.com has been entered.
 
YAR seems to use the same settings for every bot when running via ISboxer how can it separate settings so that the bots can run different Trinity setups?
EDIT: The fix was easy I must have been tired. Create separate DB client folders for each window to allow private settings for each.
 
Last edited:
YAR its failing at what it was made to do. When I disconnect it doesn't connect me back.
 
Hi Guyz,
First of all many thanks for the plugin. It works wonders.
I think I have crashed a session, it is the second time it happens to me. I remember last time I had to erase some settings files that were corrupted in a folder like user something. Would anyone know to find these files?
Many thanks!
 
You must log in or register to reply here.
Back
Top