LTN 2.7.0 bug: scheduler uses item count instead of priority

[half a cat]

When LTN chooses a provider station, it ignores priority and chooses the provider with the largest item count. I believe that LTN should choose the highest-priority provider that can fulfill a request.

I found this bug because my factory had a station for recycling byproducts that was never being used, causing the factory to back up. Although the byproduct station had a higher priority than the new product station, trains would only go to the byproduct station if I made the new product station appear to be empty (by disconnecting circuit wires).

The attached save file demonstrates the behavior. In the save file, there is a high priority provider and a low priority provider. These two stations have the same LTN signals except for priority. The train always goes to the low priority provider. By adjusting the amount of fluid, you can make it go to the high priority provider instead, showing that LTN is scheduling based on the item count and not based on the priority.

[hgschmie]

Thanks for the report and save; any chance you can add it to the github issues? I rarely look at the forums.

-h

[half a cat]

Alright, I've added it as a bug on github.

[hgschmie]

Thank you. To close the loop here as well, it is not a bug: https://github.com/hgschmie/factorio-Lo ... /issues/65

Screenshot 2026-05-24 at 21.39.31.png (367.83 KiB) Viewed 33 times

In the example, you set the depot priority for the provider station. You need to use the provide priority setting on the right side. I changed this to "1" and now it only goes to the high priority station.

I am the first one to admit that the LTN Combinator UI is not the most intuitive (and that the depot prio setting should probably be grayed out if a station is not a provider) but this is an UI issue. LTN works fine if it sees the right signals.

It may be good to flag that to the author of the LTN combinator: https://mods.factorio.com/mod/LTN_Combinator_Modernized