Official Pokelike
Public Pokelike pages or client data can support only the facts they actually expose.
Methodology
How Pokelike Wiki Verifies Information
Pokelike Wiki records where important claims come from, what each source can support, and which game version or date the information was checked against. When evidence conflicts or a detail is unknown, we show the uncertainty instead of guessing.
What the labels mean
Read the evidence type before the conclusion.
Pokémon base data
A pinned Pokémon dataset and type chart support names, Forms, evolution, and matchups—not Pokelike availability.
Community-reported
A player report can support an attributed observation or strategy, with its conditions kept visible.
Conflicting or unknown
When evidence disagrees or omits a detail, the page says so and avoids a guessed result.
How evidence becomes an answer
Record, limit, explain, and act.
- 1
Record the source, access date, and version when the source states one.
- 2
Write only the answer that the source can support.
- 3
Show community attribution, conflict, or an unknown instead of smoothing it away.
- 4
Link the answer to a useful next step, source inspection, or correction path.
A real conflict example
Resolving the Soothe Bell and Lum Berry question.
An older community thread reported conflicting boost counts. We preserved that uncertainty until a version-pinned test was available. In v3.1.1, 150 controlled cases using the original battle engine confirmed two Lum Berry rolls alone and four with an enabled Soothe Bell. Repeated stats are possible. The guide separates that result from untested special modes and live-run acquisition, and retains the older report as historical context.
Inspect the Soothe Bell exampleWhen data can be used in a calculator
Only the supported part is calculated.
A calculator needs the exact inputs required for that result and a source for those inputs. If a field is missing or disputed, that result stays unavailable while unrelated team analysis continues to work. Missing information is never silently changed to zero.
What happens after a Pokelike update
Current version and page review dates stay separate.
A new public version updates the site-level version record. Imported Item or Battle Tower data receives its own review date, while older guides keep their previous version label until their evidence is checked again.
Inspect or correct the evidence
Follow the source, or show us what changed.
The source registry shows what each record supports and where its limits begin. A useful correction identifies the affected page and statement, proposes replacement wording, and includes a public source.
Technical note for maintainers
Structured schemas validate required calculation fields and source references. The retired calculationEligible terminology is not a user-facing trust label; a calculation runs only when its required data is structurally valid and sourced.