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

[STANDALONE]DBRelogger

For me this is the best relogger at the moment. For the first time since patch 1.05 my bots are afkable again. When I woke up this morning I saw that my bot was still running after recovery of 3 crashes. I realized that this moment felt better than jerking off a horse while fucking it in the ass (I have long arms).
 
Not working anymore for me, starting diablo3 at first but crash it before logging in, then it start game again but just wont log in, only showing text "x running smooth"

Relogger Started V 0.8
Starting Alias oma
Forcing region to eu.actual.battle.net
Set Parent Process to 3480
Set Child Process to 3716
Set Parent Process to 3480
A Process Isnt Acting Right Atempting to Fix
Parent Process not responding with id 3480
Parent Process still responding with id 3480
Parent Process still responding with id 3480
Child Process still responding with id 3716
3480 parent to kill?
3716 child to kill?
3716 child alive when parent id is 3480 trying to kill it
3480 parent alive when child id is 3716 trying to kill it
A Process Isnt Acting Right Atempting to Fix
0 parent to kill?
0 child to kill?
Cannot Find BOTH Processes Force Bot to Stop & Restart
Forcing region to eu.actual.battle.net
Set Parent Process to 1260
Set Child Process to 1800
Set Parent Process to 1260
UnHandled Exception when killing Process System.ArgumentException: Saman avaimen sis?lt?v? kohde on jo lis?tty.
kohteessa System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
kohteessa System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
kohteessa System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
kohteessa DBAutoRelog.BotWatcher.reinitbotWindows(String alias)
kohteessa DBAutoRelog.BotWatcher.restartBot(String direc)
kohteessa DBAutoRelog.BotWatcher.botCheckerTick(Object source, ElapsedEventArgs e)
oma running smooth
oma running smooth
oma running smooth
 
Hey, great plugin, its been working really well while playing with 1 bot, however im having trouble getting it to work with 2 bots. I start the first bot with no trouble, but when the second tries to start DB stops working (might be because D3 never actually loads fully, my computer is pretty bad), is there a way to fix this, maybe extend the time for DB to start so D3 gets to load to login screen?
 
Not great for me. Anyhow, after disconnect error message my "bot sits at resume game and doesnt do anything".
DBRelog says it running smooth...
 
Same since i am using giles trinity this is mostly and useless plugin for me as it can't work with it...
 
Is there a relogger that makes sure d3 is logged in and in "resume game" screen before actually opening DB?
 
jubisman said:
Is there a relogger that makes sure d3 is logged in and in "resume game" screen before actually opening DB?
Click to expand...

no, this opens diablo then DB there should be enough time for it to link to your diablo, so you shouldnt need this, besides profiles select specific quests, they dont resume games.
 
How can i run 2 bots with this? I saw the ISBoxer setting, but is there some kind of guide for it on this forum?

Very impressed with this relogger!
 
Hi, Fist program just more than great very help full:)
I's only one think I cant handle witch, the think is when I start diablo manually after that start demonbuddy the "buddystats"

Shows all activity from website or telephone but when I start DemonBuddy Auto Relogger, buddystats show me "No acitive bots founds....."
Any Idea how to resolve problem or what I doing wrong in con-fig?
 
The program starts Diablo and runs Demonbuddy but in the game it can't login into my account... In what could be the problem? (Password does not contain exclamation points (!) )
 
this reloger is nice than the official. if bot stop for unkown reason. the official cant restart bot but this can.
but this reloger restart db and d3 more often. sometimes, all is ok, but reloger just close everything.
thank you for great job.
 
Last edited:
sonnzy said:
this reloger is nice than the official. if bot stop for unkown reason. the official cant restart bot but this can.
but this reloger restart db and d3 more often. sometimes, all is ok, but reloger just close everything.
thank you for great job.
Click to expand...

I have the same problem since today. It restarts after each game. I don't mind because it runs through all the profiles. However it may trigger a flag at Blizzard why I quit D3 instead of leave and restart a game.
 
Is it possible to add a feature like restart the Bot every X minutes would be really helpful for some Stuck Problem?
 
cali1212 said:
Hey, great plugin, its been working really well while playing with 1 bot, however im having trouble getting it to work with 2 bots. I start the first bot with no trouble, but when the second tries to start DB stops working (might be because D3 never actually loads fully, my computer is pretty bad), is there a way to fix this, maybe extend the time for DB to start so D3 gets to load to login screen?
Click to expand...

i'm having the same issue where it works fine with one bot, but when it tries to start the second bot the 2nd instance of DB immediately closes
 
Can't find anything in the Start Post.

Has this Restarter Session Invalid Detection, and also autostart of all bots if I open the relogger with and command syntax, or anything else ?

Thx !
 
Can this relogger run Diablo with the "- launcher" option? So I can run multiple bots?
 
Been using for a couple of days now, runs perfectly! Thanks for this great program!!
 
Buddystats doesn't work with this program though :/

Been testing it:

- Start diablo and db manually -> buddystats works fine
- Start diablo and db with DBRelogger program -> no bots found @ buddystats :/

Any others with the same problem?
 
You must log in or register to reply here.
Back
Top