The signal wildcard interrupt now (since 2.0.55) matches only those signals that are in the wait conditions. While this *is* written in the description (and therefore is probably intentional) it vastly reduces the viability of dynamically set schedules for trains via interrupts: Since the Wait for circuit condition has no equivalent to Each the signal wildcard has very little use because the only thing it can react to are those that I manually put in the wait condition anyway so for more complex train systems I'd have to add waaaay too many wait conditions.
Reproduction: Two signals are passed to the train via the station, ✓ signal is passed but the iron plate signal has no bearing on the interrupt. Therefore I cannot divert the train to the iron pick-up station unless I manually add waiting for iron signal. This changes the complexity form almost a one-liner that scales automatically as I add more station with different symbols to always having to add another type of a wait condition to the schedule.
I am sure this is a new addition since updating to the newest version of the game bricked my train system.
[2.0.55] Signal wildcard in interrupts no longer usable
[2.0.55] Signal wildcard in interrupts no longer usable
- Attachments
-
- Screenshot_2.png (187.71 KiB) Viewed 163 times
Re: [2.0.55] Signal wildcard in interrupts no longer usable
Please provide a save file because i am unable to reproduce any issues. When i sent a pair of signals "check signal = 1, iron-plate = 5" the interrupt properly triggers. From the common faults i can predict you fell into is that you sent the iron-plate with value of 1 which prevents it triggering because of the second condition doing value comparison while you expect it to be a signal type comparison (which its not).