#Installing Battle.net on Linux Mint

54 messages · Page 1 of 1 (latest)

nocturne stump
#

If Lutris fails to download for you:

  1. Get the Windows installer for the Battle Net launcher (you may need to user User-Agent switcher extension to trick the browser into thinking you are a Windows client)
  2. Add it to Steam as a non-steam game and enable proton in the properties (Worked for me with Proton Experimental)
  3. Launch the installer and following everything
  4. After done installing locate the folder /home/$USER/.steam/root/steamapps/compatdata/<SOME RANDOM PID>/pfx/drive_c/Program Files (x86)/Battle.net (you can go to the steam folder and just search the .exe's name directly)
  5. Add the Battle.net Launcher.exe as a non-Steam game again and enable Proton
  6. Follow the steps of installation along with account login.
  7. Install HOTS to specific location (chosen from launcher settings)
  8. Add Heroes of the Storm .exe file to Steam as a non-Steam game and launch it with Proton, this should remove launcher and prompt for it to be installed again.
  9. Done. Use the HOTS .exe file for launching the launcher from which you will launch Heroes of the Storm
heavy cloud
nocturne stump
heavy cloud
#

Yep

nocturne stump
#

Experimental? It ran fine for me on it

heavy cloud
#

Didn't try that will do now

nocturne stump
#

Run it with experimental and tell me

heavy cloud
nocturne stump
#

This could be a driver/dependency issue then

#

You CAN try to manually debug it by trying to figure out directly from Proton's logs

heavy cloud
#

When I did the battle net install the first time, I created an account from the first exe. bc I didn't read ahead and see that I needed to do it from this exe, do you think that affected things at all?

nocturne stump
#

If the launcher itself is not appearing that's a different problem

heavy cloud
#

Dang. And, nobara is supposed to be a gaming distro. I could ask on their discord about it though

nocturne stump
#

Do that, for testing the game itself and seeing the logs

# 
STEAM_COMPAT_DATA_PATH=/mnt/<ID>/Games/steamapps/compatdata \
STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/user/.local/share/Steam \
WINEDEBUG=+all \
"/mnt/<ID>/Games/steamapps/common/Proton - Experimental" run /mnt/<ID>/Games/steamapps/common/Noita/noita.exe &> proton.log
#

This worked for Noita which is a steam game so idk how it would work with a Non-steam game but ...

#
  • Find your compatdata path (this example uses an external drive since I keep my games there)
  • Find the default Steam install location
  • Find the proton version that is being used for launching your game
  • Find the game exe itself
#

This generates a detailed proton.log file of what went wrong

heavy cloud
#

I think the PID vanished, so maybe the problem is just that the files got removed somehow

#

Nobara discord is telling me I need proton 10

#

My computer doesn't seem to play nicely with it. I think I'll just wait till I'm on the next version of Nobara for it. Maybe then things will be more stable.

heavy cloud
# nocturne stump Do that, for testing the game itself and seeing the logs

Okay I got it working using lutris thanks to the Nobara discord. Looks like I had to click on the gear next to wine, and configure wine settings to use proton experimental. Then the lutris script handled the rest. I had to do it twice, because apparently you shouldn't log in the first time around (maybe that's what screwed up my steam install?) and then on second launch the battle net launcher seemed to work fine. Now I am installing HoTS through lutris and it.

#

I did need to use proton experimental, which I believe is proton 10

blissful moat
#

Proton experimental is recommended for Battlenet. MS has been patching it. Be warned Lutris may stop working in the future. Usually it's as simple as deleting a run off, error file in your Bnet folder. Then restarting.

heavy cloud
#

Gotcha sounds good. Yep game runs flawlessly now 🥳

blissful moat
#

Just beware those future patches. MS is probably removing bnet. Steam proton instead of wine will be your best bet going forward.

heavy cloud
#

@nocturne stump Okay I am back. On Nobara I was having stuttering when recording with OBS and HoTS would occasionally crash midgame.
I was told by a friend that he thinks it is my Nvidia drivers (I was using 3:570.153.02-1.fc42and he said I should downgrade to 566.36).
Since changing Nvidia drivers is hard on Nobara, I´ve installed Linux Mint into a 350 GB partition.

I was wondering should I now switch my Linux Mint install to use the proprietary drivers (so that I can run things like Eldin Ring?) and if so how is it done.
Information on the internet is not great and I bricked my install the last time I attempted this (on Fedora)

#

Is it as simple as running apt install nvidia-drivers=566.36 to replace my current open source drivers?

heavy cloud
#

Nvm, I found the tool

Screenshot_from_2025-06-01_23-05-32.png
#

I guess after I use this I could downgrade to 566 using apt install nvidia-drivers=566.36 ?

heavy cloud
#

Nevermind. I got OSErrors trying to install battlenet with lutris. And, now lutris won´t even detect steam proton.
Its all borked to hell and back.

heavy cloud
#

I think my best bet is to just wait until newer Nvidia drivers get shipped with Nobara (that fix the issues). As my technical understanding of it all is rather poor

nocturne stump
#

@heavy cloud you can add more drivers

#

Use the ubuntu ppa for em

heavy cloud
#

Lutris started magically working again, after uninstalling some things and restarting my computer, and then my battlenet install went through, did one test game but crashed near the end of the match

blissful moat
#

MS is still patching Bnet. This is why it goes from working to not working. All we can do is stay ahead with updates. At some point MS will close down Bnet, probably move to their store page and Steam.

#

I noticed this does not happen with other games like Black Desert. MS is being hostile in the code.

heavy cloud
#

Mint for the win 🙂

round yew
nocturne stump
round yew
#

just add the game from lutris menu?

nocturne stump
#

There are YT tutorials

round yew
#

i think ill just stick to running it in a docker container

nocturne stump
round yew
#

no lutris on void :(

#

oh wait nevermind!

#

ill compile it from voidsrc