Renaming Bug:
Replication Steps:
1: /give @p command_block_minecart 1 0
2: place anvil down and rename it "TEST"
3: place on track and type in a command ("/say hi" for example)
4: when we do "/tp @e[name=TEST] @p", it will work!
5: Now break the minecart. It is named "TEST".
6: put another "TEST" on the rail
7: save and exit world. and then reload world.
8: try same command "/tp @e[name=TEST] @p", it will NOT work!
9: the name disappeared.
Still in creative mode, left click the commandblockminecart to destroy it. IT WILL DROP AN ITEM! any other minecart WON'T!
AND it is named "@"
10: But when we do "/summon MinecartCommandBlock ~ ~ ~ {CustomName:"TEST"}" IT WILL KEEP THE NAME!
little summary:
1: Renamed commandblockminecarts in anvil, when broken, will drop minecart WITH the name given to it (Pre: "TEST", Post: "TEST").
2: Renamed commandblockminecarts in anvil, when broken AFTER RELOADING WORLD, will drop minecart WITHOUT the name given to it (Pre: "TEST", Post: "@")
3: Summoned named commandblockminecarts, when broken, will drop minecart WITH the name given to it regardless if the world is reloaded or not. (Pre: "TEST", Post: "TEST").
EDIT 4: Renamed CommandBlockMinecarts DROP ITEM in CREATIVE. which it shouldn't!
I hope this will be fixed soon so that command_block_minecarts always remain their names!!!
I tried to explain it as best as I can, here are some screenshots aswell!
Related issues
Attachments
Comments


Confirmed for 14w21b
Maybe relates somehow to: MC-32701
Blah please stop linking issue reports that aren't duplicates
First read the discription before commenting please
indeed, Blah, I'm tired that you imedietly say things without reading the discription first, it's like you only look at the title/screenshots
Edit:
well it is almost always like you don't

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.