This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| mainframe_devices:databases [2023-10-11 21:16] – [Daemon Database] andrew | mainframe_devices:databases [2023-10-11 21:56] (current) – [Daemon Database] andrew | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| **Databases** are [[: | **Databases** are [[: | ||
| - | Each facility has at least one database, | + | Each facility has at least one database, |
| - | * At mission difficulty 1, there is randomly either a [[#Camera Database]], [[#Console Database]] or [[#Facility Database]]. | + | |
| - | * At mission difficulty 2 or higher, there is always a [[#Daemon Database]], | + | |
| - | * In [[: | + | |
| Databases provide [[: | Databases provide [[: | ||
| Line 26: | Line 23: | ||
| When hacked, a **Daemon Database** permanently reveals information about current [[: | When hacked, a **Daemon Database** permanently reveals information about current [[: | ||
| - | Daemon Databases do not occur at [[:mission difficulty]] 1. At mission difficulty 2 and higher, every facility has one Daemon Database in addition to its other Database(s); this can mean a facility has two Daemon Databases, in which case there is no benefit to hacking more than one of them, unless a new unrevealed daemon is added to a device after the first Daemon Database is hacked. | + | Daemon Databases do not occur at [[:mission difficulty]] 1. At mission difficulty 2 and higher, every facility has a Daemon Database in addition to its other Database(s). |
| ===== Facility Database ===== | ===== Facility Database ===== | ||