How we check information
We prioritize the matching game’s own interface, published data and developer announcements. Third-party tools are described using their own source or official marketplace listings. A publisher’s feature claim is labelled as such until independently tested. Search results and player questions help us identify useful topics; they do not establish game mechanics or prove search volume.
Version boundaries
Every guide names its scope. Data from .net, .com, .io, Extended and World is kept separate. The version hub records confirmed relationships and missing identity information. A shared name is never enough to merge drop rates, evolution rules, formulas or save formats.
Dates and limits
“Last checked” records our source review date, not a game release date. Historical announcements remain historical. Source panels distinguish live interface checks, code inspection and publisher descriptions. We do not claim an account-based feature was playtested when only its documentation was read.
Tools and assets
The .net encounter lookup is a dated snapshot of published data, not a live account reader. It never asks for a game login or save. The compass identity and decorative diagrams are original. Limited interface screenshots illustrate the controls discussed; game imagery and names remain the property of their owners.
Corrections
For a reproducible correction, record the exact domain, displayed build, relevant source URL and the control or table that differs. Do not send game passwords or authentication tokens. Until a dedicated public contact channel is verified, this guide does not display an untested support email or a non-working submission form.