| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| daemons:fractal [2020/05/22 23:32] – [Strategy] andrew | daemons:fractal [2020/06/21 01:00] (current) – [Fractal 2.0] andrew |
|---|
| [{{ fractal.png|Fractal icon}}] | [{{ fractal.png|Fractal icon}}] |
| |
| **Fractal** is a [[:daemons:|daemon]] which, when triggered, installs daemons on 2 unhacked [[:mainframe devices:]]. The devices, and the daemons installed on them, are selected randomly. The locations of these devices are also revealed to the player, if they have not already been explored. | **Fractal** is a [[:daemon]] which, when triggered, installs daemons on 2 unhacked [[:mainframe devices:]]. The devices, and the daemons installed on them, are selected randomly. The locations of these devices are also revealed to the player, if they have not already been explored. |
| |
| Fractal cannot install daemons on devices which have already been hacked, or devices which already have daemons installed. However, it can install daemons on devices which are [[:mainframe devices:#rebooting]], on [[:mainframe devices:Security Camera#inactive cameras|inactive Security Cameras]], and on [[:mainframe devices:Corporate Safes]] or other devices that have been looted without being hacked. If there are fewer than 2 eligible devices, then Fractal installs fewer than 2 daemons. | Fractal cannot install daemons on devices which are currently controlled by the agency, or devices which already have daemons installed. However, it can install daemons on devices which are [[:rebooting]], on [[:mainframe devices:Security Camera#inactive cameras|inactive Security Cameras]], and on [[:mainframe devices:Corporate Safes]] or other devices that have been looted without being hacked. If there are fewer than 2 eligible devices, then Fractal installs fewer than 2 daemons. |
| |
| ===== Fractal 2.0 ===== | ===== Fractal 2.0 ===== |
| [{{ fractal_2.0.png|Fractal 2.0 icon}}] | [{{ fractal_2.0.png|Fractal 2.0 icon}}] |
| |
| **Fractal 2.0** is an [[:daemons:#archdaemons|archdaemon]] which can occur from [[:mission difficulty#mission difficulty 5]] and onwards in [[:modes:Endless]] modes. It installs daemons on all [[:mainframe devices:]] at the start of the mission. | **Fractal 2.0** is an [[archdaemon]] which can occur from [[:mission difficulty#mission difficulty 5]] and onwards in [[:modes:Endless]] modes. It installs daemons on all [[:mainframe devices:]] at the start of the mission, including [[:mainframe devices:Security Cameras]] and other devices which normally would never have a daemon initially installed. |
| |
| ===== Strategy ===== | ===== Strategy ===== |
| Fractal is riskier when you are using [[:programs:Parasite]], as it may install daemons on devices you are already committed to hacking. If possible, avoid triggering Fractal while hacking other devices using Parasite, unless those other devices already have daemons. Fractal and Fractal 2.0 also make [[:programs:Oracle]] more dangerous, as they can install daemons on [[:mainframe devices:Security Cameras]], which otherwise typically don't have daemons. | Fractal is riskier when you are using [[:programs:Parasite]], as it may install daemons on devices you are already committed to hacking. If possible, avoid triggering Fractal while hacking other devices using Parasite, unless those other devices already have daemons. Fractal and Fractal 2.0 also make [[:programs:Oracle]] more dangerous, as they can install daemons on [[:mainframe devices:Security Cameras]], which otherwise typically don't have daemons. |
| |
| In a mission with Fractal 2.0, it is usually essential to find and hack the [[:mainframe devices:Databases#Daemon Database]] quickly. It will not be feasible to use [[:programs:Hunter]] or [[:programs:Taurus]] to avoid daemons entirely, so save these for the worst daemons. If possible, [[:strategy:exploration|explore]] the whole facility to discover what daemons are installed on each device, perhaps using [[:items:Cloaking Rigs]] to avoid hacking cameras, and use this information to plan which devices to hack in what order. Some daemons are best triggered together so their durations overlap; for example, [[Paradox]], [[Modulate]] and [[Portcullis]] together are no worse than Paradox alone. You can also avoid daemons using [[:items:EMP Packs]] or [[:agents:Dr. Xu]]'s [[:augments:Subdermal Tools]] to disable certain devices without hacking them. | In a mission with Fractal 2.0, it is usually essential to find and hack the [[:mainframe devices:Daemon Database]] quickly. It will not be feasible to use [[:programs:Hunter]] or [[:programs:Taurus]] to avoid daemons entirely, so save these for the worst daemons. If possible, [[:strategy:exploration|explore]] the whole facility to discover what daemons are installed on each device, perhaps using [[:items:Cloaking Rigs]] to avoid hacking cameras, and use this information to plan which devices to hack in what order. Some daemons are best triggered together so their durations overlap; for example, [[Paradox]], [[Modulate]] and [[Portcullis]] together are no worse than Paradox alone. You can also avoid daemons using [[:items:EMP Packs]] or [[:agents:Dr. Xu]]'s [[:augments:Subdermal Tools]] to disable certain devices without hacking them. |
| |
| Fractal can occasionally be beneficial by revealing the locations of important devices; it may also reveal the location of an unexplored [[:mainframe devices:Security Camera]], allowing you to hack it to gain vision on a new area. Both Fractal and Fractal 2.0 also give more opportunities to benefit from [[:agents:Central]]'s [[:augments:Antiviral Proxy]] augment. | Fractal can occasionally be beneficial by revealing the locations of important devices; it may also reveal the location of an unexplored [[:mainframe devices:Security Camera]], allowing you to hack it to gain vision on a new area. Both Fractal and Fractal 2.0 also give more opportunities to benefit from [[:agents:Central]]'s [[:augments:Antiviral Proxy]] augment. |
| |
