Droids (sometimes also 'droids, short for androids), were robots: mechanical beings, often possessing artificial intelligence. They were used in a variety of roles and environments, often those considered too menial or too dangerous for Humans and other species. Droids were also used in fields that required extensive specialization and knowledge, such as medical droids and astromech droids.
Depending on the model and its corresponding purpose, droids were totally obedient, rugged, expendable, capable of vast memory recall, and mathematically precise. These characteristics made them well suited for many jobs, though the lack of independent thought in the cheaper, less advanced models limited their capability. This lack of autonomy was simultaneously a vast asset and a glaring weakness—an asset in terms of obedience and control but a massive drawback in terms of effectiveness. Designers faced a fundamental paradox—make the droids overly intelligent, and they might rebel; yet make the droids not intelligent enough and they would be ineffectual.
Customarily, droid names were an arrangement of numbers and letters.
The words droid and robot are generally taken to mean the same thing. However, the official definition of a droid is "a mechanical being with a self-aware consciousness, as distinguished from a computer by having a self-contained method of locomotion."
Droids were divided into five basic "degrees," or "classes," based upon creativity, intelligence, and capacity for independent thought.
Droids were categorized by function, though the lines between categories were often blurred. Many droids, such as members of the BD-3000 series, served a variety of roles and purposes, making classification difficult. Other droids, especially those who were "one-of-a-kind," had unique capabilities and changing characteristics that made classification impossible. Some droids changed functions as they changed owners, sometimes many times throughout their operational life. These limitations notwithstanding, droids were grouped according to their primary factory-installed functionality.
These droids were used to kill specific targets, often those too well guarded for approach by conventional means. Typically deployed by bounty hunters, assassin droids were often tasked with suicide missions—missions with almost zero probability for successful escape. In addition to their expendability, assassin droids could be programmed with advanced targeting algorithms, allowing them to be more accurate than even the best sentient sniper. Not all assassin droids utilized traditional weaponry, however—certain models, such as the ASN-121, could be outfitted with a number of different weapons or sensors, allowing for different tactics such as brute force attacks or stealthy penetrations. Because of the higher intelligence and independence required for droids of this type, rebellions were known to occur, though not very frequently.
Droids used for interstellar starships, astromech droids, were mobile multi-role droids capable of hyperspace navigation, systems monitoring/control, damage repair, and data storage. These droids had extensive databases of stellar systems and hyperspatial coordinates, which were necessary for faster-than-light travel. Astromech droids were also used in certain starfighter models, typically those with hyperdrives. They served a similar, though expanded, role—supplementing the ship's onboard computer systems and aiding the pilot in navigation, repair, and interfacing. More advanced astromech models could often pilot a small craft by themselves, blurring the line between an astromech droid and a pilot droid. Some astromechs, like members of the R2 series, were equipped with numerous features that expanded their functionality beyond navigation and repair, allowing them to become useful in almost any situation. Because of their emphasis in technical fields, astromech droids were not equipped with vocabulators or language programming; instead communicating through a series of beeps and whistles known as binary. In addition to an astromech's factory-installed functionality, many of these droids were customizable—allowing upgrades to sensors, tools, software, and even basic hardware.
Droids were used most commonly in combat-related roles, where they offered a plethora of advantages over organic units. Droids could carry heavy weaponry and shielding, move rapidly without tiring, analyze targeting and trajectory calculations instantly, and protect crucial systems by burying them deep inside the frame of the droid (often featuring backup processing and multiple layers of redundancy). Droids could follow orders to the letter, taking risks no Human ever would yet still maintaining their calm precision. Most importantly, however, these droids were expendable—unlike sentients, the amount of time and energy it cost to assemble a droid was often a tiny fraction that of recruiting (or growing) a Human and training them. Built on massive automated assembly lines, like the ones on Geonosis, thousands of capable droids could be produced in a matter of hours. Because of these factors, droids were used extensively as military units, most famously by the Confederacy of Independent Systems. Despite these advantages, however, combat droids suffered from several drawbacks. Most importantly, in order to create total obedience and foil any chance of rebellion, droid units were often crippled with extremely sub-par artificial intelligence. This drawback was exemplified by the hideously poor A.I. of the B-1 battle droid, which rarely served any purpose other than as cannon fodder. Also, many (though not all) droid units lacked the flexibility and manipulation capabilities of Human units, especially in terms of hand and finger use.
Another prime use of droids was to question prisoners, and if deemed necessary also as instruments of torture. The use of droid interrogators as opposed to Humans made sense in a number of ways: impersonal machines often increased the subject's fear, making him more likely to be cooperative; droids offered a precise medical-based analysis of a subject's system, tolerances, and whether or not he was telling the truth; all of which could be exploited frighteningly effectively by integrated serums and other tools of torture. Additionally, subjects under interrogation by droids often directed their anger and fear towards the mechanized machines; not towards the actual captors. This was often followed up by a later visit from a 'friendly' sentient officer, offering sympathy and establishing a friend-like relationship. Once a rapport had been established, often times the subject would divulge secrets willingly, without requiring direct (and sometimes ineffective) coercion.
Droids were also used in the field of medical science. They offered advantages over Humans in that they could be programmed with a massive amounts of information, none of which would be forgotten, making them extremely cost-effective. Meddroids, as they were known, could store detailed records on hundreds of patients, in addition to exhaustive information on diseases, wounds, and infirmities. Medical droids could analyze wounds or diseases and automatically determine severity of injury, necessary medication, and possible side-effects; all by utilizing sensors and extensive databanks. The emotional detachment of these medical droids was both a blessing and a curse—an advantage because droids did not let emotions interfere with their task, but a disadvantage in that patients could often feel alienated from an impersonal machine. These droids could also operate on patients, using built-in tool extensions and surgical implements. These arm extensions were often modular, allowing rapid change from one medical specialization to another (e.g. from neurosurgery to pediatrics). Because of the high costs associated with comprehensive meddroids, some model lines (such as the DD-13 line or FX-7 models) were not as sophisticated and were usually used as assistants. These medical assistant droids offered some independent functionality but were meant to be used in cooperation with dedicated medical droids, or with organic physicians.
Droids were also used in piloting roles, both directly and indirectly. Some were used for atmospheric flight, while others were used for interstellar navigation. Droids were well-suited for piloting roles for several reasons: they could be programmed with detailed schematics of a ship, they would not panic when under enemy fire, they could maintain tight formations and execute precision attack plans, and, because of their close integration with the ship's computers, they could monitor and repair damage to the ship far more effectively than a Human. Because of their expendability, droid pilots did not require escape pods or other life support systems, saving cost and complexity on the ships they flew.
Droids that were used to handle diplomatic affairs, and aid in translation between various languages, were known as protocol droids. Like medical droids, protocol droids utilized massive databanks, being programmed with thousands of different languages and dialects. Protocol droids were equipped with aural sensors, to receive audio information, and processing units, to analyze and apply necessary programming. Because of their close integration with sentients, protocol droids were often given in-depth personality matrices, allowing for a variety of different personalities and behaviors through a process called metaprogramming.
Droids were used in exploration and scouting roles as well, providing a cheap yet effective mobile sensor platform. Probe droids, often launched by the thousands, would use a one-shot propulsion system to reach the targeted area. Upon arrival, these droids would analyze the area with their powerful sensor arrays; sending the results of the scan back to the droid's creator. Droids of this type were used in many roles: military reconnaissance, deep space exploration, and mineral prospecting (primarily in asteroid fields). Other models were atmospheric-bound, relying on repulsorlift technology to move rapidly and traverse height differentials. Most scout droids carried a similar core loadout—a multiple-spectrum photoreceptor, a magnetic imaging device, a thermal imager, and signals transmission equipment. Some models featured built-in weaponry, such as a blaster, or expansion slots that could be used for a variety of additional sensors or weapons. Some droids also included a self-destruct mechanism to prevent acquisition by others. Because of their clearly defined role and the need to keep the cost per unit down, probe droids were given inexpensive processing units and relatively "dumb" A.I. This resulted in a lack of flexibility and systemic errors when confronted with unknown circumstances not outlined in the computer's parameters. These drawbacks aside, probe droids were very effective in their native role: providing inexpensive but broad sensor capability, regardless of climate, radiation levels, or hostile presence.
In addition to the primary roles outlined above, droids served in a myriad of other, more specialized functions:
Droids were typically treated as property. More advanced droids sometimes received proportionally more respect. Some protested the status of droids as slavery. This was a contentious issue, owing in part to the difficulty of assessing levels of artificial intelligence, and determining which droids if any could be considered properly sentient. Although emancipation of droids was a radical concept, some opposed memory wipes except for very simple droids.
The Naboo considered higher level droids equal as fellow sentients. Under the Galactic Empire, no laws protected droids from abuse and those who showed them respect were looked upon as strange. During the Yuuzhan Vong War (25 ABY–30 ABY), droids were targeted for destruction by the technology-hating Yuuzhan Vong invaders who saw them as abominations.
During the Clone Wars, general dislike for droids was spoken of between clones and their generals, which would regular use such slang as "clankers" or "tinnies" to refer to them.
The father of modern-day droid language is widely held to be Yperio Baobab, whose Bab-Prime revolutionized robotic communication in 200 BBY. The following is a brief chronological list of other droid languages, previous and subsequent.
As a side note, Bab-Prime was also responsible, at least in part, for the droid tendency to develop personalities if not given frequent memory wipes. A hapless employee of the Baobab Merchant Fleet, in an attempt to create a new Bab-Prime algorithm, actually created a personality virus that ran rampant through the galaxy's droid population, exacerbating what was an apparently already existing problem. Ever since this occurrence, the administration of memory wipes to droids became a commonplace occurrence.
The word droid is derived from android which means "man-like." Of course the term is erroneously used for "second degree" droids that have nothing common with humanoids. Droid is the exclusive name for every robotic entity in Star Wars. The name "robot" appears only in primitive (Pre-Republic) droids. However, C-3PO and R2-D2 were referred to as "robots" on one occasion in Star Wars Episode IV: A New Hope.
Droids' legal rights are often a fiercely debated topic among fans.
In one television documentary, George Lucas said that C-3PO--and thus by extension all droids--had no soul.
Early Expanded Universe material sometimes spelled droid with an apostrophe ('droid), short for android.
George Lucas holds a trademark on the term "droid." The miniature 'mech combat wargame BattleTech was originally released under the name BattleDroids, but was renamed due to trademark issues with Lucasfilm.
Pixar Animation Studios' film The Incredibles (2004) contains a reference to Lucasfilm's droid with the large weapon of destruction, the Omnidroid; an apparently unrelated killer droid of the same name also appears in Star Wars Galaxies. The credits of the film give a nod to Lucasfilm.
From Mickey News  (25 November 2004):
Droids were artificial beings created by sentient lifeforms to perform a variety of tasks ranging from maintenance to protocol and servitude. Droids were common throughout the known areas of the galaxy, used by numerous individuals and organizations. Droids came in multiple shapes and sizes, with some built to resemble the physique of Humans, but many droids lacked the ability to think for themselves.
Table of contents
These droids can be configured with combat modules and programmed to attack targets. Health and Damage depends on the quality and quantity of the combat modules installed.
B1 battle droids' heads were designed to imitate the shape of a dead Neimoidian's skull. In this way, they were intended to strike fear into an enemy's heart. In addition, their bodies vaguely resembled those of the Geonosians. B1 battle droids were physically identical to their direct predecessor, the OOM-series battle droid; unlike OOM models, however, they were not color-coded according to function, if any. However, some were painted with different colors to blend into a certain environment. B1s were usually slaved to a central control mainframe located on a remote starship or some other well-defended facility. However, this could lead to massive failure if the central control mainframe was destroyed, such as during the Battle of Naboo, in which Anakin Skywalker destroyed the Droid Control Ship. The monumental defeat at Naboo spurred interest in independent battle droids, and this technique gained ground following the battle. In extreme cases, the droids would deactivate the electromagnets that kept their limbs attached. During the Clone Wars, clone troopers learned to aim at the hips, torsos, and arm joints of the B1s to quickly destroy them. B1s were designed for cheap mass-production. As a result, they were very flimsy and vulnerable, but were capable of swamping an enemy with their hugely superior numbers. Other models, like the droideka, B2 super battle droid, grapple droid, and air battle droid, were more expensive. Battle droids used E-5 blaster rifles, blaster pistols, and thermal detonators in combat. They spoke with a monotonous, slightly high-pitched mechanical voice. The voice varied between units around the time of the Battle of Naboo, but by the end of the Clone Wars, the voices seemed to be standardized.
See: Deed for: Battle Droid
They were more formidable than the Federation's more numerous B1 battle droids for several reasons. They were able to transform into a wheel-like configuration, allowing rapid movement and compact storage. When they encountered their targets, the bronzium-armored droids would unfold into a tripodal weapons platform, equipped with powerful, built-in twin blasters and often personal shield generators. These shield generators were somewhat powerful, capable of deflecting or absorbing any manner of blaster weaponry up to a light artillery bolt, as well as lightsaber blades and physical attacks. Additionally, the effectiveness of these droids was bolstered by the lack of true photoreceptors; instead, droidekas utilized non-visual composite radiation sensors, less likely to be distracted by mere light-based trickery. The original design was made by the insectoid Colicoids of Colla IV, who were displeased by the limitations of Baktoid Combat Automata's basic B1s, and chiefly manufactured there. The Trade Federation used trading in rare meats as a way to ease bargaining with the ravenously carnivorous Colicoids, and were able to get special rates on these normally very costly droids. Before the Federation's defeat after the Invasion of Naboo, these droids were usually slaved to a central computer. This technique fell out of favor in the aftermath of said battle, when they would function independently as the B2 super battle droids did. However, the droidekas on Colla IV were not slaved to a central computer, making them independent. This made them much more expensive and deadlier.
See: Deed for: Droideka
Although 8D8 had been modified by his former master to perform complex starship repairs, his duties in Jabba's droid pool were menial and degrading. 8D8 secretly despised his superior EV-9D9, but nevertheless helped her torture and dismantle dozens of helpless droids.
See: Deed for: 8D8 Droid
See: Deed for: ASN-121 Droid
See: Deed for: CWW8 Droid
Though most Separatist war vehicles were deactivated after the end of the Clone Wars, the dwarf spider droids were re-commissioned through Imperial command and used by the Galactic Empire to enforce the submission of former Separatist worlds, fighting against the remnants of the very government that once used them, with the Stormtrooper Corps using the droids as their mechanical attack dogs. They would remain utilized throughout the Empire's reign, and it was not uncommon to see these droids alongside Stormtroopers at Imperial checkpoints.
See: Deed for: Dwarf Spider Droid
See: Deed for: INS-444 Droid
Cybot Galactica stopped the production of the droid after a charge being held by one of the droids detonated in a mine on Gosfambling. 600 miners died of suffocation in the cave-in. While it was found that the fault lay in the charge, the bad publicity was enough for them to quietly retire the line, though they were made in numerous enough numbers to appear across the galaxy, especially in the Outer Rim.
See: Deed for: LIN Demolitionmech Droid
Originally, the MagnaGuards were programmed with the optimum in combat techniques. As a result, Grievous had their minds wiped and trained them all individually in the seven classic styles of lightsaber combat. Once they were put to use, Grievous would not allow any repairs to be made to the droids, believing that their numerous scrapes and battle scars made them look more intimidating to opponents.
Grievous would often engage his bodyguards in practice fights as part of training, and would often damage them in such fights.
See: Deed for: Magnaguard
Hundreds of Mark IV droids were deployed from Devastator during the Galactic Civil War to scout the planet of Tatooine, where they searched the crowded streets of Mos Eisley in cooperation with Sandtroopers searching for C-3PO and R2-D2.
One such droid interrupted an ASP-series droid assembling what it thought to be an illegal antenna. The ASP droid responded by smashing the Mark IV.
See: Deed for: Mark IV Sentry Droid
During the Boonta Eve Classic of 32 BBY while the racer Ody Mandrell had his pod in a pit-stop, a single DUM-series pit droid was sucked into the engine and thrown out the opposite end of the engine. The droid "survived," (even letting out a cheer of excitement) but Ody's engine did not, costing him the race. Pit droids would also be used to scavenge any reusable rubble from podracers that had blown apart. This action could be quite hazardous, as the droids were likely to be destroyed by functional podracers that were still running the course; the low cost of an individual unit made the loss of a single droid worth the risk.
See: Deed for: Pit Droid
Super battle droids saw use throughout the Clone Wars as soldiers for the Confederacy along with its smaller cousins and the dreaded Droidekas. Though the first super battle droids seen on Geonosis wore an unpainted dull silver tone, many of the droids used in later battles of the Clone Wars were painted dark blue, likely to differentiate them from the red coloration the Confederacy used for its standard battle droids, or perhaps due to varying manufacturers.
Some Super Battle Droids were used as scouts to observe the plains of Geonosis, mostly because of their brute strength and their ability to destroy modest ground targets. This pleased many of the local Geonosians affiliated with the C.I.S., thus sometimes using the B2s as "spire guards."
See: Deed for: Super Battle Droid
See: Deed for: Union Sentry Droid
Four-legged domesticated guard animals are common on countless inhabited planets. The Guardian's similarity to these watch creatures is no accident.
See: Deed for: Guardian Mark II Droid
Utility Droids can have any combination of modules installed including a Combat module.
They were spherical in shape with several large photoreceptors and multiple arms. They had a powerful repulsorlift and were capable of hauling unconscious beings several kilometers. They contained blasters concealed in their bodies. They were illegal for citizens to own, although this was widely ignored in the Outer Rim Territories. In Star Wars Galaxies they are used widely as Combat droids.
Although LE-series droids were about four times more expensive than simple repair droids (such as WED Treadwell), they were much more universal and easier to communicate with. It could not only repair spacecraft and devices, but also modify these and was an ideal walking tool for starship or stardock maintenance. The droid was also able to install the cargo in cargo holds, help with docking operation or pilot swoop bikes, landspeeders or airspeeders. With the proper programming, it could skillfully control even a medium size starship. The protocol abilities allowed LE-series droids to establish contact with spaceport personnel and find the best way to avoid any unnecessary bureaucracy. The droid itself had specialized sensors and scopes, broadband antenna and hologram recorder and projector. It also knew a large variety of tools, starships and other vehicle types and huge amount of parts suitable for them. The skeletal body composition allowed LE-series droids to squeeze inside even the tightest places in almost every type of machinery. The LE-series droid was very popular among spaceport crew members (as a part of staff) and pilots (as co-pilots and counterparts). Many owners gave their LE-series droids names based on their serial numbers.
The Mining Droid MK3 is seen with a bucket of Lava in Episode 3. In Star Wars Galaxies they are often used as Creature Harvesters.
The lightly-armored Viper droid measured 1.6 meters in height with six manipulator arms extending from a central pod. High resolution receivers and sensors covered the domed head—including motion, acoustic, sonic, and seismic sensors, a radiation meter, magnetic imager, and holocam. Information was relayed back to its superiors via a high-frequency HoloNet transceiver. Repulsorlift engines carried the droid across terrain at up to 40 kph, while the arms gathered samples. Vipers were delivered to their targets through single-use custom built hyperspace pods. They were commonly deployed along the perimeters of key strategic star systems and hyperlanes.
Like its forerunners, the R2 was designed to work in and around space vessels as a diagnostic and repair unit. But unlike the clunky R1-series, this rounded, waist-high droid was made specifically to fit in military starfighter astromech slots. This was a radical departure, as previously all such droids had been dedicated government models. The droid's popularity was equal with Galactic Republic fighter jocks as with the general public. When plugged into a T-65 X-wing starfighter, Eta-2 Actis-class interceptor, or similar starfighter, the R2 monitored flight performance, pinpointed and corrected technical problems, and performed power management, optimizing shipboard systems. The unit could store up to ten sets of hyperspace vector coordinates in active memory, and many had the intelligence and experience to perform engine startup and pre-flight taxiing. The R2 operated flawlessly in the vacuum of interstellar space.
Flushed with the success of their landmark R2 launch, Industrial Automaton rushed to capitalize on their new dominance of the astromech droid market. The R3-series astromech droid was designed specifically for use by high-tech government agencies. The R3 was launched almost simultaneously with another niche product, the R4-series agromech droid. Outwardly, the R3 copied its popular predecessor right down to the bright, contrasting color trim on its metal chassis. The obvious difference in the factory unit was its head, a clear dome of durable plastex. The transparent hemisphere gave the droid's internally mounted sensor package greater range and showcased the R3's other major distinction, its newly updated Intellex V computer brain. Over time, however, some unit's original domes were replaced with opaque ones, or painted over carelessly. The Intellex V housed an impressive database with detailed specifications on every vessel in the Republic Navy, and could be readily programmed with additional ship specifications easily. Armed with this information, the R3 worked in cooperation with gunnery crews, security troopers, and naval chiefs of operation aboard capital-scale warships. Though its primary function was as a capital ship astromech, it could still operate as a plug-in droid for starfighters, and could hold up to five hyperspace jump coordinates in active memory. Due to the sensitive nature of the R3's programming, the rather expensive model was sold only to recognized government militaries. The Galactic Republic purchased 125 million of the droids during IA's initial production run, and later the Empire would use R3s aboard Star Destroyers and the Death Star battle stations. Following the fall of the Empire, in an effort to maintain friendly relations with the New Republic, Industrial Automaton's policy restricted it from knowingly selling to the Imperial Remnant or known Imperial factions.
The R4 had the same outward appearance of an R2 or R3 droid below the neck, but to save money on production, items such as the video display screen and miniature fire extinguisher were omitted. The holographic projector/recorder unit was retained, but relocated to the top of the head dome to allow for use of a cheaper, less miniaturized unit with a smaller rotational axis. The droid's Intellex VI computer was advanced, but geared toward common repulsorcraft designs and specs for commercially available space transports. The computer brain was designed with more space between the components, lowering production costs, but requiring a larger head dome, and likewise eliminated many of the function indicators and gadgetry found on other R-series head domes. The R4 was unsuited to the task of starfighter astromech; it could only hold the coordinates for a single hyperspace jump in its active memory, a one way trip for any fighter jock. Jedi Temple R4 units, like R4-P17, were notable exceptions, despite their R2-style dome. The droids were rugged; able to shrug off the nicks and dents common to a working garage environment as well or better than other R-droids. IA was pleased to discover that, with regular maintenance checks, the R4 outlasted its design parameters for operational life, weather endurance, personality matrix stability, and time elapsed between recharge sessions. Mass-market buyers liked the R4, as did the freedom fighters of the Alliance to Restore the Republic. They reasoned that no one would be suspicious of a mass purchase of agromech droids, the way they would be of starfighter ready copilots like the R2. The model's low cost and knowledge of general-purpose vehicles were also greatly appreciated by the resource-strapped Rebels, and soon the droids' conical heads were familiar sights in Alliance bases and Mon Calamari hangar bays. A few R4s, equipped with non-standard magnetic fault sensors, were used by the Galactic Empire to detect flaws and weaknesses in the atmospheric containment fields in hangar bays on board both Death Stars and on Star Destroyers.
The R5-series astromech droid was a line of low cost astromech droids built by Industrial Automaton. Based upon the success of prior astromech models, such as the wildly popular R2-series, Industrial Automaton intended the R5-series to cater to budget buyers at the cost of some functionality. An Imperial medic receives a report from a R5 unit aboard Devastator. Because of their inexpensive construction, however, droids of this series were plagued by a number of design flaws—most obviously, a sullen demeanor and sharp attitude resulting from deficiencies in the machine's personality matrix. Media outlets soon picked up on these errors: Mechtech Illustrated called the R5 model "a meter-tall stack of the worst business decisions you could possibly want." During the Clone Wars, members of the R5-series were used by the Republic for a variety of roles, including use aboard starfighters like the ARC-170 and capital ships like the Acclamator-class assault ship. They weren't quite as commonly used by Rebel pilots because the extra height of the R5 made them a more prominent target in an X-wing's droid socket, although the Alliance would use them in maintenance jobs extensively due to their low cost. Despite this, Wedge Antilles would use an R5 model. After a particularly poor sales year, Industrial Automaton discontinued the R5 series in 22 BBY. To cover losses, the droid manufacturing firm repackaged R2-AG-series and R4-series droids in excess R5 shells. Aboard Imperial warships, R5 units were used to monitor medical equipment such as life support capsules. A number of R5 units were part of the population of ownerless, unwanted, and otherwise abandoned droids inhabiting Kligson's Moon.
These droids cannot enter combat and cannot be equipped with combat modules. They are typically used in a more utility fashion.
Binary Load Lifters were used as labor droids in the Galactic Civil War. They were known for grievous stupidity, but extremely high strength; a living example of the "Macro Muscle, Micro Brain" concept. One CLL-8 ignored that the floor it was piling boxes on was creaking, and even after the whole corner crashed to the next level, it continued to pile boxes. In Star Wars Galaxies, they are seen most often as crafting droids, or Merchant Barkers.
The MSE stood about 25 centimeters tall and ran on six wheels. The MSE droid, although programmed with multiple capabilities, was designed with only a singular function. A modular circuit matrix was installed beneath the droid's boxy shell, and contained programming for one skill. Commonly, mouse droids carried out cleanup and basic repair duties, and could serve in security and communications fields. Since each droid possessed only a single skill, multiple mouse droids could chain together to pool their resources for more complex assignments. Trains of MSE droids could often be seen guiding troops through military installations; this kind of duty required mouse droids to be programmed with complete readouts of their assigned areas. In addition, due to their use in military outposts, MSE units were rigged to melt down if captured, giving the droids a strong self-preservation instinct. They are used for a great many things in Star Wars Galaxies, With their bonus to detonations, many Bounty Hunters, and Smugglers used them.
They were effectively power generators with legs and a very simple AI so they could understand rudimentary commands. They were commonly found on under-developed worlds that did not have an expansive power grid, or in mobile military operations. They often made a low honking noise that sounds like the word "gonk," resulting in the nickname gonk droid or simply gonk. This form of droidspeak was referred to as "Gonkian." In Star Wars Galxies they have a special recharge other droid ability, but it currently is broken. This has been reported fixed on Test Center for the forthcoming GU12.
The typical 3PO-series droid stood at 1.7 meters in height with a humanoid build. Each droid was equipped with a SyntheTech AA-1 VerboBrain and a TranLang III Communications module. These protocol droids were fluent in over six million forms of communication. Some models, such as the pricey E-3POs, also included the TechSpan I module, making it possible to interface with Imperial networks and undocumented technologies of Imperial subcontractors.
The 2-1B series was humanoid in shape. Many of its internal components were visible through a translucent torso sheath. A 2-1B model's arms featured exceptional joint articulation with precision crafted servogrip pincers at the end of each limbs. Sometimes, in certain operations, these pincers could be removed and replaced with multiple arm attachments for various medical tools and software packages for diagnosis and treatment including hypodermic injectors and cutting saws. The droid model was highly advanced and intelligent with its programming being further advanced by some of the top physicians in the Galaxy at the State Medical Academy of Rhinnal, which also integrated heuristic processors. The most useful characteristic of the 2-1B droids was the ease with which owners could update their programming and appendages. A 2-1B droid could easily become specialist in neurosurgery, podiatry, pediatrics, cybernetic limb replacement, and alien biology with a trip to a certified service center. While advanced, 2-1B droids were generally paired with an FX-series medical assistant droid for medical assistance and detailed patient analysis.
The WED Treadwell was a four-armed (with additional sockets available) automaton propelled by a treaded base. The droid's photoreceptors were mounted on a long, thin telescopic stalk, from which protruded various tool-tipped appendages. The standard WED droid had sockets to support up to six manipulators, though variants carried eight or more. These limbs were easy to install and replace, and Cybot Galactica actively encouraged consumers to purchase a variety of appendages for their Treadwells. Despite this versatility, the WED Treadwell was known to be fragile, and the repair droid required much maintenance itself.
All of these droids, save the flight computer, are expended upon use, and have a certain useage number per stack.
After a period of time will return a resource report of a chosen planet to its owner.
Used by Bounty Hunters to track their bounties. Searches all planets for the mark, but must be called from out of town.
Used by Bounty Hunters to track their bounties. Searches current planet for the mark, and can be called from anywhere. Must be outiside to be called.
Used by pilots to store and execute pilot commands.
Used by pilots to store and execute pilot commands.