Star Wars - DRK-1X and its Mistress

[shadowbloodmoon]

[sblock=OOC]If you are interested, here is a video to help you get an idea of a Mk84 and what it does:

http://www.alexisparkinn.com/photogallery/Videos/2006-3-28_Close_encounter.avi

I found another, but the site links to X-rated stuff, so I'll refrain from posting it.

The layout shows that in the engineering section are two large bays that seem to be used for nothing more than storage for tools and replacement parts.

Lightsabers, due to their nature, automatically cauterize the wounds they cause. The very first Star Wars movie seems to contradict this when Obi-Wan removes Ponda Baba's arm, but for the most part, it has remained so. As far as we're concerned, it will cauterize any wounds caused.

As far as the destroyers go, they will go overwatch, meaning that one ship will be approximately one hour ahead of the freighter at all times until they reach their destination inside the cluster, so only at certain intervals will either of the destroyers be actually in the same space as the freighter. Assuming everything goes to plan that is.

Derek should be able to plot a path that follows within a similar time frame as the freighter, but out of sync with the destroyers. The only snag will be the end, when all four ships are in the same area. But that is an encounter for Derek to figure out.... [/sblock]

It isn't long before one of the crew makes their way into the main hub. He is dressed in dirty overalls and looks as if he hasn't seen a refresher in weeks. He looks to be human, but has a small coat of extremely fine fur covering his exposed skin. He first notices the body and rushes up to it, not registering the panels or the concealed probot near him.

Checking the body and determining its state, he goes to say something on his comlink, but a well timed burst from X causes nothing but static to emerge. Cursing, he stands to go and find the internal com panel...

 

[Ambrus]

[sblock=OOC]Darn. I was hoping it would be a maintenance droid rather than an organic technician. That would have proven easier to deal with I think. Gee. I've been mulling over what to do all day; it certainly wasn't an easy call. 1X will just cross its fingers and hope it chose wisely. [/sblock]Emitting the electrostatic pulse buys the concealed probot a few more precious seconds for its heuristic processor to work its way through its carefully refined improvisational problem solving algorithms. DRK-1X's targeting sensors lock onto the male as he pulls his hand away from his comlink and rises to step towards the wall panel. Millisecond by millisecond, trillions of electrons race through the droid's processor circuit pathways as it compares possible scenarios, their probable outcomes, and which would best serve its long term goal of reaching its Mistress.

Should the man be allowed to report the saboteur's death and summon help or should he be silenced immediately with a well targeted blaster bolt? Which outcome presented the greatest risk of detection and capture? Subduing the man would most likely keep the probot from being detected in the short term, but the technician would most likely be called upon or missed at some point during the upcoming hyperspace trip. DRK-1X could possibly perform the man's duties for a time to keep anyone from noticing his inactivity, but it seemed unlikely that the probot could avoid interacting with the crew completely for the several days the trip would last. If the technician were allowed to summon help others would likely arrive to investigate the body, its murder and the sabotage of the hub's systems. A close study of the scene would reveal the murderer's handprints around the body's neck along with his fingerprints and organic residue on the panels, components and the ventilation shaft leading out. Investigators would correctly conclude that an organic was responsible for the murder and sabotage; they wouldn't likely suspect or search the ship for a small probot left aboard. Considering the pressing schedule the freighter was expected to maintain, it was even possible that no official investigation could be organized and carried out before the freighter lifted off. DRK-1X could potentially remain aboard undetected...

Its heuristic processor having reached its volition threshold, DRK-1X watches the man as he crosses the small cabin and depresses the wall panel's comlink button. Trusting that the technician was sufficiently unnerved by the discovery of the murder and distracted by his comlink conversation, 1X slowly rises from its concealed position and silently floats forward. The probot carefully deploys its second manipulator arm and, coming to a stop before the six stacked permacrete detonators, cautiously begins gathering up the explosives while attempting to remain undetected (Hide +22, Move Silently +15, taking 10). Without wasting another moment, DRK-1X turns and silently floats through the hatchway from which the technician had emerged a moment ago. Heading aft, the black spherical probot makes its way cautiously towards the closest of the two storage bays.

 

[shadowbloodmoon]

[sblock=OOC]DRK-1X has fingers? I thought those were just manipulators.... It is a good thing that even though droids are oblivious to the Force, Lady Luck smiles on them just fine... [/sblock]

"Captain, I got a body down here. Looks like one of ours, but he doesn't look familiar."

"What killed him?"

"I can't tell. No blaster wounds as far as I can see."

"Blast it all. We don't have time for this. Check around, one of the prisoners probably got on board during the fight. I'll let control know and then send someone up to get the body."

"What if I find the killer?"

"Kill him."

"Yes, sir."

The man sighs, looking down at the body one more time. As DRK-1X is finishing discreetly gathering up the explosives, the man turns around quickly, looking to where the tiny droid was previously. Moving over to look, he sees nothing but the panels on the deck plating.

Not wanting to risk his own life looking for a dangerous man, the technician takes his time putting the panels back in place. X breathes an electronic sigh of relief as it continues its path towards the starboard storage room. As of yet, X hasn't seen any other crew members, but it can hear voices coming from below the ship. There is an open hatch somewhere near it.

Moving ever so cautiously, DRK-1X finally finds the doorway to the starboard storage room. It is closed and it appears the door is codelocked.

***

While Derek is patiently waiting for the freighter to lift off, his sensors again pick up the same ship that previously entered the atmosphere now exiting it on the same path as before. As soon as it is free of Hurven Seven's pull, it vanishes into hyperspace.

 

[Ambrus]

[sblock=OOC]Heh. The tech is replacing the panels and hasn't noticed the mysterious new components? Interesting.

Droids aren't oblivious to the force; they can observe its effects as readily as anyone. Since it can't be explained by science though, except for counting midichlorians, they're hard pressed to understand its functioning or replicate its effects.

You know, I should send you the DRK-1X entry from the New Essential Guide to Droids. It's interesting because it describes how they were designed in part using mechu-deru, the Sith's mechanical engineering art. The entry goes on to say: "A Sith probe droid can track a Force-user in much the way a nashtah follows the scent of blood, partly by scanning biological entities for the presence of midichlorians, and partly by surveying the environment for anomalous Force concentrations." "The probe droid uses this data to assemble a picture of an individual's Force aura, which appears in playback as a radiant blue nimbus." Pretty neat huh?

Beside who needs some psychic mumbo-jumbo when one has the power of the Code at its command? [/sblock]DRK-1X, its arms full of permacrete detonators, floats over to the storage bay hatch's lock. Assuming it has a computer port, 1X will deploy its scomplink probe and marry it to the port in an attempt to access its simple processor and bypass the lockout mechanism. (Computer Use +14)[sblock=OOC]If there is no port, 1X will instead used the keypad as a manual interface and attempt to use the knowledge it has gained from the freighter's obsolete computer to try circumventing the lockout. If it senses anyone approaching, 1X will endeavour to locate and reach a convenient out of the way hiding spot and wait. Any exhaust port, ventilation shaft or even a mass of conduits jutting out of the wall should be sufficient to offer the little 30 cm droid cover I would think. A spot out of reach and beyond a human's regular field of vision is ideal, say anywhere high up along a ceiling or over a doorway.[/sblock]******

Derek, puzzled about the odd ship idly begins computing its hyperspace transit locus and comparing it to the spatial scans of the area it had been conducting earlier in an attempt to determine its probable destination (Computer Use +14, Astrogation +5).

 

[shadowbloodmoon]

[sblock=ooc]You know, I have been putting off getting those books because they come out with a new one with every movie and still leave out stuff from the old books. But now you're making want to run out and get them again so I can make sure that I'm telling you proper, since most of my knowledge comes from the novels and comics. Especially since this droid book has some interesting takes on how a DRK works. Now how to put that ability into X's stats... That's okay, wait until March when the Saga edition of SWRPG comes out... [/sblock]

X inserts its scomplink into the access port and it immediately opens for the Code savvy droid. Inside, the illumination is low, but X can see numerous crates and piles of spare parts, tools and other equipment for the ship. As the door closes behind it, X can hear the voices of several people getting closer. They sound as if they are discussing the body that is in the control hub. They pass the storage room by and X is once again alone with its electroneural synapses.

***

Derek calculates what it can of the strange ship's trajectory. He has to triple check them, as it appears that unless it is a stop over point, the ship is headed for empty space. The nearest port would be weeks from where Derek's calculations show that the ship is going. He can't get an exact fix, but it is definately somewhere out on the Fringes.

 

[Ambrus]

[sblock=OOC]In hindsight it would probably have been best to use the Sith probe droid stats from the Dark side sourcebook as a starting point to create DRK-1X rather than the Dark eye stats from the A&EG. The A&EG proved to be rather wonky with many design errors; the DS sourcebook on the other hand presents a more balanced droid model I think. It's almost as if the two books were designed without one designer being aware that Maul's droids from Episode I had already been described in an existing SW sourcebook. Even the New Complete Guide to Droids seems to continue the confusion of the two RPG books since it goes on to describe the Sith Probe droid as being constructed by Maul based on ancient Sith designs (like in the DS book) while simultaneously listing the manufacturer as Arakyd Industries (like in the A&EG).

