Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!

Reply to thread

Message: <blockquote data-quote="Ambrus" data-source="post: 3014166" data-attributes="member: 17691">[sblock=OOC]H'okay... I have to admit, I didn't see that coming. Wow. I was all proud because I'd subverted an ore freighter; little did I know this rogue faction has successfully subverted a whole freakin Star Destroyer. Next time I want to play on their team... <img src="http://www.enworld.org/forum/images/smilies/nervous.png"  class="smilie" loading="lazy" alt=":heh:" title="Nervous Laugh    :heh:" data-shortname=":heh:" />Is the third Death Star featured in a novel or video game or did you add it in yourself? What will they call it I wonder... The Sphere of Fear? Planet Death? Giant Hurt Ball? The Deathticle? <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f61b.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":p" title="Stick out tongue    :p"  data-smilie="7"data-shortname=":p" /> [/sblock]The human replica droid watches the space-scape outside the cockpit window unexpectedly light up with the flare of exploding satellites and the three way barrage of capitol ship blaster fire. His neural network's emotive node is briefly overwhelmed by the sudden spike of fear, confusion, and panic. The emotive surge causes a brief program failure in Derek's motor control subsystems, leading to the droid's eyelids fluttering 17 times in a rapid-fire sequence. Although he'd executed a few thousand simulated scenarios in which unanticipated sabotage occurred during the mission, none of them had involved a fire-fight between tree imperial Star Destroyers.A split second later Derek's self-diagnostic programming corrects the motor-control anomaly as his heuristic processor races to find and initiate the optimal response to the situation. Through the fighter's viewport, the human replica droid sees the freighter a few kilometers away fire its breaking thrusters and come to a complete halt as instructed just past the line of exploding satellites. Derek, meanwhile, takes no such action; instead allowing his spacecraft to continue drifting along its original trajectory. As the fire-fight continues off in the distance, Derek intercepts the control ship's command to the freighter's captain to alter his course. He then watches as the lumbering freighter fires its sublight engines and begins slowly pulling away from the Ari's Sorrow.Through the Sorrow's external sensors the human replica droid monitors the slow approach of the drifting debri from the satellites which had exploded nearest to the Sorrow. The explosions had caused the debri to reach a faster velocity than the Sorrow and it would soon drift past the small fighter. As the battle begins to wind down over a dozen kilometers behind it, Derek waits for the proper moment to act. When he sees the largest pieces of the debri cross in front of the cockpit window, initiates a thought which causes the Sorrow's maneuvering thrusters to fire. Within a few moments the Sorrow has altered its course to match that of the debri and gained enough velocity to keep up with the field of warped and charred pieces of scrap metal. A final brief burst from the nose and tail thrusters sets the Ari's Sorrow to tumbling gently through the heart of the cluster; just one more innocuous piece of space junk to, hopefully, be ignored by the cluster's occupants.With no further need to expend energy or fuel for the foreseeable future, Derek shuts down the Ari's Sorrow's engines, artificial gravity generators, life support systems and even the cabin's lights. The human replica droid remains strapped into the pilot's chair with his heuristic processor connected directly to the Ari's Sorrow's sensors and communications systems. Closing his eyes, Derek focuses inwards on his Code as he begins analyzing the incoming sensor data and communications chatter. Now he would listen and wait...******DRK-1X monitors the battle outside by way of the freighter's sensors. Accessing the freighter's aft port proximity detector's unaltered data stream, the probot monitors the Ari's Sorrow as the freighter first stops and then changes course. Soon the small ship executes a minor course change and disappears admits a field of satellite debris. With the Ari's Sorrow safely hidden 1X's counterpart's current part of the mission was complete. It was now up to the diminutive probot to locate and reach their mistress, wherever she may be.Once it hears the order to change course through its link to the ship's communications system, DRK-1X turns its attention towards it's destination, orbit station 27. It would have to disembark there undetected and begin making its way through the empire's cluster infrastructure. Silently the probot's scomplink probe begins spinning in the computer access port as it accesses the freighter's sensors to begin scanning that installation. As it analyses the sensor data, DRK-1X busies itself with dismantling the virtual constructs it had created in the ship's computer core. It first undoes the modifications it had made to the aft port proximity detector. Before disengaging its direct link-up to Four's console, the probot sends the woman a final message: "Ears violet. I will soon be disengaging myself from this vessel's computer core and so am in the process of removing all traces of my slicing activities. I intend to disembark stealthily at orbit station 27 prior to the empire's imminent security sweep. If successful I will endeavour to contact you briefly via our encrypted comlinks using our prearranged codes. Please keep in mind that our comlinks all have only a 50 km broadcast range. Since the empire's infrastructure within the cluster is so large we risk loosing contact if we get too far apart. Eyes out."DRK-1X waits a few moments for a reply from Four before deleting its last message and dismantling its direct line hook-up to Four's console. In short order, the probot searches through the freighter's computer logs for any further sign pointing to its slicing activities and modifies or erases them as is appropriate (Computer Use +20).DRK-1X then retracts, folds and stowes its scomplink probe and busies itself with the physical signs of its presence within the storage compartment. The diminutive probot carefully replaces any tools and equipment it has used during its stay, as much as possible setting everything back the way it was before it first entered the room. 1X then gathers up the equipment pack it had prepared and carefully secures it to the rounded backside of its chassis. When ready, the black spherical droid floats towards the hatch to begin its egress from the freighter.[sblock=OOC]DRK-1X doesn't intend to wait for the imperials to begin their sweep before trying to leave, it hopes to leave the freighter first. I'm not certain what's involved yet though. When it docks is the freighter inside and landing bay with gravity and an atmosphere or is it simply floating in open space while tethered by an access port? 1X intends to leave by opening one of the aft ventilation ports. If the freighter is inside a bay then it shouldn't be too hard for 1X to simply float down and sneak off. If its open space outside though it becomes a little more problematic since 1X can't use its repulsorlift in zero-G. That's what 1X was scanning orbit station 27 for; so it knows what it'll need to do to escape.If it has to go out into open space my thought was that 1X could use some swiped tools from the storage bay to move around. Depending on how far it has to go 1X could possibly move along the exterior of the hull with a pair of hand-held magnets; something most likely available amongst the room's equipment. It could slowly make its way along the hull and then cross over to the station along the exterior of the connecting umbilical. It could then continue along the outside of the station until it finds an access port or can sneak through an open landing bay door. If for some reason that isn't feasible then it could resort to using a compressed gas canister, from say a welding torch of some sort, to slowly propel itself across open space to reach an access point on the station. Depending on what it'd need based on its scans, DRK-1X would have loaded up his pack appropriately. I'm just throwing out ideas based on an uncertain situation. Feel free to narrate it as you see fit based on my intentions and plans. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile    :)"  data-smilie="1"data-shortname=":)" />BTW, is the Destroyer to which Dofina was originally taken in the cluster? Is the imperial construction infrastructure of the cluster all physically connected together? Will 1X be able to reach all the various "stations" by itself or will it have to hitch rides from one part to the next?[/sblock]</blockquote>

Verification