[Problem] Launch multipile DB bots

[itraxx]

[Problem] Launch multipile DB bots. Devs please read.

UPDATE2:
So after trying many different things I furged out that DB #298 works with isboxer IF you start your chars step by step. That means you start your first char via ISBOXER, log into the game and join a game. Afterwards you start DB and it attaches automatically to the window. You have to repeat this step until you launched all your chars. This is obviously a very complicated way to launch your setup and I would like to ask the devs to look into it. As I mentioned before version #287 handeled everything without issues.

-------------------------------------
UPDATE1:
I found the #287 DB version on my computer which I used 4 months ago. I gave it a try and the process selcetion works without any problems. Can one of the Devs please look into the changes which were made since #287? Would it be possible to reroll to the #287 selection process for future DB versions? Becuase at the moment the bot is pretty much useless for ISBOXER users.

-------------------------------------
Hi,
I have problems to run DB with ISBOXER. Actually I was able to run it 5 months ago but I stopped botting and now try to get back into business. Here are the steps which I did so far:

- Complete and fresh install of Win 7 64bit
- Extracted #298 into 3 different folders
- Installed isboxer and created a 3 toon setup
- I run DB, D3 and isboxer as Admin
- I have a 3 session key

After firing up 3 instances of D3 via isboxer I try to login with DB. The first login works without any issues. When I try to login the 2nd account I get the following error message:

Was not able to attach to any running Diablo III process, are you running the bot already? and the PID selection window doesn't show up.



Again, I am starting the 2nd DB client from a different folder and I have no clue what I am doing wrong. Actually I can't remeber if I did anything different 5 months ago but I guess not.


Many thanks for your help!

itraxx

 

[Tony]

try without isboxer

copy ur diablo3 folder to somewhere else, change its name , go to ur diablo3 copied folder and go to diablo III.exe, right click and make shortcut, now go to shortcut and right click on it, go to properties and where u have like "D:\lolz\diablo3,exe" -launch (add: -launch at the and) and now u can run multiple diablo3 instances

 

[itraxx]

Thanks Tony, but to run DB without isboxer is not an option for me. Is anyone around and happy to help who runs DB with isboxer? Any help would be much apprecited!

 

[d0rian]

Hey guys. I am interested how to run DB without isboxer. I am planing to get a second bot very soon..and i am really interested in this topic. Have no problems starting 2 or more D3s.
itraxx why runing DB without isboxer is not an option for you ? Is there actually a way to run it without isboxer. As far as i know this program is not free.

 

[Job2k9]

This happens to me a lot and its only after the previous D3 window was flashed and either not enough time went by or I didn't actually activate that D3 window. For some reason if I bring the flashed D3 window to the foreground then the next DB will find the other copies of D3 just fine.

If you want to run multiple DB's without having to shag around with the different keys you can put the key in a shortcut to db like this

"C:\directory\Demonbuddy.exe" -key yourkeyhere

You can even use -pid yourpidhere if you can figure out the pid of the D3 window so it'll automatically attach. This works great with macros and whatnot, you can launch all your d3 and db and attach with no hassle, if you aren't a fan of the reloggers available here.

 

[d0rian]

Thanks a lot Job2k9...as soon as i get the new DB key...will do as you say.

 

[JoshYoJoshYo]

This happens to me a lot and its only after the previous D3 window was flashed and either not enough time went by or I didn't actually activate that D3 window. For some reason if I bring the flashed D3 window to the foreground then the next DB will find the other copies of D3 just fine.

If you want to run multiple DB's without having to shag around with the different keys you can put the key in a shortcut to db like this

"C:\directory\Demonbuddy.exe" -key yourkeyhere

You can even use -pid yourpidhere if you can figure out the pid of the D3 window so it'll automatically attach. This works great with macros and whatnot, you can launch all your d3 and db and attach with no hassle, if you aren't a fan of the reloggers available here.

