Re: MC-57516 - The CustomNameVisible tag was removed from the entities it served the most use for.
This made the flag almost 100% useless. The community requests that the feature be returned as a way to override the new 1.8 behaviour and let the setting control if the name should be visible or not.
It makes logical sense, that if the flag saying to make the custom name visible, to actually make the custom name visible...
It should not matter that the underlying code was changed, the code should be updated to support this flag the way it worked before as it was a supported feature.
A supported feature should not be removed without a good reason, and we do not see a reason provided here.
Linked issues
is duplicated by 1
relates to 1
Comments 5
Sonic, thats the point. Asking to reverse that statement.
If we just accept everything Mojang says, and never ask for it to be the way we would prefer it, how would the game be made better for us?
Don't just accept a bad answer as the final word, push for it to be fixed 🙂
Or the Minecraft Forums 🙂
This issue should be reopened. Closing an issue (that is clearly an issue, because it worked before) as "not a bug" is not corrent, moreover without even giving a proper reason. Is Mojang still planning a plugin API? Because that's not how to do it. You should not ignore an issue just because it doesn't affect vanilla.
Still not a bug per Mojang:
[~searge] wrote:
Thus, its still MC-57516