My best guess is that Arakyd based their Dark eye production model on the Sith probe droid during its alliance with the Emperor, perhaps at his behest, but weren't able to add the mechu-deru enhancements such as the force detection so only produced a simpler stripped down version of the Sith model for mass production. Since that's what DRK-1X is, I'd say that it wouldn't have the force sensing abilities unless Dofina or Dooku had the know how and inclination to have made the necessary modifications to 1X.

Also, the entry also indicates what all those little bits visible on the probot's chassis are supposed to be. For instance, the little knobby thing on the right side of the droid's chassis is the external mount for the Dark-eye's weapon; meaning that 1X should have its blaster visibly mounted on its exterior rather than hidden inside its dedicated compartment if you cared to be accurate. Would you like me to send you the page? I also don't mind if you'd want to retcon 1X or its stats or description for accuracy's sake.[/sblock]Alone in the storage compartment, DRK-1X floats around the room taking stock of the available parts and tools as well as to scan the nooks and crannies for various good place to hide itself and/or the permacrete detonators. Once it finds such a space the probot deposits its quickly gathered payload and then floats back to the door to connect its scomplink with the access port there.

DRK-1X reestablishes its interface with its virtual access node in the ship's computer and relocks the door to the chamber while it checks to see whether Four has tried communicating with it through the virtual node while it was disconnected. The spherical probe droid then attempts to access the internal comlink A/V feeds back in the hub to monitor the investigation underway there. The probot also cautiously resumes its efforts to access the ship's navigational logs in an attempt to learn what it can of the hyperspace route used during previous trips, the satellites and sensor net protecting the cluster, the imperial infrastructure in place within the cluster, the routes taken by the freighter through that region, the security procedures and protocols in use during previous voyages there and any other information that may help it to plan the next step of its mission.

 

[shadowbloodmoon]

[sblock=OOC]If you want to scan me the page, that would be cool, but I think I like the idea that you brought up of Arakyd producing scaled down versions of the original model, which is highly probable. They never go into too much detail about Arakyd, but if I ventured a guess, due to the fact that nearly all of the major units that Arakyd produces before and during the Empire's reign were in fact copies of Sith models, that perhaps one of Sidious' advisors is also the head of Arakyd or in a position to influence the design and creation of the droids. Between the DRKs, the ASPs, the ITs, the Vipers and the Probots, they are all based on ancient Sith designs.

Nonetheless, it brings up some interesting theories involving X's true origin and how Dofina came to possess it. As far as retconning the stats, I wouldn't worry about it. Remember you created it as a modified version that is also capable of modifying itself when the need arises. Considering its purpose, a visible blaster makes no sense, thus the job done to be able to conceal it as necessary.

Let me take a look at what the page says and then we'll go from there.[/sblock]

The storage room is a huge array of pieces and parts for the engineering section of the ship. From large thermal fusion couplings to the tiniest bolts, just about everything one could need to repair a ship of this type is available in here. Hydrospanners and fusion cutters and other such tools and their respective kits are also stored in here as well. If X didn't know any better, it would calculate that it would be possible to build an entire engine or two out of just what was in the room.

Because of all the stacked pieces and crates and shelves, there are plenty of places to find shelter from prying eyes. X finds a sutiable spot to deposit the explosives before moving back to the access port. So far, Four hasn't sent any more messages.

The soldiers looking into the death of the saboteur have determined that it was a prisoner and not a guard, but as of yet, have not determined who or what caused him to suddenly die. The officer in charge notes the bruising on his neck, but mentions that without further medical checking, it could have been anything. The other soldiers carry the body back to the exit hatchway and unceremoniously drop it out of the ship, then climb down after it.

The investigating officer then speaks with the technician that found the body. They talk for a few moments as the technician describes what he found and then the officer asks if the technician found anything out of place. The technician denies that he saw anything else out of the ordinary, mentioning that a guard must have killed the man before he could do any damage.

The officer then explains all of this to the captain, who is more incensed than before. However, his pressing schedule seems more important and the case is deemed closed.

Internal comm traffic has turned to final checks now and a message does finally arrive from Four. "All set?"

As the crew is finishing their work, X has time to go over some of the previous log entries in the navicomputer. Apparently, this ship mostly makes runs in quite a few asteroid fields throughout colonial space before heading further outrim and into the fringe area. Each time, it is completely inspected by crew commisoned outside of the ones that are actually at each station, as the log stamps have different markings than the ones that should appear according to the locations that are in the memory banks.

It would seem however, that the ship's logs only go back so far. The first being somewhere near Coruscant and that was only a few months ago. None of them indicate that it was ever in the location of the cluster.

 

[Ambrus]

