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

Weird Redstone Repeater Behavior

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • None
    • Minecraft 14w29b
    • None
    • Windows 7 Home Premium 64-bit, Java 7 Update 55
    • Unconfirmed

      How to reproduce this bug (screenshots follow along):

      1) Make a contraption similar to the first screenshot. Repeaters are on 4 ticks (max). The commands in the command blocks can just be /say hi or /say trains or whatever.

      2) Put a redstone block as shown in the second screenshot, to activate the redstone repeaters. The contraption works as normal. Just like what anyone would expect.

      3) Type a /setblock command to put a redstone block in the same place. Execute it, see it work again (if the previous block was destroyed), then destroy the newly placed block. So therefore, that command is saved in the chat history. (Screenshot 3)

      4) Teleport away from the contraption so it isn't in sight (in my case, screenshot 4, I teleported 2000 blocks away).

      5) Execute the same /setblock command. Now the text appears double the speed (faster than when the contraption was visible). That's the bug.

      In my case the new VBO option doesn't change the output. Well, that's all. See if it's a true bug or my imagination.

        1. 2014-07-16_17.46.56.png
          2014-07-16_17.46.56.png
          33 kB
        2. 2014-07-16_17.46.27.png
          2014-07-16_17.46.27.png
          54 kB
        3. 2014-07-16_17.45.48.png
          2014-07-16_17.45.48.png
          200 kB
        4. 2014-07-16_17.44.58.png
          2014-07-16_17.44.58.png
          145 kB
        5. 2014-07-16_17.44.17.png
          2014-07-16_17.44.17.png
          79 kB

            Unassigned Unassigned
            Schoperation Schoperation
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: