Re: What are the priorities for the train leave conditions?
Posted: Wed Sep 07, 2016 1:35 am
Excellent, if you don't think this is useful, make a suggestion for this stuff (or add something on the suggestions already made). But don't come here and tell me this is all completely useless and your idea is so much better. If you really think your idea is so great, go convince the devs it is. Tip: don't connect the rails, that is silly. Give the train stop an option to read the train contents (the same way a belt has such an option for its own contents)siggboy wrote:It's certainly not worth the trouble to add parenthesizing and an appropriate UI for it.
As I've said before, the leave conditions don't really make train stations a lot more powerful than they were in 0.12. Even if you only had the "circuit condition" and the possibility to look into train wagons (connectable rails), you could do everything that you can do right now (and more) with reasonable effort without the need for special UI and all sorts of fine-grained conditions.
E.g.: "item count" = connect rails to station, use circuit condition; "train full / empty" = same if the rails output status signals that signify full (or empty) wagons; "inactivity" = counter that resets on wagon content change; "time passed" = simple counter
Nothing of this requires more than 2 combinators if you have connectable rails that provides reasonable outputs. You can also parenthesize to your heart's content, and even blueprint your "expressions" for re-use and sharing.
Also, show me a leave condition with more than, say, 4 terms and I'll show you that it's overengineered. That leaves simple expressions which don't require parenthesizing.
If you want powerful train routing you need "go to" or "jump to" inputs, i.e. you number the train stations on the schedule and then take the next stop from an input to the train station. So the trains won't be forced to follow a fixed route.
In short, I don't really care how fancy it is to tell the train (not) to leave, as long as I can't tell it WHERE to go after it leaves.
Note: I, too, would be much happier with the ability to dynamically set the next train stop, but I think that I saw that a dev / moderator didn't really like the idea.