#TSAO These Stars Are Ours! A setting for #CephesusEngine or #TravellerRPG

 

 

tsao2bfinal2bcover
Courtesy spacecockroach.blogspot.com
These Stars Are Ours!  (TSAO) is a tabletop RPG Sci-Fi setting for the Cepheus Engine or 2D6 OGL SCIFI (nee Traveller SRD). TSAO is a complete Alternate Traveller Universe (ATU) small-ship setting that offers rich background, interesting aliens, and many adventure seeds for the Referee. Though not without a few warts, TSAO shows the great potential of Cepheus Engine used in a setting beyond the classic Third Imperium.  TSAO may be the first setting to take full advantage of the Cepheus Engine rules from the ground up and joins Gypsy Knight Games The Clement Sector and Zozer Games Orbital 2100 as yet another example of the vibrant Cepheus Engine community of rules and settings.

 

 

The setting of TSAO is a logical outgrowth of 20th century UFO conspiracies:

Set in 2260 AD – two years after the Terrans took Keid and forced the Reticulan Empire to capitulate the book introduces the player characters to the immediate aftermath of the Terran victory in the Terran Liberation War against the mighty Reticulan Empire and its many thralls. For their part, the upstart Terrans, bolstered by their victory against their old masters, now move to become a power to be reckoned with in interstellar affairs. Against this background of espionage, maneuvering, and saber-rattling, and on the new interstellar frontiers, the player characters can forge a destiny of heroes or villains of the new United Terran Republic. (DriveThruRPG)

TSAO is delivered in a 209 page pdf (also now available in a POD option). This meaty setting is explained over six chapters and two appendixes.

 

ov
Courtesy spicapublishing.co.uk
Chapter 1 – The United Terran Republic provides much of the history and setting background. Included is not just a recap of events to date, but also many groups or factions or agencies that the player characters (PCs) could interact with. Psionics has a role in this setting. Given the assumed Tech Level (TL) of 11-12 (with some military at 13), TSAO (like Omer Golan-Joel’s earlier Outer Veil setting) is a high-tech but small-ship universe.

 

Chapter 2 – Aliens describes the humans neighbors, opponents, and allies(?). In the space of just a few pages many races are fully described and (again) are rich with adventure seeds and story hooks for development.

Chapter 3 – Characters and Careers is a great example of how to take the basic character generation system in Cepheus Engine and stretch it to showcase it’s full potential. PCs can be the default Humans or select from several alien races. Careers are taken from 13 civilian careers in Cephesus Engine or an from the 20 new ones in TSAO, including seven (7) alien “careers.”

shaka2bpreview2bii
Courtesy spacecockroach.blogspot.com
Chapter 4 – Starships showcases alien saucers and Terra’s ships along with a few other alien constructs. Art is provided by the ever-dependable Ian Stead and others. Make sure to look at the 300-ton Terran Shaka-class Light Military Transport (and especially the Decommissioned Shaka-class Transport) for a not-to-subtle nod to Serenity and the Firefly-class.

Chapter 5 – Terran Borderlands is combination gazetteer and Referee’s Information. The worlds of Known Space is detailed, along with many story hooks and adventure seeds. The usual World Generation process from Cephesus Engine is expanded upon here with an Expanded Universal World Profile that adds a bit more detail but also a whole many more ideas that PCs or Referees can grab onto.

Chapter 6 – Patrons describes 12 Patrons that might engage the PCs. The chapter is not only a grouping of ready-made adventures, but also provides insight into the setting as viewed by the authors.

Appendix A – Terran News Agency Dispatches, February 2260 is a call back to the Traveller News Service snippets that were a staple of Classic Traveller and its successors. Again, these short news items can be the start of yet more adventures!

Appendix B – Sources of Inspiration, Literary and Otherwise is TSAO‘s Appendix N. I always look over these lists to see what inspirations the authors took and to see what I may want to add to my reading/viewing.

The last part of TSAO is an index. This is one of the best indexes I have ever seen in a book. However…the pdf is not cross-linked. This highlights some of my pet peeves with so many pdf products; page numbering and no linking. TSAO is paginated like most books, with page 1 being the interior title page. Unfortunately, this is “page 3” of the pdf, meaning if using your pdf page search you will always be three pages off from your target! The publisher could of avoided (or lessened the impact) of this issue if the Table of Contents (or even that great Index?) was linked.

Production quality is very good. Compared to Stellagama’s previous The Space Patrol I can see definite improvement. Get the linking and page numbering issues nailed and I will likely have nothing to complain about….

The authors call TSAO the first in the Visions of Empire (VoE) space opera settings. If TSAO is any indication, the VoE series will be settings rich in background using (and stretching) the Cepheus Engine rules to their finest.

 


These Stars Are Ours!  By Omer Golan-Joel, Richard Hazelwood, and Josh Peters. Stellagama Publishing, 2017.

#RPGThursday – Passing on Mindjammer Traveller

If you look at this blog, it should be apparent that the Traveller RPG is one of my favorite game systems. It should also be apparent that I have something of a love-hate relationship with Mongoose Publishing. Unfortunately, they are the current banner-carriers of the Traveller RPG system in the form of their Traveller Core Rulebook for Mongoose Traveller Second Edition.

To be clear, I don’t like it. Basically, I don’t see it as any real improvement over the original version and, when coupled with a more restrictive license that limits – even harms – third-party publishers, I am loathe to support it.

I also own Mindjammer: The Roleplaying Game (Second Edition) by Modiphius/Mindjammer Press. Mindjammer 2E uses the FATE Core rules. I am not a real fan of Transhuman adventure but I saw much good press about the game and tried it. I even liked it.

pic3340140_mdThis month, Modiphius released Mindjammer: Transhuman Adventure in the Second Age of Space using the Mongoose Traveller 2E rules. So I was challenged; I like Mindjammer but dislike Mongoose. What do I do? Do I invest in the Mindjammer: Traveller Edition for $22.49 (pdf) or not?

So I picked up the Dominion Quickstart for Mindjammer Traveller from DriveThruRPG. This is a free 48 page intro game with a few pages of rules changes from Mongoose Traveller 2E and then an adventure.

What I found was very few rules changes from Mongoose Traveller 2E and a lot of background. Background I already have in the FATE Core Mindjammer version. After careful consideration, I concluded that there is not enough new or attractive in the Mongoose Traveller 2E version of Mindjammer to purchase it.

So I’ll pass, and pause to ponder. Why do I find Mindjammer Traveller unattractive? It is the rules or setting? In this case, I don’t see a good marriage of rules to setting here. Maybe my experience with the FATE Mindjammer version has biased me, but I just don’t  feel the Mindjammer setting is best served by the Mongoose Traveller 2E rules. Indeed, I feel the story-telling or narrative basis of FATE is much better for Transhuman Adventure than the very mechanical Traveller engine. The possible results are much more wondrous – like a Transhuman setting should be.

Furthermore, I realize that my unbounded desire for anything Traveller has ended. These days, I appreciate a bounty of different RPG systems from the Cepheus Engine to Traveller 5 to FFG Star Wars to FATE games like Mindjammer or Atomic Robo to CORTEX Plus games like Firefly. Each of these games captures or compliments a setting in unique and positive ways – Mindjammer Traveller just doesn’t give me that same feeling.

 

#Wargame Retroactive – Mayday (Traveller Game 1, Series 120, GDW 1983)

pic900819_mdWhile I’m waiting for my Squadron Strike: Traveller Kickstarter to deliver, I went back to my first vector movement starship combat game. The game is Mayday from the Classic Traveller RPG-universe. I have the third edition GDW flat box, copyright 1983, with the Series 120 rulebook copyright 1978 and 1980. A Series 120 game was supposed to be playable in under two hours. The back of the box taught me what mayday means and why it may still matter in the future:

 

In the earliest days of radio, a standard distress call was established using the international language of the day. In French, the simple statement help me was expressed m’ai dez. English-speaking radio operators pronounced and spelled the word as mayday. Since then, the word has become as accepted as its Morse code predecessor S.O.S.

In the future, it is likely that monitoring stations will receive the same call from the depths of interplanetary space, faintly repeating a position and a single word, mayday.

