Questions about the tracker
Where the data comes from, what the states mean, and why there is no severity column.
Does Valve read this site?
No. CS2Bugs is an unofficial mirror of Valve’s public issue tracker. Nothing here reaches Valve.
To actually file a bug, open an issue on ValveSoftware/csgo-osx-linux. This site exists so you can check whether your problem is already filed first.
Where does the data come from?
The GitHub API, for the repo above. State, labels, upvotes, comment counts and dates are read directly from it — none of it is hand-entered.
What do Open and Closed mean?
Exactly what they mean on GitHub. Open is an issue nobody has closed; Closed means it was closed, which can mean fixed, stale, or folded into another report.
Closed does not reliably mean fixed. Open the issue to see why it was closed.
Why is there no severity rating?
Because the tracker does not contain one. Labelling an issue Critical or Low would be an invented judgement dressed up as data.
The real signals are shown instead: upvotes, comment count and last activity. An issue with 90 upvotes and 200 comments tells you more than a severity badge would.
Why do some issues show both Windows and Linux?
Because the issue carries both labels. The platform pills mirror the labels rather than guessing which system is affected.
Why is Linux so over-represented?
The repo began life as the OSX/Linux tracker and that community still files there most heavily. Windows reports do land there, but many go through the in-game reporter instead and never become public issues.
So the split reflects where bugs get filed, not where they happen.
Can I upvote here?
No. The upvote number is the reaction count on GitHub. There are no accounts on this site and nothing to vote with, which also means there is nothing to brigade. To add your vote, react on the issue itself.
How current is this?
It is a static snapshot, rebuilt when the import is re-run, not a live feed. An issue closed an hour ago may still show as Open here. Every entry links to the source issue, which is always authoritative.
Why do descriptions look cut off?
They are trimmed excerpts with the issue-template scaffolding removed, meant for scanning. Screenshots, logs, system specs and the discussion are all on GitHub behind the link on each entry.
Is this run by FPSHeaven?
It shares the house style and the people behind it, but it is a separate project with nothing to sell.