Old School Ops

Reporting a Bug

What makes a report useful, what happens to it, and how to follow one you filed.

Every game · updated 2026-09-11

Report at /bugs/new. You need an account with a confirmed email address, which is the same thing everything else on this site needs. Registering takes a moment and confirming takes a click, and it is what lets you follow what happens to the report afterwards.

What Makes a Report Useful

Three things, in order of how much time they save:

  1. What you did, step by step. A report that can be reproduced is fixed; one that cannot is filed and forgotten. "Zone into Ether, walk to the shop, buy anything" beats "the shop is broken".
  2. What happened, and what you expected instead. Both halves. They are sometimes the same sentence and sometimes not.
  3. A screenshot. A picture of a wrong number settles in one second what a paragraph does not.

Also worth having: the game and version, and whether it happens every time.

What Happens to It

StatusMeans
NewNobody has looked yet
AcceptedReproduced, and it is a real defect
FixedRepaired, and named in the changelog for the version that carries the fix
Not a bugWorking as intended, with a comment saying why
DuplicateAlready reported, linked to the original

A report that is accepted counts towards the tester badges on your profile.

Following One

Your reports are on your profile, and you are notified when one moves. Answering a question on your own report is a comment on it like any other.

Do Not Report

Security problems, in public. Email us instead so the fix ships before the method does.

Things already in the changelog as fixed for a version newer than yours. Update first.

Something here wrong?

Out of date, incomplete, or assuming something it should not. Documentation errors are bugs, and this one arrives tagged and pointed at this page.

Loading…
Open the full search page