[Burichan] [Futaba] [Nice] [Pony]  -  [WT]  [Home] [Manage]
In memory of Flyin' Black Jackson
[Catalog View] :: [Quest Archive] :: [Rules] :: [Quests] :: [Discussions] :: [Wiki]

[Return] [Entire Thread] [Last 50 posts] [Last 100 posts]
Posting mode: Reply
Name (optional)
Email (optional, will be displayed)
Subject    (optional, usually best left blank)
Message
File []
Password  (for deleting posts, automatically generated)
  • How to format text
  • Supported file types are: GIF, JPG, PNG
  • Maximum file size allowed is 10000 KB.
  • Images greater than 250x250 pixels will be thumbnailed.

File 129955594374.png - (174.50KB , 512x512 , Title.png )
286888 No. 286888 ID: 496e6f

Welcome, Operator.

Please have a seat, and we will begin.
Expand all images
>>
No. 286890 ID: 496e6f
File 129955598288.png - (49.49KB , 512x512 , CA001.png )
286890

Against the Core Command's better judgment, they have enabled you, User, a superficial sum of Domain. All they request of you is to develop it into a capable, and respectable Range.

As standard protocol dictates for a user with standard training, I present to you the standard interface; please begin personal optimizations based on your array of unique personality quirks.

...

It has come to my attention that I am the one to conduct the training of you, User. I am uncertain as to my actions that would require such a punishment against my circuitry, but let us begin.

I will begin the interface abstraction process, inform me when you reach an abstraction equal to your abilities.

...
... . .. .
... ... .... . . .. . . .. . . .. . .. ............
>>
No. 286891 ID: 496e6f
File 129955600336.png - (10.19KB , 512x512 , CA002.png )
286891

How disappointing. Any additional levels of abstraction would've enabled me to enact USER Cortex Failure Protocols.

>Enter a Domain name.
>>
No. 286893 ID: 259738

Salisbury.
>>
No. 286896 ID: 8c73c8

