Page 1 of 1
API Docs do not have definitions for Decider Combinator control behavior
Posted: Sat Nov 02, 2024 1:35 am
by hgschmie
Re: [2.0.14] API Docs do not have definitions for Decider Combinator control behavior
Posted: Fri Dec 20, 2024 9:11 pm
by LeonSkills
Ran into the same issue (2.0.27).
For anyone else stumbling on this topic:
- DeciderCombinatorCondition has the same first_signal, second_signal, constant, comparator from v1.0
DeciderCombinatorParameters .
Additionally it has `first_signal_networks` and `second_signal_networks`, which is probably of type
CircuitNetworkSelection. Which is also not documented.
It is a table of {green:: boolean, red:: boolean}
- DeciderCombinatorOutput also has the `copy_count_from_input`, but `output_signal` has been renamed to `signal`.
Additionaly it also has `networks` with type CircuitNetworkSelection. And constant to set the consant to anything other than 1.
Re: [2.0.14] API Docs do not have definitions for Decider Combinator control behavior
Posted: Sat Dec 21, 2024 2:42 pm
by LeonSkills
And while we are at it.
SelectorCombinatorParameters, also misses
"stack-size", "rocket-capacity", "quality-filter" and "quality-transfer" as options for `operation'
For "quality-filter":
`quality_filter`:: SignalFilter (only with quality: QualityID and comparator: ComparatorString)
For "quality-transfer":
`select_quality_from_signal`:: boolean
`quality_source_signal`:: SignalID
`quality_source_static`:: Just a table with {name: string}, not sure what type
`quality_destination_signal`::SignalID
Re: [2.0.14] API Docs do not have definitions for Decider Combinator control behavior
Posted: Tue Mar 04, 2025 11:37 pm
by Hanakocz
SelectorCombinatorParameters also misses random_update_interval as an option when operation is 'random'
Re: API Docs do not have definitions for Decider Combinator control behavior
Posted: Wed May 07, 2025 8:33 am
by Therenas
All concerns brought up in this thread are addressed for the next release. Thanks for the reports and sorry for the wait.