The probot's scomplink probe spins slowly in the computer port as DRK-1X responds to Four's inquiry via its virtual access node. "I've removed six permacrete detonators installed by the saboteurs. There yet remains an assortment of data-slicing modules and transmitters left in the aft hub assembly however, which all appear to have escaped detection thus far. There is no data in the freighter's navigational logs pertaining to its previous trips to or from the cluster. Are you confidant about the intelligence your organization compiled in regards to this vessel's activities?"

The diminutive probe droid turns its attention away from the freighter's navigational logs and instead attempts to access the current flight plan; it was entirely possible that a new hyperspace jump program would be plotted and inputted into the nav-computer before liftoff.[sblock=OOC]Having read that Maul preferred to have his dark-eyes armed with poisoned flechette launchers I took that to mean that the ones we see in Episode I were in fact armed. I'd assumed that the droids' weaponry, whatever it happened to be, were stowed out of sight in internal compartments since I couldn't see anything on their spherical chassis that appeared to be a weapon. A bad assumption it would seem.[/sblock]

 

[shadowbloodmoon]

Four responds faster than she had been. "I think it's a little late to be asking that question, isn't it? If they haven't found those transmitters yet, they probably won't. At least until they actually start transmitting something. Look, we're about...wait...." It takes a few minutes for Four to continue. During that time, you notice that the navicomputer has started decompiling data being transmitted directly to it. "We're about to finish pre-flight checks, they should be transmitting the first leg to the navicomputer now. I'm going to guess that as soon as we're in flight, those transmitters are going to do their thing. I'm just not sure if we should jam them or not. The third player could be a hindrance or a help in this op."

[sblock=OOC]Sith are sneaky bastards aren't they? I got the scans, thank you. I expected a book like that to have a little more detail, such as processing speeds, nominal repulsor velocities, power output, etc... but oh well.... [/sblock]

 

[Ambrus]

DRK-1X begins processing the new navigational data, confirming that the freighter is indeed bound for the cluster. The silently hovering black spherical droid's scomplink probe suddenly begins spinning counterclockwise as 1X attempts to gain covert access to the freighter's communications antenna. Throughout the procedure the probot remains cautious of being detected and so follows a convoluted path through the sub-systems of the ship's electronic network while keeping watch for anti-slicing defenses and unauthorized-access alarms.

Meanwhile, DRK-1X continues to covertly relay text messages to and from Four's computer console on the bridge. "I am accessing and processing the navigational data now. I am also in the process of slicing a secure data buffer in the communications system so that, when ready, I will be able to transmit a brief encoded and encrypted summary of the freighter's projected flight path to Ears along with instructions. It remains entirely possible however, that he will be unable to follow the freighter due to the two escort vessels waiting in orbit. If that is the case we will have to arrange our own covert transport out of the cluster.

As to our unknown third party, considering the explosives the operatives left aboard I fear their interests may not complement ours at this time. The six data transmitters are set to broadcast on channels 189532.25, 683465.67, 376819.98, 781532.62, 386728.98, 312958.48 and 876493.67. I am monitoring those channels now; you may do so as well and jam them if your feel it prudent."[sblock=OOC]Assuming DRK-1X successfully processes the navigational data and gains temporary access to the freighter's communications antenna, it will use its own integrated comlink's encryption circuitry to encode a brief binary message intended for Derek. The probot will wait for a moment when the freighter's crew is busily using the transmitter and then quickly upload the encrypted data packet to the antenna's data buffer while subtlety modulating the transmission parameters of the antenna. If the procedure goes as planned, the encrypted binary data will sound like little more than a brief burst of accidental static in the middle of someone else's conversation; a pre-arranged signal that Derek is listening for. DRK-1X will then reset the antenna's transmission parameters while it erases its message from the antenna's data-buffer and likewise purges the freighter's relevant transmission logs to cover its own tracks.

The transmitted message is encrypted binary and describes the freighter's projected ascent course to orbit and beyond to its designated jump point while describing where its sensory blind-spot will be. The message also describes briefly what 1X has learned of the two Star Destroyers' projected course and escort procedure. There's also some new mission details, plans and contingencies that 1X has devised. Aside from being in binary and encrypted, the message's meaning is obfuscated with the liberal use of pre-determined codewords and spatial coordinates data based on seemingly incomprehensible units of measure. Also, since 1X knows how Derek thinks and what he would naturally assume unless informed otherwise, the message also contains poignant omissions that would likely confuse any other listeners. A few parts of the message however are delivered in simple unambiguous binary, such as a brief summary of the recent developments, some proposed plan changes and the com channels that the saboteurs are using. Ideally no one will notice or try to decrypt the transmission but if they do it will only confound them.

After its done with the transmission and covering up its tracks, 1X will proceed with attempting to carefully slice its way into the freighter's external sensor systems to go about setting up that blind spot.

BTW, what is the freighter's ETA at the cluster?[/sblock]