[kovarex] Parameterized Train interrupts cant be used in conjunction with reading train IDs
Posted: Sun Oct 27, 2024 12:19 pm
Ive been working on a train scheduler with the circuit network and discovered what i assume is a bug. i could be very wrong and misunderstanding how to use this feature. The setup is fairly simple:
- Create a small segment of rail with a stop and a locomotive.
- Create a train interrupt with a circuit condition of :parameter: > 0
- enable read train ID
- connect train station to a lamp ()in debugging it seemed any connection would trigger the issue)
- fuel up the train and let it loose.
the train immediately picks up the train ID signal and attempts the interrupt with it.
I understand why this is happening, to some degree. i mean, the signal is there, and it is > 0. However, given that the use case i see most often with this is a generic interrupt, for going to stations named '[item=coal] Dropoff' and the like, it seems a bit nonsensical to have to engineer around this. like making all of your signals negative values in order to send them to a train.
A couple proposed solutions:
- allow item parameter instead of only signal parameter in interrupt
- automatically ignore the signal that train ID is set to (the T by default)
- Create a small segment of rail with a stop and a locomotive.
- Create a train interrupt with a circuit condition of :parameter: > 0
- enable read train ID
- connect train station to a lamp ()in debugging it seemed any connection would trigger the issue)
- fuel up the train and let it loose.
the train immediately picks up the train ID signal and attempts the interrupt with it.
I understand why this is happening, to some degree. i mean, the signal is there, and it is > 0. However, given that the use case i see most often with this is a generic interrupt, for going to stations named '[item=coal] Dropoff' and the like, it seems a bit nonsensical to have to engineer around this. like making all of your signals negative values in order to send them to a train.
A couple proposed solutions:
- allow item parameter instead of only signal parameter in interrupt
- automatically ignore the signal that train ID is set to (the T by default)