kg583
- kg583
- kg583
- America/New_York
- Yes
- No
MC-132924
Low
When executing /data remove block either in the console or through functions, the CustomName of a block is not removed.
To recreate:
- Create a new world
- Place a nameable block at x y z (e.g. furnace, dropper, dispenser, etc.)
- Run /data merge block x y z {CustomName:"\{\"text\":\"Test\"}"}
- Run /data remove block x y z CustomName
Following Step
3, the block will still retain the name "Test". This bug is not simply a visual error, as running /data get block x y z CustomName will return {\"text\":\"Test\"}, confirming that the block data was unmodified by Step3. Attempting to remove other block data, such as Items, remains functional.When executing /data remove block either in the console or through functions, the CustomName of a block is not removed.
To recreate:
- Create a new world
- Place a nameable block at x y z (e.g. furnace, dropper, dispenser, etc.)
- Run /data merge block x y z {CustomName:"
{\"text\":\"Test\"}"}- Run /data remove block x y z CustomName
Following Step 4, the block will still retain the name "Test". This bug is not simply a visual error, as running /data get block x y z CustomName will return {\"text\":\"Test\"}, confirming that the block data was unmodified by Step 4. Attempting to remove other block data, such as Items, remains functional.
Java 1.8.0_51
on Windows 10 PC
When attempting to use CustomModelData for items provided by a datapack, the items do not display their custom models. See the attached screenshot for an example of the bug.
Steps
- Create a new world.
- Install the datapack attached below (datapack taken from attachment on https://bugs.mojang.com/browse/MC-138892).
- Use the following command to give yourself a water bucket with CustomModelData:
/give @s minecraft:water_bucket{CustomModelData:1}
- The item that appears in your inventory will maintain the regular water bucket texture.
When attempting to use CustomModelData for items provided by a datapack, the items do not display their custom models. See the attached screenshot for an example of the bug.
Steps
- Create a new world.
- Install the datapack attached below (datapack taken from attachment on https://bugs.mojang.com/browse/MC-138892).
- Use the following command to give yourself a water bucket with CustomModelData:
/give @s minecraft:water_bucket{CustomModelData:1}
- The item that appears in your inventory will maintain the regular water bucket texture.
When attempting to use CustomModelData for items provided by a datapack, the items do not display their custom models. See the attached screenshot for an example of the bug.
Steps
- Create a new world.
- Install the datapack attached below (datapack taken from attachment on https://bugs.mojang.com/browse/MC-138892).
- Use the following command to give yourself a water bucket with CustomModelData:
/give @s minecraft:water_bucket{CustomModelData:1}The item that appears in your inventory will maintain the regular water bucket texture.
The /setblock command is documented to avoid replacing certain redstone components in unstable situations, as detailed here. However, the command succeeds in placing certain blocks even when it registers a failure in chat.
Steps to reproduce:
1. Place two standing redstone torches next to each other
2. Stand on one of the torches and run /setblock ~ ~ ~ minecraft:tnt replace
3. "Could not set the block" will appear in chat, but the TNT will still be placed (and ignited)This effect occurs with the "replace" keyword and a null argument; it does not occur with "keep" (when the second torch is replaced with an air block) or "destroy", which contradicts the existing documentation. It would be thus helpful to locate the official specification for what the behavior should be, as I cannot track down when this was added or why (the linked documentation was updated to include the supposed intended behavior in July 2021, with some controversy).
Nonetheless, the current behavior constitutes a bug, as failure and success should not both occur. Chaining the specified command into /execute store success confirms that the handler thinks the command failed.
exhibit_b
Confirmed for Minecraft 1.13-pre7
Confirmed for Minecraft 1.13-pre7
Confirmed for Minecraft 1.13-pre8
The reported error with "Wax On" and "Wax Off" is inconsistent with MC-226484. I'm inclined to suggest that the other report's suggested capitalization ("copper block") is accurate given that the item is called a "Block of Copper" (as discussed in the comments of the other report).
Extensions have been fixed. They are side-by-side comparison images of the same seed in the same location.
That it is; this report can be safely closed as a duplicate.
Why was the bug reporter changed from @commandblockguy to @Avoma?
Why is the field called the "reporter" then? @Avoma did not report the bug. If there is necessarily a "maintainer" role, then it should be a separate field.