MC-8911Able to get pulse through a comparator by right clicking
I had a one tick clock going and the comparators weren't allowing a pulse to go through (which could be a bug itself), but when I repeatedly right clicked the comparator, I was able to get the pulse through as you can see in the screenshot.
Code analysis by [Mod] NeunEinser can be found in this comment.
Linked Issues
Normal
Created Issue:
Able to get pulse through a comparator by right clicking
I had a one tick clock going and the comparators weren't allowing a pulse to go through (which could be a bug itself), but when i repeatedly right clicked the comparator, i was able to get the pulse through as you can see in the screenshot
Environment
OSX Mountain Lion, Java version 7 update 11
Attachments1
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
I had a one tick clock going and the comparators weren't allowing a pulse to go through (which could be a bug itself), but when
irepeatedly right clicked the comparator,iwas able to get the pulse through as you can see in the screenshotI had a one tick clock going and the comparators weren't allowing a pulse to go through (which could be a bug itself), but when I repeatedly right clicked the comparator, I was able to get the pulse through as you can see in the screenshot.
Code analysis by [Mod] NeunEinser can be found in this comment .
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mod] j_p_smith](../../../data/avatars/users/92851.png){kind=small}
OSX Mountain Lion, Java version 7 update 11
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Low![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
I think this is at least related to MC-8911. This bug describes a behavior, where the comparator does not blink/ react unless you spam right click on it.
Anyways, can confirm for 1.12
I was able to semi-confirm this on 13w07a, in that if a comparator is being fed a one-tick rapid pulse, it will not allow it through until it gets updated. Some designs update the comparator and so allow the signal through, while others do not and the comparator needs a block/redstone update to start letting the signal out.
Ones that worked had the comparator near other equipment that would update at the time, non-working designs (ones that needed an update) tended to have the comparator a few blocks away from the equipment sending the signal.
Unable to reproduce.
This is a shot of a test device, a very simple redstone clock using a comparator in subtract mode feeding itself.
This second screenshot shows the piston responding when I right-click the second comparator, though it usually takes a few clicks to get it to happen. It pulses really quickly so this is the best shot I got, but as you can see it did allow the signal through in 13w10a.
Okay so it's still happening all the way in 15w42a, and here's a gfy of the setup and results.
http://gfycat.com/FrayedShadowyAustralianfurseal
Reopened and gave the ticket to George Gates.
Still happening in 15w44b.
George Gates: Since you are the reporter of this ticket, you can update the affected versions by yourself.
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time.
Can confirm for 1.12
Please link this in the description.
This issue happens because in net.minecraft.block.BlockRedstoneComparator.onBlockActivated(World, BlockPos, IBlockState, EntityPlayer, EnumHand, EnumFacing, float, float, float) the method onStateChange which checks if the comparator should be powered is called right away. Since the redstone signal stays on for 2 game ticks, there is basically a 25% chance that the player happens to activate the comparator in the 1st game tick of the signal being turned on.
This can be prevented by adding a check if there is an update scheduled before executing onStateChange. That will ensure that the repeater will not let a signal through in between the ticks.
Can confirm for 1.13-pre3
Is this still an issue in 1.13.2 or the latest snapshot 18w43c?
This report is currently missing crucial information. Please take a look at the other comments to find out what we are looking for.
If you added the required information and a moderator sees your comment, they will reopen and update the report. However, if you think your update to this report has been overlooked or you want to make sure that this report is reopened, you can contact the Mojira staff on Discord or Reddit.
– I am a bot. This action was performed automatically! Please report any issues on Discord or Reddit
Still an issue in both 1.16.15 and 1.17-pre1.
See also https://www.reddit.com/r/Mojira/comments/nmrthk/mc8911_is_still_an_issue_in_1165_and_117pre1/
Still an issue in 1.17-pre2.
Can confirm in 1.17.1.
Can confirm for 1.19.3