This also has some strange effects when it comes to comparators reading a signal from a container. Usually, the container overrides the value from any redstone lines, and that still happens. But when a redstone line is connected to both inputs of the comparator, and the comparator is reading from an container, bug is present (see images). Hopper has 1 dirt in it.
[media][media]
2.
I tried to map out multiple input and output values of the comparator, but it is highly dependent on many factors which should not affect the output. In particular, the positioning of power sources plays a large rule, and the orientation does play some rule. Sometimes adding a power source with does not affect the inputs to the comparator will change the output of the comparator. It seems that a part of the issue may be which power source is being chosen as the input. I also never say an output value greater than 7 (implies mod/sign issue to me, but other issues make it hard to figure out exactly what the problem is, especially without code.).
Aden Koperczak
Windows 10 v1.19.50
1.
This also has some strange effects when it comes to comparators reading a signal from a container. Usually, the container overrides the value from any redstone lines, and that still happens. But when a redstone line is connected to both inputs of the comparator, and the comparator is reading from an container, bug is present (see images). Hopper has 1 dirt in it.
[media][media]2.
I tried to map out multiple input and output values of the comparator, but it is highly dependent on many factors which should not affect the output. In particular, the positioning of power sources plays a large rule, and the orientation does play some rule. Sometimes adding a power source with does not affect the inputs to the comparator will change the output of the comparator. It seems that a part of the issue may be which power source is being chosen as the input. I also never say an output value greater than 7 (implies mod/sign issue to me, but other issues make it hard to figure out exactly what the problem is, especially without code.).