Wed Oct 23, 2013 9:33 am by lax
As mentioned over 9000 times in this thread, skipping the launcher works fine...
Inner Space build 5924 fixes this issue with not skipping the launcher, where having the Battle.net Desktop Client installed broke the Diablo 3 launcher. 5924 is the development build as of this post. For anyone not on the development build of Inner Space, to try it out right click IS in the system tray (notification area) and select Patcher, check "Download development (test) patches" and then close and restart Inner Space to let it patch up.
Note: The Battle.net Desktop Client does not currently close when the game is launched. To launch the next client, you should close the Battle.net Desktop Client after clicking the Play button to launch the game, otherwise the already-open Battle.net client may interfere. You may also be able to check the box in the Battle.net Desktop Client settings to allow multiple Battle.net instances, but either way you don't need to leave it open while playing. It goes without saying that skipping the launcher is a faster and more convenient way to launch your clients with ISBoxer.