Discussing: The Intruder

jedion357's picture
jedion357
May 22, 2011 - 5:20am
Refer to: The Intruder.

How would the PCs know that the virus was planning to send a message before it did? How would the PCs track the virus through the computer system?

Perhaps the virus is an AI that writes its own programs. As the PCs investigate the computer problems they discover newly written programs that they can only partially read but a successful skill check will tell them that the new program seems to be protocols for aligning the communications array and sending a messages.
With a good roll the computer expert will be able to estimate how long before the program is finished and it can send a message. Then they have that long to prevent it in some way.

Barred from sending a distress message, the AI/virus could then try to infect navigation and propulsion and begin writing protocols to allow it to navigate the ship to its desired location. Again computer specialist can estimate time on the program writing but even if the AI begins to move the ship on its own travel takes time so the PCs will have time to deal with that.

Finally the AI will if balked from moving the ship or if it seems the PCs will be able to stop him eventually can invade the life support program and delete it. This becomes serious. A referee will need some idea on how long till the atmosphere of the ship sours plus the heat loss will begin to tell eventually as well. PCs can cut the life support equipment out computer control but it will require constant monitoring.

Does the ship have robots and a robot management program? This would give the AI/virus some proactive measures it could take including the re-writing of a robot's programing to allow it to express itself through the robot and interact like a person with the PCs- though I suspect that the PCs will quickly reach the "just shoot it" level of reaction.

Finally, pirates are to bland of a enemy, make the threat a civilization of AI/virus'; if they get to the Frontier its all over as they will bring down every computer network they touch.

Naturally, the PCs could discover the location of the AI/virus civilization since the nav protocols that it was writing would hold the location. After they get their ship under control and solve this adventure they could of the own curriousity go to investigate this location or be ordered to go and investigate this location.
Which leads to adventure 2

Adventure 2 would be about discovering the scope of the danger to the Frontier and the true threat of the AI/virus

Adventure 3 should build to a big ending with lots of explosions, blood and distruction.

anyway these are just a few idle musings.
I might not be a dralasite, vrusk or yazirian but I do play one in Star Frontiers!
Comments:

Anonymous's picture
w00t (not verified)
May 22, 2011 - 6:58pm
The PC's will not be able to anticipate a distress call, however they should be able to detect it. I'll clarify that in the document. 

The virus is an AI and I agree, it should be able to write sub-routines for all the systems on a ship that are interconnected. I would think the only system not interconnected would be life support and its redundant nature. 

The AI may even try to copy itself to portable computers, maybe even one the PCs are carrying. Muhahaha.

In my games robotics and computers are separate skills, the AI would need a robotics skill/program to infiltrate robots and re-write their missions. 

Plot Hooks
  • The AI was developed by either a long-lost race, ancients or race on the other side of the galaxy. The AI may have been intended for an enemy and wiped out the enemy and the original developers. 
  • The AI was aboard a probe and found its way into the frontier sector.
  • The AI was developed by the sathar clan-y to take out clan-x and became rouge.
  • The PCs find a sathar clan-y ship, board it, the AI jumps over to their ship and takes it over. The AI either destroys the PC ships or takes off with it, the party must now learn to fly the sathar ship in order to get home. 

iggy's picture
iggy
May 22, 2011 - 9:16pm
What if the AI was on a spy mission to retrieve enemy data.  Now it is on it's way home and the player's ship is just another in a series of pawns to be used to get it home.  The players find the derelict alien ship the AI was traveling in.  It had used up all of the ships fuel and was just waiting for another ship to come within range that it deemed safe to appropriate.  Now it is on it's way with the player's ship.  The player's can stay for the ride as long as they don't try to stop it (which they will).  The AI expects that the players will just starve and perish during the journey.  The AI may even be taking a route it knows is dangerous to biological life (near stars, through radioactive nebulae, etc.).

-iggy

Anonymous's picture
w00t (not verified)
May 22, 2011 - 9:38pm
iggy wrote:
What if the AI was on a spy mission to retrieve enemy data.  Now it is on it's way home and the player's ship is just another in a series of pawns to be used to get it home.  The players find the derelict alien ship the AI was traveling in.  It had used up all of the ships fuel and was just waiting for another ship to come within range that it deemed safe to appropriate.  Now it is on it's way with the player's ship.  The player's can stay for the ride as long as they don't try to stop it (which they will).  The AI expects that the players will just starve and perish during the journey.  The AI may even be taking a route it knows is dangerous to biological life (near stars, through radioactive nebulae, etc.).


I like this idea.

  1. A Streel spy breaks into PGC corporate systems, uploads the intruder AI. Spy dies soon after the break-in, Streel can't risk being detected and abandons attempt. AI grabs data and makes it way to a terminal to meet its contact, the dead spy. Not finding him the AI jumps from system to system finding its way to the starport where it steals aboard a ship. 
  2. Jumping form ship to ship it finally ends up stranded in a remote part of a star system (pause for effect) where the PCs encounter the vessel. Dun Dun DUN!

