Why the version matters
Resource pack versions change when Mojang changes textures, models, shaders, atlases, or metadata. Choosing the correct target prevents misleading compatibility warnings.
Creative
pack.mcmeta Generator
Create Java resource-pack metadata for older pack_format numbers and the newer min_format / max_format style.
Pack details
Numbers shift when Mojang bumps pack formats. If the game warns about compatibility, compare against the current pack format list for your exact snapshot/release.
Generated pack.mcmeta
{
"pack": {
"description": "My Minecraft resource pack",
"min_format": [
88,
0
],
"max_format": [
88,
0
]
}
}Resource Pack Files
Java pack.mcmeta Generator for 1.21 and 26.x
Generate the metadata file Minecraft Java uses to identify a resource pack. Version presets cover older numeric pack_format releases and the newer min_format/max_format schema used by recent 1.21.x and 26.x versions.
Modern metadata
Newer releases use major and minor pack versions with min_format and max_format. The generator changes schema automatically instead of placing every release under the old pack_format 34 value.
Quick questions
Is this the same as manifest.json?
No. pack.mcmeta is for Java resource packs; Bedrock packs use manifest.json.
Does it create the whole pack?
No. It creates the metadata file. Add assets and pack.png separately.
What do you think about this tool?
If something feels wrong, a Minecraft version is missing, the wording is confusing, or you have a better workflow idea, send it over. Real player feedback is how these tools get sharper.