Logic Broadcast Module

[TheKingOfSpace]

Like the Wireless module, but does not need to be connected beforehand, and is not restricted to one link.

Consists of a Broadcaster and a Broadcast Receiver module.

Each connects to activation modules, a Broadcast module will activate all Receivers with the same number of connected and active activators.

The Receiver will activate/deactivate an adjacent activator if it receives a matching signal, allowing you to use it as part of your logic system.

Signals sent would normally be faction-locked; you could connect a permission module to send/receive public signals.

 

[jayman38]

"Frequency" based on activated, connected activation blocks? A wonderfully Starmade-ian solution to keep the frequency private.

Bonus: Allows frequency changes via logic. Excellent.


Secondary suggestion: I'd recommend a bi-directional transceiver block and the ability to link a display block to "simulate" large numbers of activation blocks by simply holding a number, which would correspond to that number of activation blocks, both sub-suggestions to save space on smaller builds. (E.g. Drones/fighters, Turrets, or logic Doors.) The benefit of using multiple activation blocks over this smaller, "tighter" frequency design: the ability to use logic to change frequency on the fly.

Some lower-count frequencies may become de-facto standards for certain logic applications, such as using "frequency" 21 for standard public logic doors, or 23 for activating Bobby AI in a turret, or 11-20 for private doors.

 

[nightrune]

One of the few times I toot my own horn. Chat/Channel Block

 

[kiddan]

Would you be able to place display blocks and rails beside broadcasting modules to alter all slaved rails and displays on the same frequency? If so, I'm in!

 

[nightwalker_007]

I already suggested this: Radios + Display

Basically it uses displays and search functions to allow any number of commands to be sent across a sector. It also supports encryption keys, which, if a transmitter is discovered, could be recovered by a 3rd party. Also it could be used as an in-game messaging system which would be a little more immersive than the email system (and also allow for game-wide bulletin boards). It also would have a limited broadcast range and require power, which would make it necessary for relay stations for very long distance transmissions (eg. multiple galaxies, or to relay messages from smaller ships to further reaches of the galaxy).

This suggestion would only need one extra block

As for display blocks attached to rails, see my suggestion here: Displays connected to Rail/Rail docker to send commands to/from docked entities & beamed logic block

The idea here is that a station and docked entity can exchange multiple commands back and forth from each other using one shared, or two displays (for incoming and outgoing messages). This could allow for advanced docking sequences to automate loading/unloading and docking/unlocking sequences, as well as sending general station messages for player to read (eg. "Welcome to Asteroid Station Six! Brown corridors lead to common areas, yellow leads to the infirmary.").

This suggestion requires NO extra blocks.

Like the Wireless module, but does not need to be connected beforehand, and is not restricted to one link.

Consists of a Broadcaster and a Broadcast Receiver module.

Each connects to activation modules, a Broadcast module will activate all Receivers with the same number of connected and active activators.

The Receiver will activate/deactivate an adjacent activator if it receives a matching signal, allowing you to use it as part of your logic system.

Signals sent would normally be faction-locked; you could connect a permission module to send/receive public signals.