MC-91459/setblock at Y=256 shows unique message compared to using other outside-world setblock commands / Using /setblock at Y>256 says max building height is 256
The bug
Using the /setblock command at exactly Y=256 is the only command that shows the message "The block couldn't be placed". Using /setblock at all other Y-coordinates that are outside of the building range of the world shows the message "The number you have entered (Y) is too (big/small), it must be at (most/least) 256". This message also states that the max height for building is 256, which is false.
To reproduce
/setblock ~ 256 ~ stone
/setblock ~ 257 ~ stone
- Compare the messages gotten from performing previous steps
Code analysis
By Marcono1234
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.command.CommandBase.parseBlockPos(ICommandSender, String[], int, boolean) defines 256 as maximum y value.
Suggested fix
Making so attempting to place a block by not using /setblock at Y=256 shows the text "The block couldn't be placed", or more fitting, "You can't build this high" over the hotbar, just like when trying to sleep at day. Using /setblock at Y=256 should show the message "The number you have entered (256.00) is too big, it must be at most 255".
Created Issue:
/setblock at Y: 256 displays unique message compared to other outside-world setblock messages
The command
/setblock <x> 256 <y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered
is too big, it must be at most 256"* or "The number you have entered
"The number you have entered
The command
/setblock <x> 256 <y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered
"The number you have entered
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"* or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256 was based on misunderstanding, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"* or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256 was based on misunderstanding of what the height limit was, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"* or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256
was based on misunderstandingofwhat the height limit was, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"* or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256 didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"* or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256"
*or "The number you have entered (Y) is too small, it must be at least 0"."The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
relates to
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message "Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256" or "The number you have entered (Y) is too small, it must be at least 0".
"The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message
"Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256" or "The number you have entered (Y) is too small, it must be at least 0"."The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
To reproduce:
- Enter for example
/setblock ~ 256 ~ stone- Compare the messages you get from the command of step 1 and the message from
/setblock ~ 257 ~ stone
/setblock at Y:256 displays unique message compared to other outside-world setblock messages/setblock at Y>=256 displays unique message compared to other outside-world setblock messages
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message
"Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256" or "The number you have entered (Y) is too small, it must be at least 0"."The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
To reproduce:
- Enter for example
/setblock ~ 256 ~ stone- Compare the messages you get from the command of step 1 and the message from
/setblock ~ 257 ~ stone
Code analysis by Marcono1234 can be found in this comment.
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
The command
/setblock <X> 256 <Y> <TileName>is the only setblock command that produces the message
"Cannot place block outside of the world". All other outside-world setblock commands will display the message "The number you have entered (Y) is too big, it must be at most 256" or "The number you have entered (Y) is too small, it must be at least 0"."The number you have entered (Y) is too big, it must be at most 256". See? "at most 256". Blocks can't be placed there. The problem must be related to that the developer who wrote what the chat would output if a block was "/setblock" at Y: 256, didn't think of that the height limit was 256, or something like that. Therefore, setting block at Y: 256 has a unique message, for some reason.
To reproduce:
- Enter for example
/setblock ~ 256 ~ stone- Compare the messages you get from the command of step 1 and the message from
/setblock ~ 257 ~ stone
Code analysis by Marcono1234 can be found in this comment.
The bug
Using the /setblock command at exactly Y=256 is the only command that shows the message "The block couldn't be placed". Using /setblock at all other Y-coordinates that are outside of the building range of the world shows the message "The number you have entered (Y) is too (big/small), it must be at (most/least) 256". This message also states that the max height for building is 256, which is false.
To reproduce
- Compare the messages gotten from performing previous steps
Code analysis
By Marcono1234
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.command.CommandBase.parseBlockPos(ICommandSender, String[], int, boolean) defines 256 as maximum y value.
Suggested fix
Making so attempting to place a block by not using /setblock at Y=256 shows the text "The block couldn't be placed", or more fitting, "You can't build this high" over the hotbar, just like when trying to sleep at day. Using /setblock at Y=256 should show the message "The number you have entered (256.00) is too big, it must be at most 255".
/setblock at Y>=256displays unique message compared to other outside-world setblockmessages/setblock at Y=256 shows unique message compared to using other outside-world setblock commands / Using /setblock at Y>256 says max building height is 256
The bug
Using the /setblock command at exactly Y=256 is the only command that shows the message "The block couldn't be placed". Using /setblock at all other Y-coordinates that are outside of the building range of the world shows the message "The number you have entered (Y) is too (big/small), it must be at (most/least) 256". This message also states that the max height for building is 256, which is false.
To reproduce
- Compare the messages gotten from performing previous steps
Code analysis
By Marcono1234
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.command.CommandBase.parseBlockPos(ICommandSender, String[], int, boolean) defines 256 as maximum y value.
Suggested fix
Making so attempting to place a block by not using /setblock at Y=256 shows the text "The block couldn't be placed", or more fitting, "You can't build this high" over the hotbar, just like when trying to sleep at day. Using /setblock at Y=256 should show the message "The number you have entered (256.00) is too big, it must be at most 255".
The bug
Using the /setblock command at exactly Y=256 is the only command that shows the message "The block couldn't be placed". Using /setblock at all other Y-coordinates that are outside of the building range of the world shows the message "The number you have entered (Y) is too (big/small), it must be at (most/least) 256". This message also states that the max height for building is 256, which is false.
To reproduce
- Compare the messages gotten from performing previous steps
Code analysis
By Marcono1234
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.command.CommandBase.parseBlockPos(ICommandSender, String[], int, boolean) defines 256 as maximum y value.
Suggested fix
Making so attempting to place a block by not using /setblock at Y=256 shows the text "The block couldn't be placed", or more fitting, "You can't build this high" over the hotbar, just like when trying to sleep at day. Using /setblock at Y=256 should show the message "The number you have entered (256.00) is too big, it must be at most 255".
relates to
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
I'm not 100% sure if I understood you correctly, my brain is still afk, but let's see 
"block couldn't be placed" inserted into Mojira's search box renders 188 issues: https://bugs.mojang.com/issues/?jql=text%20~%20%22block%20couldn%27t%20be%20placed%22
I searched through these issues before I wrote mine here, but couldn't find the exact issue that I've got here.
There was a recent fix, the same thrown error if a tile entity was replaced with a setblock-air which actually succeeded, but the game threw that error regardless (MC-50166), and I knew that bugpost/fix of it.
That's why I thought this issue here might be a valid one.
MC-91459 is considered valid, probably because the error message deviates from the other "out of the world / maxbuildheight" messages, but I still can't see why "my" issue here wouldn't be, as I find the error message indeed, as you called it, "too vague".
Apparently it seems that the game can detect if one tries to /setblock the same block that already is set at the same position, otherwise it wouldn't throw that message? So why does it not just give a message like: "Same block is already at destination" or so? Which brings me to a different question I need to test asap regarding /fill, which defaults to "replace" even without any "oldBlockHandling" inserted last time I checked, but I don't want to make this issue here more confusing, unless you'd say there should be some sort of consistency between /setblock and /fill?
I feel /setblock behaves a bit inconsistent, if it only replaces a block if it's not the same that was there before with the basic command, and if that behaviour is "WaI", then the error message should at least display that behaviour, which might be less confusing for beginners in CBing. That's all I meant, but, again: That's just my personal opinion
Have a nice Sunday, I'll try to wake up my brain now with some jogging in fresh air 
Confirmed for
Applies to all block position related commands, for example /fill, /setblock...
Please link to this comment in the description
The following is based on a decompiled version of Minecraft 1.9 using MCP 9.24 beta.
The reason for this is that the method net.minecraft.command.CommandBase.parseBlockPos(ICommandSender, String[], int, boolean) defines 256 as maximum y value.
Can confirm for MC 1.12.1.
Relates to
MC-122828This has been fixed in 1.13.1 due the change of the messages itself.
It actually was fixed in 1.13 the message now says "That position is out of the world!".