Archives of Nethys

Pathfinder RPG (1st Edition) Starfinder RPG Pathfinder RPG (2nd Edition)

All Rules | Downtime Rules


Equipment / Dynamic Hacking

Dynamic Hacking Encounters

Source Tech Revolution pg. 73
Hacking encounters vary to reflect the hackers’ goals and the target computer’s capabilities. Each encounter includes at least one objective tied to the hacker’s goal (such as secret data to steal or a door to open), at least one countermeasure that opposes the hacker, and often, one or more nodes that create avenues the hackers must navigate toward their goals.
To build an encounter, set the encounter’s Challenge Rating— which sets the encounter’s check DC (page 71)—and decide on an approximate encounter length based on the number of checks required to resolve the key objectives. A short encounter requires about 5–7 successful checks to resolve the main objectives, whereas longer encounters might require 10–15 checks. For each lead hacker involved, add enough countermeasures to increase the number of checks by 2 (for shorter encounters) or by as much as 4 for longer encounters. For each support hacker, increase the number of checks by 1.
Scaling an encounter in this way need not always involve adding more countermeasures but could instead involve requiring an additional success to resolve specific objectives. This way, even if more PCs join the encounter as lead hackers than you anticipated, you can easily adjust the encounter to provide a fairly similar challenge.
Timed Encounters: In Starfinder, successfully accessing a system often affords the hacker time to explore at leisure. While a dynamic hack attempt might include finite countermeasures and a clear win condition, the format also supports hackers clashing with an array of defenses that multiply faster than the PCs can deactivate them. In this case, the goal becomes resolving enough countermeasures to stay safe, accomplish the mission, and escape before being overwhelmed or detected.

Sample Objectives

Source Tech Revolution pg. 73
The following are common objectives, including adaptations of existing modules and countermeasures from the Core Rulebook.

Basic Counterhacker (Countermeasure)

Source Tech Revolution pg. 73
This capable programmer shores up the computer’s defenses.
Resolve: Deceive (DC + 0, 2 successes) or Hack (DC + 2, 2 successes)
Countdown (3): Whenever the countdown reaches 0, the counterhacker causes two effects. First, they damage the persona of one lead hacker, causing it to lose CP equal to 2d6 + the encounter’s CR. That lead hacker can halve the CP their persona lost by succeeding at a DC + 0 Process check. Second, the counterhacker can perform one of the actions below. Afterward, roll 1d3 to determine the obstacle’s new countdown value.
Attack: Increase the Process check DC to resist the damage by 2, and treat all 1s on the damage dice as 2s.
Infect: The counterhacker infects the persona with a virus. Each phase after the hackers act, the infected persona loses CP equal to 1d6 plus half the encounter’s CR, and any computer that persona’s hacker is using takes damage equal to twice the CP lost. The virus can be removed by spending a major action and succeeding at a DC + 0 Hack check.
Repair: Choose one obstacle that hasn’t been resolved. Treat one of the checks to resolve that obstacle as though it had not been fulfilled this encounter.
Trace: The counterhacker assesses the persona’s signature and identifies where its associated hacker is located unless that hacker succeeds at a DC + 0 Deceive check.

Node, Basic (Node)

Source Tech Revolution pg. 73
The collection of file paths requires some effort to navigate and secure permission to restricted areas beyond.
Resolve: Hack (DC – 2, 1 success), Process (DC + 0, 1 success)
Support: Perception
Success: Add the node’s linked obstacles to the encounter.

Node, Fake Shell (Node)

Source Tech Revolution pg. 73
This node misleads hackers toward a falsified set of files.
Resolve: Hack (DC – 2, 1 success), Process (DC + 0, 1 success)
Support: Perception
Success: Add the node’s linked obstacles to the encounter.
Special: If the Process check to resolve this obstacle doesn’t exceed the DC by 5 or more, the linked obstacles are convincing fakes that function as normal obstacles, but resolving them provides no benefit (e.g. seemingly valuable data is worthless, command modules can’t direct devices, etc.).

Root Access (Module)

Source Tech Revolution pg. 73
You secure absolute administrator privileges, allowing you to modify any of the computer’s functions with ease.
Resolve: Hack (DC + 20, 1 success), Hack (DC + 15, 1 success), Deceive (DC + 10, 1 success)
Success: You and allied hackers reduce DCs to resolve obstacles by 20 and automatically succeed at checks to analyze objectives.

Secure Data (Module)

Source Tech Revolution pg. 73
This is an average-security data module with valuable contents. Large secure data modules typically require additional checks to resolve, have higher check DCs, or both.
Resolve: Hack (DC + 0, 1 success), Process (DC + 0, 1 success)
Support: Profession check related to the data
Success: Hackers can now use the modify action accompanied by specific subskill checks to delete (Hack), modify (Hack), forge (Deceive), or copy (Process) the module’s contents. As a special minor action, a hacker can study the contents with a successful DC + 0 Process check or related skill check to seek specific info or attain a basic understanding of the module’s contents.

Wipe (Countermeasure)

Source Tech Revolution pg. 73
This program destroys important data.
Resolve: Deceive (DC + 0, 1 success), Hack (DC + 0, 1 success)
Special: Count the number of times hackers fail a check to resolve an obstacle while the wipe countermeasure is active. Once the count reaches 2 failures, this countermeasure begins erasing one or more other objectives, imposing a –5 penalty to resolve them. At the end of the next hacking phase, those objectives are removed from the encounter and can no longer be resolved.