Anonymous's picture
w00t (not verified)
May 23, 2011 - 7:30pm
The Intruder Overview
  1. Determine where the AI virus originated from (the developers).
  2. Determine how the PCs are introduced to the virus. Lots of ways to implement this but I think aboard the PCs ship is the best fit. Builds a sense of urgency and drama, especially if life-support is cut off or hampered. 
  3. Build a flow chart of systems on the ship that can be effected from lights to navigation.
  4. Build time line of events, what gets effected and when
  5. Conclusion of adventure.

Ship Systems
  • Propulsion - thrusters, navigational thrusters, void engine/FTL
  • Life Support - interconnected to main computer or seperate?
  • Computer(s) - main computer, other computers, backup computers. How are they interconncted? 
  • Navigation
  • Astrolocation systems
  • Communications
  • Detection
  • Emergency systems (computer and hardware)
  • Weapons
  • Defenses
  • Other systems such as mining, exploration, research, labs, passenger systems, transport, agriculture, etc.
  • Drive systems
  • Fuel systems
  • Alarm and intrusion systems
  • Camera systems
  • Computer lockouts
  • Damage control system (DCR)
  • Shuttles/Landers
  • Intercom and monitor systems
  • Long range detectors
  • Escape pods
  • Cryostorage passenger bays
  • Atmoprobes (great place for an AI to hide)
  • Landing drones
  • Robot management program (and some robots!) Use this to give the players something to take out their frustrations on. Helps players that simply like combat. Let these players handle the robots while others save the ship.
Computer Programs
  • Analysis 
  • Bureaucracy 
  • Commerce 
  • Communication 
  • Computer Security
  • Industry 
  • Information Storage 
  • Installation Security
  • Language
  • Law Enforcement 
  • Life Support
  • Maintenance
  • Robot Management
  • Transportation
Event Time Line
....still working on this.

jedion357's picture
jedion357
May 23, 2011 - 8:31pm
Phone conversation with w00t wrote:
How to run the intruder adventure?


two ideas:

1. have a timeline that begins with turn #1 on the turn the ships computer becomes infected and then tells you which program is being infected or manipulated on subsequent turns. Bigger programs take the AI/virus longer to digest. Eventually the AI will begin to write new protocols to facilitate its control of the ship.

2. make a chart of each program in the computer that is rolled on with randomly to see which program is being infected. The chart will include how long the program will take the AI to digest before it jumps to another program and the sorts of things it will manipulate/play with while it is figuring out the program like turning on entertainment programs and running the engineer's dralasite porn from every computer monitor ont the ship, deleting all the astrogation star system files, turning off lights, activating the alarm program for the engines etc.

Also have a general page of referee info describing the basic strategy of the AI as it seeks to commandeer the ship: Writing new protocols to navigate the ship to an uncharted system, when or if this activity is prevented it could attack the PCs but crashing the life support system forcing them to post a PC to monitor the life support equipment after  cutting it off from the computer, and finally sending a distress call via the subspace radio. If the computer has a robot management program then the AI/virus will have another means by which it can mess with the PCs
I might not be a dralasite, vrusk or yazirian but I do play one in Star Frontiers!

Anonymous's picture
w00t (not verified)
May 24, 2011 - 2:57pm

In order to determine what system is effected roll on the following table.

Roll
Effected System
01-04 Life Support
05-08 Propulsion
09-12 Computer Programs Table
13-16 Navigation
17-20 Astrolocation systems
21-24 Communications
25-28 Detection systems (external and/or internal)
29-32 Emergency systems (computer and/or hardware)
33-36 Weapons (all or signally)
37-40 Defenses (all or signally)
41-44 Pick a system; mining, exploration, research, labs, passenger systems, transport, agriculture, etc.
45-48 Engine sub-system
49-52 Fuel systems
53-56 Alarm and intrusion systems
57-60 Camera systems
61-64 Computer lockouts
65-68 Damage control system (DCR)
69-72 Shuttles/Landers launch systems
73-76 Intercom and monitor systems
77-80 Long range detectors
81-84 Short range detectors
85-88 Escape pod ejection system and computer controller
89-92 Cryostorage passenger bays
93-96 Atmoprobes (great place for an AI to hide)
97-00 Landing drones


Computer Program Table
Roll 2d10 on the following table

 Roll Result
01
Computer: Analysis 
02 Computer: Bureaucracy 
03 Computer: Commerce 
04-05 Computer: Communication 
06 Computer: Computer Security
07 Computer: Industry 
08 Computer: Information Storage 
09 Computer: Installation Security
10 Computer: Language
11-12 Computer: Drive
13-14 Computer: Robot Management*
15 Computer: Life Support
16 Computer: Life Support, backup
17 Computer: Maintenance
18 Computer: Law Enforcement 
19-20 Computer: Transportation