Anyone find that if one gets disconnected then you have to restart all clients to get that one back in? It works fine until disconnect and then logging in disconnects the other

I believe that happens only when you log the same account twice which the new one will always disconnect the previous client with the same account for obvious reasons. I did not have issue logging account 1 where it would kick out account 2. This thing rly challenges how you can multitask and orient yourself in your accounts and clients lol.

https://eu.battle.net/support/en/article/29676 anyone? It was working fine but now it shows that error all the time

no issues here, rolling 8

It's 100% kicking off a completely different account. My Internet isn't super stable so it only happens when a disconnect and then I got to close all clients and redo the whole battle.net launcher swap thing which gets old quickly. I have a theory that closing battle.net after done entirely helps prevent this.

This post was edited by RussG on May 14 2022 10:52am

No clue man, I am playing 8 accounts at once, no issues.

works great! thanks for the guide

yw

am i blind as fuck or what?

"Find the Event "Sessions\1\BaseNamedObjects\Diablo II Check For Other Instances"

|


looking to kill the process but cant find

This post was edited by Angerflst on May 16 2022 07:07pm

press ctrl + L to view the pane.