Report a Bug

Step 3 of 4

File the report

Your bug is not in the council yet, and you have your evidence ready. Now you write the report. Take your time here — this is the part that gets a bug fixed.

1. Start a new report

From the project page, select the button to create a new report. You will see a form with a few fields. We will go through each one.

Screenshot: The Create New Report button on the Issue Council

Annotate: circle the Create / New Report button

15-create-report-button.png

2. Set the version and channel

Pick the correct game version using your build number, and the channel you were on. The channel is whether you were on the live game or the test build, the PTU. This tells developers where to look. Official RSI support article

Screenshot: The report form showing the project, game version, and channel selectors

Annotate: number the project (1), version (2), and channel (3)

16-form-project-version-channel.png

3. Write a searchable title

Other players find your report by its title when they search. A vague title hides your bug; a clear one helps others find and confirm it. Official RSI support article

Screenshot: The Issue Title field with a clear, searchable example typed in

Annotate: show a strong title

17-title-field.png

Too vague

“Game broken please fix”

Clear and searchable

“Elevator at New Babbage spaceport does not arrive when called”

4. Write clear reproduction steps

This is the heart of the report. Reproduction steps are the exact actions that make the bug happen, as a short numbered list. Include where you were and what you were doing, so a developer can follow along. Official RSI support article

A clear set of steps looks like this:

  1. Spawn your ship at New Babbage and take the elevator down.
  2. Walk to the transit hub and call the elevator to platform two.
  3. Wait by the doors for thirty seconds.
  4. The elevator never arrives and the call light stays on.

Screenshot: The reproduction-steps field filled with a clean numbered list

Annotate: this is the most important shot in the guide

18-repro-steps.png

5. Attach your evidence and add detail

Add the screenshot or video, your DxDiag report, and your Game.log if the form accepts it. Evidence gives context that text alone cannot. Official RSI support article

Screenshot: The attachment area with a screenshot, DxDiag, and log being added

Annotate: circle the upload control

19-attach-evidence.png

Use the More info field to add anything else useful — how often it happens, whether it happens for friends too, and anything you tried that changed it. Official RSI support article Then submit.

Screenshot: The More info field and the Submit button

Annotate: circle the Submit button

20-more-info-submit.png

Screenshot: The freshly created report page confirming it was submitted

Annotate: caption 'done — now help it get confirmed'

21-report-created.png

That is a real report

A clear title, the right version and channel, steps anyone can follow, and solid evidence. That is the kind of report a developer can pick up and act on. Next, learn what happens to it.