Hmm?Optera wrote:What you say doesn't match with the log you provided. The log clearly shows alternating iron and copper ore shipments to Ore dropoff, Crellas and Damian Mulligan.
Line 29: iron-ore order is made, Whiro>>Ore dropoff
Line 62: copper-ore order is made, Matt>>Ore dropoff
Line 64: iron-ore delivery is made, Whiro>>Ore dropoff
???: copper-ore delivery never happens.
Do a ctrl-f on "Creating Delivery"; there's not a single copper delivery made during that log. Also, I was looking at the depot and the schedules of trains leaving... nobody went to copper. I explained why in my last post.
My request is based on what I want to receive at the train station. I'd expect the trains to do their best to satisfy the requests to the best of their ability; I don't want to deliberately force iron to stick around at the station just so the scheduler can decide to use copper. I get what you're saying, but right now if a station requests multiple items from different locations, only one item will ever be fulfilled as long as the request remains active. And which item is fulfilled is currently undefined behavior. I'm just suggesting that this undefined behavior be replaced with the same consistent set of rules used for choosing a provider station, which is what I did in the pull request.Optera wrote:If it's never filling to the point where requested amounts are satisfied your throughput is too low and no amount of coding on my end will help you.
Haha, no can do! I can't automate stop renaming, and everything that can't be automated must die.Optera wrote:PS: You should rename your stops to meaningful, unique names.
Oh fuck. I kinda hoped they tacked on numbers or something at the end when they ran out. Well, looks like I'm in the market for a circuit-based trainstop renaming mod! (good thing justarandomgeek just released one, I'll need to check it out)Optera wrote:Generated Backer Names are NOT unique and will mess up train schedules.