Note
Please be aware that commands must be executed within the simulation distance of the world. Also, please be aware that Realms currently have a simulation distance of 4.
If you have any suggestions/requests for commands to work outside of these limits, please voice them on the Feedback website.
Summary:
In the latest beta versions, the commands that the player writes in the chat depend on the simulation distance. If the execution of a command (for example, block placement) is outside the set simulation distance, it will not be executed. In previous versions (including 1.18.12) and java versions, the commands sent in the chat (by the player) depend only on the render distance, and not on the simulation distance.
Steps to reproduce:
Set render distance to 15 or more chunks.
Set simulation distance to 4 chunks (default).
Write a command to place a block / summon a mob or something else with coordinates.
Move away from the place where the command will be executed by 80 or a little more blocks.
Send a previously written command to the chat for execution.
Observed results:
The command fails and you get an error "cannot place blocks outside the world" in the chat. Because the execution of the command is outside the Simulation Distance.
Expected results:
The command will complete successfully. Because the commands sent by the player will not depend on the Simulation Distance.
Video:
1.19.0
1.18.12
Linked issues
is duplicated by 110
Attachments
Comments 31
Hello @unknown.
I had a problem with filling space with blocks (/fill) and didn't use a command block. I sent commands to the chat, but if I was more than 80 blocks from one blocks placement point, an error was generated.
After your mention of Simulation Distance, I explored the problem a bit more. It turned out that in previous versions (including 1.18.12 and java versions) the commands written to be executed by the player in the chat were not affected by the Simulation Distance value. It was enough that the area in which the command is executed was loaded (render distance is responsible for this). That is why in 1.18.12 I could fill more than 1000 blocks in length, and in 1.19 (and in some versions a little earlier) I could not exceed 80.
I have completely updated the description so that it describes the problem as accurately as possible.
In the previous update, these commands worked anywhere within the player render distance. In 1.18.30 and above, they are limited to the simulation distance. If you try to fill or clone outside the simulation distance, it gives the error "Cannot place blocks outside of the world". Players used to be able to fill very large areas or move huge builds with the clone command but that just isn't possible because of this bug. This glitch can also be recreated with commands in the chat, not just command blocks. It is clear this is due to simulation distance because turning it up increases the area in which the commands operate. The glitch is very annoying when you can't clone or fill blocks that you can clearly see.
Cannot place blocks outside world. This is the message I receive when using a /fill command when going over 72 blocks total distance from the original xyz coordinate. Before this update, I was able to /fill large distances within simulation distance and now I cannot go over 72 blocks (tested in my world) ,despite being able to see far and wide with 76 render distance at a comfortable 120fps. The blocks are very much in the world and are clearly visible from where I stand, so seeing the message: cannot place blocks outside world...is ridiculous.
The maximum distance you can fill from depends on the location inside a chunk. At simulation 4, chunks up to & including 4 chunks taxicab from the player's current chunk are simulated, so for a player at 0,0 will simulate up to 0,79.
Because of the shape of the simulated area, you cannot stand at 0,0 & fill a 80x1x80 volume. The farthest simulated block diagonal from 0,0 a player can simulate with sim 4 is 47,47. So although the farthest block is 80 blocks (including the corner the player is standing at), the largest square a player can place while standing at a corner is 48 blocks. But if a player is standing at 15,15, this drops to 33.
The current workaround is to stand at the middle of the area you want to fill, 144 blocks from side to side. Again, if you want to fill a square area, this drops to 80 blocks from side to side.
TL;DR: The current largest square area you can /fill with sim 4 is only 80x80 centered on the player's current chunk, whereas before the area depended on render distance, which could be 3088x3088 blocks at rend 96. The difference is obvious.
This is still an issue in Minecraft Bedrock version 1.21..22 - it is very annoying, because I try to build something with my son and it takes way longer than it should.
I hope that this issue will be fixed, but from what I see around here, there are a lot of small issues that are apparently just ignored. I also hope that this is not the case, regarding the ignored issues.
This really annoying issue is about to have its third birthday. Are the devs actually going to do something about it? It’s been here for way to long and I would argue that it is quite significant of an issue.
As foxynotail states bug is not related to simulation
MCPE-218937 /fill command on bottomless world
Relates to using the fill command to fill eight by 40 by 40 bricks with air on a bottomless flat world. As moving to or more bricks in any direction resolves the error code that Phil could not be completed due to being out of the world does not compute as this leaves pillars of earth in the middle of cleared areas meaning the pillars then have to be manually removed to make an area of space when creating a space project. When moving to bricks up or even one brick up completes fill command. Get moving one brick down level with the cobblestone yield and error code. Similar occurs when moving to bricks left right forwards or backwards and in some cases six bricks is required to move to complete the same function. Print screen command doesn't work using my device or using the windows g so could not provide screen image for the bug using a delay on the snip tool, also fails as Minecraft window reloads when accessing desktop. Also noticed that the world reloads multiple times during using this function.
Are you sure the command block is within Simulation Distance. If the Simulation Distance is set to the default 4 chunks then 80 blocks away would be outside that limit and commands would not execute.
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you comment with new information. Please be sure to provide all requested information. Reports that do not contain enough information may be closed as Incomplete.