End Crystal shows its hitbox positioned at its BeamTarget coords if there is no Dragon
The bug
If an end crystal has a BeamTarget set, its hitbox (when shown with F3+B) will render at the location of the BeamTarget instead of the location where the crystal actually is at.
Video
Code analysis
Code analysis by chenyuxuan can be found in this comment.
- Unresolved
FACS01- 15
- 7
- Confirmed
- Debug Rendering
- end_crystal hitbox
1.15.2 - 1.20.4
1.15.2 20w10a 20w11a 20w12a 20w13a 20w14a 20w15a 20w16a 20w17a 20w18a 20w20a 20w21a 20w22a 1.16-pre1 1.16-pre3 1.16-pre5 1.16-pre6 1.16-pre7 1.16-pre8 1.16-rc1 1.16 1.16.1 20w27a 20w28a 20w29a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2 1.16.3 1.16.4-pre2 1.16.4-rc1 1.16.4 20w45a 20w46a 20w48a 20w49a 20w51a 21w03a 21w05b 21w07a 21w10a 21w11a 1.17 1.17.1-pre1 1.17.1 1.18.2 22w11a 22w15a 1.19-pre1 1.19.1-pre1 1.19.2 23w03a 1.20.2 23w46a 1.20.4
Created Issue:
End Crystal shows its hitbox positioned at its BeamTarget coords if there is no Dragon
video attached!
Relates to
MC-173980.
relates to
The bug
If an end crystal has a BeamTarget set, its hitbox (when shown with F3+B) will render at the location of the BeamTarget instead of the location where the crystal actually is at.
Video
Code analysis
Code analysis by chenyuxuan can be found in this comment.
Forwards-resolved towards MC-174356.
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 BeamTarget near 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}}
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
they did not use pushPose&popPose before&after here.
maybe MC-174356 is because of it too?

Affects 1.15.2 as well.
Can confirm in 1.17.1.
Can confirm in 22w15a. This also seems to move its shadow to the target coordinates as well.
i think that is because of a typo in client\net\minecraft\client\renderer\entity\EndCrystalRenderer
they did not use pushPose&popPose before&after here.
maybe MC-200563 is because of it too?
Can confirm in 23w03a