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

Redstone components not being updated / stuck in weird states

XMLWordPrintable

    • Survival
    • Unconfirmed
    • Windows

      Hi.

      I have on two different occasions encountered a bug with redstone contrapsions getting stuck in weird states after quitting and logging back in. One a simple comparator powering a series of redstone dust and repeaters powering a redstone light. The other a piston door.

       

      This bug seems to affect redstone builds in a wide area. I actually have one very simple build that highlights the problem.

       

      "Torch -> repeater -> block -> redstone lamp."

      This should power the lamp, but when the bug hits it doesnt. See the attached screenshots for a quick demo.

       

      I had one or two tickingareas that were active for the area with the redstone build. This was also on a two player Realm.

       

      This is more or less what I did:

      1.  Logged on to another players Realm (I'm set as admin/operator/whatever its called)
      2. I added a circular tickingarea with a radius of 4 chunks that should have covered the whole contraption.
      3. I built the redstone contraptions on MCPE Win10
      4. I logged off
      5. Another player logged on to the Realm on an Nintendo Switch
      6. I logged on an noticed that all the redstone contrapions in a relatively wide area has stopped working.

       

      Having both players log out, then immediately log back in doesnt seem to solve the issue, however, having both players log out, wait at least 30 minutes, then have the windows 10 client log back in seems to make the stuck redstone unstuck again.

       

       

        1. not_working.PNG
          842 kB
          Espen Fjellvær Olsen
        2. working.PNG
          536 kB
          Espen Fjellvær Olsen

            espenfjo Espen Fjellvær Olsen
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: