Legacy of the Dominion

[Solluk]

Mission Title: Legacy of the Dominion

Synopsis: While the Discovery is studying the formation of a singularity, replicators on the Discovery all begin to replicate spherical, floating combat drones which attack nearby crewmembers, target control consoles, and jam communications.   Without control, the ship is in danger of being sucked into the forming singularity.  The crew must fight these combat drones, repair the ship, and get clear of the singularity. Finally, they must discover why this has happened.

Starting Point: While the Discovery is studying the formation of a singularity, a radiation discharge causes a glitch in the ship's replicators, necessitating a system reboot.

End Goal: The crew must get clear of the singularity and figure out what happened.

Story points that must be passed?:

I) Discovery begins studying the formation of a singularity, an interesting Scientific mission.  A discharge of radiation from the singularity corrupts the firmware in the ship's replicators, requiring a reboot and re-initialization.

II) All the replicators aboard begin replicating spherical combat drones which attack nearby crewmembers, target control consoles, and jam communications.

III) The crew must combat the drones and take the replicators offline while hastily conducting repairs.

IV) The ship must be piloted away from the forming singularity in time to save everyone.   Depending on the extent of the damage done by the drones, this may require the launch of shuttles to tow the ship clear.

V) The source of the problem is uncovered by Engineering/Ops personnel, possibly with the assistance of Detective-minded Security officers:  During the Dominion war, the Discovery received new replacement replicators from a starbase that had been infiltrated by a Changeling.  These replicators were illicitly programmed to create these combat drones to sabotage Starfleet vessels.  The sabotage software was never activated because the changeling was discovered and killed, years ago, before he could send the go-signal.  But the recent firmware re-initialization accidentally activated the long-dormant sabotage program.

VI) Once Engineering/Ops discovers the source of the problem, they can alert other vessels that received replacement replicators at about the same time, as they may also have this sabotage software lurking aboard, waiting to wreak havoc if the system is ever rebooted.

Departments: (To make sure everyone has something to do.)

- Flight: Everyone will have to battle drones.  The Flight officers will have to get the ship clear of the singularity.

- Engineering: Everyone will have to battle drones.  The Engineers will work with Ops to fix damage and diagnose the nature of the problem.

- Operations: Everyone will have to battle drones.  The Ops personnel will work with Engineering to fix damage and diagnose the nature of the problem.

- Security and tactical: Everyone will have to battle drones.  But especially Security officers.  Any detective-minded security officers may also help to unravel the mystery of why this happened.

- Medical: Everyone will have to battle drones.  There will also be many injuries.

- Science: Everyone will have to battle drones.  Perhaps Science personnel can isolate some weakness in the drone design that can disable them en masse.