Spyeedy

Possibly, but the thing is, in the onBlockPlacedBy method, I printed the stack's NBT list count, it returns 0, despite that the item does have content inside the list, hmm https://gist.github.com/Spyeedy/104a892bd3970d189aaf42a10f8645d7#file-lightswitchblock-java-L33

Possibly, but the thing is, in the onBlockPlacedBy method, I printed the stack's NBT list count, it returns 0, despite that the item does have content inside the list, hmm https://gist.github.com/Spyeedy/104a892bd3970d189aaf42a10f8645d7#file-lightswitchblock-java-L33

I've fixed that typo, and I've added a print statement in my Block's onBlockPlacedBy to look at the nbt list's size, weirdly enough, it prints out 0, even though in the item's nbt list, it has contents. As well as set the tag compound back into the ItemStack's NBT, just to be extremely sure the Item has the new NBT Updated the gist: https://gist.github.com/Spyeedy/104a892bd3970d189aaf42a10f8645d7

Well, that first line is part of a commented out block, but hmm, I ain't putting the list tag into the BlockEntityTag since I commented out the code inside Block#onBlockPlacedBy, I'll try uncommenting inside onBlockPlacedBy and fixing that typo

As the title says, my ItemStack's NBT tags aren't getting transferred to my Block's TileEntity NBT. This worked back on 1.12.2, so I'm not sure why it isn't working now. In the gist linked below are the Item, Block and TileEntity classes. https://gist.github.com/Spyeedy/104a892bd3970d189aaf42a10f8645d7 Thanks for responding :)

Looking at Minecraft's widgets for scrolling list, I've found ExtendedList which extends AbstractList. The latter of which handles all the logic for scrolling, etc. I looked into AbstractList and discovered that render renders the dirt background as well, which I don't want. I only want the ability to scroll, scroll bar and hiding other content that is out-of-view. With this, will I have to make my own widget for scrolling list? If not, then what other alternatives are there provided by Forge or Minecraft that I've not found?

Thanks, I'll look into that

So I understand that ContainerScreen are registered with a ContainerType through ScreenManager.registerFactory. But what about client-only screen, meaning only the GUI itself, do I need to have any registration? How will I open them? I'm not too sure.

ahh okay, thanks

Your earlier link relates to 1.15, this one is for 1.13/1.14, which I'm not developing for. But thanks for helping, or rather, mentioning that 1.15 no longer has forge blockstates

awwww, this is going to suck a lot . Well then, they should've removed the Forge Blockstate JSON section from the docs

No, the console doesn't seem to be complaining about the textures, even though there is the purple-black-checkered texture all over my model. As for my model, it's as follow, I didn't define any textures in my model as I wanted to apply the textures in the blockstate file, as I had other blocks registered that used the same model but different set of textures.

I'm using forge blockstates, and the file is as follows. (Please ignore that I used the same model for all the variants) I'm not too sure why my textures set in the default section is not applied to the model. The texture path is correct.

Updated title to put "solved" in

I managed to solve it after a week or so of racking my brain for a solution. I had a thought, why not modify the vertex data of the BakedQuad itself and change the numbers myself. I didn't know how to modify the vertex data, so I did some googling and it pointed me to this thread. Which in turn lead me to this chunk of code here. That's where I got stuck (yes, my mind was too fixated on that chunk of code to actually post an update here). So I printed the float array provided by IVertexConsumer#put and I was scratching my head over the set of floats it was giving me, then today, it hit me, those were coordinates, specifically translation coordinates for Minecraft to draw a quad. That's when I did some math (multiplication by 16) with the coordinates to determine which coordinate affect the 3 axes of a model, X Y Z. And then, I came to my solution here. I just took the data