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

Extract & Play DemonBuddy - v220 + DRelog & Giles Suite

There might be something wrong with the profile text i zipped up, will edit it in a bit and post when I have updated it. Also you guys are sure you're running it as admin yeah?

alternatively try deleting the profiles.xml in c:\drelog\ and run drelog.exe as admin again and see if that works
 
Just discovered that Drelog cannot handle/restart "Invalid Session" errors from Demonbuddy.exe :(

Any solution?
 
Mine just crashed, got to d3 hit the max sessions thing (due to me maxing out my 6 keys) but then it attempted to login (db did) a couple more times > and logged in then went to login to the game. The previous times it his the max sessions problem for too long, it closes the DB and D3 sessions and retries again.

I am not quite sure what you're doing or what you've done but its definitely not acting the right way.
 
Bazingaw said:
Mine just crashed, got to d3 hit the max sessions thing (due to me maxing out my 6 keys) but then it attempted to login (db did) a couple more times > and logged in then went to login to the game. The previous times it his the max sessions problem for too long, it closes the DB and D3 sessions and retries again.

I am not quite sure what you're doing or what you've done but its definitely not acting the right way.
Click to expand...

Pretty sure it's the same copy of DRelog that I downloaded from this thread.
Invalid session doesn't crash my Diablo3.exe or Demonbuddy.exe, it just stops the Demonbuddy.exe literally ("STOP" button changed to "START" button).
If something bad happens to Demonbuddy.exe, DRelog won't be able to detect the "stopped state" and thus won't force shut Diablo3.exe and Demonbuddy.exe and proceed with a restart.
 
Last edited:
Bazingaw said:
alternatively try deleting the profiles.xml in c:\drelog\ and run drelog.exe as admin again and see if that works
Click to expand...

After i did this it loaded right up. Do i need that profiles file?
 
@Mephuser:

Kay I wanted to confirm this before replying to you.

Ran 7 bots last night - Multiple were logged out sometime overnight due to auth issues. Below is log of 1 bot client running into this issue
Code: 
[18:52:26.241 N] Session is invalid!
[18:52:26.251 N] Bot Thread Ended. Was this requested?
[18:52:26.571 N] Logging in...
[18:52:28.154 N] Was not able to attach to any running Diablo III process, are you running the bot already?
[18:53:42.915 D] Cannot stop a bot when it is not running.
[18:53:42.915 N] Session is invalid!

Below is the log for the bot starting back up 20mins~ after
Code: 
[19:11:52.476 N] Demonbuddy v1.0.994.250 started
[19:11:52.536 N] Logging in...
[19:12:16.033 N] Attached to Diablo III with pid: 6056

This is drelog's log from the bottom window when it runs
Code: 
[1:31:52 AM] Bot#1: Rescheduling
[1:31:53 AM] Bot#1 Starting (Crash Recovery)
[1:32:35 AM] Bot#1 logged in
[1:52:26 AM] Bot#: Rescheduling
[1:52:27 AM] Bot#2 Starting (Crash Recovery)
[1:53:53 AM] Bot#2 logged in
[2:29:19 AM] Bot#3: Rescheduling
[2:29:20 AM] Bot#3 Starting (Crash Recovery)
[2:30:24 AM] Bot#3 logged in
[4:04:25 AM] Bot#4 logged out
[4:04:34 AM] Bot#4: Rescheduling
[4:04:35 AM] Bot#4 Starting (Crash Recovery)
[4:05:40 AM] Bot#4 logged in
[5:11:21 AM] Bot#5 logged out
[5:11:30 AM] Bot#5: Rescheduling
[5:11:31 AM] Bot#5 Starting (Crash Recovery)
[5:12:35 AM] Bot#5 logged in
[5:32:13 AM] Bot#4: Rescheduling
[5:32:14 AM] Bot#4 Starting (Crash Recovery)
[5:33:16 AM] Bot#4 logged in
Edited names to remove any traces to my chars. Look at the 5:11am tag, it reflects the log in which after 20+~ mins it detected that there was no bot logged in and had it resetup

edit: This is further logs from Drelog's generated log file showing Drelog's processes scanning for any D3 clients and realizing the PID for the above bot is not active anymore:
Code: 
[10/2/2012 5:11:27 AM]System.ArgumentException: Process with an Id of 6420 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at DRelog.DMagic.ProcessCrashes()


[10/2/2012 5:11:29 AM]System.ArgumentException: Process with an Id of 6420 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at DRelog.DMagic.KillProfile(Profile profile, String reason)

So yes Meph, it works. The setup I provided works, It doesn't magically break DRelog's ability to resched. I dont know but I feel like this is as good a place to say this to you since I visit the forums a lot. You need to think before you post and maybe not even post at all. Half your posts are sensationalists bullcrap that is unfounded and wrong, and the other is you working on half a braincell doing something and telling only half the picture.

GIVE ME LOGS AND SHIT SO I CAN HELP. A vague statement does nothing, doing what I did and testing and providing any logs does. Because as you can see from my testing it does work.

@Afaljar: Once you delete it and recreate the profiles through Drelog.exe (Make sure to run as admin) it should recreate the profiles.xml file. If it doesn't please let me know I will try and get a blank profile xml that works out to you guys.
 
Last edited:
After 3 hours of trying reloggers i actually made one work!

Is it possible to change those 20minutes of detection before resetup?
 
I've been using this for weeks now and absolutely love it. Can anyone get the scheduler to work? Or a way to make it work with other break takers?
 
Does it work correctly with buddyauth? Doesn't seem to do it with me, though I have entered the correct info (it passes the "test connection" too), but it always says something like "can't identify the session, will probably catch max sessions." and it does.
 
It loads Diablo 3 perfectly fine but it gets stuck on "Demonbuddy_Startup." I know I have everything set up correctly. DB is located in C:\DRelog\DemonbuddyBases\39. I'm using the beta build 39 of DB if that makes any difference (don't think it should, same program name).
 
placebro said:
It loads Diablo 3 perfectly fine but it gets stuck on "Demonbuddy_Startup." I know I have everything set up correctly. DB is located in C:\DRelog\DemonbuddyBases\39. I'm using the beta build 39 of DB if that makes any difference (don't think it should, same program name).
Click to expand...

set to run as admin? I have had no issue with it loading. If it hangs up there try running the bot manually and see if u get the fast_dll error might be .net and c++distro issues.
 
fr3357 said:
set to run as admin? I have had no issue with it loading. If it hangs up there try running the bot manually and see if u get the fast_dll error might be .net and c++distro issues.
Click to expand...

My PC only has one account which is the one I'm using, which is admin already. DB starts up fine when I load it manually but DRelog can't seem to load it for some reason... it just hangs there.
 
works like a charm... I need some info on how the scheduler works. Is there a thread somewhere that I could read with good info on the topic? I did a search for DRelog but this thing must be pretty old cuz I am not finding the info I am looking for.

For instance I want it to run 3 different profiles. Act 1 Act 2 and Act 3. Is it possible to make this relogger do that?
 
Last edited:
Having a bit of a problem, Everytime I go to run it, it says " no profile selected " when I look at my profiles, the same profiles are in the Drelog\Profiles as my "beta 42" profiles folder. This is second clean install by the way.. any help ?
 
@Llamahump2k3
Profile files you need to put into this folder : \drelog\Demonbuddys\<name of session>
 
so how do I make it save the settings for giles trinity and each individual chr?
 
You must log in or register to reply here.
Back
Top