WINE_SIMULATE_WRITECOPY=1 %command% + Proton Experimental = working Battle.net

  • citrusface@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    7 months ago

    I use Linux but I’m an idiot.

    What does %command% mean / do?

    What was the actual line you used in terminal to install battle.net to steam bc I’d rather not use lutris if I don’t need too

    • Muehe@lemmy.mlOP
      link
      fedilink
      arrow-up
      5
      ·
      7 months ago

      The WINE_SIMULATE_WRITECOPY=1 %command% is the Steam launch option you set, with %command% meaning roughly “what Steam would do without any launch options set”.

      The whole process was a bit finicky and I did it a few month ago, but from what I remember it went something like this:

      • Download battle.net installer
      • Add it as non-Steam game to run it
      • Locate the newly created prefix in Steam directory
      • Add the Battle.net.exe in it as a non-Steam game, then remove the installer (not the other way around or the prefix will be deleted)
    • Confetti Camouflage@pawb.social
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 months ago

      It is used in the Launch Options of a Steam game. %command% just gets replaced by whatever Steam would use to launch the game. It’s useful to set up anything before the game actually launches, such as setting environment variables or run scripts.

    • Rentlar@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      7 months ago

      It’s to puts stuff before the game run command.

      Normally if you just add options in that box like -fullscreen they appear after the run command.

    • JTskulk@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      7 months ago

      Installing battle.net in steam is really easy. Just add non-steam game in steam and choose the battle.net installer, then right click on it in steam and click properties, then compatibility, and choose Force the user of a specific Steam Play compatibility tool and choose Proton Experimental. Then just run it and install it like normal. Once it’s finished you just repeat the process for the actual installed battle.net program or whatever blizzard game you want. With this, you don’t have to mess with running custom commands. The blizzard launcher will be located somewhere like “/home/me/.local/share/Steam/steamapps/compatdata/2806461641/pfx/drive_c/Program Files (x86)/StarCraft II/StarCraft II.exe” where the big number after compatdata is something else. You can run the command find ~/.local/share/Steam/steamapps/compatdata -iname '*battle*.exe to help find it. Also you can tell Steam to always use proton experimental if you want, it’s been good to me. Good luck!

    • macniel@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      Why though? It’s just a simple install script you can search and install via the lutris application righ there.