This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| daemons:castle [2020-05-04 23:13] – created storm | daemons:castle [2022-09-22 16:51] (current) – andrew | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Castle ===== | + | ====== Castle ====== |
| + | [{{ castle.png|Castle icon}}] | ||
| - | This article | + | **Castle** |
| - | {{tag> | + | Castle is found in the [[: |
| + | |||
| + | ===== Castle 2.0 ===== | ||
| + | [{{ castle_2.0.png|Castle 2.0 icon}}] | ||
| + | |||
| + | **Castle 2.0** is an [[archdaemon]] which can occur from [[:mission difficulty# | ||
| + | |||
| + | Castle 2.0 is found in the [[: | ||
| + | |||
| + | ===== Strategy ===== | ||
| + | |||
| + | 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 [[: | ||
| + | |||
| + | 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 [[: | ||