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

Chunk loading being limited to players causes various issues

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: Minecraft 1.13.1, Minecraft 1.14 Pre-Release 1, Minecraft 1.14 Pre-Release 2, Minecraft 1.14 Pre-Release 3, Minecraft 1.14 Pre-Release 4, Minecraft 1.14 Pre-Release 5, Minecraft 1.14, Minecraft 1.14.1 Pre-Release 2, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2 Pre-Release 3, Minecraft 1.14.2 Pre-Release 4, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 1, Minecraft 1.14.3 Pre-Release 2, Minecraft 1.14.3 Pre-Release 3, Minecraft 1.14.3, 1.14.4, 19w34a, 19w39a, 1.15 Pre-release 1, 1.15.2, 20w06a, 1.16.1, 20w27a, 20w30a, 1.16.2
    • Fix Version/s: None
    • Labels:
      None
    • Confirmation Status:
      Confirmed
    • Category:
      Chunk loading, Redstone
    • Mojang Priority:
      Normal

      Description

      This bug is NOT in 1.13.1, a bot mistakenly added that version!

      At some point in the development of 1.14, chunk loading was limited to around players (and spawn). This causes many issues on the border of the loaded chunks. One of the worst examples I've tested so far is redstone:
      photo_2019-04-10_22-25-54.jpg
      But there are surely many other mechanics that break at the end of loaded chunks. I don't currently have a list of them.

      Which mechanics should load chunks, which shouldn't and which can work without fully loading the chunk is a matter of discussion. Examples:

      • a mob pathfinding into a new chunk
      • an entity moving into a new chunk
      • structure blocks loading in structures
      • pistons pushing blocks into new chunks
      • executing commands at faraway locations
      • big explosions (they already work fine across the border of loaded chunks, without actually really loading the faraway chunks)
      • hoppers transferring items into a new chunk

      New report for changed behaviour: MC-151049 (That doesn't mean that this one is fixed.)

      Here is a video demonstrating the issue (or MC-151049, it's a bit hard to distinguish what the actual root cause is): https://drive.google.com/file/d/1HU4DsxURtYeS81oj1ecxYRhfoHBN-lq9

        Attachments

        1. 2019-05-03_01.37.21.png
          2019-05-03_01.37.21.png
          363 kB
        2. 2019-05-03_01.40.35.png
          2019-05-03_01.40.35.png
          310 kB
        3. 2019-05-03_01.41.02.png
          2019-05-03_01.41.02.png
          723 kB
        4. 2019-05-03_01.44.32.png
          2019-05-03_01.44.32.png
          394 kB
        5. 2019-08-12_16.50.38-1.png
          2019-08-12_16.50.38-1.png
          164 kB
        6. photo_2019-04-10_22-25-54.jpg
          photo_2019-04-10_22-25-54.jpg
          115 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              FaRo1 Fabian Röling
              Votes:
              107 Vote for this issue
              Watchers:
              56 Start watching this issue

                Dates

                Created:
                Updated:
                CHK: