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

Vertical redstone dust placed against dropper/dispenser/hopper doesn't visually disappear when the dust above is removed

XMLWordPrintable

    • Confirmed
    • Block states, Redstone
    • Normal
    • Platform

      When you place redstone dust against a dropper or dispenser while that same piece of dust is being redirected and powered(as seen below),

         

      if the top piece of redstone dust is broken, the vertical piece of dust still shows.

      Even weirder is that if the dispenser is removed the vertical dust still displays:

      Once the block has been removed another can be put in it's place creating some interesting situations:

      This is entirely visual and client-side only as the dust doesn't actually power anything(like a redstone lamp).

      A re-log or a block update(e.g placing a target block next to the other side of the redstone) fixes this issue and returns the dust to the expected state.

      As far as I have tested this only happens on dispenser, droppers and hoppers although the hopper behaves slightly differently as it isn't a solid block.

      When the layout of blocks is placed with a hopper instead of a dropper the redstone redirects into the hopper:

      and then when the dust is removed it remains redirected into the hopper:

      A strange behaviour occurs on the player's F3 screen too. After making the redstone do this to the hopper, the F3 screen displays "enabled: false" yet it still picks up items:

      After a look in the hopper's gui it updates and returns to correctly display that it is "enabled: false":

       

      The F3 screen for the wire also displays that it is facing up:

       

      Weirdly this only occurs when the redstone is powered. If the same setup is built but without power the redstone dust doesn't display vertically.

      Also, if the redstone power is removed after the redstone has been glitched it will return to the expected state (as this is a block update for the redstone).

       

      Similarly this does not occur without the redirection of the redstone:

       

       

      Here is a short video of the setup:

      weirdRedstoneBehaviour.mp4

       

       I have only tested this in 1.19.2 but it might exist in previous versions as well.

        1. 2022-08-22_08.16.50.png
          2022-08-22_08.16.50.png
          465 kB
        2. 2022-08-22_08.19.47.png
          2022-08-22_08.19.47.png
          554 kB
        3. 2022-08-22_08.24.56.png
          2022-08-22_08.24.56.png
          617 kB
        4. 2022-08-22_08.29.36.png
          2022-08-22_08.29.36.png
          484 kB
        5. 2022-08-22_08.31.27.png
          2022-08-22_08.31.27.png
          422 kB
        6. 2022-08-22_08.38.21.png
          2022-08-22_08.38.21.png
          376 kB
        7. 2022-08-22_08.40.02.png
          2022-08-22_08.40.02.png
          495 kB
        8. 2022-08-22_08.42.21.png
          2022-08-22_08.42.21.png
          400 kB
        9. 2022-08-22_08.45.13.png
          2022-08-22_08.45.13.png
          365 kB
        10. 2022-08-22_08.48.39.png
          2022-08-22_08.48.39.png
          519 kB
        11. 2022-08-22_08.48.43.png
          2022-08-22_08.48.43.png
          506 kB
        12. 2022-08-22_08.51.25.png
          2022-08-22_08.51.25.png
          512 kB
        13. 2022-08-22_08.51.28.png
          2022-08-22_08.51.28.png
          528 kB
        14. 2022-08-22_08.56.36.png
          2022-08-22_08.56.36.png
          520 kB
        15. 2022-08-22_09.01.55.png
          2022-08-22_09.01.55.png
          583 kB
        16. weirdRedstoneBehaviour.mp4
          8.30 MB

            panda4994 [Mojang] Panda
            MoltenWolfCub MoltenWolfCub
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: