01:23 @ 2236-10-03
TSO 1 : Waking up Wrecked
Be sure to read and follow the guidelines for our forums.
01:23 @ 2236-10-03
Adonis twitches as his automated systems come back online. The sleek and sophisticated robotic life form lays motionless as his visual receptors and other sensors bring a flood of information to be processed.
Location : Communications Hub
He quickly analyzes and identifies his surroundings as the armory of the Odyssey. He is laying on the floor next to the door of the room lit only by emergency lighting.
A slight flicker as a set of foreign symbols scroll across the top of his vision The visor . . Instant discord fills his processing unit and he quickly runs some basic diagnostics. Physically fine Adonix is dismayed at the state of his internal logs. Recent memories have been wiped, corrupted, or encrypted, and there are signs of a digital infection still active in his system. Glancing at the security console nearby he checks the ship status. According to the ship systems the current time is 01:23 @ 2236-10-03. But the last clear searchable memory is dated 2236-08-21. Over 6 weeks are missing.
Sitting up Adonis finishes his diagnostics and removes the visor. It was acquired . . on this mission . . and only he could properly utilize its functions. It seems to have several basic scanner functions built into it but accessing them has proven problematic. Could the visor be the source of the digital infection? Unknown.
Looking around he notes that most of the small arms have been removed from the armory. This would require the captain or first officer and one other security personnel to do this. Moving to the console he interfaces with the ship’s system's and finds that it too has suffered both physical and electronic damage. Working to reset faulty systems and restore internal sensors, Adonix is filled with unease.
Objective: Restore internal and external sensors. You have no idea what the state of the ship is and with your gaps in your memories do not feel sending a distress beacon is the best option at this time.
Sam, blinks to clear her sight as her thoughts slowly form a clear idea of where she is.
Location : Engineering Bay
Raising up to look around you see the main Engineering bay are alarmed to see damaged machinery and exposed wiring. Moving to stand you have to grab a nearby rack as nausea washes over you. Quickly checking the status of ship Sam is first confused. Engineering has been physically isolated from the rest of the ships network, but even worse the date. What happened? Thinking back Sam instantly gets a headache as she tries to recall anything recent as according to the computer she is missing 6 weeks of memory but the last engineering entry is by her from a couple of days ago.
Getting lightheaded you realize that it is hard to breath. Checking the console you verify that engineering is on local life support and it is struggling. Looking up from the console she confirms that engineering is sealed tight, from the inside. She did this, but why?
Status & Objective : Systems compromised. Extensive damage. Repair is imperative. Survival depends on the restoration of power and life support systems. Failure is not an option.
Stinger tries to focus as his head swims and he is forced to brace himself with a set of secondary arms. Shaky from lack of food and lightheaded from air too thin it is hard to focus.
Location: Bridge
Looking down at the bridge's navigation console you try to recall what exactly happened. Your compound eyes instantly take in the entire bridge with flickering consoles and emergency lighting. Most of it seems to be locked down by a combination of codes you can't override at this time. However the ships navigation systems is beeping incessantly, warning of imminent danger. Frustration washes over you as your attempts to access external sensors or navigation records are baulked at each turn. The ship’s automated navigation is offline but luckily enough of it is functional to identify a threat. You just wish you knew what is was and how much time you have to avoid it. You have restored basic thruster control through access emergency overrides but without sensors or logs of where you are you are blind.
Objectives : Recover navigation logs and plot a route to safety.
Alandra, the ship’s dedicated medical officer, awakens on the cold floor of a dimly lit room.
Location: Medical Bay
By the smell of it you are in the medical bay. The soft hum of the med bays independent life-support machine is somewhat comforting. The sterile environment is a stark contrast to the turmoil in your mind. Flashes of arguments, treating the crew, and, and, it fades in a flash of white and a blinding headache. Picking yourself off the floor and lying down on the the examination table you start it it running through self diagnostics and then have it check yourself. At the tone indicating the scans are complete a glance at the chart slightly reassures you. Minor injuries and dehydration as well as lack of nutrients. Your stomach rumbles at the thought of food. But then you notice that all medical logs since the ship left port are locked down by a chief medical officer, but is isn't your credentials. Able to get access to your own records you notices that several scans were run with multiple anomalies, and the ship left port over 6 weeks ago but you can remember none of it. Leaning back to think you see a piece of paper on the floor next to where you awoke. Picking it up you see a set of security codes and . . . Oh, that's not good.
A quick check confirms that ship life support has been set to minimal. Anyone without independent life-support would soon find themselves almost suffocating.
Objectives : Stabilize the life support and check on the crew's condition.
I will unhide individuals opening scenes once everyone post in response.
She thinks to herself,One thing at a time, get life support up even if on emergency power then restore main power. Then tackle the unknowns.
She pulls up the schematics of the ship in her brain from the processor embedded in her and begins to work on fixing life support.
Rolls
Life support - (2d6)
(52) = 7
You should be able to access the shares TSO ship sheet by clicking the button below the "Rolls" section. Images of the ship layout are in the History section, bottom right
Tracing the systems status she can check she finds the main network feed to and from engineering was manually disconnected or severed. Turning she sees the panel in question is open and cables laying haphazardly pulled out of it.
He goes to work on fixing the sensors.
Rolls
Sensors - (2d6)
(13) = 4
Adonis gets to work and finds that many systems are locked out. Fortunately he can get the CCTV security feeds of the hallways at least and quickly determines the entire ship is worse for wear. Low level lighting only and multiple signs of damage can be seen. Cycling through various systems Adonis slowly learns that many have officer lockouts in place. However he is eventually able to get some basic information.
+ Current crew count aboard = 6 (Identities locked out)
+ Shuttlecraft : launch authorized by 1st officer (no further information)
+ Bridge and Engineering are not responsive from the security terminal
+ Internal comms are offline with multiple lockouts in place but with a bit of effort the emergency alert systems could probably be converted to a PA system.
+ Internal life support = Minimal atmosphere and temperature in the halls. Individual rooms are heated but have even lower oxygen to the point that any exertion by biologicals would soon lead to fatigue or even unconsciousness
As he is trying to make sense of the situation, he can't
concentrate because of a constant beeping... a beeping? Oh an imminent emergency! And coming from the navigation system.... He sees the wide window at the front for anything he can see with his eyes (he will turn on external lights if there are some). He finally realizes the ship in under threat, it may crush if it continues the current path. He tries again to use the Comms to check for other members of the crew, he can't remember who came with him to this ship, but this model is not for one person to fly alone... but Comms are off.
He checks the instruments for speed the bearing... First possible case: ship is floating with no speed then the threat (maybe a big asteroid) is coming to the ship... Second case: the ship has some speed, maybe we are heading to something (maybe an asteroid)... Stinger hates asteroids when he can't see them! Of course the threat may be different, but thinking of space pirates would only make him dizzier. Anyway, staying as they are is way riskier than trying to change course. And, at a wrong turn, the beeping would increase speed, so...
He check the ships instruments. If he sees the threat using the window, he turns away from it at full power.
If he can't see the threat using the window (or there are no windows): On case 1 (ship is floating) he turns 90 degrees to the right and ignite thrusters at 20% power. On case 2 (ship is moving), he steers the direction to it's opposite (p.e. if instruments show north, the turn south) and levels power at 20%.
I wish we had sensors online...
Rolls
Changing course - (2d6)
(53) = 8
Evasion attempt (if needed) - (2d6)
(21) = 3
Her head pounds and she temporarily swoons with the sickening pain, but catches herself in the medbay's console.
She looks at the set of security codes.
"Maybe I shutdown the medbay temporarily. Hopefully, that will give the life support more juice to work with.", she thinks and starts trying every security code on the sheet of paper.
Rolls
Login to Medbay - (2d6)
(12) = 3
Shut it down temporarily - (2d6)
(11) = 2
He checks the instruments for speed the bearing...
He check the ships instruments. If he sees the threat using the monitor, he turns away from it at full power.
After trying to change to a safer course, Stinger prepares evasive action.
Rolls
Secret Roll
So, now let's try to figure out where are we. He takes some time to focus on recovering the main navigation log and the stellar map.
Rolls
Recovery of main logs - (2d6)
(56) = 11
"Maybe I shutdown the medbay temporarily. Hopefully, that will give the life support more juice to work with.", she thinks and starts trying every security code on the sheet of paper.
As she waits a could of soft tremors rub through the ship. Collision? Not direct. Still, she hopes someone is awake on the bridge.
When the system finally lets her re-enter the codes she slows down and gets it entered properly. A quick check reveals according to the logs she disabled most of the air scrubbers some rooms ago and quickly she reactivates them as well as increasing circulation after verifying the air is clean and safe. It may take a few minutes for the air to improve.
Console
Helmsman locked out from external sensors. Insufficient authority to override.
Stinger reads the navigation logs he just recovered... Where are we? Where did we come from? What did actually happen to the ship? Where were we going before this mess happened? Are there more crew members on board?
Adonis switches to view the status of the internal comms. Offline, officer lockouts, no way of contacting the other six crew members on board… But an idea comes to his head. He glances up at the emergency lighting again. Perhaps if he reworked the emergency light into a PA system, he could communicate through the speakers, gather everyone together.
He begins refiguring the emergency system.
Rolls
Converting emergency to PA - (2d6)
(12) = 3
Console
A loud squealing claxxon sounds throughout the ship and begins modulating as if chainsaws were serenading with the accompaniment of metal grinders and 1000 cats.
After s minute the volume gradually reduces and it starts to cycle through random phrases and then stops before a single word repeats 3 times while still adjusting the volume
ATTENTION ATTENTION ATTENTION
@QuingSolaris It's like you are making a note by clipping out words from magazines.
Your hack works but you end up having to use existing ship code with built in phrases to try and communicate what you want to say over the emergency alert speaker system
It's Stinger getting a picture?
I trapped myself in here for a reason but time has passed that I cannot account for. Guess I will have to risk restoring power and go from there. One problem at a time. Fix power, then next issue of what do i find on the other side of the door.
She checks her sidearm just in case.
Rolls
restore power - (2d6)
(12) = 3
drive back up - (1d6)
(4) = 4
drive backup for power - (1d6)
(4) = 4
Sam starts slowly pushing power back to key areas of the ship. First checking life-support sighs with relief as the system registers and increase in use back to normal levels. Sam then moves onto other systems, starting with shields, sensors, propulsion, but leaves internal basic infrastructure (lights, plumbing, wall outlets, etc) and sensors as well as ship external weapons offline for now. Just to be safe.
As Stinger monitors the ships position as best he can with only visual cues he is elated when he sees power being resorted to the thrusters. However without the use of the ships primary sensors he will have to be very careful. Making a decision Stinger heads towards what he hopes is a the shortest path out of the ring. But without the other external sensors he is unable to product so the motions of the pieces of the ring and several impact the ship's shields before he is able to get clear of it. Fortunately he is able to minimize the impacts so none style the ship itself.
She inhales deep, letting the air fill her lungs. She relishes the relief for but a moment before something inside her makes her act.
She looks around the med bay for a portable diagnostic tool. According to her scattered memory she is a doctor. She better act like one.
Once she finds her device, she'll make a b-line for the bridge. Hopefully there's no injured.
"Hopefully. I can get some answers.", she thinks.
She suddenly notices a load blaring in the background. It must have been going for sometime, but she was concentrating too hard on the console to hear it.
"What is that? What is the bridge doing?", she says
Rolls
Look for portable diagnostic tool - (2d6)
(52) = 7
Sam is restoring power and but with an unplugged network, which was obviously done by her in a hurry, she has limited information. However she is somewhat relieved when power restored to both life support and thrusters were put to God use. What next...
Stinger is checking nav logs and while most are in tact there are a couple of corrupted FTL entries. He's starts working from the most recent backwards. He starts accessing other logs to try and recreate these and find an officers log.
Summary:
We hacked the ships systems, disabling them as much as possible before fleeing the ship in the shuttle. We are heading to the life supporting planet nearby. It’s a long shot, but it’s our only hope. With luck, we’ll make it and send help. The captains actions have turned this ship into a tomb for any who remain. Hopefully our efforts will keep the captain from causing harm elsewhere. Signing off.
The officers felt they needed to escape in a shuttle not sure they would survive, the captain (whoever he was) harmed everyone... if the officers took this captain in their shuttle they wouldn't need to disable the ship so the captain may still be in this ship. Why did the officers felt the need to do that to the captain and leave the rest of us? Who was this captain? What did he/she do?
The air feels better now, and the thrusters worked, but they don't repair themselves, do they?... there are other crew members working like me to get the other systems back up...
Stinger can't remember the crew on the ship, nor why is he in it... So he searches the captain's name and heritage in the logs so he can recognise him (or her) if he sees him, and what did he/she do.
He makes his way to the Bridge.
Rolls
(If needed) Send message - (2d6)
(54) = 9
Console
What? Everybody will come here?
As fast as he can, he locks the pilot controls, turns off the nav monitor, makes sure he got his armshild and pistol at ready, and adjusts his pilot badge at his shoulder.
Then he goes to the bridge's door to ensure it is working properly, and the crew can enter without problem.
Sam starts slowly pushing power back to key areas of the ship. First checking life-support sighs with relief as the system registers and increase in use back to normal levels. Sam then moves onto other systems, starting with shields, sensors, propulsion, but leaves internal basic infrastructure (lights, plumbing, wall outlets, etc) and sensors as well as ship external weapons offline for now. Just to be safe.
Your internal hard drive contents seem to be slightly garbled, but less so than your memories.
Unfortunately day to day minutia are not recorded at all times so you don't get it all but you do gain a few key pieces.
@Viking1031 Updates entered : If you want more details list questions and/or topics you are looking for information on and add a Test to scan your database to try and make sense of it and specific entries
Internal records
Ship detail inserted before departure
engineering maintenance logs - these indicate a rise in ship issues beginning about 1 month ago.
major repairs from a battle 2 weeks ago
Investigation into errors indicates some sort of biomechanical infection in the ship that affects electronics? Mechanical system's have not been affected
Looks like a virus engineered or real began to hamper ship functions. I locked myself in here for a reason and disabled the powerplant from the rest of the ship. Time to do some more troubleshooting. Do not want to cause anymore damage.
Ok, lets organize the issues:
Check for virus or viruses still present in system and remove them.
Pull up maintenance logs to find errors that begin to appear to find source of problems.
Check status of battle repairs and systems effected by it.
What was added right before we left?
With her priorities straight, she sits at a console and begins running diagnostics to find answers so she can set about finding a solution and fixing what ails the ship.
Rolls
run a diagnostic check to look for a virus - (2d6)
(61) = 7
maintenance logs - (2d6)
(43) = 7
battle damage system issues - (2d6)
(21) = 3
Find data added before departure - (2d6)
(61) = 7
drive backup for logs - (1d6)
(6) = 6
Sam starts a basic systems EWIP (electronic warfare & infiltration prevention) check and instantly finds signs of trojan programs in most of the engineering system. The disturbing thing is that the system only found them because they had been identified previously but not removed. Probing further she identifies that the programs have 2 triggers. The first is an electronic trigger, likely prevented due to the severed network. The second is triggered by a failure to remove the virus. If any of the infected systems are not properly cleaned it will instantly trigger the other systems. Glancing around the room and the disconnected systems Sam gets the idea that she was clearing each system independently. This would greatly reduce the risk of a shipwide cascading failure of all systems. Unfortunately she seems to have been knocked out before she could finish purging engineering.
Looking back over the local logs, and referencing her own internal records Sam realizes this is no random trojan. It was designed with intimate knowledge of the ships systems and controls. If the EWIP systems had not already isolated portions of the infection she is not sure how long it would have taken. Luckily the systems hard coded original templates are still clean. All she will need to do it transfer the updated EWIP database to a single clean system then use that to start restoring the others. Not too hard, but time consuming. The odd thing is that according to the EWIP logs these trojans were inserted after some of the initial system errors. Something else is or was at work. But first things first.
Creating a stand alone EWIP terminal she quickly restores it from the original then updates it. Using this Sam starts cleaning the engineering systems. Isolate, wash, restore, rinse, repeat. Only connecting systems back together once she is sure they are clean.
While the system is doing its thing she has short breathers between bouts of disconnecting and reconnecting cables. Sam takes this time to review what she can of the logs. For some reason an earlier virus, a much cruder version, focused on changing or erasing log entries date fields and indexing while leaving the content alone. She suspects it sent a key to whomever created it so that they could still look over the logs while preventing others from doing the same. However she is able to locate one that seems recent.
Summary:Last Stand
This may be my final log. The mutineers have taken control of most of the ship. We've managed to lock down engineering and life support, but they are attempting to breach. We’ve set up a makeshift defense but supplies are running low. If anyone finds this, know that we fought to the end.
Adonis makes his way to the bridge, not bothered by the low level lighting and upon reaching the door to the bridge spots the doctor looking at it in annoyance.
Once done with her work she checks to make sure her shock pistol is on stun before heading carefully to the bridge.
Rolls
Roll 1 - (2d6)
(63) = 9
roll 2 - (2d6)
(44) = 8
Role | Name | - | Role | Name |
Captain | Jaxon Thrace | 1st Officer | Elara Vraspe | |
Comms | Adonis (ADS-4) | Engineer | Samantha Delecort | |
Tactical | xxx | Quartermaster | Sera Qan | |
Pilot | Formigum Whiteblade | Medical | Alandra Mournbeard | |
Navigation | Lira Korr | Security | Trent Harker | |
Science | Valen Drex | Systems | Jana Mirov | |
Ordinance | Orion Pax | Technician | Mika Thorn |
I did not do details for the PC for now but will add some in a bit based on character creation posts.
Rolls
Unlocking the door - (2d6)
(25) = 7
"No guarantee that engineering isn't quarantined as well.", she mutters. Looking at her shock staff she grasps it.
Then she starts to beat out a message in what she hopes is Morse code on the bridge door.
She taps, DOCTOR, HERE TO HELP or at least she thinks she does.
Rolls
Attempting Morse code - (1d6)
(4) = 4
Blackness in the middle of stillness is interrupted by a flash of consciousness. Unfortunately consciousness to not ensure enlightenment and chaos if what surges to the surface as you struggle to get a grip on your situation.
Avro comes online and forms from your core. Looking around you are in a small room, probably a closet from the looks of it, and your form glitches as waves of unaligned data is flushed from your core. You have no memory of this room and have no idea how you got here. Thinking back the last clear data point is spotting a ship that looked perfect for your next jaunt. You slipped onboard and then . . . . it all goes fuzzy.
The lights are dim and a quick check reveals the computer will not respond to your voice commands. Moving to the door you are forced to find a manual release to force it open. Outside is what looks to be a bedroom. There is a large pod to one side of the room, bracketed by a couple small dressers or cabinets, as well as two other doors.
Keep your posts in Notes to me until Avro encounters another character
@Turanel2 : Welcome to the story.
Keep your posts in Notes to me until Avro encounters another character
I will put DM questions/comments/instructions for characters in purple
Character communication is in bold
Character thought is in italics
Use colors for additional emphasis, like on a characters name
Avro turns their attention to the large pod and looks though the viewing port...
Rolls
Roll Eidetic Memory to recognize the room and contents of the pod - (2d6)
(23) = 5
Date&Time(Odyssey): 16:30 @ 2236-10-03
You are missing more than a month of time from all memory. As you try to recall things you get flashes that shift and are accompanies by an intense level of pain forcing you to cease your recollections, for now.
Looking down into the pod, an advanced medical pod that looks to have independent systems for life support, cryostasis, and even auto doctor features included. Inside you see a man.
According to the pods reading he is in cryostasis and suffering from an infection of some kind.
Rolls
bypassing any locked spaces - (2D6)
(53) = 8
notice any hidden compartments - (2d6)
(23) = 5
Rolls
attempt to hot wire the door override - (2D6)
(44) = 8
Rolls
access ship layout schematics - (2D6)
(15) = 6
Rolls
if needed: activate ship wide broadcast via Coms panel. - (2D6)
(51) = 6
Rolls
override the system between S.O.S. - (2D6)
(64) = 10