[StandAlone] Yet Another Relogger!

Atom does not log you out though correct? I want to be able to do a total restart of everything. And last time I tried to enable the "break" feature on Atom it didn't do anything.

 

It stops the bot, and idle in Act Selection Menu, this is working as intented, and YAR handles it, to do a total restart, configure the scheduler in yar.

 

Any issues with Windows 8?

 

Correct which is why I asked if there would be an update to enhance the scheduler to be more specific instead of having to logout for a full hour. Atom does not do what I need it to do.

 

Not at all, at least not for me, i run YAR as admin.

 

I'm having trouble with the region set since 0.1.8.3 and bots in different regions. It appears to launch Diablo 3 too fast and cause the region of the previous process to change as well before it can login.
Here's an example: Bot 1 is US and Bot 2 is EU.
Bot 1 fires up, open Diablo 3, opens DB. Right before bot 1 can login, Bot 2 is started and region is set to EU. Bot 1 logs in but since region changed, it's logging in EU instead of US.

I bot on both US and EU with same accounts and I can't start them all because they will try to logging on the same account/region.

Hopefully this can be fixed soon. Thanks for your awesome work.

 

Does this work with a *** or wmware?

 

You are the first here to say your comp goes faster than the relogger. xD

Yes bro, GO ON, there's even a feature to check ***s state!

 

Is anyone experiencing high CPU usage with the latest YAR?

YAR 0.1.8.5 seems to be giving a lot of CPU usage in one of my bot clients.

I reverted back to YAR 0.0.0.6 and it solved the high CPU usage issue. Can you please take a look at this? Not sure why it's giving one client more priority causing it to have higher CPU load.

 

For those of use using YAR in conjunction with Apoc's D3Starter to launch multiple instances of D3 using one common installation, it would be nice if when shutting down the bot and D3 client (by issuing a stop, or via scheduled stop) that the relogger would quit the D3Starter process as well. As it is now, if you go to task manager there are multiple instances of the D3Starter process (one each for the number of times a bot was launched from the relogger) which requires one to manually kill from the task manager.

 

Is there any way to keep monster power lvl when after a crash or scheduled break. I am running with MP on, after a restart the relogger seems to reset MP to 0. Any1 else noticed this?

 

This only happens when DB doesn't have the chance to write its save file (ie. when it crashes). If you just make your settings for DB, then close it, it will save and then your MP will always stay

 

when i sleep and wake up i find that my yar says "stopped" for 2 diablos or 1 and i have to press "start" again to get it going, anyone know whats going on? i'm using 1.7.7

 

why allways being an error:initializing error for 3 times，when I am botting？

how to avoid this？

thank you

 

what happened is the same with harleystcool,how to slove it,plz.

 

Thanks man

 

Could you both provide logs cause I can not guess what went wrong

 

The break function of RadsAtom isn't working for me. When YAR recognized that nothing happens for a period of time, it closes D3 and DB and start again. Do I have to use Atom for it?

 

Thanks for reporting this issue! There already is a fixed version on Github it will wait on demonbuddy to be logged in within 180 seconds if this fails try again for 3 times .. after that close everything down and move on to the next bot to start
download the source and build it
https://github.com/sinterlkaas/YetAnotherRelogger/

 

I will add support for radsatom when I get back home again need to visit my shrink so will be back later