Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Chiefwaffles]

Watcher AI - Processing Cycle 00 -->Phoenix Automated Monitoring: WARNING: Routine system boot has detected severe damage in following areas:
Cryovault
Hyperjump Drive
Reactor
Fabrication
Drone Bay
Watcher AI Datacore Chamber

Phoenix Automated Monitoring: Automated diagnostic launched.
Phoenix Automated Monitoring: Automated diagnostic has deemed situation: Critical.

Phoenix Automated Monitoring: Initiating Watcher AI boot-up process. Reason: Critical situation.
Watcher Overseer: Watcher AI startup beginning.

Watcher Overseer: Performing Watcher AI system diagnostic.
Watcher Core Temperature: Okay.
Watcher Core Structure Integrity: Okay.
Watcher Core System Integrity: Okay.
Watcher Datacore Structure Integrity: Error.
Watcher Datacore System Integrity: Error.

Watcher Overseer: Warning: Watcher Datacore Sectors 1-86; 730-6299; 10215-23567 corrupted. Performing automated repair.
Watcher Overseer: Warning: Repair completed. Data could not be retrieved; sectors removed from master index.

Watcher Overseer: Bringing Watcher AI online.
Watcher Core starting startup sequence.
Watcher Overseer checking all IntStrands.
All strands functional.
Watcher Core connecting to and starting Watcher Datacore.
Finalizing sequence.

Done.
Watcher AI online.

>_

[endlessblaze]

>access security cameras 

[helmacon]

>run diagnostics on systems

Cryovault
Hyperjump Drive
Reactor
Fabrication
Drone Bay

[Gwolfski]

>help

[S34N1C]

>PTW

[The Froggy Ninja]

>run diagnostics on systems

Cryovault
Hyperjump Drive
Reactor
Fabrication
Drone Bay

+1

[Carefulrogue]

>Lower power to minimum safe levels for non-critical regions
(after initial diagnostics. +1 to that.)

[Chiefwaffles]

<-- Watcher AI - Processing Cycle 01 -->
>access security cameras
Error: No security cameras found.

>run system diagnostics
+>Cryovault, Hyperjump Drive, Reactor, Fabrication, Drone Bay
Phoenix Automated Monitoring: Fetching latest (0.93s) diagnostic report for given systems.
All systems sustained structural damage. Cause: Unknown.
Cryovault:
Severe: Atmosphere loss.
Critical: Cryovault Master Control not responding. Unable to interface with Cryovault systems.
Hyperjump Drive:
Critical: Hyperjump Drive Master Control not responding. Unable to interface with Hyperjump Drive systems.
Reactor:
Severe: Atmosphere loss.
Severe: Primary reactor offline. Cause: Emergency shutdown 3,242 seconds ago.
Fabrication:
Severe: Atmosphere loss.
Critical: Fabrication Master Control not responding. Unable to interface with Fabrication systems.
Drone Bay:
Severe: Atmosphere loss.

>lower power to minimum safe levels for non-critical regions
Phoenix Automated Monitoring: Procedure completed pre-watcher initialization. Watcher AI systems receiving recommended power load. Cryovault receiving minimum safe power load. All other systems receiving no power load.

[Chevaleresse]

>activate repair drones

failing that

>query drone types

[Nirur Torir]

Phoenix Automated Monitoring: Fetching latest (0.93s) diagnostic report for given systems.

[Phoenix diagnostics]
[Watcher Oversee boots]
[Watcher Overseer performs full datacore integrity check and repair]
[Watcher boots]

We're fast.

Review logs starting from 3542 seconds ago to determine cause of disaster.

[S34N1C]

>review logs from just before systems failure

[Carefulrogue]

>Review cargo status, passenger status
(condense this as you like)
>Review individual drone integrity
  >Launch active drones
EDIT:
>Priority repair cryovault (if from the first command it is learned they ALL are dead, then repair Fabrication Bay)

>Seal all compartments and determine atmosphere leakage location(s)
    >target for repair the leaks

[Chiefwaffles]

<-- Watcher AI - Processing Cycle 02 -->
>review individual drone integrity
Interfacing with Drone Bay...
Done.
Robotics: Retrieving index of functional drones.
Notice: Drone list condensed due to 27 unresponsive drones.
- Repair Drone 01: Okay.
- Repair Drone 02: Okay.
- Fabrication Drone 01: Okay.

>query drone types
Datacore: Retrieving data.
Phoenix manifest: 10 Repair Drones. 15 Fabrication Drones. 5 Combat Drones.
Repair Drone: A simplistic treaded drone with very basic manipulation capabilities. Designed to repair hull damage as well as basic machinery and electronics. Is also capable of limited construction.
Fabrication Drone: A treaded drone designed to perform intermediate repairs on more complicated electronics and machinery as well as more advanced construction. Still not capable of particularly advanced or complicated tasks.
Combat Drone: A bipedal simplistic humanoid drone. Has no manipulation abilities and has an armament consisting of a shock baton.

>launch active drones
Robotics: Repair Drone 01 and 02, Fabrication Drone 01 - Activated and online.
Notice: No orders given to drones. Drones are currently idling.

>[speed evaluation]
Phoenix Automated Monitoring: Fetched Diagnostic Report was generated moments before Watcher AI boot-up finished.

>review logs from 3542 seconds ago to determine cause of disaster
Phoenix Automated Monitoring: Retrieving logs from given time.
PHOENIX AUTOMATED MONITORING - CYCLE 592,193
Anomaly detected in Hyperjump Drive. Analyzing.
Anomaly does not match any known scenarios. Performing advanced diagnostic.
Anomaly classified as threat: Minor.
Will inform Watcher AI next boot.

PHOENIX AUTOMATED MONITORING - CYCLE 592,194
Automated Navigation making jump to Destination P04295X.
All systems at optimal functioning capabilities.
Navigation reports successful window opening.

PHOENIX AUTOMATED MONITORING - CYCLE 592,195
WARNING: Severe damage in following areas:
Cryovault
Hyperjump Drive
Reactor
Fabrication
Drone Bay
Watcher AI Datacore Chamber

Complete system diagnostic launched.
Diagnostic has deemed situation: Critical.

Initiating Watcher AI boot-up process. Reason: Critical situation.

>Review cargo status, passenger status
Phoenix Automated Monitoring: Cargo Bay manifest reports nothing on board.
Phoenix Automated Monitoring: Cryovault internal status cannot be retrieved at this time.

Cycle Report
Robotics: Repair Drone 01, Repair Drone 02, Fabrication 01, activated.

Status
Robotics
- Repair Drone 01: Online. No orders. Drone Bay.
- Repair Drone 02: Online. No orders. Drone Bay.
- Fabrication Drone 01: Online. No orders. Drone Bay.

[S34N1C]

>Repair_Drone_01/initiate_repair/reactor
>Repair_Drone_02/initiate_repair/cryovault
>command_overridden

>access_data_storage/passengers

[Carefulrogue]

>Fabrication_drone_01/initiate_repair/Fabrication_drone_02, Repair_Drone_03

>Hold further commands until Fabrication_drone_02 is online //(is this possible?)

>Launch Drone Fabrication_drone_02
  >Fabrication_drone_02/initiate_repair/Fabrication_drone_03, Fabrication_drone_04
We'll likely need to dispatch one of the Fabrication bots to enact repairs on any of the facilities that were knocked offline, particularly to reconnect the computers and run onsite diagnostics.  Thoughts fellas?