The Method
How this tracker thinks
What the words on this site mean, and what we won’t claim to know.
- Reports are evidence
- You wrote it yourself. The strongest input here.
- Confirmations are signals
- A tap. Counted, never a verdict.
- Source links are leads
- A rumor with a link.
- Official notes are context
- Pearl Abyss said it. That starts a question, not an answer.
- Published
- A full issue card published on this site. Publication is visibility, not an evidence verdict.
- Watchlist
- A public issue that isn’t published yet.
- Watched
- Both together, counted across every patch — not just this one.
- Tracked leads
- Pages the radar is holding for this patch — some public links, some still private. Still leads, not reports.
- Problem areas
- Distinct areas holding at least one tracked lead.
- Reviewed
- Candidates the radar screened — not the coverage we vetted.
What counts as a player verdict?When this tracker records an official fix claim, it notes the date. Only what players say after that date counts toward whether the fix held.
Nothing counts down. No amount of silence turns a claimed fix into a confirmed one — only players saying so does that.
It resets on the next patch. A fix claimed in one patch isn’t a claim about the one after it.
Does a radar lead mean the bug is real?No. A lead is a public page that exists and mentioned something. Finding it proves nothing.
An empty category doesn’t mean nothing is wrong either — it means nothing turned up. Titles and links stay private until something backs them up.
Teaching the scanner changes what it keeps next time. It can’t put a link past the publishing bar. The Observatory shows the whole flow.
How do you know a source is about this patch?It has to name this patch outright, or have gone up on or after patch day. When a page doesn’t say when it went up, we say that instead of guessing.
Times on the radar are when we last saw a page, not when anything happened in the game.
What do you store about me?No account, no email, no trackers, and never your IP address. Your raw report text stays private.
To limit spam we keep a scrambled fingerprint of your connection. It can’t be turned back into an address and it never appears on the site.
What can show up publicly: a count, a summary built from the options you picked, or a short excerpt a moderator approved — never your raw words by default. The save-file helper on the report page reads files in your browser, and the files themselves never leave your machine. Only the short note it writes — which you can edit or delete before sending — goes in with your report.
Scanner intelligence defaults to GPT‑5.6 Luna through OpenRouter. DeepSeek V4 Flash remains an approved manual rollback. When Luna is used, OpenAI does not train on API data by default; abuse-monitoring logs may be retained for up to 30 days.
Why does quiet not count as fixed?Because nobody answered. Silence never turns green here — an issue with no answers is just an issue with no answers.
Report and tap counts are never invented, estimated, or rounded.
When does a source link go public?When a trusted source lines up with an approved player report, or several independent sources say the same thing. It stays a lead either way.
A link from a site we don’t know needs more backup than one from a site we do — a report alone isn’t enough to publish it. Links that don’t clear the bar stay private unless a maintainer publishes one by hand.
Published issues show the links and excerpts behind them, so you can check them yourself instead of taking our word for it.
Should I still report to Pearl Abyss?Yes — first. Nothing filed here reaches them.
Crash dumps, logs, and a PERS ID belong in the official report — Pearl Abyss is the only one who can actually fix it. Mention it in your report here afterward so the record shows you did.
Everything else is in the public repo — how the counting works, what gets stored, what it costs to run, and every rule a moderator follows.
Privacy & moderation · Data sources · View the source on GitHub