Contact

Report a formula, dataset, accessibility, or route problem to IV Calc.

Send a reproducible report

Email hello@ivcalc.io. For a calculation correction, include the calculator name, copied URL with inputs, displayed result, expected result, generation or GO context, and the reference or in-game observation you used. A screenshot can help, but never include account credentials or personal information.

The copied URL is the important part. Every calculator writes its inputs into the query string, so pressing the copy control while the wrong number is on screen reproduces the exact scenario without a list of fields or a guess about what was selected. Add the result you expected and how you reached it — a hand calculation, a documented formula, or the number the game itself displayed. A report that a value merely looks wrong cannot be acted on; the same report with one of those beside it usually can.

Species and dataset corrections

For a species-data correction, include the National Pokédex number, form, field that is wrong, and a current data source. Canonical species and alternate forms can have different base values; identifying the exact form prevents one correction from breaking another record. Dataset changes are reviewed alongside known-answer tests.

Because the dataset is a dated snapshot committed with the site rather than a live feed, a correction is a reviewable edit to one record. Say which field is wrong — base stat, type, growth group, EV yield, or a GO base value — and give the value that should replace it. Where a change came from a game update, naming the update matters more than any other detail: it tells us whether one record moved or a whole column needs re-reviewing.

Generation and mode mismatches

Many apparent errors are a generation mismatch rather than a formula bug. Mechanics differ across the main-series generations, and Pokémon GO uses an entirely separate stat and CP model, so a page states the generation or mode it supports. If a page gives a result that is right for one ruleset and wrong for yours, that is still worth reporting — say which game and generation you were playing, and the fix is usually a clearer label or an added option rather than changed arithmetic.

Accessibility and scope

Accessibility reports are equally useful. State the browser, viewport, keyboard or assistive technology, and control or section that failed. The site targets visible focus, labeled inputs, 40-pixel touch controls, reduced motion, readable contrast, and no horizontal overflow at 360 pixels. This inbox is for site feedback, not account support or gameplay disputes.

IV Calc cannot recover an account, appeal a ban, verify a trade, judge a competitive ruling, or answer for any publisher. Those belong with the game’s own support. Feature requests are read and are handled more slowly than corrections, because a wrong number affects every visitor while a missing tool affects only the people looking for it.