FANDOM


R2 repair

Hopefully the repair droids can fix it.

This article is actively undergoing a major edit.

As a courtesy, please do not make edits to this article while this message is displayed, in order to avoid edit conflicts. If you wish to know who is working on the article and when the edit session began, please consult the edit history and the talk page.

"What's this, a Mark II Reactor Drone? Haven't used these clunkers in twenty years!"
―Owen Lars[src]

The Mark II reactor drone was a model of utility droid manufactured by Industrial Automaton whose body shell was reused for the R1-series astromech droid.

CharacterisiticsEdit

A second-degree droid,[3] the Mark II reactor drone was a model of utility droid built and programmed for menial labor[2] in the engine rooms of large starships.[6] Featuring a tall,[7] black body shell,[1] its heavily shielded outer casing protected its sensitive internal circuitry[2] from the most intensive radiation.[8] However, it also gave the droid a lumbering, cumbersome appearance.[2] The Mark II reactor drone was equipped with a magfield sensor ball.[4]

HistoryEdit

A successful series manufactured by Industrial Automaton,[1] the Mark II reactor drone's body shell was reused for their R1-series astromech droid when legal hassles prevented the company from directly transforming their P2-series astromech droid into a consumer product.[9] As a result, R1 units were commonly mistaken for Mark II reactor drones.[7]

In the year 0 BBY,[10] Owen Lars mistook[5] R1-G4[11] for a Mark II reactor drone, having discontinued their use on his moisture farm twenty years prior.[5]

Behind the scenesEdit

The Mark II reactor drone was first mentioned in NPR's 1981 Star Wars Legends radio dramatization of Star Wars: Episode IV A New Hope.[5]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

In other languages

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.