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

Redstone ticking area is incorrect in Old-type worlds

XMLWordPrintable

    • Confirmed
    • Multiple
    • 118404

      Edited by Auldrick:

      In worlds of the Old type, redstone ticking only occurs within the central 96 x 96 blocks. The active area does not depend on the player position nor the Simulation Distance setting. Block updates, on the other hand, work normally.

      Steps to reproduce:
      1. Create a world with the Old type.
      2. Place a redstone torch with a redstone dust beside it, within 32 blocks of any edge.
      Expected results: The torch powers the redstone dust.
      Actual results: The redstone dust is unpowered.

      Original description:
      Started an old world type with experimental gameplay enabled when it was first released, now with the prior and latest update redstone wont update. So all buildings and devices that used to function no longer update properly. Taking it out and rebuilding it doesn't work either. I have tried to copy and export it, but the new files wont update either. Switching it to infinite world type fixed the issue, but this doesn't help me still use my old world type. 

       

      screenshot and world attached

        1. C4CA1418-01A5-4482-AEF4-0611454CCA43.png
          C4CA1418-01A5-4482-AEF4-0611454CCA43.png
          1.02 MB
        2. CC3E8F1B-359F-44D1-9750-76875924C34A.jpeg
          CC3E8F1B-359F-44D1-9750-76875924C34A.jpeg
          2.73 MB
        3. D44AF24C-D18C-424E-BC7F-CFB79E763A7C.png
          D44AF24C-D18C-424E-BC7F-CFB79E763A7C.png
          469 kB
        4. E9A220FB-3360-4EB1-A7F0-6805FA5017F9.png
          E9A220FB-3360-4EB1-A7F0-6805FA5017F9.png
          1.29 MB
        5. My World.mcworld
          862 kB
        6. redstone.png
          redstone.png
          543 kB

            KayLous Lloyd Beasley
            Votes:
            12 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: