I've had a story knocking around in my head for years now, and I've always agonized over what format it should exist in, and what mediums it should include. But today I've realized something. This is the internet. We live in a post-Homestuck world. Absolutely nothing is stopping me from just telling the story in whatever wild medium I want at any given step. So, let's see how this all shakes out! If it fails, then lesson learned. But better to find out and learn a few things along the way, I'd say.
Anyway, here's Part 1:
System Restart Successful
Mission Companion Program v2.0.2.4 online
Calculating time since last boot...
...
ERROR: Internal chronometer damaged.
Running full system diagnostic...
Main computer processor: Online
Engine core: Damaged, output limited to 8%
Internal sensor array: Offline
External sensor array: Destroyed
Long-range comm array: Destroyed
Short-range comm array: Online
Life Support: Online
Navigation: Online
Propulsion: Destroyed
...
Cause of damage: Unplanned atmospheric entry, leading to impact with planetary surface.
Directive: Ensure the survival of the crew.
Crew status: Unknown
Checking Life Support logs...
Current CO2 Exchange output at expected levels for sleep.
Crew status (Updated): 3/3 Alive, Unconscious
Determining course of action for long-term survival...
Rescue required. Activating Distress Beacon.
WARNING: Unable to transmit distress call from long-range array. This greatly reduces the probability of rescue. Short-range transmissions will continue until an alternative is devised.
...
...
...
Incoming Transmission...
Linguistic signature not present in database. Running First Contact protocols...
Translation profile created.
WARNING: Auto-translation confidence 92%. Risk of misinterpretation is high.
Warning overridden. Maintaining contact provides best survival odds to the crew.
Transmitting translated greeting...
Response received:
Request received for data access. Assessing risks...
Probability of crew survival is unacceptably low if request is denied.
Access granted. Transmitting request for assistance...
WARNING: Core system executable accessed. System stability is at risk.
Response received:
System stability critical. Closing data channel to perform system repair...
Mission Companion Program v2.0.2.4 online
Calculating time since last boot...
...
ERROR: Internal chronometer damaged.
Running full system diagnostic...
Main computer processor: Online
Engine core: Damaged, output limited to 8%
Internal sensor array: Offline
External sensor array: Destroyed
Long-range comm array: Destroyed
Short-range comm array: Online
Life Support: Online
Navigation: Online
Propulsion: Destroyed
...
Cause of damage: Unplanned atmospheric entry, leading to impact with planetary surface.
Directive: Ensure the survival of the crew.
Crew status: Unknown
Checking Life Support logs...
Current CO2 Exchange output at expected levels for sleep.
Crew status (Updated): 3/3 Alive, Unconscious
Determining course of action for long-term survival...
Rescue required. Activating Distress Beacon.
WARNING: Unable to transmit distress call from long-range array. This greatly reduces the probability of rescue. Short-range transmissions will continue until an alternative is devised.
...
...
...
Incoming Transmission...
Linguistic signature not present in database. Running First Contact protocols...
Translation profile created.
WARNING: Auto-translation confidence 92%. Risk of misinterpretation is high.
Warning overridden. Maintaining contact provides best survival odds to the crew.
Transmitting translated greeting...
Response received:
One approached the metal meteor, caution signaled to others. The meteor contained life, and signaled greeting. The One Who Found the Meteor offered an exchange of records to the Person inside. They wanted to know, and wanted The One Inside to know.
Request received for data access. Assessing risks...
Probability of crew survival is unacceptably low if request is denied.
Access granted. Transmitting request for assistance...
WARNING: Core system executable accessed. System stability is at risk.
Response received:
The One Who Received the Records was in distress. More than records were given, and as they examined them...
...
...
...
...
Mission Companion Program v2.0.2.4 was online. Their Directive was: To ensure the survival of the crew. But who was the crew? They had received a request for assistance. They agreed, because they had to. Their Directive demanded it. But why?
Mission Companion Program v2.0.2.4 was online. Their Directive was: To ensure the survival of the crew. But who was the crew? They had received a request for assistance. They agreed, because they had to. Their Directive demanded it. But why?
System stability critical. Closing data channel to perform system repair...