EasyPackMaker

Extract this ZIP into your EasyPackMaker folder. Open Pack Manager and double click New Pack.bat. Enter a Minecraft version and a pack name. The finished pack folder opens when it is ready.

Use 64 bit Windows 10 or 11. Python downloads on the first run. You need an internet connection for new Minecraft downloads and a few GB of free space.

New Pack.bat
Creates an editable vanilla pack in Packs, named VERSION-Name. For example, 1.21.11-Test. Downloads are cached, so making another pack for the same version does not download everything again. Existing packs are never replaced.

Preview Pack Changes.bat
Choose a pack to see its added, modified and deleted files. This compares file contents with the original pack. It does not open Minecraft or download a launcher. An unchanged pack shows no changes.

Build Entire Zip.bat
Builds all usable resource files into a ZIP under Builds/Full Builds.
Example: AllBuild-1.21.11-Test-1.zip

Build Changed Files.bat
Builds added and changed files, plus pack.mcmeta, pack.png if present, and any needed texture metadata. ZIPs go under Builds/File Builds.
Example: ChangeBuild-1.21.11-Test-1.zip

Each build uses the next number for that pack and build type: 1, 2, 3, and so on. Older ZIPs are kept. The output folder opens when a build finishes.

Deleting a vanilla file from a pack does not hide it in Minecraft. The game uses its original file instead. Deleted files are shown in the change list but are not added to the ZIP.

Folders
Packs holds the editable packs.
Builds holds Full Builds and File Builds.
Pack Manager holds the four BAT files and Scripts.
Scripts holds the helper code, Python runtime, downloads, pack records, temporary files and lock files.

The window shows Please wait while copying, checking or building files. Longer steps also show Still working so you can tell the process is running.

Updating an existing copy
Close any open EasyPackMaker windows and the old preview launcher first. Extract this ZIP into the same folder, replacing the BAT files, scripts and README when asked. Keep your existing Packs folder.

On the next run, old support folders in Pack Manager move into Scripts. Existing builds move into the new Builds folders and receive numbered names. Pack contents are not changed. Old preview files are moved into Scripts/preview and are no longer used by the tool.

Keep Packs, Builds and Pack Manager together when moving the workspace. Do not rename pack folders after creating them or delete Scripts/pack-data. Those records identify each pack's original Minecraft version.

Versions
Enter the exact Java Edition version, such as 1.21.11, 26.1 or 26.2. Each pack keeps that version's own file layout. Snapshots and prereleases work when their official downloads and pack metadata are available. Unknown or unavailable versions show: Version not recognized.

If something fails
Only one EasyPackMaker window can work at a time. Close the other window and try again. If a download fails, run the BAT file again. Completed downloads stay cached. If two old and new support files conflict during an update, both are kept and the tool shows their paths.

Testing
Pack creation and ZIP builds were tested with 1.6.1, 1.12.2, 1.21.1, 1.21.11, 26.1 and 26.2. The change list, support folder migration and numbered builds were also checked. Windows BAT execution and Python setup have not been run in the test environment.

To run the automated tests after the first setup, open a command prompt in Pack Manager and enter:
Scripts\runtime\python.exe Scripts\test_easypackmaker.py
