Think in terms of Star Trek; Shuttle flight crew of pilot/co-pilot, a
scientist, and two engineers with various specialist tendencies.  Also,
since this IS the International Space Station, perhaps a political observer
or two?  What if one government was running an illicit experiment?  Or the
last shipment up from West Bogoslavia was contaminated...they might want to
send an observer who was a double agent.  

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Roger Burton West
Sent: Tuesday, January 24, 2006 9:27 AM
To: [email protected]
Subject: [gurps] Suggestions wanted for adventure (near-future, NASA)

I'm working on a near-future horror adventure to be run as a one-shot. I
have some idea of what's actually going on, but I'm not going to talk about
that here. The premise/players' briefing is that the International Space
Station has dropped out of communication; there is no external sign of
damage (I'm still considering what may have been done with the Soyuz escape
craft). A Space Shuttle is sent up with a crew of specialists to (a) find
out what's gone wrong and (b) evacuate the station crew if necessary.

What will NASA suspect might be wrong, and whom will they send?

Possible causes of loss of communication:

* Power failure (suggests a mechanic/engineer type)
* Communications failure (ditto)
* Life-support failure (suggests a life support tech)
* Medical emergency (disease or food poisoning; suggests a doctor)

Anything else? Those three, combined with two Shuttle flight crew, would
fill the available personnel slots on the orbiter (leaving space to evacuate
the station crew). Are there any other skills that need to be represented,
or things that might go wrong that I haven't thought of?

Roger
_______________________________________________
GurpsNet-L mailing list <[email protected]>
http://mail.sjgames.com/mailman/listinfo/gurpsnet-l


_______________________________________________
GurpsNet-L mailing list <[email protected]>
http://mail.sjgames.com/mailman/listinfo/gurpsnet-l

Reply via email to