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

Repeater Locking acts differently depending on whether it outputs to redstone dust vs. to another repeater

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.8-pre2, Minecraft 1.8-pre3
    • None
    • Windows 7

      C:\Users\Andrew>java -version
      java version "1.7.0_01"
      Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
      Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)
    • Unconfirmed

      This setup sends a one-tick pulse to the locking repeaters every time I press the button.

      What I expected to happen was that... both pistons would be activated when I allowed to pulses to travel through the line of locking repeaters.

      What actually happened was... only one piston was activated.

      Steps to Reproduce:
      1. Build the setup shown in picture #1. The repeater inside the monostable circuit (the lambda shaped stone brick thing that turns button presses into 1-tick pulses) is on the 2-tick setting. The other repeaters are on the 1-tick setting.
      2. Activate both levers.
      3. Press the button.
      4. Deactivate both levers. You should now be seeing picture #2.
      5. Press the button. You should now be seeing picture #3 (except for the sponges). This is unexpected- I expected the far piston to be activated, along with the 2 redstone dust and 1 repeater marked by the sponges.

      Edit: This bug is not present in 1.7.10. The expected result is shown in picture #4. Note that the 1.7.10 setup requires the monostable circuit's repeater to be on the 3-tick setting in order for the same results to occur. I assume this is related to and/or the source of this bug.

        1. pic 4- 1.7.10's expected result.png
          pic 4- 1.7.10's expected result.png
          253 kB
        2. pic 3- 1.8-pre2's unexpected result.png
          pic 3- 1.8-pre2's unexpected result.png
          253 kB
        3. pic 2.png
          pic 2.png
          205 kB
        4. pic 1.png
          pic 1.png
          215 kB

            Unassigned Unassigned
            andrewhuff4 Andrew Huff
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: