Before, by running /Applications/World of Warcraft/World of Warcraft Launcher on MacOS a second Battle.net client would load (with the option set to allow multiple instances in its settings, which it still is)
Now, running /Applications/World of Warcraft/World of Warcraft Launcher hangs on attempting to update Battle.net - which is never finishes and shows an error screen for the BLZBNTBTS0000005C error, which takes me to:
- Already reinstalled bnet from scratch using the help articles
Secondly, attempting to log in on an account directly after launching the client, for example, /Applications/World of Warcraft/_classic_/World of Warcraft Classic will show the login screen in-game, but after entering all details including the authenticator code, it immediately disconnects. Same behavior for an account without the authenticator attached.
The only way to open two clients from different accounts at the moment is to:
- Log on battle.net with account1
- Open the client and keep it open
- Logout of battle.net on account1
- Log on battle.net with account2
- Open the second client
Which is a massive hassle and demands many battle.net logins across the day, instead of just having both battle.net apps running side by side like before.
Update: this might’ve started happening with the MOP beta, and reinstalling bnet somehow made me reinstall all of the MOP beta while no changes were made to the Data folder (and all other clients like Classic/Era required no installation), could be some protection added for the Beta?
UPDATE (unable to reply since no comments)
I’ve managed to run multiple battle.net clients on MacOS by simply duplicating the Battle.net app in the Applications folder