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?
Search found 2 matches
- Sat Dec 13, 2025 10:50 am
- Forum: Not a bug
- Topic: [2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
- Replies: 3
- Views: 330
- Tue Nov 25, 2025 2:53 pm
- Forum: Not a bug
- Topic: [2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
- Replies: 3
- Views: 330
[2.0.72] Parametrized train interrupt fails to use parameter in "item count" wait conditions
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 ...
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 ...