| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| missions:vault [2020/06/25 16:53] – [Deposit Boxes] andrew | missions:vault [2020/07/26 10:37] (current) – andrew |
|---|
| | [[:prefabs:Vault 3]] | [[:guards:Captain]] \\ 2 [[:mainframe devices:Sound Bugs]] | Vault Terminal \\ 4 chests of Deposit Boxes \\ | 2 Secure Cases | | | [[:prefabs:Vault 3]] | [[:guards:Captain]] \\ 2 [[:mainframe devices:Sound Bugs]] | Vault Terminal \\ 4 chests of Deposit Boxes \\ | 2 Secure Cases | |
| |
| The Vault mission objective is optional; if you find the [[:facility#exit room]] and try to leave before looting the vault, you will be warned by a dialogue box, but this only asks you to confirm that you want to leave. | The Vault mission objective is optional; if you find the [[:facility#exit room]] and try to leave before looting the vault, you will be warned by a dialog box, but this only asks you to confirm that you want to leave. |
| |
| ===== Vault Terminal ===== | ===== Vault Terminal ===== |
| In response to the agency hacking either the Vault Terminal or a Secure Case, the corporation //usually// brings in reinforcements --- an [[:guards:Enforcer]] spawns at a random [[:facility#guard entrances|guard entrance]], and is [[:guard behaviour#interest point|sent towards]] the hacked device. The security response happens at most once in the mission; once it has been triggered, hacking more devices does not bring more Enforcers. | In response to the agency hacking either the Vault Terminal or a Secure Case, the corporation //usually// brings in reinforcements --- an [[:guards:Enforcer]] spawns at a random [[:facility#guard entrances|guard entrance]], and is [[:guard behaviour#interest point|sent towards]] the hacked device. The security response happens at most once in the mission; once it has been triggered, hacking more devices does not bring more Enforcers. |
| |
| The response is not //always// triggered by hacking one of these devices. Specifically, the Enforcer spawns when you hack the Vault Terminal or a Secure Case using a [[:programs:breaker]] program which breaks the [[:firewalls]] immediately, and which breaks the exact number of firewalls the device has when the program is used. This means the Enforcer does not spawn if you: | The response is not //always// triggered by hacking one of these devices. Specifically, the Enforcer spawns when you hack the Vault Terminal or a Secure Case using a [[:programs:breaker]] program which targets a specific device, breaks its [[:firewalls]] immediately, and breaks the exact number of firewalls the device has when the program is used. This means the Enforcer does not spawn if you: |
| |
| * Use an [[:items:EMP Pack]], [[:agents:Dr. Xu]]'s [[:augments:Subdermal Tools]], or the program [[:programs:Fool]] to disable the Secure Cases. | * Use an [[:items:EMP Pack]], [[:agents:Dr. Xu]]'s [[:augments:Subdermal Tools]], or the program [[:programs:Fool]] to disable the Secure Cases. |
| * Hack using [[:items:Buster Chips]] or the [[:items:Prototype Chip]]. | * Hack using [[:items:Buster Chips]] or the [[:items:Prototype Chip]]. |
| * Hack using a program which breaks more firewalls than the devices have when the program is used. | * Hack using a program which breaks more firewalls than the devices have when the program is used. |
| | * Hack using [[:programs:Data Blast]], which does not target //one specific// device, even if only one device is in its area of effect. |
| * Hack using [[:programs:Parasite]] or [[:programs:Parasite 2.0]], which do not //immediately// break firewalls. | * Hack using [[:programs:Parasite]] or [[:programs:Parasite 2.0]], which do not //immediately// break firewalls. |
| |
| In Vaults protected by an [[:mainframe devices:Emitter]], the security response is never triggered by hacking its [[:mainframe devices:Power Supply]]. | The security response is never triggered by hacking the [[:mainframe devices:Power Supply]] or [[:mainframe devices:Sound Bugs]] protecting the Vault room. |
| |
