| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| programs:parasite [2020/06/30 21:51] – andrew | programs:parasite [2020/08/21 13:26] (current) – andrew |
|---|
| Parasite can work well in low-PWR strategies, or it can free up your PWR for other uses such as [[Oracle]], [[:weapons:Volt Disruptors]] or [[:agents:Archive Prism]]'s [[:items:Holo Projection Mesh]] which can consume a lot of PWR. | Parasite can work well in low-PWR strategies, or it can free up your PWR for other uses such as [[Oracle]], [[:weapons:Volt Disruptors]] or [[:agents:Archive Prism]]'s [[:items:Holo Projection Mesh]] which can consume a lot of PWR. |
| |
| When you infect an [[:mainframe devices:Security Cameras#inactive cameras|inactive camera]] which comes online at [[:alarm level]] 1 (or alarm level 2 in [[:modes:Beginner]] mode), its firewalls are broken at the start of your //next// turn, but the camera activates before then at the start of the //enemy// turn. Any agent in vision of the camera will be seen by it before Parasite breaks its firewalls, triggering at least one guard to [[:guard behaviour#investigating|investigate]]. | When you infect a [[:mainframe devices:Security Camera]] while it is [[:rebooting]], such as an [[:mainframe devices:Security Cameras#inactive cameras|inactive camera]] that is coming online, its firewalls are broken at the start of your //next// turn, but the camera activates before then at the start of the //enemy// turn. Any agent in vision of the camera will be seen by it before Parasite breaks its firewalls, causing nearby guards to [[:guard behaviour#investigating|investigate]]. |
| |
| When any devices are infected, beware of triggering [[:daemons:Fractal]], accessing the [[:mainframe devices:Server Terminal#Primary Server Terminal]] in a [[:missions:Server Farm]] mission, using [[Taurus]], or [[:KO|knocking out]] a [[:guards:Modded]] guard --- these can install a random [[:daemons:|daemon]] on an infected device, committing you to triggering that daemon, unless the device already has a different daemon installed. | When any devices are infected, beware of triggering [[:daemons:Fractal]], accessing the [[:mainframe devices:Server Terminal#Primary Server Terminal]] in a [[:missions:Server Farm]] mission, using [[Taurus]], or [[:KO|knocking out]] a [[:guards:Modded]] guard --- these can install a [[:daemons:|daemon]] on an infected device, committing you to triggering that daemon, unless the device already has a different daemon installed. |
| |
| When hacking devices with daemons, it is sometimes necessary to infect devices which have the same number of firewalls in a particular order, to mitigate the daemons' effects. Devices with [[:daemons:Fractal]], [[:daemons:Rubiks]] and [[:daemons:Castle]] should normally be infected after others, so the others will finish hacking before the daemon is triggered; devices with [[:daemons:Echo]] should normally be infected //before// others, so that Echo won't recapture them immediately. | When hacking devices with daemons, it is sometimes necessary to infect devices which have the same number of firewalls in a particular order, to mitigate the daemons' effects. Devices with [[:daemons:Fractal]], [[:daemons:Rubiks]] and [[:daemons:Castle]] should normally be infected after others, so the others will finish hacking before the daemon is triggered; devices with [[:daemons:Echo]] should normally be infected //before// others, so that Echo won't recapture them immediately. |
| |
