A Look at the First Flash Gordon Role Playing Game

Did you know Lin Carter helped design and RPG?

I was recently rereading my copy of the Flash Gordon Role Playing Game for the Savage Worlds system. I am excited to show it and its expansions to my players and try to convince them to game in this wonderfully pulpy setting. Like Shane Hensley (the creator of the Savage Worlds rpg), I am a huge Flash Gordon fan from serials to comics to 80s cult-classic. One of the reasons I purchased the Slipstream setting book for Savage Worlds was that it was a well written adaptation of Flash Gordon with the serial numbers filed off. It was so faithful that it made sure to include the most important of Flash Gordon species, the Lion Men. I know, I know, you thought I was going to say Hawk Men, but as amazing as Brian Blessed is as Vultan they are the second most important alien species.

I am certain that I’ll get around to reviewing the Savage Worlds version of Flash Gordon eventually, TL;DR it’s great, but before I review the newer game I thought I'd take a moment to reflect on the first Flash Gordon role playing game. A game that was among the first licensed role playing games ever published and set a baseline for what might be expected in licensed products in the future.

In the nascent days of role playing game yore -- 1977 to be exact -- Fantasy Games Unlimited published one of the first Science Fiction role playing games to hit the market with Flash Gordon & the Warriors of Mongo. The first two science fiction role playing games were TSR's Metamorphosis Alpha (1976) and Ken St. Andre's Starfaring (1976) and those were relatively unique fair. The first combined the space arc and post apocalyptic genres while the second was very much gonzo 70s sexploitation SF. Flash Gordon was very different from those games in that it was aimed at an existing fanbase outside of the role playing market. It also happened to be one one of two games Fantasy Games Unlimited published that was co-written by Lin Carter -- yes that Lin Carter, the one who is responsible for most of Appendix N being in print -- with the other being Royal Armies of the Hyborean Age.

Where Royal Armies was a set of miniature warfare rules set in the Hyborian Age, the Flash Gordon role playing game was an attempt to create an entirely self contained role playing game complete with campaign setting and campaign in a single 48 page volume. That's quite a daunting thing to attempt and I have been surprised at how well Flash Gordon accomplishes its goal -- especially given the low esteem in which the RPG.net review holds the game. I’m actually quite stunned at how many reviewers have paraphrased the assertion made in the one comment on RPG.net that, “This is actually far more of a chase game than an RPG and suffers from the plot being fairly one dimensional, after all to complete it you have to overthrow Ming the Merciless whatever the buildup play.”

I disagree. Flash Gordon and the Warriors of Mongo is a fully flushed out role playing game with a campaign system that pre-dates the later Savage Worlds Plot Point campaign innovation, but that presages it as well. The events of the game are plotted in zones where certain specific encounters occur, encounters that culminate in a campaign resolution based on the first couple of years of the Alex Raymond run of the Flash Gordon comic strip with the rebellion of the Power Men against Ming.

The book has its flaws, but it also has its brilliance. The flaws lie within the underlying rules in the conflict resolution system. The brilliance lies within the freeform campaign implementation system, which as I mentioned above is a system remarkably similar to the Plot Point and Encounter Generation system mastered by Pinnacle Entertainment Group in their Savage Worlds series of games. Unlike that Plot Point system, Warriors of Mongo is more like a branching railroad than the freeform tool Pinnacle invented, but more on this later. It's time to look at Flash Gordon & the Warriors of Mongo.

System Mechanics

In a brief note at the beginning of the book Lin Carter sets out his chief objective in the drafting of Flash Gordon. "My own personal debt to Alex Raymond, and my enduring fondness and admiration for Flash Gordon made this set of rules a labor of love. I was dead set against Scott's [Scott Bizar] first idea of doing a book of wargame rules and held out for adventure-scenarios, instead."

Carter wanted a game that was able to capture the excitement of the old Flash Gordon serial through the use of a collection of adventure-scenarios bound by a single rules set. Rules that were intended to "provide a simple and schematic system for recreating the adventures of Flash Gordon on the planet Mongo." With regard to their goals, Carter and Bizar both succeeded extremely well and failed monumentally.

The system is simple...and confusing...at the same time.

Characters roll three "average" dice for the following four statistics -- Physical Skill & Stamina, Combat Skill, Charisma/Attractiveness, and Scientific Aptitude. It's an interesting grouping of statistics that demonstrated FGU's willingness to look beyond the "obligatory 6" statistics created by TSR. The inclusion of Combat Skill as a rated statistic is in and of itself an interesting choice.

At no point is it explained what an "average" die is. Is an "average" die a typical six-sided die that you can find in almost every board game ever published, or is it one of those obscure and hard to find "averaging" dice mentioned in the Dungeon Master's Guide? The rules aren't clear regarding this, but the fact that "rolls of over 12 indicate an extremely high ability in the specific category" [emphasis mine] hints that it is the "averaging" die to which they are referring -- later difficulty numbers hint that it might be the regular dice that are used.

The new gamer would have only this clue, but wargamers of the era would know that an "average" die was a six-sided die with the numbers 2, 3, 3, 4, 4, 5 printed on it instead of 1 through 6. This die was used to reduce the influence of uncertainty on outcomes in wargames at the time. More recent games, like Warhammer, rely on regression to the mean and buckets of dice to reduce uncertainty. It may seem counter intuitive, but the more often you roll the less uncertainty influences outcomes because the likelihood that the total distribution of the rolls is normal increases.

