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

R-YAR - rrrix's YAR fork

One out of 7 bots gives "Sequence not initiated" no idea why... So frustrating

Any one else getting this?
 
Error while starting botSystem.InvalidOperationException: Sequence contains no elements
at System.Linq.Enumerable.Min(IEnumerable`1 source)
at Zeta.Bot.Navigation.MainGridProvider.Update()
at Trinity.Trinity.TrinityBotStart(IBot bot)
at Zeta.Bot.BotEvent.Invoke(IBot bot)
at Zeta.Bot.BotMain.Start()
at Demonbuddy.MainWindow.HandleStartStopBot()

This the error
 
okay after night i see near 17 small errors window "Application closed - DiabloIII", so it restarts many times:D
and strange thing - i have only 5 bots and diablo folders but there was 6! thats mean one bot doesnt works, because if we launch 2 dialos from one folder one of them will be blank
 

Attachments

Last edited by a moderator:
Hello,

I'm used this bot a year ago i think I wanted to start again, but when i put this plugin into the plugin floders nothing shows op
what am i doing wrong ?
 
Hello,

I'm used this bot a year ago i think I wanted to start again, but when i put this plugin into the plugin floders nothing shows op
what am i doing wrong ?

Its doesnt work like that. It is more of a program then a plugin. Unzip it, you can create it's own folder, then goto \latestbuild\ folder and run it. After you set it up (pretty easy to do), it will launch DB and be in the plugin tab once it launches your d3 and db.
 
all good whole night - only 3 crashes of ONE bot, another 4 works fine without single restart

to compare with last time i reported 17 restart during night:D
 
Code:
N [9.3.2014 22:46:54] <bot2> Demonbuddy:3608: Process is ready
N [9.3.2014 22:46:54] <bot2> Demonbuddy:3608: Waiting for demonbuddy to log into Diablo
N [9.3.2014 22:49:53] <bot2> Demonbuddy:3608: Failed to initialize 13/15
N [9.3.2014 22:49:53] <bot2> Demonbuddy:3608: Process is not responding, Closing main Window!
N [9.3.2014 22:49:54] <bot2> Demonbuddy:3608: Process is not running
N [9.3.2014 22:49:54] <bot2> Demonbuddy:3608: Found matching log: C:\Users\bofy\d3\DB\Logs\3608 2014-03-09 22.46.txt
N [9.3.2014 22:49:58] <bot2> Demonbuddy:3608: Failed to find login time
N [9.3.2014 22:49:58] <bot2> Delete old Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:49:58] <bot2> Generate new Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:49:58] <bot2> Using Scheduled Profile C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:49:58] <bot2> Installing latest plugin: C:\Users\bofy\d3\DB\Plugins\YAR\Plugin.cs
N [9.3.2014 22:49:58] <bot2> Demonbuddy:5076: Waiting for process to become ready
N [9.3.2014 22:49:59] <bot2> Found Demonbuddy: MainWindow (1444018)
N [9.3.2014 22:49:59] <bot2> Demonbuddy:5076: Process is ready
N [9.3.2014 22:49:59] <bot2> Demonbuddy:5076: Waiting for demonbuddy to log into Diablo
N [9.3.2014 22:52:58] <bot2> Demonbuddy:5076: Failed to initialize 14/15
N [9.3.2014 22:52:58] <bot2> Demonbuddy:5076: Process is not responding, Closing main Window!
N [9.3.2014 22:52:59] <bot2> Demonbuddy:5076: Process is not running
N [9.3.2014 22:52:59] <bot2> Demonbuddy:5076: Found matching log: C:\Users\bofy\d3\DB\Logs\5076 2014-03-09 22.49.txt
N [9.3.2014 22:53:04] <bot2> Demonbuddy:5076: Failed to find login time
N [9.3.2014 22:53:04] <bot2> Delete old Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:53:04] <bot2> Generate new Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:53:04] <bot2> Using Scheduled Profile C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:53:04] <bot2> Installing latest plugin: C:\Users\bofy\d3\DB\Plugins\YAR\Plugin.cs
N [9.3.2014 22:53:04] <bot2> Demonbuddy:3352: Waiting for process to become ready
N [9.3.2014 22:53:05] <bot2> Found Demonbuddy: MainWindow (1509518)
N [9.3.2014 22:53:05] <bot2> Demonbuddy:3352: Process is ready
N [9.3.2014 22:53:05] <bot2> Demonbuddy:3352: Waiting for demonbuddy to log into Diablo
N [9.3.2014 22:56:04] <bot2> Demonbuddy:3352: Failed to initialize more than 15 times
N [9.3.2014 22:56:04] <bot2> Standby!
N [9.3.2014 22:56:04] <bot2> Diablo:3900: Kill process
N [9.3.2014 22:56:04] <bot2> Demonbuddy:3352: Closing window
N [9.3.2014 22:56:04] <bot2> Demonbuddy:3352: Waiting to close
N [9.3.2014 22:56:07] <bot2> Demonbuddy:3352: Closed.
N [9.3.2014 22:59:13] <bot2> Diablo:3900: Process is not running
N [9.3.2014 22:59:13] <bot2> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
N [9.3.2014 22:59:13] <bot2> Language set: English (Brittain) : enGB
N [9.3.2014 22:59:13] <bot2> Region set: Europe : eu.actual.battle.net
N [9.3.2014 22:59:38] <bot2> Diablo:5052: Found D3 Main Window (854184)
N [9.3.2014 22:59:42] <bot2> Diablo:5052: Waiting for process to become ready
N [9.3.2014 22:59:44] <bot2> Diablo:5052: Process is ready
N [9.3.2014 22:59:44] <bot2> Demonbuddy start delay, waiting 10 seconds
N [9.3.2014 22:59:54] <bot2> Demonbuddy:3352: Found matching log: C:\Users\bofy\d3\DB\Logs\3352 2014-03-09 22.53.txt
N [9.3.2014 22:59:57] <bot2> Demonbuddy:3352: Failed to find login time
N [9.3.2014 22:59:57] <bot2> Delete old Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:59:57] <bot2> Generate new Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:59:57] <bot2> Using Scheduled Profile C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 22:59:57] <bot2> Installing latest plugin: C:\Users\bofy\d3\DB\Plugins\YAR\Plugin.cs
N [9.3.2014 22:59:58] <bot2> Demonbuddy:2528: Waiting for process to become ready
N [9.3.2014 22:59:59] <bot2> Found Demonbuddy: MainWindow (460602)
N [9.3.2014 22:59:59] <bot2> Demonbuddy:2528: Process is ready
N [9.3.2014 22:59:59] <bot2> Demonbuddy:2528: Waiting for demonbuddy to log into Diablo
N [9.3.2014 23:02:58] <bot2> Demonbuddy:2528: Failed to initialize more than 15 times
N [9.3.2014 23:02:58] <bot2> Standby!
N [9.3.2014 23:02:58] <bot2> Diablo:5052: Kill process
N [9.3.2014 23:02:58] <bot2> Demonbuddy:2528: Closing window
N [9.3.2014 23:02:58] <bot2> Demonbuddy:2528: Waiting to close
N [9.3.2014 23:02:59] <bot2> Demonbuddy:2528: Closed.
N [9.3.2014 23:32:59] <bot2> Deleting: C:\ProgramData\Battle.net\Agent\agent.db
N [9.3.2014 23:32:59] <bot2> Language set: English (Brittain) : enGB
N [9.3.2014 23:32:59] <bot2> Region set: Europe : eu.actual.battle.net
N [9.3.2014 23:33:11] <bot2> Diablo:4388: Found D3 Main Window (6686880)
N [9.3.2014 23:33:13] <bot2> Diablo:4388: Waiting for process to become ready
N [9.3.2014 23:33:15] <bot2> Diablo:4388: Process is ready
N [9.3.2014 23:33:15] <bot2> Demonbuddy start delay, waiting 10 seconds
N [9.3.2014 23:33:25] <bot2> Demonbuddy:2528: Found matching log: C:\Users\bofy\d3\DB\Logs\2528 2014-03-09 22.59.txt
N [9.3.2014 23:33:27] <bot2> Demonbuddy:2528: Failed to find login time
N [9.3.2014 23:33:27] <bot2> Delete old Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 23:33:27] <bot2> Generate new Kickstart profile: C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 23:33:27] <bot2> Using Scheduled Profile C:\Users\bofy\d3\DB\Profiles\YAR_Kickstart.xml
N [9.3.2014 23:33:27] <bot2> Installing latest plugin: C:\Users\bofy\d3\DB\Plugins\YAR\Plugin.cs
N [9.3.2014 23:33:27] <bot2> Demonbuddy:4140: Waiting for process to become ready
N [9.3.2014 23:33:28] <bot2> Found Demonbuddy: MainWindow (1116100)
N [9.3.2014 23:33:28] <bot2> Demonbuddy:4140: Process is ready
N [9.3.2014 23:33:28] <bot2> Demonbuddy:4140: Waiting for demonbuddy to log into Diablo
N [9.3.2014 23:36:27] <bot2> Demonbuddy:4140: Failed to initialize more than 15 times
N [9.3.2014 23:36:27] <bot2> Standby!
N [9.3.2014 23:36:27] <bot2> Diablo:4388: Kill process
N [9.3.2014 23:36:27] <bot2> Demonbuddy:4140: Closing window
N [9.3.2014 23:36:27] <bot2> Demonbuddy:4140: Waiting to close
N [9.3.2014 23:36:29] <bot2> Demonbuddy:4140: Closed.

Version 25 overnight. The game was closed
 
1. The YAR always create Kickstart file
even if checkbox is empty
please fix this - it may be a root ofthe problem... and i use my own YAR starter file fo each profile

2. N [14.03.2014 9:21:39] <*****> Demonbuddy:9276: is paused to long (90 seconds)
N [14.03.2014 9:21:40] <*****> Restarting...
another problem - the DB working fine, but YAR told its paused and restart it...
 
Last edited:
Im guessing the "Force Enable All Plugins" feature does not work? (Not sure how it happens) But twice now my RYar has restarted demonbuddy with no plugins enabled.. and it keeps restarting that way until I manually enable the plugins again, and close it so it reopens with them enabled...
 
Im guessing the "Force Enable All Plugins" feature does not work? (Not sure how it happens) But twice now my RYar has restarted demonbuddy with no plugins enabled.. and it keeps restarting that way until I manually enable the plugins again, and close it so it reopens with them enabled...

Correct. The latest beta has some new API's I can use to get this working, but, it's completely different from how it "used to" work and requires a redesign of the YAR plugin.
 
New version posted: http://www.thebuddyforum.com/attach...64928-r-yar-rrrixs-yar-fork-r-yar-0.2.2.2.zip


YAR logging based logic is now working again - e.g. Plugins Compiled, disconnected, bot stop and and other error/info message actions. (This means "Force Enable All Plugins" works again :))
YAR can now re-use ISBoxer windows.
Changed default gold inactivity timer to 5 minutes.

Why isnt Torment, Master and such added to the profile difficulty with this version? Its still working half-arsed for me because it resets the bot config for some reason and start profiles on master instead.
 
Why isnt Torment, Master and such added to the profile difficulty with this version? Its still working half-arsed for me because it resets the bot config for some reason and start profiles on master instead.

YAR actually has no control over this anymore. It used to control the difficulty through the Kickstart profile (it's an attribute in the GameParams element in the profile). With 2.0, Demonbuddy has control over the Difficulty (in the bot settings window). The difficulty attribute is ignored in GameParams now.
 
YAR actually has no control over this anymore. It used to control the difficulty through the Kickstart profile (it's an attribute in the GameParams element in the profile). With 2.0, Demonbuddy has control over the Difficulty (in the bot settings window). The difficulty attribute is ignored in GameParams now.

Then how come when i use YAR that the difficulty gets reset to Normal? But without it, the difficulty remains the same as ive set in bot settings
 
2.2.2 version got problem with pinging google ( dont reopen new diablo)

2.3.0 when get checked minimalized at start cant be reshowed, and opened from bar
 
Last edited:
hi rrrix,

I just made a pull request to your github for MonsterPowerLevel fix by using GameDifficulty. Mine is work fine now by have that setting controlled by YAR
 
Back
Top