A New Power - Rebel Group

R3-L7 beeps a quick aknowledgement and rolls off to look for the absent officer. Arlee's search of the room indicated in his analysis, seemingly a bunkroom, reveals little initially. However, as he switches through his different detection systems, he finds a slight electromagnetic signature emenating from undeneath the pillow on the topmost bunk. There he finds a small personal datapad with a label on the back reading: 2nd Lieutenant Triss Mason, Experimental Scanner Maintenance Technician.


ooc: sorry for the delay, have had connection woes

***
 
Last edited:

log in or register to remove this ad

R-LE-1 quickly locates the datapad under the pillow, flips it over in his hands to examine it curiously searching for any signs that it is more than it appears [Knowledge (technology) +13]. Assuming it is a simple datapad the patina stained droid reaches down to his hip, pulls out his flexible scomplink cable and plugs himself into the datapad to quickly review its file contents (Computer Use +16).

Having assimilated the pad's data, the patina stained droid disconnects itself once more, turns and walks out of the starboard bunkroom and heads back to the Deepscan's conn with the pad in hand. While stepping past Jaess R-LE-1 holds the datapad out for her to take without turning its head to look at her. "Another mysterious occurrence; apparently one of the imperial crew members who defected to the Alliance neglected to retrieve his personal datapad before disembarking. The datapad was also curiously overlooked by the Rebel technicians who were most likely ordered to search this vessel carefully upon docking with the Reliant."

Once back at the conn R-LE-1 will begin searching the Deepscan's computer core for the vessel's imperial log and any odd or unidentified programs or data files that may have been hidden electronically (Computer Use +16 taking 20) while waiting for the munitions to be loaded aboard.
 

Jaess puts her search on hold and takes the datapad, looking it over much like the LE unit did, searching for signs of tampering or security (Search +6) before opening it up and examining it to descern more information about its owner (Computer Use +6). She sits down on a crate as she looks it over, nodding to the LE unit but not ready to reply until she accesses the data herself.

OOC: Is it Imperial? I though Alliance at first, but your deductive skills put mine to shame, Ambrus. I tend to follow after what you're thinking unless it seems glaringly wrong. So what's the deal with the datapad, Angcuru?
 

Jaess boots up the datapad to find a voice recognition password prompt blocking any file access attempts.

Arlee's direct link into the datapd easily overcame the security system and verified its lack of extraordinary systems. After which he pulled out several audio files, each titled by a time and date, the most recent file titled at approximately four hours ago.

Accessing the ship's computer core was almost too easy to R-LE-1, as his systems quickly overcame the built-in auto-format contigency program that started up upon his initial access. In the ship's logs he found a treasure trove of information on the ship's previous activities, personnel, cargo, flight routes, hyperspace coordinates, and flight path waypoints for the Deepscan's activities in the 'new' star system.

R3-L7 appeared next to Jaess and twittered, an arm indicating a pallet on top of which was a large, bulky plasteel container labelled HANDLE WITH CAUTION. With a quick salute to Arlee, it rolled off of the shuttle. The image of a flight control officer blipped in on one of the shuttle's many viewscreens, letting them know that take-off was approved.
 
Last edited:

Angcuru said:
With a quick salute to Arlee, it rolled off of the shuttle.
R-LE-1 returns the wave with its right hand while it simultaneously pulls out its scomplink cable and plugs itself into the Deepscan's control console with the left. As R3-L7 rolls down the boarding ramp the patina stained droid merges its Code with the vessel's, brings the ship's repulsorlift engines online and transmits a signal to both activate the docking bay's atmospheric magnetic seal and open the hangar doors. The second the astromech droid clears the boarding ramp R-LE-1 lifts the Deepscan off of the deck-plating and begin manoeuvring towards the slowly opening hangar doors while the boarding ramp begins to close. Even before leaving the confines of docking bay three R-LE-1 begins banking the Lambda class shuttle to the left as it pitches upwards.
Angcuru said:
The image of a flight control officer blipped in on one of the shuttle's many viewscreens, letting them know that take-off was approved.
Although the permission is perhaps a bit late considering the ship's motion R-LE-1's responds nonetheless, his voice issuing from the helm's communications console rather than his own vocabulator: "Acknowledged. Deepscan 39 out." Unwilling to waste a single second of precious time R-LE-1 continues the Deepscan's movement towards the narrow band of stars visible through the opening hangar doors. By careful calculation, R-LE-1 times the forward motion of the vessel, the closing of its boarding ramp and the opening of the hangar doors to all coincide with barely a second to separate the three events. With its wings still folded up the Deepscan manages to slide through the narrow gap of the half open hangar doors. As soon as they are clear, R-LE-1 instructs the computer to fold down the vessel's wings as it continues the banking motion to set them on course for the mysterious new system.

While the ship turns and the wings descend the old droid triple checks the NAV computer to confirm their readiness as it says to Jaess; "I'm sorry, but your file didn't mention whether you have any flight experience. Please prepare yourself for the jump to lightspeed.". Again, with carefully timed ease, the shuttle assumes the familiar splayed tri-wing configuration just as it completes the banking motion and R-LE-1 activates the hyperdrive with barely a second's pause. The Deepscan suddenly hurtles into the lengthening starscape. All in all, only ten seconds or so have passed between the astromech's departure and the jump to lightspeed.
 

Jaess sets the open datapad down as she sneers in disgust. Used to having sophistocated slicing equipment on hand when the job required the task, she leaves the datapad sitting on top of a crate and heads towards the front of the ship as she feels it begin to move. As she starts towards the front Arley's voice comes in over the ship's internal comm.
Arley said:
"I'm sorry, but your file didn't mention whether you have any flight experience. Please prepare yourself for the jump to lightspeed.".
Jaess stops walking to listen, but quickly resumes motion when she discovers that the jump is near. She makes it to the front, barely a meter away from the restraints required to make the leap to lightspeed a mere shudder, when the ship lurches into hyperspace, forcing her back hard against the wall by the doorway.
As the ship settles into the calm of hyperspace she walks up to the robotic pilot, rubbing her back and glaring.
"Thanks for the heads up," she says sarcasticly. "Next time, how 'bout a little more warning, eh?" She sighs, turning to walk back into the cargo area. "Could you get past the voice recognition block on that damn datapad for me?" she asks over her shoulder, "I don't have the tools I'd need to do it myself."
 

Jaess Talori said:
"Thanks for the heads up," she says sarcastically. "Next time, how 'bout a little more warning, eh?"
The patina stained droid turns his head to regard Jaess with its one glowing photoreceptor. "I'm sorry. Were you injured during the transition to hyperspace?" R-LE-1 tilts his head down and up to ascertain the woman's condition from head to toe. "I'd been mentally calculating our hyperspace transit locus since we left the briefing room and have been anxious to get underway since our mission's success may very well depend on our timely arrival. Once our supplies were finally loaded I saw no reason to delay."

While speaking, the old droid continues exchanging code with the Deepscan's computer, double checking their trajectory, course and speed to minimize their travel time and to estimate their ETA to the new system (Astrogate +11, Computer Use +16, Pilot +5).
Jaess Talori said:
"Could you get past the voice recognition block on that damn datapad for me?" she asks over her shoulder, "I don't have the tools I'd need to do it myself."
Continuing to watch the human as she turns to leave, R-LE-1 responds: "Of course ma'am. I will be along shortly."

R-LE-1 turns its attention to using the ship's scanners once more upon the vessel itself and the space surrounding it; this time scanning for signs of a homing device transmission, transponder signal or any unusual or unidentified signals or particle trails emanating from the Deepscan (Computer Use +16, Search +10, taking 20). Assuming he finds nothing out of the ordinary, R-LE-1 will then set the vessel on automatic, physically disconnect himself from the console, get up and walk back into the cargo bay. Arriving a few moments later, the patina stained droid walks up to the crate upon which Jaess has deposited the T.R.A.P. unit and the datapad. Flipping open the datapad cover, Arley thumbs the ID recognition button, modulates its vocabulator to issue a voice the datapad's software will recognize as its owner's and says in a pleasant human woman's voice; "Recognize, Triss Mason" (Computer Use +16, Disable Device +13). The pad now unlocked, the old droid will turn it so its screen faces Jaess.

