Star Wars - DRK-1X and its Mistress

[shadowbloodmoon]

Comparing the data with what is coming in to the navicomputer, X sees that the two seem to match up. Apparently, the first leg of the trip will involve just flying to the outskirts of the cluster. This will take about three days, if the calculations are correct. The fourth day will be spent receiving new transmissions from the lead escort destroyer heading through the cluster and relaying from the control in the center of the area. Then the last moments will be spent in the sensor net before going into the complex proper.

Four responds as you are compiling the message to Derek. "Well, I'd much prefer if we didn't have to come up with our own way out. I do however think we should come up with a backup plan if Ears is compromised while we are on mission. I'll try to keep an eye on those transmissions. I'm guessing that someone else is going to be wanting those coordinates, but the explosives don't make sense. That is unless.. Hold on."

Four doesn't continue for some time. Your current access tells you however that the ship is almost ready for lift off. A communication between the freighter captain and the Star Destroyer commander has begun again.


"Commander, this is the Nerevar. We're clear for egress."

"Copy, Nerevar. Coordinates have been successfully downloaded. Once you achieve orbit, prepare to release control to remote system."

"Will do, Commander. Anything else?"

"No. Just do as you're told."

"As you wish."


The transmission ends and then ground control is contacted. X determines that this is the best time to send its burst to Derek.


"Control, this is Nerevar. We have launch confirmation. Prepare to release magnetics."

"Roger, Nerevar. Weather favorabl....<static>. Out."

"Say again, Control. We lost you there."

"Condition green, you're good to go."

"Copy Control. Nerevar out."


X feels the ship lurch as the magnetic clamps that hold the ship down while the repulsors fire are released. The external vid-feeds show the landing pad clear of any debris that may have remained after the brief firefight with the prisoner-slaves. The clamps have retreated into their housing and the ship begins to slowly rise. You can also feel the valves and hatches to the outside closing and sealing while the life-support system starts to switch over to internal air.

Going through the various monitors, you can see the entirety of the ship, all save for directly behind the engines. This would seem like a prime spot to hide, except for the engine wash. There are some spots though that, unless someone with extremely acute sense were watching, they would miss anything smaller than say, a fighter, that might happen to be lurking there. As it is, all the X can see outside the ship is the slowly vanishing clouds and the darkness of space.

Just in the distance, a speck of light slowly becomes triangle shaped. This must be one of the Star Destroyers Derek mentioned. The other must have already gone ahead.

Four finally sends another message. "No turning back now."

***

Derek watches as the freighter lifts off from the surface of Hurven Seven, confirming its trajectory with the information that DRK-1X had sent him in a brief burst. Not too far from the freighter is one of the Star Destroyers, the other having already left.




[sblock=OOC] Four days total, the first leg is the longest, the rest will be micro jumps through the cluster. Oh and 300 XP. [/sblock]

 

[Ambrus]

As the freighter lifts off and the crew focus their attention on the task of maneuvering up the the planet's atmosphere DRK-1X, alone in the aft storage compartment, takes advantage of the opportunity to slice into the ship's sensor array sub-system. Largely ignoring the majority of the flow of data being accumulated by most of the Nerevar's sensors, the probot focuses its Code on tapping into the data-feed of the single aft port proximity detector. 1X creates a simple program (Computer Use +14, taking 10). which would cause the sensor to refrain from registering any objects which remained in its field of detection. Only objects or particles which first passed through the field of detection of a neighboring sensor would register and be recorded in the freighter's sensor logs. Objects, or a small ship, which approached the freighter but that remained in that sensor's field of detection without deviation would thereby remain effectively invisible to the crew of the Nerevar.

The probot cautiously buries the program deep into the relevant sensor's dedicated sub-processor. DRK-1X then carefully checks its cherished Code work while continuing to monitor the sensor's unfiltered data-feed to verify that the Ari's Sorrow is indeed where it's supposed to be lest it be required to make some hasty changes to the sensor logs if it weren't.

