Closed subaridji closed 1 year ago
figured out: apparently after some failed login attempts battle.net enables captcha protection for autherization.
in this case autherization within command line arguments stops working at all. the only way to login remains only through passing captcha and launching game from bnet client.
problem resolves itself when captcha is disabled after some time (6h in my case).
no issues in code, maybe just +1 topic in faq\readme
Thanks for raising this. I'll leave this open until I get a moment to update the FAQ.
I've updated the FAQ to show the following. Let me know if I can word this any better :)
Q: When Diablo opens it won't allow me to select an online character A1: This will be due to your password or username being entered in incorrectly. Please note that multiple failed authentication requests can cause a temporary lockout from that realm (seems to be around 15-30mins). A2: In some circumstances, Battlenet can also require a capcha code to be entered to verificaton. If in doubt, try logging in via the battlenet client and see if it prompts for captcha. It might take several hours for this to resolve itself (6 hours observed in issue #17).
smth's wrong in $arguments, can't debug. accounts.csv string looks like this:
the game is being launched and renamed but somehow 'connecting to battlenet' screen is being skipped and i'm being thrown on offline characters tab. switching to online tab results in 'cannot connect to server' dialog. same options given via shortcut work like a charm:
tested with or without password encryption and timetracking - no difference