Minecraft Forums

Changes in 16w20a:

Additions

assets/minecraft

• blockstates
• bone_block.json
• magma.json
• nether_wart_block.json
• red_nether_brick.json
• structure_void.json


• models
• block
• bone_block.json
• magma.json
• nether_wart_block.json
• red_nether_brick.json
• structure_void.json


• item
• bone_block.json
• magma.json
• nether_wart_block.json
• red_nether_brick.json
• structure_void.json




• textures
• block
• bone_block_side.png
• bone_block_top.png - used in a structure I think
• magma.png - new nether block
• nether_wart_block.png - decorative, craftible
• red_nether_brick.png - decorative, craftible


• entity
• bear/polarbear.png - new mob
• skeleton
• stray.png - new variant
• stray_overlay.png


• zombie/husk.png - new variant


• items
• structure_void.png

Changes

assets/minecraft

• lang/en_US.lang
• textures/blocks
• structure_block.png - texture changed, all variants

Quote from Tepig4444»

I have the same issue, so I did what you said and the launcher said this:

"[07:53:46] [Client thread/ERROR]: Unable to parse metadata from minecraft:textures/blocks/prismarine_rough.png"

BTW: Im using the versticraft pack

Quote from rmfranco»

Can someone please give me a link to this thread? It took me 2 days to re-find this thread. I wasn't able to find it in my History.

Quote from rmfranco»

Hello. First, I've posted what I'm looking for elsewhere, so, to save typing time, here's the link to it:

http://voxmc.com/forum/showthread.php?t=8588&p=53450#post53450

If you don't want to follow the link of someone you don't know, you can reach it by googling Vox populi minecraft, it's in the forums, under What's new, with the title Pack jsons? Help with resource pack, please.

I've made a pack for my personal use, taking parts I like from different packs, and putting them into mine. I have most of what I want, but still would like "random" passive mobs. I've never used jsons before, but I think it's what would be able to help me. At the least, direct me to someone's pack who has a json for passive mob textures, & I'll work with what I can.

Thanks for any help.

Edit: I just realize, I've posted on here before, probably about the same thing, though I'm too lazy to find it right now.

Quote from Meringue»

Hey, i have a little of a hard time figuring out the durability stuff:

Say i want to add 2 sword textures – one for a used, slightly worn sword, maybe for 50% durability and less, and another texture for a heavily damaged sword used from 10% durability until it breaks:

{"predicate": {"damage": 0.5},"model": "item/sword_stillgoodenough"},

{"predicate": {"damage": 0.9},"model": "item/sword_timetogetanewone"}

Would this work, or would the textures only be applied at exactly 50% and 90% damage?

Quote from riodroid»

so, after going through this tutorial, i added lots of textures, but i had problems with rotation orientated blocks (logs & pillars)

i figured that you can give a different model to each rotation, then i found this on the web (dunno where, i forgot)

{
"variants": {
"axis=y": { "model": "oak_log" },
"axis=z": { "model": "oak_log", "x": 90 },
"axis=x": { "model": "oak_log", "x": 90, "y": 90 },
"axis=none": { "model": "oak_bark" }
}
}

the problem is that i cant randomise the texture/model.

i cant even randomise rotation.

any idea how to make this work?

