Differences

This shows you the differences between two versions of the page.

--- daemons:validate [2020/05/04 23:14] – created storm
+++ daemons:validate [2020/05/19 22:11] (current) – andrew
@@ Line 1: / Line 1: @@
-===== Validate =====
+====== Validate ======
+[{{ validate.png|Validate icon}}]
-This article is a stub.
+**Validate** is a [[:daemons:|daemon]] which spawns an [[:guards:Enforcer]] at a [[:facility#guard entrance]]. The Enforcer enters the facility [[:guard behaviour#alerted]].
+===== Strategy =====
+Validate is widely regarded as the worst daemon to trigger. Adding another guard to the level is usually more harmful than the effect of any other daemon; but it's worse than that, because the guard is an alerted Enforcer who throws [[:guards:Enforcer#scan grenades]] to detect your agents behind [[:cover]]. The effect is so severe that the mere //possibility// of Validate should make you think twice before hacking a device with an unknown daemon.
+It is therefore usually best to avoid triggering Validate, especially early in a mission. You can use [[:programs:Hunter]] or [[:programs:Taurus]] to remove Validate from a device you need to hack, or if appropriate use an [[:items:EMP Pack]] or [[:agents:Dr. Xu]]'s [[:augments:Subdermal Tools]] to temporarily disable the device instead of hacking it.
+If you must hack a device with Validate --- or if you cannot resist the payoff of doing so --- then you should normally wait until you have completed any other mission objectives, found the [[:facility#exit room]], and made a plan to get your agents there. If the [[:facility#guard entrance|guard entrances]] are near where your agents need to be, it may be a good idea to put agents next to them, ready to [[:KO|knock out]] and [[:KO#pinning|pin]] the Enforcer. Alternatively, if you have an agent in place before triggering Validate, you can distract him by [[:strategy:sprint toggling]].
-{{tag>incomplete}}

Invisible, Inc. community wiki

User Tools

Site Tools

Differences

Page Tools