Allow Parameterization of the Constant Value in the Decider Combinators Output
I know this just got added in the latest experimental build, so possible this is already in the pipeline, but I wanted to bring it up.After the recent patch we can now specify a value for the signal being output by a decider combinator. This value, for whatever backend reason, does not show up when you try to parameterize a blueprint. As the title states, it would be awesome if this could be part of the parameterization. Below is the use case I ran into where I think this would be helpful, just for some context.
Currently I have a circuit that essentially takes the items my ship currently has, and target values for how many of each of those items I want. Based on this, I control what types of asteroid crushing I am doing. On top of this, I use bit masking to use this central circuit to set multiple asteroid crusher's recipes independently, based on the type of asteroid in front of that crusher.
It looks like this:
- 03-09-2025, 19-00-39.png (591.94 KiB) Viewed 239 times
And the combinator that takes the input of the belt looks like this. The "1" here is a unique power of 2 for each asteroid crusher I lay down.
- 03-09-2025, 18-53-23.png (322.13 KiB) Viewed 239 times
When I go to parameterize, the "1" for the bitmask shows up, but the "1" for the decider output value doesn't show up, as seen below:
- 03-09-2025, 19-01-55.png (465.77 KiB) Viewed 239 times
Would love if you guys could make this a parameter. This was my use case but I imagine others will have lots of others. First time posting so if I should be posting this somewhere else I'm happy to do so, just let me know.
And finally just adding the BP incase anyone is curious: