Station end custom default wait conditions.
Moderator: ickputzdirwech
-
- Manual Inserter
- Posts: 4
- Joined: Tue Oct 11, 2016 6:01 am
- Contact:
Station end custom default wait conditions.
A simple request, hopefully. But I would like the ability to set the wait condition at the STATION end, and whenever a train is set to go to that station, it will put the wait conditions you set there automatically. To be clear, the station isn't responsible for sending out the train instead of the train's timetable, it just copies what it has to the train when you put it in the timetable, so you can edit it if you want there. This would ease up on the number of clicks, make it a lot faster and easier when working with multiple trains, and/or sending trains to stations that are intended to have a lot of traffic.
Re: Station end custom default wait conditions.
For me this sounds over-complicated.
How about "routes": Define a route and assign it to trains as schedule. If you change the route it changes for all assigned trains.
How about "routes": Define a route and assign it to trains as schedule. If you change the route it changes for all assigned trains.
Cool suggestion: Eatable MOUSE-pointers.
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
-
- Manual Inserter
- Posts: 4
- Joined: Tue Oct 11, 2016 6:01 am
- Contact:
Re: Station end custom default wait conditions.
I see where your going with routes, and that may turn out to be a better idea. But I would argue that would be more complex than my idea. For routes, I would assume that would require another gui layer specific for routes. Plus how would the schedule system we have now interact with defined routes? Can we copy paste routes, and edit them for a new route with minor changes. What if we want a train with just a detour that other trains don't need? Do we have to use a new route for that? A major advantage of your idea though is in mining operations or major production changes. "Oh no that mine is out, time to just change this one thing, and ALL the trains will work. No waiting for them to arrive here so I can copy pasta." This is a great thing.ssilk wrote:How about "routes": Define a route and assign it to trains as schedule.
However, I think putting a new tab in the stations we place now that is nearly identical to the schedule tab we have for trains, would make more sense in keeping it simple. Then, for instance, when you schedule the station with "Wait till full or Inactivity 5 sec or Wait 30 sec" you just have to select that station in the train's schedule, and it will copy it to the train. If you want more trains with the same schedule, after your done with one, you can copy paste it to other trains like you do now. This builds on the old system, without actually adding anything really new, and reducing the tedium and effort to managing a fair to large number of trains. I guess a major thing with this setup though is that the station schedule would have to be the same for all stations using the same name, or that could get confusing, cause it simply copies what the station has to the train. If there was a mismatch, which would it use?
Mockup
Either way @ssilk, I appreciate the reply and love to debate about game mechanics and such (to the point I don't know why I'm not on here all the time >.<)Re: Station end custom default wait conditions.
I love this idea - I almost never have trains visiting the same station with different wait conditions: although if there was an option to not use it that would be great: eg trains default to "Station conditions", but you can still change it to other conditions manually.
Routes would be great though, ideally both!
Routes would be great though, ideally both!
Re: Station end custom default wait conditions.
Well, I thought a bit about your idea and it would be really simple to create a mod, that does about this: It copies a schedule into a train, when stopped on a train stop.
Idea in detail:
Some new entity. I call it "schedule copier".
This is placed as near as possible to a train stop. It auto-connects to that train stop and gets a software-event, if a train comes in and stops.
In this case it looks up for a the next single loco in vicinity around. I think just to some short piece of rail with a locomotive on it; the single loco needs to be switched to "manual". That locomotive is the user-interface for this idea, cause the schedule of that is then just copied into that of the stopped train.
That's it.
That idea can be enhanced of course, but for a first testing this could be programmed down in a "long afternoon".
Idea in detail:
Some new entity. I call it "schedule copier".
This is placed as near as possible to a train stop. It auto-connects to that train stop and gets a software-event, if a train comes in and stops.
In this case it looks up for a the next single loco in vicinity around. I think just to some short piece of rail with a locomotive on it; the single loco needs to be switched to "manual". That locomotive is the user-interface for this idea, cause the schedule of that is then just copied into that of the stopped train.
That's it.
That idea can be enhanced of course, but for a first testing this could be programmed down in a "long afternoon".
Cool suggestion: Eatable MOUSE-pointers.
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...