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

Plugin req. Quitting d3 when DB crash

H

hetsig

New Member
Joined
Jul 20, 2012
Messages
509
Reaction score
0
Im botting on HC and the only time I die is when DB stops working or crash, which sadly happens way to often. Is it possible to make a plugin that quits d3 when DB stops working or crash? If someone can make this happen I can give a donation. Im so tired of all these HC deaths :/
 
Since DB loads the plugins, if DB crashes, the plugins will cease execution as well... so making a plugin to fix this problem isn't an appropriate solution. You're probably looking for a standalone application. All you will need to do is monitor the D3 and DB processes at a specified interval to make sure they are still running, and if not - terminate Diablo 3.

Do you have any input as to why you think DB may be crashing in the first place?
 
^Beat me to it.

not possible to make a plugin for DB to close D3 when it crashes. You would have to create an external program that moniters the processes and closes D3 when DB crashes.
 
applepiez said:
^Beat me to it.

not possible to make a plugin for DB to close D3 when it crashes. You would have to create an external program that moniters the processes and closes D3 when DB crashes.
Click to expand...

What I would probably do is create a plugin that spawns a separate process and keeps communication via a named pipe or something.. waiting on "pings" to make sure DB is alive and working, and if a timeout is reached or the pipeclient is disconnected, it force closes D3/DB if still running.

DB Started -> Plugin Loaded -> Spawns new process -> Connects to pipe -> Sends PING every X seconds as DB is running

Alternatively one could do this with just a simple threaded while loop checking if a process is running though.
 
Last edited:
cZk said:
What I would probably do is create a plugin that spawns a separate process and keeps communication via a named pipe or something.. waiting on "pings" to make sure DB is alive and working, and if a timeout is reached or the pipeclient is disconnected, it force closes D3/DB if still running.

DB Started -> Plugin Loaded -> Spawns new process -> Connects to pipe -> Sends PING every X seconds as DB is running

Alternatively one could do this with just a simple threaded while loop checking if a process is running though.
Click to expand...

So is this something you could help me out with? I'd ofc give a donation for time you'd have to put in.

I cant sleep at night now, always worrying about another DB crash :P
 
hetsig said:
So is this something you could help me out with? I'd ofc give a donation for time you'd have to put in.

I cant sleep at night now, always worrying about another DB crash :P
Click to expand...

Sure, I'll whip something up tonight.
 
You could try using AntiIdle with
http://www.thebuddyforum.com/demonbuddy-forum/plugins/60274-standalone-dbrelogger.html
or
http://www.thebuddyforum.com/demonb...n-command-line-based-anti-crash-relogger.html


cZk said:
What I would probably do is create a plugin that spawns a separate process and keeps communication via a named pipe or something.. waiting on "pings" to make sure DB is alive and working, and if a timeout is reached or the pipeclient is disconnected, it force closes D3/DB if still running.

DB Started -> Plugin Loaded -> Spawns new process -> Connects to pipe -> Sends PING every X seconds as DB is running

Alternatively one could do this with just a simple threaded while loop checking if a process is running though.
Click to expand...

I am currently working on something like this for AntiIdle...
It will check if pipeline server is running if not will start it and communicate with it just by sending pid info about DB and the attached D3 and close one of them when DB freezes
 
You must log in or register to reply here.
Back
Top