Hey all, new to forums so here is a question...

What are the rules about Droids?? Not PCs but purchasing them? I saw in the CRB that there is a small list of them w/ their prices on them, but it doesnt say what the "Stock" droid stats are.

For example and Astromech R2 has ... stats

A 3PO droid has ... stats etc.

So what are the starting stats for these guys and how could you incorperate them into gameplay?

Personally I would love that we could customize them, like an Astromech w/

1-B 3-A 4-I 1s in the rest and skills that will make it a Mechanic/Pilot/Slicer

What are the rules on this???

I'd say it would just depend on the circumstances and what your party was looking for.

If the party in my campaign felt like "We need a slicer droid who's good at computers", then I might whip up an NPC droid with a 3 or 4 in Intelligence and a few of the relevant skills, like you described.

Then I'd price it at something that felt like a good fit--I'd look up the prices for droids shown in the book and base it off that.

Then I'd have the PCs find a shop and do some Negotiation to purchase it.

Well as NPCs they follow the same rules for generating NPCs....

The GM decides what the stats need to be to fill the role needed... and that's it.

So if you want an astromech droid, you explain to the GM what you want, roll a Negotiate or Streetwise check vs. the difficulty the GM specifies...and he hands you a droid.... Triumph/lots of Advantage, you get R2-D2, Despair/lots of Threat, you get Chopper.

That helps, but what if we want a specific droid to our specific characteristics and later want to upgrade it like PCs or weapons...what are the rules for that?

I'd guess they'd use the same rules as cybernetics. You can already buy standard equipment and define it as an installed system for droid.

Want it to be better at slicing? Buy it a databreaker and suddenly it's got R2's interface prong.

Want it to have better sensors? Buy it Electrobinocs + General Purpose Scanner.

So if you want an astromech droid, you explain to the GM what you want, roll a Negotiate or Streetwise check vs. the difficulty the GM specifies...and he hands you a droid.... Triumph/lots of Advantage, you get R2-D2, Despair/lots of Threat, you get Chopper.

Or R5-D4

Hey all, new to forums so here is a question...

What are the rules about Droids?? Not PCs but purchasing them? I saw in the CRB that there is a small list of them w/ their prices on them, but it doesnt say what the "Stock" droid stats are.

For example and Astromech R2 has ... stats

A 3PO droid has ... stats etc.

So what are the starting stats for these guys and how could you incorperate them into gameplay?

Personally I would love that we could customize them, like an Astromech w/

1-B 3-A 4-I 1s in the rest and skills that will make it a Mechanic/Pilot/Slicer

What are the rules on this???

As far as stats go, you refered to the Table 12-1 in the Adversaries chapter of the CRB. Those prices are for the various NPCs listed in that same chapter, stats and all. Table 12-1 is on page 409, and the droid stat-blocks are on page 410-412.

I saw those...would those be the standard stats used or can we change them? In other words is that the "Stock" Astromech we can get or can we get a different one?

Those are pretty much just stock versions. GMs are free to do whatever they want. If they want a droid with all characteristics maxed to be available for purchase to PCs for 1 credit, they're well within their right.

I have always wondered about this because I really wanted to have a droid sidekick. I was pretty happy that they have remotes in the new books.

I saw in the CRB that there is a small list of them w/ their prices on them, but it doesnt say what the "Stock" droid stats are.

Okay, I must be stupid - but where the heck is the list of droids in the rule book? I would have figured that it'd be in the gear and equipment somewhere, but I'm not finding it. Someone cite me a page number?

Page 409, you cuddly little penguin, you.

Dunno why, but it's in 'Adversaries'.

Of course, seeing as how many droids are sentient, with even humble gonks capable of feeling affection, fear and pain, it makes one wonder about the morality of buying and selling sentient beings...

Page 409, you cuddly little penguin, you.

Dunno why, but it's in 'Adversaries'.

Of course, seeing as how many droids are sentient, with even humble gonks capable of feeling affection, fear and pain, it makes one wonder about the morality of buying and selling sentient beings...

You can always just buy biological slaves if you prefer.

Page 409, you cuddly little penguin, you.

Dunno why, but it's in 'Adversaries'.

Of course, seeing as how many droids are sentient, with even humble gonks capable of feeling affection, fear and pain, it makes one wonder about the morality of buying and selling sentient beings...

You can always just buy biological slaves if you prefer.

Ew. Too much maintanance.

I'm currently thinking about rules for building a droid. My wife's character wants to build one, much like Anakin did with Threepio. I think it should totally be allowed as long as the PC can collect the parts. Rather than complex rules, I'm thinking an Average mechanics check once the parts are collected. Then I'll start with a base NPC droid of the type the PC wants to build, and raise/lower stats according to the Mech roll results.

I wonder if the Technician book will have more about droids.

That sounds like a good way to start, Grimmshade. I kinda imagine that Anakin built C3P0 from a standardized set of parts and schematics that might have been collected over time. He's a basic factory-style protocol droid, but he just happened to be assembled from scrounged and purchased parts.

Page 409, you cuddly little penguin, you.

Dunno why, but it's in 'Adversaries'.

Of course, seeing as how many droids are sentient, with even humble gonks capable of feeling affection, fear and pain, it makes one wonder about the morality of buying and selling sentient beings...

You can always just buy biological slaves if you prefer.

Ew. Too much maintanance.

No kidding. I cant be bothered to clean the cat box, let alone pick up after a slave!

(Thanks, M. I was a stupid head last night)

These aren't the droids you are looking for...... Had to be said

I am still trying to figure this out. I plan on droids being a big part of my characters future but not sure exactly how to implement them. Would they kind of be a secondary PC you control?

Example: I really loved the relationship Luke had with R2. What I want is for my character to have that kind of relationship with a remote. Sadly the in the new book the remote is only a sight seeing tool really. But if I want to upgrade it so it can slice into computers... not sure how that would work.

Since anyone can buy a Droid with the prices in the rulebook, or use make up rules to build one, I have no problem just letting the PC's have an NPC droid in their crew. I'd just use the NPC stats.

As for adding things to droids, upgrading, etc., I think I'd use the weapon and vehicle modification rules as a basis, and go from there. Certainly it would require money and/or parts and a Mechanics roll (or computers for the brain.)

Adding something to a droid that could be purchased separately in the book anyway (say a scanner or something) isn't really going to unbalance the game, so just narratively make it part of the droid.

Since anyone can buy a Droid with the prices in the rulebook, or use make up rules to build one, I have no problem just letting the PC's have an NPC droid in their crew. I'd just use the NPC stats.

As for adding things to droids, upgrading, etc., I think I'd use the weapon and vehicle modification rules as a basis, and go from there. Certainly it would require money and/or parts and a Mechanics roll (or computers for the brain.)

Adding something to a droid that could be purchased separately in the book anyway (say a scanner or something) isn't really going to unbalance the game, so just narratively make it part of the droid.

True enough. But with the remote I would effectively be turning it into a droid when before its basically treated as a piece of equipment. Granted the only thing I would want it to be able to do is slice computers, like R2D2 did. Thinking about it... it might be better if I simply narrated it and simply had it giving me a boost die?

A Droid could technically have the remote as a "built-in" piece of gear. Basically it would be an extension of the Droid.

A Droid could technically have the remote as a "built-in" piece of gear. Basically it would be an extension of the Droid.

True, but I think price wise I think my best option is to have a remote and upgrade it so its more of a multitool. I probably won't be able to buy an actual droid for a while, but as soon as we get to a brake point I can get a remote and depending on if the GM permits me to upgrade the remote.

What's the deal with the naming conventions of the R-model astromech droids? R2 was clearly top-shelf in Episode 1, but during the clone wars Mace Wendu has an "R6." R2s traitorous replacement was that golden R3 model for a couple of episodes, which is feasible, but unless there's a naming thing going on when owners customize their droids (+1 to naming after each major update) I don't see a system behind different surnames for droids that are the same model. Narratively it makes sense to have R2 be the R2, since having several of them in one scene would confuse things, but if one refers to it as an R2 unit there could be an R2-A1 or R2-Z9 or any number of name mixes to ensure that we don't have to wonder why a droid 4 generations in advance is working next to its not-significantly-younger "sibling."

I have a friend that actually explained this to me. I'll see if I can find out from him where he got his info.