Custom blocks that do not declare the geometry and material instances components fall back to the legacy means of using blocks.json to determine their appearance. Blocks doing so may declare the minecraft:flower_pottable component. However, these blocks are not rendered in the flower pot; they are invisible.

Workaround difficult

A workaround exists for this bug using server-rendering with minecraft:geometry.full_block. However, this model does not match blocks.json UV mapping and also implies other hardcoded features, such as ambient occlusion casting. As such, it’s still often desirable to use the legacy blocks.json rendering method.

In principle, the client-based rendering could be used only for core rendering while the potted form could use embedded rendering. However, minecraft:embedded_visual is incompatible with client-based rendering.

Considering this web of issues/limitations, any of the following would be desired/expected:

• Allowing the embedded visuals component to work with client-based rendering

• Rendering a cube matching blocks.json UV mapping in the flower pot

• Emitting a content log error indicating that minecraft:flower_pottable requires the geometry and material instances components.

Demonstration

Below is a custom pottable block using the geometry and material instances components:

Here is a matching block but without the geometry and material instances components:

Indeed, the block is inside the flower pot. Stack count is decremented on usage and returned on an additional interaction.

Reproduction

This bug can be trivially reproduced with the following code:

{
	"format_version": "1.26.0",
	"minecraft:block": {
		"description": {"identifier": "bug_pottability:custom_block_with_client_rendering"},
		
		"components": {
			"minecraft:flower_pottable": {}
		}
	}
}

This example is taken from the behavior pack in the following world attached for convenience:

This world can be opened for inspection or unzipped to access the code associated with such. Also included is a demonstration of the same behavior but using server-based rendering.