There's a package for Debian/Ubuntu, a COPR repository and a package for Fedora, a PKGBUILD for Arch, an installer for SteamOS, Bazzite and everything else, an AppImage and a Nix flake. You can also build it yourself: it's a Rust program with very few dependencies, so that takes three commands and a few minutes.
Everything below installs the same two binaries, the menu entry and the icons.
Download lightforge_<version>_amd64.deb from the
releases page.
The file name says 1.0.0.beta.13 because GitHub doesn't allow a ~ in an
asset name. The version inside the package, which apt reads and sorts by,
is 1.0.0~beta.13:
sudo apt install ./lightforge_1.0.0.beta.13-1_amd64.debIt needs glibc 2.35 or newer: Ubuntu 22.04, Debian 12 or anything later.
apt installs nothing else with it; see what you need below.
Lightforge has its own COPR repository,
built from source for every current Fedora release. Add it once, and
dnf upgrade updates Lightforge together with the rest of your system:
sudo dnf copr enable simplykenny/lightforge
sudo dnf install lightforgeWithout the repository, download lightforge-<version>.x86_64.rpm from the
releases page
and install it by hand. You then download each new release yourself:
sudo dnf install ./lightforge-1.0.0.beta.13-1.x86_64.rpmThe same file installs on openSUSE with sudo zypper install. Like the
.deb, it needs glibc 2.35 or newer.
On the AUR, with any AUR helper:
yay -S lightforge-bin # prebuilt binaries
yay -S lightforge # built from sourceBoth packages are the PKGBUILDs in packaging/aur, uploaded unchanged, so
makepkg -si in either folder installs the same thing without a helper.
The installer works on any distribution with glibc 2.35 or newer, needs no root, and only touches your home folder. Run it again any time to update.
Double-click: download lightforge-installer.desktop from the
releases page and
double-click it. Your desktop will warn that the file is untrusted; choose
Continue. A terminal window shows the download, checks it, installs Lightforge
and starts it. GNOME Files opens the file as text instead of running it, so on
GNOME use the command below.
Install from a terminal:
curl -fsSL https://raw.githubusercontent.com/LightforgeProject/lightforge/main/packaging/installer/install.sh | bashUninstall:
curl -fsSL https://raw.githubusercontent.com/LightforgeProject/lightforge/main/packaging/installer/install.sh | bash -s -- --uninstallUninstalling removes Lightforge itself. Your games, the Wine prefix and your settings stay where they are; see Uninstalling for where they are.
On a Steam Deck, do this in Desktop Mode (Steam button, Power, Switch to
Desktop). SteamOS already has the 32-bit libraries Battle.net's installer
needs, so leave steamos-readonly alone. The first-run setup asks whether the
device is a Steam Deck or Steam Machine or a desktop PC running SteamOS.
Retail World of Warcraft is well over 100 GB, so on a Deck add your SD card as
a drive during setup.
One file, no install: download Lightforge-x86_64.AppImage (or
Lightforge-aarch64.AppImage on ARM, see ARM64) from the
releases page,
put it wherever you like, make it executable and start it:
chmod +x Lightforge-x86_64.AppImage
./Lightforge-x86_64.AppImageA browser download is never executable, which is why the chmod. In a file
manager the same switch is under Properties, Permissions. The AppImage updates
itself in place when a new version is out, so keep it in a folder you can
write to, and don't rename it.
Lightforge doesn't add itself to your application menu from an AppImage. Gear Lever or AppImageLauncher do that, or use Add to Steam in Settings.
The command-line tool is inside too: ./Lightforge-x86_64.AppImage cli doctor.
It needs FUSE, which every current desktop distribution and SteamOS have. If
it says otherwise, ./Lightforge-x86_64.AppImage --appimage-extract-and-run
starts it without.
Experimental: nobody has run Lightforge on ARM hardware yet. Each release has
an aarch64 tarball and Lightforge-aarch64.AppImage, and the installer above
picks the aarch64 tarball by itself. There are no ARM .deb, .rpm or Arch
packages yet.
On ARM, Lightforge installs Blizzard's native ARM64 client, so the game itself runs without emulation. Battle.net exists only for x86, and runs through the FEX emulator that GE-Proton's ARM build brings along. Lightforge downloads that build by itself.
Asahi Linux on Apple Silicon uses 16K memory pages, and Wine does not run on
those without Asahi's muvm. Expect it to fail there for now. If you try it on
any ARM machine, tell me how it went, with the output of lightforge doctor.
nix run github:LightforgeProject/lightforgeFor the command line only, without the launcher:
nix run github:LightforgeProject/lightforge#lightforge-cliThe flake starts Lightforge through steam-run-free, because Proton needs a
32-bit loader in the standard paths and NixOS has none. Keep
hardware.graphics.enable32Bit = true; set for Battle.net's 32-bit graphics.
Steam itself isn't needed.
git clone https://git.tuxcore.pro/kenny/lightforge.git
cd lightforge
cargo build --release --lockedThat gives you two binaries in target/release/:
lightforge-gui: the launcher.lightforge: the command line. See docs/CLI.md.
Run it from the build folder:
./target/release/lightforge-guiOr install it, which also adds the menu entry and the icons, like a package would:
make install PREFIX=~/.local # no root needed
sudo make install # or system-wide, into /usr/localmake uninstall takes the same PREFIX and removes exactly what it
installed. Every icon and the window decorations are compiled into the
binaries, so there's no data directory either way.
Use --locked: it builds with the exact dependency versions the project was
tested with, instead of whatever is newest today.
A Rust toolchain, 1.90 or newer. Get it from rustup
if your distro's is older. You don't need GTK, Qt or Vulkan headers. The only
-dev package is libudev's, for gamepads (libudev-dev on Debian/Ubuntu,
systemd-devel on Fedora, part of systemd on Arch). The launcher links
libc, libm, libgcc_s and libudev and nothing else; everything else a
desktop app needs is loaded at runtime.
Fonts. Text is drawn with whatever fontconfig provides; no fonts are built in. Every normal desktop has them. A minimal container doesn't, and shows blank labels.
A desktop portal. The file and folder pickers go through
xdg-desktop-portal and a backend for it. Every desktop environment ships
one; on a bare window manager (sway, i3), install xdg-desktop-portal-gtk or
xdg-desktop-portal-wlr, or Browse does nothing.
A GPU driver. The launcher uses Vulkan and falls back to software rendering by itself if Vulkan doesn't work, so it starts almost anywhere. If your GPU gives it trouble, force software rendering:
ICED_BACKEND=tiny-skia lightforge-guiThat's all WoW needs. Lightforge downloads and checks Proton-GE itself, so you don't need Steam, Lutris or a system Wine.
Battle.net needs one more thing: 32-bit libraries.
Everything Lightforge does to build the prefix is 64-bit and works without
them. Battle.net-Setup.exe is the only 32-bit program in the setup, so
without 32-bit libraries, Proton and the prefix set up fine and then the
installer exits within a second. The launcher checks for this before it
starts and shows the command for your distro. Here they are:
| Fedora | sudo dnf install wine.i686 ✅ verified on Fedora 44 |
| Fedora Atomic (Bazzite, Silverblue) | rpm-ostree install --apply-live wine.i686 (if it refuses: without the flag, then reboot) |
| Debian / Ubuntu | sudo dpkg --add-architecture i386 && sudo apt update && sudo apt install wine32:i386 |
| Arch | sudo pacman -S lib32-gnutls lib32-freetype2 lib32-vulkan-icd-loader (multilib must be enabled; Arch's wine no longer brings them) |
| openSUSE | sudo zypper install wine-32bit |
Only the Fedora line has been tested on a real machine. The others should be right for how those distributions are packaged, but I haven't tested them. If one is wrong, tell me in Discord and I'll fix it.
Two more details:
- The table names the Wine package even though Lightforge uses Proton's own
Wine. What's really needed is the 32-bit graphics stack, and the distro's
winepackage pulls in all of it. On Fedora,glibc.i686andfreetype.i686alone pass every check, and the installer still fails. - On Debian, installing Steam also fixes it, because the Steam package enables i386 and pulls in the 32-bit libraries. You shouldn't need Steam for this, though.
You can skip Battle.net. Decline it during setup. WoW works without it, but you won't have the in-game shop, the Token or the other games.
If you want to give a build to someone else, don't use one built on your own machine. It needs the glibc version you have, and on a rolling distro that's newer than everyone else's. Here, a local build needed glibc 2.44, which is newer than SteamOS and Bazzite have, so it didn't start on either.
make releasebuilds inside a Debian 12 container and fails if the result needs a glibc
newer than 2.35. The binaries end up in target/container/release/,
stripped, and run on Arch, Fedora, Ubuntu, Bazzite and the Steam Deck.
You need podman (or make release CONTAINER=docker).
The first time, the launcher takes you through a short setup:
- Where games should live:
~/Games/Blizzardby default. You can add other drives now or later. - Region and language, so you get the right game version and language.
- A scan for Blizzard games already on this machine. If you've played through Lutris, Bottles, Heroic, Faugus or your own prefix, your installs are found and used where they are. Nothing is moved or downloaded again. The scan reads Battle.net's own registry, so it doesn't search your whole disk.
- Battle.net, if you want it: the prefix, a verified Proton-GE build and the client itself, in three steps you can follow.
After that you're on the Play page.
When a new version is out, Lightforge shows an update notice:
- Installer: the notice updates Lightforge for you. Running the installer again works too.
- AppImage: the notice downloads the new AppImage and puts it in place of the old one; restart Lightforge to use it.
.debor.rpmyou downloaded: the notice fetches and checks the new package and opens a terminal where your package manager installs it and asks for your password. Or install the new file over the old one yourself.- Fedora COPR and Fedora Atomic:
sudo dnf upgrade, or your system's normal update. - Arch: your AUR helper's update (
yay -Syu), or the notice, which builds the new PKGBUILD in a terminal. - From source:
git pull
cargo build --release --lockedUpdating never touches your config, games or addons; they are stored outside the program.
sudo apt remove lightforge, sudo dnf remove lightforge,
sudo pacman -R lightforge-bin, the installer's
uninstall command, or
make uninstall PREFIX=~/.local. Then delete whichever of these you want
gone:
~/.config/lightforge/ settings
~/.local/share/lightforge/ Proton builds, addon ledger, logs
~/.cache/lightforge/ artwork, catalogues (safe to delete any time)
The games are stored separately:
~/Games/Blizzard/prefix/ the Wine prefix (can be rebuilt any time)
~/Games/Blizzard/games/ your games, often more than 100 GB
Deleting the prefix only means it gets rebuilt. Deleting games/ deletes
your downloads, so check what's in there first. If you added other drives as
libraries, each of them has its own Lightforge/games/ folder too.
Ask in Discord. Install problems are the reports that help me most, because I can't reproduce them on my own machine.