Difference between revisions of "MPC - Command relay"
From Perpetuum
DEV Gargaj (talk | contribs) m (1 revision: import #2) |
DEV Gargaj (talk | contribs) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Command relays extend the range of the network control flow. They don't consume energy and once they're connected they pipe through your commands. In a case when a command relay is directly connected to a main terminal the terminal | + | [[Image:Icon pbs control tower.png|right|nolink]] |
| + | Command relays extend the range of the network control flow. They don't consume energy and once they're connected they pipe through your commands. In a case when a command relay is directly connected to a main terminal the terminal becomes unattackable. Agents first have to disable the command relay then they can proceed to attack the main terminal. | ||
| + | |||
| + | '''Important fact:''' this protection mechanism works regardless of the connection direction. | ||
[[MPC_-_Main_terminal|< MPC - Main terminal]] | [[Lexicon|Table of contents]] | [[MPC_-_Reactor|MPC - Reactor >]] | [[MPC_-_Main_terminal|< MPC - Main terminal]] | [[Lexicon|Table of contents]] | [[MPC_-_Reactor|MPC - Reactor >]] | ||
| + | |||
| + | [[Category:MPC nodes]] | ||
Latest revision as of 02:39, 6 January 2013
Command relays extend the range of the network control flow. They don't consume energy and once they're connected they pipe through your commands. In a case when a command relay is directly connected to a main terminal the terminal becomes unattackable. Agents first have to disable the command relay then they can proceed to attack the main terminal.
Important fact: this protection mechanism works regardless of the connection direction.
