Yes, indeed I think about rewriting this at weekend and also make new drawing.MeduSalem wrote:Well you will have to make another of that "pretty" drawings of yours to explain that to me, ssilk...
Well, see it so: If the system would be perfect it would not make much fun playing it. Really!By the way if a train waits at the requester until it is empty... that's going to be problematic if another requester station needs also resources. If all trains are waiting somewhere then a trainstation might starve to death... else you need exactly as many trains as there are requester stations. If you just have one to many it causes traffic jam because the one that's too much will end up in queue behind a train that is waiting to unload at a requester station. If you have one too less then somewhere a station starves. Also it wouldn't guarantee that 2 or more trains aren't heading for the same requester... so eventually they might all end up hogging one requester station, while all others are starving.
A player that tries this system the first time will come into that situation and he will find solutions of course, cause he is not silly (prove: you already explained some).
It doesn't have a list. No Schedule. The schedule is dynamically created when a train get's it's order. Order is created, when a provider has the items, that a requester needs. The rest (filling with the right amounts, emptying...) is the players task.So bottomline... that doesn't work reliable. A requester station that doesn't need any resources should deactivate itself and be taken out of the list of available target stations to prevent above from happening. Meaning... your trains can't wait there... because once the train station is offline the train will head for the next station in its list.
Again: Provider provides an amount of item X, Requester requests amount of item X. Then order is created: Transport item X from Provider to Requester. A free train is assigned and gets this Schedule:
* Go To Provider, wait until minimum of either requested or provided items in.
* Go To Requester, wait until empty.
* Go To TrainPort and delete schedule.
You see: That logic is pretty simple.
Well, that's the reason, why the train needs to wait until unloaded. It's the best of all compromises, cause the player will get time to solve the problems one after the other. I'm sure, this works much better as expected.Which then obviously is the provider station if you don't have a depot. But then all the trains that aren't needed anymore will start hogging the provider stations again which is with multiple outposts providing resources a problem because all the trains might want to go for the same provider and not equally distributed among all outposts... it's a vicious cycle... that can only be broken if there's a depot scheduled after leaving a requester and making trains wait there until BOTH a requester station and a free provider station is available and dispatch only one train for each request.