A giant +1 on this.
TBH, this isn't even a feature request. This feature already exists in the game, but for some inscrutable reason it's only exposed in some places but not others.
Maybe the title of this suggestion should be "please finish your half-completed updates to circuit networks".
Please, PLEASE make circuit connection behavior configurable per wire
Moderator: ickputzdirwech
- IsaacOscar
- Filter Inserter
- Posts: 711
- Joined: Sat Nov 09, 2024 2:36 pm
- Contact:
Re: Please, PLEASE make circuit connection behavior configurable per wire
It seems this feature will likely be in 2.1: viewtopic.php?p=632506#p632506
Re: Please, PLEASE make circuit connection behavior configurable per wire
YES, separate R/G checkboxes for each input AND output function is the perfect answer IMO. It is very easy to understand, and I can't think of any setup that would not become possible.
Inputs would sometimes need to be either/or, though. For some things, like setting requests or filters, it can just add the signals together and it makes sense. But for other functions, it's probably confusing and/or unworkable to use both inputs. I'm thinking of set recipe, set stack size, enable/disable, train stop priority...probably a lot of situations actually. Hopefully not too difficult of a special case to accommodate. If not, then it wouldn't be a disaster if all inputs have to be either/or.
Inputs would sometimes need to be either/or, though. For some things, like setting requests or filters, it can just add the signals together and it makes sense. But for other functions, it's probably confusing and/or unworkable to use both inputs. I'm thinking of set recipe, set stack size, enable/disable, train stop priority...probably a lot of situations actually. Hopefully not too difficult of a special case to accommodate. If not, then it wouldn't be a disaster if all inputs have to be either/or.
Re: Please, PLEASE make circuit connection behavior configurable per wire
+1M
This should be a standard feature of at least every device that can output more than one multi-signal that can overlap others, silos - contents + requests, production machines - ingredients + contents. Basically anything that handles signals describing products.
This should be a standard feature of at least every device that can output more than one multi-signal that can overlap others, silos - contents + requests, production machines - ingredients + contents. Basically anything that handles signals describing products.