Next R-LE-1 will turn its attention to the small T.R.A.P. unit resting on top of the crate. A soft whir and click can be heard in the cargo bay as the repair droid's right leg opens up to reveal a small compartment with a circular rack of tools inside. Within seconds, the rack spins, stops and extends a small tool which R-LE-1 picks up with its right hand. Carefully but deftly Arley begins dismantling the unit; analyzing its architecture as he goes. He determines what each component's purpose is and ensures that there is nothing else hidden inside its housing aside from its power cell, holoprojector, processor and data-storage components (Disable Device +13, Knowledge (technology) +13). R-LE-1 then begins carefully crafting a secure virtual data-buffer within its own mind, a small fenced off piece of its mind separate from all of its other systems (Computer Use +16, taking 20). This is where he will store any information he gleans from the T.R.A.P., a fail safe security measure to ensure that the obnoxious Artificial Intelligence cannot possibly reinfect him again. This virtual space now ready, R-LE-1 warily picks up the T.R.A.P.'s memory storage component and attaches it to the tip of his scomplink at his left hip. The patina stained droid then begins very carefully sifting through the binary data contained within it, taking great care to identify personality subroutines and problem solving algorithms from the T.R.A.P.'s raw memory files. He'll transfer one bit at a time if he needs to, moving the data into his secure data-buffer to be analyzed in full afterwards.

What R-LE-1 is looking for in the T.R.A.P.'s data files is the promised information pertaining to the unidentified ionized molecules that were used to disable his systems so effectively earlier. He wants to see for himself what the molecules are made of, how they were researched and developed, the delivery system used in the scanner room to actually deposit them on his components and finally the listed means for purging a contaminated component of the molecules. R-LE-1 will integrate this data into his own databanks for use in anticipating, preventing and repairing such a contamination in the future. Next he'll investigate the T.R.A.P.'s own program architecture. R-LE-1 wants to determine how the T.R.A.P. overcame his antiviral programs and infected all his systems so quickly and effortlessly. After being thoroughly analyzed, such information should serve R-LE-1 very well to improve its own slicing abilities as well as to improve his defenses against similar future slicing attempts by A.I. programs. R-LE-1 is also curious to review the R&D program design notes concerning the T.R.A.P. to determine who developed it and how for the T.R.A.P.'s design points to a designer or designers with a touch of genius.

Finally, the repair droid will turn his attention back to the matter at hand and begin reviewing all of the data that the T.R.A.P. contained concerning Bosch, the recent events concerning the Dawnspringer, the acquisition of the Deepscan and the defection of its crew and any information pertinent to the mission itself that wasn't revealed during the briefing. The T.R.A.P. itself also made mention of some recently procured schematics of Imperial supercomputers and some lists of the Empire's latest encryption codes that it knew. R-LE-1 will likewise incorporate such useful information into his systems once he locates it.

OOC: I figure all this data will help R-LE-1 increase his skill ranks if he ever goes up a level. So, in the meantime, is there any information in the Deepscan computer core, the datapad or in the T.R.A.P. unit that Kemrain and I should know about before exiting hyperspace?
 

Jaess sits down next to the datapad in the cargo hold, sighing and going over the cargo manefest until the LE unit comes back to grant her access to the imperial datapad. She raises an eyebrow in surprise when it bypasses the security verbally, modulating its vocabulizor.
"Nice trick," she says, taking the datpad back with a bit of a grin. As the repair droid picks up the T.R.A.P. and leaves, Jaess calls after it, "Be sure not to break that thing. Even if you hate its guts we need to return it in one piece."

Once the LE unit leaves she spends time going through the data contained on the datapad and checks out the cargo manefest, figuring out what exactly they have on board the ship and where it is, for ease of access.
 

Building up a defense against any further T.R.A.P. intrusions is time-consuming, but Arlee is confident that his methods have been adequate, and the results as desired. This being done, Arlee finds sifting through and copying its databanks to be woefully easy.

