Alarms are a game mechanic that simulate how aware the authorities are that there is an intruder, and how close they are to finding them.
Within a host, alarms capture the alert level of both the host’s autonomous defenses (ie. ICE) as well as any metahuman sysops. On the local mesh, they measure the alert level of the mesh itself, and local GOD agents guarding the nearest uplink node.
The alarm clock
There are separate alarm clocks for each host and for different parts of the local mesh. These clocks are typically 12-segment.
Alarms typically increment by 1 point for each successful sleaze hack (0 with a raise) and 2 points for each failed hack.
If a Raise on the sleaze hacking roll can be used to make the hack more effective, then the decker can choose to use the Raise to avoid the alarm increment or improve the hack effectiveness, but not both.
Each time the alarm score is incremented, roll a d12. If the result is lower than or equal to the current alarm score, consult the table below to see what happens.
- 1-3 - no effect
- 4-8 - autonomous tracing persona start to patrol, running on the nearest uplink node. Treat these as Trace ICE.
- 9-11 - Killer ICE is deployed.
- 12 - a GOD counter-hacker with at least a d8 in Hacking and a mid-to-high-end ‘deck comes to kick ass and take names.
NotesTBD, but depends on the host’s overall security level.
Reducing the local mesh alarm score
Deckers can use a new utility called Spoof to dodge the effects of a high local mesh alarm score. Spoof works by routing all the decker’s traffic through a nearby device, setting it up to look like the culprit when the authorities notice.
The decker has to have had Spoof loaded before the first hack begun, and kept it loaded throughout. When Spoof is unloaded, the local mesh alarm value immediately halves (rounded down).
Spoof doesn’t help with host hacking.