Packdev Toolkit

Packdev Toolkit

A collection of developer tools for building modpacks and datapacks. Pull textures/models out of resource packs, dump lang entries, search datapacks, and copy item IDs: all without leaving the game!

Requirements

• YetAnotherConfigLib (YACL).
• EMI (optional).
  • When present, exporting and translation-key-copying work on any hovered item/recipe in EMI.
• Fabric API (Fabric).

Features

Export hovered asset/recipe (O)

Press the export key (default: O) to pull whatever you're looking at into a checklist screen, where you pick which files to copy into your export folder:

• Looking at a block: grabs every texture used by its current block model (including block entities like chests).
• Looking at an entity: grabs its texture.
• Holding an item: grabs the item's texture(s).
• Hovering an item in EMI: same as holding it.
• Hovering a recipe in EMI's recipe viewer: saves the recipe straight to a datapack JSON file (singleplayer only).

Hold Shift while pressing the export key to instead grab the raw JSON definitions (blockstate + block model, or item model) instead of the PNG textures.

Selected files are copied into your configured export directory (see Configuration) and the containing folder is opened for you automatically.

Copy translation key (J)

Press the copy key (default: J) while looking at a block/entity, holding an item, or hovering an item in EMI to copy its lang entry to your clipboard:

"item.minecraft.diamond": "Diamond"

Handy for quickly building en_us.json entries for modpack renames.

Item Descriptions exports (Z)

With Item Descriptions loaded, you can grab descriptions directly in their expected format.

Press the export description key (default: Z) while looking at a block/entity, holding an item, or hovering an item/tag in EMI to automatically append its description lang key to your resource pack's en_us.json file.

This automatically merges with your existing en_us.json if it exists, without overwriting other entries.

Browse vanilla/mod resource (/packdev browse)

This will open up a screen where you can select files from loaded mods to export to your configured data and assets directories.

Dump item IDs and registries (/export)

Grabs item IDs, registries, or tag entries and saves them. Click the chat message to copy to your clipboard or open the exported JSON file in your queries folder.

Search datapacks for item/block usage (/query)

Requires OP. Scans every loaded datapack for references to a given item or block and writes the matching file IDs to a JSON file in your export folder (queries/ subfolder), then links the file in chat.

Useful for answering "which loot tables have this?" or "which structures use this block?" without manually searching through datapack files.

Configuration

Accessible from the config screen in-game using YACL, or packdev_toolkit.json in your config folder

Export Directories

You can configure three separate destination folders for different types of output. These can be relative to the game/server directory or absolute paths:

• Resource Pack Export Directory: The folder that client assets like textures, blockstates, and models are written to (default: packdev_toolkit_resource_pack).
• Data Pack Export Directory: The folder that server data like recipes are written to (default: packdev_toolkit_data_pack).
• Queries Export Directory: The folder that /query and /export list files are written to (default: packdev_toolkit_queries).

Keybinds

Keybinds are rebindable through the Controls screen under the "Packdev Toolkit" category.

Credits

Thanks to Cassian for the idea and basic implementation of translation key copying!

License