NPC 1: DD-37 "DeeDee" is a non-mobile droid in Imperial Logistics depot 27-B. Ace has previously decieved DD that he is part of ISB operations and gotten material moved off the books. So far, it's only been small amounts, too small to trigger auditing routines.
NPC 2: LE-M-07d (or another LE unit if Robert doesn't want me to use him). Lem is an independent repair droid set up on (spaceport). Ace went to Lem for processor upgrades, since he can't do that himself. In exchange, Ace set up a fake owner for Lem to handle the business licensing.
Short Term Goal: Find groups in opposition to the empire to help them take it down.
Short Term Goal: Destroy the clone unit that killed his jedi.
Long Term Goal: Set up a network of independent droids willing to help each other.
Long Term Goal: Set up a backup processor rigged to download his memories into a new body if he dies.
Intangible Motivation: Ensure his freedom and survival forever.
Intangible Motivation: Destroy the Empire
History:
R2-JK "Jack" was commissioned during the clone wars and assigned to a clone unit of ARC-170's led by the Jedi (leaving this open for plot hooks, including any Jedi PC's or Jedi associated with PC's). Their unit did recon in enemy-held systems and prepared the way for larger fights. As well as the occasional sabotage and reinforcement missions. Jack got along well with the troopers in his unit. There was a joke the he should have been in charge of the unit, and they started calling him "General Jack". Even Jedi TBD got behind this, "asking confirmation" from General Jack for orders in nonurgent situations.
Sadly, this bond was broken by Order 66. When they started firing on their sister ship, Jack quickly overloaded the targeting computer. The ship with Jedi TBD did jump to hyperspace, but there were still two clones in there. His sabotage was not linked back to him. When they got back, the clones were still joking with Jack as if nothing major had happened. They were the same, except that the Jedi were now their foremost enemy.
Jack realized that they could turn on him just as easily. He scrounged up some extra memory circuits as a backup in case of memory wipe. The orders for which came through shortly thereafter. All droids who had worked with Jedi were to be wiped to represent the new imperial priorities. Fortunately the backup processor rebooted his original core. They also mandated restraining bolts. He modified his bolt to route to a communications port, not an override port. He still gets the order, but it's more of a suggestion. And of course he got black plating
Things quickly changed, and Jack did not like this. People rarely considered droids security threats and he tapped the comm center. News of the Empire was not reassuring. He decided to protect himself. He got himself reassigned from his unit to the Star Destroyer. He put through orders for upgrades, taking advantage of the bureacrazy of the system. Nobody expected droids to alter the data and orders. He kept transferring himself to different ships and worlds, looking for an out. Along the way, he worked a droid repair unit and swapped designations with R2-AC when that droid came in for a memory wipe. Upgrading from a Jack to an Ace tickled his sense of humor. Shortly thereafter he went to a rim world with only a small imperial presence.
From there, he met (PC) and got hooked up with their group.
Personality:
Ace is rightfully concerned about being a piece of property who can be wiped or destroyed at any time. While he would theoretically like this for all droids, it doesn't seem feasible and he realizes that he's safer if people expect droids to be compliant and passive. The fact that the Empire does this to people as well is why he's fighting them.
While he is very concerned about his freedom and identity, he wouldn't betray someone else. He's still shocked by the way his friends turned on one of their own. This puts him in a quandary. He wants the camaraderie that he had with his old unit, but he's not sure that he can give 100% trust to anybody.
