[1.10.2] Only render block if player holds a specified item

[Fubar]

Hello there.

 

I'm currently trying to render a block invisible unless the player holds a specified item - for example an apple.

As long as the player is holding said item the block will be visible for that player.

It's a simple block and has no entity.

It could also be used as a building block which means you could have many of them at once in the same chunk.

 

I tried overriding render methods in the block class like shouldSideBeRendered and returned true/false depending on the held item, but since those methods get only called after a block update/placement they are not suitable for my situation.

 

So my guess is I need to register my own render type and return it in the getRenderType method ?

 

I'm a bit lost here and would like someone to point me in the right direction on how to implement that.

 

Thank you for your time.

[Animefan8888]

You could override getActualState(...) then return the state that is not visible on the server, and if it is client side use Minecratf.getMinecraft().thePlayer to check if the client side player is holding the item and if so switch the blockstate to the visible one only client side. This will work I assume unless you plan on changing something other than the rending of the block, if you need some psuedocode ask.

[Choonster]

I implemented this here using a per-tick check to see if the player's held item reveals hidden blocks (using a capability) and re-rendering chunks containing hidden blocks when the player starts or stops revealing them. This is based on the code that allows EnderIO's Yeta Wrench to hide Conduit Facades.

 

I had to use a ticking

TileEntity

, but I tried to keep it as lean as possible.

 

There was a small FPS drop when starting or stopping the revealing due to the chunks re-rendering, but FPS seemed stable once the chunks had been rendered.

 

This may or may not be as performant as the

TextureAtlasSprite

method suggested by diesieben07.

[Draco18s]

I'd use the TextureAtlasSprite method.  They're real easy to use, unless you're doing crazy shit like trying to generate a runtime texture.  Just go look at the TextureAtlasSpriteClock and TextureAtlasSpriteCompas classes.  What they do is override

updateAnimation

, look at player/world information, and determine which frame of the animation should be used and update it.  Dirt simple.

 

The hard part is letting Minecraft know there's a custom TextureAtlasSprite class involved (you may have to dig around in the compass/clock item classes and related code; I haven't done this for 1.10 yet).

[Egietje]

U can take a look at the code of the barrier block and learn how it is done the vanilla way

[Draco18s]

Just go look at the TextureAtlasSpriteClock and TextureAtlasSpriteCompas classes.

These don't actually exist anymore, the item override mechanic is used instead of the hardcoded texture classes.

 

Ah, thanks diesieben07.

I think I'd glimpsed that, but didn't look very far into it. Also, away from my dev environ.

[Draco18s]

Right, just that vanilla isn't a reference point any more.