20.04.2013 Views

comStar Firewall alert - PhaseThrough

comStar Firewall alert - PhaseThrough

comStar Firewall alert - PhaseThrough

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Streams are still evolving and are not yet as stereotyped as the<br />

paradigms of the Awakened community. Technomancers following<br />

the same set of parameters—“riding the same stream,” as some<br />

say—have started to codify and streamline their beliefs, paving the<br />

way for currently Emerging technomancers.<br />

rationalizating the digital Mind<br />

Though many technomancers do not like being pigeonholed<br />

or do not easily accept pre-defined doctrines, many of<br />

the newly Emerged find it comforting to adopt practices and<br />

techniques devised by others that fit with their own ideas and<br />

perceptions of the virtual world. As the process of Emergence is a<br />

life-changing event, challenging beliefs and turning one’s life upside<br />

down, individuals who become technomancers often change<br />

their outlook and even their personality, which can explain why<br />

even the most rational mind might turn into a believer in the<br />

mystic nature of code.<br />

creating a Stream<br />

To create a new stream, the player must choose the following:<br />

1. The core concept of the Stream.<br />

2. The type of sprites that can be compiled by technomancers riding<br />

the stream.<br />

3. The means by which technomancers on the stream resist<br />

Fading.<br />

The definition of a stream is vital for a technomancer, as it<br />

defines his underlying philosophy, how he reacts to and interacts<br />

with both the real and the virtual worlds. While the beliefs of a<br />

technomancer stream are less tangible (especially from the roleplaying<br />

point of view) than magical traditions that are based on<br />

known religious or magical concepts, the gamemaster and the<br />

player should work together to create a stream that makes sense<br />

within the scope of their specific game and the Shadowrun universe<br />

as a whole.<br />

concept<br />

The core of a stream is its philosophy of the Matrix and the<br />

Resonance. It is a technomancer’s way of explaining how the<br />

Matrix changed with Crash 2.0, what Resonance is, and how she<br />

can manipulate the processes of the Matrix. While the fundamental<br />

belief of a stream has no game effects, it affects the way<br />

a technomancer views the Matrix, nodes, and virtual reality. It is<br />

therefore important to sketch out a stream’s core concepts before<br />

detailing how it works in game terms.<br />

Does your technomancer have a natural affinity for the<br />

cyberworld, perceiving it as her real home? How is the technomancer’s<br />

interaction with Matrix processes defined in terms<br />

of complex forms? Does she actively force the code to do her<br />

bidding or persuasively ask the living Matrix to change as she<br />

desires? Does she rationalize her existence as an evolutionary<br />

branch that mankind has taken, or is everything the result of<br />

higher forces?<br />

Each of these ideas is a stepping stone toward fleshing out<br />

how the character perceives herself in relation to both reality and<br />

the digital realm.<br />

Unwired<br />

optionaL rULe:<br />

The Resonance Difference<br />

The way that technomancers, complex forms,<br />

and sprites operate—using Resonance—is far different<br />

from how standard personas, programs, and agents<br />

work. For simplicity and flow, these are often treated<br />

the same in terms of game mechanics, and, indeed,<br />

this makes some practical sense. For example, complex<br />

forms must interact with nodes and standard<br />

Matrix programs, and so the complex forms would<br />

need to “speak the same language” in terms of input/<br />

output and be recognized as legitimate “software,”<br />

otherwise there would be problems.<br />

Nevertheless, complex forms and sprites are not<br />

composed of code in the normal sense, and so it is<br />

conceivable that certain actions made against them<br />

might not get the same results as they would against<br />

typical software. This optional rule provides for this,<br />

but gamemasters should be aware that this gives<br />

technomancers a certain edge over hackers, and so<br />

should apply it careful. Alternately, these options<br />

could be handled as echoes.<br />

attack protection<br />

Normal Attack programs are less effective against<br />

technomancers and sprites, as the code faults such<br />

software normally exploits are simply not there. Apply<br />

a +2 dice pool modifier to the Defense Test against<br />

such attacks.<br />

difficult to analyze<br />

Though megacorps and security companies have<br />

made great inroads in identifying technomancers,<br />

complex forms, sprites, and even echoes, the nature of<br />

Resonance still makes each of these harder to identify—<br />

they simply don’t match regular code patterns, and the<br />

look of a complex form used by one technomancer looks<br />

completely different when wielded by a technomancer<br />

from a different stream. Increase the threshold for<br />

Matrix Perception Tests against technomancers, complex<br />

forms, sprites, echoes, and widgets by 1.<br />

immunity to crashing<br />

Under this rule, the normal routines and tricks<br />

that make software vulnerable to crashing do not<br />

exist in Resonance-fueled complex forms. This makes<br />

technomancer complex forms immune to crashing,<br />

unless the Crash action is initiated by a technomancer<br />

or sprite. Technomancers and sprites may still crash<br />

the programs of regular Matrix users.<br />

immunity to defusing<br />

For the same reasons, A Data Bomb created by<br />

complex form cannot be disarmed by a normal Defuse<br />

continued on page 138<br />

Simon Wentworth (order #1132857) 9<br />

137<br />

technoMancers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!