Methodology

We parse mod JAR files and auto-generate documentation from structured data. That's the whole method, stated plainly — no manual writing, no AI-generated prose describing content nobody verified, no guessing.

Every Minecraft mod that runs in the actual game has to register its content — items, blocks, recipes, loot tables, tags — into Minecraft's own registry system, because the game itself refuses to load anything that doesn't. Our engine opens a mod's JAR file directly and reads those same registry entries: the crafting recipe JSON a mod ships, the loot table that defines what a block drops, the texture file for an item's icon, the tag membership that groups it with similar items. Nothing is invented, estimated, or filled in from memory — if the mod's own files don't declare it, the page doesn't show it.

This is also why coverage varies mod to mod. Some content lives entirely in a mod's Java code rather than in a data file the engine can read — when that happens, we say so on the page rather than guessing or leaving a broken-looking gap.

Every item, recipe, and drop rate you see here traces back to a real file inside that mod's own download. If you find something that looks wrong, it's either a real bug in our parser or something the mod's own files genuinely say — either way, we'd like to know. Contact us.