Alpvax

Why? What are you trying to achieve? I'm fairly sure your mod is already a resource pack, the only thing is that you can't disable it in the GUI.

It sounds like there is a difference between the NBT data of the different stacks. You should be able to use the vanilla /data command: https://minecraft.gamepedia.com/Commands/data to find any differences. It might be a bit of work trawling through the data (I would recommend only having the 2 stacks in an empty inventory).

Please don't use a white font. Not all of us use a dark theme, and it looked like a blank post at first.

Maybe post an image during the day so the armour can actually be seen? Also, we will need your rendering code to be able to debug it.

I would rather not use "decorative_blocks" because that doesn't really say what they are, and people may start adding other "decorative" blocks into the tag. Maybe "small_storage_blocks" or "storage_blocks_2x2" or something similar would be better. As for the actual blocks, there are more than just quartz and copper which would fall into the 2x2 tag: Glowstone Clay Snow Honeycomb Honey (reversible, but requires 4 glass bottles) Magma Cream Quartz Copper (reversible, but I think only if the block isn't weathered?) Amethyst

You're missing part of the item name in 6 of the last 7 entries in your loot table

You're trying to create a new instance, but not calling a constructor. Get rid of the "new" keyword.

Is this now preferred to using ObjectHolder? Or has this approach superceded ObjectHolder?

There are 3 methods which sound like they do something very similar, overridden by various different blocks: updatePostPlacement is used to make connections with adjacent blocks (fences/walls). /** * Update the provided state given the provided neighbor facing and neighbor state, returning a new state. * For example, fences make their connections to the passed in state if possible, and wet concrete powder immediately * returns its solidified counterpart. * Note that this method should ideally consider only the specific face passed in. */ public BlockState updatePostPlacemen

You've commented out the event listener (ModelBakeEvent) which actually instantiates your custom model (in BlocksMod.java).

Check out TheGreyGhost's MBE04: Dynamic_block_models. It does almost exactly what you want (make sure you understand, not just copy-paste).

That is the only way. All blockstates are calculated on registration, so there is no way to save that to a single blockstate. If there are that many, you may need to rethink your approach. You could maybe store a chunk capability with a map of blockpos -> blockstate, but I'm not sure that would save you much (after all, that is what the world saves). And you'd have a much harder time sorting out the rendering.

I'm assuming big-endian. But TBH, I thought the byte order was part of the UTF-8 spec. I've never seen it called UTF-8 BE.

You could try looking at how the vanilla /fill command does it. I'm not sure how optimised it is.

Should probably be a new topic, as it's a different issue. I believe it is the same as the undyed version. The dye is saved in the NBT.