worked for me for a day. now the play button not activating after i kill the process. restarted pc. restarted bnet.

managed to get it work again. by closing exiting the first bnet app. play button now available when you launch the 2nd game.

right, but keep in mind (as ppl have called out in this thread), v-machine setups are probably safer as with this method, youre directly altering game files which is against ToS. use at your own risk

trying it with processexplorer and processhacker - nothing works

cant find this shit **\Sessions\1\BaseNamedObjects\DiabloII Check For Other Instances** any tips?

did everything as he said

What? If you are "altering" a file, you're doing something other than what's outlined in this method. You're just closing a running process on your computer. Additionally, this exe or individual handles of it tends to crash on its own a lot anyway.



Go to view and turn on the lower pane, select D2R.exe and at the bottom look for the event you listed.

someone else pointed this out: the "d2 check for other instances" handle is part of warden, if you kill a process that warden explicitly runs, you are ALTERING game behavior which, ToS language is general for this reason, violates Blizz ToS. like i said, use at your own risk

blizz wont give a fk i guess

Pog if True/Works.

Nvm got it all working now…

Where did you get this information? According to the platform (battle.net client) TOS, warden runs on the battle.net client, and only "while the platform is running", at least that's their justification for installing spyware on our systems, although they don't specify if something might be left behind running as part of warden when the client is closed. I often notice processes related to b.net like b.net updater running after I've closed the client. Your articulation in this kind of discussion is refreshing and pleasant, but my interpretation of "game behavior" is something the game is doing or not doing in terms of gameplay. I.E. an example of altering game behavior would be something like the old farcast mod that let people cast melee attacks at infinite range, or modifying various speed frames, or TPPK, or displaying a part of the map the player hasn't explored, and various other exploits players have used in the past. It doesn't seem that closing a process would reasonably qualify as altering game behavior, in my view.

Additionally, the d2r exe in its entirety or in part is more than capable of crashing on its own, and it does. It seems unlikely that Blizzard would seek punishment for this, or even have a reliable way to distinguish between intentional close by the player and a failure to respond. The best they can do in this regard is log the last things the game was doing leading up to the crash / failure to respond / closure of the process.

This post was edited by MP5_THuG on Oct 19 2021 09:19pm