Commands that target a valid location in an unloaded chunk return a confusing error. The error seems to imply that the location is not valid, but the location is valid, it is just in an unloaded chunk. This occurs whether the command is run manually or when run through a command block. This affects setblock, testforblock, and summon.
What I expected to happen was...:
Commands (setblock, testforblock, summon, fill) that targeting an unloaded chunk return an error saying cannot target unloaded location.
What actually happened was...:
Error message "Cannot (place block|test for block|summon the object) outside of the world" is shown.
Steps to Reproduce:
1. Teleport to a test chunk to force the chunk to be created, if it hasn't already been.
Ex: /tp @p 1000 100 1000
2. Teleport to another spot, far enough away that the test spot is no longer loaded.
Ex: /tp @p 100 100 100
3. Run a command that targets a location in the test chunk.
Ex: /setblock 1000 100 1000 minecraft:stone 0 replace
Ex: /testforblock 1000 100 1000 minecraft:stone
Ex: /summon Chicken 1000 100 1000
I'm not sure what the error message text should be, perhaps something like:
"Cannot (place block|test for block|summon the object) in an unloaded chunk" or "Cannot (place block|test for block|summon the object) in an unloaded location".
I also think that the error message that is currently shown should continue to exist but only be used when trying to target an invalid location (eg. -y or y>255).
Linked issues
is duplicated by 6
MC-32087
Ambiguous string - commands.summon.outOfWorld
Resolved
MC-56722
Command block bug saying" Cannot change block outside of the world"
Resolved
MC-70198
setblock command creates "cannot place block outside world" when place block in unloaded chunks
Resolved
MC-72242
clone command seems to be hitting imaginary world boundaries
Resolved
MC-78791
/testforblock does NOT send a pulse when the tested block is out of the rendered world
Resolved
Comments 10
My apologies, I did not see the mod comment requesting a new open ticket, was monitoring your other ticket. This has been reopened.
Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
this bug is also for /fill command.
There is semi walkaround in 1.9 snapshosts. You can create end_gateway that destination is in unloaded chunk, and drop an item into it, so chunk will load. Disadventage of this method is that you can't specify end_gateway destination coordinates with tilde.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
Do not duplicate your own ticket ( MC-32485 ).