Assemblers let you pick the recipe and read the contents. Why don't requester chests?
Posted: Fri Nov 29, 2024 5:43 am
I always thought there was some kind of limitation that meant a entity had to choose EITHER, but not BOTH:
1. Change behavior. Like what an assembler creates or what a requester requests
OR
2. Output information about its content.
I thought that was the reason requester chests could change requests or read content, but never both.
Automatic recipe setting seems to reveal that isn't a real limitation. So could logistic chests (and landing pads) be allowed to set requests and read contents?
Also, it might be nice if "Set Recipe" could be limited to just the red or just the green wire input. I can use combinators to guard against sending accidental input signals, but it's a bit delicate and error-prone.
1. Change behavior. Like what an assembler creates or what a requester requests
OR
2. Output information about its content.
I thought that was the reason requester chests could change requests or read content, but never both.
Automatic recipe setting seems to reveal that isn't a real limitation. So could logistic chests (and landing pads) be allowed to set requests and read contents?
Also, it might be nice if "Set Recipe" could be limited to just the red or just the green wire input. I can use combinators to guard against sending accidental input signals, but it's a bit delicate and error-prone.