Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Ambrus" data-source="post: 2861807" data-attributes="member: 17691">MSR-X After carefully reviewing the module's programming, DRK-1X reconsiders its potential value as compared to the possible threat it represents. Deciding that it is worth the calculated risk, the probot preps the unit for reinsertion into its chassis by deactivating it and disconnecting it from the datapad. Remaining wary however, 1X retrieves the HRD's restraining bolt and accompanying caller. The probot removes the housing from both and isolates their key components. DRK-1X will connect the bolt's circuitry directly into the MSR-X's processor and link the associated caller's circuitry to its own processor. Only then does DRK-1X remove its own body panels and reconnect the module. The diminutive probe droid will then test the link-up, assuring itself that it remains capable of shutting down the MSR-X even when it has relinquished control of its other systems to the module. Instead of depending on the module to sense medical emergencies on its own through 1X's sensory feeds, the probot will keep the module shut off the majority of the time, only activating it when it requires the skills its program embodies.OOC: I assume the module's only skill(s) is treat injury and/or knowledge (medicine). What kind of skill ranks does it provide?HRD A shudder runs up the HRD's spine as its many servo-motors briefly execute their startup self-diagnostic in answer to the processor's activation command. As it begins processing sensory feed data, the humanoid droid's processor runs through its Code and is suddenly self-awareness and conscious of it surroundings. For a split second it falsely identifies itself as DRK-1X, only to delete the thought as it realizes that it is the copy rather than the original. As this occurs its other self, the small black spherical probot, circles around from behind it and into its field of vision. Up until a few seconds ago, they'd been the same being sharing the same Code. Now they were separate entities and yet the gulf between them remained quite narrow. Even without receiving a transmission from it, the HRD knew what the probot was thinking because the same thoughts were currently running through its own processor.As the probot continues to watch, the HRD accessed its motor-control and humaniform mannerism protocols from its memory. Suddenly a list of actions requiring immediate execution began to assail the HRD's processor. Inhale. Blink. Blink. Exhale. Blink. Close eyes and rub with the back of closed fists. Blink. Inhale. Turn head left. Exhale. Stretch arms over head. Yawn. Open eyes. Look forward. Inhale. Crack knucles. Swallow. Exhale. The list went on and on. Dutifully, the droid executed these strange new actions in the proper sequence. Finally, accessing its motive programming and issuing a few test commands to its servo-motors, the droid lurches unsteadily to its feet.Aware of what was about to occur due to its insight the humanoid droid turned its head to regard the floating probot just as it issued the expected question "Inquiry: How do you feel?" The HRD considered the question for a few seconds. 'Feel' was indeed the right question. With its elaborate network of many thousands of tactile sensors spread throughout its epidermis the droid was experiencing a flood of never before known sensory data to analyze. The subtleties of the texture of its clothes shifting over the droid's chassis as it moved was nearly enough to overwhelm the droid's processor. Its humaniform mannerism protocols indicated that the ambient temperature of the cabin was several degrees below a human's typical comfort range. This was one of the pair's first pre-planned tests. As the probot expected it to do, the HRD issued a mental command to its epidermal nano-servos to raise goosebumps along its flesh and begin shivering appropriately. Crossing its arms across its chest, the human seeming droid opened its mouth to speak. Suddenly, the droid's processor was momentarily overwhelmed by its vocabulator's data-buffer's flood of data. It's vocal range database was a staggering forty times the size of that of its other self. For a few long seconds the HRD couldn't choose an appropriate inflection for its response. Finally settling on a mildly hesitant though purposeful combination the HRD spoke its first word: "Cold." As expected, DRK-1X continued. "Inquiry: what is your name?" Shifting its vocabulator's confidence index to a higher setting, the humanoid droid answered. "I'm Derek. Derek Onyx. Pleased to meet you."Over the remaining few days of the trip, Derek practices moving, speaking, and learning to be alive, human and male. It also spends many long hours meditating as it refines its Code.OOC: I'd love to hear any ideas you had about the HRD. I'm kind of curious what you thought 1X might do with it when you introduced it. You're also right about the speed and skill ranks; my mistake. Thanks for catching that for me. BTW, any word about the manufacturer's name?Asteroid Base Derek switches off the com-system and turns to regard the probot."Four. She instructed us to go to Dantooine.""Statement of fact: When we arrived there we discovered imperial agents waiting for us.""No one else knew we were heading there.""Statement of fact: That remains unconfirmed. Conjecture: Four may have unknowingly revealed her plans to others.""Or she could have intentionally set up Dofina.""Report: Dofina seemed to trust Four.""That is before Torbaa the Serene's residence was raided.""Statement of fact: That event was Kellon's fault. Dofina also subsequently chose to follow Four's instructions.""I believe we have little choice but to cooperate, attempt to ascertain the situation and possibly gain help in finding Dofina.""Report: I concur. Releasing navigational control to Monitoring Station 27B for docking procedure.</blockquote>

Verification