This bug has apparentally been around since at least 2013 and has never been fixed for some reason. This caused me to fix it in a modified CraftBukkit clone a few years ago and re-apply it to new versions on release, up to 1.12.2. With this message, a screenshot of the commit that fixes the bug is included.
The change is done to a method I believe should return true if the comparator outputs (and the two torches should be on), and returns false when the comparator does not output (and the two torches should be off). This method currently returns true if inputPower >= sideInput, but this should be inputPower > sideInput for the case when the comparator is in subtraction mode.
pieter12345
This bug has apparentally been around since at least 2013 and has never been fixed for some reason. This caused me to fix it in a modified CraftBukkit clone a few years ago and re-apply it to new versions on release, up to 1.12.2. With this message, a screenshot of the commit that fixes the bug is included.
The change is done to a method I believe should return true if the comparator outputs (and the two torches should be on), and returns false when the comparator does not output (and the two torches should be off). This method currently returns true if inputPower >= sideInput, but this should be inputPower > sideInput for the case when the comparator is in subtraction mode.
[media]