| From: | gt6877c@*****.gatech.edu (S.F. Eley) |
|---|---|
| Subject: | Matrix 1.0 to 2.0 Conversion |
| Date: | Thu, 30 Nov 1995 18:44:44 -0500 (EST) |
rough set of guidelines:
MATRIX 1.0 --> 2.0 CONVERSION RULES
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
by S.F. Eley
sf@********.org
Okay folks, here's how to turn turn your old SR adventure Matrix maps into
newfangled Matrix 2.0 host maps. This system is a bit oversimplified, and
hasn't been playtested yet, but it should work as a starting point. Please
mail me feedback if you try this system and like it (or don't.)
HOST LAYOUT
Every SPU and CPU is a host. It's that simple. The datastores connected
to an SPU are data on that host. The slave nodes are part of that host's
Slave subsystem. The I/O ports and SAN's are in the host's Access subsystem.
All the IC is consolidated on the host's security sheaf. Any questions?
Here's how to map it:
1.) Draw every SPU and CPU using the line connections between them, just as
they're shown on the Matrix map. An SPU with a SAN connects to an LTG
or PLTG; use the text in the adventure to determine which.
OPTIONAL: In Matrix 1.0, the CPU can connect you to any node with the
"teleport" operation. If you want to replicate this, the host that
was the CPU can connect to all other hosts as a chokepoint. Some of
the hosts may be hidden, however, via trapdoors (p. 33, VR2). Note
that this isn't necessary with the simpler 2.0 layout, and may
ruin the challenge of some decking runs.
2.) A host keeps the security code (Orange, Red, etc.) of the SPU or CPU.
The Security Value is equal to the old node's Rating. If the system
is a Red system of Rating 3 or less, double the rating. Subsystem
ratings are as follows (round down or up depending on nastiness):
ACCESS: The Security Value, plus the rating of any Access or Barrier
IC on the node connection. Add +2 if any I/O ports are connected to
the host, +4 if the host is connected to a SAN.
CONTROL: 1.5 times the Security Value, +2 if the host was an SPU,
+4 if the host was the CPU.
INDEX: 1.5 times the Security Value, plus half the number of
datastores connected to the node. Add +2 if one or more datastores
contains critical information.
FILES: Roll 2d6 and consult the following table:
2-3 Index Rating - 2
4-5 Index Rating - 1
6-8 Index Rating
9-10 Index Rating + 1
11-12 Index Rating + 2
SLAVE: 1.5 times the Security Value, plus half the number of slave
nodes connected to the node. Add +2 if any of the slave nodes are
security systems.
3.) Build the security sheaf according to the Trigger Step Table on p. 63,
VR2. The following rules apply for specific forms of IC and alerts:
ACCESS & BARRIER: They don't exist in Matrix 2.0. Instead, they add
to the Access subsystem rating for the host (see ACCESS, above.)
PROBE: This will be activated on either the first or second Trigger
Step. (Use your discretion.) The Probe IC rating is the average of
the Probe IC ratings in all nodes on the host. If there is no Probe
IC in the Matrix 1.0 map, add Probe IC with a rating equal to the
host's Security Value.
TRACE: This will be activated on either the first or second Trigger
Step. (Use your discretion.) The Trace IC rating is the highest
rated Trace IC of any node on the host.
OPTIONAL: Trace & Burn or Trace & Dump IC can be trapped to perform
these actions if the GM wishes (see p. 47, VR2).
TAR BABY: Tar baby IC, if it exists, will be activated on the third
Trigger Step (just before Passive Alert.) The rating is the highest
rated Tar Baby IC of any node on the host.
DAMAGING WHITE IC: Killer and Crippler IC may be activated before or
after a Passive Alert (which will be either the third or fourth
Trigger Step.) The rating of damaging white IC is the highest rated
IC of that type for any node on the host, +1 for each time that type
of IC is duplicated. (E.g., if a Killer-5 is on the SPU, and Killer-3
and Killer-2 are in connected slave nodes, the total rating is Killer-5
+ 2 = Killer-7.)
GRAY IC: Gray IC is usually activated after an Active Alert, but one
gray IC program may be activated before Active Alert (this will be Tar
Pit if it exists on the host). The rating of gray IC is the highest
rated IC of that type for any node on the host, +1 for each time that
type of IC is duplicated.
BLACK IC: Black IC will be activated after all other IC. The rating
of Black IC is TWICE the highest rated Black IC on the host. (No
bonuses for multiple instances; this is deadly enough!) The form of
the Black IC should fit the context given in the adventure.
SCRAMBLE IC: Scramble IC is at its original rating for the files of
any datastore containing it. If every datastore on the SPU has
Scramble IC, Scramble at the highest rating on the host protects the
entire Files subsystem.
Other IC (ripper, worms, data bombs, etc.) are entirely at the GM's
discretion, as are constructs, party IC, and IC options. Try to make
it appropriate to the Matrix system in question, and what the decker
needs to accomplish. If you don't use ANY of them, the hosts will all
tend to look the same, so be creative.
System shutdown will always be the last Trigger Step on the sheaf.
OPTIONAL: If the host acts as a chokepoint or is otherwise
critical to the run, don't include system shutdown.
4.) Central Metaphor: This should be easy. Most published Matrix systems
are already sculpted realities to some extent anyway.. Those that
aren't, pick something appropriate to the corporation. It might vary
from host to host, but it usually won't.
And there's your system. Be sure to look at it and tweak the various
Ratings and IC to create the same level of challenge that was originally
intended.. This will get easier as you run more Matrix 2.0 sessions.
If you just can't make it work, don't hesitate to scrap the whole published
Matrix and build your own, putting the important data wherever you feel it
belongs. The key to Matrix 2.0 is paranoia and style.. If the Matrix looks
cool, and the decker is paranoid, you've basically got it right.
[*FINI*]
