Affects Version/s: Minecraft 1.12, Minecraft 1.12.1 Pre-Release 1, Minecraft 1.12.1, Minecraft 1.12.2 Pre-Release 1, Minecraft 1.12.2 Pre-Release 2, Minecraft 1.12.2, Minecraft 17w43a, Minecraft 17w43b, Minecraft 17w45b, Minecraft 17w46a, Minecraft 18w01a, Minecraft 18w03b, Minecraft 18w16a, Minecraft 18w19a, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre6, Minecraft 1.13-pre7, Minecraft 1.13-pre8, Minecraft 1.13, Minecraft 1.13.1-pre1, Minecraft 1.13.2, Minecraft 18w48a, Minecraft 18w48b, Minecraft 18w49a, Minecraft 19w03b, Minecraft 19w03c, Minecraft 19w05a, Minecraft 19w06a, Minecraft 19w07a, Minecraft 19w12b, Minecraft 19w13b, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2 Pre-Release 3, 1.15.2 Pre-Release 1
Fix Version/s: None
This bugpost is not about forcing success if you /setblock or /fill an already-existing block( s ), but about changing the somewhat imprecise error message
"The block couldn't be placed." (Since 17w46a: ) "Could not set the block.".
Furthermore, the message is inconsistent with the one for /fill in a similar setup: "No blocks filled".
As by now also the error messages for commands improved greatly, I feel the error message for this case should also be changed, as the output is "too vague".
The same also goes for e.g. a naturally spawned white/yellow sandblock, if you stand on it and do
and even if you insert its (currently still in the game) datavalue like so:
then it still gives you that error message.
Wouldn't it make more sense/be more precise to output an error message along the lines of e.g.:
"Same block already at destination" or "No block changed" or similar?
If you try to fill just a single block that you already filled before with stone, again with stone, you get a different error message displayed in chat than the /setblock-error message: "No blocks filled."
This bugpost is not about forcing success if you /setblock or /fill an already-existing block( s ), but about changing the somewhat misleading or inconsistent error message "The block couldn't be placed.". It would be maybe better for both beginners in CBing, as well as advanced CBers for debugging their maps/contraptions, if the (error) message would be more precise, like suggested above, and maybe also consistent with the /fill-message, if the Devs think this would be better for CBers.