Page 1 of 1
[2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
Posted: Tue Nov 25, 2025 2:53 pm
by capn_thule
I will use X as stand-in for "parameter wildcard" rich text.
I was playing with an automatic item requester using signals and interrupt-based train schedule.
It all mostly works as expected, but once I switched from
concrete names (ITEM Load) to wildcarded (X Load), the wait condition (X >=3) no longer works, because X is not replaced with ITEM.

- 202511~2.JPG (2.04 MiB) Viewed 330 times
As a result, train keeps loading indefinitely:

- 202511~4.JPG (2.45 MiB) Viewed 330 times
Note that the bug only happens if at the moment of interrupt, the train does not contain ITEM. If it does, the condition renders properly:

- 20705E~1.JPG (609.79 KiB) Viewed 330 times
Re: [2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
Posted: Tue Nov 25, 2025 3:14 pm
by Loewchen
But isn't the train empty when the interrupt triggers, so there is no item to fill the cargo wildcard?
Re: [2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
Posted: Tue Nov 25, 2025 7:29 pm
by robot256
The Circuit Signal Wildcard will be filled in with the first signal that meets the condition. It will be filled in everywhere in the interrupt that the Circuit Signal Wildcard appears. It will *not* fill in slots containing the Item Wildcard, because it is a signal not an item. Unless I'm completely wrong, in which case I'm sorry.
You need to use the same wildcard symbol in the interrupt schedule as you use in the intereupt trigger conditions. Then it will be filled in correctly. Or does it not fill in signal wildcards in the Cargo conditions even if they match with valid items?
Another option would be to use "cargo not empty" and "inactivity" conditions, or maybe the one of the asterix symbols?
Re: [2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
Posted: Sat Dec 13, 2025 10:50 am
by capn_thule
Hm, I think you're correct @robot256.
The problem is, this is the only wildcard symbol allowed here.
So I guess it's not a bug but should be considered a feature request to allow for wildcard signal in this condition?

- 202512~1.JPG (1.66 MiB) Viewed 73 times