With sharing turned on, the BlizzNux Launcher tells blizznux.com whether things worked, so the next person on the same setup knows what to expect. This is what it sends, and where each kind of report ends up.
Sharing is opt-in
The launcher asks once, after you link your blizznux.com account, and you can change it any time in Settings. With sharing off, no automatic launch or game reports leave your machine.
One thing works either way: when a game closes, the launcher can ask How did it run? (Perfect, Playable with issues or Broken, plus an optional note). That answer is sent only if you press Send, and you can open What will be sent first.
Launch reports
Sent when the launcher starts Battle.net: did the client come up within two minutes?
- A success adds to the running "works" count in that Battle.net build's thread in Updates.
- A failure gets its own reply in that thread, with your setup and the launcher log, so people can see why.
Game reports
Sent when a game session ends. The launcher follows every game session for as long as it is open, not only the first game after Launch: later games in a Battle.net that was left open, and games in a Battle.net that was already running when the launcher started, are followed too. A game that was already running is timed from when it really started. Each session ends with the How did it run? question.
- A session of a minute or more counts as a success and adds to the "works" count in that game build's thread. That automatic report is sent at most once a day per build, so playing all evening still counts as one.
- A session shorter than a minute is not reported automatically. The launcher shows the How did it run? prompt instead, saying "<game> closed after N seconds", and sends something only if you pick an answer, Broken included. A lost connection to Blizzard, a login queue or simply quitting is therefore never posted as a game that did not start.
World of Warcraft sessions are reported under the version that was actually played, Retail, Classic or Classic Era, each with its own build (since launcher 0.2.19). Sessions on test realms, betas and Anniversary are not reported, because the site follows Retail, Classic and Classic Era only.
Game reports carry no log; only failed launches and bug reports attach one.
If the launcher cannot tell which build of a game is installed, it sends no game report and says so in plain words. Since version 0.2.11 it reads the build from the game's own records, including Hearthstone and games installed outside the default folder.
A report you chose to send that does not get through, for example because you were offline, is saved and tried again each time the launcher starts, for up to a week.
Bug reports
Sent when you press Report a problem (in Settings, under Diagnostics), or automatically when Battle.net fails to start if you have linked your account and turned on that separate switch in Settings (it is off by default). Bug reports go to a staff-only area, not to the public threads, and do not depend on the sharing setting. They mention your name for staff, but you get no notification and they never appear on your profile.
A report is attributed to you only while the launcher is logged in. After you log out, or revoke the launcher on your profile, its reports count as anonymous until it is linked again, which happens by itself when you log in.
What a report contains
Your distro, kernel, desktop and session type (Wayland or X11), CPU, memory, GPUs and drivers, the Proton build, the umu-launcher version, what kind of prefix is used, the Battle.net and game builds, and the launcher version. Every report also carries an install ID, a random ID created the first time the launcher runs, so one install counts once; and, when the launcher is linked, your account token.
Failed launches and bug reports also carry the end of the launcher log: the last 120 lines for a failed launch and the last 200 for a bug report. Home folder paths are replaced with ~, and repeated lines are folded into one, like (×126) …, so a noisy warning cannot push the real error out.
Your profile
Launch and game reports keep the Distro, Kernel, GPU, GPU driver and Proton / Wine fields on your profile up to date, so they follow the machine you actually play on. Bug reports never change them.
Where it all shows up
The compatibility board on the front page, the build threads in Updates, and the release thread for your launcher version, which keeps its own "works" count.