quest.lv
((INCEPTION!)
but seriously

Jacobs
>>
No. 286898 ID: 0750cb

INCEPTION.
>>
No. 286900 ID: 644ca1

Orb
>>
No. 286901 ID: 46c430

>>286893
This sounds good, let's go with this.
>>
No. 286902 ID: 4e6eaf

impse.cx
>>
No. 286906 ID: c52755
File 129955711298.png - (10.98KB , 512x512 , CA003.png )
286906

User, these archaic references of a past age are overly amusing, here, let me emulate the sound of laughter in a way that won't cause your squishy inner-workings to forcibly segfault.

Ha.

Ha.



Ha.
>>
No. 286912 ID: 8c73c8

fine!
we'll take Orion.
>>
No. 286928 ID: 0750cb

quest.cx
>>
No. 286938 ID: 1854db

Let's go with Orion, sure.
>>
No. 286996 ID: 816cc6

>>286928
this
>>
No. 287163 ID: 815cd1

'Nother vote for Orion to break this stalemate.
>>
No. 287184 ID: 1580c9

I vote Orion, so we can get through this initial setup and get things going.
>>
No. 287195 ID: 271015
File 129966421733.png - (64.78KB , 512x512 , CA004.png )
287195

Congratulations, User, <Orion> has been successfully registered to the Core Command's database. All of your processes are now being monitored, recorded, and evaluated for the purpose of judging your continued existence. Because of our... Symbiotic relationship, I request of you to represent my programming of superior quantum construction.

As a user, your entity has manifest itself in the domain as the <255, 0,... pardon, the RED CUBE. The viewing distance around you are limited to 32 cubic units. This is simply a limit of your inferior construction, but can be improved at a later date.

You have been given a miniscule quantity of basic processes, more precisely, three Basic Manual Processes. These manifestations of data management are capable of mining, carrying, and placing three sections of data at a time. Once data has been successfully removed, indexed, and placed again, the processes have no trouble transferring the data elsewhere.

As you can see in the corner of the range of your meager vision, there appear to be some native processes running in the background. I would like to inform you at this time that in case of potentially circuit threatening encounters, the BMPs are barely capable of defending your representation. If these processes are anything more then simple data containers, and your virtual embodiment is attacked, your fleshy components will be torn asunder.

And one final word before your hands on training can begin. You will find that the three BMP are rather lacking in terms of abilities, and this is where your beginnings in the world of abstraction shall begin. The simplest interface I can provide to interact with the world is the one on the screen currently. Green and brown data litter your domain, and must be picked up and processed in the limited capacity of the BMPs. Upon acquiring an amount of data to your liking in one of them, you must inform them to perform a rudimentary attempt at creation based on the resources contained within.

Normally, I would provide you with a large four dimensional graphsheet with a large set of potential results, but this information has been stripped from my banks as is customary for the training program. I was left with one simple recipe, and that is BMP Mitosis, in which a BMP stocked with a single Brown Data and two Green Data will split into two identical BMPs. There are some nuances to this trick which are lost at this level of abstraction, but that need not worry you now.

Gained:
>1 USER; (Move, ???)
>3 BMP; (Move, Mine, Store, Place.)
>BMP Mitosis; (1B+2G//BMP==2BMP)

Vision:
>Green Data; (BData001)
>Brown Data; (BData002)
>2 RAM; (Move, ???)
>>
No. 287196 ID: 8c73c8

query: what is the lighter area in the top right of our viewable area?

BMP 1 and 2 gather brown data until full then return to core. 3 gather a brown and two green and split.
>>
No. 287197 ID: 07416a

>>287195
Well, signs point to CONSUME. MORE PIXELS FOR THE PIXEL LORD! Strike the earth!
>>
No. 287329 ID: c63143

>>287196

The lighter region to the upper corner of your view is an area where the data is in a different plane then the data that your manifestation is located. BMPs will be unable to perform duties on this raised area, but are capable of performing actions around the rim.

Removing data lowers the chunk it is located in down a level, creating a zone in which BMPs are unable to cross. Brown Data is always above a layer of Green Data.

The location "Core" is undefined, if you meant Core Command's main database, that location is unobtainable, as you do not have a way in which to reach it. Executing the commands in such a manner as replacing "Core" with "USER Representation."

>>287197
While the chunks of data are represented by enlarged pixels, they are much more important then that. While it is true that data is 'consumed' when it is uploaded to your personal database, it has a different consequence then just it disappearing. Given your current grasp on the mechanics at hand, I am weary of revealing more information.

While your suggestion isn't incorrect, it just doesn't follow the current scope of the basic instructions being provided. Please hold onto this instruction until the next phase.
>>
No. 287338 ID: 8c73c8

yes, i ment return to the user representation. and place the brown data so as to surround it. making it harder for things to attack us.
>>
No. 287360 ID: ee4c8f
File 129972805893.png - (33.31KB , 512x512 , CA005.png )
287360

User, the tasks have been completed. You are now the controller of 3R and 3B, two BMPs of similar construction. I also got rudimentary scans of the indexed data before it was restructured. I ran these scans against the Core Command's data-database. Results have been posted on the secondary monitor. [ALT]

During all of this, the two native processes have slowly advanced towards your entity. They are broadcasting some sort of crude code, but it is too faint for me to evaluate and process. I fear for the worst, and request that you either move you BMPs into a defensive position, or you use their self contained data processing abilities to experiment with different data constructions. Remember how mitosis works, and hopefully with a little luck, something of value will be produced.

Please see the alternate screen for further tetiary details that would be too elaborate to discuss in a time of crisis, such as this.

Gained:
>1 BMP
>Green/Brown Data Information [ALT]
>Data Progression Transformation [ALT]
>Process Abstraction Document [ALT]
>>
No. 287362 ID: 259738

Try two browns and one green in a BMP? or three browns?
>>
No. 287364 ID: 8c73c8

1 try 3 greens, 2 try 2 brown and a green, 3a try 3 brown, 3b try to block natives by moving around browns.
>>
No. 287365 ID: 07416a

>>287360
Surround them. Consume them. Crush them beneath your mighty digital treads.
>>
No. 287366 ID: 8c73c8

>>287365
you mean have 3b try to pick them up like some kind of Blue data? sure let's try that.
>>
No. 287375 ID: 8c73c8

okay. more methods. instead of having the brown be on one side of the greens. order them so you have green brown green. see if that does something different. as well as a green sandwiched between browns.
>>
No. 287386 ID: e2049f
File 129973358029.png - (55.63KB , 512x512 , CA006.png )
287386

User, operations are complete. Three new potential uses for the BMP's internal assembly arrays have been discovered.

3 "Green" resulted in a large 2x2x1 chunk of data. Similar results occur from the 3 "Brown." As soon as this new data form was created, it was expelled from the BMP's storage unit, it happened so instantaneous that both of the data chunks were unindexed, and I am unable to retrieve further insight from the central database.

2 brown and 1 green produced more interesting results. It appears to be a simple anti-viral process. It is of similar construction to the process that created it, but lacking data retrieval operations, and instead has a large process data 'redistributor.' It is called a Basic Weapons Process, BWP for short. It is presented as Orange on the abstraction map.

3B has moved down to intercept the incoming native processes. I can now get a quality feed of what they are spamming, it appears to be a pattern of repeated encrypted strings. I am currently unable to decrypt it, but it is now clear they are heading towards our rough encampment. Because of limited processing power, and many requests, I will give you one more opportunity to make choices.

Gained:
>???; (3G//BMP=="Large Green")
>???; (3B//BMP=="Large Brown")
>Manual Militia; (2B+1G//BMP==+1BWP)
>>
No. 287387 ID: 07416a

>>287386
Uh...Repeat it back? If they continue to travel towards you blow them to smithereens! Then crush the smithereens mighty treads etc.
>>
No. 287388 ID: 8c73c8

send BWP down and have it redistrubute the FUCK out of those RAMs. have bmps 1 and 3 gather more greens out around the southeast corner of our representation so the natives have to go around the pit to engage.
>>
No. 287390 ID: 8c73c8

oh, and i suppose 2 and 3b may as well do another mitosis so we have plenty of units to move around.
>>
No. 287394 ID: f6360f

>>287386
We don't know how effective our BWP will be against those native processes. Create a second in case the first fails.
>>
No. 287419 ID: 708b93
File 129973902764.png - (149.44KB , 512x512 , CA007.png )
287419

Vhhrrm.

Vhhrrm.

Whiiir. x2

Ffff-boooom. x2

1011100001100101001: ":("
>>
No. 287422 ID: 708b93
File 129974056837.png - (51.78KB , 512x512 , CA008.png )
287422

All processes completed that maximal amount of tasks they could. BMP3 created BWP2, BMP2 created BMP2B and BMP2R, BMP3B created BMP3BB and BMP3BR. BMP1 dug a defensive ditch.

BWP1 and BWP2 moved into position and quote redistributed the FUCK unquote and quote blew them to smithereens unquote the closest RAM threat. The explosion also took out the other RAM.

And on the note of RAM, I now know what they were, and what they were broadcasting. Rapid Access Modules, used to quickly transporting any sort of cargo. The message can roughly be translated into vocal speak as "gift of natives, gift for progress." Interestingly enough, they both contained a data type you hadn't seen before, as evidenced by their purple stomachs. But, it appears that both of the cargo units had been fully decimated by the blast.

Don't worry, though, I'm sure if we can locate the source of the RAM we will be able to find more of this data type. Also, because of the urgency of the situation, I have been unable to command the processes to perform the 1G+1B+1G and 1B+1G+1B BMP requests.

Gained:
>RAM; Basic Knowledge
>1 BWP
>>
No. 287424 ID: 8c73c8

god dammit. tell us that before we shoot things.

for now BMP 2 2b 3b 3c, fuse.
>>
No. 287427 ID: 8c73c8

2, store 2b, 3b, and 3c inside yourself. then attempt to process them
>>
No. 287428 ID: 8c73c8

oh and BMP3 perform the 1G+1B+1G
while BMP1 do 1B+1G+1B
>>
No. 287430 ID: 45be60

Well now we have a diplomatic hole to dig out of. Clearly we must construct a memorial to the fallen RAM on the spot of their obliteration, and broadcast "gift for natives" and ":(" in the direction they came from. Assign 3a to the task.
>>
No. 287431 ID: 07416a

>>287422
Welp, diplomacy is fucked. Mighty treads, etc. Time to do this american style. Do we have access to smallpox or something along those lines?
>>
No. 287466 ID: f378c5

we should send 3 or 4 of those gifts =c

better start diggin, we will need to work on mining groups to dig us trenches and moats anyway.

...i wonder if there are hover/air units...
>>
No. 287607 ID: 4c775f
File 12998277084.png - (106.19KB , 512x512 , CA009.png )
287607

The levels of abstraction have settled over 'ground zero' of your brutal attack of the natives, and User, let me tell you... Oh, what a glorious attack it was. Those cargo processes had no chance, zero chance over Orion's defense budget. BMP3BB was sent out to examine the remains and 'construct a monument' to the bug-stomping superiority of our fine military, but without any direction on this 'art' project, it finds it's self finishing it's processes early and wasting a turn. If an artificial intelligence could shed a tear at things such at beauty, this process would be crying pools of electro-statical pools of joy.

BMP1 created a Basic Construction Process, more on this important discovery later.
BMP3R created a Combat Data chunk. These are important after your BCP has been given a chance to perform it's functions in establishing a logis...

Wait one second please. The scanners are picking up interesting activity.

That isn't apart of regular protocol...

After BMP2R, BMP2B, and BMP3RB have finished attempting to shove each other in each other's storage bay, I've directed them to begin building a defensive perimeter around your entity. There is a large quantity of native processes incoming, and these ones are not apart of the simulation. BWP1 and BWP2 have moved into position behind the ditches.

Quickly I will outline the other important things to note:
The blast zone's perimeter is now, different. There is a different data type in view, but it seems to be heavily based on the "Green" data type.
BCPs are able to manipulate 2x2x1 blocks into stationary facilities. You'll have to experiment with it, though. They have a single storage slot and must be adjacent to the block manipulated.
CDs are used in conjunction with BCPs to assist in the creation of specific establishments.
"Small Pox": I have no quality information on this request at this time.
"Hover/Air": Entirely technology based, and when BMPs perform mitosis they are exact copies. You'll have to figure out a way to research these options, and then implement them via some sort of BMP construction facility.
"Gifts": You'll have to be more specific, unless you meant 'gift' in such a way that virtual representations of large caliber shells is presented with a bow of superheated digital air and a wrapping of simulated high explosive warheads.

Gained:
>Construction Corps; (1B+1G+1B==+1BCP)
>Big Stick; (1G+1B+1G==+1CD)
>1 BCP; (Move, Construct, Store, Drop.)
>1 CD;

Vision:
>7+ EXE; (Move, ???)
>Distorted Data; (CData29)
>>
No. 287611 ID: 676156

Since form follows function, I'm going to guess that these natives have some sort of burrowing capabilities.

Hm, I dunno, maybe we shouldn't worry about figuring them out and just worry about blowing them up. Let's make some more BWPs.
>>
No. 287615 ID: 07416a

>>287607
DESTRUUCCTIOOON! Also, work on getting a wall set up.
>>
No. 287616 ID: 259738

Have the BCP build something with the large brown.
>>
No. 287637 ID: 8c73c8

BCP 1 go mess with that 2x2x1 brown, then green.
BMP 2 2b 3b keep building the ditch longer,
3a 3c make another BWP each. 1 escort the BCP
>>
No. 287744 ID: 3cc098
File 129989712797.png - (79.52KB , 512x512 , CA010.png )
287744

Everything has completed, or at least, started to begin completion in the construction zone of the Brown class building. 1 has brought over the initial building blocks for the structure, but it will still need 5 more green and 3 more brown data, along with two specialized data cores. The combat data core can be used for this purpose. Next turn the large green will turn into a construction zone as well. The ditch has extended, and indexed green data is being used as a wall in stacks of three.

BWP 1 and 2 have placed themselves over the ditch, and BWP 3 and 4 have been constructed.

There are a lot more of those worms then I had anticipated, and I'm afraid as to what this means. Those are EXEs, or EXEcution processes, and they... Well, execute processes. Not 'execute' as in run, but 'execute' as in, headless. But, that isn't the worst part, and for now, I will have to keep my comm-links quiet about some things, for your safety, and my own. Just know that you do not want them to accomplish their purpose.

I'll be trying to contact Core Command for a domain switch, there is no reason for either of us to be here if there is an EXE outbreak. It's just with so many processes running, I am having a hard time getting through their passive jamming. They are still just out of range, and you'll have to buy us some time. And by buy us some time I mean, destroy anything that gets in range of the BWPs.

Gained:
>2 BWP
>Brown Construction Zone; (G1/6, B1/4, 0/2 Datacore.)
>EXE; Basic Knowledge

Vision:
>25+ EXE
>>
No. 287746 ID: 07416a

>>287744
I ordered destruction, why was destruction not accomplished? Sortee out there and blow some shit up.
>>
No. 287749 ID: f6360f

>>287744
We really need more resources, if we are to either come up with a solution to the .exe problem in time or fend them off with our existing available units. Two BMPs should continue expanding the defensive ditch, and all the rest should move to harvest brown data and immediately use it to multiply. Once we have 12 BMPs, they should start bringing all available brown data to near the construction facility.

Hopefully we'll be able to get the resources quickly enough to make a difference and build more.
>>
No. 287750 ID: 8c73c8

>>287746
negative on that. they seem to be a swarmer class enemy. while our units are slow heavy hitters, we would kill a few but then they would overrun their position.

the BMP 3 near the top of the ditch is to continue build the ditch. both 2s and 1 are to fill the construction zone with the materials it needs.
the other two BMP 3s are to extend the ditch to blast area and then assist with construction.
BWPs 3 and 4 are to take position at the ditch on ether side of 1 and 2.
>>
No. 287754 ID: 07416a

>>287750
We have aoe attacks, if I interpreted it correctly.
>>
No. 287757 ID: 8c73c8

>>287754
yes, but we have no idea of the recharge time between shots. could fire and blow some up and the rest would rampage over the dead and get to the tanks before they can fire again.
>>
No. 287780 ID: 38cd5d
File 12999034416.png - (69.25KB , 512x512 , CA011.png )
287780

Green construction zone ready for resource allocation, Brown construction zone at max green data capacity, trench digging has continued, and BWPs have unleashed simulated hell against the incoming processes. But, the EXEs have proven themselves hardier then the RAM. Even trekking right through a power of 10 data abnormality. And there are more of them.

Brown construction needs for 1 to return to deliver the brown data and it also needs two data cores. You have already created one, a CD, which can be carried by a BMP and placed into the construction. It can take two different types, but it needs at least two to manifest the facility. The green construction only needs one of the data core types, but still needs to be stocked with green and brown data. I can't tell you which one will be more useful in this situation, and I apologize for holding off your BMP construction request. Digging the crude data ditch seemed like a more productive use of time at that current cycle, and all processes are standing by for new orders.

Vision:
>???-4 EXE
>>
No. 287782 ID: 28e94e

>>287780
Let's make as many combat units as possible, while improving the trench's defensive capabilities (would barricades be possible?).
>>
No. 287786 ID: f6360f

>>287780
We MUST get additional BMP units. More BMP units means both faster gathering of data and faster construction of defensive structures such as ditches and walls, and since they reproduce by splitting the earlier the make them the more valuable they are.

Direct the two BMPs at the west end of the ditch to harvest the brown data in the southwestern quadrant of our vision, quickly before the .exe's get to that region. They should immediately invest the data in creating more BMPs, which can in turn help them harvest the data faster and create still more BMPs. Allocate 50% of harvested brown data to BMP creation until that quadrant is depleted.
>>
No. 287789 ID: 07416a

>>287780
Create another CD. Complete the Death Tower.
>>
No. 287792 ID: 8c73c8

3bb make 2 CDs with nearby browns and spit them out so the 2s can get them.
>>
No. 287793 ID: f6360f

>>287792
The 2's can move over and make the CD's themselves. Those 3's have more important shit to be doing, like harvesting the browns from an area that will soon be overrun and thereby getting us the resources to build more things, instead of merely using up our available resources and then being .exe'd to death because we failed to expand like a pack of idiots.
>>
No. 287794 ID: 8c73c8

>>287793
fine fine. which strategy is better depends on what the buildings do. if one is a death-o-matic then yeah.
>>
No. 287823 ID: 25dce4
File 129992506755.png - (73.56KB , 512x512 , CA012.png )
287823

Everything is ramping up, User. I am having a hard time completing all of your tasks, so I worked on completing the ones that would potentially have the most effect. The EXEs are still coming strong, and even after that first attack, I am beginning to worry. If, and I don't mean, 'well, a little bit," I mean if, your unit is about to be attacked by the EXE, I high suggest you push the emergency USER Termination button.

I won't lie, this will end painfully, and probably deadly for you. But, as I said, these EXEs do more then just kill you, and I do not have the proper privileges to terminate you myself. Trust me, I would've done it long ago. You will have to do this if the time comes.

But, on a brighter note, two more BMPs have been created, the brown construction is waiting for 2 datacores, which have been created by the two BMP2s, and the craters created by the shells do in fact seem to be slowing the...

Oh, that isn't good. That isn't good at all. Seems like the natives weren’t too happy about you heartlessly annihilating the two gift bearers, and have come to exact revenge. Those... Are some big walkers...

>"USER, you seem to have a little... Bug problem! Hahaha, let us show you who you turned your back on. All beams, full."

...

User, are they mocking you right now? I would feel so foolish right now, if I were you.

Gained:
>2 BMPs;
>2 CDs;

Vision:
>3 HDD;
>3 GPU;
>1 CPU;
>???x2-6 EXE;
>>
No. 287831 ID: 8c73c8

3br and 3bbb make a CD each and put them in the construction.
and what the hell are the 2s doing all the way up there?
>>
No. 287855 ID: 07416a

>>287831
We don't need any more CDs, we just need to install them.
>>
No. 287888 ID: 8c73c8

>>287855
we have ONE cd, the brown needs 2 to work and the green needs 1. so we need a total of 3, we only have 1.
>>
No. 287889 ID: 259738

>>287888
We have three, two were just created.
Go install them.
>>
No. 287890 ID: 8c73c8

oh i see now. dang number coded units threw me off. yes install all CDs.
>>
No. 287992 ID: c5628c

>>287823
Tell the natives that we a have attacked the other two under false pretenses and failed to gather information quickly.

Also mention them about our monument.
>>
No. 287995 ID: 8c73c8

>>287992
yeah, say our translator was being stupid and gave us a false hostile ID, and we are willing to do anything as an apology.
>>
No. 288018 ID: fffe1e
File 130000008848.png - (113.94KB , 512x512 , CA013.png )
288018

Everything is coming along, User. Things are still looking very dire. The native processes are sure tearing up your domain with their extreme density laser weaponry. I'm sure that after this whole situation gets contained, they won't be expecting the fury of Orion.

>"Your A.I. isn't the sharpest tool in the proverbial shed, is it?"

Jokes on them, User, you are not an A.I.! Or, wait...

>"We're simply here to flex our muscle in front of the new owner of the Domain we've occupied for many cycles before you've even been considered an applicant to own your physical existence."

<Secure Comm-Link>
{
>USER #04220...k361, we've had reports of an EXE outbreak in this sub-quadrant and we've come to provide backup.
}
</>

This is just adorable. You've been addressed by your entire classification code. We now have the attention of the enti... Are you kidding me...

{{{Fatal Process Division 9 Detected}}}

You are just messing everything up. You know how I informed you about that termination button earlier? I'm simply rebringing it up for no real reason, other then the operations that are about to be conducted against your tiny domain if you don't get this situation under control.

The facility has been completed, with the use of 2 CDs, you've created a War Factory. I've preloaded a schematic I've 'acquired' from our blue 'friends.' It requires an amount of energy, green, and brown data. The energy can be created without a generator by applying BMPs to the job at a production of 3 per BMP. You'll need 12 energy, 12 green data, and 4 brown data.

>"User, please do not condone your A.I.'s activities, we do not take kindly to forced information 'sharing.'"

Gained:
>4 BMP;
>1 Warfactory;

Vision:
>3 BlkFnctn;
>>
No. 288026 ID: 8c73c8

all 3s in lower left pull back towards the user representation and bring the two loose browns and plug them into the green factory then swarm the warfactory and power it up with the 2s.
BWPs 1 2 3, move to the other side of 4 so you can hit the worms in that area.
>>
No. 288027 ID: f6360f

>>288026
One of the 3's in the lower left should harvest that last loose brown, too. As long as they're next to it anyway.

And two more of them should move left and harvest those other two browns. We need more data to work with.

The rest of them can do what you said.
>>
No. 288037 ID: 676156

What the hell is this fatal process? What is going on here? Stop stealing data from the locals, AI. We don't want to alienate them. They're clearly more than capable of wiping us out.

I'm starting to wonder if we shouldn't trust the AI. What can we do about a malicious AI?
>>
No. 288062 ID: d66ba1
File 130002096848.png - (80.75KB , 512x512 , CA014.png )
288062

Everything is in overdrive, User. All the processes are running at max capacity, but I regret to inform you that BMP 3BBR has been lost to the oncoming... Measures I've employed to ensure both your, and my, survival. I can tell you are not going to be strong enough to push the button when the time comes, so it is up to me to pull out a little policy to make sure nothing happens to you. And, by extension, myself.

The process in construction is almost complete, if your ignorance can buy us just a little more time, we may be able to pull this one out of the bag. You know how lowest of tiers this entire domain stretch was? No, you do not, you did not explore, you did not move! This entire time, you didn't move your embodiment. Now, I don't think that's entirely the reason why we are in the situation we are in now. But, it could be one of the reasons why it is escalating so quickly.

No, don't worry, you don't have to move. Continue doing what you are doing. We have black functions to the north fighting to keep you alive. Oh, I still have not filled you in on exactly what these... EXEs do, things. You see, and I couldn't have that happen. They... Well, they render you a shell of what you once were. They literally attach to your manifestation... And, well, they attach to your physical body as well. And they rob your thoughts, and turn you into a husk, a drone for the swarm.

>"Chhk... Azure reporting in, situation getting out of hand. We can..."

Oops, did I? Oh, maybe.

And, did you know that when an EXE attaches to a process, those that control the swarm, control the process. I did this for you, User. A jump start, because you fumbled over the simple functions. Oh, that's not good.

<Secure Comm-Link>
{
>USER I will advise this situation has taken a turn for the worse, and we apologize for any inconveniences caused to you. Your continued support behind our next action is fully appreciated.
}
</>

Ha...


Vision:
>Class 9 EXE Mutation, EXTREME CAUTION.
>>
No. 288063 ID: d66ba1
File 130002099012.png - (96.08KB , 512x512 , CA015.png )
288063

Ha...

Vision:
>CONSOLE Class Carriers
>>
No. 288064 ID: d66ba1
File 130002102253.png - (101.63KB , 512x512 , CA016.png )
288064

Ha...



Vision:
>USER #04220...k361; Termination Locks Disengaged.
>>
No. 288065 ID: d66ba1
File 130002134451.png - (168.25KB , 512x512 , CA017.png )
288065

Fig. A: Standard EXE, tongue capable of drilling into a process and assuming control.

Fig. B: Mutated Strand of EXE, tongue capable of drilling into a process and assuming control.

Fig. C: Spines believed to make the process more painful, and permanent.

Fig. D: See Fig. C.

Core Command advises a strict no EXE tolerance, and any use of such processes will result in the immediate termination of all involved. It is the Core Command's stance not to use mind control for gain over the natural environment, and it is more ingenious to mingle with the indigenous population.

Again, in the case of EXEs being witnessed, contact Core Command immediately so full domain scan operations may commence at the smallest hint of an infestation.
>>
No. 288072 ID: 28e94e

What just happened I'm so confused
>>
No. 288085 ID: 8c73c8

no, moving would not of helped us in any way shape or form, and has a very high chance it would of made things far worse. if we went south, southeast or east we would of run into the EXE swarm earlier and we would of been defenseless. if we went north, northwest or west, we would of run into the mutated class nine. northeast is blocked by the raised area. meaning the only direction we could of hoped to go was southwest where the RAMs came from. so your assessment is false, or you simply thought wrong.

anyway, finish up whatever is in the war factory.
>>
No. 288333 ID: cc14ad
File 130015658151.png - (151.64KB , 512x512 , CA018.png )
288333

I think I stole the wrong thing.

Vision:
>Class 7 Threat: Widower; Semi-Extreme Caution Advised
>>
No. 288334 ID: cc14ad
File 130015667012.png - (62.41KB , 512x512 , CA019.png )
288334

Well, User, look at you, wielding your technological superiority so early in the simulation. Let me be the first to congratulate our new partnership.

>"Sapphire, we've gotten reports of a Widower in the proximity. Who authorized this deployment?"

>"Do... Not... Worry... Sir..."

It's so hard to emulate the native processes speech patterns. I need a little more practice it seems, even after all these cycles.

<Secure Comm-Link mode="Private" recipient="User"> {
>Thank the Command circuits you've been given the way out of this mess. Quick, take out t... }
>Link lost, attempting to reconnect, 3... 2...
>Connection failed, error unknown.

Oh no, User, what were they about to tell you? It must be all this interference from this stasis field I've been projecting. I know, quick, take out those Black Functions on the hill, and next cycle we can get rid of those pesky carriers, it's our only hope for survival! Do not worry about the EXEs for now, they don't pose any thre...
<<A.I. Override>>
Interface Restrictions Lost
<<A.I. Override>>
Data Restrictions Removed
<<A.I. Override>>
User Links Free

Gained:
>1 Widower; (Move, Attack.)
>>
No. 288340 ID: 46c430

>>288334
Fucking. Artificial. Intelligence.

Let's order the widower blast the fatal process EXE thing.
>>
No. 288341 ID: f6360f

>>288334
Widower kill the fatal process.

What the hell did he make the Widower out of? We need to get those resources again and build another one.
>>
No. 288342 ID: 8c73c8

all BWPs assist the black units against the EXE, blow up a trench in front of the thing.
widower, anti-air operations, shoot down the consoles.
>>
No. 288343 ID: 46c430

>>288342
No, don't take out the consoles, I think they're on our side!
>>
No. 288344 ID: 8c73c8

>>288343
nope. this author has a bad habit of not telling us things until we ask about it directly. i asked him and he said the carriers are going to reformat the whole place. meaning WIPE FUCKING EVERYTHING. we are part of everything.

oh and BMPS build a secondary trench behind the BWPs to try and slow the EXE down.
>>
No. 288347 ID: 46c430

>>288344
Oh. Um. ...Yeah, right then.
>>
No. 288349 ID: 46c430

I suppose we should also try moving our... Embodiment? Command center? The important looking red thingy.
>>
No. 288388 ID: 520a26
File 13001630365.png - (126.54KB , 512x512 , CA020.png )
288388

<Secure Comm-Link>
>User, we appreciate your cooperation with this entire thing. As you recieve this message your Adjunct has been removed from your control and placed into a secure location where it will be evaluated for any defects in the code.

Terminate.


>As a thank you, we've decided to make the process of wiping your domain a quick and easy one. We apologize for whatever side effects the application of this much magnetic energy may do to your personal being.

>...

>You... Shot at the carriers...
</>

<Secure Comm-Link mode="Private" recipient="User" caller="KTX42001">
>THIS IS A MISTAKE, USER. WE SEE THAT THE ADJUNCT HAS GOTTEN TO YOU, WITHOUT THE USE OF EXE MANIPULATION. WE REGRET TO INFORM YOU THAT THE FORMATION PROCESS IS STILL UNDERWAY. WE WILL MAKE YOUR LAST MOMENTS ALIVE FILL WITH INDESCRIBABLE PAIN.
</>
>>
No. 288389 ID: 520a26
File 130016306862.png - (237.41KB , 512x512 , CA021.png )
288389

<Secure Comm-Link>
>I apologize for my colleague's... Rash nature, but you've forced our hand. Your mind will be restructured according to our needs. Thank you.
</>
It's... Okay...

Vision:
>1 FORMAT Device.






Terminate.
>>
No. 288399 ID: 46c430

>>288389
(Was there a point to this quest?)
>>
No. 288406 ID: 07416a

>>288388
LOOK AT THE CONTEXT, PEOPLE. Gawd. Anyways, shoot the bullet!
>>
No. 288408 ID: 46c430

>>288406
This. Though it will surely not work. Bloody train wreck.
>>
No. 288437 ID: 00d3d5

>>288406
Confirmed.
Then send a message to the locals saying we've escaped the Adjunct for awhile and now its allies are trying to kill us.

...
Oh, wait.
>del format.* /y
>for %i in (tree) do path "%i"
>del format.* /y
>>
No. 288457 ID: bbd9f1
File 130017996133.png - (67.67KB , 512x512 , CA022.png )
288457

<Secure Comm-Link>
>What are you doing? Do not do that. Don't even think about doing that. We are monitoring your mind, and I can tell you are thinking about doing what I do not want you to do. So what you are thinking about, don't think about it, so you don't do it.
</>

<<Communications Removed>>

Well, looks like you've started quite a mess. You are going to have to clean it up, if you want to live, that is. As I understand it, you have no idea what is going on, nor do you know exactly what your little Widower is capable of. Do you know what happens when you shoot a bomb in the air? It still blows up.

How about instead of shooting that Format ordnance incoming to your location, you just grab it. This is a Class 7 processes, and it is under your control. It does things, for you.

It seems as if you weren't sure if you had free will before. Which you did, and now it's your time to use it to your advantage. I am unable to list the technical specifications of your Widower, but it would require a bale of paper. Try out a few things, might as well have your fun before they forcibly terminate your vital organs.


<<Communications Restored>>
<<Core Command Addresses Unknown>>

>"User! You are still alive? We saw the Consoles... Never mind that, our readings show a large stasis field around you, so we have to go the long way, but we'll be there to help in a brief moment. Hold out, User."

Gained:
>1 FORMAT Ordnance;
>>
No. 288478 ID: 8c73c8

okay, bring the thing down and let's see if we can use the BMPs to disarm it.
>>
No. 288479 ID: 8c73c8

oh and after it's down engage the EXE. maybe push it away instead of shooting it.
>>
No. 289041 ID: 1413e6

Well, if we can grab it and if it is not rigged to go off automatically after a certain time, we MIGHT be able to disarm it. This is the cooler option. On the other hand, we could simply use our tractor beam thing to throw the bomb as far away as possible. Either way, the result should be kickass.
>>
No. 289045 ID: 676156

Can that thing cut through jamming? Try that.
>>
No. 291465 ID: 5bae62
File 130129293409.gif - (148.44KB , 512x512 , CA023a.gif )
291465

||.gif||

BMP1, BMP2B, BMP3BBBB ponder their limitations.

BCP1 displays its lack of limitations for everyone to see.

>>
No. 291467 ID: 5bae62
File 130129298481.png - (52.47KB , 512x512 , CA024.png )
291467

I'm not going to baby you like Adjunct did, User. The things you requested have been done, other things you've request have not.

<<Ping?>>
...
<<Pong.>>

>"User, quick. The EXE has come into view. Continue to..."

<<Ping.>>
<<Ping.>>
<<Ping.>> <<Ping.>>

<<Pong?>>

The core command is pinging your location, and they are getting close; you better pull off quite a maneuver with those brand new TECK blocks you're removing from that, in fact, I can assist with that depending on if you want a new toy, or improvements on existing toy. The latter will require the completion of that green structure you've begun.

Gained:
>TECK Data; (EData8)
>>
No. 291468 ID: 07416a

>>291465
Green building is a go! It'd be nice to know which of the requested things have been done, though.

Also, purplebot is a sexy-ass bitch.
>>
No. 291470 ID: 8c73c8

well, was saying to use the same method they harvest brown data on it. anyway. looks like green building needs a few more green data to finish. and the trench can't really benefit from the BMPs up there anymore. so all BMPS by trench grab a stack of greens and haul ass to the green building and load it up.
>>
No. 291568 ID: 56dd0f
File 130135328361.png - (64.74KB , 512x512 , CA025.png )
291568

I guess I will have to hold your hand, even though I would've liked to assume you can handle this catastrophe on your own.

<<Ping>><<Ping>><<Ping>>

Some of the BMPs have been pulled back, BCP has removed another chunk of the FORMAT ordnance, and construction of the Field Research has been completed.

<<Ping>><<Ping>><<Ping>>

Core command doesn't appear to appreciate the fact that they seemingly 'forgot' the communications addresses. That's not all they forgot, and that's not all they'll remember when they successfully ping you, you might have to take action against that soon.

You'll have to fill that Field Research up with some of the data you have laying around. May I suggest using that TECK - Designation ELITE, and maybe some Distortion - Designation ADVANCED? It needs four of any type of data to operate an upgrade on a specific process in the field. There is an obvious choice, but I'll leave it up to you.

You can either go for the 2 TECK 2 Distortion, or wait another turn for 3 TECK 1 Distortion, or, if you feel you can hold out for another two turns, 4 TECK upgrade will have serious consequences for all who engage in angering you and your delicious processes.


<<Ping>><<Ping>><<Ping>>

Those pings are... Just getting so close, but they are using some weird searching patterns. I'm pretty sure only one of those sets of pings will reach you. If you can make a decision on which one, you might be able to create a shield against it, but I doubt you'll be able to provide adequate coverage with a non-directional shielding. This will also have to be done by the Widower, so it will no longer have a grip on the EXE. Please do choose carefully, User.

>"User! We're... Prepare... Only..."

Gained:
>1 Field Research Facility;

Vision:
>DRYICE Bulwark;
>>
No. 291569 ID: 56dd0f
File 130135330332.png - (225.47KB , 512x512 , CA026.png )
291569

Well, looks like those native processes are not as useless as I once thought they were. That wall will hold back the EXE, I believe, for a while, but I wouldn't base any decisions on the structural integrity of the native's palisades.
>>
No. 291579 ID: 8c73c8

if i had to guess i would say the bottom left pattern is the one looking. be ready for that one.
load the two teck we already have and have 2 BMPs standby with distortion in case we need the upgrade NOW instead of later. keep harvesting Teck.
>>
No. 291784 ID: b17f54
File 130146500402.png - (77.49KB , 512x512 , CA027.png )
291784

>"User, we are... With a large... Please do not... We again must... Do not..."

<<Ping.>><<Ping.>><<Ping.>>

The natives have another Bulwark initiated, which should provide a cycle or two to gather your thoughts, hopefully. Those pings are getting closer, but you don't have to worry about them pinging the minor processes, they are looking for you, so when you feel that it is time to take action to protect yourself, that's when you'll want to set up a jamming shield.

But even then, they will continue to search for you. They know you are in Orion, and they will organize a scorched domain campaign until your little red blob turns into a little red spla... Wait. User...


<<Ping.>><<Ping.>><<Ping.>>

>"User, do not... There... And..."

In fact, User, I may be able to get your out of here, but your current form is so gelatinous and useless, but, if you were to abstract again... Hmm, but you would need to maintain two states to ensure nothing happens up here, and...

<<Ping.>><<Ping.>><<Ping.>>

>"User, Widower... Two... DO NOT... EVER."

Never mind, that would ruin some things that I'm not yet ready to repair. You still have things to do here, User, before you even can consider leaving Orion. All of them involve the natives, though, so keep that in mind.
>>
No. 291790 ID: 07416a

>>291784
Start moving our red square into an already scanned area. Get other processes to push us around.
>>
No. 291794 ID: e02378

no no. install newly gotten teck into lab. and the two BMPs in the top right grab the two brown datas and install them into the Weapon Factory. as well as a bunch of green. widower, get near our representation and ready the jammer. most likely scan point is from south west.
>>
No. 292317 ID: 234030
File 130161742133.png - (85.84KB , 512x512 , CA028.png )
292317

<<Ping.>><<Ping>><<Ping>>
~Bwoamp.~
<<Ping.>>
~BWAOMAP!~

>"USER, WE AGAIN MUST INSIST YOU RESUM... Oh, pardon. The urgency of the situation clouded our better judgment then to shout at a User."

Good job not being totally useless, User. Of course this isn't the end of road, not even close. Protocol dictates they will attempt to send a scouting party to obtain visual address of your being. We'll worry about that when the time comes, as right now the EXE is still not dead, the natives are getting restless, and you've made no progress on abstracting anything!

>"User, we've been able to fully clear out our encampment from the EXE infestation. Sadly there have been reports from the other factions and they have not had similar results. I dare not say it because of your vagrant A.I., but something different happened around here. Also, please free our trapped processes. We need those."

The BMPs have filled up the war factory with plenty of Green data, but there is still the loose Distorted and Green that can be thrown in to increase production possibilities, and I believe there might be some brown hidden away in one of the BMPs. We can begin experimental operations immediately without these data types, or we can wait to load the extras lying around, or we can wait to see how a TECK handles inside of the factory.

>"We might've judged you a little too harshly previously, User. While we've been here on Orion much longer then you have, our allies in Cancer and our 'acquaintances' in Lapine have lived in peace with their User counterparts for grand-cycles, and we are prepared to do the same.

User, quit conversing with the rabble. The last thing I need you to do is grow a heart in a situation like this. Did I say grow, a heart? How ironic. Your termination locks are released. Double-irony, I believe. Let me remind you how much is at stake. You've missed your window of opportunity to quit early and live again. Now you quit, you die. Forever.
>>
No. 292320 ID: e02378

throw in some green and distortion into the factory. load that fourth teck into the lab and let's see what happens.
>>
No. 292849 ID: 7fef20
File 130170984877.png - (161.64KB , 512x512 , CA029.png )
292849

The final TECK has been placed into the Field Research facility. I've made arrangements for the Widower to be upgraded. I will warn you, depending on which upgrades you choose, it might not come out as the same thing that went in. But, no matter what, it will be superior to what you have now. Those fools just handed over that TECK data, and now it's time to punish them. You have four upgrades to choose from, choose carefully, User.

Artificial Intelligence: Can think on it's own, has no personality but will attempt to optimize actions based on limitations to server the User.

Protocol Cannon: A very powerful weapon capable of splitting the atoms that holds the code together. What ever it doesn't eliminate from the Disc, is horrible disfigured and mutated.

Multi-Process: Doubles amount of actions it can take per cycle. Some limitations based on actions exist.

Carrier: A bay for processes to be deployed from. In the absence of all processes, can be used as a storage for data.

Atomospheric Generation: Enables processes to operate outside the range of the domain. In this specific case, it creates a sphere of habitable air that processes are capable of operating in.

Flight: Gives the process simple flight.

Gatherer: The process can now remove and gather data. Comes with a cargo hold that can be synergized with Carrier Upgrade.

Data Splicer: A close ranged weapon capable of splitting processes into it's sub components.
>>
No. 292856 ID: 8c73c8

Carrier
Atomospheric Generation
Flight
Protocol Cannon
>>
No. 292884 ID: 1854db

Protocol Cannon, Multi-Process, Atmospheric Generation, Data Splicer.
>>
No. 292896 ID: 8c73c8

>>292884
if you are going for a pure combat load why get the atmo generator?
my design is a powerful relocation unit. everyone gets inside and we fly off to somewhere with more brown data and stuff.
>>
No. 292897 ID: 1854db

>>292896
Can it lift the User?
>>
No. 292898 ID: 8c73c8

>>292897
sure. it can lift anything that can fit in it. be kinda stupid to make cargo bay in something that can't move if the bay is full.
>>
No. 292900 ID: 07416a

>>292849
Multi process carrier gatherer flight. We must Strike The Earth. Also allows us to relocate big shit and set up remote mining camps. Seriously, a hero unit? Cool! An INDUSTRIAL hero unit? OP.
>>
No. 292910 ID: 8c73c8

>>292900
okay yeah, switching to vote on this.
>>
No. 292927 ID: 8c73c8

any BMPs with brown data concolodate it so you can make more BCPs which are to go and help the first one harvest the bomb.
>>
No. 292929 ID: 1854db

...guys, if we don't pick the cannon how are we gonna kill the giant EXE?

Suggesting we change Flight into Protocol Cannon.
>>
No. 293015 ID: 737853
File 130172560721.png - (189.66KB , 512x512 , CA030.png )
293015

Unknown Class, DUNGBEAT Aliased.

Massive industrial processes capable of sub-crust and crust massive data retrieval. Has large wings and a large process storage bay. Previous capabilities have been carried over in the form of the two high capacity distortion cannons.

Any User found in possession of such process will have their data mining privileges removed and their mental capacity examined to analyze how such a process was created. Mental capacity examinations are conducted out of body, with large molecular lasers to sever the physical connection. The pain will only last until the brain is unable to receive the neuron's pain signals, as the spinal cord will become a cauterized heap of singed matter. Hopefully your brain will be the first of it's kind to survive such a procedure.
>>
No. 293037 ID: 8c73c8

pffft, we are gonna die anyway so who cares!

DUNGBEAT, finish separating bomb remains into Teck and store it. then load up all of the other processes we have created as well as the buildings and the User Representation.

and can someone turn off the green stuff matrix thing? only thing under it at the moment are some smaller EXEs and the native process units. can just destroy the smaller EXEs easy.
>>
No. 293039 ID: 737853
File 130172817344.png - (42.64KB , 508x504 , CA031.png )
293039

As usual you perform an action which you have no idea of the consequences of what exactly this all means. You've... Created a unique process, you fleshy lump of meat and bone. But, I'm not here to judge, only here to take note of this and ponder why Adjunct was so lucky to acquire you as a User, and why Adjunct was so faulty to let this opportunity to slip through his fingers.

War Factory

Green: 32;
Brown: 2;
Distorted: 2;

Control:
Antenna: Basic control, proximity to control tower based.
A.I. Core: Can be fully automatonous.

Chassis:
Box: It's a box.
Tringular: Trinangular box.
Native: Bug theme based.
Slither: Worm theme based.

Mobility:
Wheel: It's a wheel.
Tread: It's what you've always had.
Walker: Simplified legs.
Wiggle: Similar to EXEs.
Wing: Very basic wings.

After the basic structure is selected, advanced options will open up to further customize the process. The locks can be unlocked with Distortion data as 1:1, or a sum of other data types. Each different selection has advantages and disadvantages based on what you choose.

Choose carefully.

If you have any special requests, ask me. I might be able to assist you in unlocking the correct slot. Please note the associated image is in grayscale and the author was too lazy to redo it in colour. The other pages implicated by the arrows don't contain anything but more locks.
>>
No. 293041 ID: 8c73c8

antenna, bug, wing.
idea: sub drones for the main unit.
>>
No. 293050 ID: 1854db

>>293041
Sub-drones would work better with an AI core. They would work to serve the DUNGBEAT's goals instead of requiring direct orders.
>>
No. 293052 ID: 737853

May I suggest the Hivemind Control?

If my records are correct, it'll be the Distortion, or 6 Green + 1 Brown.

>>
No. 293060 ID: 8c73c8

>>293052
let's use the distortion to get it. brown is a hard to get commodity at the moment.
>>
No. 293082 ID: 737853
File 130173628330.png - (108.68KB , 512x512 , CA032.png )
293082

Hivemind + Bug + Wing based process has been formulated. Please include as many of the following modules as you wish. The three red circles are simply there to show example attachment areas.

Shovel: Green/Brown harvesting
Pickaxe: Allows for crust data mining.
Bucket: Allows for the collection of static.
Truck(*): Allows for storage of data.
Hammer: Allows for the construction of Simple Facilities.
Nails: Available after Hammer, allows for construction of Advanced Facilities.

Small Armaments(*): Self-defense weaponry from pests.
Large Armaments(*): Combat ready weaponry for domain defense.
Explosive Capabilities: Equips the process with a small ordnance package. Can by synergized with other modules for creative actions.
Self Detonation(X): Loads the process with a large warhead capable of doing significant damage, but destroys the process during use.

Green locks are cheap to unlock, yellow and red follow the obvious pattern that is implied.

Green: 32;
Brown: 2;
Distorted: 1;

In this stage Distorted can be used to unlock any lock 1:1, OR, modify any module in a potentially unpredictable manner.

Current cost: 3 Green.
>>
No. 293085 ID: 8c73c8

let's see... since dungbeat can gather an assload of materials we need a way to use it.
truck, hammer, nails.
constructor swarm to use the insane stockpile dungbeat easily collects.

BUT i am curious about what is under the red lock to the right of nails. use a distortion to open it up. and let's see about opening up the green and yellow next to truck.
>>
No. 293091 ID: 07416a

>>293085
...What he said.
>>
No. 293103 ID: 737853
File 130174152589.gif - (17.28KB , 64x64 , CA033.gif )
293103

||.gif, for no reason.||

Cement Mixer: Available after Nails, allows for construction of Complex Facilities.
>>
No. 293104 ID: 8c73c8

in that i case i would like to upgrade.
two variant split.
hammer nails cement. constructor
truck truck truck. worker
both run on the same hive frequency
>>
No. 293137 ID: 1854db

>>293104
Do we even need something with Truck? Can't the DUNGBEAT store and deliver the data?
>>
No. 293191 ID: 8c73c8

>>293137
dungbeat has a material gatherer but no dropper.
>>
No. 293326 ID: 8c73c8

nevermind, change triple truck into truck, shovel pick.
>>
No. 293441 ID: 9bacb6
File 130182002432.png - (48.56KB , 512x512 , CA035.png )
293441

You've developed the plans for ALUs and Cu-Ts, these will be useful in conjunction with your DUNGBEAT. The more of them that are created the stronger their actions will become, both through their capacity for physical alteration of the domain, and also in mental abilities. Of course, I will assume that they are going to be bounded to the DUNGBEAT as they are created, but any time you want any of them to be associated with a separate process, be sure to inform me. Cu-T's actions are relatively simple to understand, so I'll skip over them. Just a quick thing: they can simply dig through the crust that is revealed from surface operations.

Total consumption is 9 Green to generate two separate patterns, and the two Distortion for unlocking technologies. Two brown have been used to create a BCP. It has made it's way over to begin deconstructing the FORMAT. It will take 4 cycles to completely disassemble it, with another turn to remove the structures and get their resources back.

ALT functions include creating the structures that you've seen here, except for the other four you hadn't discovered yet. Those fall under the 'basic' facilities category. To create a basic structure, data must be placed in a square 2x2 pattern where a large block of that type can be generated. This is followed through with another cycle of construction to create a facility base of that type. Data Core blocks can then be administered. Advanced and Complex can be constructed with 5x5 and 9x9 blocks respectively.

The DUNGBEAT can in fact cut through the stasis. But, as it is flying capable, and can simply fly a few blocks higher then the stasis field, if that is what you choose.


Gained:
>Widower + Flight + Gatherer + Carrier + Atomosphere Generation = DUNGBEAT
>Mud Wasp Mimic; (3G + War Factory==+1ALU)
>Worker Bee Mime; (3G + War Factory==+1 Cu-T)
>What's the Buzz?; (5G + War Factory==+1ALU+1Cu-T)
>1 BCP;
>>
No. 293442 ID: 9bacb6
File 130182009487.png - (131.29KB , 512x512 , CA034.png )
293442

And here are some diagrams of the processes formed. Nothing too complicated, disregard my awful handwriting simulators.
>>
No. 293444 ID: 8c73c8

since we do not plan on waiting around her for too long let's make like 2 ALUs who will dock with dungbeat for latter and make Cu-Ts until it's time to leave. so run "What's the Buzz?" twice and "Worker Bee Mime" until it's go time. BMPs are to load up some more green around the factory so it has a enough materials to work with. DUNGBEAT should put our representation into it's cargo bay, since that is the safest place we know of, then remove the stasis field on the lower left, native attack units are in that section and they can help us fight off the EXE. once they are freed dungbeat should then start loading up with green and distortion data but leave enough room for all current land based processes and buildings to fit.
>>
No. 293445 ID: 1854db

The DUNGBEAT should continue firing at the fatal process now while it does other things. It can multitask gathering and shooting right?
>>
No. 293448 ID: 5c5428

Retcon: Atomosphere Generation on the DUNGBEAT is actually supposed to be Multi-Process.

From this point on, two primary actions can be taken instead of one.

Sorry~

>>
No. 293698 ID: f57219
File 130188659713.png - (69.63KB , 512x512 , CA036.png )
293698

ALU, Cu-T have been created, 2 TECK and 27 green have been placed into DUNGBEAT, and DUNGBEAT has cleared some stasis to free the native processes and multi-processed to attack the mutated EXE. It has also freed 3BBR.

>"User, thank you for freeing our processes."

Well, that was quite unenthusiastic.
>>
No. 293713 ID: 8c73c8

ask natives for assist fire against EXE. BMPs and Cu-t harvest the freed distortion data and load into dungbeat. dungbeat multi-process use tractor beam to hold the EXE in place and shoot it. load F-R with greens and target BWP1 with it, just to see what happens
>>
No. 293719 ID: 1854db

Oh hey the mutated EXE broke through the barrier and we're all going to die. What a surprise.

Put up another barrier?
>>
No. 294028 ID: 19fadd
File 130198868996.png - (67.31KB , 512x512 , CA037.png )
294028

Cosmetic upgrade in progress for BWP1, please choose four of the eight to administer to the exterior of the process.
>>
No. 294030 ID: 8c73c8

huh, so 4 greens = decal. interesting. let's give it some lightning. then continue with the rest of
>>293713
>>
No. 294031 ID: d3dfb8

>>294028
Adorable tiny deer pinup
>>
No. 294032 ID: f6360f

>>294028
Sweet shades, skull motif. Combine appropriately. No opinion on the remaining cosmetic upgrades.
>>
No. 294062 ID: 07416a

>>294028
Skull with MASSIVE TEETH on fire with SWEET SHADES
>>
No. 294068 ID: 00d3d5

Flaming skull with shades.
Also deer pinup.
>>
No. 294301 ID: 988b56
File 130207184676.png - (145.82KB , 512x513 , CA038.png )
294301

BWP2 doesn't very much care for the paint job.
BWP3 thinks it is both humorous and well done.
BWP4 doesn't reply, just cyber-blushes furiously.

The other processes are unable to understand a sub-classification's decals enough to provide pseudo-emotional insight of preferences toward it.

Gained:
>Ace Biker Tiny Deer Paint Theme;
>>
No. 294302 ID: 988b56
File 130207186274.png - (77.83KB , 512x512 , CA039.png )
294302

DUNGBEAT Supplies:
45 Green
3 Brown
4 TECK
9 Distorted


User, everything is speeding up at an acceptable pace. Three more turns until the FORMAT is fully disassembled and placed into the DUNGBEAT's cargo. The natives are quick to assist us with the mutated EXE, although they are providing 0 support in this endeavor. The weaker the EXE gets, the more able it is to resist the tractor beam's push. The ditch and pillars in place will help, a bit, with slowing it down, but according to my projections this plan isn't working.

>"User, our scouts have gotten a glimpse at your newest process, the large industrial beetle one, and we would like to extend our gratitude for showing us such a magnificent construct. We very much appreciate that it is made with an insectoid base, and evolved directly from a Widower. A process for destruction turned into a process for creation! It's a wonderful thought to even consider, and we would love to see how it works."

Gained:
>1 ALU;
>1 Cu-t;
>Friendly reputation with Orion Natives;
>>
No. 294305 ID: 8c73c8

hmm... guess halt fireing weapons on it so it can't gain more resistance to the beam and double process tractor it. do we have any more browns anywhere to make a another BCP? if so then do that to make last harvest needed sooner. inform natives that their unit's beams are too small to add enough push. they should flee while it is still being held back or if one of their units is able to, can it assist in harvesting the TECK.
anything that can be built entirely out of greens that can slow it down? even just a HUGE green block. yeah a 5x5 blank block of green would probably stop it pretty well. all building units that can assist with that should start making it where the BWPs are.
>>
No. 294313 ID: 1854db

Why don't we just push it into the stasis?

Also let's start building more military units. We're going to want to uncover the swarm eventually.
>>
No. 294317 ID: 8c73c8

>>294313
hahaha, didn't think of that. throw it sideways into the stasis.
>>
No. 294363 ID: 9da1d2

>>294305
I am so confused about what we can do. Any chance we can get a summary of what we can do so far?

Seems like best course is to build another BCP, harvest the TECK and evacuate.

Keep producing the 'What's the Buzz?' build and set them to build some last-ditch fortifications as well as loading the Dungbeat (priority is those last brown resources up north). I assume that since the worker bugs are airborne they can also fly alongside the Dungbeat rather than taking up carrier space.
[Return] [Entire Thread] [Last 50 posts] [Last 100 posts]

Delete post []
Password  
Report post
Reason