Yep, provided the two cubes on the model have the same dimensions, it will simply overlay the bottom most element on the upper one without z-fighting.You would just need an element with just a top face to place on top. (note that the cullfaces will also affect the ordering, so no CTM uses for this, if you keep them the same you shouldn't have issues)

Quote from robloxianroblox»

I'm still having issues with this, I can't for the life of my figure out how to fix it, nor what you mean. (No, It's not my model, I didn't make it.) I'd really appreciate if someone could tell me what's wrong with it, so I can fix it, or you can fix it for me. Here's the json code.

{
"__comment": "Fair warning, this format is highly likely to change even more in the future!",
"ambientocclusion": false,
"textures": {
"particle": "blocks/dirt",
"grass": "blocks/better_grass_0",
"grass_side": "blocks/better_grass_side_1",
"better_grass_sides": "blocks/better_grass_sides",
"bottom": "blocks/dirt",
"top": "blocks/grass_top",
"texture": "blocks/stone_andesite_smooth"
},
"elements": [
{
"__comment": "Center",
"from": [ 0, 0, 0 ],
"to": [ 16, 16, 16 ],
"faces": {
"down": { "uv": [ 0, 0, 16, 16 ], "texture": "#bottom", "cullface": "down" },
"up": { "uv": [ 0, 0, 16, 16 ], "texture": "#top", "tintindex": 0, "cullface": "up" },
"north": { "uv": [ 0, 0, 16, 16 ], "texture": "#bottom", "cullface": "north" },
"south": { "uv": [ 0, 0, 16, 16 ], "texture": "#bottom", "cullface": "south" },
"west": { "uv": [ 0, 0, 16, 16 ], "texture": "#bottom", "cullface": "west" },
"east": { "uv": [ 0, 0, 16, 16 ], "texture": "#bottom", "cullface": "east" }
}
},
{
"from": [ 16, 0, 0 ],
"to": [ 16, 16, 16 ],
"rotation": { "origin": [ 16, 16, 0 ], "axis": "z", "angle": 22.5 },
"faces": {
"east": { "uv": [ 0, 0, 16, 16 ], "texture": "#better_grass_sides", "tintindex": 0, "cullface": "east" }
}
},
{
"from": [ 0, 0, 0 ],
"to": [ 0, 16, 16 ],
"rotation": { "origin": [ 0, 16, 0 ], "axis": "z", "angle": -22.5 },
"faces": {
"west": { "uv": [ 0, 0, 16, 16 ], "texture": "#better_grass_sides", "tintindex": 0, "cullface": "west" }
}
},
{
"from": [ 0, 0, 16 ],
"to": [ 16, 16, 16 ],
"rotation": { "origin": [ 0, 16, 16 ], "axis": "x", "angle": -22.5 },
"faces": {
"south": { "uv": [ 0, 0, 16, 16 ], "texture": "#better_grass_sides", "tintindex": 0, "cullface": "south" }
}
},
{
"from": [ 0, 0, 0 ],
"to": [ 16, 16, 0 ],
"rotation": { "origin": [ 0, 16, 0 ], "axis": "x", "angle": 22.5 },
"faces": {
"north": { "uv": [ 0, 0, 16, 16 ], "texture": "#better_grass_sides", "tintindex": 0, "cullface": "north" }
}
},
{
"__comment": "CenterOverlay",
"from": [ -0.01, 0, -0.01 ],
"to": [ 16.01, 16, 16.01 ],
"faces": {
"north": { "uv": [ 0, 0, 16, 16 ], "texture": "#grass_side", "tintindex": 0, "cullface": "north" },
"south": { "uv": [ 0, 0, 16, 16 ], "texture": "#grass_side", "tintindex": 0, "cullface": "south" },
"west": { "uv": [ 0, 0, 16, 16 ], "texture": "#grass_side", "tintindex": 0, "cullface": "west" },
"east": { "uv": [ 0, 0, 16, 16 ], "texture": "#grass_side", "tintindex": 0, "cullface": "east" }
}
}
]
}

Quote from neoix»

Good point, but isn't the converter tool still around?

Quote from insomniac_lemon»

Yeah uhhh, sort of, although it's going to be quite overcomplicated and more resource heavy than it should be. And to be honest, you probably won't want to do it.

TL;DR is that you have to disable the tint on your models and make separate models for lit and unlit. It's not as simple as tweaking the recolor value that is applied to it. Because no recolor values aside from biomes (and even then that's not great, still hardcoded stuff) are tweakable yet, it's either on or off.

Further on the technical side, the '1.8' style blockstate format will not recognize the addition of the power argument. This means you need to use multipart arguments to give each power level its own model (or in this case, the same model but with a different texture, but really it's still another json file you need because the devs have a philosophical rulebook on how blockstate files should and shouldn't work) in order to replicate the power level shading of the redstone that's usually done with tint.

Even with multipart system of 9 parts (4 arms, 4 up arms, 1 center... this is no personalization and no optimization by having dedicated models for specific states to have less mesh), it gets to the point this is a really bad idea. Take the original things you need (blockstate lines, model files, textures)... and multiply that by F I F T E E N. That's right.

Fif.

Teen.

Sixteen, there is also an off state.

I really wish some of those hardcoded colors would just get added to resource packs, though since I have been hanging out with people in the Modded Minecraft community I know that there would be complaints from that side as modders would have to change the way they do things (on the bright side, that did not stop block models from being added, and resource packs in any case are more official than mods).

Quote from insomniac_lemon»

And the fun don't stop there kiddies, as per Grum's comment on MC-60242, it's even possible that using multipart in the manner will be broken in the future:

From the looks of it, Mojang wants states to only be things that should affect rendering, as I assume having more states takes more memory. Unfortunately, they seem to be limiting that to things that affect rendering in vanilla, which limits a lot of what resource packs can do. Hopefully a few of the unused states will be kept for resource pack authors though.

