Redstone can lock a conduit to always output signal
mifrai opened this issue ยท 1 comments
Issue Description:
When the following is true:
- a redstone is placed next to a redstone conduit
- the conduit's input/output is set to the same channel
- a positive redstone signal is put into that channel
That channel on the conduit gets locked into the on state.
See the example screenshot. The top is the setup. The bottom is example of the broken state where all red stone inputs are removed.
What happens:
When the source redstone signal is removed, you still get a signal on the channel -- even if all signals are removed.
What you expected to happen:
When the source redstone signal is removed, you stop getting a signal on the channel.
Steps to reproduce:
- Add a conduit to the world
- Add a redstone, connected to the conduit
- Enable input and output on the conduit, change to use the same channel
- Add a redstone torch and make sure the conduit inputs to the same channel
- Remove the redstone torch
- All output on that channel will now be 'on'
Affected Versions (Do not use "latest"):
- EnderIO: 5.0.50
- EnderCore: 1.12.2-0.5.65
- Minecraft: 1.12.2
- Forge: 14.23.5.2838
- SpongeForge? no
- Optifine? no
- Single Player and/or Server? Single player
Your most recent log file where the issue was present:
May relate to #5206