Overfilled LTN receiver behaves as provider?
Posted: Sat Jun 01, 2019 4:12 pm
An accidentally disconnected wire caused a requester stop to overfill (since it was only counting the chests for one wagon) and after fixing it I noticed a very strange behavior:
- The requested stop started calling trains as if it was a provider (which of course never loaded since the inserters go the other way and would just time out).
- The station is configured with Iron Plate = -64k, Request Threshold = 32k.
- At the time of this event the chests Iron Plate content was about 160k.
I assume that once -64k+content goes negative again the strange behavior will self-fix itself. Just to be safe I disconnected the wire that goes to the LTN stop lamp and will reconnect it after the chests have drained.
But I am curious. Is this the normal intended behavior? Shouldn't the presence of a Request Threshold in the configuration cause the stop to not even consider acting as a provider?
- The requested stop started calling trains as if it was a provider (which of course never loaded since the inserters go the other way and would just time out).
- The station is configured with Iron Plate = -64k, Request Threshold = 32k.
- At the time of this event the chests Iron Plate content was about 160k.
I assume that once -64k+content goes negative again the strange behavior will self-fix itself. Just to be safe I disconnected the wire that goes to the LTN stop lamp and will reconnect it after the chests have drained.
But I am curious. Is this the normal intended behavior? Shouldn't the presence of a Request Threshold in the configuration cause the stop to not even consider acting as a provider?