Mayday is a science fiction game of small spacecraft in danger, distress, and ship-to-ship combat. The ships are out-fitted by each player with a variety of laser weapons, missiles, defensive systems, and computer packages. Using realistic vector movement, players maneuver their ships against each other on a hexagonal grid. Scenarios include The Grand Prix, The Attack, Piracy, Battle, and Smuggling.

Mayday is played “using realistic vector movement and intriguing combat systems….” Recently, I closely looked through the short (15 page), digest-size rulebook and was struck by both how simple the game was, and yet how much detail and universe-building was contained within.

A Small-Ship Universe

pic514041_mdMayday was also marketed as Traveller Game 1. Mayday took Traveller Book 2 Starships and brought it into a hex and counter setting. What struck me looking through the book is that Mayday is firmly in the “small ship Traveller universe.” Section 8. Ships provides the following starships:

  • Scout (100 ton)
  • Courier (100 ton)
  • Escort (100 ton)
  • Free Trader (200 ton)
  • Yacht (200 ton)
  • Transport (400 ton)
  • Armed Merchant (400 ton)
  • Destroyer (400 ton)
  • Colonial Cruiser (800 ton)
  • Corsair (400 ton)

Small craft are also fuel-limited in Mayday. The Fighter is rated “4G12” meaning it has a maximum acceleration of 4G in a turn, and cannot make more that a total of 12G of acceleration/deceleration before running out of fuel.

Vectoring About

Mayday is the game the taught me what vector movement is. Each starship, small craft, or missile has three counters; the past position, the present position, and the future position. The use of these three counters allows one to readily see the vector movement of the combatants. This easy vector movement system is what I had always focused upon and I didn’t really pay attention to the combat.

Lasers and Missiles Oh My!

In the Mayday version of the Traveller universe there are basically two offensive weapons; Lasers and Missiles. Of the two, the Laser is the most common starship and small craft weapon. However, a close analysis of the Attack Table and Damage Table reveals it is actually not the best weapon. Without consideration of any modifiers, a Laser will hit a starship 58% of the time, whereas a Missile will hit 83% of the time. Against small craft, the chances are 42% for Lasers and 58% for Missiles.

pic516813_mdLasers are also very close-range weapons realistically effective out to no more than 5 hexes (or 5 light seconds). This is because Laser Fire has a -1 Die Modifier (DM) for each hex of range. [Interestingly, Mayday page 12 references Traveller Book 5: High Guard and its fleet combat rules. The Mayday rules state that ships with matched courses (same hex, course, speed) are at “boarding range.” Short range is within 5 hexes (5 light seconds). Long range is beyond 5 hexes, but less than 15. Ships beyond 15 hexes/15 light seconds range are “out of range” and cannot fire.]

The damage potential of a Laser versus a Missile is also dramatically different. If a “hit” is achieved a Laser gets one roll on the Damage Table whereas a Missile gets two rolls if it has a proximity fuse or three rolls (!) if it uses contact detonation. This dramatic difference in damage potential finally brought home to me, more than any number of damage dice, the difference in the power of these two weapons systems in Traveller. It also vividly showed me why Missiles are the weapon of choice for starship combat at the mid-tech levels of Traveller.

Computing Power

Many people criticize the assumptions Traveller made when it came to computers. Marc Miller and company missed with their prediction of the computer revolution. For myself I tend to ignore the inconsistencies with our reality and try to play the game. In the case of starship combat, I think the problems are not as dire as some make them out to be. Instead, I try to play the game using the rules as written to see what the designers were trying to communicate.

In Mayday, like Book 2, computers are actually a key part of ship-to-ship combat. This is because Traveller computers are limited. For example, a Model/1 computer has a “CPU” of 2 and “Storage” of 4. What does this mean? It means that the ship can “load” programs taking up space equal to “Storage” and can “run” programs in a given phase of the turn with sizes the “CPU” can support.

Take a typical Free Trader with a Model/1 computer. According to the ship description, the available computer programs (and size) are:

  • Target 1, Launch 1, Gunner Interact 1, Auto/Evade 1, Return Fire 1, Anti-Missle 2, Maneuver 1,  Jump-1 1, Navigation 1.

