Bug report
Include the URL, exact steps, expected and actual behavior, browser, operating system and a screenshot without private data.
Ask a question, report a reproducible problem, suggest a correction or discuss a commercial partnership.
Include the URL, exact steps, expected and actual behavior, browser, operating system and a screenshot without private data.
Include device model, firmware if known, connection mode, reported mapping and whether the result repeats elsewhere.
Describe the audience value and disclosure expectations. We do not sell tool outcomes or disguised editorial conclusions.
Do not send passwords, account tokens, full device serial numbers or raw personal text. Most reports need only the physical key code, controller index, anonymous timing result or screenshot of the tool state.
For formulas or technical claims, link to a primary source or provide a reproduction method. Accepted corrections are reflected directly in the affected methodology, limitation or compatibility record with an updated review date.
Paid relationships must be disclosed and cannot purchase a tool outcome, ranking or editorial conclusion. Advertising proposals should include destination URL, market, format, campaign dates and whether tracking parameters or scripts are required. We reject deceptive download buttons, forced redirects and ads that imitate test results.
I answer from this site only — the 28 browser tests, the controls library for 46 games, the sensitivity converters and the two games. I can tell you which page to open, how a tool works and what its result means.
I will not guess. If something is not on the site, I will say so.
Answers come from this site's pages.