Last updated: October 31, 2026. BreedingCalculator.net researches game mechanics and develops independent calculator tools. This policy explains how we evaluate sources, implement formulas, handle uncertainty, and correct mistakes. Our priority is the usefulness and reliability of each tool, not publishing as many pages as possible.
1. Scope and editorial independence
We cover creature breeding, incubation, inheritance, maturation, configuration, and other calculations in video games. We are not an official partner of any developer or publisher. Advertising, sponsorship, or affiliate relationships, if introduced, must not determine the numerical results shown by a tool.
2. Research and evidence hierarchy
Game mechanics change over time and may differ by platform, event, mode, generation, or server. We examine the context of each source before applying its statements to a formula.
- First preference: official game help centers, patch notes, developer documentation, and directly confirmed mechanics.
- Second preference: reproducible in-game observations, well-maintained community references, and documented public datasets with version context.
- Supporting evidence: independent player guides that explain their methods and are consistent with stronger sources.
- Unverified anecdotal claims are not treated as settled facts or precise probability values.
When sources disagree, we explain the conflict where it materially affects the result. We do not average incompatible values or assume that a mechanic from one game version applies to another.
3. Calculation design and testing
Before publishing, we define the purpose of the calculator, each input, allowed ranges, units, and expected outputs. The implementation must handle empty and invalid input safely, reject unreasonable values, and avoid results that suggest more precision than the underlying data permits.
We test ordinary cases, zero and minimum values, maximum practical values, rounding, conditional effects, and combinations of modifiers. When boosts stack multiplicatively rather than additively, that distinction is documented and tested. A reset control and results displayed directly below the calculation action are expected for new tools.
Some game data is better represented as a versioned table rather than a general formula. Special breeding combinations, event-limited creatures, and parent restrictions must be modeled explicitly when relevant.
4. Game-version and dataset management
Each released calculator should identify the covered game and meaningful version or update period. Static datasets should include a review date where possible. If a patch makes important outcomes unreliable, we may display a warning, limit the tool to an older supported version, or remove it until checked.
For private servers and legacy builds, users should be able to enter compatible custom settings where feasible. We do not silently label results universal when they depend on configuration.
5. Probabilities, simulations, and uncertainty
A predicted outcome may be certain, merely possible, or unknown. We distinguish those states explicitly. We do not invent exact drop rates, breeding odds, shiny probabilities, hidden values, or bonus formulas based on impressions. Estimates must state their assumptions and explain the source of the estimate.
Illustrative numbers used to explain a formula must be labeled as examples. A simulated or sample calculation is not evidence that a result has been observed in the current live game.
6. Accessible, mobile-first presentation
Calculators should be usable with keyboard controls where practical, show labels for important inputs, maintain readable contrast, and fit typical mobile screens. We aim to avoid unnecessary dependencies, intrusive overlays, and complicated registration flows.
7. AI-assisted workflows
AI tools may assist with drafting code, organizing research, evaluating consistency, or improving clarity. AI output is not an independent source of game facts. Important numerical claims and game mechanics must be checked against suitable documentation or reproducible tests before release.
8. Corrections and transparency
When we identify an error, we aim to determine the affected game version, inputs, and root cause. We then update the method and result display, note material changes when useful, and retest relevant boundary cases. Minor typography changes may not require a public correction note.
Useful correction reports include the calculator URL, game version, exact inputs, result shown, expected result, and a supporting source. Do not send passwords, private game-account information, or unrelated sensitive details. Send correction reports to contact@breedingcalculator.net.
9. Reviews and publication decisions
We favor maintaining existing tools over releasing unverified new calculators. A tool may stay in research phase when datasets are unstable, source quality is poor, or competition already provides a significantly more complete solution. A planned game category does not guarantee publication.
See our About page for the project overview and Game Disclaimer for important limitations.