I don't know if the benefits offset the additional cluttering of the selector UI, for something that isn't entirely intuitive.


I don't really see how this adds a significant amount of clutter. Selector combinators already have 7 very distinct modes that each come with their own UI. This would ...

TL;DR
Add a way to convert a signal to a signal ID (the ID of the icon).

What?
Allow a mode in which the Selector Combinator converts the input signals into their signal ID.
For example, Iron Ore could have an ID of 1, Copper Ore an ID of 2, Stone an ID of 3, etc.
In essence, like the stack ...

I understand that this can be confusing, but there's 2 sides to consider here. Namely, that it's really damn convenient to be able to set up machines for theoretical later rarities already. I've constructed a blueprint that can handle all the rarities, and just needs a single constant combinator to ...

Just gonna pile on this and say that there's a desperate need for more clarity here.
Just to give a baseline, I'm aware that my color vision isn't 100%, but it's good enough that I've not had any official diagnosis.

Gleba in general is kind of a mess of colors when compared to prior planets, but ...

This is one of the things that has annoyed me the most since this feature got added. I frequently want to use this feature so that I can name constant combinators, to remember what exactly the values it outputs represent. However, the global nature of this is more often a problem than a benefit.

If ...