• Last Seen: 6 yrs ago
  • Old Guild Username: Kelsiven
  • Joined: 12 yrs ago
  • Posts: 966 (0.21 / day)
  • VMs: 0
  • Username history
    1. The Wanderer 12 yrs ago

Status

User has no status, yet

Bio

User has no bio, yet

Most Recent Posts

code name so secret no one knows, even the people that know it dont know it
Danke! Why do I have an ominous feeling about this whole situation though?
Instaurabo
Upon entering the armory, Instaurabo immediately located the slightly taller, but much more sturdily built battlebot. He only nodded when the other spoke of the other model, following it. His eyes focused on the abnormally moving limb, called a ‘leg’ by humans. Star silently sent a command to his internal processors. Analyze and identify problem. Immediately data began scrolling down his sensors, showing measurements in his sight, including the very angles the limb was moving at. Analysis Complete. Possible reasons for malfunction are... -Loss/Inconsistent pneumatic pressure -Loss/Inconsistent power -Faulty Circuitry -Water infiltration -Broken Joint -Broken Servo -Broken Bearing ... Instaurabo immediately stopped going through the data readout when they located the other bot. ‘Jack’ removed some armor plating on his left leg. Within was a mess of wires and some cracked circuitry. Immediately, the computers began re-analysis of the issue. Analysis Complete. The list has been narrowed to... -Loss/Inconsistent power -Faulty Circuitry Offer more detailed list under each section? Instaurabo had already begun disassembling the dead model’s leg, his tool morphing at an impressive rate, the pieces seeming to come off in his hands as easily as a human might take apart a puzzle. He selected several pieces of circuitry and removed some longer pieces of wire, ignoring the fact that not all the wire had belonged to this original system. “I AM CUTTING OFF THE POWER SUPPLY TO YOUR LEG. THIS IS A PLANNED PROCEDURE.” It was a programmed feature in his system- in the past less intelligent bots had been known to destroy engineers mid-job, observing loss of power similar to any other attack and responding in kind. Instaurabo moved quickly, carefully removing the older circuitry and cataloging it in his system as he did, next removing any worn, exposed, or faulty wiring. He reached back and slipped the cords of the Battery Pack built into his kit, calibrating the appropriate charge. Methodically he went through, testing connection points with small bursts of electricity- this caused the mechanical limb to jerk, kick, and turn. At various points, upon finding an irregularity in the movement, Star would take his dissembler, carefully adjusting various switches and screws, applying lubricant were necessary. Finally satisfied, he replaced both the charging cords and removed the welding pen, carefully soldering in the individual connections from recalled memory and his newly updated data banks. He once again went through the process of testing for each section that required new circuitry as he installed the new chips, and once satisfied carefully bundled the cords neatly according to purpose and grouping, using discarded wire as ties. The final thing he did was reconnect the circuits to Jack’s main system, allowing him renewed access to power and control of that leg. Saving and Compiling notes of procedure... “I WOULD ADVISE IMMEDIATE TESTING, AS THERE IS A .23903% CHANCE OF CALIBRATION ERROR.” Instaurabo went back to the helmet of the dead model, disassembling it. He knew exactly what he was looking for- it was simple, a memory storage model used universally among the humans for storing data- and used universally among robots for storing smaller static programs. It was located within the sound processing unit, as expected. Raising a hand to his own head, Instaurabo twisted his fingers precisely, pressing, and then sliding a small section of his headpiece sideways, exposing several slots. He plucked out a similar storage module, about the size of a fingernail, and slid the newer one into place, discarding the old one without a glance. Fingers once again moved in a practiced motion, relocking the plate. Functioning Audio Projection module detected. Switching control from System Speakers. Vocabulary database expanded. “Better.” His new voice had become more similar to Jack’s, though not quite the same. More human would be an accurate statement. “This facility hasn’t shown any sign of life, robotic or otherwise, besides us. I have already had the computers run scans on the building. My primary directive has not altered. I am to locate and repair friendlies in any manner possible.” Instaurabo tilted his head slightly. “However, friendly is undefined, and I have no area of assignment. My directive is vague as well. I believe I possess a basic understanding of humanity however. They seem to focus primarily on survival. I doubt that our creators would have caused their own destruction unless it ensured the further survival of the specie.” His processors focused momentarily on the weaponry possessed by the other bot. “I identify you as friendly, mainly based upon the lack of ‘shots fired’. However, my own function was not designed for combat duties, nor solo traveling. I request permission to join your squadron as combat engineer until such a point that a humanoid can re-assume control.” [POWER TO COMPUTE: Scan Jack and his equipment for further malfunctions.]
Power to Compute! How successfully can his leg be repaired with a slightly different model design and proper tools? @Warbozz
Instaurabo
Directive. That is what he was missing. Instaraubo had been processing what actions he should take, but was overwhelmed. Literally. His primary function was to repair and redesign damaged technology... Whereas parts of the building itself were torn apart. The large generators alone were enough to drive his processors crazy, his eyes kept wanting to target individual parts, and then list their functions, and then list possible replacements, etc etc. For each and every piece of trashed technology a red outline and alert were plagueing him and his computations. “STANDBY RECOGNITION AND IDENTIFICATIONS REPAIR FUNCTIONS 223 TO 432124. ACTIVATE ON REQUEST.” Affirmative. Recognition and Identification functions active on inquiry mode only. If his audio projection had been working, a very human sigh would have escaped the robot. There was a faint crackle, and the worn computer’s voice spoke again. Alert. The Repair center has been activated, sensors identify humanoid shaped droid. It is currently broadcasting on the emergency frequency. Just then, his internal radio spoke into Instaurabo’s ear. Or rather, it ran the data through the same converter that transfered actual sound into data that his processors could understand. It was pretty much the same as hearing it. "This IU MK-5 number 34829. Nicknamed 'Jack' broadcasting on immediate emergency frequency. If you can hear...respond immediately." “COMPUTER. POWER AND CONNECT COM SYSTEM TO REPAIR CENTER.” Affirmative. Power and communications opened between generator room and repair center. “MK-5. THIS IS INSTAURABO, NICKNAMED ‘STAR’. I REQUEST YOUR CURRENT STATUS AND DIRECTIVE.” Star paused. Humans would find his vocal projection harsh and displeasing. It was unfortunate that his software for vocalization was out of date, he would have to fix this. Another radio frequency came through his system. ”K-9 Unit, Mk. 1, CERBERUS responds. I am tracing your location, state the nature of your emergency, IU MK-5.” The computer crackled as the speaker picked up in the armory. ”This is Jack. I am located at the armory. I have just finished grabbing what I could. My primary and only directive is to survive. You said you are an engineer unit. My left left is suffering damaged circuitry at the knee joint...can you fix it?” “THIS IS STAR. AFFIRMATIVE. I AM CAPABLE OF ADVANCED REPAIRS. GRANTED RESOURCES. ARE ANY OTHER ROBOTS OR HUMANS WITHIN YOUR VICINITY?” ”I have received communications from an unknown robot. My scanners have not been able to detect any viable ‘life’ signatures. Do you know what has happened here?” “NO INFORMATION AVAILABLE. MY REACTIVATION WAS INITIATED WITHIN THE LAST TWENTY-FOUR HOURS. WHAT IS YOUR BUILD AND DESIGN PURPOSE?” ”I was designed to provide vital combat support to allied infantry and carry ammunition to other squads during the war. You stated you were an engineer. What extent of damage can you repair?” Instaurabo stood and quickly replaced his gear within the appropriate storage slots. He requested the location of the armory from the computers and set out after ordering the computer to continue to relay his words through intercom. “MY PARAMETERS STATE SPECIFICALLY TO REPAIR ANY AND ALL DAMAGE TO ‘WORKING’ CONDITION. WORKING DEFINED AS FUNCTIONING IN ORIGINAL CAPACITY. HOWEVER, I RESERVE THAT LACK OF RESOURCES WILL RESTRICT THE QUALITY OF REPAIRS. I RECOMMEND YOU LOCATE A SIMILAR MODEL TO YOURSELF IF CIRCUITRY IS YOUR MALFUNCTION. ” ”I have located a similar model. Its function and purpose were the same as mine. It is not the same version but simply an older model. Are you capable of using its circuitry to repair mine?” “STAND BY. TESTING AND MANUAL FITTING MAY BE REQUIRED. PLEASE SECURE YOUR CURRENT POSITION. I WILL COME TO YOU.” ”Please move with urgency. I may be peaceful but it is possible something hostile has also picked up on your transmission.” Instaurabo froze for a split second at that last message. He asked the computer to close the local communications and moved at a jog towards the armory. His processors hadn’t come up with that possibility, he was designed for war, but not for battle. A sad miscalculation.
I'll toss you a PM then
BKburke, in the mood for a bit of collab radio conversation?
Yo, @Warbozz does the base computer tell me of Jack's Location?
What ever helps the rp. Its up to the gm though.
I love collaboration posts. TitanPad is an excellent resource.
Sweet. Haven't used Titan, but I have used Piratepad and like three others xD
Pathfinder was last on thirteen hours ago. It looks more like inconvenient timezone to me than anything else- Also, how do you guys feel like collaborative posts?
© 2007-2026
BBCode Cheatsheet