Difference between revisions of "Hacking"
(Updated description and added Rewiring section) |
|||
(4 intermediate revisions by 2 users not shown) | |||
Line 13: | Line 13: | ||
* '''[[Security Level]]''': Each class of machines exists in three different varieties, rated by security level from 1 to 3. Higher security machines provide greater functionality, but are correspondingly more difficult to hack. | * '''[[Security Level]]''': Each class of machines exists in three different varieties, rated by security level from 1 to 3. Higher security machines provide greater functionality, but are correspondingly more difficult to hack. | ||
− | |||
− | |||
* '''Utilities''': Active [[hackware]] contributes to hacking attempts, most directly by making each hack easier. | * '''Utilities''': Active [[hackware]] contributes to hacking attempts, most directly by making each hack easier. | ||
− | * '''[[System Corruption]]''': Being corrupted decreases the chance of success | + | * '''[[System Corruption]]''': Being corrupted decreases the chance of success (-Corruption/3%). |
− | * '''[[Operator]]s''': Having a network of operators under your control helps bypass | + | * '''[[Operator]]s''': Having a network of operators under your control helps bypass machine security systems, though the benefits decrease with each additional operator. When hacking terminals, one allied operator confers a +10% to the chance of success, while the benefit of each additional operator is halved (+5%, +2%, +1%), with each operator providing no less than +1%. |
=== Process === | === Process === | ||
From your point of view, hacking is simply connecting to a system and choosing/entering commands. However, the system itself responds in three phases: | From your point of view, hacking is simply connecting to a system and choosing/entering commands. However, the system itself responds in three phases: | ||
− | * '''Detection''': Initially your presence is unknown, but with each subsequent action there is a chance your activity will be detected. Detection happens more quickly at higher security machines, and becomes more likely with each failed hack, but can be mitigated by | + | * '''Detection''': Initially your presence is unknown, but with each subsequent action there is a chance your activity will be detected. Detection happens more quickly at higher security machines, and becomes more likely with each failed hack, but can be mitigated by defensive hackware. Accessing the same machine multiple times also increases the chance of detection. |
− | * '''Tracing''': As soon as suspicious activity is detected, the system attempts to locate it. Failing hacks increases the speed of the trace, more quickly for worse failures. If a session is terminated while a trace is in progress, that trace will resume from where it left off if | + | * '''Tracing''': As soon as suspicious activity is detected, the system attempts to locate it. Failing hacks increases the speed of the trace, more quickly for worse failures. If a session is terminated while a trace is in progress, that trace will resume from where it left off if a connection is reestablished. |
* '''Feedback''': Once traced, the system is permanently locked and may attempt to counterattack the source of the unauthorized access, which either causes system corruption or disables connected hackware. | * '''Feedback''': Once traced, the system is permanently locked and may attempt to counterattack the source of the unauthorized access, which either causes system corruption or disables connected hackware. | ||
Line 43: | Line 41: | ||
== Hacking Robots == | == Hacking Robots == | ||
Almost any robot can be hacked. Access a robot's system using either a [[Datajack|melee datajack]] or [[Remote Datajack]]. | Almost any robot can be hacked. Access a robot's system using either a [[Datajack|melee datajack]] or [[Remote Datajack]]. | ||
− | |||
− | |||
=== Factors === | === Factors === | ||
Line 50: | Line 46: | ||
* '''Robot Class''': Certain robot systems are more difficult to hack than others. | * '''Robot Class''': Certain robot systems are more difficult to hack than others. | ||
− | |||
− | |||
* '''Utilities''': Active [[hackware]] contributes to hacking attempts, most directly by making each hack easier. | * '''Utilities''': Active [[hackware]] contributes to hacking attempts, most directly by making each hack easier. | ||
− | * '''[[System Corruption]]''': Being corrupted decreases the chance of success | + | * '''[[System Corruption]]''': Being corrupted decreases the chance of success (-corruption/3%), but a corrupted target increases the chance of success (+corruption/3%). |
* '''[[Datajack]]s''': Multiple successful datajack penetrations gives a +5% hacking bonus for each additional connection (up to +15%). | * '''[[Datajack]]s''': Multiple successful datajack penetrations gives a +5% hacking bonus for each additional connection (up to +15%). | ||
+ | |||
+ | * '''[[Operator]]s''': Having a network of operators under your control helps bypass robot system security, though the benefits decrease with each additional operator. | ||
+ | |||
+ | * '''Destroyed [[Garrison Relay]]s''': Each destroyed relay lowers robot hacking defense. | ||
=== Commands === | === Commands === | ||
* '''PARSE''': Scans the robot's system for useful internal details, including its current level of system corruption and a breakdown of hacking calculations and likely success rates. | * '''PARSE''': Scans the robot's system for useful internal details, including its current level of system corruption and a breakdown of hacking calculations and likely success rates. | ||
− | * '''LINK''': Embeds a program that broadcasts data to Cogmind and all allies via the datajack, helping predict what the robot will do next. This confers a +15% bonus to both targeting and | + | * '''LINK''': Embeds a program that broadcasts data to Cogmind and all allies via the datajack, helping predict what the robot will do next. This confers a +15% bonus to both targeting, damage, and evasion against that robot. While linked, a robot's label and scan window name include an additional indicator: (+). |
* '''REBOOT''': Completely disables the robot for a certain duration (15~25 turns). Rebooting a robot erases its short-term memory, so if you're out of sight when it starts up again it won't know where you went, or even that you were ever there. | * '''REBOOT''': Completely disables the robot for a certain duration (15~25 turns). Rebooting a robot erases its short-term memory, so if you're out of sight when it starts up again it won't know where you went, or even that you were ever there. | ||
Line 74: | Line 72: | ||
=== Defense === | === Defense === | ||
Some robots are capable of remotely protecting others from hacking attempts. Similarly, you can protect your allies from hacking attacks with active defensive hackware. | Some robots are capable of remotely protecting others from hacking attempts. Similarly, you can protect your allies from hacking attacks with active defensive hackware. | ||
+ | |||
+ | === Rewiring === | ||
+ | While a robot is disrupted (usually after taking some forms of EM damage to its core), bump into it to attempt a rewire, which if successful will assimilate it. No additional utilities are required, though the chance of success is improved by offensive hackware. Disrupted allies can be instantly reactivated in the same manner. | ||
+ | |||
+ | The base chance of rewiring success is 10%, or 50% with a [[datajack]], which also automatically succeeds at its penetration roll. | ||
+ | |||
+ | If flying, note that you'll need to switch to some other form of propulsion in order to come down and rewire a target. | ||
[[Category:Game Concepts]] | [[Category:Game Concepts]] |
Latest revision as of 21:24, 1 March 2017
Hacking is the art of interfacing with a robot or machine and commanding it to do something, often in violation of security systems.
In Cogmind there are three types of hacks:
- Common: Most of these are commands native to the system itself, functions and data that Operators and other robots need access to for their work.
- Unauthorized: These are hacks that attack the system itself or abuse it in some way, decidedly not what you’re supposed to be doing there. They are always entered manually--you’ll never see these listed like the others.
- Unique: NPCs will under special circumstances, or for plot purposes, give codes that can be used to achieve unique effects. These would of course always be entered manually.
Hacking Machines
Interactive machines appear in color rather than gray. Access their interface by bumping (moving) into the solid color space containing the representative letter.
Factors
Each function/command at a machine has its own base difficulty to hack, though there are numerous other factors at play in determining your chance of success.
- Security Level: Each class of machines exists in three different varieties, rated by security level from 1 to 3. Higher security machines provide greater functionality, but are correspondingly more difficult to hack.
- Utilities: Active hackware contributes to hacking attempts, most directly by making each hack easier.
- System Corruption: Being corrupted decreases the chance of success (-Corruption/3%).
- Operators: Having a network of operators under your control helps bypass machine security systems, though the benefits decrease with each additional operator. When hacking terminals, one allied operator confers a +10% to the chance of success, while the benefit of each additional operator is halved (+5%, +2%, +1%), with each operator providing no less than +1%.
Process
From your point of view, hacking is simply connecting to a system and choosing/entering commands. However, the system itself responds in three phases:
- Detection: Initially your presence is unknown, but with each subsequent action there is a chance your activity will be detected. Detection happens more quickly at higher security machines, and becomes more likely with each failed hack, but can be mitigated by defensive hackware. Accessing the same machine multiple times also increases the chance of detection.
- Tracing: As soon as suspicious activity is detected, the system attempts to locate it. Failing hacks increases the speed of the trace, more quickly for worse failures. If a session is terminated while a trace is in progress, that trace will resume from where it left off if a connection is reestablished.
- Feedback: Once traced, the system is permanently locked and may attempt to counterattack the source of the unauthorized access, which either causes system corruption or disables connected hackware.
Machines
See a machine's page for the specific functionality of that machine, including indirect hacking (manual commands):
Hacking Robots
Almost any robot can be hacked. Access a robot's system using either a melee datajack or Remote Datajack.
Factors
Each robot command has its own base difficulty to hack, though there are numerous other factors at play in determining your chance of success.
- Robot Class: Certain robot systems are more difficult to hack than others.
- Utilities: Active hackware contributes to hacking attempts, most directly by making each hack easier.
- System Corruption: Being corrupted decreases the chance of success (-corruption/3%), but a corrupted target increases the chance of success (+corruption/3%).
- Datajacks: Multiple successful datajack penetrations gives a +5% hacking bonus for each additional connection (up to +15%).
- Operators: Having a network of operators under your control helps bypass robot system security, though the benefits decrease with each additional operator.
- Destroyed Garrison Relays: Each destroyed relay lowers robot hacking defense.
Commands
- PARSE: Scans the robot's system for useful internal details, including its current level of system corruption and a breakdown of hacking calculations and likely success rates.
- LINK: Embeds a program that broadcasts data to Cogmind and all allies via the datajack, helping predict what the robot will do next. This confers a +15% bonus to both targeting, damage, and evasion against that robot. While linked, a robot's label and scan window name include an additional indicator: (+).
- REBOOT: Completely disables the robot for a certain duration (15~25 turns). Rebooting a robot erases its short-term memory, so if you're out of sight when it starts up again it won't know where you went, or even that you were ever there.
- OVERLOAD: Outright destroys the robot by overloading its core.
- ASSIMILATE: Reprograms the robot to serve you. You can issue general orders, as described in the Allies section.
- MANUAL: Opens an interface that can be used to enter unique commands obtained on your travels.
Defense
Some robots are capable of remotely protecting others from hacking attempts. Similarly, you can protect your allies from hacking attacks with active defensive hackware.
Rewiring
While a robot is disrupted (usually after taking some forms of EM damage to its core), bump into it to attempt a rewire, which if successful will assimilate it. No additional utilities are required, though the chance of success is improved by offensive hackware. Disrupted allies can be instantly reactivated in the same manner.
The base chance of rewiring success is 10%, or 50% with a datajack, which also automatically succeeds at its penetration roll.
If flying, note that you'll need to switch to some other form of propulsion in order to come down and rewire a target.