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

/locate and custom worlds

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Invalid
    • Affects Version/s: Minecraft 16w39b, Minecraft 16w39c, Minecraft 16w40a, Minecraft 16w42a, Minecraft 16w44a, Minecraft 1.11 Pre-Release 1, Minecraft 1.11, Minecraft 16w50a, Minecraft 1.11.2, 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 17w45a, Minecraft 18w22a, Minecraft 1.13-pre1, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w43b, Minecraft 18w43c
    • Fix Version/s: None
    • Confirmation Status:
      Confirmed
    • Category:
      (Unassigned)

      Description

      If you use /locate in a custom world with some structures disabled it still gives the location of the nonexistent structure.


      Mod edit: Copied repro steps from MC-130441

      Expected output:

      'Could not find that structure nearby.' (or whatever the command says when it fails)

      Returned output:

      'The nearest <structure> is [coords].'

      The bug

      The /locate command returns coordinates of structures even in worlds when structure generation is disabled.

      To recreate

      1. Create a new world where generate-structures=false.
      2. Use /locate <structure> and observe the output.
      3. Click the coordinates to travel there.
      4. There is no structure because structure generation is disabled.
      5. Command should output there is no structure nearby.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                isle James Bauer
              • Votes:
                13 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  CHK: