I'm all about choice, and I completely agree that taking away control from the user is always a bad idea. but i have to stress that my mod wont do everything. and still allows the users to add their own textures etc.
Take a look at the mod its self - https://github.com/TheJaysH/BiarMod
It currently it has 2 options in terms of adding the blocks & Items.
1) supply it a zip with the json payload, and textures
2) just supply the json.
The first option will create the ResoricePack.zip from the textures the users supplied - and apply it.
The second will just add the blocks & Items, which leaves the Resources down to the user.
the json is as follows:
{
"TABS": [
{
"langName" : "Example Tab",
"unlocalizedName" : "tabExample",
"icon" : ""
}
],
"BLOCKS": [
{
"langName" : "Example Block",
"unlocalizedName": "exampleBlock",
"registryName" : "example_block",
"tabIndex" : 0,
"hardness" : 1.5,
"soundType" : "STONE",
"material" : "ROCK"
}
],
"ITEMS": [
{
"langName" : "Example Item",
"unlocalizedName": "exampleItem",
"registryName" : "example_item",
"tabIndex" : 0,
"maxStackSize" : 16
}
]
And this is the Zip file structure (should they choose to use it)
`biar.json` is the aforementioned json file
.minecraft/
|
|__ biarmod/
|
|__ biarmod.zip
|
|__biar.json
|
|__textures/
|
|__items/
| |
| |__example_item.png
|
|__blocks/
|
|__ example_block.png
The idea of option 1 is a one size fits all solution for mod pack developers who just want blocks & items with one texture who may not have the know-how to create a full ResourcePack.zip
And my vision down the line, is to have a comunity repo for "block-packs" or "item-packs" so users can download a set of blocks and items made by the community.
The main push for this idea came from a modpack developer i know who wanted me to add a bunch of items to the pack - they were just used for crafting recipes and noting more. That gave me the idea to create this.