BlizzNux collects one thing: reports of Blizzard games running on Linux, specific enough that someone else can reproduce them.
What belongs here
A report of something you actually ran, with the setup you ran it on. Working, broken, or working-with-caveats are all worth posting — a confirmed break saves the next person an evening.
What to include
- Distro and kernel (
uname -r)
- GPU and driver version — Mesa or NVIDIA
- Proton or Wine build, including Proton-GE and Experimental
- Your exact launch options
- What happened, and where it broke
- The date you tested it
That last one carries more weight here than anywhere else. A driver release or a game patch can invalidate a report overnight, so an undated "works fine" is close to useless.
The easy way: the BlizzNux Launcher
The BlizzNux Launcher installs and starts Battle.net through Proton. Link your account and turn on sharing, and it reports each launch and each game run for you, with your setup attached. Those reports are what the Compatibility board on the front page counts. A written report here is still worth more when something breaks in an interesting way.
How tagging works
Every thread you start gets one of these:
- General — reports of what you ran, questions, and anything else.
- Distros and Drivers — the system side. Kernel, Mesa, NVIDIA, distro packaging.
Updates and Meta are written by the site itself: automated upstream changes, and posts about BlizzNux.
Then add up to three game tags for what it is about — Diablo, StarCraft, World of Warcraft and so on. Battle.net launcher is in that list too, because the client breaks independently of every game it installs, and BlizzNux Launcher is for the launcher itself.
House rules
No piracy, no cracked clients, no anti-cheat circumvention. Beyond that: post what you know, say what you are unsure of, and correct the record when something changes.
