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

Some structures that were generated in previous 1.16 snapshots can't be located using /locate, but trigger their respective advancements.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Won't Fix
    • Affects Version/s: 20w20b, 20w21a, 20w22a
    • Fix Version/s: None
    • Environment:
      Windows 10, Java 1.8.0_251 64 bit
    • Confirmation Status:
      Community Consensus
    • Category:
      Structures

      Description

      Description:

      On snapshot 20w19a, the Nether generation changed once again. That's normal. But I noticed that Fortresses and Bastions generated in worlds created before 20w19a cannot be located when using the /locate command.

      (Note: I just discovered that this bug also affect Overworld and End structures, not only Nether ones). (I'm putting the most explained case, the Fortresses & Bastions, but for the other structures they also need a fix).

      The seed is: 8825242716498603998. Today, on the new coordinates, there are a big Soul Sand Valley and a big Basalt Deltas, where on old snapshots were Nether Wastes, Crimsom Forest, and a Basalt Deltas.

      Also, on Bastions, Piglins don't generate correctly, and even spawn there Zombified Piglins. Extra: On 20w21a this was overlaped with a lowercase error, but on 20w22a now this bug returned exactly as it was before 20w21a.

      How to reproduce:

      1) Use seed 8825242716498603998 on 20w18a/20w17a (versions for the example).
      2) At spawnpoint, create a Nether Portal. There should be a Crimsom Forest with a Fortress.
      3) Modify the structure.
      4) For the Bastions, just go to the coordinates of the photos. (This also applies for the Fortress).
      5) Finally, charge the world on 20w21a/20w20b-a/20w19a.

      Note: The same bug applies for every version that changed nether generation. Examples are opening a world of 20w06a on 20w15a or opening a 20w15a world on 20w17a.

      PD: If you see some spanish parts, that's because I use spanish, but now I'm reporting a bug. Thanks for hearing.

      Notes: 20w19a trigger the advancements.
      20w20a-b trigger the advancements.
      20w21a don't trigger the advancements.
      20w22a trigger the advancements again. 

        Attachments

        1. 2020-05-17 (16).png
          2020-05-17 (16).png
          412 kB
        2. 2020-05-17 (19).png
          2020-05-17 (19).png
          743 kB
        3. 2020-05-17 (22).png
          2020-05-17 (22).png
          339 kB
        4. 2020-05-17 (23).png
          2020-05-17 (23).png
          433 kB
        5. 2020-05-17 (28).png
          2020-05-17 (28).png
          375 kB
        6. 2020-05-17 (35).png
          2020-05-17 (35).png
          873 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              thejoaqui777 TheSuperPlayer
              Votes:
              11 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                CHK: