Game report moderation and anti-abuse policy
Intake boundary
Use the repository's Game compatibility report / 游戏兼容性报告 Issue Form. GitHub converts form answers into an editable Issue, so submission is only intake—not validation, publication, or a direct database write.
Required evidence
One report covers one game and build. It must include App ID, date, exact device, firmware, OS, kernel, Mesa, Gamescope, runtime/Proton, anti-cheat observation, graphics/display/power settings, launch options, procedure, duration, result, issues, fixes, rollback, and sanitized evidence.
Moderation queue
Intake
GitHub sign-in and required form fields create an Issue labeled game-report and needs-review.
Safety and privacy review
A maintainer rejects secrets, personal data, serial numbers, credentials, copyrighted game files, saves, harassment, cheats, and anti-cheat bypass instructions.
Evidence review
The reviewer checks exact versions, one-variable reproducibility, source ownership, log sanitization, rollback, duplicates, and conflicting reports.
Editorial decision
The report stays community evidence unless reproduced or explicitly published with that label. Only a reviewed snapshot change updates the game database.
Conflict and correction handling
A newer report does not automatically override an older one. Compare game builds, branches, SteamOS/Proton versions, devices, settings, and dates. Preserve dissenting evidence when conditions differ; correct the snapshot through review rather than editing generated output.
Anti-abuse controls
Blank Issues are disabled; the form requires privacy, one-report, no-bypass, attribution, and Code of Conduct confirmations. Maintainers may label, close, lock, redact, or report disruptive content. These controls reduce abuse but do not make public submissions secret—contributors must sanitize before posting.
Publication states
| State | Meaning | Production effect |
|---|---|---|
needs-review | Submitted, not validated | None |
needs-info | Missing reproducible evidence | None |
accepted-community | Coherent but not project-reproduced | May be cited with label |
verified | Review and required reproduction complete | Eligible for snapshot change |
rejected | Unsafe, duplicate, unverifiable, or out of scope | None |
Sources
Version history
- 2026-07-15: Added signed-in intake, privacy, conflict, anti-abuse, and approval boundaries.