Help Fix the Game
How to report a Star Citizen bug the right way.
Found something broken? Complaining about it online rarely reaches the people who can fix it. A clear report on the Issue Council does. Here is the whole process, in plain English, for new players and veterans alike.
Why this matters right now
Every big update brings a wave of frustration. A new build lands, something breaks, and the forums, Reddit, and Discord fill with reports of the same problem. Yet the developers sometimes say they cannot reproduce it on their own machines.
Here is the gap. The people who fix bugs do not triage social media. They work from the Issue Council — the official site built for exactly this. A bug with no clear report there is a bug they may never be able to find, let alone fix. Official RSI support article
One good report, with steps anyone can follow, is worth more than a thousand angry posts. This guide turns your frustration into that one good report.
What the Issue Council is
The Issue Council is a website run by the developers where players report bugs and help confirm each other’s reports. The official Issue Council site Think of it as a shared logbook of everything that is broken, with the evidence gathered in one place so the team can investigate.
It is for bugs only. Ideas about balance, design, or new features belong on Spectrum, the official Star Citizen forum. A report that does not describe a bug gets archived. Official RSI support article
Who can use it
Only backers can sign in and contribute — anyone who has bought a Star Citizen package. Official RSI support article You use the same RSI account you log in to the game with. If you do not own the game yet, that is the one thing you need first.
New to all of this? Start with our Day One Citizen guide. And if you use a referral code when you enlist, you begin with fifty thousand bonus UEC in your account.
The four steps
Each step has its own short guide. Read them in order the first time, then keep them as a checklist.
1. Gather your evidence
Your build number, your Game.log, a DxDiag report, and a screenshot or short video. Five minutes of prep makes a report developers can act on.
Open guide2. Search before you file
Sign in, search for your bug, and check whether someone has already reported it. If they have, you add to their report instead of making a duplicate.
Open guide3. File the report
Pick the right version and channel, write a clear title and reproduction steps, and attach your evidence. This is the part that gets a bug fixed.
Open guide4. Track it and help others
Learn what each status means, and add your reproduction to other reports. Ten confirmations move a report up the queue toward the developers.
Open guideIssue Council or Spectrum? Where it goes
The fastest way to get ignored is to post in the wrong place. This is the rule.
| What you have | Where it goes |
|---|---|
| Something is broken (a crash, a missing item, a door that will not open) | Issue Council |
| A weapon feels too weak, or you want a new feature | Spectrum |
| You lost a ship or items and want them back | An RSI support ticket |
Reporting a bug from the test build instead of the live game? The same rules apply, with a test-specific feedback channel. Official RSI support article
More help and official sources
Official (RSI)
You need to be a backer to help
Only backers can file reports on the Issue Council. If you have not enlisted yet, use a referral code at signup and start with fifty thousand bonus UEC — then you can help shape the game too.