{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidyfflkflzhg2aw7lutqq4rmtklw7spukqj5bqufuowiqrriszlki",
    "uri": "at://did:plc:i7budt2wflrcfy6jtvfocbix/app.bsky.feed.post/3mfv2roetd272"
  },
  "path": "/viewtopic.php?p=1278302#p1278302",
  "publishedAt": "2026-02-27T19:24:33.000Z",
  "site": "https://www.tt-forums.net",
  "tags": [
    "JGR"
  ],
  "textContent": "> Hey JGR,\n>\n>\n> [del]since the last update,[/del ] I only noticed the “dispatch slot” issue when loading an older save game. It seems to have been missing for quite some time. I would still like to have it back. Otherwise, I would have to make a lot of adjustments to all my old games. I miss the option to select “Dispatch Slot” for train orders.\n> Selecting “Dispatch Slot” helps me send trains to the depot for cleaning after one day of circulation.\n\nThis condition is only shown for order lists which actually have dispatch schedules.\n\n\n> I think the “Timetabel state” is very good. Is it possible to set the maximum speed of the train here? For example, reduce the current maximum speed by 10% or 20% (also observe speed limits indicated by signals).\n\nNo, this is a conditional order type, you can set a speed limit for orders in the timetable window.\n\n\n> Is it possible to create a +1 day option here?\n> If I select a time => 2329, and a vehicle arrives (due to a delay) at 0012, then this rule no longer applies. Changes at the end of the day (freight trains often run overnight and can then use passenger routes) cause difficulties.\n> It would be sufficient to be able to set a range between two times (=> <= 2329 - 0300).\n> Screenshot 2026-02-27 085306.png\n\nYou can just use two conditional orders for this.\n\n\n> Is there a chance for my second patch \"progsignals_use_lateness_counter\" to be reviewed or integrated?\n> I still miss this feature. But if “Timetable state” were to include signal-dependent speed reduction, that would also be sufficient.\n\nIf I get time I can look into finishing this, though I remain unconvinced that this is really a good approach.\nThat said, if the timetable state conditional order is sufficient, then you can just use that and a speed reduction in the timetable without needing any new features, and this sounds like it would make more sense with what you are trying to do anyway.\n\nStatistics: Posted by JGR — 27 Feb 2026 19:24\n\n* * *",
  "title": "OpenTTD Development • Re: JGR's Patch Pack",
  "updatedAt": "2026-02-27T19:24:33.000Z"
}