• The VOIDRUNNER'S CODEX is coming! Explore new worlds, fight oppressive empires, fend off fearsome aliens, and wield deadly psionics with this comprehensive boxed set expansion for 5E and A5E!

[SWD20] Why can't I play a Battle Droid?

Operator

First Post
The humble Trade Federation Battle Droid... I want to play one in Star Wars D20.

However, according to the Core Rules they have no autonomous functions, being essentially slaved to an orbiting "droid control ship" which controls all of the droids on the surface. However, the highest canon of all things Star Wars - the films themselves - disprove this.

The events of TPM showed us a few odd things about in the TradeFed war droids:

Dumb - The entire droid army ground to a halt when the orbiting droid control ship was destroyed. There is an obvious causal link between the two events, as described by the film's characters who expect the destruction of the orbiting control ship to have this effect.

Smart - The infantry droids have a rank structure, signified by their colour scheme. Some of the droids are commanders. Some of the droids are specialists. This is interesting because there would be no logical reason to designate certain droids as "commanders" if they are all just "dumb terminals" controlled by a central computer.

Smart - The infantry droids have a sense of humour, as evidenced by one droid which makes fun of Qui-Gon in the hangar bay before attempting to arrest him. This is interesting because it suggests that either the droids have local intelligence, or the orbiting droid control ship's central computer was deliberately causing the "dumb terminal" infantry droid to mimic intelligence and humour.

Smart - The droids react to stimuli independently, as seen when the fighter and infantry droids in the TradeFed battleship turned to look at the Republic cruiser landing in the opening sequence of the film. This is interesting because they would have no reason to react in such a manner if they are merely "dumb terminals" being controlled by the ship's central computer which already knows about the cruiser.

Smart - The droids do not know what other droids have seen, as demonstrated in the Theed hangar when the commander droid does not recognize Qui-Gon even though numerous other droids have already been in combat with him. There is no reason that a central computer would make an individual droid act as though it doesn't know what other droids have seen, if they are all in fact controlled from one point.

Smart - The droids talk to one another, as seen by the commanders giving orders to their subordinates. This would be totally inconsistent with the "central control" model.

Smart - The droids need to independently process environmental stimuli, as seen by the fact that individual droids all need to turn their heads to look at enemy targets before firing (something which should be unnecessary if their visual data input and location information is all being processed by a central intelligence).

Dumb - The droid army moved in precise synchronization when deployed during the battle with the Gungan army. This would be consistent with the centralized control model described in the SW1 cross-sections book. Smart - (It is also consistent with really well trained soldiers simply acting in step with each other.)

Dumb - The droids move without any apparent traces of fear or uncertainty whatsoever, and march fearlessly into the line of fire without any apparent concern for their own safety. During the battle with the Gungan army they moved forward in lock-step, marching inexorably toward the Gungan lines and refusing to break formation even when they began taking heavy losses. Smart - (This is consistent with droids being programs not to fear death. We see Clone Troopers, Storm Troopers, Jedi, and the crew of the Tantive IV do the same thing!)

Dumb - Infantry droids are not equipped with a wide variety of weapons, being armed only with ordinary blasters. If they had powerful anti-personnel airburst or chemical weapons at their disposal, they could have quickly eliminated the Gungan armies by simply having infantry droids carry those weapons through the shield barrier and deploy them.

Dumb - Droid tactics are not particularly creative. Against the Gungan theatre shields, they could have enjoyed quicker success with fewer losses by simply calling in an airstrike or orbital bombardment to bring down the shield. A human commander would have called down airstrikes or orbital bombardment to bring down the shield, rather than march his men directly into the teeth of the enemy defenses. A human commander might have alternatively called for heavier weapons to be brought to the field of battle, or for specialized weapons to cut his losses. (Of course, this just proves that the Neimodian Commanders-in-Cheif are dumb, not the droids.)

Mixed - The infantry droids on the planet's surface did not shut down until many seconds after the orbiting droid control ship was destroyed. The ship's bridge and central control section was destroyed first, followed by multiple scenes of pilots cheering, followed by the disintegration of the ship's toroidal section, followed by a quick cut to the surface of the planet where the droids began to shut down.

The infantry droids actually fell apart after the destruction of the droid control ship, as evidenced when Jar-Jar Binks touched one of the droids and its head popped off. Some observers are under the impression that the head merely dropped to its folded storage position, but it actually separated from the droid body and fell to the ground, as can be seen from careful inspection of the film.

Why would the droid army exhibit so many characteristics of independent, sentient robots when they were supposedly mere "dumb terminals" controlled by a distant intelligence? This is a very difficult question to answer. If they are "dumb terminals", then why would they have ranks? Why would they exhibit characteristics of humour? Why would they react independently to environmental stimuli, or need to individually process visual information before reacting to it? Why would they talk to one another? Why would one droid know something that another droid doesn't? All of the above characteristics tend to strongly suggest that the droids do have local intelligence. In fact, it is virtually inconceivable that war droids would exhibit such characteristics if they are indeed mere "dumb terminals". The selfless actions of the droids in combat may seem to refute this conclusion, but it is always possible that their droid brains were hardwired not to consider personal risk, and/or to obey orders without objection.

Another fact which conclusively disproves the "dumb terminal" idea is the fact that they continued to operate for a few seconds without orbital control signals. A few seconds may not sound like a lot, but it is still impossible under the "dumb terminal" model.

So if we have established that they must have autonomous intelligence, why would they shut down with the destruction of the droid control ship? Why would they need a control ship at all? These paradoxes are difficult to resolve, but not impossible to resolve. There are a two possibilities that I can see:

The droids are actually receiving a carrier signal from the control ship, which merely instructs them to continue operating. This may have been designed as a safety measure for the Neimoidians, who would otherwise be hopelessly outnumbered by their opponents in the unlikely event of a droid revolt. A droid revolt seems unlikely, but it is always possible that if the droids are sentient, they might object to their treatment. Another possibility is that the Neimoidians may fear that a competitor might have somehow maliciously reprogrammed the droids to revolt, hence a central point of control. This is a rather poor design decision from many aspects (there must be some better way to deal with the possibility of droid revolt or malicious re-programming), but we should remember that the Neimoidians are businessmen rather than soldiers or engineers. This signal would have a "keepalive" period which would explain the fact that the droids continued to operate for a short period of time, and there might actually been a self-destruct command built into the droids in the event that the keepalive signal was lost, thus explaining the fact that the droids actually fell apart after the loss of the signal.

The army assembled to fight the Gungans was substantially different from the droids on the TradeFed battleships or the units in Theed. Those droids might have been low-end units, as opposed to the higher-end units in Theed which had substantial local intelligence (like normal droids, such as R2 units and interpreter droids). The droids who fought the Gungans certainly seemed to exhibit a lower level of individual initiative. However, this would suggest that some of the droids on the planet (particularly the commander units in Theed) would have continued to function after the destruction of the control ship. According to the novelization, this didn't happen.

Regardless of what happened during TPM, we have clear proof during AotC that the Battle Droids are independent.
 

log in or register to remove this ad

Operator

First Post
Battle Droid Behavious in Attack of the Clones
In the original script for AtoC, a squad of Jedi were sent to find the control ship and shut it down, thus duplicating the tactics of TPM. The squad successfully shut down the control signal, and all the droids in the arena stopped. A cheer went up from the about-tobe-TPK'ed Jedi, but the droids cut the celebration short when they suddenly reactivated and resumed their assault. In the final version of the movie, this scene was thankfully cut. Because this would have been very dumb... It's been a decade since the Battle of Naboo, you don't think the TradeFed would have developed a counter measure?

That there is a countermeasure is not at issue, the question is what is the counter? I think the answer can becan be found in the "C3PO Incident". C3PO's head was attached to a battle droid body, and a battle droid body was attached to C3PO's head. This scene seemed to be meant as (questionable) slapstick humour, which it was, but it also shows us somethign interestign abot Battle Droids. It indicates that droids have twin processing centres!

