Editing Droid House Rules (section)

==== Developing a software package ====
Characters can develop skill software themselves instead of buying it.  Proficiency in the skill helps develop good software but is not required.
{| class="wikitable"
|-
! Die Code !! Time Required !! Die Code !! Time Required !! Die Code !! Time Required
|-
| 1D+1 || 1D days || 5D+1 || 4D+1 weeks || 9D+1 || 3D+1 months 
|-
| 1D+2 || 1D+2 days || 5D+2 || 4D+2 weeks || 9D+2 || 3D+2 months 
|-
| 2D || 1D weeks || 6D || 5D weeks || 10D || 4D months 
|-
| 2D+1 || 1D+1 weeks || 6D+1 || 5D+1 weeks || 10D+1 || 4D+1 months 
|-
| 2D+2 || 1D+2 weeks || 6D+2 || 5D+2 weeks || 10D+2 || 4D+2 months
|-
| 3D || 2D weeks || 7D || 1D months || 11D || 5D months
|-
| 3D+1 || 2D+1 weeks || 7D+1 || 1D+1 months || 11D+1 || 5D+1 months
|-
| 3D+2 || 2D+2 weeks || 7D+2 || 1D+2 months || 11D+2 || 5D+2 months
|-
| 4D || 3D weeks || 8D || 2D months || 12D || 6D months
|-
| 4D+1 || 3D+1 weeks || 8D+1 || 2D+1 months || 12D+1 || 6D+1 months
|-
| 4D+2 || 3D+2 weeks || 8D+2 || 2D+1 months || 12D+2 || 6D+2 months
|-
| 5D || 4D weeks || 9D || 3D months ||  ||  
|}
As was already observed, current technology limits the "Die Code" a Droid can acquire through programming to 12D+2.<br />

"Time Required" is the time needed to develop a software giving the Droid "Die Code" in a skill.  If more than one character is working on its development, a modified version of the Combined Actions rules (second edition rulebook, page 69) is used.  The project leader rolls on the Command Difficulty table to find out how many characters could be commanded if they were available.  The time needed is "Time Required" divided by the minimum of that number and the number of character really available. <br />

'''Example:''' Arnold no longer has the money to buy the Dodge software so he's going to try to develop it with the help of his team-mates Alix and Vaurianne in order to raise R2rien Dodge skill to 4D.  Sara, who owns the Droid, is not happy about it and wants to supervise the project.  Alix has Droid Programming / Repair 2D, Arnold has 2D+2, Vaurianne has 3D+2 and Sarah has Command 2D+1.  The average of Alix, Arnold and Sara's Droid Programming / Repair skill is close to 3D. With a roll of 14 (due to a lucky wild die) Sara beats a Moderate difficulty and could have co-ordinated the work of up to six characters; as only three are available, the project will take 1D weeks divided by 3. <br />

'''Example:'''  Assume that Sara rolls only 8: she would beat an Easy difficulty and only be able to co-ordinate the work of two characters.  Alix, Arnold and Sarah will have to work full time for 1D weeks divided by 2.  A lot of time is wasted  because of bad decisions, sterile progress meetings or simply lack of co-ordination.  After the development time has elapsed, one character and the gamemaster make an opposed roll.  The gamemaster rolls the new Die Code the character are trying to program into the Droid while the character rolls the average Die Code in Droid Programming / Repair of all the participants and adds the number of dice of the best character in the skill being programmed. <br />

'''Example:''' Alix has Dodge 5D, Arnold has 5D+2 and Vaurianne has Dodge 3D+1.  The average of their Droid Programming /  Repair skill is closest to 2D+2, thus one of them should roll 2D+7.<br />
{| class="wikitable"
|-
!   !!   !! VE !! E !! M !! D !! VD !! H !! New Die Code !! Debug
|-
| P >= G||  ||  ||  ||  ||  ||  ||  || As expected ||  
|-
| P < G <= || P + 2 || 1 || 2 || 3 || 4 || 5 || 6 || As expected || 0.5
|-
| P +  2 < G <= || P + 4 || 1 || 2 || 3 || 4 || 5 || 6 || 1 level lower || 1.0
|-
| P +  4 < G <= || P + 6 || 2 || 3 || 4 || 5 || 6 || 6 || 1 level lower || 1.5
|-
| P +  6 < G <= || P + 8 || 2 || 3 || 4 || 5 || 6 || 6 || 2 level lower || 2.0
|-
| P +  8 < G <= || P + 10 || 3 || 4 || 5 || 6 || 6 || 6 || 2 level lower || 2.5
|-
| P + 10 < G <= || P + 12 || 3 || 4 || 5 || 6 || 6 || 6 || 3 level lower || 3.0
|-
| P + 12 < G <= || P + 14 || 4 || 5 || 6 || 6 || 6 || 6 || 3 level lower || 3.5
|-
| P + 14 < G <= || P + 16 || 4 || 5 || 6 || 6 || 6 || 6 || 4 level lower || 4.0
|-
| P + 16 < G <= || P + 18 || 5 || 6 || 6 || 6 || 6 || 6 || 4 level lower || 4.5
|-
| P + 18 < G <= || P + 20 || 5 || 6 || 6 || 6 || 6 || 6 || 5 level lower || 5.0
|-
| P + 20 < G ||   || 6 || 6 || 6 || 6 || 6 || 6 || 5 level lower || 5.5
|}
When the Droid  Programming / Repair roll is not made, there will always be a chance when the Droid uses the skill that he will hit a bug, get caught in a loop, shut itself down, anything. "VE", "E", "M", "D", "VD" and "H" give the number that must be equalled or exceeded with a roll of one die every time the Droid uses the skill; if that roll is not made, something happen and the Droid simply cannot use the skill. <br />

'''Example:''' The gamemaster rolls 4D and gets 17, Arnold rolls 2D+7 for a total of 13.  Not entirely successful, but it could have been worse: R2rien Dodge is now 3D+2; furthermore every time the Droid tries something more complicated than a very easy Dodge, he may have problems. <br />
Example: While under a tree in the jungle, R2rien spots a gadaji nut falling from the tree and tries to dodge it.  The gamemaster rules that it is a moderate action and rolls 6; it is higher than 3, thus the Droid can attempt to Dodge the nut.<br />

'''Example:''' A few days later, the party is ambushed by bounty hunters. Lacking fighting  skills R2rien tries to flee and  declares a full Dodge.  One bounty hunter with a 6D Blaster is firing at him at medium range, the difficulty is 12 and he rolls 27.  R2rien must roll 16 at least for his Dodge or he's hit by the bounty hunter.  That correspond to a difficult Dodge; thus, unless the gamemaster rolls 4 or more on one die, R2rien shuts itself down and will not move until he is restarted.  Of course, he will also be hit by the blast.<br />

Fixing a bugged software is done through the same procedure except that the time required is not rolled; instead "Debug" is used as the result of each dice.  Even though there is no guarantee that the fixed software will be free of bug,  use of state of the art development method make sure that it will not get worse.  <br />
'''Example:''' the time required to fix R2rien Dodge ix 3 x 2 = 6 weeks. After 6 weeks, both the player and the gamemaster roll again.  If the player rolls higher, R2rien Dodge software is fixed; he now has 4D. If the gamemaster does not beat the player by more than 3, some bugs have been fixed, but not all; R2rien Dodge is now 4D but he keeps failing from time to time.  If the gamemaster beats the player by more than three, nothing changes. <br />
The character points cost for raising a skill by one pip is only half the number of dice of the current die code rounded up.  Having a bugged software fixed doesn't cost the Droid any character points. Restarting the software development from scratch sometimes takes less time than fixing the existing one but that costs the Droid more character points. <br />

'''Example:''' a few month later, Arnold wants to raise R2rien Astrogation from 5D to 6D.  After 5D weeks, the gamemaster rolls 6D for a total of 34. Arnold rolls 2D+2 and adds 3 to the roll (he has Astrogation 3D); he gets a 13 and changes that score into a 21 by spending 2 character points.  R2rien  has to spend 9 character points, his Astrogation is still 5D but fails from time to time now while it never did before.  Arnold can either try to develop the software again in 5D weeks at the expense of 9 extra character points from R2rien or fix it in 5 x 3.5 = 17.5 weeks at no character point expense. <br />