Well, it is difficult to say out of one's head if a journey will take 8000 or 9000 ticks.
That's what the autofill feature is for.
The problem is, when autofilling the timetable in ticks, the timetable will NOT be filled with real travel lengths, for example:
Assume daylength 16, then 1 day = 1,184 ticks.
Train goes A -> B in 1,800 ticks ~ 2 days.
It fills num_days * ticks_per_day into the timetable when autofilling.
In this case, that becomes 2 * 1,184 = 2,386.
2,386 - 1,800 = 586 ticks of inaccuracy with no way of telling how you should adjust the timetable in game.
I think it would be enough to either:
-modify timetable autofilling so that it fills in real travel times, i.e. 1,800 instead of 2,386 ticks,
or:
-call 74 ticks a timetable-unit(TTU)(*insert smart name here*) and have timetabling use that as a unit. That would mean that timetables would remain constant even if you change daylength mid-game (i.e. user wants to rush through an era boring for him, then slows time down for Age of Fun)
Personally, I think the second solution should not be hard to code, wouldn't break anything and the numbers would be simpler to manage(users don't wantto mess with hundreds and thousands as it is with ticks)
What do you think of this?
