Back to the main page

Mailing List Logs for ShadowRN

Message no. 1
From: sedahdro@*****.com (Victor Rodriguez, Jr)
Subject: Decker resolution system
Date: Mon, 13 Nov 95 12:30 EST
Hello all,
I recieved the following from a friend of mine who use to subscribe
to this list a couple years back. It is a system designed to resolve matrix
combat quicker. This is from the same person I got that character
generation system that I posted earlier this summer. I feel that some of
you might be interested so here it is:
---Sedah Drol


>Return-Path: <mancinis@****.cc.purdue.edu>
>From: steven mancini <mancinis@****.cc.purdue.edu>
>Subject: Re: Decker resolution system
>To: sedahdro@*****.com (Victor Rodriguez, Jr)
>Date: Mon, 13 Nov 95 8:36:56 EST
>
> Decker Quick Resolution System
> ------------------------------
>
> by Steve Mancini
> mancinis@****.cc.purdue.edu
>
>
>Step 1: Determine the "Quest Rating"
>
> This fluctuating variable represents the overall difficulty
> of the Decker Quest. In some instances, (As in those using FASA
> Modules), you may need to average a number with regard to an entire
> preset system. Othertimes, you may use an established number as
> is. For example, thanks to the Tir Sourcebook, Lofwyr's Matrix
> Node is a Red-10. Your quest in this instance may be 10. ( You
> wanna go tapdancing in the business of a Great Dragon eh??)
> It is important to realize this Rating, like that in an Astral
> Quest, is the target for most tests. A rating too high, when augmented
> by the Color of the system, may make the quest impossible. This may
> be what you hope to accomplish, or it may not. Okay enough Preaching
> for the time being.
>
>Step 2: Determine the System Color.
>
> Just like traditional matrix, the quest will have a "Color". The
> same rules that apply to the Quest Rating also apply here. However, just
> like the above, the colour will start out "weaker" and grow to its full
> strength as the Quest progresses.
>
>Step 3: Decker Stats Sheet. (Optional)
>
> Fill in the Decker's Stats (MPCP, Bod, Evas, etc.) so that you
> know what they are running with. I have made this sheet disposable so
> that each Matrix Quest is run on *a* sheet. (Sorry Gang, no fancy
> Word Process Programs here... yet.)
>
>Step 4: The Decker Meets the "Dweller"
>
> This initial stage corresponds to the launching pad for the
> Initiate on an Astral Quest. The Decker, using his/her Computer Theory,
> rolls an Unresisted test against a target equal to the Quest Rating.
> These count as a automatic successes when having to overcome the node.
> They refresh each time the decker rolls for any test. However, each time
> they are used the autos require at least *one* additional success be rolled
> by the decker for them to count. These autos do NOT count when resisting
> anything to which the deck's Hardening applies (aka Black/Grey IC)
>
>Step 5: The Quest.
>
> All deckers start at the START box. Then simply proceed forward
> "Up" the quest to the OBJECTIVE box. In each box is a IC or required
> program. The IC that are White (Barrier, Access, Probe, etc) must be
> surpassed or they send the system into alert, automatically raising the
> quest rating by 1, up to x2 Quest rating. The IC that causes damage to
> the decker must resisted only once, much like that in an Astral Quest.
> Each New Level is Discovered by an "Analyze" Location. Once the
> new level is found, the security on that level must be surpassed. If it
> is not surpassed, the decker returns to the lower level and rolls
> D6 again. ** Hacking Poll Only Refreshes upon a successful advancement
> to a new level. **
> Optional: We have deliberated the option that once the analyze is
> successful, the decker may raise an additional level for each time they
> surpase the "threshold" of the Quest. ie A decker rolls 8 successes in
> a Green System (Threshold = 2). The first 2 successes are applied to the
> threshold of the quest, leaving 6. The next success is applied to
> over-coming the "place" the decker is currently at, leaving 5. Since this
> is a Green System Quest, the staging is 2, allowing the decker to raise
> 2 additional levels `up' the Quest.
> As with all systems, feel free to fluctuate the length. If the
> decker is trying to hack straight into a security door from the door
> itself, the GM may wish to remove any number of the "Levels" of the
> Quest for that instance.
>
>Step 6: Misc Information.
>
>Decker's Contribution: .5(MPCP) + (Active Utility MP)/100
>
>Node Efficiency:
> Less than 50% Load Rating........... -1 to "Quest Rating"
> 50% to 100% Load Rating............. No Modification
> 100% to 200% of Load Rating......... +2 to Quest Rating
> 200%+ of Load Rating................ ShutDown
>
>All IC Have 3 Modes:
> Normal: No Modifications
> Hardened: +2 to Target Unless attack has Penetration
> Option
> Shifting: +2 to Target Unless attack has AOE Option.
>
>------------------------------------------------------------------------------
>
> THE DECKER QUEST || The Decker:
> /-----------------------------\ || +------------------+
> | 4 Evaluate for $$$ | || | Computers: |
> |-----------------------------| || +------------------+
> | 5 Sift for Data | || | Theory: |
> |-----------------------------| || +------------------+
> | 7 Tar Pit | || | Hacking: |
> |-----------------------------| || +------------------+
> | 8 Killer IC | || | Body: |
> |-----------------------------| || +------------------+
> | 9 Marker IC | ||
> |-----------------------------| ||
> | 10 Probe IC | || The Deck:
> |-----------------------------| || +------------------+
> | 11 Barrier IC | || | MPCP: |
> |-----------------------------| || +------------------+
> | 12 Access IC | || | Bod: |
> |-----------------------------| || +------------------+
> | 13 Trace & Report | || | Evasion: |
> |-----------------------------| || +------------------+
> | 14 Gray Blaster | || | Masking: |
> |-----------------------------| || +------------------+
> | 15 Access IC | || | Sensors: |
> |-----------------------------| || +------------------+
> | 16 Jammer IC | || | Hardening: |
> |-----------------------------| || +------------------+
> | 17 Trace & Dump | ||
> |-----------------------------| ||
> | 18 Acid IC | ||
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 19 Grey Killer IC | || MPCP |L| |M| | |S| | | |D|
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 20 Tar Baby | ||
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 21 Binder IC | || Phys |L| |M| | |S| | | |D|
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 22 Hog Program | ||
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 23 Analyze | || Ment |L| |M| | |S| | | |D|
> |-----------------------------| || +-+-+-+-+-+-+-+-+-+-+
> | 24 Objective | ||
> \-----------------------------/ ||
>
>
>
>
>Type Color Decker Uses Target Procedure
>----- ----- ----------- ------ ----------
>
> Access White Decept/Sleaze n/a If decker fails, 1st failure results
in passive alert
> raising the rating of this IC by 50%; second failure-
> system alert (raise Quest rating by 1).
>
> Acid Grey MPCP + Hacking Evasion Reduces 1 point of Bod per success
>
> Barrier White Sleaze Only n/a If decker fails, 1st failure- raise
this IC rating by
> 50%; 2nd failure- system alert (raise Quest Rating by 1).
>
> Binder Grey MPCP + Hacking Evasion Reduces 1 point of Evasion per success
>
> Blaster Grey MPCP + Hacking Evasion Does Moderate + 1Box/Success to the
MPCP Monitor.
> When it crashes IC then makes Unresisted(MPCP), every
> extra success (over the Hardening) reduces the MPCP
> by 1 permanently.
>
> Jammer Grey MPCP + Hacking Evasion Reduces 1 point of Sensors per success
>
> Killer Grey MPCP + Hacking Bod Base Damage Load Rating
> Light .5 Rating
> Moderate Rating
> Serious 1.5 Rating
> Deadly x2 Rating
>
> Killer Black Body + Hardening BodY Does damage against decker similar to
Grey IC
>
> Marker Grey MPCP + Hacking Evasion Reduces 1 point of Masking per success
>
> Probe White Decept, Sleaze(+2) n/a 1st Failure- raise this IC's rating
by 50%;
> 2nd Failure- System alert (raise Quest Rating by 1).
>
> Scramble White Decrypt, Decept n/a If decker fails, destroys data.
>
> Tar Baby Grey Decption, Sleaze Evasion If decker does not overcome IC, it
crashes the Utility
> Used against it.
>
> Tar Pit Grey Deception, Sleaze Evasion If decker does not overcome the
IC, the IC crashes ALL
> copies of Utility in On-line storage.
>
> Trace & * Grey Relocate Masking Trace IC makes Unresisted(Masking). 1
Success and it is
> locked on target. Trace completed in (10 Turns) divided
> by the number of Successes.
> Decker may attempt to use Relocate against it.
> -Burn Grey *** Acts as Blaster(1/2 Trace Rating) and attacks deck.
> Only another decker or a frame can protect the decker.
> It automatically attacks the MPCP.
> -Dump Grey *** Automatically dumps decker.
> -Report Grey *** Reports the real world address of the decker.
>
>
>
>CyberCombat: (Virtual Realities, p. 48)
>
>IC have a target equal to the persona attribute that is used as target.
>
>Decker resists using MPCP plus whatever they wish to allocate from Hacking
Pool.
>
>Shield Programs may be used against Killer IC or Attack Programs.
>
>Hardening reduces the final damage of Blaster/Killer/Attack Programs.
>
>All damage is recorded on MPCP's Monitors; 10 boxes and the decker crashes.
> All damage except that of Blaster IC can be restored by restarting the
> deck or by using a Medic Program.
>
>
>
>COPYRIGHT: 1995
> I claim authorship for this work with respect given to the
> Shadowrun(tm) game system for which it is derived. I don't want
> cash if you use it unless you opt to make money from it.
>
>
--
I know where my towel is, do you?
GC3.1
GO>CS d- s:--- a21 C++++>$ U--- P L-- E? W+>W+++ N o? K? w+>w++++ O--- M-- V
PS+++ PE Y+ PGP- t++ 5+ X++ R++>+++$ tv++ b- DI++ D+ G++ e* h r++ y++

Further Reading

If you enjoyed reading about Decker resolution system, 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.