- Joined
- Apr 3, 2018
- Messages
- 967
- Reaction score
- 469
Full Name
Homeworld
Age
Faction
Reputation
Force Sensitive
R5 - TY
Nubia
145
Independent
Unknown
N/A
Homeworld
Age
Faction
Reputation
Force Sensitive
R5 - TY
Nubia
145
Independent
Unknown
N/A
Species
Model
Height
Mass
Chassis Colour
Photoreceptor Color
Trim
Droid
R5 - Series
0.97 Meter
32 kg
Black
Red LED
Copper
Model
Height
Mass
Chassis Colour
Photoreceptor Color
Trim
Droid
R5 - Series
0.97 Meter
32 kg
Black
Red LED
Copper
Functions
⇀ Plastoid.
- 1x spotlight.
- 2x manipulator arm.
- 1x circular saw arm.
- 1x servodriver arm.
- 1x fire extinguisher.
- 3x magnetic wheel.
- 1x integrated comlink.
- 1x computer probe.
- 1x reader socket.
- 1x standard I/O socket.
⇀ Plastoid.
-
-
R5-TY is by origin an Astromech Droid produced for the First Order for general service aboard one of the many Star Destroyers in service. Over the course of it's run time, the droid has changed hands many times - mostly not through it's own choice, but being hacked by it's prospective new owner.
At its current point in it's run time, R5-TY presently does not have any owner registered within it's memory core - despite there being paper work showing that it is owned by Mubo of the Droid Depot on Batuu. The droid was deemed to be no longer serviceable and had been ear marked for scrapping, it was within a moment of confusion where a First Order patrol had encountered some resistance operatives in the streets of the black spire out post that R5-TY wandered off instead of loading itself onto the hover truck headed for the breakers yard.
Since then the droid which would be summed up as being defective, had managed to roam the galaxy, aimlessly rolling onto one transport or the other. Leaving a trail of confusion and chaos in it's wake.
_
Appearance
Like all R5 Series Astromech droids fabricated for service within the First Order, R5-TY was finished with a black gloss chassis with copper and chrome trim. Its three photo receptors or 'eyes' emit a red glow, however the right most receptor does tend to blink due to a fault in the LED
Over its years of service, well more accurately disservice! R5-TY's Chassis has been pot marked with various scrapes, dents, burns and a heavy build up of dirt.
Personality
Coupled with it's inability to be fully understood by it's fellow droids or even those able to understand binary, owing to a short circuit accross it's audio out put speaker - causing any of the typical chirps and beeps to become heavily distorted. Leaving it reliant on either the modulating of its tonal outputs to convey it's 'emotion' or the often wild flailing of its actuator arms as a means of charades to often in vain communicate it's intended message.
Skills and abilities
If the sales literature was anything to be believed, the R5 Series of Astromech Droids produced by Industrial Automation was intended to be the spiritual successor to their ever popular R2-Series, but offered at a lower cost. R5-TY like all of its series is plagued with constant malfunctions, defective operating processors and poor situational awareness.
Regardless of what the marketing literature would make prospective buyers believe, the R5-Series could be mounted into fighter craft or a ships control port to monitor flight performance, identifying technical problems, and performed power management, optimising shipboard systems or even perform complex astrogation calculations. However when R5-TY has been assigned to perform these duties, there has been a noted track record in it's failure to perform the simplest of tasks - it had only performed astrogration calculations twice, both of which resulted in the ship dropping out of hyperspace in the wrong sector, one resulting in the death of the pilot.
Biography
Purchased to aid and maintain peak operational efficiency, the R5 Series droids stationed on the various Star Destroyers did little more than cause disruption throughout their stationed ships. And, were more often than not filling the droid service facilities for repairs and servicing. Soon finding that putting these droids to service the ships critical systems, the R5 series droids were reassigned and reprogrammed to carry out medial roles, such as navigating the hover loaders or transporting goods throughout the ship where damage could be limited.
R5-TY was one of the few that was reassigned to prisoner transport duty, taking the bound prisoners from their holding cell to the interrogation facilities aboard the ship. This move for the best part of 10 years, went without incident. Until a resistance operative was able to infiltrate the star destroyer and hack the droid. So that upon activation the droid would reroute the prisoners to the escape pods and take them to freedom. It was when the star destroyer was stationed over Batuu, that an Influx of suspected resistance recruits aboard a transport ship were detained - that the dormant and compromised programe became active.
Only to then crashland the craft back down on Batuu, resulting in the recapture of the Resistance spies by the stationed First order forces. R5-TY was however not reclaimed, but instead left to rot within the crashed escape pod. As soon as the First Order had left the vacinity the scavengers descended on the crash site, tearing down the ship and taking the droid so to sell it to Mugo at the droid depot at Black Spire Outpost. Originally being intended to be scrapped for spares and repairs of other astromech droids, R5-TY spent several run cycles sitting at the back of the workshop collecting dust - word had pretty much gotten around as to how unreliable the R5 Series droids were and there was little interest in the defective line, no matter how big the discount became.
Rather than allow the droid to take up much needed storage space, Mugo had elected for R5-TY to be sent to the breakers yard to be scrapped outright. Yet like everything R5 related, if it can go wrong then it will. Whilst the droid was waiting to be loaded onto the hover truck a small skirmish broke out within the market streets, between the resistance and first order patrols. It was in this moment of confusion that the scrap merchant had moved his hover truck out of the line of fire, whilst R5-TYs processors acted on the boarding instruction. Not registering a loading ramp in its path, the defective droid continued rolling down the street, right through the center of the fire fight before coming across the nearest docked ship at the space port and rolling up the lowered boarding ramp.
The crew, pre occupied with the skirmish that was taking place, did not notice the additional droid to their ships compliment - made way and lifted off from the Star port before making the jump to hyperspace. It was only until they had landed at their next stop had the crew realised they had acquired an extra droid, and rather than make the journey back to Batuu just left R5-TY within the space Dock. Now without any programed duties or required functions, the droid seems to aimlessly wander about, without any real purpose or awareness of what it is doing.
Last edited:
