Related to MC-174356
Steps to reproduce
Go to 0 100 0 (in any dimension)
Summon an end crystal and name it, or use this command
/summon end_crystal ~ ~ ~ {CustomNameVisible:1b,CustomName:' {"text":"Custom Name"}'}Give it a
BeamTargetnear by/data merge entity @e[type=minecraft:end_crystal,limit=1,sort=nearest] {BeamTarget:{X:5,Y:100,Z:5}}The CustomName appears at its BeamTarget coords
Also happens if the summoned end crystal has the BeamTarget included in the command
/summon end_crystal ~ ~ ~ {CustomNameVisible:1b,CustomName:'{"text":"Custom Name"}',BeamTarget:{X:5,Y:100,Z:5}}[media]
Linked issues
relates to 1
Attachments
Comments 14
maybe you need to use CustomNameVisible:1b to make it work. and don't know if "Custom Name" works, I always write it like in json format just in case
Setting true is an allias for 1b, and adding the quotes around the key makes no difference and is only needed for keys that have non [A-Za-z0-0_-] names
I was trying to recreate the issue (and I can), and I've found that the custom name is being displayed over the entities' hitbox (press F3+B).
Because of this, it looks like this may be caused by MC-174356.
i think that is because of a typo in client\net\minecraft\client\renderer\entity\EndCrystalRenderer
[media]
they did not use pushPose&popPose before&after here.
maybe MC-174356 is because of it too?
Interesting. I tried the command /summon end_crystal ~ ~ ~ {CustomName:"Custom Name",CustomNameVisible:true,BeamTarget:{X:0,Y:70,Z:0}} and the shadow appeared at the beam target, but the custom name didn't appear at all.