As inorganic mechanical beings, all Droids have certain attributes that affect how they interact with their environment and other beings.

Ability Modifiers[edit | edit source]

Droids are nonliving entities, so they do not have Constitution scores. Droids can increase any two of their five remaining Ability Scores by +1 each at 4th level and every four levels thereafter, just like any other character. These increases represent improved heuristics and algorithms that the Droid has developed from experience as well as upgrades to its components undertaken as part of routine maintenance. Droid Ability Modifiers are determined by their Degree and size. A Droid can never have an Ability Score less than 1, regardless of modifications.

Behavioral Inhibitors[edit | edit source]

Droids (Except 4th-Degree Droids) cannot intentionally harm a sentient living being or knowingly allow a sentient living being to be harmed. Furthermore, all Droids must follow orders given to them by their rightful owners, as long as those orders don't require the Droid to harm a sentient living being. Droids with Heuristic Processors can sometimes violate these restrictions by creatively interpreting their behavioral inhibitors.

Ion Damage Vulnerability[edit | edit source]

As electronic constructs, Droids are vulnerable to damage from Ion Weapons. Generally, Ion Weapons have the same effects on Droids that Stun Weapons have on living beings.

Maintenance[edit | edit source]

Droids do not sleep, eat, or breath. However, they do need to enter shutdown mode and recharge for 1 hour after 100 hours of operation. If a Droid fails to do so, it must make an Endurance check each hour (DC 10, +1 per additional hour after the first) or move -1 persistent step along the Condition Track. This persistent condition can only be removed by the Droid recharging for 1 hour.

Memory[edit | edit source]

A Droid's Trained Skills, Feats, and Talents can be reassigned with the Use Computer skill (See Reprogram Droid). A Droid hero can use its own Use Computer skill to perform this reprogramming, but it takes a -5 penalty on its Skill Check. If a Droid is ever subjugated to a complete memory wipe, it becomes a basic model of its type, losing any levels and abilities gained.

Nonliving[edit | edit source]

A Droid is immune to Poison, Disease, Radiation, noncorrosive Atmospheric Hazards, Vacuum, Mind-Affecting effects, Stunning effects, and any other effect that only works on living targets. Droids have no connection to the Force and can't gain the Force Sensitivity feat, or learn Force Powers. Droids do not have a Constitution score, so they don't get bonus Hit Points for having a high Constitution, and they apply their Strength modifier to their Fortitude Defense. Unlike living beings, Droids don't "Die," but they can be disabled or destroyed.

If a Droid is reduced to 0 Hit Points, it is disabled and cannot be reactivated until it is repaired so that it has at least 1 hit point. If the attack that reduced the Droid to 0 Hit Points also exceeds the Droid's Damage Threshold, the Droid is destroyed instead. A destroyed Droid cannot be repaired or salvaged. Droids do not gain an ability bonus to Constitution-based Skill Checks and may not take Feats or Talents with a Constitution prerequisite.

Repair[edit | edit source]

Droids can regain lost Hit Points only through the use of the Mechanics skill (See Repair). A Droid can use this application to repair itself, but it takes a -5 penalty on its Skill Check.

Shut Down[edit | edit source]

