As to CBers, AreaEffectCloud(AEC) now can be used as "marker" to mark the coordinates of important command blocks, while I found an issue about AEC with CustomNameVisible:1. When it's teleported to other place, it's display name doesn't follow. Only when re-display the name will it be at the right place.
Steps to reproduce:
·Run the following commands one by one.
/summon AreaEffectCloud ~ ~ ~ {Duration:2000000000,CustomName:"aec"}/entitydata @e[name=aec,type=AreaEffectCloud] {CustomNameVisible:1}/tp @e[name=aec,type=AreaEffectCloud] ~5 ~ ~notice that the name didn't move -----
/entitydata @e[name=aec,type=AreaEffectCloud] {CustomNameVisible:0}/entitydata @e[name=aec,type=AreaEffectCloud] {CustomNameVisible:1}notice that the name display at the right place -----
Run this command to kill the marker:
/kill @e[name=aec,type=AreaEffectCloud]What I expect is when an AEC marker was teleported, it's display name should follow the entity, instead of just keep staying there.
Hope you can fix it.
Linked issues
Comments
mrpingouin1
mrpingouin1
I still maintain that this is a duplicate of MC-90954 :
The problem comes from the entity position not being send to the client. At any point the custom name and the particles are at a different position. Use this command instead of the first one provided.
/summon AreaEffectCloud ~ ~1 ~ {Radius:0.5f,Duration:2147483647,Particle:"flame",CustomName:aec}The fact that the entity position is corrected when CustomNameVisible is switched is still not directly related to the CustomName. We can just change some other data to force the server to send the new data of the entity, and thus correct his position.
/entitydata @e[name=aec,type=AreaEffectCloud] {Air:1}
Duplicate of MC-90954