No more than 6 “spaces” of programs can be loaded. As you can hopefully see, not all the programs can be “loaded” at once. Thus, the crew must make a decision.

  • Target is needed to shoot, unless one wants a -4 DM for “manual control”
  • Maneuver is needed to change course/speed.
  • Launch is needed to fire missiles…or a small craft
  • Gunner Interact allows characters to use their Gunnery skill (one of the few connections between Mayday and the Traveller RPG)
  • Auto/Evade makes you harder to hit, but cannot be run with the Maneuver program
  • Return Fire must be used with Target and allows ships to fire at ships/craft that fired at them first
  • Anti-Missile is used for point defense against impacting missiles
  • Jump is needed to activate the FTL (hyperspace) drive…useful to escape
  • Navigation is needed to compute the hyperspace jump

There are other programs available, such as Predict (positive DM to hit), Selective (ability to target specific systems), and Maneuver/Evade (harder to hit but less maneuver capability).

Making sure you have the right program available at the right time is crucial for combat in Mayday. For many years I ignored this section and just played with the Simplified Computer Rule:

Any activity may be performed, without regard  to computer program requirements. The size of the ship’s computer is used as an attack DM for lasers (computer model 1 gives a DM of +1) and as a defense DM when attacked by lasers. DMs for range, sand effects, manual control, and anti-missile fire still apply, but no others do. This simplified rule allows concentration on movement and basic combat. 6. Computer Programming (p. 9)

Simply Complex

Mayday is what I call a “simply complex” game. The rules are simple, from easy vector movement to a straight-forward combat system. Taking into account the computer rules really does make this game “intriguing” like the rulebook claims, and that makes it complex in that the choices one makes are relevant, interesting, and impactful. I also appreciate the insight this simple game gives me into the universe building that Marc Miller and friends started 40 years ago.

Mayday is currently rated 5.8 on BoardGameGeek. I personally rated it a 7 (Good – Usually willing to play) back in 2008 when I think I was updating my collection. Given my more recent appreciation for the game, I think it deserves a rating increase to 7.5.

 

 

#RPGThursday Retrospective – Manufacturer Settings (2009-2010)

At the end of the 2000-aughts my roleplaying collection again took a different turn. For a few years, I turned away from new game systems and instead invested in campaign settings. At the time, the seemingly most popular settings were published courtesy of major publishers, or what I term “manufacturer settings.” I realize the term is not totally fair; in more than a few cases the setting was a labor of love from a small-time or alternative author that teamed with the larger publishing house because they had the experience and marketing prowess to bring the product to market.

pic544013_mdUniverse of Babylon 5 used Mongoose Publishing’s Traveller (1E) game engine. This campaign setting was translated from an earlier D20 series. UoB5 suffers from poor editing and sloppy game system translation as well as poor production quality. Given how rich a setting the B5 Universe is, to have the game version be so poorly done is a travesty. A major disappointment.

pic651616_mdReign of Discordia (Mongoose/Gun Metal Games) was another campaign setting using the Traveller 1E-engine. Another system translation (originally True20) it suffered from many of the the same issues as U0B5. Another disappointment.

pic760617_mdWhen I saw Hammer’s Slammers (Mongoose) I just had to get it. Here was going to be the RPG version of my favorite military science-fiction series! Even better, it used the Traveller 1E-game engine that I was so familiar with!

What a let-down.

The fact that it was Mongoose should of been a warning. That and the cover art – that soldier is nothing like I imagined Hammer’s Slammers to be. Opening up the book, the maps were so amateur and very un-military-like. The rules were an expansion of the basic game engine, and links to future products were promised (and never delivered).

In my disgust with Mongoose – they had obviously tried to cash in on the Hammer’s Slammers name and ended up doing a great disservice to the IP – I turned to another recognized gaming name. pic797297_mdSpace 1889: Red Sands (Pinnacle Entertainment Group – PEG) was the campaign setting book for Space 1889 using the Savage Worlds game engine. This was by far the best of the setting books I tried as it was a good match of setting (steampunk) and game engine (Savage Worlds – “Fast, Furious, Fun”). The campaign setting also works well with the

aeronefpdf
Courtesy Wessex Games
Aeronef  (Wessex Games) miniature rules I had recently found. Indeed, long ago I used Red Sands to create Aeronef characters.

By the end of 2010 my flirtation with campaign settings died out. Looking back, each of these settings I tried was backed by a major publishing house and closely tied to their game engine. In the case of Mongoose the poor production values reflected to me a cash-grab attitude the turned me off then like it does today. The second part of the problem was that there was little “new” in these settings; in each case the setting was a translation of an older IP or license into a newer game engine. Red Sands was the best done of my lot, but I was looking for more.

In retrospect, this era – 2009 thru 2010 – was a major disappointment. Interestingly to me, I purchased each of these settings in a dead-tree form. This was among the last times I did that. The rise of online publishing and the availability of content through sites like RPGNow or DriveThruRPG (and more recently the Open Gaming Store) were starting to dramatically change not only how, but what content was being delivered to RPG customers like myself.

All images courtesy RPGGeek except where noted.

#RPGThursday Retrospective -Cortex Worlds (Serenity, 2005; Battlestar Galactica, 2007; Savage Worlds Explorer’s Edition, 2008)

I spent 2007-2009 stationed overseas, and my access to gaming materials was limited. Upon my return stateside in 2009, I quickly searched the local game stores and found a game that changed my RPG life. The game was an RPG based on the reimagined Battlestar Galactica TV series. Battlestar Galactica Role Playing Game (BSG) represents to my a major turning point in my RPG gaming history.

It’s in Color!

200px-bsg_rpg_cover
Courtesy Battlestarwiki

BSG was a very different game that I had seen in the past few years. First off, the Corebook was a hardcover that was lavishly illustrated with pictures from the TV series. It did not have the desktop publishing feel that I had become accustomed to in the past few years (see the 1990’s and my Second RPG Interregnum).

Cortex at the Core

BSG used the Cortex System (these days the BSG version is known as Cortex Classic). In Cortex, character attributes are not numbers, but a die type ranging from d4 to d12+d4. Skills were also described by die types, and each character also had Assets or Complications that also were rated by a die type. The core mechanic was a simple Skill Die + Attribute Die vs. a Difficulty number.

Assets and Complications were very interesting to me. BSG was the first time I really saw a mechanical impact of role playing characteristics of a player character. But the part that really excited me was Plot Points. Although I had played with Hero Points in James Bond 007 RPG, it was the Plot Points mechanic in BSG where I first started understanding a “game economy.” I also have to say that BSG has my second-favorite ever Combat Example (second only to James Bond 007 RPG) which replays a scene recognizable from the series.

The other very interesting part of BSG were vehicles. Unlike vehicles and spacecraft in the Traveller RPG games, BSG described vehicles in the same way characters were presented; attributes and traits. I actually embraced this approach because it was more “narrative” and fit with the Assets/Complications and Plot Points in supporting more narrative play.

Finding Serenity

So much did I like BSG that I went in search of another Cortex System game; Serenity. Published by Margret Weis in 2005, it was the 2005 Origins Awards Gamer’s Choice Best Role Playing Game of the Year Winner. I had missed this one but now caught up. Serenity uses a earlier (and slightly less refined) version of Cortex Classic but was similar enough that I caught on easily.

A Savage Exploration

Having caught the “attribute as dice” bug, in 2008 I picked up the then-new Savage Worlds Explorer’s Edition. Described as “Fast! Furious! and Fun!” I quickly discovered that this rulebook was another set of rules sans setting. It also had a near-miniatures rules feel to it (see Figures and Battle Mats, p. 4). That said, I really was intrigued by:

  • Character attributes described by dice
  • Edges/Hinderances
  • Wild Cards and Extras (maybe the first time I recognized “Minion” rules)
  • Bennies (Game Economy)
  • Initiative using playing cards

The part that confused me was Arcane Backgrounds. I had a difficult time grasping this at first, and really didn’t understand what Arcane Background could do until seeing it used in a later setting book.

Discovering a New Narrative

The major impact BSG/Serenity and Savage Worlds had on my RPG gaming experience was the introduction of a more narrative style of play. The use of Assets/Complications or Edges/Hinderances along with the game economy tools of Plot Points/Bennies totally changed how I viewed playing RPGs. My games became less simulationist and more narrative. Now, I had seen (and played) some more narrative games (like James Bond 007 RPG or even Babylon Project) but I did not fully recognize what was happening. With Cortex System and Savage Worlds I recognized this change in gaming style and embraced it. It also helped that at this time I moved away from a preference for hard(ish) sci-fi settings and went to settings influenced by pulp (in no small part due to my discovery of the Wold Newton Universe through Philip Jose Farmer’s Tarzan Alive and The Other Log of Phileas Fog and Win Scott Eckert’s Myths for the Modern Age

The move to narrative also explains my next purchase.


Battlestar Galactica Role Playing Game, Copyright (c) 2007 Margaret Weis Productions, Ltd. and Universal Studios Licensing LLLP. 

Serenity Role Playing Game, Copyright (C) 2005 Margaret Weis Productions, Ltd. and Universal Studios Licensing LLLP.

Savage Worlds Explorer’s Edition, Copyright (C) 2008 Pinnacle Entertainment Group. Produced under license by Studio 2 Publishing, Inc.

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

star_wars_roleplaying_game_saga_edition_core_rulebook
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 CORE MECHANIC

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.

 

 

Encountering #TravellerRPG using #CepheusEngine

Hattip to Tales to Astound for inspiration here.

Tales to Astound has a very interesting series on using the Classic Traveller RPG system. One item that caught my attention a few weeks back was Encounters. TTA rightly points out that in Classic Traveller, “Encounters are there to create situations, which lead to adventures.”

This describes my common GM style to a tee. I usually am a low-prep GM, depending on the situation as it develops to help create the adventure. Sure, I often have a meta plot that is working behind the scenes, but the Travellers often find themselves intersecting the meta plot, not necessarily driving it. It is through encounters that this intersection happens.

Looking at the new 2d6 Cepheus Engine System Reference Document, I decided to dig into the rules and find out where the encounters were. At the same time, I looked at other “events” that rely on time. Boy, was I in for a surprise for all I found. There are some hourly, many daily, a few weekly, and even monthly and annual events. Putting all these together actually helps to establish a “routine” to life that can assist the GM in creating those encounter situations that lead to adventure.

Here are the many I found:

  • Pension (Yearly) p. 31
  • Explorer’s Society (Every 2 months) p. 32
  • Ship Inspections (Upon Arrival) p. 49
  • Gain Skills (Weeks?) p. 57
  • Drug Effects (Days/Weeks/Months) p. 71
  • Fatigue (Hours) p. 97
  • Natural Healing (Daily) p. 98
  • Medical Care (Daily) p. 98
  • Passage (Weekly or By Jump) p. 106
  • Skim Fuel (Hours) p. 107
  • Salaries (Monthly) p. 108
  • Life Support (Monthly) p. 109
  • Port Fees (Weekly/Daily) p. 109
  • Routine Maintenance (Monthly) p. 109
  • Law Enforcement Encounters (by event) p. 113
  • Find Supplier (Days) p. 115
  • Resist Disease (Hours/Days/Weeks) p. 163+
  • Radiation Effects (Hours/Days/Weeks) p. 165
  • Starvation/Dehydration (Hours/Days) p. 169
  • Animal Encounters (multiple encounters Daily) p. 184
  • Social Encounters (As Needed/Daily/Weekly) p. 186+
    • Legal (Daily)
    • Random (Daily)
    • Patron (Weekly)
    • Rumor (Weekly)
  • Starship Encounters (Enter/Leave System) p. 192
  • Adventure Checklist – Weekly Event (Weekly) p. 202

Encounters are really where “situation meets adventure” happens, but the other temporal events can also create situations for adventure:

  • “What do you mean you can’t pay my salary this month?”
  • “I have radiation poisoning and may only have weeks to live.”
  • “Last time we skimmed fuel we got jumped by pirates!”

All of these events happen at set time intervals and can be points the GM uses to create a situation that leads to adventure.

I am working up a GM play aid that captures all these temporal events and encounters. I intend to keep it handy for use as the game clock ticks by. I want to use this same approach to events in time and encounters not only in Classic Traveller/Cepheus Engine games but to apply the same concept to all my RPG adventures, especially Fantasy Flight Games Star Wars Roleplaying Game.


Cepheus Engine System Reference Document – A Classic Era Science Fiction 2D6-Based Open Gaming System, By Jason “Flynn” Kemp. Copyright (c) 2016 Samardan Press.