comStar Firewall alert - PhaseThrough

sprites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
new Sprite rULeS
This section provides new rules and expanded definitions of
sprite abilities.
SpriteS and node acceSS
As creatures of resonance, sprites may travel to and from
the resonance realms as they please. This allows them a kind of
shortcut, taking a path from one node to another via the resonance
realms, rather than through the Matrix. This does not, however,
give them a free pass to bypass firewalls and system security. A
sprite may only use this shortcut to access a node in which the
technomancer to whom they are registered is present (i.e., the
technomancer calls them into the node), or in which they have
legitimate account or backdoor access. Otherwise, the sprite must
hack into the node, following the same rules as any other hacker
(p. 221, SR4).
Unlike agents, whose decision-making capacity is limited,
sprites are sapient enough to make decisions like any metahuman
hacker or technomancer. Keep in mind, however, that their knowledge
of the real world or anything beyond the Matrix—including
metahuman behavior and logic—is quite limited, if not nonexistent.
When not advised by a technomancer, sprites may fail to
assess metahuman behavior and predict responses correctly.
Since technomancers maintain a link with their sprites, as
long as they remain online, they are able to communicate and
exchange information in terms of text, files, and even impressions.
Thus, sprites can be used to generate user accounts or install backdoors
to pave the way for hackers to access a node (though doing
so counts as at least one remote service, and probably several).
craSHing SpriteS
If a sprite suffers enough Matrix damage to fill its damage
track, it crashes. A crashed sprite shuts down (or gets booted into
the resonance realms, whatever you want to believe) and is not
able to recompile on the Matrix for 16 days minus its rating, with
a minimum time of 32 hours. Crashed sprites still count against
the technomancer’s limit of registered (and unregistered) sprites,
though a technomancer may release a sprite from its remaining
tasks while it is crashed. Since an unregistered sprite’s 8 hours
of service still elapses while it is crashed, it will never return.
The only way for a technomancer to bring a crashed unregistered
sprite back from its digital imprisonment before its time is to
make a resonance realm search to find the source code of the
sprite (see p. 174).
optionaL rULe:
Spectrum of Complex Forms
Since Unwired introduces new programs and complex
forms that the five basic sprites described on p.
236, SR4, do not have, neither as complex forms nor
as optional CFs, gamemasters may choose to extend
the number and type of (optional) complex forms that
each sprite possesses as he deems fit.
Linking (Long -terM regiStering)
A compiling technomancer can semi-permanently script
a registered sprite to a task or set of tasks (so called linking) by
paying Karma equal to its rating. Once linked with Karma, the
sprite no longer counts against the technomancer’s limit for
registered sprites, and any remaining services are lost. The linked
sprite will remain at its final service 256 days, unless decompiled
or disrupted, in which case it will return to its duties after 16 days
minus its rating (see Crashing Sprites, p. 154).
SpriteS and coMpLex forMS
With the gamemaster’s discretion, the complex forms of all sprites
described herein and on p. 236, SR4 may be equipped with program
options as optional powers. Instead of choosing optional complex
forms for every 3 full rating points (p. 236, SR4), the technomancer
may add a suitable program option to one of the innate complex forms
of the type of sprite he attempts to compile (or optional forms, as long
as the rating of the sprite is high enough to choose).
new SpriteS
The Shadowrun, Fourth Edition, rules present just some of the
sprites than can be compiled in the Matrix. Unwired introduces five
new categories of sprites that can be compiled by technomancers
riding an appropriate stream (see Resonance Streams, p. 136). Unless
otherwise stated, sprites follow the general rules for compiling, registering,
and decompiling found on pp. 234–236, SR4.
code Sprite
Code sprites interact with the Matrix on the machine code
level. Their specialty is watching and changing the flow of data and
energy resources.
Unwired
Sprite iconograpHY
The appearance of every icon in the Matrix is the
result of deliberate sculpting, and sprites are no exception.
Every sprite’s appearance is chosen at the
moment of its compilation, with just about any look
possible, ranging from mechanical forms like gears,
over electronic resemblances of animals to humanoid
form. Any shape is generally possible. But there are
certain things which affect its appearance besides
the wish of its creator. Not only does its matrix signature
depend on the compiling technomancer, the
metaphor of his living persona also heavily influences
their sprites’ look. Secondly the Stream a technomancer
follows has a major affect on the sculpting. It
is synonymous not only for his outlook on the matrix
in general, it defines what kind of relationship the
technomancer has to its sprites. A mere tool to its
owner looks quite different than a trusted near-equal.
Finally, the intention with which the sprite is compiled
does leave clues in its appearance. If there aren’t any
clues apparent, the kind of sprite gives some clue
about its cause
Simon Wentworth (order #1132857) 9