Minecraft resource pack converter

How does world transfer work — and what it doesn't do

The table comes from client-side data, not from memory. For each version from 1.8.9 to 26.3, the Mojang client is used, and adjacent versions are cross-checked. A texture is considered migrated if its image in the old client matches pixel-perfectly with the new file in the new version. So blocks/wool_colored_red.png becomes block/red_wool.png, and armor 1.21.2 is lost in entity/equipment.

Atlases are split into sprites. In 1.20.2, the interface textures were split into separate files: widgets.png and icons.png were split into hundreds of sprites. The converter extracts them from your pack's atlases at the original scale, including 32× and 64× packs, and adds button-scaling metadata. It also splits 1.9 clock and compass frames and 26.2 bed tops.

custom_model_data — in items. From 1.21.4 the game no longer reads overrides in item models. The converter collects items/*.json with the same thresholds and models, and updates all JSON files in the pack to correct references to renamed textures and models.

What doesn't transfer is explicitly noted. Block states from 1.12 are converted to 1.13 format based on options, but new blocks from 1.13 have no source to copy from; translations up to 1.13 are rewritten entirely, as outdated shaders would break loading. Special descriptions apply to certain items (banners, heads, compass). Such files are not included in the pack but are listed in the report by name. Sounds and OptiFine are moved as-is; they are not verified.

Back — only by number. Older version files cannot be translated: one number changes in pack.mcmeta, and the data pack stops glowing red. The format number will indicate what it is resource pack parsing and several packs can be combined into one on the page pack merging.