Game facts, not guesswork.
A database built from the same public definitions the MIND client loads.
Catalog provenance
This snapshot covers 8,403 records from the deployed 0.48.4 public client. The website runs independently of the game server after import.
- Release
- 0.48.4
- Image revision
82e15177e8df8b8f0a27de103c942a23fb707d84- Catalog
/assets/data-CtryB2Rm.js- Catalog SHA-256
e402c7a7820c1287a22366e87e5d454c70adc211393f46962390144976f37115
What the numbers mean
Drop percentages come from creature loot definitions, not community samples. Runtime scaling, world loot, event rewards, specialized ocean systems, and other server-only sources are not represented as exhaustive drop tables. Missing level requirements are shown as a dash, not an invented level. Quest icons are sigils this site draws from the title of each quest, and a dungeon whose encounters the client ships no still for draws a plan of its own interior the same way; neither is client art.
The talent calculator is the one page that does not read the public catalog: the client's data bundle carries no talent collection, so its tables come from the game's authored source and its numbers are what the client's own resolver computes for a build. Its artwork is the client's own too, except five rows the client composes from a crest recipe, which carry a dashed frame because this site drew the glyph.
NPC and creature zone links use public positions and explicit zone boundaries. We do not guess a location where boundaries are unavailable or confuse dungeon-local coordinates with world locations.
The source references 30 IDs that are absent from the imported collections. Those links are omitted rather than creating broken or fabricated records.
Replacing the old wiki safely
This is the new database foundation, not a completed migration. The running MediaWiki and its articles remain untouched. Existing pages, revisions, discussions, user attribution, and uploaded media must be exported and reviewed before cutover.
Legacy article URLs need an explicit redirect map to their new database entries or preserved articles. Unmatched articles must remain accessible in an archive. Production routing changes require approval; there is no automatic deletion or replacement of the live wiki.