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

[STANDALONE]DBRelogger

i simulated a crash, but it didnt relog my diablo.

LOG:

Code: 
Relogger Started
Starting Alias bot1
Set Parent Process to 2600
Set Parent Process to 2600
Starting Alias bot2
Forcing region to us.actual.battle.net
Set Parent Process to 5880
Set Parent Process to 5880
Starting Alias bot3
Set Parent Process to 5288
Set Parent Process to 5288
Windows Error Up with id 1928 ChildID 0 ParentID + 5288
 
sabres said:
i simulated a crash, but it didnt relog my diablo.

LOG:

Code: 
Relogger Started
Starting Alias bot1
Set Parent Process to 2600
Set Parent Process to 2600
Starting Alias bot2
Forcing region to us.actual.battle.net
Set Parent Process to 5880
Set Parent Process to 5880
Starting Alias bot3
Set Parent Process to 5288
Set Parent Process to 5288
Windows Error Up with id 1928 ChildID 0 ParentID + 5288
Click to expand...

Happens same to me..
 
dbrelogger crashed on .net framework window

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at DBAutoRelog.BotWatcher..ctor(String path, String dbloc, String d3loc, String bnetu, String bnetp, String dbkey, String dbrout, String dbprofile, String name, String forcecountry, String forcelanguage, Form1 parentfrm)
at DBAutoRelog.Form1.button2_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DBAutoRelog
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/****/Downloads/DBRelogger/DBAutoRelog.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.278 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.282 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Click to expand...
 
more input, try again with brand new db folder .173
don't log me in first at all and next, it was trying to open db, here screenshots...any thought?
using newest relogger v0.5 + your plugin folders also.
i'm assuming that because it did not log in me in first place so therefore when it try to load db, it couldn't read the profile and load routines....
 

Attachments

  • Untitled1.webp
    Untitled1.webp
    56.4 KB · Views: 112
  • Untitled2.webp
    Untitled2.webp
    58.5 KB · Views: 86
Last edited:
andyt315 said:
more input, try again with brand new db folder .173
don't log me in first at all and next, it was trying to open db, here screenshots...any thought?
using newest relogger v0.5 + your plugin folders also.
Click to expand...

Are you sure you have the folder in routines?
help453.webp
 
buddystat work with this relogger also?
for multibot you need multi folder for this?
 
i do not know if u need multi folder, but just in case i have multifolders for everything and working flawless with plugins ofcourse.
 
sabres said:
i simulated a crash, but it didnt relog my diablo.

LOG:

Code: 
Relogger Started
Starting Alias bot1
Set Parent Process to 2600
Set Parent Process to 2600
Starting Alias bot2
Forcing region to us.actual.battle.net
Set Parent Process to 5880
Set Parent Process to 5880
Starting Alias bot3
Set Parent Process to 5288
Set Parent Process to 5288
Windows Error Up with id 1928 ChildID 0 ParentID + 5288
Click to expand...

same what happened here.
 
If you are having trouble pm me your skype so i can help.
 
why demon buddy ask for the routine? im usin irengo plugin...
 
kaime said:
- re-tiling selected diablo clients to a full screen or any resolution set (would be badass, to rescale selected diablo window with 1 click)
- re-tiling all clients after crash (now they just stand fullscreened)
- fully customizable tiling options (resolution, position, key assignment etc.) and make the relogger to remember latest setting, or saving them as .ini or smth
- adding Demonbuddy for the tiling support
- including hardcoded AntiIdle plugin as an optional feature
- killing DB sessions
- "Start All" button with sequentional logins
- Donation button to support this project!
Click to expand...

just bumping my suggestions and adding new ones.
 
Thank you for this great software.
"Force Language" option not working for me, is it implemented yet or yet to be?
That would be a gamechanger cos I'm stuck with some ru accounts and having a hard time to run ru/en clients together atm.
 
You must log in or register to reply here.
Back
Top