This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
daemons:castle [2020/05/20 12:23] – andrew | daemons:castle [2022/09/22 16:51] (current) – andrew | ||
---|---|---|---|
Line 2: | Line 2: | ||
[{{ castle.png|Castle icon}}] | [{{ castle.png|Castle icon}}] | ||
- | **Castle** is a [[:daemons:|daemon]] which, when triggered, raises the [[: | + | **Castle** is a [[:daemon]] which, when triggered, raises the [[: |
Castle is found in the [[: | Castle is found in the [[: | ||
Line 9: | Line 9: | ||
[{{ castle_2.0.png|Castle 2.0 icon}}] | [{{ castle_2.0.png|Castle 2.0 icon}}] | ||
- | **Castle 2.0** is an [[: | + | **Castle 2.0** is an [[archdaemon]] which can occur from [[:mission difficulty# |
Castle 2.0 is found in the [[: | Castle 2.0 is found in the [[: | ||
Line 17: | Line 17: | ||
Castle is somewhat weaker than [[Rubiks]] since it only affects one device. Like Rubiks, it can be mitigated by hacking other devices first; on the other hand, triggering Castle early in a mission is often fine because of the chance it hits a device you don't need to hack. Even if Castle does hit a device you need to hack, you should be fine as long as you have an efficient way break high firewalls such as [[: | Castle is somewhat weaker than [[Rubiks]] since it only affects one device. Like Rubiks, it can be mitigated by hacking other devices first; on the other hand, triggering Castle early in a mission is often fine because of the chance it hits a device you don't need to hack. Even if Castle does hit a device you need to hack, you should be fine as long as you have an efficient way break high firewalls such as [[: | ||
- | {{tag> | + | As Castle 2.0 raises firewalls on 10 devices, is more likely to hit critical devices. To prepare for Castle 2.0, you will want at least one efficient high-firewall [[: |