#RPGThursday Retrospective – My #StarWars Saga (Star Wars RPG Saga Edition, 2007)

Courtesy Wookiepedia

Between 2007 and 2009 I was stationed overseas, and therefore had limited access to RPG items. I had put a lot of my items in storage so I did not have a strong library to draw upon. I was looking for a new RPG game, but had resigned myself to having to wait until my return stateside or use DriveThruRPG (a risky proposition given the internet security of the time). One day I was in the Base Exchange and saw a new book on the shelf, Star Wars Roleplaying Game – Saga Edition Core Rulebook. The book caught my eye partially because it used a very different form factor (9″x9″) and had a beautiful gold Darth Vader on the cover.

Forward – Going Back?

The Forward was very interesting because Chris Perkins claimed this was the latest iteration of a Star Wars RPG and the first to span the entire six-episode saga (p. 5). This was news to me; I had missed the earlier excellent West End Games Star Wars RPG – although interestingly I had the associated Star Wars: Star Warriors star fighter combat board game – and the original WotC version.

Saga Engine

In terms of the game engine, Star Wars Saga (SWSaga) technically used Wizards of the Coast d20 Modern. In reality, it would later become apparent SWSaga was an interim step between d20 Modern and Dungeons & Dragons 4th Edition. I had tried to use the d20 Modern engine before, but had only limited success. This time around I committed myself to learning the system and playing with it. In concept it sounds so easy:


The Star Wars Roleplaying Game uses a core mechanic to resolve all actions. This central game rule keeps play fast and intuitive. Whenever you want to attempt an action that has some chance of failure, you roll a twenty-sided die (or “d20”). To determine whether your character succeeds at a task (such as an attack or the use of a skill, you do this:

  • Roll a d20.
  • Add any relevant modifiers.
  • Compare the result to a target number.

If the result equals or exceeds the target number (set by the GM or given in the rules), your character succeeds at the task at hand. If the result is lower than the target number, you fail. (p. 9)

So simple, and easy to figure out. Except that d20 is built on breaking the rules. Feats and Talents are mechanical ways characters can act in addition to the rules. This concept took a long time for me to fully understand because d20 appears internally inconsistent since it emphasizes – at least to me – ways for characters to “break” rules.

Characters with Class

Unlike the Traveller RPG system I was so familiar with, character generation in SWSaga uses classes. Coming as I do from a Traveller RPG background, classes have always felt foreign to me. That said, I dug into SWSaga and built many characters, putting together their Attributes and Skills and Feats and Talents (oh my!).

I struggled again to understand what I was doing. Looking at it critically, I think I struggle with character generation using classes in d20 because I subconciously want to see a life path progression system, not a video game-like leveling up of characters.

May the Fourth Be With You

Combat also proved challenging. As it soon became apparent, SWSaga was moving towards D&D 4th Edition, in which combat has sometime been described as a tabletop video game. On one hand the combat system was a bit familiar, being that it drew heavily from WotC’s Star Wars Miniatures game that I played with my boys. But at the same time it was different. A different part that I found very confusing was Conditions (p. 149). I think I found Conditions confusing not because of what they represent, but how they were presented in the book. Going back now (and after many other narrative games) I see how conditions attempt to explain a non-damage situation in terms of a mechanical game effect. At heart it is not really a difficult concept to imagine, but I found it was not communicated very well by the unlabeled Condition Track on p. 149.

Force…and Destiny

For an RPG about Star Wars, I found The Force rules convoluted and disorganized. In particular, it would seem to make sense to look at Chapter 6: The Force for the relevant rules but within that section one is referred to the Use the Force skill in Chapter 4 (p. 77). Looking at Chapter 6 today, I can see that The Dark Side, and especially Dark Side Transgressions, were a stab at non-mechanical (i.e. narrative) means of explaining how to avoid falling to the Dark Side. To further add to the confusion, Destiny Points (found in Chapter 7: Heroic Traits) were included as an optional form of game economy but I rarely used them because the narrative effect was limited – whatever narrative action was there had been reduced down to a table lookup mechanic (seven effects, three of which were Force-related)(p. 113). From today’s perspective, and after having now played Fantasy Flight Games Star Wars Roleplaying Game, I see how SWSaga Destiny is an earlier form of FFG Star Wars’ Obligation / Duty / Morality mechanic. However, the implementation in SWSaga is weak; the relationship between a character’s Destiny (p. 112) and the tangible Destiny Point is neither detailed nor strong.

Sad Saga

As much as I tried, I just could never get SWSaga really going. It was not for lack of effort on my part; I eventually bought EVERY SWSaga book in the series. In the end though, I found the setting suffered from the same bloat and canonicity battles that plague the Traveller RPG community – that is, the setting is too detailed and too well defined that it is easy for a GM to get locked into a certain course of action. Indeed, after purchasing every book in the SWSaga series, I realize that I had too much information (although the entire collection is a good ode to Star Wars Legendsbut in the end the rules were too bloated for me to handle.

A New Start

So committed was I to turning over my d20 leaf that I even bought the Dungeons & Dragons Roleplaying Game Starter Set (2008). I prepared to plunge into the world of D&D after avoiding it for 30 years. I really wanted to try to play d20. I thought my boys would want to play D&D (both read many of the Rick Riordan fantasy series). In the end though my inherent dislike of the fantasy RPG genre, coupled with a feeling that D&D 4th Edition was a tabletop video game, put a relatively quick end to that little gaming excursion. As much as I tried to make SWSaga my new science fiction RPG, it just didn’t work. As much as I love Star Wars, playing in the setting using SWSaga felt like I was getting too hemmed in. Even with the option of playing in multiple eras, it still felt restricted (it didn’t help that my boys were huge prequel and Clone Wars fans – two of my least favorite eras – and they wanted to play in those times whereas I didn’t).

The Saga Narrative…NOT!

In preparing for this retrospective, I pulled out the Core Rulebook and tried to look at it independently of the other books in the series. Much like the Traveller RPG community has arguments over the Little Black Books, I can see how the Core Rulebook – by itself – is not a bad game. Setting aside, everything needed to mechanically play a Star Wars adventure is included. Looking at it with my eyes today, I also see how SWSaga attempts to reduce many narrative play elements to mechanical effects. Nowhere is this better seen than in Talents and Feats. Unlike Skills which represent various abilities (be it trained, natural, or luck – p. 57), Talents are particular to a character class and Feats are special features that give characters new or improved capabilities (p. 79). Thus, the classic Star Wars character Han Solo (p. 255) gets classed as a Scoundrel (p. 45.) with the Spacehound Talent (p. 47) – giving him proficiency with starship weapons – and the Quick Draw Feat (p. 87) because, after all, Han shot first! All of this is very descriptive of the character, but together it reduces the character to a set of well-defined – even narrow – mechanical effects. The Core Rulebook example of Han Solo has him with four Classes, seven Talents, eight Feats (several of them in multiple areas) and six Skills. The implied game limitation it that without the “right” Talent or Feat, the action is unachievable by a character regardless of the player’s desire. Thus, instead of “playing” their characters, players start trying to gain/spend XP in pursuit of the right Skill/Talent/Feat to justify a desired action. To me, this is the opposite of narrative play.

So my search for a new RPG continued, and my next two RPG purchases brought back an oldie while introducing something new.

Star Wars Roleplaying Game: Saga Edition Revised Core Rulebook by Christopher Perkins, Owen K.C. Stephens, and Rodney Thompson; Copyright (c) 2007 Lucasfilm Ltd & (R) or TM Where Indicated, All Rights Reserved. Used Under Authorization. Some rules mechanics are based on the Star Wars Roleplaying Game Revised Core Rulebook by Bill Slavicsek, Andy Collins, and ID Wiker, the original DUNGEONS & DRAGONS (R) rules created by E. Gary Gygax and Dave Arneson, and the new DUNGEONS & DRAGONS game designed by Jonathan Tweet, Monte Cook, Skip Williams, Richard Baker, and Peter Atkinson. This Wizards of the Coast game product contains no Open Game Content.



#FourRPGs of Influence

Reading the #FourRPGs hashtag on Twitter is a great nostalgia trip, as well a thinking challenge. Here are the four RPGs that most influenced me.

From tasteofsoundsfiles.wordpress.com

#1 – Classic Traveller (Published 1977 – discovered 1979)

Anybody remember the game store Fascination Corner in Arapahoe Mall in the Southeast suburbs of Denver? It was there I bought my first war-game, Panzer, by Yaquinto Games in 1979. Soon after that, I found a little black box with a very simple logo. The game was Traveller, and it was a role-playing game. Being a huge Star Wars fan, I just had to have the game. This was my gateway into RPGs. Although I had friends who played Dungeons & Dragons, I didn’t (fantasy didn’t catch my attention then, and to this day still doesn’t). I have never looked back since.

I actively played RPGs until the mid-late 1980’s. After college, my job and family didn’t really give me the time to play. Instead, I became a bit of a collector. I tried to keep up with Traveller (buying Marc Miller’s T4 and later the Mongoose Traveller versions). I tried other Somewhere in the mid-2000’s, I discovered DriveThruRPG, and started building an electronic collection of games that I had missed. Being a huge Traveller RPG fan, I stayed with GDW RPGs for the longest time. Sure, I dabbled in other systems (like the James Bond 007 RPG), but I really tried to stay away from Dungeons & Dragons. I had tried my hand at D20 Modern, invested heavily in the Star Wars: Saga Edition, and even looked at Savage Worlds, but none of then really captured my interest.

From en.battlestarwiki.org

#2 – Battlestar Galactica (Published and discovered 2007)

Being a huge fan of the show, I just had to have Margret Weis’ Battlestar Galactica RPG. I was immediately sold on what is now known as the Cortex Classic System (which, in retrospect, is not so different from Savage Worlds). The Battlestar Galactica RPG was a major turning point for me because it was with this game that I truly embraced designs beyond the Classic Traveller system. The Plot Points system, i.e. a tangible game currency for the players to influence the story, was a major break from my previous gaming philosophy. I realized that I was too fixated on systems like Classic Traveller, with its many sub-games, which is very wargame-like and not actually a great storytelling engine. I continued to follow the Cortex system, and these days really enjoy the Firefly RPG using the Cortex Plus system.

From en.wikipedia.org

#3 – Star Wars: Edge of the Empire (Published and discovered 2013)

While Battlestar Galactica started me on the path to narrative RPG play, I didn’t truly arrive until Star Wars: Edge of the Empire. I had got the core rule book and the Beginner’s Game and tried to play with my boys. But at first I just didn’t “get it.” What do all those funny dice really mean? One day I discovered the Order 66 podcast, and listened to their advice on Triumph and Despair. At that moment it all clicked. From then, I was sold on the the system and strongly believe that this game is the best marriage of theme and gameplay. That said, I have to say that the later volumes of this game system, Age of Rebellion and Force & Destiny don’t hold my interest as much as Edge of the Empire does.

From evilhat.com

#4 –Atomic Robo (Published and discovered 2014)

After Edge of the Empire, I started looking for other narrative RPGs. Somehow, I happened across a copy of Atomic Robo. I picked up the game (mostly on a whim) but after reading it was so intrigued by the gaming possibilities. As fortune would have it, I also discovered a Bundle of Holding that had many FATE products. I discovered I had been missing out on a great game system. Now, in addition to Atomic Robo, I enjoy Diaspora (FATE 3.0) and Mindjammer (FATE Core). I have even played a few games using FATE Accelerated with the boys, much to their (and my) enjoyment.

Truth be told, these days I pay much more attention to the “game engine” than the actual game. I admit that my favorite “game engine” these days is FATE Core. That said, I still enjoy Traveller (and even the much-maligned Traveller 5) although the newest Mongoose Traveller Second Edition is not impressing me.

RPG Thursday – Edge of the Empire Reconsidered

Courtesy podbay.fm

I am a latecomer much of the new media. In particular, I find many podcasts are too long and on subjects that only marginally interest me. With Fantasy Flight Games taking on the Star Wars gaming license, I revisited an older podcast, Order 66, to see what the gamer community had to say. I’m glad I did because Order 66 has forced me to reconsider my opinion of Star Wars: Edge of the Empire RPG.

Order 66 started out as support for the d20 version of the Star Wars RPG, specifically the Star Wars: Saga Edition. I was first surprised to find that Order 66 has reinvented itself in support of the new FFG version of the game. This made me suspicious; are they nothing more than company hacks or do they really like the new system? What I quickly found out is that GM Mike and GM Dave are alot like me; eager to learn the new system but hesitant to jump in fully.

What finally convinced me that Edge of the Empire (EotE) has more going for it than I gave it credit for was Episode 2 – Beginner Box, Veteran Style. With this podcast I finally really understand the power of the EotE core mechanic – all those colorful dice and numerous symbols. What really grabbed me was the advantage-threat and triumph-despair conditions. I like how the rules actually assign narrative control. For instance, the player character (PC) rolls to throw a rope across a ravine. The roll is success with advantages. The player then narrates the success (subject to GM approval). In this case it might me “the grapnel holds, and wraps around twice making a very strong anchor.” On the other hand, if the roll was a success, but with threats, the GM could explain “the grapnel holds, but it looks a bit precarious as only one hook is actually caught.”

The podcast also made it clear that the core mechanic supports a highly cinematic version of the Star Wars Universe. The descriptions of game events shows that the combination of skills and fluid initiative makes for fast, pulp-like science fiction action. Sure, blasters are deadly but those minion troopers can’t shoot straight anyway (just like the source material)! This means the game should be FUN for those playing it. A major consideration as I give thought to using this game for a campaign with my kids.

The thought of a shared narrative between the GM and players is also highly appealing to me, especially as I consider using EotE as a game for my kids. The shared narrative mechanic could be a great mechanism for drawing out my son with Autism Spectrum Disorder (ASD) as it could draw him out and get him to participate more and exercise his imagination.

RPG Thursday – A Retrospective Look at The Babylon Project

Courtesy RPG Geek

Not long ago, I was in a (sometimes) FLGS and saw a whole slew of Mongoose D20 Babylon 5 RPGbooks. Having seen this sit on the shelf for over a year, I approached the staff and was able to make a deal to get a nice discount on a bulk buy. All the books I purchased were source books covering races or campaigns; I don’t have the Mongoose Babylon 5 D20 rules nor do I want them given they were based on Dungeons & Dragon Third Edition. What I do have is Mongoose Traveller Universe of Babylon 5 and the much older Chameleon Eclectic Entertainment, Inc. The Babylon Project.

I actually didn’t remember much of The Babylon Project and never actually played it with a group.  I do remember thinking the combat system was “complicated.”  I recently took the time to reread the rules. In doing so, I now have to reconsider the game and give it more credit than I had previously.

In terms of production values, the book was ahead of its times. Full-color pages make it rich looking, even if some of the art is of marginal quality (a mix of photos from the series and artwork inspired by the same). Today people would scream for a low-ink version for print-at-home.

I remember not liking character generation. Of course, I had grown up on Classic Traveller  making many of the concepts in The Babylon Project seem foreign. Character generation in The Babylon Project uses a combination storytelling and point-buy approach and is done in three phases. In the first phase, the player uses storytelling aspects to create a character concept and basic history. This in turn leads to adjusting the 13 attributes that define your character. Attributes are rated 1-9 with each race having a typical attribute value. Players can adjust the typical attributes based on the concept and background but for every attribute raised another has to be lowered. The second phase – childhood – has the player answer another set of questions which guide picking Learned Skills and Characteristics (an early version of the Savage Worlds or Cortex System advantages/hindrances). This same process is repeated in a third phase – adulthood – which again gains Learned Skills and more (or changed) Characteristics. This system was very much NOT what I had grown up with in Traveller or my other RPGs of this time like FASA’s Star Trek: The Roleplaying Game or the first edition of Prime Directive. At the time, I think it was just too different for me to be comfortable; now I see it for what it is – a well thought out, guided, lifepath character generation system.

The adventure and campaign system focuses less on episodic events than on creation of a story arc. The Babylon Project certainly tries to match the grand, sweeping, epic feel of the series. The mechanic used is the Story Chart which the Gamemaster uses to loosely chart out the path of the campaign. The Story Chart uses four basic symbols to lay out an adventure:

  • Non-exclusive Chapters: Events which do not directly relate to other events in the story; can be worked into story almost any point to uncover key pieces of information, encounter non-critical NPCs, or experience important scenes.
  • Exclusive Chapters: Events which the characters must experience and can only happen once; these change the nature of the story and cannot be revisited or reversed.
  • Independent Chapters: Not critical to the overall puzzle, but may help.
  • Information: The flow between chapters that lead from one to another.

Like character generation, I think at the time I viewed this (again) as too different to understand. Today, I can see the designer’s intent and zeal to get closer to the grand, sweeping, epic feel of Babylon 5. Unfortunately, even today I don’t often see a similar approach in other games that could use it like Star Wars Saga Edition or even Battlestar Galactica.

The core Game Mechanic is actually very simple. Players compare Attribute+Skill and Specialty+/- Modifiers +/- a Random Modifier against a Task Difficulty set by the GM. To use the examples from the book:

Jessica is attempting to bypass the reactor control circuitry. The bypass isn’t particularly difficult, but Jessica is working by flashlight in zero-G. Dana specifies that Jessica will take the necessary time to make sure the job is done right. Taking all of those factors into consideration, the GM decides that the task is Difficult, which gives it a Difficulty Number of 11. Jessica’s Intelligence is 5; her skill in Engineering: Electrical is 3; and her Specialty in Electrical Applications adds another 2 – all totaling to an Ability of 10. Her GM decides that no additional penalties or bonuses apply. (The Babylon Project, p. 90)

The Random Modifier is created by taking two die (a green positive and red negative) and rolling. Look at the lowest number. That die is now the modifier – positive if the green die and negative if the red. This makes the Random Modified range from +5 to -5.  To continue using the example from the rule book:

Dana rolls the dice. Her Negative Die result is 5, with a Positive Die result of 2. Thus, her Random Modifier is +2. (The Babylon Project, p. 91)

The degree of success or failure is also a consideration. As the example continues:

Jessica’s Ability in her attempt to bypass the reactor control circuitry is 10. Adding the Random Modifier of +2 just rolled by Dana gets a total Result of 12. That’s 1 over the Difficulty of 11 set by the GM – a Marginal Success. The GM tells Dana that Jessica’s bypass has fixed the problem, but that it won’t hold up for long, and not at all if the reactor is run at over half its rated power output. Thus, her success in the task resolution fixes the problem, but the GM interprets its marginal nature as a limitation on engine power and fortitude. (The Babylon Project, p. 91)

Given my close acquaintance with Classic Traveller and the definite lack of a clearly defined task system – much less an emphasis on degrees of success – it is not surprising I didn’t immediately embrace the simple task mechanic in The Babylon Project.

Combat comes in two forms, Close and Ranged, and is played in phases of two-seconds each meaning the player character gets a single action. Players make an attacker roll versus a defender roll. An important combat consideration is aim point; there is a default aim point and if the attacker wants to (or must) aim elsewhere there is a modifier. The degree of success determines how close to the aim point the hit occurs and the level of damage. Combat then moves to Immediate Effects. This table determines if the hit results in immediate death, stun, or impairment. Given the Damage Ratings of the weapons and not-so-great armor this means combat in The Babylon Project is very dangerous! Once combat is over, then Final Effects are dealt with, to include the extent of injuries and wounds. Like all of The Babylon Project, there is a heavy emphasis on the storytelling effect of the injury. Again this is nothing like Classic Traveller yet today I can see the design effect the designer was reaching for – speedy combat using the simple core mechanic with detailed wounds and healing latter. I think the designer achieved what he was trying to do with combat.

The Babylon Project also uses Fortune Points, this games version of Bennies or Plot Points. Each player starts a session with five Fortune Points. Fortune Points can be used to improve a task roll, save  your life in combat, and attempt a task that the player normally could not attempt. This game mechanism is not found in Classic Traveller and a the time I think I saw it as too cinematic or “space opera” for my hard sci-fi taste. Today, I take for granted the use of Plot Points or Bennies or like mechanisms as a useful tool for players to exercise narrative control on the game instead of leaving it in the sole hands of the GM. I have also grown to appreciate the cinematic benefits of Plot Points as I have moved (a bit) away from hard sci-fi rules mechanics.

Courtesy RPG Geek

The last page of The Babylon Project rulebook is a one-page GM Reference Sheet. Literally everything needed to run the game is on this one page. Really…everything! How did they ever expect to sell a GM screen? In fact they did – it was one of the items I also picked up in my bulk buy – and used three panels. The left panel has Attributes and Skills (a useful reminder of the entire list available) as well as Martial Arts Maneuvers (rules added in the Earthforce Sourcebook supplement). The right panel is a Weapons and Armor table – again useful but not absolutely essential. The center panel is a colorful, slightly reformatted version of the original GM Reference Guide.

Courtesy RPG Geek

It would also be negligent of me not to mention that one of the reasons I originally got The Babylon Project was for the space combat system. Introduced in Earthforce Sourcebook, the space combat system was developed by Jon Tuffley and based on his successful Full Thrust miniatures system. This approach to incorporating popular, known, miniatures space combat rules and an RPG was later repeated by the Traveller community with the publication of Power Projection: Fleet.

Rereading The Babylon Project has opened my eyes to just how much of a gem this game really is. Compared to the more recent Mongoose Traveller Universe of Babylon 5, which I reviewed in 2011, the earlier The Babylon Project is more appropriate to the source and setting. Since the 1997 publication of the game, I have also matured as an RPG player and am more comfortable with the narrative/storytelling  and cinematic aspects of the rules. I can now see where The Babylon Project is much like the early Cortex System (Serenity and Battlestar Galactica RPGs) or Savage Worlds – game systems I really love and enjoy playing.  I think I will work on a story arc for The Babylon Project and see what happens….