Jump to content

Do tile entities need a ItemBlock and a .json file to have its texture be shown in the inventory?


Recommended Posts

Posted (edited)

i have a tile entity that looks like a shulker, its texture works when placed to the ground, but they appear purple and black(somethings missing) in the inventory, plus when you break them they use these white particles that looks like white enchantment letters not what youd expect because my tile entity is ender pearl green. so do these tile entities .json in assets file like regular blocks? if so what  do i put i there to make it use the block texture, most blocks i made have no itemblocks in it. It is based on the shulker code btw. even uses the same model from shulkers with animations.

 

ItemBlock: https://pastebin.com/yT6PtYh7

block: https://pastebin.com/UPKzfzDQ

tileentity: https://pastebin.com/c9bq9zFE

Edited by TheRPGAdventurer
Posted
On 4/21/2019 at 8:26 PM, diesieben07 said:

 

  • Items always require a json model, regardless of if they are an ItemBlock or not. There is a hack that can be done to make them render "in code", similar to a TESR, use Item#setTileEntityItemStackRenderer with a custom TileEntityItemStackRenderer implementation for that.

Im assuming this hack is used so you dont have to use a .json block model?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.