Contact

The most useful reports include the calculator URL, every input, the displayed result and a link to the source or in-game observation that conflicts with it. For a skill-table correction, name the skill and action row.

Email hello@xpcalcs.com. This mail link opens your configured email application; nothing is collected until you choose to send a message through your own provider. Do not send account passwords, recovery details, bank PINs or any other private account information — no report needs them, and a public username is only useful when the problem is a hiscore lookup that failed.

Reporting a wrong number

Because every calculator writes its inputs into the address bar, the fastest possible bug report is a copied link. Press “Copy link” on the page while the wrong result is on screen and paste that URL into the message: it reproduces the exact scenario without a screenshot or a list of fields. Add the result you expected and how you arrived at it. A hand calculation, a wiki section, or a screenshot of the in-game number is enough; a claim that a figure “looks off” without one of those cannot be actioned.

Reporting a data or table correction

Skill training methods, activity rates, drop denominators and Slayer task weights live in dated data files rather than in prose, so a correction needs to identify a row. Name the page, the skill or master, the exact action or task, the value shown and the value that should replace it, and cite the wiki article plus the date you checked it. Where a value changed in a game update, saying which update helps more than any other detail, because it tells us whether the whole table needs re-reviewing rather than a single cell.

Hiscore lookups

Several calculators can fill in levels from the public hiscores. If a lookup fails, include the username you tried, the time it happened and the message shown on the page. That service is external and can rate-limit or go down; when it does, manual entry stays available on every affected tool, so a failed lookup is never a blocked calculation. Usernames sent for a lookup are handled as described on the privacy page.

Accessibility and everything else

Accessibility reports are welcome and are treated as bugs, not suggestions. Include the browser, any assistive technology and the specific control that was difficult to use. The site targets full keyboard operation, visible focus rings, AA colour contrast, respected reduced-motion settings and a usable layout down to a 360-pixel viewport. Feedback about wording, a missing worked example or a calculator that ought to exist is also read, though feature requests move slower than corrections. This inbox is site feedback only; it cannot help with an account, a ban appeal or anything else that belongs with the game publisher.