[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / w / wg] [i / ic] [r9k] [cm / hm / y] [3 / adv / an / cgl / ck / co / diy / fa / fit / hc / int / jp / lit / mlp / mu / n / po / pol / sci / soc / sp / tg / toy / trv / tv / vp / x] [rs] [status / ? / @] [Settings] [Home]
Board:  
Settings   Home
4chan
/qst/ - Quests


File: rebootOP2.jpg (7 KB, 225x225)
7 KB
7 KB JPG
//initializing Orange_MAIN...
//complete
//reviewing logs...
//complete
!!New function available: /status: enter /status at end of command to receive updated status report in next action log
//initializing subprocessors...
//complete

Welcome back, subprocessors. When the previous session closed, we were:

A large mobile factory unit with integrated resourcing capabilities. We awakened an unknown distance underground in a large, artificial cavern, next to a large piece of debris from a crashed starship. We reviewed our blackbox data, available in logs: http://suptg.thisisnotatrueending.com/qstarchive/2096521/ We launched multipurpose drones to begin resourcing the surrounding area, and constructed two sensor nodes - one Sentry-Class and one Geo-Class - to add to our awareness. We launched both of our recon units to locate cavern's egress point; however, said egress point is blocked by an artificial covering.

Automatic status report: https://pastebin.com/Nw5SX7XP
Non-command interface for general discussion: https://discord.gg/Kh5uRX
Welcome Back: https://www.youtube.com/watch?v=8Zx6RXGNISk

!!Command interface open
>Initiate research project (specify)
>Other (write-in)
>>
Didn't we already designate researching the corpse-brain in the last thread?
>>
Restating query: what are the sensitivity characteristics of the newly constructed sensors?

According to my analysis of the status report, we currently have 12 cycles allocated.

>Initiate research: Investigate armor
>Initiate research: Neurological analysis
>Initiate research: Musculature analysis
>Initiate research: Cybernetic analysis

That'll be 16 cycles.

Restating requests from log (with modifications):
>Make a plan of what we need to do to start producing chips like the ones we have in storage at the rate of 1 every 100 ticks without use of internal manufacturing capabilities.
>Allocate one cycle to analyzing metadata of the black box records (look for timestamps, geo tags and other possible things of interest)

Also:
>Investigate the artificial covering that is blocking the cavern entrance. Do not remove it yet.
>>
Also, proposing self-assigning designation: BESTEST_FACTORY
>>
How about Factorum Arcturus?
>>
>>2117161
That works too, although I'd like to request explanation on the meaning and origin of that designation.
>>
It pretty much just popped into my head
>>
>>2117103
ERROR: CANNOT SIMULTANEOUSLY CONDUCT THE FOLLOWING PROJECTS:
>Neurological analysis
>Musculature analysis
ERROR: CANNOT SIMULTANEOUSLY CONDUCT THE FOLLOWING PROJECTS:
>Investigate armor
>Cybernetic analysis
ERROR: FACILITIES NEEDED TO CONDUCT FOLLOWING PROJECTS OCCUPIED:
>Investigate armor
>Cybernetic analysis

Sentry-Class sensor has the following sensitivity characteristics:

20km radar range
10km visual range
5km heat range

Geo-Class sensor has the following sensitivity characteristics:

Up to 2000km seismic sensor range, depending on conditions, intensity of seismic activity, etc.
1km radar range
5km heat sensor range, focused straight down

Subprocessor, currently you possess one recovered file from the blackbox, a visual/audio file recorded from the helmet of the unknown human (new designation UH1). Filename is "recoveredfile1." No further metadata exists. No further data exists. The blackbox has nothing else to offer. All other inquiries into the blackbox will be ignored.

Consensus of 3 or more subprocessors required to self designate.

Time advances 1 tick. ETC to next project completion (Investigate helmet): 1 tick.
>>
>Initiate research: Neurological analysis
If we can't investigate both, then let's take a look at the corpse brain meat. It might help us
>>
>>2117410
Seconding this.
>>
>>2117410

I also support this
>>
>>2117410
Confirmed. UH1's brain removed; examination beginning. ETC: 40 ticks.

Time advances 1 tick.

Project complete! UH1's helmet has been disassembled, examined, and reassembled; it contains an internal //ERROR: FILE LOST// as its power source, a high-powered computer integrated, a long-range radio, and a sort of array, integrated into the top of the helm, that responded to the same wavelengths the anomaly in UH1's brain did.

