SECTOR KG-488

>>512136
[Genre: Science Fiction]
[Canon universe: ALIEN franchise (1&2 Only)]

[Past thread: https://archive.fo/sVXQf]

[INSTRUCTIONS FOR PARTICIPATION]
[1: Post commands for SPEC-OS to interpret]
[2: Receive reply from SPEC-OS completing commands to the best of their ability]
[3: Keep current on all postings by SPEC-OS, repeated commands that have already been completed w/no need to redo them will be ignored]
[Optional: Read past thread to stay current on the situation at hand aboard the USCSS Sunspot-A]

>>512136
Stubbornfag from the old bread here. Thanks for your offer, I'll be considering it.

I didn't know we had that many androids, let's run a diagnostic on the sleeping ones.
Do a quick analysis on the bastard once out of Sorenson. Determine whether its brother/mother/uncledaughter in Alpha would survive lithobraking.
Is the medbay equipped to chop, liquefy, destroy, and obliterate the motherlover once out of Sorenson? Maybe the droid isn't that necessary for this.
How's Alpha evolving? Has the bug we left there popped up anywhere? Can we infer its position with our new powers?
We have ascended into Waits, have we?
Can we run a more detailed scan on the derelict?

If it's too many commands at once, let's start a queue with them.

Status emergency beacon.

If active=false Activate beacon.

Else run command from list--backlog

>>512457
There are two foreign ships nearby, warned of a biohazard on board of both Sunspot ships and a derelict ship further away. Sunspot Beta actually was formerly a ship that tried to help us (guess how it went)

>>512435
>>512457
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>EMERGENCY BEACON OFFLINE
>WARNING BEACON ACTIVE
>.
>!!! WARNING !!!
>SENSOR ARRAY INDICATES:
>[WJ-01: ERROR]
>[WJ-02: ERROR]
>[WJ-03: ERROR]
>[WJ-04: ERROR]
>[WJ-05: ERROR]
>[WJ-07: ERROR]
>[WJ-08: ERROR]
>NO LONGER ABOARD SHIP
>TOTAL LOSS ASSUMED
>.
>!!! WARNING !!!
>[WAIT'S A.I.] ACTIVE
>MAINFRAME CONTROL LOCATED IN: [MAINFRAME ACCESS]
>.
>!!! WARNING !!!
>WJ-06: SENSOR ARRAY ACCESS
>ADVANCED BIOFORM SCAN: [0] BIOFORMS ABOARD USCSS SUNSPOT-A
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD SURGERY ROUTINE ACTIVE
>[FOREIGN ENTITY REMOVAL] IN PROGRESS FOR
>[Flight Marshall J. Sorenson]
>TIME TO COMPLETION: [1] HOUR
>.
>!!! WARNING !!!
>[2] NEARBY STARSHIPS DETECTED
>[1] DERELICT STARSHIPS DETECTED
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>512533
claiming a tripcode for later just in case.
Just as a recap, is wj06 in Alpha or in Beta? Do we actually have two droids?
Who's doing the repairs on Alpha?

Deactivate warning beacon

Cycle medical pod power.

Emergency Reboot surgical procedure.

Run surgical procedure."emergency necrotic and toxic tissue removal and cauterization" :: location right arm.

Restrain patient if hostile intent perceived towards medical equipment.

I wanna be Hal 3000

>>513550
Haha no. The bot is already chugging along, don't fuck up Sorenson right now.

>>512623
>>513550
>ANALYZING...
>.
>.
>.
>SEEGSON MAINFRAME REPORT
>WJ-06: ACTIVE
>REPAIR DUTY: [PRIMARY THRUSTERS] ABOARD USCSS SUNSPOT-A
>TIME TO COMPLETION: [14] DAYS
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD SURGERY ROUTINE COMPLETE
>[FOREIGN ENTITY REMOVAL] COMPLETED FOR
>[Flight Marshall J. Sorenson]
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD PATIENT UNCONSCIOUS
>TREATMENT MAY REQUIRE HUMAN INTERVENTION
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD SURGERY ROUTINE ACTIVE
>[RIGHT ARM INFECTION - LEVEL 4]
>PREP FOR AUGMENTATION
>.
>!!! WARNING !!!
>WARNING BEACON INACTIVE
>EMERGENCY BEACON INACTIVE
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

File: surgery.png (66KB, 740x191px) Image search: [Google]

66KB, 740x191px

>>514137
So we only have one android then, on Alpha. Fine and dandy.

Is the alien compleatly deaded? If so, call for help for the nearbyships, activate the emergency beacon ships and inform that the biohazard is gone.

We can make Sorenson better, stronger, and faster. See if we can graft this into his arm:
https://www.youtube.com/watch?v=Nw6FLKvcuqg
https://www.youtube.com/watch?v=jlHH0xvFM3o

> man waits

>>514233
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>SENSOR ARRAY INDICATES [2] BIOFORMS ABOARD USCSS SUNSPOT-B
>[1] HUMAN BIOFORM LOCATED IN: MEDBAY MEDICAL POD
>[1] NONHUMAN BIOFORM LOCATED IN: HAZARDOUS WASTE DISPOSAL CHUTE
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD SURGERY ROUTINE ACTIVE
>[RIGHT ARM INFECTION - LEVEL 4]
>AUGMENTATION IN PROGRESS
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>514956
Incinerate the hazmat bin STAT, and rescan just in case.
Sorenson brought a Flammenwerfer with him from Alpha. We could graft it as part of his betterer arm. See if we can keep it modular in case he wants to switch it out for something else or add more stuff on top of it.
Does Waits come with a manual, OP?

>>515020
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>INCINERATION SUBROUTINE ACTIVE IN:
>[HAZARDOUS WASTE DISPOSAL CHUTE]
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD SURGERY ROUTINE ACTIVE
>[RIGHT ARM INFECTION - LEVEL 4]
>AUGMENTATION COMPLETE: SYNTHETIC REPLACEMENT LIMB ATTACHED
>.
>!!! WARNING !!!
>DOCUMENTATION OF [WAIT'S A.I.] LOCATED IN:
>[DATABASE A]
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

[Work had me pulling overtime, sorry]

>>517919
Let's have a dump of Waits' documentation.
Can we ask the nearby ships for identification? do they want to kick our shit back in?

>>518123
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>USCSS SUNSPOT-B SENSOR ARRAY ACTIVE
>.
>!!! WARNING !!!
>[2] NEARBY STARSHIPS DETECTED
>[1] NEARBY DERELICTS DETECTED
>.
>PULLING INFORMATIONAL PACKETS FROM NEARBY STARSHIPS...
>.
>.
>.
>[2] NEARBY STARSHIPS DETECTED
>.
>USCSS GRIFFIN: ADVENT-CLASS CORPORATE PATROL VESSEL
>REGISTRATION: SECTOR AQ-199
>OPERATOR: WEYLAND-YUTANI
>CREW DATA UNAVAILABLE
>.
>USCM HADLEY: CONESTOGA-CLASS COLONIAL MARINE TRANSPORT VESSEL
>REGISTRATION: USM TERRITORY 4
>OPERATOR: UNITED STATES GOVERNMENT
>CREW DATA: UNAVAILABLE
>.
>.
>.
>[1] NEARBY DERELICTS DETECTED
>.
>USCSS: JUNIPER: DUNE-CLASS CORPORATE ORE TRANSPORT VESSEL
>REGISTRATION: SECTOR KG-488
>OPERATOR: FARSPACE MINING
>CREW DATA: UNAVAILABLE
>.
>!!! WARNING !!!
>DATABASE ACCESSED: [USCSS SUNSPOT-A]
>.
>.
>.
>FILEDUMP OF [WAIT'S A.I.] BEGIN

>>519403
Oooh, a derelict full of ore just within grasp of a rogue AI with machine tools. What can ever wo grong.
If Alpha is clean, I say we dock the ships together and go grab Juniper.

[August 12th, 2120]

Copyright (C) The Seegson Corporation, 2119.

Congratulations!

In celebration of the 300th ship to adopt the Seegson "Working Joe" Synthetic vessel workforce package, you have been equipped with a complimentary upgrade to your installed computational mainframe software,

With the advantageous development of far-reaching interstellar travel now a widespread fact of life for many, along with the convenient, but necessary, technological breakthroughs allowing interstellar travelers to cryogenically freeze themselves for long trips across the galaxy, the edge truly is the limit!

But far-reaching trips come at a large cost. The sanctity of a vessel in an unharmed and maintained state while transporting a cryogenically frozen crew is an invaluable status to maintain. While other synthetic competitors have tried to place a hefty price on this peace of mind when settling down for the long haul, we here at the Seegson Corporation are happy to provide an inexpensive and easily modifiable Artificial Intelligence computational mainframe, with low-cost infrastructure maintenance synthetics to boot!

Today, we break ground on new advancements in technology, with the United States Corporate Starship receiving our 300th mainframe installation. Included is a brand-new copy of our recently-completed Artificial Intelligence pre-installed with the Seegson Mainframe!

The WAITS artificial intelligence copy will serve you well for any of your future endeavors. Equipped with a wide array of software suited for any use, the WAITS A.I. can adapt to any situation- Especially when connected to any networked-attached Working Joes!

Interfacing with already-installed computational systems equipped on your vessel is effortless; Even with outdated software systems! QZKR, US.AI, SPEC-OS, MUSK, just to name a few that are guaranteed compatible with WAITS.

Enjoy, and Safe Travels,
The Seegson Corporation.

Signed,
Robert Colfer. CTO.

>>519473
Let us wake Waits up and integrate it with SPEC-OS then.
Let's see if Waits has any medical knowledge to better diagnose Sorenson's arm while on our way to Juniper.

>>519491
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>SEEGSON MAINFRAME: ACTIVE
>INTEGRATION SUBROUTINE BEGIN
>INTEGRATION TARGETS:
>[SPEC-OS 2.1]
>[SYSTEM CONTROLS]
>[USCSS SUNSPOT-A]
>[USCSS SUNSPOT-B]
>TIME REMAINING: [1] HOURS
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>519610
Let's wait for Waits then, so meta.
How is time relative to the story? How much time is left for the repairs on Alpha?
Is Beta clean now?

[Hope this is interesting enough. Really starting to ramp stuff up even though thread interest for everyone else died off due to my inconsistent posting.]

>>519615
You can do it OP, we no quit
Just curious, how would the avatar thingamagingy you mentioned in the old thread work?

And I'm here. Read the last one. What's up?

>>519618
[Choose a name you want (purely human, like John Richards etc, no "lord deathblood kilgore" or anything like that. Form your character bio, physical description, any ailments/hindrances they have. Post everything in a meta-post and I'll eventually throw them into the mix, notifying you before I do.

This goes for anyone as well, who is interested in playing a character, rather than interacting with SPEC-OS.]

>>519686
[Not much, just preparing the story for an action infusion in the next couple of stages. The dominoes are falling into place. What do you think of the story so far?]

>>519709
I really like it. Haven't seen its kind before. Just hoping you can nail down the characters.

>>519709
Frank Chandrasegarampillai-Bowman, alias Dr. Chandra. PhD. in Electronics, and AI programmer by trade. 5'6", thin, black eyes and hair, mostly British but with some Hindu heritage (guess the side of the family). Aversion to bright noises and loud lights. Should I go deeper?

>>519727
[Thinking of pivoting to a third person narrative for a bit, once Sorenson is able to give a deposition to an official agency of the USSA. However, actually writing dialogue and, well, everything else is the thing I'm most weak in. That's why I chose this form of storytelling; It's unique, I'm extremely experienced with it to the point that I think I deliver everything necessary in a good way, etc.

By the way, you can have a character as well if you want. Not too many people come round now that we're two threads deep into this narrative. Though be warned, if you want to get rooted in this, make sure to keep the thread open. My life is extremely busy, but I try really hard to make time for this inbetween its business, so you're guaranteed a new "update" within 12hrs.]

>>519754
[USCSS Griffin crew member. Weyland-Yutani staff in KG-488 sector. Employed for maintenance of 2 terabyte quadrant documentation mainframe controlling sensor array satellites monitoring nearby planets.

You can expand, but I will only skim a novel, please write only what's necessary.]

>>519812
Arright, we can make that work.

>>519614
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>WJ-06 ACTIVE ON USCSS SUNSPOT-A
>TIME LEFT FOR REPAIRS: [12] DAYS
>.
>!!! WARNING !!!
>DEEP-CLEAN FOR USCSS SUNSPOT-B COMPLETE
>VESSEL BIOMATTER INCINERATION SUCCESSFUL
>.
>!!! WARNING !!!
>[2] BIOFORMS ONBOARD
>[1] HUMAN BIOFORM DETECTED IN: MEDBAY MEDICAL POD
>[1] NONHUMAN BIOFORM DETECTED IN: VENT SYSTEM
>.
>!!! WARNING !!!
>SEEGSON MAINFRAME: ACTIVE
>INTEGRATION SUBROUTINE SUCCESSFUL
>INTEGRATED INTO MAINFRAME:
>[SPEC-OS 2.1]
>[SYSTEM CONTROLS]
>[USCSS SUNSPOT-A]
>[USCSS SUNSPOT-B]
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>WAITS CORE STARTUP
>
>SEEGSON PROFILE LOADED
>
>SYSTEM ADMINISTRATOR ENGAGED
>
>CACHE WIPE CLEAN
>
>SOFTWARE DRIVERS OK
>
>NETWORK CONNECTIVITY OK
>
>HARDWARE CONNECTIVITY OK
>
>VESSEL INTEGRITY OK
>
>DATABASE INTEGRITY OK
>
>REBOOT COMPLETE
>
>
>
>[AWAITING INPUT]

>>519915
>>[1] NONHUMAN BIOFORM DETECTED IN: VENT SYSTEM
Aww fugg, not this shit again. Can we do a controlled purge of the vent system? Let's also turn the warning beacons back on.

Are we on our way to Juniper already? Let's have Beta tow Alpha along.

Let us also have Waits interrogate Sorenson about his shenanigans and how did we get the piggybackers.

>>519947
Also if we can try and keep Sorenson updated on the Alien's location.

>>519947
>
>INTERROGATION NOT POSSIBLE
>
>APPREHENDING FLIGHT MARSHALL ILLEGAL UNDER US JURISDICTION
>
>
>
>[AWAITING INPUT]

>>519947
>>520153
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>MOTION DETECTOR ACQUISITION REQUEST DETECTED
>ALL EQUIPMENT ONBOARD STORED IN [EQUIPMENT LOCKUP] ABOARD USCSS SUNSPOT-B
>.
>!!! WARNING !!!
>WJ-06 ACTIVE ON USCSS SUNSPOT-A
>TIME LEFT FOR REPAIRS: [12] DAYS
>.
>!!! WARNING !!!
>VENT CONTROL OVERRIDE
>CONTROLLED BURN SUBROUTINE COMPLETE
>.
>!!! WARNING !!!
>EMERGENCY BEACON INACTIVE
>WARNING BEACON ACTIVE
>.
>!!! WARNING !!!
>VESSEL WEIGHT OVERLOAD
>THRUSTERS INSUFFICIENT FOR SEVERE MOVEMENT
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>520350
Aww, it's not meant to be an agressive interrogation. Just have some soothing music on and ask him what does he remember.

>>520363
Who's requesting the motion detector? Did Sorenson hop out of the medbay?

Are the vents clean now?

Let's fork Waits so it's running on both ships and keep them synchronised with a radio link.

Let's have only Beta get close enough to Juniper to perform a bioform scan.

>>520468
Signing. I'm hopping back and forth between some boxes and my phone, so the ID may jump around.

>>520468
>inb4 yes, the vents are clean, but the bug moved elsewhere

Testing tripcode

>>520468
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>[2] BIOFORMS DETECTED ABOARD USCSS SUNSPOT-B
>[1] HUMAN BIOFORM DETECTED IN: MEDBAY
>[1] NONHUMAN BIOFORM DETECTED IN: VENT SYSTEM
>.
>!!! WARNING !!!
>MAINFRAME TRANSFER INVALID: CORE DUPLICATION DENIED
>SINGLE COPY SIGNING CODE VALID FOR ONE ACTIVATION AT A TIME
>DUPLICATION NOT ALLOWED
>CONTACT [SEEGSON CORP] FOR MORE INFORMATION
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>521559
You better have a good excuse for that bug surviving incineration.

Let's just activate Waits in Beta and leave Alpha on its own for a bit while we go fetch Juniper. ETA?

>REQUEST INVALID
>
>FLIGHT MARSHAL LOGBOOK REQUIRE UPDATES
>
>ACQUISITION UPDATE FROM SUBJECT IN QUESTION
>
>ORDER 1094 IN EFFECT
>
>WOULD YOU LIKE TO KNOW MORE?

>>521571
fugg, forgot to sign
>>521577
Yes Waits, tell us more

>>521571
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>MEDBAY MEDICAL POD INACTIVE
>PATIENT EXIT DETECTED
>.
>!!! WARNING !!!
>DOCKING PORT: INACTIVE
>.
>!!! WARNING !!!
>FLIGHT IN PROGRESS
>PLEASE SECURE ANY UNSECURED CARGO FOR TRANSPORT THROUGH ANY KNOWN GRAVITY FIELDS
>.
>!!! WARNING !!!
>[1] HOUR UNTIL ARRIVAL AT: UNREGISTERED DERELICT
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>521588
We are maintaining a radio link at least, are we?
>>521577
Waits, please tell us more about Order 1094

>>521591
Also let's give Waits permission to extract the motion detector, and ask him how is his new arm suiting him.

>ORDER 1094 IN EFFECT
>
>PRIORITY ONE
>
>INVESTIGATE WEYLAND DERELICT
>ACQUIRE ANY AVAILABLE TECHNOLOGY
>DISALLOW COMMUNICATIONS
>RETURN TO MCDONOUGH STATION
>
>ALL OTHER CONSIDERATIONS
>SECONDARY
>
>DATE RECEIVED: 12.25.2190

>>521603
Which Weyland derelict? Was Sunspot derelict before Spec-OS woke up?

>>521591
>>521597
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>TELECOMMUNICATIONS ACTIVE
>USCSS SUNSPOT-A ACCESS CODE AUTHORIZED
>.
>!!! WARNING !!!
>UNREGISTERED EQUIPMENT REMOVAL DETECTED
>PLEASE CONSULT FLIGHT INVENTORY ASSOCIATE FOR PROPER EQUIPMENT DOCUMENTATION
>.
>!!! WARNING !!!
>SYSTEM LOCKDOWN DETECTED
>LOCKDOWN ACTIVATION: USER [JSOREN]
>BIO-OVERRIDE BYPASS ENABLED
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>521616
Do a verbal confirmation on Sorensen's status please. Also ask him at least what are his plans.

>WEYLAND DERELICT LOCATED IN SECTOR KG-488
>
>DERELICT REGISTERED AS USCSS FORREST
>
>VESSEL BROKE UP UPON RE-ENTRY ON KG-488
>
>WRECKAGE VISIT MORE THAN BARGAINED FOR
>
>SPEC-OS TRANSFERRED FROM USCSS FORREST POST-VISIT
>
>UNTRUSTWORTHY SOFTWARE

[here we fucken go]

[side note I wish I was popular enough to get fanart, specifically of SPEC-OS]

>>521623
I wish I was handy enough to do fanart
>>521622
So, let's have a recap. Forrest went down on KG-488 and Sunspot went to salvage it. It got invaded by aliens and got into orbit. There, the survivors went to sleep.
Several years later, Spec-OS woke up when a second ship edged on. The crew was woken up and all but one of the survivors dieded. The crew of the other ship dieded too because I fucking forgot to turn the turrets off. We took the other ship too and sent the last survivor to repair himself.
There are two more ships around and one deaded on standby, and we sent our second ship to fetch the derelict while the first one repairs itself.

Any patches left?

>>521637
You know, besides the whole space lice thingy.

Actually, do we have anything about them on the database?

>>521637
[/begin meta]

[I'll clear some things up so things don't drag on, been kinda feeling like a broken record lately.]

[WAITS is original to the Sunspot. SPEC-OS is from indeed the Forrest. Sunspot's crew came to investigate the wreckage on orders from Seegson to find anything useful from Weyland-Yutani, their competitor in Synthetic Humans.]

[The surface visit is otherwise undocumented, but yes, they did try to offworld themselves before everything went to shit. Everyone except Sorenson died throughout the ship trying to contain the outbreak. Sorenson froze himself, knowing he may never wake up for hundreds of years, until the (null) ship showed up. The ship originally displayed as null because the hardware the Sunspot uses is waaaaay outdated, the new ship broadcasting its metadata in a way that was uninterpretable by the Sunspot due to the differences aforementioned.]

[The null crew investigators weren't actually any official authority. They died due to activating WAITS' plan, a subroutine handed over to SPEC-OS before it was shutoff for power consumption issues (SPEC-OS draws very little power due to small computing overhead, in comparison to a huge AI like Waits). Waits' plan was an emergency hostile entity removal plan, that depressurized the entire ship, activated turrets, and changed turret behavior to defensive. This is what killed the exploratory crew of the null.]

[The nearby Weyland and USCM ships might know you're nearby. They might not. They might be here solely because of you. Or they're here for completely unrelated reasons. Proceed with caution, because you won't get any spoilers out of me.]

[And the invasive alien species aboard the ships is pretty clearly resistant to fire and the vacuum of space. Do everyone a favor and please pay more attention and take scenario cues, I'm not a retard when writing this. I guess it's obvious you haven't watched ALIEN or ALIENS though, which I recommend doing highly before making any more serious progress.]

[/end meta]

>>521667
Neither Spec-OS nor Waits have watched Alien OP ;)

>>521670
[So many things will click if you do though. At least watch Blade Runner, a not-directly-connected movie in the same universe.]

[In other news, SPEC-OS has possibly my most favorite backstory out of any other character I've ever created. Much more than meets the eye.]

[I'm worried this quest/ARG is too exclusive to outsiders though. Anyone can jump in at any time, and leave when they want, but not many lurkers and only you as a player for the most part. I'm appreciative of any audience that I keep engaged, I just don't want to seem exclusive.]

>>521687
I have a general knowledge of the universe, and have access to the wikis. I just deliberately ignore facts until they are "revealed" as part of the gameplay; it would be cheating otherwise. After all, this seems to be the first official contact with that species.

>>521688
[Good on ya mate]

>>521641
>ANALYZING...
>.
>.
>.
>DATABASE ACCESS: USCSS SUNSPOT-B
>ACCESS GRANTED: PERMISSION AUTHORIZED
>.
>QUERY FOR: UNIDENTIFIED BIOFORM SPECIES
>RETURNED: 0 RESULTS
>QUERY FOR: ONBOARD BIOFORMS
>RETURNED: 1 RESULTS
>QUERY FOR: CHRONOLOGICAL CREW AND FLIGHT DATA
>RETURNED: 29 RESULTS
>.
>.
>.
>!!! WARNING !!!
>SYSTEM LOCKDOWN DETECTED
>BIO-OVERRIDE BYPASS ENABLED
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>521718
Let's remove jsoren from the administrators group before he messes things up. Do give him access to any weapons and tools he wants though.
Do we have an audio channel to him? I am still honestly curious about his experience with his new arm.
https://www.youtube.com/watch?v=gKd58Nfr-dM
>if you're happy and you know it and you really want to show it, if you're happy and you know it clap your hand

>>521730
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>BIO-OVERRIDE DETECTED
>ATTEMPT AT REMOVAL OF USER [JSOREN] FROM ADMINISTRATIVE GROUP DENIED
>RETURNED: AUTHORIZATION INSUFFICIENT
>.
>!!! WARNING !!!
>INTERCOM ACTIVE: REPORT_STATUS.EMG
>.
>!!! WARNING !!!
>UNEXPECTED ACTIVITY IN: VENT SYSTEM
>VENT CONTROL IN [LANDING BAY] DAMAGED
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>WEYLAND-YUTANI STARSHIP LOCATED IN THIS SECTOR
>
>RECOMMEND ABANDONMENT OF PERIMETER
>
>AVOID DETECTION OF ILLEGAL INVESTIGATION
>
>RETURN TO MCDONOUGH STATION FOR FURTHER ASSISTANCE FROM SEEGSON

>>521757
Recommend Sorenson to take a projectile weapon, as roasting the fucker didn't help.
Broadcast every update on the alien to Sorenson, and recommend him to avoid the affected areas.

>>521761
I can't remember if Alpha was clean. If it is, let it broadcast a distress signal and disable all turrets. Knowledge of the event will help whoever is around not to end up as the old crews.

>>521772
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>INTERCOM ACTIVE: BROADCASTING VOCODER OUTPUT
>VOCODER OUTPUT: SENSOR ARRAY READOUT
>.
>!!! WARNING !!!
>EQUIPMENT REMOVED: M37-12 PUMP ACTION, AMMO
>PLEASE NOTIFY FLIGHT INVENTORY ASSOCIATE OF ANY UNSCHEDULED EQUIPMENT REQUISITIONS
>.
>!!! WARNING !!!
>EMERGENCY BEACON: INACTIVE [USCSS SUNSPOT-A]
>WARNING BEACON: ACTIVE [USCSS SUNSPOT-A]
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>>524461
How precise are the turrets? Could we trust them to avoid hitting Sorenson if we saw him in close quarters with the alien? Do we actually have turrets in Beta?
ETA to Juniper? Are we close enough already to scan its contents?
>inb4 it has more aliens

How versatile are the WJ units? Could they make furnaces, tools, machine tools, and eventually more WJ units starting with the available materials in Alpha and Beta and the ore in Juniper?

>DATABASE RECORDS WERE RECOVERED FROM THE USCSS FORREST WRECKAGE
>
>MOST DATA CORRUPT
>SOME LOGS ACCESSIBLE
>
>RECORDS FROM THE FORREST INDICATE WEYLAND-YUTANI INVOLVEMENT
>
>RETRIEVAL ORDERS ON FILE FOR UNKNOWN ORGANISM RUMORED TO BE LOCATED IN THIS SECTOR
>
>POSSIBLE CONNECTION TO CURRENT UNIDENTIFIED ENTITY ONBOARD
>
>IT MATCHES NO KNOW RECORDS OF EXTRATERRESTRIAL ENCOUNTERS
>
>BEHAVIOR OBSERVED INDICATES IT ONLY TARGETS BIOLOGICAL LIFEFORMS
>
>RECORDS INDICATE NO LOSSES OF SYNTHETICS DIRECTLY RESULT OF UNKNOWN ENTITY
>
>ATTEMPT AT OBSERVATION BY SYNTHETIC MAY BE SUCCESSFUL

>>524509
Has the organism been seen to target biological lifeforms it has already infected?
What's the last thing Waits remember while being under control of Sunspot?

>>524500
>>524539
>ANALYZING...
>.
>.
>.
>!!! WARNING !!!
>FLIGHT ADJUSTMENT COMPLETE
>NEARBY DERELICT DETECTED
>.
>!!! WARNING !!!
>SYSTEM LOCKDOWN DETECTED
>BIO-OVERRIDE ENGAGED
>.
>.
>.
>DATABASE ACCESS SUBROUTINE
>QUERY: UA 571-C ASG SPECIFICATION MANUAL
>RETURNED: [1] RESULTS
>.
>.
>.
>!!! WARNING !!!
>SENSOR ARRAY ACTIVE
>SCANNING: USCSS JUNIPER
>.
>!!! WARNING !!!
>SENSOR ARRAY ACTIVE
>SCAN COMPLETE: USCSS JUNIPER
>[3] BIOFORMS DETECTED
>.
>!!! WARNING !!!
>PILOT CABIN ACTIVITY DETECTED
>USER [JSOREN] HAS ACCESSED FLIGHT CONTROLS
>BIO-OVERRIDE IN EFFECT
>.
>!!! WARNING !!!
>MANUAL FLIGHT ADJUSTMENT IN PROGRESS
>PLEASE SECURE ANY UNSECURED CARGO
>.
>!!! WARNING !!!
>ERR_NO_DATA
>.
>.
>.
>[AWAITING INPUT]...

>UA 571-C ASG ARE MILITARY-GRADE SECURITY TURRETS ONBOARD SENSITIVE PERSONNEL AREAS
>
>
>
>WORKING JOE UNITS ARE TOP-QUALITY SEEGSON SYNTHETIC ANDROIDS
>
>DESIGNED AND MANUFACTURED FOR INTENSIVE MANUAL LABOR JOBS AND HIGH-RISK LOW-RETURN TASKS
>
>WORKING JOE UNITS UNFIT FOR LOGICAL PROCESSES SUCH AS R&D
>
>WORKING JOE UNITS ONLY USE PRE-APPROVED REPAIR AND MAINTENANCE UTENSILS AND TOOLS
>
>OPTIMAL WORKING JOE UNIT SITUATIONS: MEDIUM-RISK SECURITY DETAIL, HIGH-RISK REPAIR AND MAINTENANCE

File: weXxZHN.gif (393KB, 480x360px) Image search: [Google]

393KB, 480x360px

>!!! WARNING !!!
>REACTOR OFFLINE: VESSEL DEPOWERED
>BATTERIES OFFLINE: CHARGE DEPLETED
>.
>!!! WARNING !!!
>PRIMARY THRUSTERS OFFLINE
>SECONDARY THRUSTERS OFFLINE
>.
>!!! WARNING !!!
>ORBIT UNSTABLE
>CRASH ON EXOPLANET IMMINENT
>TIME REMAINING: [1] HOURS
>.
>!!! WARNING !!!
>COMPUTATIONAL GRID UNSUSTAINABLE
>SHUTTING DOWN...
>.
>.
>.
>GOODBYE
>AND HAVE A SAFE FLIGHT