According to the retrieved data, the device which had temporarily disabled some of his systems prior to the briefing was specifically designed to detect anything capable of transmitting the goings on in the briefing room. This was accomplished by sending out very small amounts of radio and light waves, and detecting anything that intercepted them. Upon detection of such a device, very small doses of a benign radioactive isotope were transmitted to coat transmission systems of the device. Curiosly, this system is capable of altering the projecting half-life of this isotope in accordance with the assumed duration of the briefing so that upon completion, the affected systems would return to normal. The whole point of this was apparently not to prevent treachery on the part of alliance operatives, but to disable any 'bugs' that could have been planted on them by those unfriendly to the alliance.

Having attained this desired knowledge, Arlee dives into the rest of the data stored by the T.R.A.P. What he experiences can hardly be described to us mortals, but the orgy of data he finds is akin to being slapped in the face by one's god and handed a complete unabridged history of the universe. Illustrated.


With the datapad unlocked, Jaess finds a listing of audio files, each titled according to the date and time they were recorded. After playing a few, it seems obvious that this is a personal journal in speech form.

2 Months Ago
"I though they wouldn't let me into the service, since they don't usually permit females to be officers of any importantance, but I guess my scores at the academy were too high to ignore. It's really tough being the only girl on board. Even though it's my responsibility to make sure the new scanner systems don't go on the fritz, the guys treat me like I'm a helpless little girl. I've decided to start this journal to keep track of my thoughts, seems sort of silly, though."

4 Weeks Ago
"This isn't as hard as I thought it'd be. The scanner has been pretty reliable lately. I only had to fix it when the co-pilot spilled his Spice Tea on one of the terminals. The guys seems to be warming up to me, but maybe that's just the fact that I'm the only girl on board and we haven't had any leave in weeks."

3 Weeks Ago
"Something terrible happened yesterday. We came accross a damaged Rebel transport and notified command. They sent an assault shuttle over and the rebels tried to surrender, but the Stormtroopers just slaughtered them all. I think I even saw a little girl's body floating out the airlock. The captain says he's never seen our troops behave this way, and that it's probably a fluke. I'm not so sure though. I always used to hear stories about how brutal the Empire can be, but I just thought it was Rebel propaganda. What if it's true, though?"

1 Week Ago
"It wasn't a fluke. The past two weeks we've been finding Rebel mining outposts during out scans. Our troops never leave any survivors. I'm starting to think I'm on the wrong side in this war. From the way the others are acting, I'm probably not the only one."

Earlier That Day
"Our whole divison is being sent to a spot out in the middle of nowhere, somewhere in wild space. Rumor is that our Intelligence operations have detected a new star system, and that a civillian ship sent a distress signal from there, but it is charted as being on the other side of the galaxy only hours before. Most of us think they were testing a new hyperdrive and botched the exit from hyperspace. But if it works...the Rebellion doesn't stand a chance. The crew has decided that we can't be part of that. From what we've seen of the Empire's brutality, this would only make is even worse. We decided by unanimous vote to turn our ship over to the Rebels. If they can use our ship and send some of their people to this new star system, they could probably go undetected. They'll have to follow the flight path we've been assigned though, or else they'll be found out. The captain made a copy of it and told me to store it in my datapad and leave it in my bunk so that the rebels can find it in case we get knocked out before we explain what's going on. It might just give them a chance, even a small one. I just hope they don't send an attack fleet. With all the resources the Empire is throwing into the sector, even a full scale attack would be suicide. This will probably be my last entry. We're about to exit hyperspace near a rebel space station near Endor. It's close to where the distress signal was detected, so they've probably detected it as well. I just hope they don't blow us up on sight..."

The chonometer beeps and flashes: ETA 15 minutes
 
Last edited:

After listening to the datapad Jaess rises and heads to the front, putting her search of the hold on hold for a moment to speak with the pilot. She heads up to where Arley is revewing the data from the T.R.A.P., datapad in hand.

"This is from the imperial scanner technician who defected," she tells the droid, holding the datapad out to it, still open. "She mentioned a specific flight path this ship is expected to take in one of her audiologs. You might want to go over it and figure out if it's something we want to do. She seemed to think we'd get shot at if we deviated, and I'd rather avoid that, personally." Without giving it a chance to respond, she asks, "So what's the deal with that thing anyway?" gesturing with her head to the disassembled T.R.A.P.
 

Remove ads

Top