So with the recent update we can send cargo through rails, which got me thinking.
Why can't we use a block to adapt signals through rails, without triggering standard rail behavior for signals?
So my suggestion is, a logic block that when slaved to a rail or docker will mirror that signal to a logic block slaved on the other side.
Or more visually,
Adaptor <-> rail <-> docker <-> Adaptor.
This would allow arbitrary signals between docked systems and ships to trigger a variety of behaviors, and even saves on wireless logic if it can be implemented.
For example, a cargo pallet could trigger a closing/securing function on a freighter, or have additional logic on it triggered from the station/freighter without fussing around.
Alternatively a pilot could set up a modular system via a docked entity that they can trigger via inner ship remotes, without needing to manually hook up the wireless blocks.
Literally plug and play.
Why can't we use a block to adapt signals through rails, without triggering standard rail behavior for signals?
So my suggestion is, a logic block that when slaved to a rail or docker will mirror that signal to a logic block slaved on the other side.
Or more visually,
Adaptor <-> rail <-> docker <-> Adaptor.
This would allow arbitrary signals between docked systems and ships to trigger a variety of behaviors, and even saves on wireless logic if it can be implemented.
For example, a cargo pallet could trigger a closing/securing function on a freighter, or have additional logic on it triggered from the station/freighter without fussing around.
Alternatively a pilot could set up a modular system via a docked entity that they can trigger via inner ship remotes, without needing to manually hook up the wireless blocks.
Literally plug and play.