Consider: the battle droid body was able to seize control of C3PO's head. It was able to coordinate its movements with other battle droids and take shots at Jedi knights, which means that it had control of his eyes and it could see what he saw. It was also able to shout war cries such as "Die, Jedi Dogs!", which means that it had control of his voice box. Conversely, the battle droid head was able to use C3PO's body. It engaged in combat as well as it could (considering the inferior performance characteristics of C3PO's body), and it forced C3PO's body to grab a blaster and shoot at Jedi knights.

But why would a battle droid have two independent processing centres, each of which is obviously capable of doing the job on its own? The answer may lie in the control-ship countermeasure. Let us postulate the following:

The head processor is the same design used 10 years earlier at Naboo, and it shuts down when the control signal is lost. This may be a technical limitation or it may have been a deliberate design decision (giving the Neimoidians a "kill switch" in order to shut down the entire droid army if it ever turns on them).

The body processor is a new design which does not require the control signal. If a special shutdown signal is received from the control ship, it shuts down along with the head processor. But if the control signal merely stops, it assumes that the control ship was destroyed, and it seizes control.

The resulting theory neatly explains everything described or seen in the arena battle with respect to control signals and C3PO:

The battle droid body gets C3PO's head. Its in-body processor does not detect the presence of a battle droid brain, so it assumes that the control ship has been destroyed. It goes independent, using the inputs from C3PO's audio/video sensors to guide its decision-making and movements. At one point it even sends words to C3PO's vox, the (in)famous shout of "Die Jedi Dogs!".

C3PO's body gets a battle droid head, which takes control of C3PO's body because C3PO's body was never really meant to control its own actions without higher-brain functions present. It is able to fight despite the poor performance of C3PO's body, but it is disabled before the control signal is cut off, so we never get to see if it would have shut down as I expect it would have when the control signal stops.

The remaining battle droids shut down briefly when the control signal stops, and then they start themselves up again. This momentary delay would be explained by the switch-over from one processor to the other.

Unless somebody can come up with a better theory, this one seems good for now. If the droids had been designed so that they did not require a control signal at all, there would have been no shutdown (even a temporary one) when the control signal was lost. If the droids had only one processing centre, there would have been no way for the battle droid to control itself while its head could separately control C3PO's body. None of the actions taken by either of the two hybrid droids were consistent with C3PO's intent, so both hybrids were obviously under the control of whichever battle droid component happened to be present.
 


DnDChick

Demon Queen of Templates
With that argument, you could play one in my game, too. lol

Of course, one of the first side quests I'd have ready for you is for your droid to find some way to removed the control module. Otherwise, as soon as a droid control ship came by ... :]

Oh yea, I'd also require that you say "rogerroger" whenever someone gave you a command. If ya wanna play one that bad ya gotta roleplay it, too. :)

Of course, even if that essay fails to convince your GM to let you run one, there is always the old standby of "this droid was found nearly destroyed and restored by a tech specialist and now has an independent brain salvaged from another droid."

But seriously ... excellent work there! Rather a convincing argument. Bravo!
 

Peterson

First Post
First off - impressive essay. Anyone in my group that goes to that much trouble (almost) always gets what they wanted.

Second - according to my copy of D20 Star Wars you can play a super battle droid (the B2), but I'm assuming you want to play a B1 by your essay. Why not attempt to convince the GM to allow you to have a B2 brain in a B1 body - unless it's really all about the "rogerroger" line.

Third - you could always do what I did for a npc. Somehow, a Gunguan brain got transplanted into a B1 body (a la General G). Nothing like hearing "Mesa say rogerroger". :D

Regardless, good luck and it's my hope that you get to play one. If you do, come back and share your adventures.

Peterson
 

Operator

First Post
Oh, a tall, lanky, and skeletal B1 is definatly the type I want to play. And I'd respond to every request with a crisp "Roger-roger." Roleplaying the factory default quirks balanced agianst a few long decades of operational life in ways never intended by the designers is one of the things I most enjoy about playing a Droid.

My group once played a solid two-year game of D6, and little R2-D3X ('Dex') was to become the most feared pilot in the Rebellion. 32 confirmed kills.

I'm thinking a B1 droid that went missing in the wake of the Clone Wars and has drifted from port-to-port in the outer rim, workign as a mercenary, bodyguard, or other heavy for the highest bidder. Basically, your typical bacground for any scoundrel-soldier from the Outer Rim. Add in a few unique quirks:

- A programed dislike of Jedi, the Republic, AND the Empire makes him grousse about all forms of government. But as a soldier droid he can only thrive when subject to a strict hierarchy. (He's the grumbling Private in every WWII movie!)
- Protocol Droids and Astromech are designed for decades of service, and often last a century or so, this colors their personalities and is fun to roleplay. A B1 Battledroid is designed to de dispossible, and mine has lived for decades....
- He's seen combat, a lot of combat, and is thus a season veteran... without any inherient boost in BAB, HP, or Skills!
- He's collapsable for easy storage! (I predict hours of ammusment!)
- He shall be named 'Roger Rodger'!
 

Roudi

First Post
Operator said:
(there must be some better way to deal with the possibility of droid revolt or malicious re-programming)
That probably explains the development of the restraining bolt. Far more effective at controlling fully-intelligent droids (though I'm not sure about the feasability of restraining bolts on an entire ARMY of droids).
 

Peterson

First Post
Operator said:
Oh, a tall, lanky, and skeletal B1 is definatly the type I want to play. And I'd respond to every request with a crisp "Roger-roger." Roleplaying the factory default quirks balanced agianst a few long decades of operational life in ways never intended by the designers is one of the things I most enjoy about playing a Droid.

My group once played a solid two-year game of D6, and little R2-D3X ('Dex') was to become the most feared pilot in the Rebellion. 32 confirmed kills.

I'm thinking a B1 droid that went missing in the wake of the Clone Wars and has drifted from port-to-port in the outer rim, workign as a mercenary, bodyguard, or other heavy for the highest bidder. Basically, your typical bacground for any scoundrel-soldier from the Outer Rim. Add in a few unique quirks:

- A programed dislike of Jedi, the Republic, AND the Empire makes him grousse about all forms of government. But as a soldier droid he can only thrive when subject to a strict hierarchy. (He's the grumbling Private in every WWII movie!)
- Protocol Droids and Astromech are designed for decades of service, and often last a century or so, this colors their personalities and is fun to roleplay. A B1 Battledroid is designed to de dispossible, and mine has lived for decades....
- He's seen combat, a lot of combat, and is thus a season veteran... without any inherient boost in BAB, HP, or Skills!
- He's collapsable for easy storage! (I predict hours of ammusment!)
- He shall be named 'Roger Rodger'!

You are my (droid) hero. Think you can make my next game?

Seriously, that's an awesome idea.

Peterson
 

Gospog

First Post
Agreed. If I was the GM, you would be a battle droid.

Excellent essays.

Will this Battle Droid be a veteran of some of the battles in the movies? At the end of the big battle of Episode I, we see those little droids picking up battle droid parts (assumedly) to be re-used.

One of your droids processors (the head one, according to your theory) could have seen action on Naboo. The other (the body processor) could have seen actio on Geonosis.

Could be a cool tie to the movie and give your GM some plot hooks.
 

DnDChick

Demon Queen of Templates
Better yet, your droid's body could be the very one that was attached to C-3PO's head. Some sort of file/personality transfer took place between 3PO and your battle droid's "bod processor" that gave him just enough independence to break free from the control module when he was rebuilt and given a proper head. ;)


Edit: Come to think of it that wouldn't work ... that droid was cut to scrap by the Nautolan Jedi. Ah well ... still a neat idea. :p
 

Remove ads

Top