Streaming from Linux
The managed app is Windows-only today (a native Linux client is in the works). Until then, any stock OBS can stream to the team server - you lose auto-record and pull markers, so start your stream at raid start and stop it after; the server keeps the VOD either way.
1 · Get your stream settings
Sign in on the account page and click Show my stream settings. You'll get the server URL and your personal stream key. The key is a password - don't share it or show it on stream.
2 · OBS settings
Install OBS Studio 30+ (distro package or Flatpak), then:
- Settings → Stream: Service Custom, paste the server URL and stream key.
- Settings → Output (Advanced mode): encoder x264 (or NVENC on NVIDIA / VAAPI on AMD & Intel if available), rate control CBR, bitrate 6000 kbps at 1080p or 12000 kbps at 1440p, keyframe interval 2s, B-frames 0.
- Settings → Video: canvas and output at your game resolution, 60 fps.
- Capture (best): install
obs-vkcaptureand launch WoW withOBS_VKCAPTURE=1in its environment (Lutris: game options → environment variables; Steam:OBS_VKCAPTURE=1 %command%). Real game capture, works on X11 and Wayland. NVIDIA needs driver 515+; on Wayland run OBS as native Wayland. The agent below creates the source for you. - Capture (fallback): X11 - Window Capture (Xcomposite) of the WoW window; Wayland - Screen Capture (PipeWire), pick the WoW window once (the portal remembers it - don't delete and re-add the source).
- Add your game and voice audio sources; mind what your mic picks up.
3 · Combat logging
The timeline and pull markers come from WoW's combat log. Enable Advanced Combat Logging in WoW (System → Network) and install the team addon - it auto-logs the right content and plays nice with other logging addons:
Unzip into your WoW _retail_/Interface/AddOns/ folder
inside the Wine/Proton prefix. Lutris default:
~/Games/battlenet/drive_c/Program Files (x86)/World of Warcraft/_retail_/
4 · Auto-record: the headless agent
Skip manual start/stop: rtd-agent watches your combat log and starts/stops the stream around raids and keys automatically - the same triggers as the Windows app, driving your own OBS. Needs Node 22+.
tar xzf rtd-agent.tar.gz -C ~ cd ~/rtd-agent/agent node rtd-agent.mjs setup # sign in, point at OBS + your Logs folder node rtd-agent.mjs run # or install the bundled systemd unit
Encrypt your stream key at rest (recommended): after setup,
run node rtd-agent.mjs harden-key. It seals the key into a
machine-bound systemd credential (TPM or a root-only host key) and removes the
plaintext from agent.json - useless if your disk is imaged or
backed up. It prints the one LoadCredentialEncrypted= line to add
to the service unit. For full at-rest protection, also enable disk encryption
(LUKS) on the machine. (See the agent README.)
5 · The Linux app (beta)
The full client as an AppImage: dashboard, timelines, pull review, live streams with DVR, and auto-record - driving your own OBS over its websocket (it never installs, closes, or reconfigures OBS beyond the stream destination, canvas, capture source, and chat blocker). Enable OBS's WebSocket server (Tools → WebSocket Server Settings) and enter the details under Settings in the app. Updates are a red pill in the title bar - no silent installs on Linux.
chmod +x ReviewTheData.AppImage ./ReviewTheData.AppImage
Ubuntu 22.04+/Mint: install FUSE 2 first -
sudo apt install libfuse2 (Ubuntu 24.04: libfuse2t64) -
or run with ./ReviewTheData.AppImage --appimage-extract-and-run.
Without it, launching does nothing.
Beta: the agent (above) is the battle-tested path; run whichever fits. Both can share the same OBS - just not at the same time.
What works, what's coming
Streaming, auto-record (agent or app), team-only VODs, and retention all work like the Windows client - and review works in any browser at reviewthedata.io/team/review: live streams with DVR, past VODs, and the full dashboard, no app needed. Capture and encoder settings stay yours in OBS.