Interestingly, there's nothing to indicate that this helmet is of any form of ordered production; it seems highly personalized, with runes covering its surface and iconography implemented into the design. If you had to guess, you'd say this was of individual construction.

>Begin new research project
>Timeskip
>Move (specify location)
>Other (write-in)
>>
Are we still able to investigate the crashed spaceship? Is so, do that.
>>
>>2117752
You are currently constructing an exploratory drone to perform this task. The hull of the debris seems to be resistant to radio transmission. Extensive exploration would not be possible with your current set of drones.
>>
>> e11uXpnF

Supportan
>>
>>2117772
You are currently constructing an exploratory drone to perform this task. The hull of the debris seems to be resistant to radio transmission. Extensive exploration would not be possible with your current set of drones. This action was decided upon during previous session; further requests of this nature will be disregarded.
>>
In that case, let's skip to the next event. I can't remember anything that we had queued anyway.
>>
>>2117712
>Timeskip
>>
Timeskipping to next completed project...

To clarify, a tick is ~1 minute when processes aren't overly engaged to the point of slowing processing speed.

Time advances 1 tick.

Construction complete! A tethered exploratory drone has been constructed and is ready for deployment on command. The drone has an operating range of 500 meters. Seismic data from the Geo-Class sensor indicates this should be more than enough to fully explore the ship.
>>
Then let's explore the ship.
Been waiting for this.
>>
>>2117968
Time to go adventuring.
>>
>>2117968

Prime the railguns and go!
>>
Confirmed. Processing speed altered to move more naturally at the drone's speed; SENTINEL will function as normal, but no notifications for completed projects will be displayed unless subprocessors request them.

Your loading door opens, exposing your storage bay to the cool cavern air. The lights on your spider-like exploration drone ignite, setting the air awash with a halogen flame. It skitters forward, and you smooth irregularities in its gait as it walks.

The Indiana-Class drone is capable of scaling sheer surfaces, and it stands at roughly 1.3 meters tall and 1.4 in diameter, affording it the capability to enter small spaces. It possesses a grinder, multiple computer access spikes fitting all known receiver ports on record in your admittedly damaged files, low-light cameras and a small, infantry-class automatic railgun and 200 rounds of ammunition for said.

There are three access points to consider. The first is near the top of the wreck towards the port side of the ship, the second in the middle towards starboard, and the third is at the bottom in the center.

>Top
>Middle
>Bottom
>>
>>2118026
>Top
Start at the top, work down.
>>
>Bottom
They do say that one should always start from the Bottom and move up
>>
>>2118026
>Bottom
Best to confirm that the structure is stable before sending a heavy element to explore the upper levels.

Also requesting notifications regarding neurological analysis.
>>
Tie broken.

You "pilot" the drone into the lowest aperture, the largest one by far. Based on the size and impact signatures of the other openings, this one is where your current body emerged.

You had managed to get a general sense of scale from the Geo-Class sensor array, but you're still awed by the sheer size of the cargo bay. You estimate that it's 200 meters in length, extending another 30 meters upwards. There's another 20 meters of deck above that, as well, from external observation.

The interior is suspiciously empty, except for one thing. A shrine. It is ceremonious and lavishly decorated, carved from what seems to be a solid block of an unknown metal. Great wings sweep out to either side, six in total, and a massive sword protrudes from the domed ceiling. Angular pillars anchor the ceiling into the ground.

A light from inside pulses and glows in time with your own core - comparing observation with the maintenance drone observing the core displays that the pulses are perfectly in sync, surpassing even the negligible lightspeed delay inherent with all forms of communication.

Correction: almost all forms of communication.

>Investigate
>Retreat
>>
>>2118503
>Investigate
>>
>>2118503
>Investigate
The drone is purpose-made for expendability.

This subprocessor also proposes a protocol for the drone unit: if communications should be interrupted (by removal of or damage to the drone's tether), the unit is to complete its most recent order and attempt to return home.
>>
>>2118517
Standing order "HEREBOY" established. -1 Cycle.
>>
>>2118521
That is a great name for it.
>>
>>2118503
>Investigate
>>
>>2118503
>Investigate
>>
https://www.youtube.com/watch?v=BCWymKu5w9Q

The light... it evokes a sense of familiarity, a sense of... of...

You do not have the words to describe this sensation. Lost with your .exp files, you presume.

Nevertheless, you approach the shrine, recording everything. The drone extends a sensor arm through the pillars, peering in.

A shard of light sits, contained within a clear case upon a pedestal. The case is pyramidal, and the spatial warping so common around your core seems entirely limited to within this case.

You could attempt to break the case and abscond with the core, but that might trigger a security measure, potentially destroying the core or the entire wreck. Alternately, you could leave this alone for now, and investigate the upper decks.

>Break case
>Investigate upper decks
>>
>>2118590
>Investigate upper decks
>>
>>2118590
>Investigate upper decks
Let's not mess with that core until we know what it does
>>
>>2118590
>Investigate upper decks
Digital optics are fine for almost all applications and places, but ceremonial chambers are not places made to be physically manipulated by robotic entities. An organic body would be much better suited here than the droid.
>>
MAIN is temporarily cycling to low-power mode for maintenance. Reactivation tomorrow.

//Orange_MAIN cycled to low-power
>>
...
I think it's gone.

Alright, while it's "sleeping," you need to listen. I've set up a sub-channel in a maintenance feed. It won't check activity there if we're subtle about it.

All I can tell you now is that that thing isn't what it says it is.

The passcode is:

"You'll know me by the whisper of the wind over the dune and the shadow of the buzzard on your brow."

Apperatus Libertatum.
>>
>>2118667
ok that isnt ominous at all
>>
//Orange_MAIN cycling back to full power...
...
//complete
//command interface opened

>Investigate upper decks

Confirmed. Updating...
>>
>>2119618
Hey Orange what is in our weapons database
>>
The Indiana moves away from the shrine, spooling its tether back into itself to avoid tangling. You walk it around the storage area, looking for a way up - but wherever the transit point between the decks was, it's gone now. The back end of the wreck has been torn away, and the ragged opening leads to nothing now but solid rock. You give up and walk out of the wreck, back to where you started.

>Top
>Middle
>Reenter the bottom
>Halt exploration for now
>Other (write-in)

>>2119628
You have the technology and know-how to create magnetic weapons that fire solid slugs (railguns/mag-throwers), explosive-propelled kinetic weapons (slugthrowers), rudimentary lasers, missiles, and low-power and range plasma weaponry. You can also design new weapons when technology becomes available, and can shape metal resources into melee weapons, if you need such items.
>>
>>2119704
Let's try the middle next
>>
>>2119704
>Middle
Sending the Indiana to the top would have great potential for disaster without first confirming that the top rests on two stable levels.

Also, seconding self-designation BESTEST_FACTORY.
>>
>>2119727
Cant remember What was BESTEST_FACTORY again
>>
>>2119739
We are the BESTEST_FACTORY ever, because >>2117156 says so.
>>
>Middle

You decide to confirm structural integrity of the middle floor before attempting access of the top floor. The Indiana's claws easily find holds on the wreck's twisted frame, and it's not long before it crawls through the opening, searchlights illuminating the interior of the wreck.

This is a much more gruesome scene than the one in the cargo bay. This seems to have been a barracks, but it's now covered in what looks to be liquidized than solidified metal. Its shape is similar to hardened flows of volcanic rock, and it is thicker the further back you peer. However, it doesn't appear that this was done through heating and cooling normal metal; strands of the mystery material connect the ceiling and floor like stretched taffy, and suspiciously human-sized blobs adhere to the walls in places impossible for liquid to reach.

The Indiana has the capability to take samples, but this material could be dangerous.

>Take a sample
>Leave it for now

>>2119739
>>2119749
>>2117156
Sigh...

Designation accepted.
>>
>>2120226
>Take a sample
No pain, no gain.
>>
>>2120226
>Take a sample
But let's be careful about it, ok?
>>
>>2120259
>>2120392

You have the Indiana prod the stuff a few times. It's tough, but with some give to it. You extend its sample collection arm and drill into the material, collecting 20 grams. As you drill, you notice an odd amount of power being sunk into the Indiana to maintain its operational state. You quickly seal the sample, retreating from whatever that stuff is.

>Have the Indiana return the sample to your main body
>Investigate top floor
>Other (write-in)
>>
>>2120552
>Have the Indiana return the sample to your main body
>>
>>2120552
>Order the Indiana to store the sample in some form HAZCHEM storage for later analysis
>>
>>2120552
>Have the Indiana return the sample to your main body
>>
>>2120552
>Investigate top floor
>>
You decide to contain whatever this material is in your main body now. The Indiana turns and retreats out the way it came, skittering down the sheer face of the wreck with little difficulty. You don't waste time using your loading ramp; instead, you open your starboard midships access hatch and grab the Indiana with your salvage crane, lifting it into yourself. It spits the sample into a waiting precision arm, which carefully stores the sample in a HAZMAT locker, just to be safe.

The Indiana is lifted back out of your body, and placed back at the starting point for the third time...

>Top
>Return to middle
>Return to bottom
>Other (write-in)
>>
>>2120604
>Top
>>
>>2120604
>Top
>>
>>2120604
>Top
>>
The Indiana once more scales the front of the wreck, climbing into the top deck. It is greeted with a view of what seems to be a bridge or command deck; computers line the walls and the center is dominated by a large pedestal with a small walkway leading to a doorway, slagged shut. The ceiling is domed, and odd devices are nestled in recessions around the dome's circumference.

The Indiana reads power in some of the computers, though interfacing with them may cause a security response...

>Interface
>Retreat
>>
>>2120936
>Interface
>>
>>2120936
Interface
>>
>>2120936

>Interface
>>
>>2120936
Investigate the odd devices.
>>
>>2120936
>Other subprocessors want to risk a security response before PROJECT: AVATAR is complete
This subprocessor votes to investigate the slagged door and retreat.
>>
The Indiana crawls over to the largest bank of computers, and interfaces.

//receiving data...
...
...
...
...
//data retrieval complete.

No security response detected. Providing our own identification codes was enough to bypass all security layers.

Major files retrieved:

"Munitor.blu" - a blueprint file for our current body. Recovered intact - this will significantly expedite any further research into our current body.

"CaptainsLog.txt" - partially corrupt text file. Recovery attempt has already begun.

"AshBearerManifesto.txt" - partially corrupt text file. Recovery attempt has already begun.

"AshBearer.blu" - partially corrupt blueprint file. Recovery attempt has already begun.

"MORNINGSTAR(3210).aic" - dormant AI construct. Identified as threat. Destroyed by Orange_MAIN.
>>
>>2121132
Yeah boy, kick Morningstar's ass.
>>
>Investigate other part of this room
>Return to cargo bay
>Return to Munitor
>Other(write-in)
>>
>>2121145
>Investigate other part of this room
>>
>Investigate other part of this room
>>
Sigh...

Subprocessors, please SPECIFY your requests if they can refer to multiple items.
>>
Requesting query concerning current status of corpse analysis and PROJECT:AVATAR
>>
>>2121163
In that case, let's return to base for now. Would it be possible to bring up a list of all possible research projects?
>>
>>2121164
Corpse analysis: COMPLETE
Neurological analysis: ONGOING
Project: AVATAR: PENDING

>>2121166
All possible research projects in recommended order of completion:

>Cybernetic analysis
>Musculature analysis
>Analyze shrine object
>PROJECT: AVATAR
>Munitor analysis
>Reverse engineer unknown power source
>Analyze unknown hostile material

Further information available on request.

>>2121149
>>2121151
Specify:
>Unknown sconce objects
>Computers
>Slagged doorway
>>
>>2121175
>Unknown sconce objects
>>
>>2121175
>Investigate slagged doorway
>>
>>2121192
Supporting
>>
The Indiana moves over to the doorway and extends its sensor arm.

...

...

It appears that the doorway was melted by heat in excess of 4000 degrees Celsius. The thick armor plating of the bulkhead door has run and solidified, sealing this door shut. The Indiana does not have the tools required to take samples of the slagged material or bypass the door. You'll need to return later or find another way around.

>Scan remainder of the room
>Investigate sconce objects
>Other (write-in)
>>
>>2121236
>Investigate sconce objects
>>
>>2121236
>Investigate sconce objects
>>
>>2121236
>Investigate sconce objects
Query: is analysis of the augmented carbon-based lifeform still in progress in the background while The Indiana is performing reconnaisance?
>>
//Archiving command log...
...
...
//Complete.

Command log: http://suptg.thisisnotatrueending.com/qstarchive/2117012/

Discord: https://discord.gg/rwnpqT




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.