Quote from Ignaf»

@Eleazzaar: Yes I see now, you helped a lot. Thanks

@Lemon: Yes they are Huge in my hand and flat in the inventory. The rest works well. But sorry I don't understand, they are normal sice?

With most blocks you can fix this by removing any display tags in the relevant item model, and setting the block model to have the parent of "block/block" (though some like carpets you might want a different parent, I have a full list of new models here), as that is where all the default block display tags are stored

At last, the long awaited

Changes from 1.8.9 to 1.9-pre2

Note that in the below:

• * is a wildcard for when a bunch of similar files all exist, such as the colors of stained glass panes
• square brackets with numbers mean a file for each number in the range ([])
• "-" to the end of the line is a comment
• items can now be placed on the head using commands, as item models and block models were unified in the code
• see the Minecraft Wiki article for a few of the model additions, most notably multipart and overrides

Additions

• assets/minecraft/loot_tables/* - see the Minecraft Wiki article, not a resource pack feature

• assets/minecraft/structures/* - the new way to store structure data related to the structure block, not a resource pack feature

Changes

• pack.mcmeta - now requires a pack_format number of "2", as opposed to "1" which was required since 1.8.8 (the tag was ignored before then)

• assets/minecraft/lang/en_US.lang - many changes, only notable ones listed below. I suggest using a online diff program/Notepad++'s compare plugin to see more changes if interested
• Streaming stuff removed as the feature was as well
• Boat renamed to Oak Boat
• Potions and status effects completely redone, including removing unused potion prefixes
• Added subtitles, you might want to look through these if you use custom lang anywhere else

• assets/minecraft/texts/splashes.txt
• Added "More Digital!", "doot doot", "Falling with style!", "There's no stopping the Trollmaso", and "Throw yourself at the ground and miss"
• "0% sugar" changed to "1% sugar"
• Removed "SOPA means LOSER in Swedish!"

Removals

Edit: added changes to brewing stand gui

Quote from Alvoria»

Now that the 1.9 pre-release has come out, would one of you wonderful people mind creating a 1.8 > 1.9 list for those of us who are lagging behind on these changes? Thank you in advance.

I can try to get something together tomorrow if no one does it by then. I won't be able to get much done tonight, as there are quite a few changes, and to delay things even further it seems that 1.9-pre1 recent version was compiled by a Unix system instead of a Windows like 1.8.9, and my diff program refuses to ignore that fact when listing changed files.

Edit: okay, I convinced it to ignore the Windows/Unix line break difference. A list of changes besides line break type should be coming sometime tomorrow. Until then, here is a raw list of changes

Edit 2: I have been busier than I originally expected on Thursday, so I only finished about a third of the list so far. I'll hopefully have the full list ready to post sometime on Friday

Quote from HuntersPlays»

Can you tell me what the glowing redstone ore files are called in the folders?

Quote from HuntersPlays»

Greetings from 2016, 2015 posters. I have an issue and I would like some help with it:

I have four alternate textures for the quartz ore, but as you can see one of them has gone rogue. I can't figure out what's wrong with it, the .json files seem fine to me:

Block States (resourcepack/assets/minecraft/blockstates)

"quartz_ore"

{
"variants": {
"normal": [ { "model": "quartz_ore", "weight": 5 },
{ "model": "quartz_ore_1", "weight": 2 },
{ "model": "quartz_ore_2", "weight": 2 },
{ "model": "quartz_ore_3", "weight": 2 },
{ "model": "quartz_ore_4", "weight": 2 }
]
}
}

Models (resourcepack/assets/minecraft/models/block)

"quartz_ore_1" (the one with the issue)

{
"parent": "block/cube_all",
"textures": {
"all": "blocks/quartz_ore_1"
}
}

"quartz_ore_2"

{
"parent": "block/cube_all",
"textures": {
"all": "blocks/quartz_ore_2"
}
}

"quartz_ore_3"

{
"parent": "block/cube_all",
"textures": {
"all": "blocks/quartz_ore_3"
}
}

"quartz_block_4"

{
"parent": "block/cube_all",
"textures": {
"all": "blocks/quartz_ore_4"
}
}

Extra thing: My redstone ore alternate textures work (all four of them) but when I try to mine it, step on it or put a block next to it (that's when it glows) it changes to the original texture set by the resource pack (no matter what alternate version was being displayed). Is there any way of changing that so it stays with the alternate version even when it glows?

Thanks anyways.