******

Derek listens to DRK-1X's brief binary message disguised as static, allowing his internal comlink to decrypt the missive. The human replica droid swings around in the pilot's chair and begins keying the navigational data into the nav-computer as he processes his upcoming hyperspace jump (Astrogation +5). Derek monitors the freighter's ascent through the planet's atmosphere while he verifies the computer's computations.[sblock=OOC]Thanks for the xp! Out of curiosity, do you recall the last time you gave me xp? I'm curious to know what the 300 points covers. Also, does Derek get the same amount?

The Commander's mention of the freighter having to relinquish flight control to the larger ship sounds to me like they'll be establishing up a fairly substantial computer network between the two ships over a comlink channel. If so it occurs to me that 1X might be able to use its connection to the freighter's computer to slice remotely into the Star Destroyer's systems. Does that make sense? If so, 1X might be able to modify that ship's sensor's too, and possibly learn something of Dofina's fate. Are either of the Star Destroyers here one of those to which Dofina was brought after her capture? What would be the DC to breach a Star Destroyer's computer network?[/sblock]

 

[shadowbloodmoon]

With X monitoring the now modified proximity sensor, Derek is able to easily slip inside the envelop that the little probot has created for the fighter that Derek is flying. The HRD realizes that precision flying will be required for the trip, but it has little worry as to its possiblity, given directions from his counterpart.

[sblock=OOC]Umm... You know, I'd have to look again to see when I gave it to you last time. I do know it's been a while. The 300XP for now covers all the stuff for the planet Hurven Seven. To be honest though, I haven't really thought through how I want to do Derek's growth. I mean he is technically a separate character now, so giving him separate Xp could work, but also I could consider him a cohort that you play too. I think we'll stick with the same Xp for both for now. So yeah, he gets 300xp too.

What you are proposing makes sense, but even for such a talented droid such as X, would be difficult. However, that being said, R2D2 was able to hack the first Death Star quite easily, so.. there you go. Since the Empire is somewhat competent in its current form, accessing the Star Destroyer's computer systems is DC30. Difficult, but not impossible if X takes its time.

Neither destroyer matches the markings of the one that left with Dofina...

Anything else you want either to do in flight, you can mention now, otherwise I'm going to fast forward to the arrival at the outskirts of the sensor net.
[/sblock]

 

[Ambrus]

OOC: I searched through our recovered in-game posts and found the last time you awarded DRK-1X experience points; it was following its escape of the burning settlement on Dantooine just after its battle with Vader's probe droid and its first conversation with Four in disguise. So all in all, 1X hasn't gotten any xp for its explorations of the bio-lab, its shopping trip on the space station in the Dantooine system, its creation of Derek or for Four's kidnapping. It's been a good little while. I'd hope that single-handedly killing three über-rancors would be worth a few points.

For Derek's xp, I'd just award it its own xp based on whatever it personally does. Up until they reached the Hurven system both droids had the same experiences. Since they've split up though DRK-1X has infiltrated an imperial compound and stowed aboard a freighter. Derek, on the other hand, took a side trip to the pirate's space station to refuel the Ari's Sorrow while avoiding an imperial inspection. Award xp however you see fit; whatever you decide is fine with me.

As usual I do have a few pet projects planned for the three days of the trip. The first thing 1X intends to do is proceed with its plan to slice the Star Destroyer's native computer network via the freighter's remote computer link-up. It'll remain very cautious by using a circuitous route through the network and take its time so as to avoid alerting anyone to its intrusion. It's primary aim is to modifying the capital ship's sensors ASAP the same way it did the freighter's; to give the ship an effective blind-spot. It's second goal is to search the Destroyer's computer core for any data it has pertaining to Dofina and her whereabouts. Lastly, and it may indeed be a long shot, but during its time in the Destroyer's network 1X will try to locate a droid somewhere on the capital ship who is physically plugged into the network and, if possible, attempt to reprogram it remotely. DRK-1X's aim isn't to create 1X-3, but it wouldn't mind reprogramming a droid to serve as its sleeper agent; a simple mouse droid or a random maintenance astromech would be sufficient. It'd want the droid to keep performing its regular duties but also be ready and willing to serve 1X remotely as an sleeper agent if ever 1X needs some help aboard the Star Destroyer; perhaps during the probot's escape from the cluster. It may be a pie in the sky idea but 1X plenty of time to kill during the next few days.

1X's other significant project is to reprogram itself with either some craft or repair skill ranks and use the spare parts and tools in the storage bay to create six remote receivers it can hook up to the detonators it has acquired. If it can't find the kind of parts it needs 1X will sneak back into the hub and swipe the detonators' original receivers and modify those back in the storage bay. If possible 1X will even try to, at best, improvise little housings for each bomb or, at worst, simply wrap each matched pair tightly in the equivalent of duck-tape. 1X's aim is to end up with six lightweight little bombs that it can carry together in a bundle and detonate separately from a distance via a preset comlink signal. Not yet sure what 1X might use them for, though they might prove crucial eventually. Hopefully the whole bundle won't weigh too much. If so 1X will probably try to hand off a few to Four.

Aside from that DRK-1X will periodically check the freighter's sensor logs to ensure that its subtle modification to the aft proximity sensor is continuing to work properly. It'll converse with Four on occasion via the network to discuss further plans as well as the issue of how they might increase their chances of getting "Ears" through the sensor net. At one point (or perhaps two) during the trip DRK-1X and Derek will have to shut down for an hour to regenerate. 1X will do its best to hide itself in a concealed and ideally out-of-reach location within the storage bay before doing so.

Any other free time it has 1X will spend meditating on its own Code and the upcoming difficulties it may encounter in the cluster. At its end, Derek will do much the same while monitoring the flight and the various inter-ship comlink transmissions. That's about it for me. You can narrate this stuff however you like or simply summarize the results; your call.

 

[shadowbloodmoon]

[sblock=OOC]You know, you're right. I could swear I gave you some before the asteroid base, but I can't find it. In that case, from the lab: 400xp. From the shopping spree: 200xp. From the asteroid base activity: 200xp. So another 800xp altogether, which by my calculations, should bring you to 4th Character Level.

For now, I'll stick with also awarding Derek the 300xp, I'll just have to adjust the calculations depending on his actions in situations where he isn't with X. No worries there.

I also went ahead and made sure that X 'touched up' both ships, unless you wanted to leave one of the escorts with the ability to see Derek...[/sblock]

DRK-1X, the most industrious probot the galaxy has ever seen, goes to work on its plans to rescue its Mistress, the forever in trouble Dofina. X knows that only at certain times will it be able to access the Star Destroyer through its communication link with the freighter, so it sets a chronometer to make sure that it is ready to perform its work when these times arrive.

In the interim, X busies itself making its makeshift bombs. It takes some time, but the detonators are premade to accept remote receivers, so the work is simple enough. It just well, takes time.

Four checks in every so often, mostly to confirm the status of Derek more than anything. Though she is interested in what X is doing, she is more concerned about the coming mission. She mentions something to the effect of once you are safely inside the complex, she plans to continue her masquerade as long as she can. She did mention that she had another mission to accomplish inside, but she was going to first wait to see if you could find any trace of Dofina's location inside the complex through their mainframe. Then you would set about actually getting her free.

When the time comes to do its work on the Star Destroyer, X wastes no time. Going for the virtual throat of the ship's systems, X makes its way inside the geometry of the warship's network. The difference between it and the freighter's is unsurprisingly vast. Where the freighter was easy to manipulate, X has to call on every bit of Code mastery secrets it knows and even make up new ones in order to remain undetected and gain access to the necessary part of the system it needs to alter the sensor cluster returns.

While it works, X sends a part of its code as a sprite to see if it can find anything relating to Dofina or her capture. Unfortunately, it is unable to find anything relating to either. It appears that this ship was actually just recently commisioned and so any records it has of activity are very new.

X finally manages to subvert the sensor cluster enough that instead of reporting a finding where Derek is flying the Sorrow, it instead shows a previous recording of nothing. The time elapse between the switch is so miniscule that only a droid could detect it.

X repeats the process on the other escort vessel, again finding nothing on Dofina, or much of anything else. X learns in its minimal time connected to the Imperial network that if any of the droids that are onboard the ship made contact with any user on the system, they relayed as much to the nearest control monitor nearby. If X were able to stop this electronic relay, it wouldn't have the ability to program the droid fast enough to convince it not to take other measures to alert the crew. At least, not in the time it has to work. If X had time actually aboard the vessel, that might change.

The ships rarely talk to each other during the trip, mostly to simply confirm positioning and status. It would seem the crew of the freighter has no love lost for the Imperial crew escorting them.

The time finally arrives when the three days are up. The fourth is spent with the three ships playing hopscotch through the massive cluster. Through the freighter's sensors, X notes that this place would indeed be dangerous if someone didn't know the route. The cluster is made up of black holes.

X focuses much of its time keeping Derek alert to any changes in the patterns of lfight necessary to remain with the convoy of ships and not get caught up in any of the rogue gravity waves that exist out here. X also notices something else. The transmitters that were installed in the freighter's core begin sending signals out. One of the other ships is sure to detect them if given the chance.

 

[Ambrus]

[sblock=OOC]Thanks for the xp! I actually leveled in a PBP game!!! I never thought this day would come. This has been the single longest, hardest earned level I've ever gotten in any RPG.

