For me, now it no longer works aside from the initial login. After the second instance starts up (regardless of using authenticator), my other instances sit at Connecting... forever. After seeing this I tried, to login via the launcher and I'm now getting little puzzle verifications so it seems that Blizzard is blocking the direct connections for me.



This post was edited by Bucknasty1618 on Aug 5 2022 06:45pm

This does seem to go away after a while

This post was edited by Bucknasty1618 on Aug 5 2022 06:46pm

Not sure if the frequent logins due to me making a more automated script caused this to happen

Do you update the settings json file? I'm wondering if that might have anything to do with it.

Ok I see, yeah this is a shortcut and the D2R process cannot handle that additional two factor authentication apparently when launched directly. Assuming this is more for mules/alts, setting up a strong password and disable MFA will do.

i found that via direct mode(1) you cant join game via friend list, is that the same in your case?

It works for me over friend list, right click and join on those accounts which I started directly.

ah, i just re-tested this, you are right, it first appears like they are offline, but takes like 20 seconds for them to become online status, thanks a lot!

This post was edited by LolKok on Aug 10 2022 07:29am

After researching on this topic, I wrote this utility that you might be interesting in loading multiple clients (remove space in the quote to get a valid url):



Please note this only works WITHOUT launcher.

There is a bit problem with that approach when you start all of them at once before finishing battle net connection inside a client. They will take the web token from the registry (previous account start and it's a mess xd).