I understand that but id imagine syntax and spacing matter so this is what my chunk looks like. Is that correct?
“GameLaunchWindowBehavior”: “2”,
“HardwareAcceleration”: “true”,
“StreamingEnabled”: “true",
“Version”: {
“FirstRun”: “false”,
“Release”: {
“FirstRun”: “false”,
“LastBuildVersion”: “13747”,
“LastSeenPatchNotesVersion”: “13747”
}
TLDR: I did the same procedure as Phattie and it seems Starcraft II works again and can be updated fine for me now, thank you very much for this.
As I had uninstalled it while troubleshooting I had to reinstall it using the lutris installer:
When the battlenet installer opens I go into drive_c/users/<myname>/Application Data/Battle.net/Battle.net.config as described by Phattie’s comment above and set HardwareAcceleration and StreamingEnabled to true.
When the battle.net installer does the 100%->0% thing and stops forever I waited a bit and then killed the battlenet launcher install process (ps aux | grep .exe then kill the installer one) which lets the lutris installer continue.
After this I set the wine version to proton and started it up. The launcher started normally and I could install Starcraft II. I have now launched the game and it works perfectly.
Notes on this method:
The game install window takes some time to open after clicking the button so don’t worry about nothing happening immediately.
The download progress visually stays at 0% until it reaches playable and then stays at that percent. It stopped at 93% for me but after I restarted battle.net it said it was fully installed.
I get some random error messages periodically while battle.net is running but I just close it immediately after starting Starcraft so it doesn’t bother me.
It seems like it sometimes gets stuck at “trying to wake up” when starting the client but turning it off and on again fixed it every time it occured for me.
I personally did not have to replace any files with older versions or do anything else that chazdingle mentioned but that doesn’t mean it works the same for everyone of course.
That looks good to me 
Im not sure with the spacing, but its json so it shouldn’t matter.
TapeEater: Mine looks like this and works fine. Mine is installed using lutris so yours may look different if it isn’t though.
{
"Client": {
"GameLaunchWindowBehavior": "2",
"HardwareAcceleration": "true",
"Sound": {
"Enabled": "false"
},
"Streaming": {
"StreamingEnabled": "true"
}
},
"Games": {
"s2": {
"AdditionalLaunchArguments": "-Displaymode 1"
}
}
}
Interesting yours is within a Streaming object… not sure why ours should be different haha although now it makes me wonder if my entry is wrong! 
I could install bnet using instructions here but I can’t update d2. Still 0% of updating progress and “waiting another update”
It took a while and the UI doesn’t update normally like you’d expect, you just have to wait. Mine took about 15-20 minutes to update and I have a gigabit connection.
Check my comment above, the download status cannot be trusted at all. It is downloading, just telling you something else.
Agent.8012 keeps crashing every minute.
You can check the folder yourfolder/Battle.net/Agent/Agent.8012/Errors
Edit: wine 5.7 seems to be working, at least the agent is not crashing and the status is not frozen.
Edit2: lutris wine 5.7 is working to download the game client.
I think 8012 works fine - Mint, Lutris, default runner (lutris-7.2), old install of WoW, - just the update servers are overloaded with the WotLK going live this morning. I had the same issues about 3 hours ago right after the WotLK went live, crashing etc etc. Came back now, and successfully updated WotLK.
Oh and I did make the change to Streaming as per @Karl above in the Battle.net.config file.
There is no battle.net.config in my installation. Is there anything I can do to generate one?
Does anyone have a solution for steamdeck here? The installer will not go passed 50%.
I was able to get it working. Haven’t tried to reproduce yet, but here were my steps:
After following these steps, I was able to install and am now playing Overwatch. This was tested on Sunday, September 18th.
After killing the installer process after the 100 to 0% bug
Battle net was able to start
Games installed, but took forever
Games booted fine.
Not ideal, but atleast i can play d2r. I missed the late PTR changes because of this 
I was able to follow the instructions linked in this thread to get games working on Steam deck again! Thanks everyone.
Hopefully Blizz resolves the issue with the new agent file.
Steam Deck (Proton compatibility) worked good before the last update. Please fix this issue or revert those changes for the agent!
Doing a fresh install of the Blizzard App will get it back to running, but if you look carefully Agent.8012 is still crashing continously in the background.
Hello, even if I was able to install the Battle.net as someone above me suggested, the launcher doesn’t upgrade the games, also it doesn’t let me launch them, remaining in a permanent state of “Updating…”.
Please blizzard, the games already works fine, in many cases even better then windows, so make a full support on linux at least for the Battle.net app. =(
After initial success with the lutris-7.2 runner earlier in the day on 2 prefixes (one to update Lich King, the other to finish installing SC2), I have spent the rest of the day pulling my hair out trying to get it working with a fresh install and later today to update other games. My final working config was esync and fsync disabled, runner lutris-5.7 (the first one in the Lutris download list) and the battle.net.config changes suggested earlier in the thread. Using this, SC2 updates, but all the World of Warcraft games will sit initialising for over half an hour. I think with the Wrath of the Lich King and other PTR content rolling out today along with an update to the agent and certificates, their update servers are overwhelmed. As an aside, it was a painful wait in Windows to update WoW but SC2 downloaded ok.
ehi guys I just noticed a thing, please confirm if you also encounter this!
In my battle.net installation the launcher, since the start, try to upgrade itself to the beta version, so the other games cannot upgrade due to this.