Docs
Setup, troubleshooting and referenceGet StarStats running.
Five steps, in the order people get stuck on them. Four of them you would not guess. If something here doesn't match what you're seeing, that's a bug in this page — tell us.
Windows or Linux. There is no macOS build.
Saying that plainly beats letting you find out after a download. Grab the latest from the downloads page. On Windows take the installer — _x64-setup.exe — or the .msi if your setup prefers it. On Linux there's an _amd64.AppImage and a .deb.
The Windows installers are signed with a CA-issued certificate, so the signature names TheCodeSaiyan Ltd rather than an unknown publisher. SmartScreen may still prompt for a while — that's a separate reputation system, and a newly-issued signing identity starts with none. Choose More info → Run anyway, or check the signature first — the downloads page shows exactly what it should say.
The desktop app is the thing that reads your log. Everything else on this page is about connecting it to your account.
The website makes the code. The app takes it.
That's the way round people get wrong, so: on the web, go to Connected Uplinks and press Generate pairing code. You get eight characters. Type them into the desktop app.
The code lasts five minutes and works once. It skips letters that look like other letters — no I, L, O, 1 or 0 — so you can read it off the screen without squinting.
The code isn't a secret worth guarding: it only works for the account that generated it, so someone shoulder-surfing it can't attach their own machine to you.
Optional. This is the one to read about first.
To show your hangar, StarStats reads your RSI profile using your own login — which means pasting a session cookie named Rsi-Token into the desktop app. Skip it and everything else still works; you just don't get hangar data.
It's worth understanding what that grants before you paste it, so it has its own page.
Prove the handle is yours, via your RSI bio.
On /settings, start verification. You get a code shaped like STARSTATS-XXXXXXXX. Paste it into your public RSI bio, save the bio on RSI, then come back and press Check now. We read your public profile page and look for the code.
The code lasts 30 minutes. Nothing polls — the check only happens when you press the button, so saving the bio and walking away won't verify you.
Refreshing the page hands you the same code back rather than a new one, so you don't have to re-paste it every time you lose your place.
Off until you turn it on. Then press Save.
In the desktop app's settings there's a checkbox: Sync settings with your account. It's off by default, and it stays greyed out until the app is paired — step 02. Ticking it isn't enough on its own; the settings pane holds your changes until you hit Save.
With it on, this app's theme and settings live on your account and follow you to other machines. You can revoke that from Connected Uplinks on the web at any time.
What this checkbox does not mean is “nothing leaves your PC until now” — a paired app sends, and the server refuses what it shouldn't have. Both halves are true and /trust explains them.
That's setup done. Guides take it from here.
Guides is the other section, and it assumes what's above already works: the desktop app (four of its six tabs aren't named after their job), your dashboard, sharing and settings.
Most of it is one of six things.
No log found, the wrong game channel, sync being refused, kills not showing up — troubleshooting covers each one and why it happens.