[0.16.51] Rail signals can read themselves twice?
[0.16.51] Rail signals can read themselves twice?
While unexpected, I can understand why it'd work this way, I'm just looking for confirmation.
Efficient inefficient design.
Re: [0.16.51] Rail signals can read themselves twice?
Thanks for the report however that's working as intended. The same as if you connected the input of a combinator to the output; simply don't do that if that's not what you want to happen.
If you want to get ahold of me I'm almost always on Discord.