comStar Firewall alert - PhaseThrough
comStar Firewall alert - PhaseThrough
comStar Firewall alert - PhaseThrough
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
cess (even if the agent tries to hack his way in, the attempt<br />
will automatically fail). This security feature both deters<br />
piracy and prevents mass invasions by agent mooks (the<br />
so-called “Agent Smith” scenario).<br />
A copied agent may be patched in order to give it a<br />
separate unique access ID with a Logic + Software (Rating<br />
x 3, 1 week) Extended Test.<br />
new prograMS and actionS<br />
This section introduces a number of new utilities and<br />
describes the use of these programs in SR4.<br />
new Software<br />
Programs are the lifeblood of hackers and are often<br />
quite useful to non-hackers as well.<br />
corrupt (Hacking)<br />
A mixture of Edit and Browse subroutines, Corrupt<br />
programs are designed to track down and demolish specific<br />
information in a node without actually deleting the files in<br />
which they are saved (see the Corrupt Data action, p. 112).<br />
The idea is that, since deleted files can be restored from<br />
back-ups, Corrupt edits the files to overwrite the targeted<br />
information while leaving the file intact, without making<br />
any indication of the alteration, so that the corrupted file is<br />
eventually backed up as well, making detection and recovery<br />
of the original more difficult.<br />
Additionally, Corrupt programs can be attached to a<br />
particular file in the same manner as Data Bombs (p. 226,<br />
SR4). If triggered, the Corrupt program demolishes the<br />
data before it can be accessed. Corrupt programs used in<br />
this way can be deactivated in same manner a Data Bomb is<br />
defused (see Disarm Data Bomb, p. 223, SR4).<br />
disarm (Hacking)<br />
Disarm is used to undermine programs without crashing<br />
them. It is used to corrupt targeted software so that the<br />
disarmed program cannot act against the hacker (and only<br />
the hacker), effectively neutralizing its use. Operating systems,<br />
personas, IC, agents, sprites, and malware may not be<br />
disarmed, but this utility is effective against most Common<br />
Use programs, Hacking programs, and autosofts.<br />
nuke (Hacking)<br />
Nuke is a combat utility that does not inflict Matrix<br />
damage, but instead hogs up system resources in an attempt<br />
to freeze the target user. Treat damage from a<br />
Nuke attack similar to Matrix damage from an Attack<br />
program. However, each box of Nuke damage instead<br />
deducts one point from either the node’s Response<br />
or System/Pilot (in case of agents or sprites) with the<br />
appropriate effects on Matrix Initiative, processor limit, and<br />
subscription limits. The attacker determines which attribute is<br />
affected by each point of Nuke damage. If Nuke reduces both<br />
values to zero, the target’s persona freezes. The user or agent<br />
can take no action within the Matrix until he reboots (p. 221,<br />
SR4). Likewise, Response reduced by a Nuke attack cannot be<br />
restored without a reboot.<br />
Unwired<br />
agent coMpetencY<br />
Agents may be capable of operating independently,<br />
but this does not mean that they are just as capable as<br />
hacker characters. In fact, while they are very smart in<br />
many ways, agents possess a number of drawbacks that<br />
make them inferior to metahumans.<br />
The Pilot program that guides an autonomous agent is<br />
an incredibly sophisticated software with logical and analytic<br />
capabilities on par with any metahuman. This does<br />
not mean, however, that the agent has decision-making<br />
capabilities equal to metahuman. Not only do they lack a<br />
lifetime of experience to base their judgements on, they<br />
often lack the context that would enable them to fully<br />
understanding a situation. For example, while the agent<br />
may understand that certain icons engaged in cybercombat<br />
with others are considered enemies, and might<br />
even grasp some of the finer tactical points, it would<br />
not necessarily understand the personal relationships<br />
or social cues between them, and so would not realize<br />
that, say, attacking one icon might enrage another, or<br />
recognize that one icon is attempting to surrender or<br />
switch sides, or comprehend that one icon is simply<br />
toying with its opposition and hasn’t unleashed the big<br />
guns yet. Contextual information is even more lacking<br />
when the agent interacts with the physical world in some<br />
way (via sensor, security system, or drone, for example),<br />
as agent Pilots are programmed for Matrix activities, not<br />
for interfacing with meatspace. (This is less true of drone<br />
Pilots, which are programmed for real-world activity, but<br />
are specifically tailored for the drone model they occupy;<br />
see Pilot Capabilities, p. 103, Arsenal.)<br />
Pilots are also limited in their capacity for creative<br />
thought. They tend to stick to their orders, making strictly<br />
logical choices according to programmed decision trees<br />
(see Agent Scripting, p. 100)—which may not always be<br />
the best course of action. When faced with an unexpected<br />
obstacle or set of choices that don’t fit their programming,<br />
they tend to fall back and regroup—a safer choice over<br />
improvisation. Note that agents due have “fuzzy logic”<br />
routines that allow them to judge and act on imprecise<br />
concepts and conditions, but taking action based on generalized<br />
probabilities also has its drawbacks.<br />
When in doubt, gamemasters can secretly roll a<br />
Pilot + Response Test against an appropriate difficulty<br />
threshold to determine how agents respond to difficult<br />
situations based on their orders (see Issuing Commands,<br />
p. 214, SR4).<br />
Due to the unique and organic nature of the living persona,<br />
technomancers are immune to Nuke attacks, while sprites and<br />
other autonomous entities that depend on the resources of the<br />
node they are on (rather than the technomancer), are not.<br />
purge (common Use)<br />
The sole purpose of Purge programs is to search through nodes<br />
infected with virus programs to find the virulent code and eradicate it<br />
Simon Wentworth (order #1132857) 9<br />
111<br />
software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .