Faction A Tisket a Tasket, A Green and Yellow Basket

[M33P]

I N T R O

It is a period of rebuilding for the FIRST ORDER. For the rest of the galaxy it means little
but for the DROIDS of the FIRST ORDER it means endless hours of repairs, updates, and
modifications... .... ...
-

Natasi Fortan | @FIRST ORDER DROIDS
​

Beep boop MREAOOOWWWW. Noise filled the abandoned corridor, a violent burst of steam erupting from an opened wall panel as sparks began to spray. A sharp hydraulic hiss sounded as the corridor lighting shifted red, doors on either end sealing with a solidifying thud. MEEEEEEEEP. Another flurry of beeps and whirs escaped the limited vocalizer aboard a small MSE-6 series droid careened down the polished floor of the FIV Erebus. M33P had been transferred almost a full month ago but it never seemed like its days, his days, ever got any shorter. From a power coupling malfunction aft of the ISD II to a ghost glitch in the turbolift system the FIV Erebus was absolutely the most bug infested ship he'd seen. Or at least, been assigned - he wasn't exactly seeing in the conventional sense. With a rapid squeak of wheels against the pristine deck plating he zoomed back towards the site of the expulsion of steam and gas, a small sensor probe popping up from the small boxy frame.


OXYGEN LEVELS: DEPRECIATED
NITROGEN LEVELS: ABOVE RECOMMENDED
C02 LEVELS: ABOVE SAFE LEVELS
TEMPERATURE: 49.2C
CONCLUSION: UNSAFE FOR HUMAN OCCUPANCY
ACTION: REQUEST ADDITIONAL DROID SUPPORT
ENCRYPTION METHOD: 01000010 01001001 01001110 01000001 01010010 01011001
>DECRYPTION METHOD: 01000001 01010011 01000011 01001001 01001001 00101111 01010101 01001110 01001001 01000011 01001111 01000100 01000101

TRANSMISSION: 01010000 01010010 01001001 01001111 01010010 01001001 01010100 01011001 00100000 01001111 01001110 01000101 00100000 01010010 01000101 01010001 01010101 01000101 01010011 01010100 00101110 00100000 01010100 01001111 01011000 01001001 01001110 01010011 00100000 01000100 01000101 01010100 01000101 01000011 01010100 01000101 01000100 00100000 01001001 01001110 00100000 01000001 01000110 01010100 00100000 01010011 01000101 01000011 01010100 01001001 01001111 01001110 00100000 01000001 01010101 01010010 01000101 01001011 00100000 01010100 01001000 01010010 01000101 01000101 00100000 01000010 01000101 01010011 01001000 00101110 00100000 01000011 01000001 01010011 01000011 01000001 01000100 01000101 00100000 01001100 01001001 01001011 01000101 01001100 01011001 00101110 00100000 01010100 01000001 01010011 01001011 01010011 00100000 01010010 01000101 01010001 01010101 01001001 01010010 01000101 01000100 00100000 00101101 00100000 00110001 00101110 00100000 01010011 01000101 01000001 01001100 00100000 01001100 01000101 01000001 01001011 00101110 00100000 00110010 00101110 00100000 01000101 01011000 01000001 01001101 01001001 01001110 01000101 00100000 01010011 01001111 01010101 01010010 01000011 01000101 00101110 00100000 00110011 00101110 00100000 01000011 01001111 01001110 01000110 01001001 01010010 01001101 00100000 01001110 01001111 00100000 01010101 01010000 01010011 01010100 01010010 01000101 01000001 01001101 00100000 01001001 01010011 01010011 01010101 01000101 01010011 00100000 01000001 01010100 00100000 01010010 01000101 01000001 01000011 01010100 01001111 01010010 00101110 00100000 01000001 01001100 01001100 00100000 01000001 01010110 01000001 01001001 01001100 01000001 01000010 01001100 01000101 00100000 01010101 01001110 01001001 01010100 01010011 00100000 01010010 01000101 01010011 01010000 01001111 01001110 01000100 00101110

 

[K-0K0]

[SDr] VERSION_7;DAT. 235//K-0K0
DISPLAY.DATA//113M-e
sensors=active; data-uplink=;active; operation-status=active;
function=security; permissions=enforcement; combat-mode=allowed;
interaction-disposition="pleasant";
[FUNC_STATE//_A3]
▶ LOCATION: FIV EREBUS
▶ OBJ: ASSIST WITH REPAIRS​

The corridor in which K-0K0 patrolled was secure. With scanners and sensors active, the KX-series droid walked with thumps of metallic limbs on deck plating, as it continued in the task assigned it. A collection of background processes were active within the data center of the droid, uplinks to the First Order infonet and security sectors aboard the FIV Erebus, which continually shared information between them; it allowed a never-ending state of awareness of a multitude of statuses within K-0K0's patrol area, including updates to those commands, such as the request for assistance that was received over the comm network...

PRIORITY ONE REQUEST. TOXINS DETECTED IN AFT SECTION AUREK THREE BESH. CASCADE LIKELY. TASKS REQUIRED - 1. SEAL LEAK. 2. EXAMINE SOURCE. 3. CONFIRM NO UPSTREAM ISSUES AT REACTOR. ALL AVAILABLE UNITS RESPOND.

It seemed the Erebus had yet another malfunction that was detrimental to organic sentients - like so many things. And while not programmed to have an opinion on the matter one way or the other, were K-0K0 to be asked to actualize a response to the state of the vessel, it would be presented as 'temperamental and in need of replacement'. But the droid was a servant, in service unquestionably, and simply responded to the request command that was forwarded to it.

COMMAND UPDATE:
▶ ASSIST WITH REPAIR REQUEST IN SECTION {AUREK THREE BESH};
▶ SUB-OBJ=DETERMINE IF DAMAGE WAS {ACCIDENTAL} OR {INTENTIONAL};​

With a flash of blue-tinted optics, K-0K0 turned on the spot and began to walk in the direction of the assignment. There was a surprised sound from a pair of Stormtroopers, who the droid cut off with the sudden and abrupt turn, to which one of the troopers called out after the KX-series model:

<"Hey, watch it, tin can!">

"This unit apologizes," K-0K0 replied in its vocalized tone, as it turned to regard the Stormtrooper - and his designation - without pause. "It did not intend to disrupt your already-delayed patrol movements, and this unit is clearly at fault. It would add helpfully: were you on schedule, such a poor interaction between us might have been avoided. Good day."

<"Wh-wait-huh?"> The Stormtrooper did a double-take, but the rest of his words were lost, as K-0K0 rounded the passage corner. <"Damned droids...">

It did not take K-0K0 long to reach the aft section of the vessel. Merely five minutes. Perfectly within reasonable traversal protocols. And when the tall KX-series droid entered the sealed area of the starship, it began to process the situation with the sensors built into its chassis. Toxins were present, though the cause was unknown, as K-0K0 looked for the droid that had made the assistance request... and saw the MSE-6 type droid.

"Greetings, MSE-Six model," K-0K0 said, as blinking optics indicated the receiving of updated data. "This unit has been assigned to assist with repairs, as required, where your model is incapable of doing so. Namely, this unit will handle whatever you cannot reach. Which is everything, above you and around you, beyond a single foot in distance by design."

And were the security droid ordered to give an opinion about the MSE-6 type droids generally, it would have presented 'ineffective and redundant'. But K-0K0 had no thoughts on the matter, it was simply there to perform a task and prevent death to organic lifeforms on the vessel...

M33P​

 

[BB-10R2]

the blessed bartoo​

How times had changed for BB-10R2.

No one had called him Bartoo in nigh-on a decade, now. It had been as long since he'd shaken a cocktail for a master to whom he had been assigned. In fact, it has been as long since he was assigned to one specific person. He'd been stuck in the maintenance pool since the Battle of Bakura. But as the First Order's advancement in technology meant that the ships he had been required to assist piloting on were no longer in service. There wasn't much active duty use for an astromech like BB-10R2, and so he was relegated to the wrench-jockeys.

Lo, the mighty had fallen.

The automated work assignment flashed a signal to BB-10R2, who processed the request before he transmitted an acknowledgment and rocked off his charging cradle, wheeling his way out of the mechanical pool ant into the corridor. Luckily for obsolete droids like BB-10R2, there would always be a place for droids like him as long as there were environments too dangerous for sentients to go -- like the one that BB-10R2 was heading for now.

He arrived a few minutes later and beeped a greeting at the droids that had already gathered there, following it with a status update and a request for a task.

K-0K0 | M33P

 

[M33P]

"Greetings, MSE-Six model," K-0K0 said, as blinking optics indicated the receiving of updated data. "This unit has been assigned to assist with repairs, as required, where your model is incapable of doing so. Namely, this unit will handle whatever you cannot reach. Which is everything, above you and around you, beyond a single foot in distance by design."

In the short amount of time it had taken to transmit and receive responses from other responding droid M33P had managed to isolate the source of the problem. At least, the immediate problem. A power relay had blown, the stored electrical power causing a small explosion which in turn had cracked an environmental conduit. With a whir and a chirp, a small arm protruded from the frame of the MSE droid, at it's tip - a small nozzle. A burst of sealing foam shot forth and covered the cracked conduit followed by a slow hiss as the foam went to work. At least now the leak of CO2 into the corridor had been staved but there was still plenty to be done.

>Transmission: Salutations K Zero K Zero. The environmental conduit has now been sealed however manual manipulation of several levers will be required at about a height of two meters. Please adjust levers, One, Seven, Three, Eight, all to position One. That is, perpendicular to the flow indicated by the markings on each conduit.

It was one downfall of his model, short wheels, limited storage space, for anything remotely above ground level he was useless - or mostly anyway. The one benefit the MSE-Series droids did have were the narrow channels designed for them which cut through bulkheads and allowed rear-of-panel access where larger more cumbersome droids... M33P briefly sent a sensor wave towards K Zero K Zero... wouldn't fit without removing panels or cutting into the bulkhead. Only a few feet into the small MSE channel the Mouse Droid's sensors picked up something... a sound of.. rolling? Frantically M33P scanned its memory, comparing the sound profile to its stored data. After a few microseconds he'd found it.

Bweeeeeep! A loud chirp echoed as he shot out into the corridor, an excited hum vibrating his entire hull.

>Transmission: BARTOOOOOOO!!!!

K-0K0 | BB-10R2 ​

 

[K-0K0]

[SDr] VERSION_7;DAT. 235//K-0K0
DISPLAY.DATA//113M-e
sensors=active; data-uplink=;active; operation-status=active;
function=security; permissions=enforcement; combat-mode=allowed;
interaction-disposition="pleasant";
[FUNC_STATE//_A3]
▶ LOCATION: FIV EREBUS
▶ OBJ: ASSIST WITH REPAIRS​

K-0K0 watched with no interest or thought, as the small droid went about completing tasks at a lower height level, as was its primary purpose with design of its schematics. Granted there were access panels to get within the bulkheads, but the tall droid still felt overall the design was flawed. Yet, it didn't think on it for long. There was little else to do, save wait, so the KX-series droid began to run a background diagnostic check, flushed its temporary cache and began rebuilding data stores to categorically improve on performance down to the millionth of a second.

Transmission: Salutations K Zero K Zero. The environmental conduit has now been sealed however manual manipulation of several levers will be required at about a height of two meters. Please adjust levers, One, Seven, Three, Eight, all to position One. That is, perpendicular to the flow indicated by the markings on each conduit.

And K-0K0 finished the background processes. It acknowledged the tasks required, right around the moment a shrill beep sounded, followed by the arrival of a BB-series model droid. Those were a little more tolerable, far more modern in design and function, though still maintained some drawbacks to schematic limitations. Nonetheless, while the two small droids - who appeared to know one another - interacted, K-0K0 stepped forward and unlatched the piping panel with some rotations of the hands, similar to a drill.

"Yes, hello," K-0K0 said in response to the BB droids greeting. "If you will excuse this unit, it is in the process of using it's considerable programming in security, threat analysis, hand-to-hand combat techniques and patrol optimization... to adjust levers. So this unit requests the due silence to process appropriately--"

Within three seconds, K-0K0's hands had pushed the levers to the appropriate positions.

"--and done. As you were."

With a careful look of the scanners, K-0K0 began to enact its secondary objective. To determine if the levers had fallen into that position, or been shifted, either mistakenly or purposefully. It would be difficult to surmise if it had been on purpose, of course, but it felt confident in being able to discover the first part of the query from command.

"According to sensory data of operating the levers, with this units long reaching and superior limbs, they maintain solid and uninterrupted threading," K-0K0 said as its blue-tinted optics flickered. "It is this units analysis that the levers were intentionally lowered into dangerous positions. It is now evident after data reporting that the issue needs resolving."

COMMAND UPDATE:

▶ CONTINUE TO ASSIST WITH REPAIR REQUEST IN SECTION {AUREK THREE BESH};

▶ SUB-OBJ=DETERMINE WHO OR WHAT TURNED THE LEVERS {INTENTIONALLY};

▶ SUB-OBJ-2=REQUEST SUBORDINATES IN AREA TO ASSIST IN PROBLEM SOLVING {MSE-6 and BB-10R2};​

K-0K0 turned to the other droids, before it inclined its head in a vaguely human mannerism:

"MSE-Six model, BB-Ten model, you are both being requested to assist this unit in determining what caused this purposeful lever placement, and to bring he, she it, they or them to the brig. This unit would ask other, more capable models, but command has told this unit to use you."

With a mechanical version of a sigh, K-0K0 turned optics back to the open panel and pointed.

"We must begin with trace scans for DNA. BB-TenArtoo, are you able to perform this task for organic residue?"

M33P | BB-10R2​

 

[BB-10R2]

BB10-R2's eye-dome rotated in place between K-0K0 and M33P several times, photoreceptor totally dilated as if he could somehow absorb more of the context of the situation by widening the scope of visual light. Bartoo had spent some time with M33P in the past and had always found the droid adequate. The commentary from unit K-0K0 suggested that perhaps the taller droid did not share Bartoo's assessment of his erstwhile partner. Bartoo made a blatting sound under his metaphorical breath, then wheeled forward, shifting his photoreceptors.

He beeped a few times at K-0K0, acknowledging the request. DECLARATIVE STATEMENT:: THIS BB-10 UNIT IS EQUIPPED TO ASSIST WITH THIS TASK. STAND BY.

Bartoo wheeled over towards the levers, extending his multitool arm to collect whatever DNA matter he could find. The arm retreated into his body and he began to translate the DNA into electronic data. DECLARATIVE STATEMENT:: THIS BB-10 UNIT MUST INTERFACE WITH FIV EREBUS' SECURED DATABASE. STAND BY.

Bartoo rounded back towards the entryway, found the interface and jacked in. He chittered to himself as he scanned the database, then made a rude sound. DECLARATIVE STATEMENT:: THIS BB-10 UNIT MAY REQUIRE MAINTENANCE; QUERY RESULTS ARE ILLOGICAL. TWO SPECIMENS LOCATED, HOWEVER, BOTH PERSONNEL ARE MARKED DECEASED IN AN ACCIDENT EARLIER THIS MONTH. TRANSMITTING DATA NOW. PLEASE ADVISE.