Back to the main page

Mailing List Logs for ShadowRN

From: David Fallon <dfallon@****.EDU>
Subject: Re: Nostalgia and computers
Date: Tue, 3 Dec 1996 02:55:51 -0800
> Actually this has been a lot of fun for me as a GM.
> Bull hangs on to the case of his old deck, as well as a few simple
> chips.
> The old chips are really doing anything anymore, they're just there for
> simple functions like the on/off switch, etc. and because they're
> familiar to Bull.
> Fun!
> Speaking of Cyberdecks.
> Anyone have any ideas for how to have a decker set up a lasting
> subroutine on a host?
> Would it have to be done through a frame?
> Or could a high enough success add permanent programming to a host
> system?
>
> Any opinion as to IF/HOW a decker could do this kind of stuff?
>
> Steven A. Tinner

My opinion on the situation is to just do it as a "sustained" test, along
the lines of WW or such. Repeatedly compare his straight computer skill (or
matrix programming, or whatever), against the security level of the node,
totalling sucesses minus the threshold of the system. Blue is 0, green is 1,
yellow is 2, and red is 3. This roll is done repeatedly over the span of a
few days, (Repeated breakins to the system, and all of the hassle that
entails), where the decker can make one attempt per day to "add" to his
creation. Once the decker has a certain number of sucesses, depending on how
much he wants to do, the creation is basically permanent barring a full
system overhaul by Matrix security people for the computer that was
affected. If the decker wanted to write something that just scanned for
information and then sent out a message to the decker, it would be about
five sucesses to succeed. If the decker wanted to both scan for information,
and then modify it, it would be about 10 sucesses. If the decker wanted to
capture information, and then remove all traces of it, making it look like
it never came, that would be on the order of 15 or so sucesses. If the
decker fails a roll when trying to build up his total sucesses, then the
whole process must be restarted.

Example: Bull (GRIN) the decker is planning on creating a secure mail drop
for his team. He plans on doing this in the local library's system, a measly
green-4 system. No real need to hack into fuchi for this one. The ice on the
system is some level one and two white ice that he can breeze through
without even jacking in, so for this example I'm going to ignore the decker
breaking into the system every day. So, for the first day, Bull must use his
computer skill (A hefty 8), rolling against a target number of 4.
Unsurprisingly, he gets 5 sucesses. Because this is a green system, Bull
subtracts one from that, and then writes that down as his total for the day.
Bull is shooting for a full 15 sucesses, since he's interested in making
sure no trace of his communications remain on the library's computers. Day
two. 3 sucesses more, minus one to get a total of 6 sucesses for the two
days. This continues for another couple of days, until the fateful day 5. On
day five, with a total of 12 sucesses already, bull blows it big-time and
rolls a big one sucess. Since it's a green, that counts as no sucesses, and
bull goes home cursing since he has to totally restart the process.

Additional notes: If a decker doesn't have the time to repeatedly break into
the system, there is an alternate path. The decker can do all of the work
offline, and only break in once to install the patch, but there are several
caveats. First, the decker must be familiar with the system. This means that
the decker has to spend a few hours, at least, in the system, before he/she
can even consider doing the programming offline. From there, all target
numbers are at +2, and it takes two days for every roll against the system
node. Once the decker completes the patch, he can install it in one shot, by
going into the system and getting at least one sucess in a final roll
against the system node. If he fails that last roll, the patch was fatally
flawed and he has to start all over again.

Also, keep in mind that it's _REALLY_ hard to install patches into systems
of orange or red level, because not only do they have high target numbers,
you have to get a minimum number of sucesses every time. Why? Because
they're red systems. They're pretty darn tough. That, and so players don't
go around writing patches left and right to rechannel all of the bank's
incoming money into their accounts.

Note, this is only for VR 1.0. I don't really remember the VR 2.0 rules
enough to create a system for them, but if you're still interested, I can
read up on 'em and whip something up. I think you can probably adapt what
I've created, though.

David Fallon
[SK]Club
Clan Stalker
http://www.geocities.com/Area51/6060

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.