Rather than use the Battle.net client, I have shortcuts that go directly to d2r.exe with my password already input. This allows me to quickly change which account is logged in on which pc. As of last night this worked with no issue. Tonight I’m getting the following error, and can’t get online without going through their loader and clicking the shortcut there.
JSON error: Error_SDK_Tassadar client invalid_input(1910) Token : <usually 5, but number differs sometimes>
Nothing has changed at all on my end, so I hope this isn’t the new normal for connecting.
RESOLVED: It seems they fixed it internally. I didn’t do any scan/repairing as one poster noted. Shortcut just works normally again.
8 Likes
same problem don’t know how to fix it
3 Likes
also getting this problem, as far as i can tell it started happening only a few hours ago
2 Likes
I have this problem as well. Does anyone know a fix?
2 Likes
Same problem here, hope they roll this back
3 Likes
Same problem. Just got home from work and spent 15 minutes too long trying to just play the game in a TOS approved manner and still cant get on bnet in game unless I launch directly from the bnet launcher. AI has a whole set of hurdles for me to jump over but I’m checked out for the night, and this is work.
I ask, “Blizzard, WHY?”, and I hope the answer is security, but if inconvenience is the price I’m not buyin’.
1 Like
please help with this. i dont understand why its doing this either. just started today
1 Like
Bump what the heck is even happening
1 Like
Hope we get some updates.
1 Like
same issue here. started happening a few hours ago.
1 Like
do we need authentication tokens to skip Bnet now and be able to just load from desktop…… i play HC…. my comp crashes when i have Bnet up, but not when i go from icon
1 Like
Go from parameter to token, Using token fixes all the issues.
1 Like
wonder if blizzard is trying to kill loaders.
2 Likes
Kill that new bot called Cartographer/Wanderer
Regarding bots, pure speculation below. Take it with a grain of salt.
Blizzard is working on massive changes for Starcraft 2 with a PTR, and considering Tassadar is an SC character, I wonder if Tassadar is one of their internal codenames for a shared server-side system which got updated in the same process and now causes unwanted side effects with other games.
Regardless, same problem here, all my shortcuts broke too. Battle.net launcher is extremely bloated and slow, and direct launching is far more comfortable.
Had this problem, too. it’s now been fixed. I ran scan and repair on Bnet launcher. then Bnet trigger an app update. updated the Bnet and it’s working fine on the shortcuts, no change needed. Not sure if the scan and repair is related.
1 Like