How to force exit/close db through plugin?

[zippysticks]

Is there a command that will exit db? I know there's like CommonBot.BotMain.Stop() to stop it, but is there a similar tag that exits demonbuddy?

 

[hti]

try

System.Windows.Application.Current.Shutdown();

 

[zippysticks]

try

System.Windows.Application.Current.Shutdown();

I get the following error:

The calling thread cannot access this object because a different thread owns it.

Anyway to override it and just shutdown the main bot as a whole?


Edit: Nevermind, found it myself with:

Environment.Exit(0);

Anyone see any problems of using Environment.Exit(0); instead of Application.Current.Shutdown();?

 

[hti]

I get the following error:

The calling thread cannot access this object because a different thread owns it.

Anyway to override it and just shutdown the main bot as a whole?


Edit: Nevermind, found it myself with:

Environment.Exit(0);

Anyone see any problems of using Environment.Exit(0); instead of Application.Current.Shutdown();?

No problem, I just forgot this possibility =)

 

[righttang]

No problem, I just forgot this possibility =)

Thanks for that, is there a way to kill the attached diablo process? I mean if multiple DB and multiple Diablo III.exe are running, how do I know which one I should kill?

 

[zippysticks]

Thanks for that, is there a way to kill the attached diablo process? I mean if multiple DB and multiple Diablo III.exe are running, how do I know which one I should kill?

I used Environment.Exit(0); tag to replace your leavegame() tag from your gold inactivity so DB can fully exit instead of just leaving. This way, my relogger can take over because once it detects if diablo or DB isn't running concurrently, it will force kill both if they exist and relogs in for me like as if it was a fresh start.

 

[righttang]

I used Environment.Exit(0); tag to replace your leavegame() tag from your gold inactivity so DB can fully exit instead of just leaving. This way, my relogger can take over because once it detects if diablo or DB isn't running concurrently, it will force kill both if they exist and relogs in for me like as if it was a fresh start.

Will this code work even the notification hasn't been closed?

 

[zippysticks]

Will this code work even the notification hasn't been closed?

What notification?

 

[CodenameG]

try{	foreach (Process proc in Process.GetProcessesByName("Dablo III"))            {                proc.Kill();            }}catch(Exception ex){	MessageBox.Show(ex.Message);}

that outta do it even if it is a little messy.

 

[zippysticks]

try{	foreach (Process proc in Process.GetProcessesByName("Dablo III"))            {                proc.Kill();            }}catch(Exception ex){	MessageBox.Show(ex.Message);}

that outta do it even if it is a little messy.

Would it only kill the diablo that DB is attached too? Or would it kill all process matching "Dablo III" that is running?

 

[CodenameG]

that would kill all running diablo 3's

 

[zippysticks]

Eek, that would be bad for multiple botting =(

 

[sinterlkaas]

Eek, that would be bad for multiple botting =(

you can get current attached diablo in ZetaDia.Memory.Process