What this generator is actually good at
The generator is not just a ZIP button. It is the place where a painted texture, a model hook, and a Minecraft version become one exportable pack. That matters because most pack work breaks not on the art itself, but in the handoff between filenames, folder structure, and the final archive.
If you already have the PNGs, this page is the shortest route from loose assets to a pack that the game can read. If you do not have the art yet, the generator still helps because it forces you to think in terms of final targets: item, block, armor, or model variant.
Start by deciding what kind of asset you are packaging
| Asset type | Best tab | Why it belongs there |
|---|---|---|
| Vanilla item replacement or variant | Items | That is where item IDs, textures, and CustomModelData hooks line up. |
| Simple block retexture or six-face cube | Blocks | It keeps the blockstate and per-face texture work in one place. |
| Armor layers and icons | Armor | It handles the texture layer split that is easy to misplace by hand. |
1. Name the pack
Enter a pack name at the top. It will be used in pack.mcmeta and as the downloaded ZIP name. Treat this as more than decoration: a clear pack name makes later updates and testing much less chaotic when several versions are bouncing around a team or a Discord thread.
2. Choose the server version
The version selector controls whether give commands use old NBT syntax or the new 1.20.5+ Data Components syntax. The textures themselves may still be fine across several versions, but the command layer and model hooks can change just enough to create subtle confusion if you ignore the selector.
3. Add items
Open the Items tab, enter a vanilla item ID, upload a PNG texture, and optionally enter a CustomModelData number for a custom variant. This is the common path for story props, weapons, notes, relics, and decorative consumables.
If the item needs a command later, do not treat the pack as the whole job. The visual hook usually belongs here, while the final give command belongs in the Custom Item Builder.
4. Add blocks
Open the Blocks tab to replace a block texture or build a cube from separate top, bottom, front, back, and side textures. This is where builder workflows often get calmer, because you stop guessing where each face should live in the pack and let the export layer handle the exact structure.
5. Add armor
The Armor tab lets you replace armor layers and inventory icons for common Minecraft armor materials. That is especially useful when a server wants visual identity without sacrificing vanilla gear logic underneath.
6. Preview and download
Use the preview button to check blocks, items, and armor. Then click Download Resource Pack to generate the ZIP locally in your browser. This preview step matters more than it sounds. The pack that looks “probably fine” at thumbnail scale is often the one that ships with one swapped face, a weak silhouette, or a filename you meant to rename later.
Common mistakes
- Uploading art before deciding whether it is an item, block, or armor problem.
- Treating the version selector as optional even though the command side will depend on it later.
- Using CustomModelData visually in the pack but forgetting to connect it on the command side.
- Skipping the preview and only noticing mismatched faces or icons after export.
- Assuming the generator should also author the item command when that job belongs in a different tool.
When to switch tools
Switch to Texture Painter when the PNG still needs to be made. Switch to Custom Item Builder when the asset is ready and now needs a version-aware /give command. Switch to Villager Trades or Custom Potions when the final item is not just a pack asset but part of a reward, shop, or gameplay delivery system.
FAQ
Do I need to understand the whole folder structure before using this?
No. That is one of the main reasons the generator is useful. It gives you a clean export layer without making you manually rebuild the same folder tree every time.
Can I use it if I already painted the texture elsewhere?
Yes. The generator works well as the packaging stage even if the PNG came from another editor.
Does this replace the Custom Item Builder?
No. The generator handles the pack side. The builder handles the command side.
Is CustomModelData only for weapons?
Not at all. It can power notes, passes, cups, props, currency, quest items, and almost any custom-looking item.
Why preview before download if the ZIP is cheap to regenerate?
Because previewing catches structural mistakes while the context is still fresh, before the pack gets passed to someone else or copied into a server workflow.