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

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[StandAlone] Yet Another Relogger!

Status
Not open for further replies.
Argh still can't start DB with other winuser (admin account). The requested operation requires elevation sh*t again......
Diablo starts fine.
 
sinterlkaas said:
It will detect basic idle situations like:
  • no plugin pulse for x seconds (this is what drelog does)
  • no game for x seconds
and some other things that still need some tweaking..
for now it will only try to Stop and Start Demonbuddy (yes I know this is not the best solution but this is 1 of the reasons why it is still in beta) :)

And for the question about crash detection: Yes it does support crash detection!
Click to expand...

Great job. It works fine. But I have a problem, may be a bug?. The bot is running with no mistake, but sometimes the unresponsive time exceed 60 seconds, and then the game have to restart. I have used your "antiIdle" plugins and I set the frozen time to 300 seconds could solve this problem. Hope we could set this idle number in your next version.

[2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Is unresponsive for more than 60 seconds
[2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Killing process
[2012/12/10 2:38:44] <Dwight Chandler> Diablo:1584: Process is not running
[2012/12/10 2:38:44] <Dwight Chandler> Demonbuddy:3624: Closing db
[2012/12/10 2:38:44] <Dwight Chandler> Demonbuddy:3624: Waiting to close
[2012/12/10 2:38:47] <Dwight Chandler> Demonbuddy:3624: Closed.
 
Last edited:
Failed to load profile: Element Continue is not supported. Please check your XML and try again. (<Continue profile="02_Core.xml" />) Line 12 While trying to run Alkaizer Run 2.99.1 RC or .2 ... any help ?
 
L4s3c7k4 said:
Failed to load profile: Element Continue is not supported. Please check your XML and try again. (<Continue profile="02_Core.xml" />) Line 12 While trying to run Alkaizer Run 2.99.1 RC or .2 ... any help ?
Click to expand...
i have no idea what profile is that but I'm pretty sure its a plugin/DB problem check that you have the plugin required for that profile
 
tesslerc said:
sinkerlaas can you make it randomize the seconds when it closes D3 and DB?
it closes always on 00 seconds.
Launch has a delay for DB and has a delay until logged in so that is ok.

Also if it fails for 3 times in a row it just stops, so if internet is down for 1 hour and you aren't home for 12h - it won't auto start again.
I would set a delay for 1h until retrying again - that way it shouldn't hog the server incase of downtime.
Click to expand...

I've already suggested the throttled relogger tess, he's working on it.

As for the the randomize close db....It doesn't matter on the SECONDS. Yar doesn't simply logout...it kills the said D3 process. Meaning depending on your internet connection, and blizzards, you'll log out at a random timestamp anyway. Not to mention, not everyone's pc time is 100% synced with what their servers are either. So what is 1:29 for you, might end up being 1:28:32 for them.

So, while yar has the command to close on exactly say 1:30, realistically what blizzard sees is going to random anyway.
 
Last edited:
Is there a difference between MP0 and Disabled in the profile management screen?
 
rbrinks said:
new update works like D3Loader? Changing the Unique ID of diablo each windows user?
Click to expand...
It is not exact the same I did not add any linking for D3 stuff I will later

L4s3c7k4 said:
Failed to load profile: Element Continue is not supported. Please check your XML and try again. (<Continue profile="02_Core.xml" />) Line 12 While trying to run Alkaizer Run 2.99.1 RC or .2 ... any help ?
Click to expand...
This is a DB issue when using -autostart for db launch arguments .. try enabling Kickstart this should fix the problem

Geckoz said:
Is there a difference between MP0 and Disabled in the profile management screen?
Click to expand...
the difference between MP0 and disabled is that MP0 will set the MP to Level 0 and disabled simply does nothing about MP and will use DB default settings
 
So I guess that means you can have Monster Power off in the in-game options, and YAR can enable it for you. Thats nice!
 
sinterlkaas said:
It is not exact the same I did not add any linking for D3 stuff I will later


This is a DB issue when using -autostart for db launch arguments .. try enabling Kickstart this should fix the problem


the difference between MP0 and disabled is that MP0 will set the MP to Level 0 and disabled simply does nothing about MP and will use DB default settings
Click to expand...

Any ETA on Session Killer fix?
 
Sinterlklaas, I tried your user account option and it's working straight away. Is the purpose of it to get different registry IDs on the different sessions?

Is it possible to use my *** with it somehow, or does it not actually log into the new user account?
 
I have a set of a3 profiles set to mp 0, yet it says "[18:15:05.315 N] [YetAnotherRelogger] Recieved MonsterPowerLevel: 1"

I do have a1 and a2 set to mp 1 though. Anyone having this problem?
 
Im having an issue where it doesnt actually pick between the different profiles Ive set up. Just keeps doing act1..
 
Windows user selection works great...However, it doesn't recognize D3prefs files...It runs all bots on defaults settings and can't make it run with higher MipBias...any way to fix it?
also, once we set some key shortcuts, when we close and program again, they doesn't work.I have to edit them, click save and then they work...until i close the program and run again.
 
Hi there!

I just installed YAR and so far i'm impressed :)

Is there any way to disable the auto-focus the DB when the D3 is in focus?

Code: 
[10-12-2012 02:03:36] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
[10-12-2012 02:03:39] <Bot 1> Failed to bring Demonbuddy to fron
[10-12-2012 02:03:42] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
[10-12-2012 02:05:02] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
[10-12-2012 02:05:05] <Bot 1> Failed to bring Demonbuddy to fron
[10-12-2012 02:05:56] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
[10-12-2012 02:05:59] <Bot 1> Failed to bring Demonbuddy to fron
[10-12-2012 02:11:26] <Bot 1> Diablo:10080: has focus. Bring attached Demonbuddy to front
[10-12-2012 02:11:29] <Bot 1> Failed to bring Demonbuddy to fron
 
Last edited:
Status
Not open for further replies.
Back
Top