372
edits
Changes
Copy Block Entity Renderer to MC1.16 archive
A <code>TileEntityRenderer</code> or <code>TER</code> is used to render blocks in a way that cannot be represented with a static baked model (JSON, OBJ, B3D, etc.). A tile entity renderer requires the block to have a TileEntity.
== Creating a TER ==
To create a TER, create a class that inherits from <code>TileEntityRenderer</code>. It takes a generic argument specifying the block's TileEntity class. The generic argument is used in the TER's <code>render</code> method.
Only one TER exists for a given tile entity. Therefore, values that are specific to a single instance in the world should be stored in the tile entity being passed to the renderer rather than in the TER itself. For example, an integer that increments every frame, if stored in the TER, will increment every frame for every tile entity of this type in the world.
=== <code> render </code> ===
This method is called every frame in order to render the tile entity.
=== Parameters ===
* <code>tileentityIn</code>: This is the instance of the tile entity being rendered.
* <code>partialTicks</code>: The amount of time, in fractions of a tick, that has passed since the last full tick.
* <code>matrixStackIn</code>: A stack holding four-dimensional matrix entries offset to the current position of the tile entity.
* <code>bufferIn</code>: A rendering buffer able to access a vertex builder.
* <code>combinedLightIn</code>: An integer of the current light value on the tile entity.
* <code>combinedOverlayIn</code>: An integer set to the current overlay of the tile entity, usually <code>OverlayTexture#NO_OVERLAY</code> or 655,360.
== Registering a TER ==
In order to register a TER, call <code>ClientRegistry#bindTileEntityRenderer</code> passing the tile entity class to be renderer with this TER and the instance of the TER to use to render all TEs of this class.
== Creating a TER ==
To create a TER, create a class that inherits from <code>TileEntityRenderer</code>. It takes a generic argument specifying the block's TileEntity class. The generic argument is used in the TER's <code>render</code> method.
Only one TER exists for a given tile entity. Therefore, values that are specific to a single instance in the world should be stored in the tile entity being passed to the renderer rather than in the TER itself. For example, an integer that increments every frame, if stored in the TER, will increment every frame for every tile entity of this type in the world.
=== <code> render </code> ===
This method is called every frame in order to render the tile entity.
=== Parameters ===
* <code>tileentityIn</code>: This is the instance of the tile entity being rendered.
* <code>partialTicks</code>: The amount of time, in fractions of a tick, that has passed since the last full tick.
* <code>matrixStackIn</code>: A stack holding four-dimensional matrix entries offset to the current position of the tile entity.
* <code>bufferIn</code>: A rendering buffer able to access a vertex builder.
* <code>combinedLightIn</code>: An integer of the current light value on the tile entity.
* <code>combinedOverlayIn</code>: An integer set to the current overlay of the tile entity, usually <code>OverlayTexture#NO_OVERLAY</code> or 655,360.
== Registering a TER ==
In order to register a TER, call <code>ClientRegistry#bindTileEntityRenderer</code> passing the tile entity class to be renderer with this TER and the instance of the TER to use to render all TEs of this class.