I have tried everything I know.
it disconnects the bots faster than I can put them up with it.
no idea how to fix it.
Ok, I'll try to give you some advice , things that worked for me. No warranty though, its a pity yar author seems to be too busy lately to update the relogger. Once you get it working properly, you'll be glad you did, I would PAY for a working and actively maintained relogger just like I do for Db.
It must not be an easy task though, as the game has been out for a while now and no reloggin utility has been developed by the db staff!
1) As someone previously stated, TWEAK your settings. Look for a working solution. Try with less than all the bots at once, even if I guess you'll be inclined to keep all working while you tweak it.
2) Don't use both gold timers; either yar or trinity one. Best setup for me is trinity inactivity timer at 5 and yar gold time at 6 minutes. this way, if your bot gets stuck but is not inactive (just like going back and forth between 2 positions) gold timer will trip you out and in. Having both gold timers on proved troublesome for me on the past.
3) Enable autoposition and do not modify its default settings. Works better imho.
4) Try to modify d3prefs as little as you posibly can. You dont have to work at 40% cpu with your 15+ bots , 80 percent is just fine!
5) Try diferent versions. Of both yar and demonbuddy. Remember you have the experimental version at your disposal. For me , 1.9.2 yar ,#295 DB and .14 trinity is giving best results. I wouldn't recommend last db beta and .16 trinity yet,because I haven't tested them long enough myself.
6) Use apoc d3starter. If you get the gray screen problem , download the last version from plugins here in Db site and overwrite it.
7) yar will create a new plugin in your plugins folder called yar. Copy it and create a new folder called plugins INSIDE the yar folder too. It should be like this : Demonbddy/yar/plugins/yar/plugin.cs. Do
not remove the yar folder from demonbuddy plugins.
8) Some profiles work better than others with yar. The ones you should be using are those whose authors actually check the profile is working with yar and create relogging files. Afaik rixx, tin and gnome do this. Use them....they'll work better.EDIT: Take your time to check their threads on how to use them with reloggers!!!
9)I've found not using YAR kickstart lead to less crashes for me.
10) Yar is a plugin, you know what it means.....it will probably break with every other important Db , trinity or d3 update. So, do not inmediatly change to every new db beta and trinity as fast as they show up. Check the relogger is working properly with them first!
11) Allow for some more time on everything.; double the time yar takes to start a game, double the time yar takes to kick out diablo when starting, and so on.
12) You'll need TIME to get it working. It took me more than 1 month to get it working properly. Right now, is not having more than 2-3 crashes a day, and most of them are connection related. Running 8+ bots.
I hope you'll find some info here useful. These are my personal settings and It finally works the way it should.Just don't expect for it to be working 100% flawless since the start. It WILL REQUIRE tweaking. But I can assure you, once you get it working, you'll never be able to run your bots without a relogger...
13) Tony mode on: if it keeps not working:
Uninstall and reinstall net framework 4.0 and c++ redis. If your system is 64 bits, download both x86 and x64 versions of c++ redis.
Do a clean install of db, Trinity, yar and other plugins if you feel like.
Repair d3 files....there's a repair utility in the launcher.
14) It kept me having problems when using it with radsatom. Haven't tried Atom though. I wouldn't recommend it.
15) Be completely aware YAR could increase your chances of being detected and banned as it automatices (spelling?) a lot of stuff. In other words, don't use it if you are not willing to take the risk.
Good luck!