I read in the v0.8.5 patchnotes that station-linked storages are restricted so trucks can't perform the same operation as the train is. I've tested, and this is indeed true.
It's also build-breaking.
Is there a way to combine the reservation systems, to allow trains to ignore cargo reserved by trucks, and vice versa, but still allow both to consider cargo from the same source?
The other limit- that each storage can only be linked to one station- is also build breaking, and actually for the same build- I had one station filling a set of storages, and the other emptying them, with limits/requests set so they would never trigger the other, and they could not ship directly to one another. This was for a construction materials access, allowing me to build & demolish with distributed "mall" locations for the trucks to get stuff from & return it to, making for short response times, but only a single actual production/storage facility, served only by trains (I used two separate stations there too, but they didn't share storages). These changes to linked storages, together, roughly double the minimum size for such a "mall" station pair, making it much harder to tuck out of the way in limited space, and it now also requires far more complex balancer logic (and belt routing) to make it work (due to requiring 4 separate locations for each product- Train in, Train out, Truck in, Truck out, with priority for what goes where, rather than only two, In and Out, connected by a straight belt- or set of parallel belts). I feel like the current system should definitely disallow multiple links from stations performing the same operation, as I've seen builds that had parallel loading stations linked to the same storage (generating endless numbers of trains that weren't aware the space they targeted was already full), but it ought to allow links from opposite stations (one send, one receive) like this, despite the potential for an infinite cargo loop. It's far from the only way to make one of those. Could the above suggested unified cargo reservation system also have one station "see" reservations placed by other stations, and cargo inaccessible to the train (ex. by the "do not export to belts unless above" slider), and therefore make these new restrictions unnecessary?
I imagine this would necessitate a "cargo order" for stations, potentially partially exposed to the player. Direct-attached stations would come first, then manually-linked ones that may or may not have an order of their own.