Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-119312

TickingAreas unload periodically, causing the chunk(s) to stop simulating for a moment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 1.18.10.20 Beta, 1.18.10
    • 1.16.201 Hotfix
    • None
    • Confirmed
    • Multiple
    • 480194

      TickingAreas don't tick reliably which could be a huge problem for technical maps/Marketplace content that require command blocks to function.

      It appears that larger tickingAreas unload more frequently, and when they fail it affects every chunk in that area. More testing needs to be done in order to confirm this, though.

      In , the first value is how many gameticks have been simulated in the tickingArea over the course of an hour. The second value is how many gameticks have been simulated by the player over the same time frame.

      In the picture below, the chunks labelled chunk[_] are separate chunks in the same tickingArea. This is evidence that larger tickingAreas unload more often.

      Steps to Reproduce

      1. Open tick_testing.mcworld. It contains a scoreboard system that counts ticks in several chunks simulated by the player, and in ticking area.
      2. /tp -89 1 -128
      3. Flip the lever.
      4. Wait for a few minutes, or up to an hour.

      Expected result

      All scoreboards display the same number.

      Actual result

      Areas simulated by the player have a higher value on the scoreboard than that of the tickingArea.

        1. tick_testing_2.png
          27 kB
          axialeaa
        2. tick_testing.mcworld
          82 kB
          axialeaa
        3. tick_testing.png
          33 kB
          axialeaa

            voidredstone axialeaa
            Votes:
            33 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: