Custom blocks using server component-driven rendering (e.g., minecraft:geometry and minecraft:material_instances) do not apply MER across all forms of the block model. These forms have been observed to include:

• Held item (1st and 3rd person)

• Item entity

• Item frame mounts

• Shelf mounts

The minecraft:item_visual component cannot be used to work around this issue.

Demonstration

The screenshots demonstrate this issue using item frames, item entities, placed blocks, held blocks, and a flower pot (only allowed for component-driven form). Both examples are of custom blocks that point to the same fully white texture with maximum emissivity. The one whose handheld item form glows uses client-driven rendering. Its textures are bound via blocks.json. This has the correct behavior, even causing the block model to glow in an item frame and as an item entity. The other uses component-driven rendering. Its handheld, item entity, and item frame models are not glowing when they all should be.

Interestingly, the embedded visual form of the component-rendered custom block (in the flower pot) works fine.

Reproduction

This issue affects all custom blocks in Vibrant Visuals using component-driven rendering.

The demo videos and code are taken from the behavior pack in the attached world for convenience. This world can be opened (in Minecraft Preview) for inspection or unzipped to access the code associated with such. If testing these separately, ensure it is dark and Vibrant Visuals graphics are enabled in settings.