-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with the Asia server #28
Comments
Thanks for reporting. Yes it's an issue at Blizzards end that I can't control unfortunately. In the meantime I recommend launching all but one of your accounts on another region. Use battlenet to launch the last instance on Asia (KR), Use the instance launched via bnet to make Asia games, then use friend joining to join KR games. Keep this issue open until auth issues are resolved as others will also likely come here looking for info, cheers! |
Great news everyone! There will be an additional config option to choose between using traditional username and PW to authenticate via parameters or to alternatively authenticate via a Token (essentially what happens when you open the game from the battlenet client). It will be a few days for me to build, test, test, test again and release. |
Resolved in new release. Setup steps must be performed, see release notes and setup instructions on readme. |
Hi shupershuff. Thank you for supporting us, D2R lovers. Cannot login to Asia/Korea server via Shortcut (bypass Battle net App) after October 6th 2023 |
Love the script! One question how can you force it to use token when you have it going through parameters? I know you mentioned it but i can't find how to do in the info screen unless im blind. Had an issue this morning trying to log into asia and kept giving me error for dcloen |
Thanks for the feedback! |
Hi, first of all - great script. Helps so much with multiple instances.
The problem:
Connecting to the Asia server doesn't work. After the game starts, it tries to connect to battle.net and it says "cannot connect to server". If run from the official Battle.net app it works fine. Some people on various Discord groups mentioned that other similar scripts don't work either so it's likely something on Blizzard's end. Not sure if anything can be done from the script itself but reporting just in case.
The text was updated successfully, but these errors were encountered: