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

"Powered" blocks can get "stuck" upon structure load.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 1.14.4, 1.15.2, 20w18a, 1.16 Pre-release 5
    • Fix Version/s: None
    • Labels:
      None
    • Confirmation Status:
      Confirmed
    • Category:
      Commands, Redstone, Structures
    • Mojang Priority:
      Normal

      Description

      It's possible for a block's "powered" state to become 'stuck' upon loading it from a structure block.

      To recreate:
      1) Place a Save structure block that will save one block: a pressure plate on top of it.

      2) Jump on the pressure plate to activate the structure block

      3) Load the resulting structure elsewhere. The pressure plate's "powered" state will be stuck to "true" permanently, and cannot be changed without using a debug stick or breaking the block.

      Similar things can be done with other blocks, mostly (but not always) those with "powered" block states:

      • Buttons and pressure plates remain permanently activated as described above if saved while powered. If saved while unpowered, they operate normally.
      • Repeaters, comparators, fence gates, note blocks, trapdoors, doors load their "powered" state as it was saved and won't correct themselves until given a further block update.
      • Redstone lamps do the same as repeaters and the like with their "lit" state instead of "powered".
      • Command Blocks and Structure Blocks function as repeaters/lamps–if powered when saved, they will think they're still powered when loaded up (despite not having a corresponding block state) and will not correct this until given a block update.
      • Redstone wire will load normally if there was a different block in that spot before it was loaded. If, however, it loads into a block that was already redstone wire, it will load its "power" state as it was saved, and will not correct this until given a block update, though other states autocorrect as they should.
      • Tripwire hooks load as attached and powered if saved that way even if no string is present in the new position; normal block updates will not correct this, though reconnecting a full tripwire will do so.
      • Observers are hard to save with proper timing, but I have managed to create 'stopped' observer clocks (and 'double-time' observer clocks) by saving two observers pointing into each other and loading them repeatedly.
      • Redstone torches, levers, and all rail types load and function properly.

        Attachments

        1. 2019-10-24_12.08.03.png
          2019-10-24_12.08.03.png
          411 kB
        2. 2019-10-24_12.15.27.png
          2019-10-24_12.15.27.png
          397 kB
        3. 2019-10-24_12.25.51.png
          2019-10-24_12.25.51.png
          319 kB
        4. 2019-10-24_12.36.44.png
          2019-10-24_12.36.44.png
          484 kB
        5. 2019-10-24_13.05.01.png
          2019-10-24_13.05.01.png
          767 kB
        6. repeaterclock.nbt
          0.3 kB

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            GrifterMage Callum Milne
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              CHK: