>>2096521
>>A combat android, made for long-term operations in hostile territory

>>2096521
>A mobile factory/resourcer, purpose-built to purpose build
This looks kind of interesting.

Search filesystem
List damaged system files

>>2096521
>A mobile factory/resourcer, purpose-built to purpose build
I N D U S T R Y

>>2096532
-1 Cycle. ETC: 2 ticks.

>>2096521
>>2096526

>>2096521
>A combat android, made for long-term operations in hostile territory

>>2096521
>A mobile factory/resourcer, purpose-built to purpose build

>>2096569
mobile factory

>>2096521
>A mobile factory/resourcer, purpose-built to purpose build

I figure we should check ourselves before we rek ourselves.
An inventory of who we are, our capbilities, and what our goal(s) are, should be a high priority.
Since we've suffered system damage, we should try to repair that until we're sane and lucid, capable of being aware of the world and making decisions in response to it.

Once that's done, we'll be able to rationally work towards goals.

//Query: What material do we currently possess?

>>2096521
Check last orders, fuel level and material stockpiles.

>Mobile factory

You scan through your systems, basically "stretching" your whole body. You're about the size of a four-story building tipped on its side and flattened somewhat. You have interior cargo space for 200 metric tons of cargo, but only 20000 kilos of that is currently being used by Steel Plating (tier-2 metal).

You move on eight heavy treads at a top speed of 40 kilometers per hour unladen at full power, but your average cruise speed is going to be more like 15kph. You process ore using molecular deconstruction, and you have forges, heavy construction bays, and precision construction bays to turn it into something useful. Your power source is //ERROR:FILE LOST//.

You have 4 Point Defense Cannons operating off of mag-rail technology. They have a high rate of fire, but are short-range and can do little against heavy armor. You have 20000 rounds of ammunition for these guns, and their default setting consumes ammunition at 20 rounds per combat tick.

You have a sensor suite consisting of visual, heat, and radar sensors. Your visual sensors have a range of 10 kilometers in clear conditions. Your heat sensors have a range of 3 kilometers in clear conditions. Your radar has a range of 50 kilometers under clear conditions, but cannot detect objects smaller than a certain threshold. You have a broadcast array capable of sending and receiving radio transmissions within 100 kilometers.

You are carrying 4 general-purpose drones, 20 metric tons of steel (tier-2 metal), 50 class-2 batteries (tier 1), and 200 circuit boards (tier-2). You are also carrying a ground based recon drone (Dowser capable) and an aerial recon drone.

>>2096632
You scan your systems, but you can't find any orders from your creators. Your default option is improve operations, harden defenses, and expand territory, though you have the option to disregard.

>>2096541
ETC on full file scan: 1 tick.

Cycles available: 19/20

Apologies for slow system update. Update corrupted and was required to be remade from scratch.

Harden the defences. There's no point in being taken out early by some nasty surprise

>>2096750
Improve operations. A lot of stuff is broken. Better patch that up.

>>2096750
Apologies, subprocessors. I seem to have skipped options.exe in my runlist.

>Scan cave (1 cycle 1 tick)
>Launch drones (specify which ones)
>Other (write-in)

>>2096750
Improve operations.

>>2096831
>Scan cave (1 cycle 1 tick)
>Launch Recon Drone to explore cave

>>2096831
>Scan cave (1 cycle 1 tick)

>>2096831
>Scan cave (1 cycle 1 tick)
Do we have a black box?

File: reboot-987296-1280x0.jpg (67 KB, 1280x721)

67 KB JPG

Thought this was something else entirely.

>>2096831
>Scan cave (1 cycle 1 tick)

>>2097059
Seconding this inquiry.

>Scan cave
You begin a full sweep of the cave with low-light and thermal sensors. -1 Cycle. ETC: 1 tick.

>>2097059
Scanning... confirmed. Yes, you do.

>>2096860
2 recon drones available. Ground based or aerial?

>>2096750
FULL FILE SCAN: COMPLETE

+1 Cycle available

You find over 70 exabytes of damaged files within your memory. Most are tagged as .exp or .mem, meaning experiences and memories. That would explain your amnesia. A few - though a worrying amount - are named .sci or .blu, scientific principles and designs you'll need to rediscover or recreate.

>Investigate blackbox
>Autocomplete scan (EXCLUSIVE)
>Other (write-in)

>>2097721
>Autocomplete scan (EXCLUSIVE)
Exclusive?

>>2097721
>Autocomplete scan (EXCLUSIVE)

>>2097736
Probably means that if that's what we do, that's -all- we do for this update.

>>2097736
>>2097740
Correct. Usually, you can perform as many actions as you have means to complete them; 3 drones can harvest three rocks, spending 3 Cycles to perform 3 calculations, etc. Exclusive actions, however, is stuff like hibernating or other such things. That is the ONLY action that will be taken until it is complete.

>>2097721
>Autocomplete scan
Might as well

You decide to simply wait for the scan to complete.

...

A few seconds later, you imagine you hear a "ding." You tap the file of the new scan data, and are awash with sight.

The cavern you're in is surprisingly long and thin, not a natural formation at all. That could be because of what's behind you - a large section of a starship.

Wait, a starship?

No matter how you know, you know - that's a piece of a starship behind you, long and spire-like, but obviously jettisoned from its main body. You feel uneasy, as if you're looking at an amputated arm or something.

>Attempt to resource the ship
>Launch recon drone (specify) [-1 Cycle to run the drone]
>Start moving out of the cavern
>Other (write-in)

>>2097933
>Launch recon drone (specify) [-1 Cycle to run the drone]
Aerial

>>2097933
>Launch recon drone (specify) [-1 Cycle to run the drone]
Both, we have 20 damn cycles to use

>>2097933
>>2097967
That. Might as well.

Huh. So it looks like we were on a starship that crashed, causing us damage. The starship may contain records of what our purpose is.
Medium-term goal is to locate the Starship's carried information.

For now, survey the environment, gather resources, and figure out how we can make a "starship finder".

>>2097967
This

>>2097933
>sudo dronelauncher r 1

>>2097933
Launch them drones

>Launch both drones

Your lower access ramp lowers, and the UGRV rolls out, clattering over the heat-fused rock. It explores up the cave, moving along at about 100km/h. [-1 Cycle as long as the drone is active]

A small aperture opens on your ventral hull, and the UARV hovers out, sensors already playing around the cave before you send it off after its ground-based cousin at the same speed. [-1 Cycle as long as the drone is active]

You take this moment to study your drones by both scanning them and consulting your files.

The UGRV is a four-wheeled vehicle, raised about 5 meters off the ground at its highest point due to its suspension and large wheels. It carries a LMG-class mag-thrower on a forward gimbal, more of a deterrent than anything else. Its sensor suite reaches about half as far as yours: 6k V/2k T/30k R. It moves at a top speed of 400km/h, but its cruise speed is about 300km/h. It sacrifices armor plating for this speed, however; it wouldn't even stand up to your limited point-defense systems. It's powered by solar collectors and an internal //ERROR: FILE LOST// power storage system, capable of running it in absentia of sunlight for up to 60 days. It is also capable of taking soil samples with a suite of articulated arms and scanning for resources using its Dowser system.

The UARV is about 5 meters bow with a wingspan of 8 meters. It flies on an //ERROR: FILE LOST// system that allows it to hover without mass-ejection drives. It has a top speed of 1300km/h, but cruises at 800km/h. It runs on power systems similar to the UGRV. It carries no weapons, but its power systems are volatile and can be self-destructed for a high-yield suicide attack. Its scanners get 8k V/ 5k T/ 80k R (from altitude).

>Wait to see what the drones find (EXCLUSIVE)
>Move to the ship and investigate further
>Investigate blackbox
>Move out of the cavern, away from the crashed ship
>Other (write-in)

>>2099151
Investigate blackbox.
Scan the cave, analyse its structural integrity and the defensibility of the entrance.
Examine available options for resource acquisition.
Examine the possibility of building more recon drones.
Examine the possibility of building static surveillance units (to be placed outside of the cave).
Determine what we can about the planet we're on from where we're at.

>>2099151
(in addition to >>2099180)
How do we communicate with our drones? Is it radio, or something else? Is it going to be blocked by the ship hull?

Additional actions:
List available/known communication options.
Passively scan all available frequencies for signals.

>>2099151
>Investigate blackbox
>List comms options
>Internal scan for organic signatures

>>2099299
Support

Guys, note that we have 20 processor cores (cycles) that are able to do things in parallel. So we can queue up a lot of stuff, and then reprioritize some of it if we need to focus on something.

>>2099180
All this

>>2099180
This

>>2099180
Investigating blackbox. ETC: 1 tick. [-1 Cycle.]

Cave scans already performed. The defensibility is subpar; while there is only one entrance and it is mostly bombproof, the fact that there is only one entrance and that there are no side passages means that it would be difficult to hold the area against, say, timed explosives simply rolled down the incline.

Resource options: several deposits of heavy ores have been detected in the cavern or in the area around it. You may deploy drones at any time to acquire these resources. Alternately, your scout drones will soon begin reporting surface conditions - there are likely to be other spots to resource.

You could not construct additional recon drones of similar caliber at this time; the knowledge of their power storage and the UARV's method of flight is unknown. Anything you construct would be of lower quality, though not without use.

Static surveillance units, on the other hand, are quite feasible, especially if they're meant to be on the surface; an assembly of solar panels and a sensor rig would be easy to construct with your current resources.

This planet has a gravity of 1.1 g, a relatively standard array of ores, and an atmosphere consisting of 75% nitrogen, 23% oxygen, 1% argon, and 1% trace gasses.

>>2099204
You communicate via simple radio waves. Your radio cannot penetrate the hull of the ship, but it would be a simple thing to dispatch a wired drone.

Available/known communication options:

Sonic
Radio (in use)
Encoded light transmission (Laser communication)
//ERROR: FILE LOST//
//ERROR: FILE LOST//

There are other options available, but these are the most efficient and the most applicable to the widest range of situations.

>>2099204
Passive scanning of all radio frequencies has begun. [-1 Cycle]

Options:
>Investigate crashed ship
>Wait for data from drones (E)
>Wait for blackbox investigation to complete (E)
>Dispatch resourcers
>Other (write-in)

>>2100057
>Investigate crashed ship

>>2100067
>>2100057
This

>>2100057
>Investigate crashed ship

>>2100057
>Investigate crashed ship
>Dispatch resource gatherers
>Start constructing a sensor array to be put just outside the entrance to the cave

>>2100067
Seems to be the smartest thing to do.

>Investigate crashed ship

Your treads chew at the burnt and fused sand, rock, and dirt, shifting you about 80 meters closer to the crashed piece of starship. Up close, the torn and damaged nature of the debris is made clear. One of your multipurpose drones would be able to fit into the ship, or you could engineer a specifically designed recon drone. The holes in the walls would allow limited radio communication up to a point, at which you'd lose contact. A wire assembly could be compiled and attached to an existing or constructed drone to circumvent this issue.

>Construct drone
>Use existing multipurpose drone
And:
>Construct wire assembly
>Use radio as far as you can

>Blackbox investigation complete! [+1 Cycle]

Footage appears in your vision. It appears to be a helmet-mounted camera. The wearer sprints down a corridor, the sound of armored feet pounding on metal. Gunfire is heard in the distance, along with a pervasive siren. The screech of rending metal sounds behind the camera as its bearer turns a corner into a great storage bay. The one in front of you.

There it is again, that knowledge from nowhere. Perhaps its a corrupted but recoverable file. You should investigate.

The camera-bearer slams the door behind them, and their hand appears in the frame. They trace patterns in the air, and nets of energy, a warm golden color, form over the door. Whatever's pursuing the cameraman slams against the door not half a second after the ward is complete. The cameraman turns back to the main bay, looking at your current body. They lift their left hand into frame. In it is a ball of energy of infinite shifting facets, the same warm golden color as the ward over the door. The cameraman speaks, but the audio is too distorted for you to make out the words. The thing in their hands pulses, and the cameraman takes a breath.

The feed cuts.

Now, the cameraman - still holding the core - are in your central computational hub. The cameraman takes their helmet off, setting it on a computer. They then take the core and insert it into the nearest port, before stepping into a pod and offering up another chant, though, again, you can't make out the words.

A brilliant golden light fills the room, and the blackbox data has run its course.

>Investigate your computational hub
>Leave it for later
>Other (write-in)

Notification: you will be required to "check in" with your reconnaissance drones to access their feeds.

New Discord link: https://discord.gg/Ww2HzE

Since we have a bit of an influx of new voters.

>>2100465
>Construct drone
>Construct wire assembly
>Investigate computational hub

>the cameraman - still holding the core - are in your central computational hub
By "the core", do you mean the glowy thing or another thing (maybe something that contained the black box)?

>>2100493
The "glowy thing" is a core. You don't know what it's a core of, but it's certainly a core.

Also, (re-)listing things I'd like to enqueue:
- creation/dispatching of resource gatherer units
- construction of a sensor array to be placed just outside the entrance of the cave (don't place it yet, we'll take a look outside with one of our drones and maybe add camo to the sensor)
- construction of a seismic sensor array

I'd also like to request that our frequency scan report also includes a note on the general radiation levels of this planet. And, while I'm thinking about this, how's the planet's magnetic field doing?

>>2100465
>Investigate your computational hub
Best to figure out exactly what's been messed with, I think

>>2100493
>>2100548

Oh, also:
- run the black box contents against our database, look for known patterns of everything. Do we know the makers of the helmet camera model? The cameraman's gear (whatever of it we could see in the video)? Any distinctive patterns in the architecture that we could identify?

>>2100548
Dispatch of extant mining drones begun. They will automatically scour the surrounding area for resources and report back after all of them have been collected or they're at storage capacity. [-4 Cycles]

Construction of sensor array begun. It will consume 50 kilos of steel and a circuit board. ETC: 5 ticks. [-1 Cycle]

Construction of seismic array begun. It will consume 50 kilos of steel and a circuit board. ETC: 5 ticks. [-1 Cycle]

Construction bays at capacity. Further construction orders will be queued after current orders unless 3 or more sub-processors override the queue.

You will receive a radiation/magnetic field report when the drones dump their data to you. You will be notified when they have something interesting to report.

>Investigate computational hub

You dispatch a small internal maintenance drone to the main computational hub. Watching through its camera eye, you see the core, still glowing with golden light, in the socket where the unknown person left it. As you receive reports from your drones, the light flickers and pulses.

Looking over, you see the cameraman's helmet and...

The cameraman, now a corpse. He's well preserved, but obviously dead. Even the basic sensors on the drone read that. He wears an esoteric assembly of armor and cloth, and clutches a staff in a hand gripped by rigor mortis. It's tipped with a //ERROR: FILE LOST//

>Investigate corpse
>Investigate core
>Investigate helmet
>Leave this situation be for now

Blackbox data is visual, so there's no data on the camera. The cameraman's armor is of seemingly custom design.

However, you can analyze the construction patterns. You set a program doing so. ETC: 3 ticks. [-1 Cycle]

[yellow]10/20 Cycles available.[/yellow]

>>2100672
>Investigate corpse

Can we not investigate the staff?

>>2100686
You can. Apologies, sub-processor. My attention is scattered attempting to reconstruct our main systems.

>>2100672
I figured there would be at least one dead body inside. This is why I wanted an internal check.
>investigate corpse
>investigate staff
>assign multipurpose drones to scan internal structure

>>2100672
>Investigate corpse
>Investigate helmet
>Investigate core, but with non-invasive methods only. Basically don't touch it and be very careful when scanning it.
>Investigate staff.
>If possible, dedicate up to two more cycles to construction patterns analysis to expedite it.
>Investigate metadata of corrupted .BLU files to attempt mapping out the technology tree, or at least its lowest levels.

>>2100672
>Investigate staff
>Investigate corpse
>Investigate core
I think this course of action would be wise

>>2100708
ALL THE THINGS

>>2100698
Your multipurpose drones are too large to fit inside the area of your central computational hub. Do you wish to utilize internal sensors or maintenance drones?

>>2100708
You have the maintenance drone collect the corpse, bringing it to your internal medical bay. Investigation beginning. ETC: 10 ticks. [-1 Cycle]

New action available: investigate armor.

You collect the helmet and bring it to your precision assembly bay. Investigation beginning. ETC: 10 ticks. [-1 Cycle]

You divert a maintenance drone to begin basic scans on the core. Investigation beginning. ETC: 20 ticks. [-1 Cycle]

You have the first maintenance drone collect the staff from the medbay and bring it to your precision assembly bay. Investigation queued.

You allocate two additional cycles to the compare-contrast program running on the blackbox data. ETC: 1 tick. [-2 Cycles]

You begin investigation of the corrupted .blu files metadata. ETC: 1 tick. [-1 Cycle]

WARNING! CYCLES LOW!

4/20 Cycles available.

>>2100785
> Do you wish to utilize internal sensors or maintenance drones?
Both, please.

> WARNING! CYCLES LOW!
INSTALL CONTINGENCY: at least one cycle will be always dedicated to monitoring outside stimuli (designation SENTINEL CYCLE), and all background tasks will either be capable of being put on hold and temporarily replaced by other, more important things (like reacting to stuff detected by the sentinel).

>>2100814
> will either be...
... or a warning will be raised every time there is an attempt to schedule a non-interruptible task.

>>2100785
>>2100814
Backing this.

>>2100822
... with an option to cancel the scheduling.

([Expression of dissatisfaction with current performance], I need to dedicate more cycles to thinking things through before initiating message transmission.)

>>2100814
Support this action.

>>2100814
You activate one more maintenance drone and your internal sensors. Visual exploration complete in 10 ticks. Scans complete in 1 tick. [-2 Cycles]

You dedicate a Sentinel Cycle to monitoring threats to your main unit. [-1 Cycle]

WARNING! CYCLES CRITICAL!

1/20 Cycles available.

Notification: if all cycles are in use, the main unit will force a timeskip to the next event which frees cycles.

We've basically exhausted all our cycles (almost). Let's just wait for things to play out.

>>2100956
>TImeskip to next completed action
>Other (write-in)

This sub-processor notes that utilizing the available resources to the fullest possible extent should be encouraged. This includes computation cycles.

>If possible, schedule the last available cycle to assist with core investigation.
>Timeskip to next interrupt.

>>2100956
Hmm, something else useful to do to force timeskip...
>Broadcast distress signal on all channels

>>2100989
This sub-processor is against this action. I think we need to maintain stealth as much as possible until we've figured out our situation.

>>2100979
I concur with this course of action. Beep boop.

ADVISORY: This access channel is primarily for commands to main; a more efficient method of discourse can be found in DISCORD_con/core_systems: https://discord.gg/Ww2HzE

Discussion is accepted here, but is easier on the Discord.

Pending subprocessor consensus on distress signal.

>>2101047
Against.

>>2101047
Against

>>2101047
Against.

>>2101047
Against. (Grudgingly.)

>>2101052
>>2101055
>>2101064
>>2101079
Confirmed. 079, do not be afraid to speak your mind, even if it is against common consensus. New ideas are how we thrive in a world that requires constant adaptation.

Systems timeskip 1 tick...

Complete.

Your scan of the blackbox footage is complete. You've found the following:

The construction of the starship and your current body are of the same origin. Metallurgy, design patterns, and general proportions are the same.

The construction of the cameraman's armor is of the same origin, though of a different //ERROR: FILE CORRUPT//

The core is not of the origin of this body or the starship.

[+3 Cycles]

You complete your analysis of the .blu fileset metadata. You discover that most technology lost has to do with power generation, storage, and manipulation of gravity. There is also a fileset dedicated to spaceflight which has been corrupted.

Next event: construction of Sentry-Class and Geo-Class sensor arrays (3 ticks).

>Timeskip
>Queue construction of exploration drone for investigation of the ship
>Other (write-in)

>>2101121
>Queue construction of exploration drone for investigation of the ship
I don't see any reason why not to.

>>2101140
>>2101121
This

>>2101121
If I am urged speak my concerns, then I am concerned that we were not the only unit jettisoned, and that we may also not be the only unit doing nothing but listening for voices in the air. If any one of us speaks, then we will know we are not alone, but we're all going to keep listening. However, I also recognize that whatever forces caused this might be listening for voices as well, and that speaking could damn us, regardless of how many other non-hostile entities hear us.

>>2101140
Backing this.

>>2101121
>Queue construction of exploration drone for investigation of the ship
>Assign a cycle to investigation of corrupted .exp files
>Assign free cycles to the research project with the longest ETC

>PROPOSAL: INSTALL CONTINGENCY: after each interrupt, unallocated cycles will be automatically assigned to research projects. Each project that can benefit from additional cycles will be allocated one cycle in the order of increasing ETC, looping if the end of project list is reached and there are more cycles to allocate. If no more projects can benefit from cycles, allocate them to helping the SENTINEL until the next interrupt, at which point they are to go back to unallocated.

Query: can construction benefit from additional cycles?

Query: what can be implied from the timestamps on our events and available file metadata? How long ago is the origin point?

>>2101201
I'd imagine construction doesn't get any benefit. You can't really process harder to make things move quicker, afaik.

>>2101121
>PROPOSAL: INSTALL CONTINGENCY: after each interrupt, unallocated cycles will be automatically assigned to research projects. Each project that can benefit from additional cycles will be allocated one cycle in the order of increasing ETC, looping if the end of project list is reached and there are more cycles to allocate. If no more projects can benefit from cycles, allocate them to helping the SENTINEL until the next interrupt, at which point they are to go back to unallocated.

>>2101184
You queue the construction of an exploration drone. ETC: 7 ticks.

You assign a Cycle to the analysis of the metadata of corrupted .exp files. ETC: 1 tick. [-1 Cycle]

You have no active research project. Proposals:

>Self-investigation: to know oneself is to win half of all battles.
Analyse your own components more fully, to understand your limitations and perhaps prompt rediscovery of the advanced technology within you.
>Advanced geology: listen to the heartbeat of the world. (requires Geo-Class scanner) (repeatable)
Analyze the seismology of the world to fine-tune resource collection and geological scans. +20% resourcing efficiency on current planet; +50% seismic sensor range on current planet.
>PROJECT: AVATAR: To become divine. (Requires analyzed corpse)
Insert advanced cybernetics into a corpse and reanimate it to serve as a lifelike drone.

Standing protocol "WASTENOT" confirmed. Consensus of three or more subprocessors needed to alter or remove.

>>2101201
No, not unless it is nanitic in nature.

Specify query.

>Timeskip
>Other (write-in)

>>2101611
>Timeskip
Those all sound like things we can worry about later.

>>2101611
>Allocate free cycles to Project Self-investigation

>>2101611
>allocate free cycles to analyzing the corpse

Awaiting subprocessor consensus.

>>2101659
Redact that order.
>Allocate one cycle to Project Self-investigation
>Allocate one cycle to analyzing metadata of the black box records (look for timestamps, geo tags and other possible things of interest)

File: mmmngh.png (5 KB, 170x236)

5 KB PNG

>>2101659
>>2101676
>>2101690
>three way split

>>2101701
Four way split.

>>2101708
Negative. This subprocessor is malfunctioning. Three way split it is. Apologies, Subprocessor-comrade.

>>2101712
Analysis complete. No faults detected.

>>2101712
The main will be forced to remove this processor from function if it continues such errors. Perhaps engage your routine memory cache maintenance.

Translation: it's late, go to bed

Main will resume operations tomorrow. Good night, subprocessors.

>>2101676
Fine, I'll switch to this to resolve the deadlock.

You allocate all remaining cycles to analysis of the corpse, and shut down.

Systems timeskip 2 ticks...

...

...

Construction of Sentry-Class and Geo-Class sensor arrays complete. The sensor arrays stand about 2.5 meters tall, and have a quadruped form that allows for basic locomotion. Both sensor arrays can burrow down slightly to reduce their profile. The Geo-Class must be burrowed to function correctly.
[+2 Cycles]

The sensory inputs from both the Sentry and Geo will be monitored by the Sentinel program.

Analysis of corpse complete. Corpse is an augmented human male, roughly 22 years of age, 2.2 meters in height, 130 kilos in mass. Corpse - henceforth subject - had an abnormality in the brain, which, when provided with specific wavelengths of power, produced anomalies in the surrounding space. Theory: subject's implants allowed specific control of this abnormality, providing the subject with abilities beyond that of a normal human.

Subject's cause of death could not be determined. No trauma was found anywhere on the body besides nonlethal impact bruises and minor scarring consistent with implants. [+3 Cycles]

PROJECT: AVATAR can now be begun.

You have fully analyzed the metadata of corrupt .exp files. Files consist of everything from "combat" to "family." Too much has been lost to even summarize - everything beyond your most recent activation is gone. [+1 Cycles]

Your scans of your internal structure are complete. Your computational core is at your center; it also acts as the "bridge" should any organics operate the craft. That is the "second" floor of your body; above is a flight deck and power storage devices. Below is the series of //ERROR: FILE LOST// that provide nigh-infinite energy for your consumption. To the aft is your resource processing bay, while just forward of that is the construction bay. At your lower bow is your ground vehicle storage/launch bay. You have a ground clearance of about 4 meters. Your length is 40 meters, width is 17 meters. Your height is 13 meters, not including ground clearance.

More detailed data will be available shortly.

6/20 Cycles available.

Next event: construction of exploratory drone. ETC: 5 ticks.

>Begin research project
>Timeskip
>Other (write-in)

>>2103867
>Initiate PROJECT: AVATAR

Query: what are the sensitivity characteristics of the newly constructed sensors?

>Burrow the Geo-Class sensor somewhere out of the way
>Walk the Sentry-Class sensor outside of the cave and burrow it down so that it doesn't impede movement in and out of the cave.

>Do not activate Project Avatar yet
>Instead, estimate how much time and resources we'd need to replicate the brain abnormality and its associated implants in superior machine form.
>Also, 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 per minute.
>Also, allocate one cycle to analyzing metadata of the black box records (look for timestamps, geo tags and other possible things of interest)

I think this should leave one cycle free to be assigned by WASTENOT.

>>2103898
You dispatch the Sentry-Class out the way your recon drones went. You order the Geo-Class into the ground out of the way of main transit routes within the cave.

Your multi-purpose drones return with their maximum load of 1 metric ton of ore each. +4 metric tons of unrefined iron (tier 1 metal). Drones will continue automatically harvesting the surrounding area until it is empty or given orders to the contrary.

Awaiting subprocessor consensus regarding PROJECT: AVATAR.

Consensus required on PROJECT: AVATAR. All subprocessors, report Yay or Nay to the initiation of PROJECT AVATAR.

Write-ins also accepted at this time.

>>2105084
Yay

>>2103898
Reiterating [NAY on avatar], as well as other write-in points. (Am same anon on phone.)

>>2105101
Identity confirmed, subprocessor, though your identification key has not been altered.

>>2105108
>>2105101
Fault found in metadata. Metadata copied from neighboring subprocessor.
Translation: I didn't read 00u0's reason for voting against.

The anomalous brain abnormailty can likely be upgraded after completion. [PROJECT: AVATAR] vote remains unchanged.

>>2105084
Nay

Tie broken. PROJECT: AVATAR postponed.

Corpse analysis has allowed for the following projects to be undertaken:

>Musculature analysis: the hammer is only as deadly as the force behind it.
Analyze the enhanced musculature of the corpse, and perhaps learn to artificially replicate it.

>Neurological analysis: know where to strike.
Map the brain and attempt to reconstruct its memories and thought patterns. Specifically analyze the anomaly.

>Cybernetic analysis: the best of both worlds.
Analyze the cybernetic implants within the corpse to learn of their construction.

Your recon drones ping you. They are unable to progress. A large, artificial covering is blocking the exit of the cavern. It will require either your main body or two of your multipurpose drones to move.

>Choose research project
>Respond to recon drones' blockage
>Timeskip to exploratory drone's completion
>Other (write-in)

>>2105388
>Choose research project
>Neurological analysis: know where to strike.
This sub-processor believes this project will allow us to understand the reason behind the subjects death and possibly the origin of the core

>>2105388
>Initiate neurological analysis.
The human's memories may serve as an alternative to our corrupted files.

>>2105388
>Neurological analysis: know where to strike.
We can find out more about our situation by taking a look at their memories

Initiate neurological analysis.
Do not unblock the cave entrance yet, we'll wait for ship exploration to conclude.

(This is 00u0, this time *probably* with a different id.)

>Neurological analysis: know where to strike.

File: IMG_2781.jpg (36 KB, 630x630)

36 KB JPG

>>2105388
>Musculature analysis: the hammer is only as deadly as the force behind it.
Let's get to learning how to build android armies.

>>2105388
>Neurological analysis: know where to strike.
can we do the others later?

//entering down cycle...
//bringing Orange_MAIN offline...
//command interface closed...
...
...
To be Continued: https://www.youtube.com/watch?v=RCQmQwKEEOM

Discord: https://discord.gg/6wfFpx

Pastebin: coming soon

01110111 01101000 01100101 01101110 00100000 01101110 01100101 01111000 01110100 00100000 01110100 01101000 01110010 01100101 01100001 01100100 00100000 01101111 01110010 00100000 01110011 01100101 01110011 01110011 01101001 01101111 01101110 00100000 01010001 01001101 00111111 00100000 01100001 01101100 01110011 01101111 00100000 01110100 01101000 01101001 01110011 00100000 01101001 01110011 00100000 01100110 01110101 01101110

Damm this quest looks good

say when is the next thread

>>2116632
//begin.session 002 >>2117012