-
Bug
-
Resolution: Invalid
-
None
-
Minecraft 16w36a
-
None
-
Win10Pro, i7-4770 @3.4GHz, GeForce GTX 680, Java 8-91
-
Unconfirmed
Now that things like chests can have custom names, I tried naming a beacon. It CAN be named, and when it's placed, then picked up, the name sticks with it. But when I run: testforblock x y z minecraft:beacon -1
{CustomName:"CustomBeacon"}it returns: "The block at x y z did not have the required NBT tags."
Replacing that beacon with a named chest and running: testforblock x y z minecraft:chest -1
{CustomName:"Chesty"}in the exact same spot returns: "Successfully found the block at x y z."
- relates to
-
MC-124395 Beacon block entity contains code for custom names, despite not storing it to NBT and the beacon GUI not having one
- Resolved