Render
BlockView-extending interface to be used by net.fabricmc.fabric.api.renderer.v1.model.FabricBakedModel for dynamic model customization. It ensures thread safety and exploits data cached in render chunks for performance and data consistency.
There are differences from BlockView consumers must understand:
BlockEntity implementations that provide data for model customization should implement RenderAttachmentBlockEntity which will be queried on the main thread when a render chunk is enqueued for rebuild. The model should retrieve the results via getBlockEntityRenderAttachment. While getBlockEntity is not disabled, it is not thread-safe for use on render threads. Models that violate this guidance are responsible for any necessary synchronization or collision detection.
getBlockState and getFluidState will always reflect the state cached with the render chunk. Block and fluid states can thus be different from main-thread world state due to lag between block update application from network packets and render chunk rebuilds. Use of {link #getCachedRenderData()} will ensure consistency of model state with the rest of the chunk being rendered.
Models should avoid using getBlockEntity to ensure thread safety because this view may be accessed outside the main client thread. Models that require Block Entity data should implement RenderAttachmentBlockEntity and then use getBlockEntityRenderAttachment to retrieve it. When called from the main thread, that method will simply retrieve the data directly.
This interface is only guaranteed to be present in the client environment.