Allow a single rail signal to connect across multiple parallel rails (e.g., in yard/stacker layouts) so they share the same signal block logic.
This would make the multi-lane layouts shown in Friday Facts #377 – New new rails fully usable.
Currently, these new rail designs look amazing — but don’t function as intended for stackers, because each rail acts as a separate block.
(Blueprint ghost layout – visually clear, but signals don't link blocks together)
(In-game version of new curved rail layout inspired by FFF #377) What?
I’m suggesting that when building rail yards or stackers using the new 2.0 curved rails:
- A single rail signal placed before the fan-out section (on the main line) can be configured to apply to all parallel rails in the block.
- The block highlight would appear across all connected lanes.
- Trains would treat all these lanes as one shared block.
- If all lanes are occupied or blocked, the signal would turn red — just like normal.
Why?
The new rails shown in FFF #377 are excellent visually and were clearly intended for rail yard aesthetics.
But functionally, they behave as separate blocks per lane, making them:
- Unusable for unified signaling.
- Tedious to blueprint or automate.
- More cosmetic than practical.
- Let stackers and yards behave properly.
- Avoid complex signal micro-managing.
- Let us use the beautiful rail fan-outs as intended.
- A new "shared signal" entity.
- A toggle on signals for multi-lane mode.
- Or automatically linking lanes built in parallel (if safe).