Huge Droid Mistake In 'Trouble Brewing?'

By Robert James Freemantle, in Game Masters

Hey guys. I'm getting ready to run Trouble Brewing and I just can't get my head past the so called J9-B8 droid that the book claims is made by Cybot Galactica, makers of 3PO series. The picture clearly shows a protocol droid of the 3PO series, yet I know that J9 droids are insectoid looking, made by a totally different manufacturer and not for protocol.

I can't find any other information on CG manufacturing other types of series like a "J" series. But then I see that it hangs about with an R4 unit too, which makes me think they were being mega lazy with their naming. But as a GM who wants all the details right, it's like a nightmare for me. I have a great picture that I either show to the players and call it a 3PO or show now picture and describe it as insectoid J9 type.

The reason this is a bigger problem is that I have a jawa player in the party that I just know will want to scavenge what it can toward rebuilding it eventually...because...jawa. So you see why I'm being so anal on this.

Edited by Robert James Freemantle

there is no harm in altering the details. Probably, it's a bit of an error (though by no means a Huge Mistake) so you can pretty easily describe the droid you know to be more accurate and name the manufacturer appropriately if it comes up.

My handy "New Essential Guide to Droids" shows J9 series droids are made by Roche, not CG.

Give him a new name.

Obviously this is a glaring error and you should get your money back, and even another free book to make up for your suffering.

kidding

Just change it. THe Adventures are ideas, and do most of the grunt work for you. if you cannot be flexible and do some things off the cuff, you shouldn't be GMing.

Everyone who as done RPGs could tell you horror stories of GMs who were inflexible and couldn't handle player ingenuity to the point it was more of a problem because of the flexibility

GM: The innkeeper gives you the key to a room upstairs and tells you he knows nothing about your quest to find the blue staff

Player: Wait.... how did he know we were on the quest to find the blue staff?

GM: I told you he knows nothing about it

Player: The only reason he would tell us he didn't know anything about it, would be someone telling him NOT to tell us.

Other player: kill him and burn down the inn, just to make sure

^True story^

Since we are sharing: once upon a time, we were playing a canned adventure with a reasonably new GM. We had to recover coordinates of a Rebel Safe World from the Empire. The game has the players captured and the Boss of the Adventure was to parade the MacGuffin up and down in front of us in a cutaway scene. The Jedi in the group? Rolling very, very well, crushed the MacGuffin with telekinesis, removing the coordinates from the Empire's hands and killing the story stone dead.

The GM? He had a blue screen of death. Seriously, the game came to a dead stop for well over an hour while the GM desperately tried to come up with a way to recover. We, in real life, went to the real life store, came back, and he was still "Buh! What do I do." We even gave him suggestions - the Empire had a backup, those wasn't the real MacGuffin - but he couldn't adapt to leaving the book.

Finally the Jedi threw in the towel. "Okay, tell you what. I don't do that. Lets just get on with it" - and the game then proceeded.

So you have to learn to adapt, young grasshopper. Don't be like this guy.

Edited by Desslok

The J9 series does fit the described profile. However, I encourage you to use whatever entertains your group the most. perhaps a gonk-droid-turned-jukebox that speaks in samples from its massive musical database.

Oh I'm a very flexible GM, believe me. Just threw me for a loop in my advance read up...that's what advance reads are for after all! I'm also very new to the system too, as in GM'd about half a session so far.

I will make this a proper bug looking J9 worker drone then.

Since we are sharing: once upon a time, we were playing a canned adventure with a reasonably new GM. We had to recover coordinates of a Rebel Safe World from the Empire. The game has the players captured and the Boss of the Adventure was to parade the MacGuffin up and down in front of us in a cutaway scene. The Jedi in the group? Rolling very, very well, crushed the MacGuffin with telekinesis, removing the coordinates from the Empire's hands and killing the story stone dead.

The GM? He had a blue screen of death. Seriously, the game came to a dead stop for well over an hour while the GM desperately tried to come up with a way to recover. We, in real life, went to the real life store, came back, and he was still "Buh! What do I do." We even gave him suggestions - the Empire had a backup, those wasn't the real MacGuffin - but he couldn't adapt to leaving the book.

Finally the Jedi threw in the towel. "Okay, tell you what. I don't do that. Lets just get on with it" - and the game then proceeded.

So you have to learn to adapt, young grasshopper. Don't be like this guy.

I've had sessions like that. Three of them, back to back to back, in the first three sessions of the same campaign.

  • They killed the droid crime-lord who was supposed to be their contact to join the Rebellion.
  • They decided that the best way to escape a space station was to do a head-on assault on the station's imperial barracks so they could steal some stormtrooper armor.
  • They ditched Bail Organa (one character's 'uncle'), leaving him to the Empire to take the blame for something that they had failed to stop from happening.

Fortunately, in my case, the would-be 'blue screen' moment came at the *end* of each session, giving me a week to recover. Also fortunately, I have more than a few years GMing under my belt.

I've never been sure whether I'm glad or disappointed that the campaign ended after the 4th session, when player's work schedules became incompatible.