Not that it matters much, as you will soon see.

After rolling statistics, players choose from one of the following roles -- Warrior, Leader, and the Scientist. This leads one to wonder which group Dale Arden fits, an oversite similar to that made in early John Carter role playing games as well, but that is another conversation entirely. Though I will state for the record that my vote is for Leader. The primary effect of choosing a particular roll is to add one point to the statistic most related to the profession.

These attributes are later used to determine success based on a very simple mechanic. Stat + d6 > TN. Let’s take a look at a possible conflict the players may encounter.

If the characters find themselves in the Domain of the Cliff Dwellers one possibility is that they will encounter the deadly Dactyl-Bats. Let’s say the players decide they want to fight off the Dactyl-Bats. The success or failure of this action will "depend upon the combat skill of the most skilled member of your group. Roll one die and add the result to your military skill. A final total of fourteen or greater is needed to drive off the Dactyl-Bats." Failure indicates the character is wounded and that the party must rest. It's a simple resolution, but one that lacks any significant cinematic quality.

This conflict resolution feels awkward and mildly unsatisfying. Other mechanical resolutions in the game are similarly weak. All conflicts are resolved strictly via single die rolls and the typical punishment for failure on an action is a loss of a certain number of turns. These turns are valuable as players need to recruit enough allies to defeat Ming before he has time to become powerful enough to squash any rebellion. While the statistics of the game are firmly rooted in roleplaying concepts, the resolution and consequence system still echoes board game resolutions and this is probably why many say the game plays more like a board game than a role playing game. This is one of the game’s key weaknesses, as is the inconsistency of resolution techniques. For example, fighting a Snow Dragon is resolved in a different manner than the encounter just discussed.

I imagine one could build a good game conflict resolution system built around the statistics highlighted in Flash Gordon, but this book lacks that system and there are no real rules for how to “role play.” Then again, there weren’t rules for that in most role playing games at the time either. What is intriguing here is the move away from tactical resolution to narrative resolution. Yes, it’s primitive and reviewers are right to critique it, but with only a slight tweak the system is essentially a parallel to Apocalypse World and/or InSpectres.

Rather than adapt the game’s current system, I’d probably just use this series of encounters as the basis for a Savage Worlds campaign. I also think it might be interesting to try to use a modified version of the Dragon Age pen and paper rpg system, the AGE system, as a substitute for the mechanics in the Flash Gordon rpg. There is something about the stunt system within those mechanics that I think really suits the pulp/cliffhanger genre. The AGE system is simple enough that it wouldn't require a lot of work to adapt it. One could also use the OctaNe system, itself a modification of InSpectres, if one wants to stick to the "narrative" feel that Bizar and Carter seem to have been attempting here. OctaNe succeeds where this game fails mechanically -- and OctaNe's system is ridiculously easy to learn and use.

Game Campaign System

This is where Flash Gordon really shines. The game's basic structure is that of a "recruitment" campaign where the players must journey from land to land -- based on how they are connected on an abstract schematic and not based on actual geography though the schematic takes those into account -- where they encounter various challenges and face various foes. For example, let's say our stalwart heroes find themselves in the Fiery Desert of Mongo. If they are mounted on Gryphs he journey will be easier than if they are not. It is possible, though not guaranteed, that the players will encounter Gundar's Gandits who will attempt to capture the players and sell them into slavery. The players may also encounter a Tropican Desert Patrol made up of troops loyal to Ming. The end goal of the area is for the group to recruit Gundar and his men, but that requires role playing and/or defeating the Tropican Desert Patrol. The description of the Desert and the possible encounters are abstract enough that they could easily inspire several sessions of roleplaying -- with a robust system like Savage Worlds -- all it lacks is a nice random encounter generator like the one found in The Day After Ragnarok to fill in the holes.

In essence, the Flash Gordon role playing game includes one or more major encounters for each geographical region of Mongo. As they players wander from place to place, they can/will face these challenges. What is inspired, and ahead of its time, about this structure is that the encounters are "story plot points" that must be achieved but can be achieved in the order of the player's choosing. There is room for exploration of the world at the same time that the players are succeeding at mandatory plot points. It is a narrative campaign without the railroading. Pinnacle Entertainment Group uses a similar structure in their Rippers, Slipstream, and Necessary Evil campaigns. It is a system that allows for narratively meaningful and fun play without the need for extraordinary planning on the part of the Game Master. All it lacks is a method, like the random encounter generator I mentioned above that is used by most plot point campaign systems, to fill in the scenes between the set pieces. Though it should be noted that there is sufficient information within the Flash Gordon rpg to easily construct a set of encounter generators with very little work.

Conclusion

Criticisms regarding the underlying conflict mechanical system, or lack thereof, are spot on when it comes to Flash Gordon. Character generation and conflict resolution lack any feeling of consequence or depth. BUT...If you want a campaign road map to use with another game system, preferably a fast-furious-and-fun one or a "narrativist" one, then this product is a deep resource. It will save you from having to read pages and pages of the old Alex Raymond strip in order to get an understanding of all of the minor details necessary for the creation of a campaign. You should certainly read the Alex Raymond strips, they are wonderful, but reading them should never be made to feel anything remotely like work. Bizar and Carter have done the work in presenting the campaign setting, all you have to do is adapt it to your favorite quick and dirty rpg mechanical set.