Issue reports and follow-up

Keep a player report with conditions, sources and dates. These reports require editorial review before publication and are separate from anonymous votes and private fix notes.

No logs, attachments, names, contact details or third-party information. Do not put personal data in source URLs. A player’s check and an editor’s evidence review are separate.

Editing and deletion require the owner key in this browser. An ID cannot recover access after changing devices, clearing storage or losing the key. Existing backups exclude this key.

Report text is deleted 30 days after first acceptance; edits do not extend this. This consent does not permit long-term republication in articles.

Checking report availability…

Select the required fields, review the preview, then consent to publication. Optional fields may be blank.

Issue reports and follow-upGame (Required)Issue guide (Required)Symptom (Required)

Steps tried (1–8) (Required)

Select a game and an issue guide first to see the steps you can report.

Current status (Required)Did it work before? (optional)What changed just before? (optional; choose the last change)Date the player checked the result (optional)Game version (optional)Start with a digit; up to 24 ASCII characters: letters, numbers, . + _ - (e.g. 1.2.3). Leave blank if unknown.OS (optional)GPU vendor (optional)Source URL (HTTPS, optional)Date the player read the source (optional)

Blank means not recorded. A link whose content you have not read is not verified.

Your reports

Published reports with similar game and symptoms

Up to 20 reviewed reports. Counts and votes do not prove causes or official fixes.

No reports ready for publication yet.