Packdev Toolkit
No reviews yet
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!
Includes quality of life improvements and small tweaks to enhance and customize gameplay.
Neoforge is a fork of the Minecraft Forge available for versions 1.20.1+ of Minecraft. Many Forge mods are compatible with Neoforge and vice versa.
Fabric is a mod loader for versions 1.14+ of Minecraft, particularly popular for client side and optimization mods.
Community voices
Reviews
Click once to include, again to exclude, again to clear
No reviews yet. Be the first to review this project!
Get it on
Available Platforms
CurseForge
Modrinth
Compatibility
Supported Environments
About
Project Details
For authors
Embed Badge
If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.
Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.
Identifiers
Platform IDs
About
Description
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.
| Command | Dumps / Exports |
|---|---|
/export hand |
The item in your main hand (as copyable chat array) |
/export hotbar |
All 9 hotbar slots + offhand (as copyable chat array) |
/export inventory |
Your entire inventory (as copyable chat array) |
/export biomes |
All registered biomes (as a JSON file in your queries folder) |
/export structures |
All registered structures (as a JSON file) |
/export configured_features |
All registered configured features (as a JSON file) |
/export placed_features |
All registered placed features (as a JSON file) |
/export registry <registry_id> |
All entries in any registry (as a JSON file) |
/export tag <registry_id> <tag_id> |
All entries inside a specific tag (as a JSON file) |
/export tags_of <registry> <entry> |
All tags that a specific entry belongs to (as a JSON file) |
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.
| Command | Searches |
|---|---|
/query find_item_in_loot <item> |
loot_table and loot_modifiers JSON for the item ID |
/query find_block_in_features <block> |
worldgen/configured_feature JSON for the block ID |
/query find_block_in_structures <block> |
.nbt structure files whose block palette contains the block |
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
/queryand/exportlist 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
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.
| Command | Dumps / Exports |
|---|---|
/export hand |
The item in your main hand (as copyable chat array) |
/export hotbar |
All 9 hotbar slots + offhand (as copyable chat array) |
/export inventory |
Your entire inventory (as copyable chat array) |
/export biomes |
All registered biomes (as a JSON file in your queries folder) |
/export structures |
All registered structures (as a JSON file) |
/export configured_features |
All registered configured features (as a JSON file) |
/export placed_features |
All registered placed features (as a JSON file) |
/export registry <registry_id> |
All entries in any registry (as a JSON file) |
/export tag <registry_id> <tag_id> |
All entries inside a specific tag (as a JSON file) |
/export tags_of <registry> <entry> |
All tags that a specific entry belongs to (as a JSON file) |
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.
| Command | Searches |
|---|---|
/query find_item_in_loot <item> |
loot_table and loot_modifiers JSON for the item ID |
/query find_block_in_features <block> |
worldgen/configured_feature JSON for the block ID |
/query find_block_in_structures <block> |
.nbt structure files whose block palette contains the block |
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
/queryand/exportlist 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
Screenshots
Gallery
-
Extraction Screen -
Blockstate Extraction -
Recipe Extraction
Versions
Files
Relations
Project Relations
More like this
Similar Mods
Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.
On ModDex
Community snapshot
By the numbers
Statistics
Want to reach Minecraft players?
We're looking for a server hosting partner to feature here and other parts of the site. Interested? Send us a message!
Get in touchGet it on
Available Platforms
On ModDex
Community snapshot
By the numbers