MCPE-17208Repeaters set to 1-redstone-tick & comparators have no delay compared to redstone dust
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay. This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters/comparators, by redstone dust, or by just incorrect redstone timings in general. I've also noticed that repeaters, comparators, redstone torches, and redstone dust are powered with the correct timing delay when repeaters are powering them, either directly or with redstone dust in-between, but the affected components listed below will still be powered as though there were no dust between them and the repeater (meaning that you can power a line with dust -> repeater -> 2nd dust -> redstone lamp, and the redstone lamp will come on at the same time as the 1st dust and repeater, and actually 1 redstone tick before the 2nd dust that's supposed to be powering it! This bug almost certainly has something to do with the way that redstone components are powered in MCPE ignoring certain factors (this bug is another example: MCPE-11871).
List of blocks this bug affects:
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect:
- repeaters (the proper delay will be applied to repeaters being powered by other repeaters or redstone dust coming from other repeaters)
- comparators (same as with repeaters)
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
- redstone dust (but components hooked up like repeater -> dust -> piston will actually be powered 1 redstone tick before the dust and in the same tick as the repeater is powered)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.
Linked Issues
Created Issue:
Pistons are activated one redstone tick earlier than they should be.
Pistons will sometimes be activated one tick earlier than they should be. See video and pictures for example:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
Attachments2
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 Version 1607
- 0.15.8 0.15.90.7
Pistons are activated one redstone tick earlier than they should be.Repeaters have no delay compared to redstone dust
Pistons will sometimes be activated one tick earlierthan they should be. See video and pictures for example:
https://youtu.be/z5BXgd2fbP8This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects:
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects:
- pistons
- dispensers
- redstone lamps
List of blocks this bug doesn't seem to affect:
- repeaters
- comparators
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects:
- pistons
dispensersredstone lampsList of blocks this bug doesn't seem to affect:
- repeaters
- comparators
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects:
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
List of blocks this bug doesn't seem to affect:
- repeaters
- comparators
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects:
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers
List of blocks this bug doesn't seem to affect:
- repeaters
- comparators
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different from
MCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannot weakly power adjacent blocks in both MCPE and the Java edition. So this is most definitely a bug.
Repeaters have no delay compared to redstone dust, when they should have a 1-redstone-tick delay
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
observers- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
Original description from when I thought this was a piston bug:
This means that pistons have to activated AT LEAST 2 redstone ticks apart to ensure they are not activated simultaneously. I am not sure if this is a bug with pistons, a bug with repeaters, or just a bug with redstone timing and ticks in general, but I don't think this was happening pre-0.15.3. In that version, pistons seemed to work flawlessly and their timings appeared to be just fine. In 0.15.3, several piston bugs were fixed, but their fixes, along with possibly the change to make pistons redirect redstone dust, seem to have caused all sorts of new timing issues that have rendered many contraptions broken due to a complete non-determinism in which piston will activate first, even when it is blatantly clear that they should be separated by one redstone tick.
In the Java edition, piston timings are always the same when on is hooked up to a repeater and the other isn't. This MAY be due to the faster pistons in Java Minecraft (and that's a whole other topic that already has a bug report for determining whether the pistons in MCPE should be sped up or not), but again, I'm pretty sure this wasn't happening before 0.15.3.
I'm not sure whether or not the cause of this bug is the same as or different fromMCPE-16371, but whatever the case, this is almost DEFINTELY not WAI, because the piston not hooked up via repeater should definitely go first. Maybe if pistons could be strongly powered, you could argue that both pistons were being simultaneously powered by the redstone dust, but pistons cannotweakly power adjacent blocks in both MCPE and the Java edition. Sothisismost definitely a bug.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases.
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay (or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.
Repeaters have no delay compared to redstone dust, when they should have a 1-redstone-tick delayRepeaters set to 1-redstone-tick have no delay compared to redstone dust
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay
(or perhaps the redstone dust has too much delay?). This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters
- comparators
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay. This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects (not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect (not a complete list, either):
- repeaters (the proper delay will be applied to repeaters being powered by other repeaters or redstone dust coming from other repeaters)
- comparators (same as with repeaters)
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.
Repeaters set to 1-redstone-tick & comparators have no delay compared to redstone dust
When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay. This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters, by redstone dust, or by just incorrect redstone timings in general.
List of blocks this bug affects
(not a complete list):
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect
(not a complete list, either):
- repeaters (the proper delay will be applied to repeaters being powered by other repeaters or redstone dust coming from other repeaters)
comparators (same as with repeaters)- redstone
torches (by sending the dust/repeaters into blocks to invert the torches)This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.When you hook up 2 redstone components and power one directly with redstone dust, and the other with a repeater set to a 1-tick delay, Both will be activated at the same time, as if the repeater has no delay. This leads to non-deterministic outcomes, wherein the component that will be powered first is pretty much random. See video and pictures for example:
Note that at the time of recording, I thought the bug was with pistons, and didn't realize it also applied to redstone lamps and other blocks, too. I now believe this bug is either caused by repeaters/comparators, by redstone dust, or by just incorrect redstone timings in general. I've also noticed that repeaters, comparators, redstone torches, and redstone dust are powered with the correct timing delay when repeaters are powering them, either directly or with redstone dust in-between, but the affected components listed below will still be powered as though there were no dust between them and the repeater (meaning that you can power a line with dust -> repeater -> 2nd dust -> redstone lamp, and the redstone lamp will come on at the same time as the 1st dust and repeater, and actually 1 redstone tick before the 2nd dust that's supposed to be powering it! This bug almost certainly has something to do with the way that redstone components are powered in MCPE ignoring certain factors (this bug is another example:
MCPE-11871).List of blocks this bug affects:
- pistons
- sticky pistons
- dispensers
- droppers
- redstone lamps
- observers (placing redstone dust on the input of one and a repeater on the other and activating both simultaneously will cause both observers to be activated at the same time)
- note blocks
List of blocks this bug doesn't seem to affect:
- repeaters (the proper delay will be applied to repeaters being powered by other repeaters or redstone dust coming from other repeaters)
- comparators (same as with repeaters)
- redstone torches (by sending the dust/repeaters into blocks to invert the torches)
- redstone dust (but components hooked up like repeater -> dust -> piston will actually be powered 1 redstone tick before the dust and in the same tick as the repeater is powered)
This bug does not occur on the Java edition, as repeaters set to a 1-tick delay always add a 1 redstone tick delay no matter what they're hooked up to. I'm not sure how long this bug has been in the game, but it has been there since at least 0.15.3. This bug causes various redstone contraptions to act as if they were being affected by
MCPE-16371, since there's no distinction between a repeater powering something and redstone dust powering something in many cases, causing several things to be powered at the same time, which results in random/unpredictable behavior.
relates to
relates to
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
duplicates
duplicates
duplicates
relates to
I think this may be related to, or even the same bug as, MCPE-17208.
OH WHAT THE
...so this is very similar to MCPE-17208 / MCPE-17274...
Re-opening, as this was incorrectly closed as a dupe of MCPE-13983, which was a separate bug which has now been fixed. I have copied over the information provided by [Mojang] Tomas Alaeus relating to this bug and added it to the description. Also revised the report title and attached the relevant screenshots from MCPE-17208 & MCPE-17274.
Updated the title and description to reflect recent testing that shows that this bug also affects redstone lamps and other redstone components as well.
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).