I'm unsure if this is a bug or if I'm misunderstanding how it should work, so here’s what I'm experiencing:
Expected Behavior: In this example, I set up an interrupt that should identify a non-full station, specifically iron-ore[IN]. Once it finds this station, it should proceed to iron-ore[OUT].
Actual Behavior: As far as I understand, it can't find an empty iron-ore[IN] because the item parameter isn't being correctly replaced with iron-ore.
[kovarex] [2.0.11] Interrupt wildcard used to match station name without item inventory presence
Re: [2.0.11] Item Parameter for "Station is Not Full" Problem
This wildcard works only when inventory is non-empty. If it is, the wildcard matches nothing.
Re: [kovarex] [2.0.11] Item Parameter for "Station is Not Full" Problem
Yes, I never thought about it being used this way, trying to use it to "select" any station (set of stations) with some properties.
This might be worth trying to implement, but I don't promise it now.
Another one with the same idea: 117457
This might be worth trying to implement, but I don't promise it now.
Another one with the same idea: 117457
-
- Burner Inserter
- Posts: 6
- Joined: Fri Feb 20, 2015 7:32 pm
- Contact:
Re: [kovarex] [2.0.11] Interrupt wildcard used to match station name without item inventory presence
I was also trying to use this for an interrupt system that checked if both an "In" and "Out" station were available for a wildcard before starting a delivery run and was pretty disappointed when it didn't work, so I hope this gets implemented.
Re: [kovarex] [2.0.11] Interrupt wildcard used to match station name without item inventory presence
Moved to not a bug, to make clear this is a feature we will do later.
-
- Inserter
- Posts: 20
- Joined: Sat Nov 14, 2020 2:39 am
- Contact:
Re: [kovarex] [2.0.11] Interrupt wildcard used to match station name without item inventory presence
Yep, I misunderstood one of the FFF and tried similar "At [circuit wild card]Loading" and "Destination [circuit wildcard icon]Unloading". Obviously I see my error, but would be cool if the "At [wildcard]String" could match and "capture" against station names.
I like these features, but the first-item-in-cargo approach seems less flexible. The "At *station" is more contextual, and the condition better expresses the intent, and would work generically regardless of if you're empty, and mitigates the risk of an errant item on a belt polluting a train and causing the train to start running a differ load/unload on the basis of one polluted item.
I like these features, but the first-item-in-cargo approach seems less flexible. The "At *station" is more contextual, and the condition better expresses the intent, and would work generically regardless of if you're empty, and mitigates the risk of an errant item on a belt polluting a train and causing the train to start running a differ load/unload on the basis of one polluted item.