A summary of an upstream author’s public record. We attach the original URL, review date and source revision. This does not mean we reproduced the result.
Help the next player.
Good evidence travels. Share a repeatable test, correct a detail, or explain how you solved a problem.
Make the next report more useful
Build a community report
Record what you observed, the conditions, and the evidence. This tool prepares a report on your device. Nothing is transmitted or submitted.
A community submission destination has not been configured yet. Keep your exported report and share it when the site publishes a contribution channel. This form does not send reports to the upstream project.
Clear claims.
A traceable source.
Run status and evidence type answer different questions. We keep them separate on every game record.
A player’s account with its own scope and environment. Exported reports begin as unreviewed. A report only becomes a published record after editorial review.
Reserved for a documented independent run with version, conditions, progress and evidence. No launch record carries this label.
Make your report reproducible
- Name the game’s region and revision, and the project commit. Use “Unknown” when you do not have a value.
- Record the exact scene reached and the time spent testing. A boot, a combat scene and a completed game are different claims.
- For frame rates, include CPU, GPU, browser version, render resolution, scene and how you measured.
- Link the source for corrections. For a proposed solution, describe the steps and whether you verified them.
- Share evidence links and logs. Keep game images, generated game code and personal information out of reports.
For changes to the upstream project itself, consult the original repository and its own contribution process. This site is an independent community resource; its report builder does not submit issues to the author. See the author’s README for the project’s current instructions.