Today I'm going to wrap up my in-depth review of the rulebook for Heritage's 1978 Star Trek Adventure Gaming in the Final Frontier (STAGFF), then move on to fan written works that added to the original game. In Part 1, I covered the Basic Game rules and scenario. To sum up my findings so far:
- STAGFF is better organized and presented and more playable than its predecessor, Space Patrol.
- The Basic Game is based upon using the classic Trek characters (Kirk, Spock, Koloth, etc.) and provides stats for them.
- For the most part, the Abilities -- Strength (ST), Dexterity (DX), Luck (LK), Mentality (MN), Charisma (CH), and Constitution (CN) -- are each applied to only one or two specific tasks with modifiers. No Skill system is given.
- The game suffers from unnecessary complexity.
- The Basic Game provides a brief Scenario called "The Shuttlecraft Crash" and includes a map.
- Even in comparison to the few other RPGs of the time, STAGFF feels more like a wargame, and feels nothing like Star Trek itself.
Over 1,000,000,000 years ago the Slavers ruled the Galaxy. They died off when one of their subject races rebelled with sufficient ferocity. The only known remains of the last Slaver Empire are Stasis boxes. These are special force field boxes in which time stands still. These boxes can be opened using a magnetic probe and they often contain artifacts, devices and other remains of the lost Empire. Just such a box gave the Federation its anti-gravity technology used on starships. Another stasis box contained a super-weapon that was lost due to Kzinti intervention. The slaver stasis boxes are the most sought after archaelogical treasures in the known universe.
The scenario opens with the ENTERPRISE shadowing an alien vessel traveling in unknown territory. The alien vessel, possibly a Kzin or Klingon ship (this is at the discretion of the Mission Master. Any aliens can be used. When aliens are mentioned in this scenario they will be called aliens, but the Mission Master can fill in whatever aliens he thinks would be appropriate) makes a landing on a small Class M world near a partially ruined building. The alien crew, numbering 8 individuals, are seen getting out and entering the building. The ENTERPRISE sends down a party of 6 crewmen to investigate.
The planet has been seeded by the ancient race known as the Providers and has animals from many parts of the Galaxy. The building in the ruins is an ancient Slaver outpost and contains 4 stasis boxes hidden within its walls along with various creatures and the searching alien landing party. The Star Fleet crew must prevent the stasis boxes from falling into the hands of the aliens. The walls of the building are made of a Slaver alloy which prevents the operation of the communicator (and thus the Transporter) and tricorder readings are only partially effective through its walls. Doors in the building are sliding doors requiring a strength of at least 13 to open or can be burned down by a phaser set on Dematerialize. The aliens are hostile and will attack the Federation crewmembers on sight.So that's kind of cool. A sequel of sorts to the 1973 Star Trek animated series episode "The Slaver Weapon" by Larry Niven, and author Michael Scott even got Kzin/Kzinti correct! And an adventure on a planet seeded with the remnants of both Slavers and Providers? All it needs are the Ringers from the Enterprise RPG scenario "The Drifting Ring", and we'll have all the Ancients covered.
In all seriousness, a few things worth noting. First, the "dungeon crawl" nature of the mission is pretty obvious: kill the Kzinti, find and take the treasure. It feels more like a D&D adventure than anything actually inspired by a Star Trek episode. Second, here is evidence that as early as 1978, the question of how do deal with the Transporter in a Star Trek RPG is identified as problematic (and still discussed today, as shown in one of this week's more popular threads on RPGnet). Prospective GMs take note: "Slaver Alloy" as an alternative to "Ion Storm". Third, I do find it interesting that there are some similarities between this Scenario and the one included with the Japanese RPG Enterprise (ancient race, stasis devices)... I wonder if Tama Yutaka had actually seen this game before he was inspired to write his own years later?
The Scenario is more interesting than the one in the Basic Game, and much more deadly. It makes use of the elements from the Advanced Game such as Psionics and some of the new creatures listed later on including the Capellan Power Cat, the Vulcan Sehlat and... the Mugato! Those whacky Providers.
The Scenario is followed by a brief section on custom Character Creation, which basically consists of rolling various dice for the six primary Attributes, the all-important Size attribute (right down to the centimeter) and Movement. The rule for awarding experience essentially amounts to two sentences, encouraging the Mission Master to award Attribute points and new equipment training for a successfully completed scenario.
The section on Psionics makes it clear that, with the exception of Vulcans and the Kziniti, characters will rarely have a Psionic power, determined by a roll (1% chance). If the roll succeeds, they roll to get Empathy (with a rule for Gem-like healing), Telepathy, Telekinesis, Clairvoyance, Precognition, Mind Control or Teleportation. Again, this section is very similar to the PSY Talents section in Enterprise. I suspect the list was influenced by Traveller Book 3 - Worlds and Adventures, but the random generation method looks to be Michael Scott's own, later borrowed and further polished by Yutaka. It's definitely not the Psionics of Eldritch Wizardry.
The next section is on Familiar Star Trek Life Forms, a list of nearly 50 alien races and creatures from both TOS and TAS. Examples (note the use of the generic AR - Ability Rating - for creatures as opposed to alien races, as detailed in the Basic Game; note also, typos are not my own):MUGATO - Great white horned ape of Neural with poison fangs. They mate for life and will avenge mate's death. Basic move: 12, Basic size: 250 cm, AR 18.
TELLARITE - Pig-like humanoids, they are members of the UFP and can be members of a Star Fleet crew. They are very argumentive and alcohol only makes them more so. Basic size: 175cm, Basic move: 10m, CH -2.
VULCANS - Pointed-eared humanoids of great emotional control and logic. Their blood is based on copper salts and they have protective nictating membrances to protect their eyes from dirt and glare. They have limited powers of telepathy and empathy in that they usually have to be in contact with a subject for the powers to operate. Once every seven years they must mate or die. Basic size 200cm, Basic move: 11m, ST +3, DX +2, MN +3, CT +4. They are members of the United Federation of Planets (in fact, one of the most highly regarded members) and are found throughout Star Fleet's crews. The Vulcan Spock is a successful hybrid of Vulcan and Human heritage.
Rules are also provided for Creating Alien Creatures, based on Space Patrol's random attribute generation method (3D6 for AR) and a series of tables: Type and Shape, Size, Special Capabilties, Size Modifier and Basic Movement.
The next sections are the Advanced Equipment Table and a 4-page List of Equipment and Weapons, many based on Star Trek items (ex: Lirpa, Phaser Bore, Phynburger (sic), Universal Translator, five types of Tricorders), and the rest corresponding roughly to that provided in Space Patrol. These are generally just descriptions with little or no detail as to their effects, provided later in the Advanced Game Weapons Tables that are part of Advanced Combat.
The Advanced Combat Rules don't add much to what was outlined for ranged and hand-to-hand combat in the Basic Rules. In fact, despite the four pages they occupy, the Advanced Rules really only add three things: a modifier for Initiative (or, as it's called throughout the book, "Initiation"), tables for the use of all the weapons previously introduced, and rules for the use of Armor and Shielding (in short, the value of the Armor Rating is subtracted from the damage when hit).
The book starts to wrap-up with simple instructions for creating custom Scenarios, re-uses Space Patrol's types of scenarios, and throws in a few Trek-ish bones into each such as this:
You may have realized that the players of a scenario do not have to be Star Fleet crewmembers. They could be Klingons, Romulans, or some other race. Think how nice it would be sometime to be able to solve a problem technologically and not be hampered by the Prime Directive restricting your every action. Admittedly the Star Fleet crew has the harder job, having to play by the United Federation of Planets' rules and still get the job done. But Kirk seemed to manage from week-to-week, and you can too.
It then gives some advice to the prospective Mission Master on how to keep players engaged by emphasizing the mystery to be solved in the story, and how to deal with players in general. This also leads to one of the stranger passages of the book:
(T)he Mission Master does not volunteer answers to questions that are not asked... Suppose that Spock was using the semi-sentient talking computer of the ship systems to scan an area . He asks for the computer to report any relevant dangers. It would be asking too much of the computer to understand Spock's unreasonable fear of the Groupies at a Star Trek convention. Thus, unless our favorite Vulcan asked, the computer would see no reason to mention his adoring fans waiting in the landing area.
Both of these excerpts are examples of a few places in the game where you may sense a little disdain for Star Trek itself, but I think it's worth noting that STAGFF is really a product of its time.First, it was 1978 and, in the wake of Star Wars, repeats of Star Trek were starting to feel a little dated. Yes, a big film was on its way in late 1979, but little was known about it. Star Trek and "Trekkies" were seen as cheesy and as objects of derision, even more so than today (for example, the 1976 SNL sketch with John Belushi as Kirk, and Mad magazine's Trek parody later that same year). The way I recall it (and I was only in my early teens in the late 70s), it really wasn't until the films and the Next Generation shows that Trek (even TOS) began to gain some wider respect in pop culture.
Second (and I've mentioned this before), 1978 was early for RPGs, which were still growing out of their wargame origins. The fact that STAGFF was created (probably on the cheap) only to help Heritage Models sell its Star Trek miniatures emphasizes that "role" was still being defined in gaming. At that time, it was probably inevitable that such a game would turn out to be "let's phaser things and take their alien treasure!" As a result, STAGFF is really just a great big list of things to kill, weapons to kill them with and the mechanics to do so.
I'd argue that things haven't improved much in this regard over the past 30+ years. Despite the noble efforts of FASA, LUG and Decipher to emphasize elements in their games such as diplomacy, the Prime Directive, character skills and "the needs of the many", the fact remains that the Trek games that have survived and done best over the years (tabletop or computer-based) are those that are focused on starship combat and "let's phaser things and take their alien treasure!" There have been a number of online discussions lately as to whether Trek is really suitable for roleplaying at all, especially when you have players (and GMs?) that focus on Trek-nology and do things like transport a photon torpedo over to the enemy's bridge (RPGnet thread).
I'm not trying to philosophize (not yet, that'll come later). I'm just pointing out that the easiest criticism to level at STAGFF -- that it's "not very Star Trek" -- is still true of Trek games today. In 1978, I'm not sure that mattered or offended all that much. And despite these strange passages in the rulebook, their are other places where you can tell that the author must have loved the show. For what was probably supposed to be a simple miniatures game, he went a little further than just slapping the name "Star Trek" onto his Space Patrol rules.
The rulebook finishes by referring the reader to the best merchandise available at the time: books! In the days before VHS and The Google, references such as The Star Fleet Technical Manual, The Star Trek Concordance, The Making of Star Trek, and the novelizations of TOS and TAS would be a Mission Master's best friend. At the bottom of the page was the "Star Trek Catalog" of Heritage Models: the list of 31 packages of miniatures, half of which would never go into production.
The most notable elements missing in this Star Trek game are the things that Michael Scott would later remedy somewhat in Star Patrol and Starfleet Voyages: the themes of exploration, character building, starships and starship combat. Although a comprehensive approach wouldn't show up until FASA's 1982 Star Trek The Roleplaying Game, this is not the end of the STAGFF story. Two fan-written works published years apart in Different Worlds magazine would take two very different approaches to extending STAGFF, and make it more like the Star Trek game they wanted it to be. I'll look at those in the near future.
But wait! There's more.....
Here is the last in my series of excerpts from my translation of the 1983 Japanese TRPG, Enterprise. I've finally (well, 3 weeks, not bad!) finished translating both the rulebook and the accompanying scenario, "The Drifting Ring". The scenario book wraps with designer Tama Yutaka's notes (below) on what he was trying to accomplish with the game, and the importance he saw in upcoming tabletop roleplaying game revolution.
ENTERPRISE - ROLE PLAY GAME IN STAR TREK (Japanese)
The first original TRPG came after Enterprise, and was another science fiction title called Star Quest (Tsukuda HG-032-R). Interestingly, it was written by Ed Lipsett, an American expert on Japan and author of the wonderful 1979 Spacefarers' Guide series from Phoenix Games, which served as a starting point for Star Quest. The first Japanese translations of Traveller were starting to appear and gain popularity, and Tsukuda was eager to have their own competing product in place. Star Quest was similar in concept to Traveller, but utilized a d1000 mechanic (roll 3 d10: designate one as the 100 value, one as the 10 value, and the last as the 1 value, to get a result from 001 to 1000). Around the same time, Tsukuda released the first domestic fantasy TRPG, Roads to Load (HG-030-R). All of these games set the stage for TRPGs in Japan -- imported and domestic, licensed and original -- which would become increasingly popular well into the early 90s.
ENTERPRISE - Contents
ENTERPRISE - Game Mechanics
For now, Enterprise appears to be mostly a curiosity, especially to those accustomed to more sophisticated (and English!) RPG systems. Nevertheless, I thought it was important to at least get it documented.
