{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihlevw5u34k7kyf4x27iglo3zmth5zz7w5hojpxebiwhkctpzxm64",
    "uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mfburiokfcb2"
  },
  "path": "/viewtopic.php?p=449663#p449663",
  "publishedAt": "2026-02-20T09:41:33.000Z",
  "site": "https://forum.luanti.org",
  "tags": [
    "https://git.bananach.space/luaatc_envs. ... auto_yards",
    "Maverick2797"
  ],
  "textContent": "> Speaking of usecases, lemme ask you. I found an, I think, undocumented, and probably unused, feature when looking at the wagon properties UI that has buttons for Prv/Next FC. I see in the code, though didn't find it in docs, that we can supply a sequence of FCs separated by ! reversed with ;(iirc) but this is not used anywhere I could find. Afaik, nothing in the basic mod steps through the sequence. I am thinking of making the feature user-friendly, but I cannot come up with a usecase that is beginner-friendly that would not be easier and more fun by just doing something like using two wagons, or some other simple mechanic we already have. Any ideas for a usecase that is beginner-friendly and fun for this?\n\nNot sure about beginner use cases as once you start using FCs enough to have multiple of them in a single wagon you should be fairly familiar with how Advtrains works, but I've used multi-FC in wagons across a small network of automatic yards, using LuaATC's split_at_fc() and step_fc() to control where to sort the wagons (env code at https://git.bananach.space/luaatc_envs. ... auto_yards\n\nstep_fc() is currently the main usecase for ! separation and ? reversing. FCs could also be used to control a splitting passenger service by having wagons 1-nwith eg FC longline and wagons n+1-trainlength as FC shortline, either to be collected by a returning train or departing the other way with a trailing loco.\n\nStatistics: Posted by Maverick2797 — Fri Feb 20, 2026 09:41\n\n* * *",
  "title": "Mod Releases • Re: [Mod] Advanced Trains [advtrains] [2.8.0]",
  "updatedAt": "2026-02-20T09:41:33.000Z"
}