On Linux this is very easy to do with Steam and Proton, without the need to install any third-party apps or change settings in the launcher or the game.

Step by step guide

Note: Two different Battle.net accounts with Diablo 2 Resurrected are required.

1. Download the Battle.net installer.

2. On Steam in the Library section go to Add a Game -> Add a Non-Steam game -> Browse -> select the file Battle.net-Setup.exe -> Add Selected Programs

3. Right-click on the newly created entry -> Properties -> we can name this however we want, such as Battle.net 1. In the Compatibility tab check Force the use of a specific Steam Play compatibility tool and choose Proton 10.xx in the dropdown below.

4. Right-click on the entry again -> Play. This will launch the Battle.net installer. We can accept all the default options and when it's finished the Battle.net launcher will be installed in a Wine / Proton prefix automatically created for this program.

5. Go to Properties again and edit the Target and Start in fields, so that they point to the installed app's executable instead of the setup file. We can easily find the installation path of the Battle.net app by running this command in a terminal from the home directory:

   find . -name 'Battle.net Launcher.exe' -exec readlink -f {} \;

   Copy the path found, paste it into the Target field, and enclose it in double quotes.

   In the Start in field enter the path as well but remove the /Battle.net Launcher.exe part and add quotes to it too.

6. Now when we click Play the Battle.net app will open and we can log in with our account and install / run Diablo 2 Resurrected.

Since Wine / Proton automatically isolate file systems and processes from each prefix, we can repeat the same steps a second time, creating another entry called Battle.net 2 and installing the Battle.net app and the game again, which will go into a different and independent prefix.

In the end we can run both entries simultaneously and log in with a different Battle.net account on each one, enabling dual-boxing without having had to tweak any settings in the game or the launcher or use third-party apps.

Here's a demo video of the finished setup:

Personally, I've been using the Workstation edition with KDE happily for many years now and always update yearly two releases forward, when the one I'm currently on is close to EOL. I've not faced any issues in more than 10 major versions, and going from 40 to 42 was no exception. These are some tips that I think are important to maintain such level of continuity and stability:

• Don't use programs from third-party repositories, except for RPMFusion. They might introduce conflicts with other packages or not provide versions for new Fedora releases on time. With so many apps nowadays on RPMFusion and Flatpak this is very easy to avoid.
• Keep / and /home in separate partitions. This way even if something goes wrong with the release upgrade you can reinstall from scratch without any damage to most of your configuration and personal files.

Congratulations to Red Hat and the Fedora team and community!

This time luckily only minor document formatting changes were needed to make them fully compatible with the new version of MDX that it uses.

Only for the base domain (username.gitlab.io) I had to also update the repository path under Settings -> General -> Advanced -> Change path to /newusername.gitlab.io.

Finally, I didn't face any issues with the deploy pipelines in the new namespace.

To make a prefix use a certain Wine build first it needs to be added under Tools -> Wine Version Manager and after that is done in the Prefixes tab it can start being assigned to them.

The update process from the beta 17 was pretty simple although some configuration options were moved to a different file and some CSS styles seemed to work differently on certain components, which required some additional small tweaks.

Official announcement.

To install the PWA (Progressive web app) simply click on the install button that shows up in the URL bar while browsing the site.

Since the main features work well, I will continue using Docusaurus v2 exclusively for this website from now on.

Hopefully it'll also make it easier to maintain in the long term and more secure since it uses newer libraries.

Stuff that still needs to be migrated and won't be available for a while:

• Most docs.
• Offline version.
• Disqus comments.

Release notes.

With Wine lots of titles became playable, while it evolved from a complicated, bare-bones tool to a diverse ecosystem supported by front-ends and helper apps. For instance Winetricks, a script that simplifies the installation of some Windows runtimes and libraries, like DirectX or Visual C++, which many games require. Others like Lutris and PlayOnLinux allow creating and managing isolated Wine environments tailored to specific programs, through a graphical interface.

Even with the help of these tools configuring Wine to run certain games often involves manual tweaking of settings, registry edits, and troubleshooting compatibility issues. The process can be daunting and time-consuming for newcomers and even seasoned Linux users.

The Wine Application Database (AppDB) allows users to browse and submit test results, documenting how well each application runs under Wine and any tweaks that were needed to make it work. Contributing to the AppDB not only helps other users but also serves as a personal record for future reference. For example, my submissions include:

• Pirates of the burning sea - A naval MMORPG that ran smoothly with the addition of a few dependencies.
• Final Fantasy VIII - PC port of the classic PS1 JRPG which also ran well with really simple adjustments.
• UOSteam - Mapping tool for the game Ultima Online. Only needed one small additional library to execute without issues.

By sharing these setups, I think I might’ve helped others manage to replicate successful configurations while creating a reference for myself when installing a similar application, or the same program on a new machine. This can be especially useful since official support in my experience is usually very hard to get for particular problems.

It can be used while browing the website connected to the internet.

The previous version created using Sphinx can still be accessed here although it is not being updated anymore.