Now I'm not certain what to do about it. DRK-1X could take a level of soldier and gain four feats out of six which it could then replace with whatever feats it wants by reprogramming itself. Although it's legal by the RAW (and Jedi Counseling #22 clarifies the point as does JD Wiker's own website) I just wanted to swing it by you first since it seems a bit wonky to me. The addition of 1d10 vitality points and a +1 BAB is also pretty sweet. What are your thoughts on the matter? Also, how do you want to handle rolling for vitality?

Thanks for assuming 1X would slice the second Star Destroyer; I hadn't realized that they'd both be accessible. I figured only one of the ships would bother networking with the freighter to control it remotely.

DRK-1X would ask Four to clarify her intentions. Does she plan on staying in the cluster after 1X is ready to head back out? What exactly does she want to accomplish asside from rescuing Dofina?[/sblock]DRK-1X, detecting the transmissions emanating from the freighter's hub immediately emits its own jamming frequency as it quickly heads out the hatchway. Although curious who these saboteurs were working for, the probot sees no tactical advantage to drawing any further unwanted attention to the freighter on which it is hiding. Quickly scanning the area to ensure it is alone, 1X goes to work on the access panels; prying them off and and setting them down on the deck. Without any preamble or delicacy, the spherical black probe droid deploys its twin manipulator arms and begins tearing out the transmitters and data-slicing modules one by one. When finished DRK-1X quickly replaces the panels, gathers up the various devices and returns to the relative safety of its storage compartment to continue monitoring the voyage.

******

As the voyage progresses, Derek endeavours to thoroughly map the route he's taking through the hazardous area by conducting extensive scans of its dangerous stellar phenomena. As he compiles the data he carefully inputs it into the navigational computer so that, when the time comes, he'll be ready and able to backtrack through the area as quickly as it is safe.

 

[shadowbloodmoon]

[sblock=OOC]Seriously? How long have you been gaming on here? Of course, I can't say much myself, I've only leveled once and that's in Living ENWorld.

I usually like my players feeling like they've earned their xp and levels and I believe X has done that in spades.

As far as leveling goes though, I don't see a problem with the soldier or the reprogramming. You are a droid after all and as such, you are afforded some penalties as well as some bonuses to balance them. Such as the fact that you can't heal naturally.... It's up to the player to play the character they want and it's my job to challenge that character based on their abilities, no matter what they are. So in a nutshell, be my guest. As far as VP, let's just do the standard 3/4 maximum and round normally.

Four remains characteristically vague about her other mission, though she repeatedly emphasizes that it will not jeopardize rescuing Dofina. She does say that she plans on returning with you and Dofina however. And Derek of course.[/sblock]

X's excellently manufactured stealth abilities keep it from being detected by the few crew members that frequent this part of the ship as it transits the deadly cluster of fallen stars. Removing the data transceivers is a simple matter, as is returning to X's temporary shelter.

It isn't much longer until the freighter finally reaches its destination and the true test of X's Code mastery begins. Within an hour, all three, or rather, all four ships reach the outer range band of the sensor net.

***

Derek maps each and every gravity wave that his and the fighter's memory banks can hold. This information, Derek knows, will be key to not only the success of the mission, but also the safety of all those involved, including himself. Every spare electron was spent making sure the mapping was correct.

Soon, still in the shadow of the freighter, Derek notices that the sensor net is just ahead, as are the two Star Destroyers. Or rather three of them. He notices that the control ship for the sensor net is just ahead as well.

Derek also notices something else in the distance. At first, when looking at his sensors, it looks like an anomaly of sorts, perhaps a random gravity shadow. A closer look reveals that it is something else, and quite real. And quite large.

 

[Ambrus]

[sblock=OOC]I started PBP games right here on ENworld shortly before this campaign began, say about April of last year (this campaign started in May IRC). Since then I've joined, created characters for and played in 3 Star Wars campaigns, 3 D&D campaigns and an Iron Heroes game. Of those, yours is the only one still running; three fizzled out after less than a few dozen posts while the other two managed a few hundred before collapsing. Most ended because the GMs quit, for whatever reasons. Not only is your campaign the only one I've leveled in, but it also has the distinction of being the only PBP RPG in which combat has occurred and in which I've received experience points; any experience points. Why do you think I'm so appreciative of your effort and game mastering skill? Not only is your game challenging, true to the genre and action packed; best of all it's fun, rewarding and it keeps happening! Kudos to you!

Wow. Five feats really helps to round out a character. Stacking bonuses is fun.

DRK-1X will try to convey to Four that it is willing to help her to fullfil her goals, whatever they may be, as long as they don't interfere with rescuing Dofina. It'll most likely be able to go places and slice networks that she won't; it would seem to be her advantage to increase her chances of success by allowing 1X to help her if possible. Out of curiosity, did Four's personal journals contain any hint of what she might be planning? Recognisance? Sabotage? Terrorism? Assassination?[/sblock]DRK-1X witnesses the convoy's arrival at the detection-net through the freighter's long-range sensors. As expected, an timely influx of navigational directives makes its way through the telemetry link shared by the arriving vessels to the ore freighter's computer core. In response the massive vessel's breaking thrusters fire, causing the equipment and the bulkheads in DRK-1X's storage compartment to shake and creak loudly before settling.

The hovering probe droid, with its scomplink probe quietly spinning in the computer access port before it, pays the disturbance no mind. DRK-1X is busily projecting its consciousness across open space along the three arriving vessel's shared telemetry-link. It is frantically searching for a new avenue to appear along which it could travel to the distant control ship's computer core. Knowing that that vessel, along with the network of sensor satellites spanning the region, remain capable of detecting the Ari's Sorrow DRK-1X waits for it to contact the three arriving vessels and so join their telemetry link.

[sblock=OOC]If a telemetry link is established to the control-ship, DRK-1X will use the slicing techniques it's developed over the last few days of the trip to quickly try and give the control-ship a similar blind spot (Computer Use +20, taking 10). If possible it'll also attempt to gain some measure of control over the sensor-net satellites and either modify them as well or, at worst, identify their scanning procedures and communicate that information to Derek over its own short-range encrypted comlink to help him in his attempt to breach the network undetected.[/sblock]******

Derek, sits unmoving at the helm of the modified heavy hutt fighter, his dark brown human-like hands folded simply in his lap. His brown photoreceptors stare unblinking at the distant wedge-shaped control-ship and the many pinpoints of light of the network of detection satellites. A small panel at the back of his head stands ajar with a cable dangling from it, joining the droid directly to the fighter's computer core. Having executed hundreds of thousands of virtual simulations of his attempted penetration of the sensor net over the past few days, the human replica droid turns its full attention to its one and only real attempt. His Code is strong, and failure is unacceptable; Derek's mistress' fate lay in his success.

The human replica droid's heuristic processor teems with electrons as he studies the satellites' configuration through the vessel's sensors. Derek continues to wait patiently for his opportunity to occur; that moment when the freighter would enter the net and the distant satellites would focus their sensors on it (Pilot +15). Through its direct link, the HRD verifies one last time that the nav-computer is ready with a pre-programmed hyperspace trajectory out of the area should it fail in its attempt (Astrogation +16).

 

[shadowbloodmoon]

[sblock=OOC]Thanks for the kudos. I certainly hope I am able to continue this trend then.. Speaking of, I think it's about time for the rest of the crew to get their xp too. I know it's been a while for them as well.

Going over Four's journal only reveals snippets of what could possibly be her mission inside the complex. It constantly makes reference to something called "Peaceful Terror". Her conjecture as to what it is varies as much as her shapes. She goes from biological weapons to aggressive diplomatic tactics to 'some sort of Force power'. She also mentions someone named Bevel, but the relationship she describes with this person seems to change forms as much as she does.

While Four appreciates the offer of help, she says 'this is something I must do alone'. She won't discuss the matter further.
[/sblock]

If the two machine entities could sweat, they probably would. All their planning and simulated execution was over. Now was the moment of truth, the moment of triumph or defeat. To them, it was a matter of 1 or 0.


"Freighter, prepare for scan."
"Roger, control. Shutting down engines now."
"Copy, realigning sensor network. Scan begins in 5...4...3...2..."


Perhaps it was a misalignment, a miscalculation as it were. For a machine, such things were impossible. For a droid, there were no mistakes. Only 1s and 0s. So for these Imperials, these humans, to see through the deception should have been impossible. It should have never happened.

And it didn't. What did happen was even more bizarre. As the freighter and its shadowing fighter cleared the sensor net, a series of explosions behind the two ships indicated that the satellite sensors were being destroyed by some unknown force.


"Control, what in blazes is going on?"
"Standby freighter."
....
"Freighter, divert course to orbit station 27. Hold position there until further notified."
"Roger, control."


Between the two of them, both droids were able to somewhat piece together what was happening. One of the Star Destroyers was firing on the satellite network. X's line into that destroyer's network was cut, as all communications immediately shutdown from it when the firing began.

The ship never had a chance though. The combined firepower of the two other destroyers made short work of the once pristine Imperial vessel. It was uncertain who or what caused the mess, but one thing was for sure, the station would be on high alert for some time. This was going to make things difficult.

Derek finds a safe place temporarily to hide himself and the Sorrow and he and X share their analysis of what they are seeing through their sensors. Both get a full view of what Derek's sensors had picked up. There were three of them, each in varying stages of completion. The most complete looked like the skeletal structure of a large manufactured moon, easily 150km in diameter. The complex was connected to all three of these things, with fighter patrols, shuttlecraft and work ships flying everywhere.

Eventually, the freighter is told to dock and it does so. X notes that they intend on having it swept by troops before allowing anyone to disembark...

 

[Ambrus]

[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...

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? [/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.

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]