A Droid that is Shut Down can take no actions and is effectively unconscious. Shutting down a willing Droid is a Standard Action. Shutting down an unwilling Droid is more difficult, requiring you to Grab the Droid, and then make a Mechanics check (DC = Droid's Will Defense) as a Standard Action while its grabbed. You cannot shut down an unwilling Droid with Locked Access unless it is disabled or otherwise helpless.

Skills[edit | edit source]

Droids normally cannot use any Skill Untrained except for Acrobatics, Climb, Jump, and Perception. A Droid with a Heuristic Processor ignores this limitation.

Droid Systems[edit | edit source]

Droids can have many of their characteristics changed by installing or replacing existing Droid Systems.

Automatic Languages[edit | edit source]

All Droids can speak, read, and process Binary, as well as understand one language chosen by the designer (Usually Basic).

 Additional Adjudicating Droids[edit | edit source]

Reference Book: Star Wars Saga Edition Scavenger's Guide to Droids

Adjudicating Droids can present unique challenges for the Gamemaster. Although they are essentially living machines, Droids cannot be treated as simply another Species or character type. Below are common Droid issues and information on adjudicating them.

Damaged and Destroyed Droids[edit | edit source]

Damaged and destroyed Droids are treated similarly to organic heroes when it comes to damage and death. However, Droids are also machines and can be reassembled or have their data accessed by other means, so they have additional options not available to organic characters. New approaches to damage and destruction are presented below. Information on Droid damage and repair from the Saga Edition Core Rulebook is also included here for convenience.

  • Conditions: A Droid is treated the same as an organic character when it comes to the Condition Track and Persistent Conditions. Unlike organic characters, however, a Damaged Droid might gain a quirk (See Droid Quirks).
  • Destroyed: If a Droid is reduced to 0 Hit Points by an attack that deals damage equal to or greater than its Damage Threshold, the Droid is Destroyed. However, it can spend a Force Point to become Disabled instead of Destroyed.
  • Disabled: When a Droid is Disabled (The equivalent of being unconscious), it moves -5 steps on the Condition Track, falls Prone, and is unable to take any Actions. It remains inert and inoperative until repaired. A Droid that is repaired immediately reactivates and can get up to fight again, but it starts Prone.
  • Repair Droid (Requires Tool Kit): A character with Mechanics as a Trained Skill can spend 1 hour of work and make a DC 20 Mechanics check to repair a Damaged or Disabled droid, restoring Hit Points equal to the Droid's Character Level and removing any Persistent Conditions currently affecting the Droid. A Droid can attempt to repair itself, but it takes a -5 penalty on its skill check.

New Optional Rules[edit | edit source]

The following new optional rules can be included, in whole or in part, in your game to give Droid Heroes some of the versatility seen in the Star Wars films. As with all optional rules, inclusion of the following rules in the game is subject to Gamemaster approval.

  • Sacrificial Appendage: When a Droid would normally be reduced to 0 Hit Points or moved to the bottom of the Condition Track, the Droid can choose instead to have one of its limbs severed. If the droid chooses this option, it is instead moved to the -4 step on the Condition Track, or, in the case of being reduced to 0 Hit Points, it retains 1 Hit Point. The sacrificed Appendage should be a limb rather than a tool that the droid can easily do without. The Appendage can be successfully reattached with a repair check (See Repair Droid). The Droid receives Hit Points from the repair, as usual.
  • Destroyed Droids: Taking into account the method of destruction, the Gamemaster determines what parts of a Droid remain after it is destroyed. Blaster fire or an explosion might scatter small and large pieces around the area. A Droid destroyed by a Lightsaber might have slices or holes burned through its chassis, or large sections of the Droid's appendages might be completely severed. The Gamemaster should also determine which of the Droid's systems, accessories, appendages, or tools are damaged or destroyed.
  • Reactivating a Destroyed Droid: At the Gamemaster's discretion, a character can attempt to salvage and reactivate a destroyed Droid. Reactivating a Droid requires that its Processor, power source, and communication interface must be intact. The battery and communication interface can be replaced or replicated if needed. A destroyed Droid cannot reactivate itself. The character attempting the reactivation must make a DC 20 Mechanics check and work on the droid for 5 minutes.
    • A character can attempt to reactivate a Droid as a Full-Round Action, increasing the DC to 30. If the check is successful, the Droid moves + 1 step on the Condition Track. However, the Droid is still considered to have 0 Hit Points and cannot move, attack, or take any action other than skill checks for skills based on Intelligence, Wisdom, or Charisma.
  • Salvaging a Destroyed Droid: Salvaging a destroyed Droid requires a Tool Kit, time, spare parts, and additional Mechanics checks (See Repair Droid). A reactivated Droid can assist in its own repairs by using the Aid Another Action, although it cannot attempt to repair itself directly. The time required to salvage a Droid can be affected by the level of destruction sustained by the Droid. Repairs might take several hours, several days, or even several weeks, as determined by the Gamemaster. Destroyed Droids usually require spare parts costing 50% or more of the Droid's original cost.

Improvised Droid Tasks[edit | edit source]

Heroes might try to take maximum advantage of the unique resources a droid offers. A Droid's built-in equipment, traits, and unique social status in the Star Wars universe cause Droids and Droid Heroes to be called upon to carry out tasks well beyond their original programming.

When considering an unusual request for or by a Droid character, consider the following:

  • Does the droid have a Heuristic Processor? If not, then the request must be governed by the standards of the Basic Processor or Remote Processor, so the task must be laid out in specific terms. Unless the request is defined in ways the Droid understands, the Droid cannot act beyond its programmed Skills, Feats, special abilities, and tasks. Even if the tasks are clearly delineated, the Droid might perform them poorly or inefficiently or become confused if the task does not proceed as planned.
    • A Droid equipped with a Heuristic Processor is better equipped to handle unusual situations, so it can act on fewer, less specific instructions. Additionally, focusing on the advantages of the Heuristic Processor emphasizes the choice of processor in Droid creation, rewarding those players who select it.
  • Is the request already covered by an existing Talent, Feat, or Droid special quality? Don't shortchange players who select certain Heroic Class, Droid, or Droid Prestige Class Talents and Feats by allowing other Droids to replicate those abilities too often. If it seems reasonable that a given Droid might be capable of an action similar to an existing ability, allow the action to proceed with a lesser chance of success and/or a lesser result than could be gained with the existing ability.
  • Is the request likely to be abused by the player in future sessions, or likely to become exploited regularly? If not, allow the idea to be used at least in this instance. However, if the idea could become an unwelcome addition to future sessions, the Gamemaster can avoid denying its use outright by allowing the character to spend a Force Point or a Destiny Point (If appropriate) for the action. Another option is for the Droid to suffer a Persistent Condition and move -1 or more steps on the Condition Track at the end of the task.
  • Should the task be covered by new Talent, Feat, or special quality? Some tasks generated by players are more appropriately covered by creating a new Droid-degree Talent, Feat, or special quality. If the player creates a wholly customized or new Droid Model, a special quality can be added at the Gamemaster's discretion.
    • If the Droid is an existing stock model, create a Talent or a Feat instead. If the ability seems like something a Droid ought to be able to learn, create a Feat. If the ability seems focused on a trademark task of a particular model or degree of Droid, create a Talent specific to that degree of Droid.
  • Adjudicating simple and complex tasks. If the Gamemaster decides to proceed with the request, he or she should decide what actions, attacks, and skill checks are required for success. Simple tasks are typically covered by one skill check, but unique circumstances might require more time and/or multiple checks. Complex tasks should take multiple rounds with multiple checks.
  • Plan for failure. A Droid that performs a task outside its realm of expertise can make for potentially amusing or unexpected situations if it fails. The Droid might become confused, carry out the next operation without completing the first task, return unexpectedly, call on the owner for clarified instructions, or give up and report the failure. In the middle of a battle or a critical mission, this failure can cause confusion or threaten a mission's success, forcing the heroes to act quickly to resolve the situation. Gamemasters should take advantage of this potentially dramatic or amusing situation.

The Droid that Gained levels[edit | edit source]

In adventuring parties featuring less than five players, adding a Gamemaster-controlled Droid to the party can be a great way to balance the party without having to adjust your encounter design. Many gaming groups can only muster three or four players and a Gamemaster, while the game is designed for a typical group of five players and a GM. Filling those empty player spots with Droids is a nice option, because a Droid can easily fade into the background during noncombat encounters, whereas a living character that does so might seem shallow and one-dimensional. If you decide to include a Droid ally as a means of filling out the party's numbers, you should probably think about the Droid just like you would any other major Gamemaster character, and plan on it being with the party for the duration of the campaign.

You should choose a Droid Model that fills an appropriate niche in the party. Similarly, you should probably think about the kinds of adventures your heroes are going to be going on, and what roles need to be filled. If the party lacks a Pilot, a Pilot Droid seems like a good choice. However, there are other considerations. Some Droids don't do well on adventures due to their forms (Try getting that Wheeled Droid up a long set of stairs). A good option for creating Droids to round out a party of heroes is to use a stock Droid Chassis and then build the Droid from the ground up. This not only lets you build exactly the kind of Droid you need to fill a gap in the party, it unshackles you from the usual physical forms of various Droids.

As the heroes gain levels, so should the Droid. The levels you choose for your Droid should likewise continue to help the Droid fill in the gaps in the party. If the party is short on firepower, the Droid should take levels with a high Base Attack Bonus and good combat Talents. However, you also have another option to consider. If you want the Droid to grow and to develop as an interesting Gamemaster character, consider having the Droid take levels in the Independent Droid Prestige Class. This helps represent the fact that the Droid is becoming more and more unique thanks to its time with a party of heroes at the center of great, galaxy-shaking events.

Community content is available under CC-BY-SA unless otherwise noted.