ROUTER TOKEN

I've thought about the possibilities for configuration right now, and there are certainly some limitations on what we can "program" our stuff to do(see lovesketch2):

Lets you place Router objects or is usable itself(if usable itself it could be one of those repeatable tokens from the radio guys).

The router would send a keyword on a frequency when it receives a certain(or any) keyword on another frequency (or maybe the same).

So basically it would have a CONDITION part and an ACTION part (see lovesketch1) .
If the CONDITION keyword is left blank, all messages broadcasted on the CONDITION frequency would trigger the ACTION message.
If the ACTION keyword is left blank, when the ACTION message is sent, the keyword will be the one received on the CONDITION frequency.

In my opinion, having a tile ocuppied by an object that would only "route" one signal is a price a bit too high, so i guess the thing would be to have an object/token that could "route" several signals at once,i've made a little drawing of 2 possible config screens(see lovesketch1).

With this tool we could...
-If we know the enemies artillery frequency, we can set it up so the power gets routed to the forcefield whenever a message is received on that artillery frequency, or back to turrets if radar sees an enemy closing.
-Setup prox sensors in a more efficient way (see lovesketch2) .
-We could have warning messages into our "radar freq"(the one we usually listen to) routed from prox sensors or perhaps an alarm button(trigger).
-Other cool stuff, i'm sure.

Problems...
-Loops, i guess Eskil could check for looping signals...

lovesketch1:

lovesketch2: