- build a constant combinator
- game.player.selected.get_control_behavior().get_section(1).set_slot(1, {value={type="virtual",name="signal-X"}})
- observe first slot of first (only) section has signal X with count 0
- game.player.print(game.player.selected.get_control_behavior().get_section(1).get_slot(1).min)
- observe min of 0, the count of the signal
- manually set signal X count to 1
- game.player.print(game.player.selected.get_control_behavior().get_section(1).get_slot(1).min)
- observe min of 1, the count of the signal
- optionally build a new constant combinator for the next step, this will not affect the outcome
- game.player.selected.get_control_behavior().get_section(1).set_slot(1, {value={type="virtual",name="signal-X"},min=1})
- observe error
[Rseding91] [2.0.7] Cannot create LogisticFilter with non-zero value
[Rseding91] [2.0.7] Cannot create LogisticFilter with non-zero value
Attempting to create a logistic filter with a non-zero value on a constant combinator control behavior produces an error "Can't specify non zero request with non trivial item filter condition."
Re: [Rseding91] [2.0.7] Cannot create LogisticFilter with non-zero value
Thanks for the report. The issue seems to be that the quality condition is defaulting to "any" which is not valid for values in constant combinators. If you add quality="normal" directly after the name="signal-x" it fixes it. That's not a great fix - since quality things are mostly meant to default to the correct values so they can be omitted when the quality prototypes are not being used.
If you want to get ahold of me I'm almost always on Discord.
Re: [Rseding91] [2.0.7] Cannot create LogisticFilter with non-zero value
This is also an issue when assigning a signal as output signal e.g. in a decider combinator (`set_output(idx, { signal = ... }`)