View attachment 81621
View attachment 81622
[sblock=Rex Take 3]Rex (R3-X20) is an R3 series astromech droid who once belonged to the smuggler, Sarn Doree. Rex was wiped just before his Sarn purchased him twelve years before, it was poorly executed and there are bits of information without context that rattle around in his processes. He has pieced bits of the information together to know enough that he once preformed calculations in an x-wing squadron and that he already possessed several mods before his last wipe. Sarn was a talented smuggler, but he needed an assistant who could splice and help with hyper-drive calculations, if the assistant could also pilot when they weren't under duress it was a boon that made his life easier.
With Rex by his side, Sarn's notoriety increased. When opportunities arose he had Rex fitted with after-market upgrades. It was during such upgrades that Sarn first noted that Rex was not a standard R3. Someone had tinkered with Rex's guts, replacing damaged circuitry with bits that didn't quite belong. It made the upgrades a challenge, to install the upgrades and integrate them into his programming without wiping Rex. Despite the droids quickly developing personality, there was too much information that he couldn't risk losing, and he was growing fond of the droids quirky nature.
For years Sarn and Rex were inseparable, Rex pulling Sarn out of dozens of scenarios that would have been his end. Sarn always tried to stay out of the Galactic conflicts, Sarn hated the politics of the New Republic almost as much as he hated the remnants of the first empire, but there was money to be made moving illicit goods for the resistance (and other less reputable organizations). It was not unheard of for Sarn to take on the odd job for the resistance, though he generally avoided working with the First Order, just as he had avoided working with the Empire in the past. Sarn may not have been the most reputable individual, but he had a strong personal code that guided his "business" decisions. He freely shared his outlook with Rex, and those outlooks became woven within Rex's directives.
Sarn's history with the resistance, the empire, and the First Order led to the First Order identifying him as an enemy combatant. During a hyperspace jump, they were ambushed by First Order ships, apparently the First Order had caught wind of the black market tech they were smuggling for the resistance. At first it seemed like previous adventures, Rex began jamming their comms and splicing into their ships using their ships communications hardware in hopes of disabling the First Order ships so they could slip away. The First Order were aware of this tactic and had prepared their defenses accordingly. The First Order boarded their ship and began killing on sight, some of the crew managed to slip away in the few escape pods they had. Rex watched as the First Order officer, Officer Glys, caught Sarn off-guard. There was little that Rex could do to stop it, but that didn't stop him from trying. Two of their grunts wound up writhing on the ground before, they managed to fit him with a restraining bolt. He watched as Glys killed Sarn and confiscated the ship and all its cargo, to include the Rex himself. R3's processes were disrupted by the restraining bolt and they would have wiped him, but they wanted to recover what information they could from his databanks first... big mistake.
They had loaded the cargo to include Rex on a small shipping frigate bound for a First Order star destroyer, they knew Rex was designed and modded to splice, but what they didn't realize was that Rex was equipped with a Data Breaker. He managed to disable the restraining bolt, steal a large swath of data as to the nature of First Order operations in the region, and sent the few First Order forces on the Frigate into the vacuum of space. He probably could have gotten away with it up to that point, there were no survivors and he could wipe the ships data, but a data loop kept reminding him the First Order and Glys were responsible for Sarn's death. He couldn't help himself as he siphoned tracked down the Glys' digital presence, his companion had always said the best way to hurt someone was by hitting their credit stick, and he needed to hurt the people who had ended his companion. He drained the Glys' credits, and did his best to do some damage to the man.
His Splicing didn't go unnoticed, First Order technicians back traced his splicing and accessed recordings of the droid spacing the ship's crew and splicing their network. A bounty was quickly placed on Rex. Glys was held responsible for the Data breach due to his oversight and was promptly relieved of his command position. He has been reduced to a ship's officer and would do anything to see Rex destroyed and stripped for parts. By disabling the comms on the freighter, and shutting down all non-essential systems Rex managed to float around on a derelict freighter for months before realizing the dire nature of his situation. He began running calculations as to which scenarios had the highest probability of his survival, he came to the conclusion that on his own he had the highest chance of survival, but all alone on a ship as though he didn't exist. Readjusting, he calculated highest chance of survival while negatively impacting the First Order, he came to the conclusion that by approaching the resistance, he would avoid being turned in for the bounty and could possibly work with them towards harming the First Order. His plan formulated, Rex piloted the freighter to known resistance space. The Resistance was more than happy to receive the confiscated cargo, but questioned the droid's authenticity, believing it to be a ploy by the First Order.
The resistance technicians tried to wipe Rex, but after one of their technicians wound up crumpled on the ground and their systems became flooded with the First Order data he had stolen, to include the bounty on him. One of the technicians who understood binary worked out an agreement, explaining to Resistance leadership the droid's situation. At first there was a call for the droids destruction, it was too much of a risk they argued. Finally, Lt. Mason stepped forward, "I'm in need of a new astromech anyways, I'll take responsibility for it." So for several months, he traveled the outer rim aboard the small cruiser with Lt. Mason. On a resupply on Tatooine, Lt. Mason managed to pick up a young girl, apparently from a wealthy family who had become stranded on the planet, Arsinoe.
It started with Rex merely observing the girl, taking note of the way she seemed so out of place, but still belonging wherever she went, somehow the natural center of attention. A particular scene replaying in the little droids processors: Sarn at one of the space ports while waiting on a client, dragging away a man who had "gotten handsy" with a girl despite her protests. "Keep an eye on the girl, I'll be right back."
Rex followed her around, guarding her against the less than savory types that often wind up fighting in wars on either side. She doesn't understand his beeps and boops, but Rex feels compelled to keep her safe. An underlying chivalry that he inherited during his time with Sarn. While Rex doesn't see himself as her personal astromech droid, it is likely how his association with her has come to be viewed by any who witness the droid following her around. He is merely keeping an eye on the girl...
So when the time came to drop the girl off on Kabal, Rex protested in his blips and boops. He didn't want to leave the girl alone. After some negotiation with Lt. Mason and crew, they allowed him to part ways for the time being so he could keep a watchful eye on the girl. They hadn't felt completely comfortable leaving her on Kabal all alone anyways, though leaving her with an Rex didn't help alleviate their concerns that much, it was better than nothing.[/sblock]
View attachment 81622
[sblock=Rex Take 3]Rex (R3-X20) is an R3 series astromech droid who once belonged to the smuggler, Sarn Doree. Rex was wiped just before his Sarn purchased him twelve years before, it was poorly executed and there are bits of information without context that rattle around in his processes. He has pieced bits of the information together to know enough that he once preformed calculations in an x-wing squadron and that he already possessed several mods before his last wipe. Sarn was a talented smuggler, but he needed an assistant who could splice and help with hyper-drive calculations, if the assistant could also pilot when they weren't under duress it was a boon that made his life easier.
With Rex by his side, Sarn's notoriety increased. When opportunities arose he had Rex fitted with after-market upgrades. It was during such upgrades that Sarn first noted that Rex was not a standard R3. Someone had tinkered with Rex's guts, replacing damaged circuitry with bits that didn't quite belong. It made the upgrades a challenge, to install the upgrades and integrate them into his programming without wiping Rex. Despite the droids quickly developing personality, there was too much information that he couldn't risk losing, and he was growing fond of the droids quirky nature.
For years Sarn and Rex were inseparable, Rex pulling Sarn out of dozens of scenarios that would have been his end. Sarn always tried to stay out of the Galactic conflicts, Sarn hated the politics of the New Republic almost as much as he hated the remnants of the first empire, but there was money to be made moving illicit goods for the resistance (and other less reputable organizations). It was not unheard of for Sarn to take on the odd job for the resistance, though he generally avoided working with the First Order, just as he had avoided working with the Empire in the past. Sarn may not have been the most reputable individual, but he had a strong personal code that guided his "business" decisions. He freely shared his outlook with Rex, and those outlooks became woven within Rex's directives.
Sarn's history with the resistance, the empire, and the First Order led to the First Order identifying him as an enemy combatant. During a hyperspace jump, they were ambushed by First Order ships, apparently the First Order had caught wind of the black market tech they were smuggling for the resistance. At first it seemed like previous adventures, Rex began jamming their comms and splicing into their ships using their ships communications hardware in hopes of disabling the First Order ships so they could slip away. The First Order were aware of this tactic and had prepared their defenses accordingly. The First Order boarded their ship and began killing on sight, some of the crew managed to slip away in the few escape pods they had. Rex watched as the First Order officer, Officer Glys, caught Sarn off-guard. There was little that Rex could do to stop it, but that didn't stop him from trying. Two of their grunts wound up writhing on the ground before, they managed to fit him with a restraining bolt. He watched as Glys killed Sarn and confiscated the ship and all its cargo, to include the Rex himself. R3's processes were disrupted by the restraining bolt and they would have wiped him, but they wanted to recover what information they could from his databanks first... big mistake.
They had loaded the cargo to include Rex on a small shipping frigate bound for a First Order star destroyer, they knew Rex was designed and modded to splice, but what they didn't realize was that Rex was equipped with a Data Breaker. He managed to disable the restraining bolt, steal a large swath of data as to the nature of First Order operations in the region, and sent the few First Order forces on the Frigate into the vacuum of space. He probably could have gotten away with it up to that point, there were no survivors and he could wipe the ships data, but a data loop kept reminding him the First Order and Glys were responsible for Sarn's death. He couldn't help himself as he siphoned tracked down the Glys' digital presence, his companion had always said the best way to hurt someone was by hitting their credit stick, and he needed to hurt the people who had ended his companion. He drained the Glys' credits, and did his best to do some damage to the man.
His Splicing didn't go unnoticed, First Order technicians back traced his splicing and accessed recordings of the droid spacing the ship's crew and splicing their network. A bounty was quickly placed on Rex. Glys was held responsible for the Data breach due to his oversight and was promptly relieved of his command position. He has been reduced to a ship's officer and would do anything to see Rex destroyed and stripped for parts. By disabling the comms on the freighter, and shutting down all non-essential systems Rex managed to float around on a derelict freighter for months before realizing the dire nature of his situation. He began running calculations as to which scenarios had the highest probability of his survival, he came to the conclusion that on his own he had the highest chance of survival, but all alone on a ship as though he didn't exist. Readjusting, he calculated highest chance of survival while negatively impacting the First Order, he came to the conclusion that by approaching the resistance, he would avoid being turned in for the bounty and could possibly work with them towards harming the First Order. His plan formulated, Rex piloted the freighter to known resistance space. The Resistance was more than happy to receive the confiscated cargo, but questioned the droid's authenticity, believing it to be a ploy by the First Order.
The resistance technicians tried to wipe Rex, but after one of their technicians wound up crumpled on the ground and their systems became flooded with the First Order data he had stolen, to include the bounty on him. One of the technicians who understood binary worked out an agreement, explaining to Resistance leadership the droid's situation. At first there was a call for the droids destruction, it was too much of a risk they argued. Finally, Lt. Mason stepped forward, "I'm in need of a new astromech anyways, I'll take responsibility for it." So for several months, he traveled the outer rim aboard the small cruiser with Lt. Mason. On a resupply on Tatooine, Lt. Mason managed to pick up a young girl, apparently from a wealthy family who had become stranded on the planet, Arsinoe.
It started with Rex merely observing the girl, taking note of the way she seemed so out of place, but still belonging wherever she went, somehow the natural center of attention. A particular scene replaying in the little droids processors: Sarn at one of the space ports while waiting on a client, dragging away a man who had "gotten handsy" with a girl despite her protests. "Keep an eye on the girl, I'll be right back."
Rex followed her around, guarding her against the less than savory types that often wind up fighting in wars on either side. She doesn't understand his beeps and boops, but Rex feels compelled to keep her safe. An underlying chivalry that he inherited during his time with Sarn. While Rex doesn't see himself as her personal astromech droid, it is likely how his association with her has come to be viewed by any who witness the droid following her around. He is merely keeping an eye on the girl...
So when the time came to drop the girl off on Kabal, Rex protested in his blips and boops. He didn't want to leave the girl alone. After some negotiation with Lt. Mason and crew, they allowed him to part ways for the time being so he could keep a watchful eye on the girl. They hadn't felt completely comfortable leaving her on Kabal all alone anyways, though leaving her with an Rex didn't help alleviate their concerns that much, it was better than nothing.[/sblock]
