Back to the main page

Mailing List Logs for ShadowRN

Message no. 1
From: shadowrn@*********.com (Adam Hansen)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Thu Jun 27 19:35:00 2002
Hey everyone,

New to the list here, so far I'm enjoying what I read.

I've recently resurrected our Shadowrun campaign with a new batch of
players. Finally, I have a group who wants to do more than make cybered up
musclemen and power game.

New to the group...is a decker. Now I get get to use ALL of the rules for
the first time.

Is there any guidelines from converting the old system maps of SR1/SRII to
the system security sheafs from VR2.0/SR3?

And what exactly is in Matrix? The only gaming supply store around here is
horrible, and I haven't had the chance to order it online yet. Is it worth
getting?

Thanks in advance

Adam
Message no. 2
From: shadowrn@*********.com (Bira)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Thu Jun 27 22:10:01 2002
On Thu, 27 Jun 2002 18:35:57 -0500
"Adam Hansen" <1shadowrun@*****.com> wrote:

>
> Hey everyone,
>
> New to the list here, so far I'm enjoying what I read.
>
> I've recently resurrected our Shadowrun campaign with a new batch of
> players. Finally, I have a group who wants to do more than make cybered up
> musclemen and power game.
>
> New to the group...is a decker. Now I get get to use ALL of the rules for
> the first time.
>
> Is there any guidelines from converting the old system maps of SR1/SRII to
> the system security sheafs from VR2.0/SR3?

Just make it up... The difference between the two editions is so big
it's not worth designing conversion rules.

> And what exactly is in Matrix? The only gaming supply store around here is
> horrible, and I haven't had the chance to order it online yet. Is it worth
> getting?

It has cyberdeck construction rules, rules for programming, new programs,
new IC, and a nice "essay" on how the Matrix works in 2060 society :).

--
Bira -- homem saído das entranhas da Terra para mudar o destino da humanidade,
usando apenas um filhote de urubu e um rolo de "silver tape"...
http://www.shadowlandbr.hpg.com.br
Message no. 3
From: shadowrn@*********.com (Lone Eagle)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Fri Jun 28 04:00:01 2002
>From: "Adam Hansen" <1shadowrun@*****.com>
<Snip>
>Is there any guidelines from converting the old system maps of SR1/SRII to
>the system security sheafs from VR2.0/SR3?

Probably, but I'm afraid I can't help you on that one. Last resort: run a
search!

>And what exactly is in Matrix? The only gaming supply store around here is
>horrible, and I haven't had the chance to order it online yet. Is it worth
>getting?

Oh yes, never even think about playing a decker without it!
Actually it isn't absolutely vital but some of the systems in there are
sooooooooo! useful it's unbelievable. You know how much an Attack Deadly
Utility costs, save all that money by writing the program yourself!!
Brilliant!!!
>From a GMs point of view, Security Sheaves on the fly are the pages I look
at most.

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
Message no. 4
From: shadowrn@*********.com (Gurth)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Fri Jun 28 05:15:06 2002
According to Adam Hansen, on Fri, 28 Jun 2002 the word on the street was...

> Is there any guidelines from converting the old system maps of SR1/SRII
> to the system security sheafs from VR2.0/SR3?

Back in 1995, when VR2.0 was just released, then-listmember Stephen Eley
wrote up a set of conversion guidelines. A few years later, I put these
into the Plastic Warriors net.book, The Player's Guide to Shadowrun House
Rules, available in RTF format from
http://plastic.dumpshock.com/shadowrun/supplements.html

Here's the relevant bit:

-----

Okay folks, here's how to turn your old Shadowrun 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, VR 2.0).
Note that this isn't necessary with the simpler VR 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:

Roll Rating
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,
VR 2.0. 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 gamemaster wishes (see p. 47, VR 2.0).
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 gamemaster'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.

-----

> And what exactly is in Matrix? The only gaming supply store around here
> is horrible, and I haven't had the chance to order it online yet. Is it
> worth getting?

Matrix is basically VR 2.0 for SR3 -- it includes rules for things like
building your own deck, writing your own programs, extra options for use in
the Matrix, background on how people interact with the Matrix, and so on.
If you have a decker in the group, it's worth getting; otherwise, you can
probably do without, though.

--
Gurth@******.nl - http://www.xs4all.nl/~gurth/index.html
Little ever changes, if anything at all
-> NAGEE Editor * ShadowRN GridSec * Triangle Virtuoso <-
-> The Plastic Warriors Page: http://plastic.dumpshock.com <-

GC3.12: GAT/! d- s:- !a>? C++@ UL+ P(+) L++ E W--(++) N o? K w(--) O
V? PS+ PE@ Y PGP- t@ 5++ X(+) R+++$ tv+(++) b++@ DI- D+ G+ e h! !r y?
Incubated into the First Church of the Sqooshy Ball, 21-05-1998
Message no. 5
From: shadowrn@*********.com (Adam Hansen)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Fri Jun 28 08:35:01 2002
[/SNIP]

Looks great. Consider it playtested, as I will use it to run a few of the
published adventures. I am running DNA/DOA, a decent adventure, and the
decking portion of the run is very small.

What a way to start new players out by having Aztechnology peeved at them?
:)

Thanks again
Message no. 6
From: shadowrn@*********.com (Gurth)
Subject: Host Conversion from SR1/SR2 to SR3/VR2.0
Date: Fri Jun 28 10:45:01 2002
According to Adam Hansen, on Fri, 28 Jun 2002 the word on the street was...

> [/SNIP]
>
> Looks great.

What does? (Yes, I know you're _probably_ talking about the host conversion
rules. But this is a subtle hint that we'd like you to quote the relevant
parts of a message, so we all know what you're referring to :)

> Consider it playtested, as I will use it to run a few of the
> published adventures. I am running DNA/DOA, a decent adventure, and the
> decking portion of the run is very small.

Not sure if I'd call that adventure "decent," but there are worse ones to
start out with, certainly.

--
Gurth@******.nl - http://www.xs4all.nl/~gurth/index.html
Little ever changes, if anything at all
-> NAGEE Editor * ShadowRN GridSec * Triangle Virtuoso <-
-> The Plastic Warriors Page: http://plastic.dumpshock.com <-

GC3.12: GAT/! d- s:- !a>? C++@ UL+ P(+) L++ E W--(++) N o? K w(--) O
V? PS+ PE@ Y PGP- t@ 5++ X(+) R+++$ tv+(++) b++@ DI- D+ G+ e h! !r y?
Incubated into the First Church of the Sqooshy Ball, 21-05-1998

Further Reading

If you enjoyed reading about Host Conversion from SR1/SR2 to SR3/VR2.0, you may also be interested in:

Disclaimer

These messages were posted a long time ago on a mailing list far, far away. The copyright to their contents probably lies with the original authors of the individual messages, but since they were published in an electronic forum that anyone could subscribe to, and the logs were available to subscribers and most likely non-subscribers as well, it's felt that re-publishing them here is a kind of public service.

Thwap!