PokeMMO Community Wiki:Data snapshot/2026-09-15

From PokeMMO Community Wiki
Revision as of 14:40, 15 September 2026 by Myztic (talk | contribs) (Document the supplied PokeMMO client resource export, checksums, interpretation rules, and citation format. (via create-page on MediaWiki MCP Server))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page documents a PokeMMO client resource export used as a dated primary source for wiki articles. It records provenance and checksums without redistributing the supplied archive or its complete media contents.

Article status: Reviewed
The archive structure, core JSON files, checksums, and Bulbasaur record were inspected directly.
Last verified: 2026-09-15
Verification scope: Archive identity, resource counts, core-file checksums, and field-level interpretation described below. The PokeMMO client build number was not embedded in the export.

Provenance

  • Export method: PokeMMO client → Settings → Utilities → Dump Moddable Resources
  • Supplied to the wiki project: 2026-09-15
  • Archive name: dump.zip
  • Archive size: 37,430,688 bytes
  • Archive SHA-256: 5d7582757adbb99e67acaa8eb4aa53aa24586520c762734cd39dd299741d5ed9
  • Embedded metadata: info.xml describes the contents as “Directly dumped resources” and reports resource version 0.0.
  • Client build: Unknown; the export does not contain it.

The underlying archive is not published on the wiki. Editors can reproduce the export from their own current PokeMMO client and compare checksums.

Contents inspected

The archive contains 34,142 entries, including:

  • 720 records in info/monsters.json;
  • 559 records in info/skills.json;
  • 3,037 battle-sprite files;
  • 2,860 monster-icon files;
  • 24,659 overworld-sprite files;
  • item data, item icons, cries, trainer sprites, and other exported resources.

Core-file checksums

File SHA-256
info.xml b50189ae985ac44bde5bf6296a0f088b31bf5b5c80b16ff846a0c919f51b72ee
info/monsters.json fddf7e81d2671f0567315b6d370d8c3b410ef8f99a2479ed92286a94ab77929b
info/skills.json 1f22d71d45ca0109e6e4ac65aea59dda56f768b4ccf97b4fc4eb54923eab6ed0
info/items.json 30666f16cda9f229afab5ff080eab4027f31f05a51ffa652ada0959413371530

A separately supplied English string export, dump_strings_en.xml, has SHA-256 2da27ed3eebfdd17a0d6f9a6b86ad50eed734f5f961a80cfd81ca502ad1e14c0.

Interpretation rules

Fields may be published as PokeMMO-specific when their meaning is explicit in the export, including names, types, height, weight, growth type, catch-rate value, obtainable flag, released forms, evolution type and value, base stats, EV yield, named abilities, egg groups, level-up moves, egg moves, tutor moves, tiers, held-item entries, and described locations.

The following fields require more documentation before interpretation:

  • gender_ratio is encoded numerically; do not convert it to a percentage without confirming the encoding.
  • Ability entries are ordered but not labeled as regular, secondary, or hidden in this export; list the names without assigning slot meaning unless independently verified.
  • Move records labeled TM?? do not identify a confirmed acquisition method; do not publish them as a TM list.
  • Numeric rarity_flags values are undocumented. Human-readable rarity fields such as “Lure” may be quoted directly.
  • Accuracy value 101 in skills.json appears to be a sentinel; do not display it as 101% without documentation.
  • An empty array means only that the snapshot lists no entries; phrase the claim accordingly.
  • The missing client build number limits reproducibility. Record it manually for future snapshots.

Citation format

Use a citation beside each supported claim:

<ref name="client-dump-2026-09-15">[[Project:Data snapshot/2026-09-15|PokeMMO client resource dump snapshot, 2026-09-15]], <code>info/monsters.json</code>, record ID 1 (Bulbasaur); core-file SHA-256 recorded on the snapshot page.</ref>

Name the exact file, record ID, and field group. Do not cite the snapshot for strategy, market prices, event availability outside the exported locations, or any interpretation listed as unresolved.

Media

Sprite files can establish what the current client displays, but export access does not itself grant republication rights. Follow Project:Image use and attribution. Until a non-free-content policy is adopted, exported sprites are research evidence only and must not be uploaded for display.