There a guide for any of that? Thanks!

 

[Job2k9]

There a guide for any of that? Thanks!

Guide for figuring out the PID? Well I used autohotkey to make a macro to manage everything and that program has commands to figure out the PID of windows. I'm sure there are other ways but other than the macro I'm unfamiliar.

My ahk code for that is:

WinGet, D3PID, PID, Diablo III
Run "C:\directory\Demonbuddies\db.lnk" -key mykey -pid %D3PID%

Getting into ahk may be a bit of work. You could probably look at using YetAnotherRelogger. It seems pretty popular here.

 

[itraxx]

This happens to me a lot and its only after the previous D3 window was flashed and either not enough time went by or I didn't actually activate that D3 window. For some reason if I bring the flashed D3 window to the foreground then the next DB will find the other copies of D3 just fine.

If you want to run multiple DB's without having to shag around with the different keys you can put the key in a shortcut to db like this

"C:\directory\Demonbuddy.exe" -key yourkeyhere

You can even use -pid yourpidhere if you can figure out the pid of the D3 window so it'll automatically attach. This works great with macros and whatnot, you can launch all your d3 and db and attach with no hassle, if you aren't a fan of the reloggers available here.

Was hoping that this could solve my problem but even if I bring the flash wind to the front the next DB does not find the other windows. The strange thing is that I never had any issues with DB and isboxer and 5 months ago everything was working fine. What has changed since then? Looks like the PID selection process has somehow changed in the new DB version:

I guess here are many ISBOXER + DB users and I am still hoping that someone can help me...

 

[Job2k9]

The PID detection is very shitty I agree. Something changed in DB because it was fine for the longest time then went to shit and I'd have to jump through hoops to get DB to detect D3 until I made the macro find the PID itself.

 

[itraxx]

The PID detection is very shitty I agree. Something changed in DB because it was fine for the longest time then went to shit and I'd have to jump through hoops to get DB to detect D3 until I made the macro find the PID itself.

What a disaster. So they changed the pid selection process recently? That means that DB is not usable with ISBOXER anymore? Or does someone know a workaround?


@ Devs: Can you please reply to this topic and tell us what has changed? PLEASE fix the selection process and make it work with ISBOXER again. I am even happy to provide yyou my isboxer acc details to test it if you guys don't have a license.

 

[d0rian]

Here is a fast way to find out the PID. Open Task Manager and choose View/Select Columns and put a check in PID(Process Identifier). After you do that you should be able to see all your processes PID's in the Processes tab.
This is in XP...7 should be something near to that.

 

[itraxx]

Here is a fast way to find out the PID. Open Task Manager and choose View/Select Columns and put a check in PID(Process Identifier). After you do that you should be able to see all your processes PID's in the Processes tab.
This is in XP...7 should be something near to that.

Even if I add the pid as a parameter I still get the same error:

Was not able to attach to any running Diablo III process, are you running the bot already?

I don't know what to do anymore. Is there anyone around who runs DB+ISBOXER an help me with that?

 

[itraxx]

I found the #287 DB version on my computer which I used 4 months ago. I gave it a try and the process selcetion works without any problems. Can one of the Devs please look into the changes which were made since #287? Would it be possible to reroll to the #287 selection process for future DB versions? Becuase at the moment the bot is pretty much useless for ISBOXER users.

Thanks

 

[itraxx]

UPDATE2:
So after trying many different things I furged out that DB #298 works with isboxer IF you start your chars step by step. That means you start your first char via ISBOXER, log into the game and join a game. Afterwards you start DB and it attaches automatically to the window. You have to repeat this step until you launched all your chars. This is obviously a very complicated way to launch your setup and I would like to ask the devs to look into it. As I mentioned before version #287 handeled everything without issues.

 

[GordonGekko]

Exactly the same prolem here. Would be great if on of the Devs could look into it.

 

[Tony]

for those with problems,use support issues section

closed