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

locate biome command fails when executed at great heights and depths

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.19.2
    • None
    • Operating System: Microsoft Windows Version 21H1 (OS Build 19043.2006)
      Java version: 17.0.4.1
    • Unconfirmed
    • (Unassigned)

      The /locate biome command fails when executed from below y=-63 or from above y=320 in regular worlds.

      Steps to recreate:

      1. Create and join a new world (world type: default) with cheats enabled.
      2. Find the biome you are currently in.
        1. Press F3 to open the debug screen. The biome you are currently in is displayed on the left side of the screen.
      3. Verify the command works at normal elevations.
        1. Run the command "/execute positioned ~ X ~ run locate biome Y", where X is any value between -63 and 320, inclusive, and Y is the biome you are currently in.
      4. Verify the command does not work at extreme elevations.
        1. Run the command "/execute positioned ~ X ~ run locate biome Y", where X is any value below -63 or above 320, and Y is the biome you are currently in.

      NOTE 1: using the /execute command is convenient for verifying command behavior, though the command can also be verified if you fly or build up or down to the appropriate elevations and run /locate directly. The command fails in both survival and creative mode. See attached image for command response.

      NOTE 2: this command will not fail if you are in a superflat world and you attempt to locate the biome present throughout the entire superflat world, regardless of the elevation from which the command is run. Only superflat worlds and default worlds have been tested in the discovery of this bug report. See attached image for superflat command response.

            Unassigned Unassigned
            ccwithun Calvin Withun
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: