Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-32522

Confusing error message when targeting a location in an unloaded chunk

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 13w38c, Minecraft 14w30c, Minecraft 1.8, Minecraft 1.8.3, Minecraft 1.8.7, Minecraft 15w41b, Minecraft 1.11
    • Fix Version/s: Minecraft 18w03b
    • Environment:

      OSX 10.8.4
      Java 1.6.0_51

    • Confirmation Status:
      Confirmed
    • Game Mode:
      Creative

      Description

      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).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                c0rdawg Corey Maher
              • Votes:
                10 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  CHK: