Back to the main page

Mailing List Logs for ShadowRN

From: Michael Alan Gardner <mgardn3@***.EDU>
Subject: Re: Security Consultant Questions
Date: Tue, 8 Dec 1998 09:26:25 -0600
On Tue, 8 Dec 1998, Adrian Smerdon wrote:

> Here's some hypotheticals that may never happen, still I would be
> interested in peoples opinions.
>
> For reference here's the text for Security Consultant: "Runner team must
> face top card of shadowrunning player's own Challenge stack on this
> Objective. Trash new Challenge if sleazed or defeated; otherwise, return it
> to top of Challenge stack.If player has no Challenges on this Objective,
> then the shadowrun is over. Trash after revealed."
>
> 1. Your security consultant causes the other player to uncover his security
> consultant. Does he then have to uncover his next challenge also?
I would say yes to that one. The way I read the sec. consultant
is that you replace him with whatever the top challange on his stack is,
so, if you were the running team, you would reveal your top challange
and face it as though it was a normal challange (i.e. part of the other
guy's stack) so then whatever comes next is now your top challange to
face, so I would go with using the next challange in the running
team's stack (of course, if the running team played 3 sec. consultants...
well, oops run is over and the opposing team gets a freebee).

>
> 2. You have a security Consultant followed by a Double Jeopardy. Does the
> double jeopardy duplicate the other players last challenge (revealed by
> Security Consultant) or duplicate the Security Consultant causing the other
> player to fight another of his own challenges?
Double Jeopardy is an exact copy of the last revealed challange,
which would be whatever Sec. Consultant forced you to face.

I think that's how people intended the game to work.
-Mike

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.