Sunday Summary – A colorful Slammers week of #wargame and #TravellerRPG fun mentioning @ADragoons @gmtgames

Short update follows…

Wargame

I will have another article coming to Armchair Dragoons this week talking about Rand Game Associates 1975 wargame Hitlers Last Gamble: The Battle of the Bulge by Dave Isby. “What,” you say, “another Bulge game?”

Commands & Colors Samurai from GMT Games is scheduled to arrive Monday, UPS says.

Traveller RPG

While my Wargame Wednesday looked at Hammer’s Slammers and wargames, this week I’m turning my attention to RPGs and Hammer’s Slammers.

Reading for Roleplaying…or #Wargame? – The Elusive Shift: How Role-Playing Games Forged Their Identity by Jon Peterson (@docetist) – or – I’m a Munchkin Grognard (#RPG #TravellerRPG)

My first role-playing game (RPG) was Traveller from game Designers’ Workshop back in 1979. In the same little store where I discovered my first wargame, Panzer by Jim Day from Yaquinto Publishing (1979), I found a small, very plain black box with three Little Black Books inside. So started my RPG adventures which would parallel my wargame experiences. As I was a solid military history reader and generally avoided fantasy science fiction in those days I never felt the urge to play Dungeons & Dragons like a few of my friends. But that was OK; we played the heck out of Traveller for RPGs and Star Fleet Battles (Task Force Games, 1979+) for wargaming back in those days. All of which means I entered the world of RPGs without realizing that I was amongst defining moments of the hobby. The Elusive Shift: How Role-Playing Games Forged Their Identity by Jon Peterson provides a “lost” history of how Dungeons & Dragons and other games came to define a new genre of gaming – the role-playing game.

As Peterson points out, Dungeons & Dragons (1974) did not call itself a role-playing game. Indeed, the cover stated it was, “rules for fantastic medieval wargames campaigns” (Peterson, 15). Starting from this observation, Peterson in The Elusive Shift takes the reader on a historical survey of how role-playing games came to be defined; or, as Mr. Peterson says:

It is not the ambition of this study to settle on a tidy dictionary defintion of role-playing game but instead to show historically how the game community came to grapple with agreeing on one.

Peterson, The Elusive Shift, p. 19

A Munchkin Grognard Traveller Perspective

Like I already stated, my first foray into RPGs was through Traveller, not D&D. At the same time I was entering the wargaming hobby. Forty years later I consider myself a wargame Grognard, that of an “Old Guard” of players who have been involved in the hobby a long time. So it was interesting to realize that in RPG terms of the late 1970’s and early 1980’s that I was a “munchkin.” As Peterson relates:

It was around this time that the pejorative term munchkin entered the role players’ vocabulary. The Wargamer’s Encyclopedic Dictionary (1981) defines a munchkin as “a young wargamer, generally under 14 or 16 years of age,” in contrast to a grognard, “a wargamer who has been in the hobby a very long time.”

Peterson, The Elusive Shift, p. 232

As I was 12 years old when I got my first wargame and RPG, I was actually a very young munchkin which is probably why I missed out on so much of the background fighting over what the RPG hobby was; I simply did not have the money to subscribe to all those newsletters or magazines where the discussion was taking place! Even if I did subscribe, as a sixth-grader the discussion may even had gone right over my head (figuratively and literally).

Through reading The Elusive Shift I also came to discover just how much of an influence Traveller has on my definition of an RPG. Peterson goes so far to call Traveller a “transcending design” (p. 173) and devotes an Intermezzo in his book to the game. Since Traveller was my first, and for several years my only, RPG* when I read the “rules” I accepted them as “the way” without question. Peterson points out that how one plays Traveller is a matter of player preference; “There are three basic ways to play Traveller: solitaire, scenario, and campaign. Any of these three may be unsupervised (that is, without a referee; the players themselves administer the rules and manipulate the situation” (Traveller Book 1, p. 3). To this day I have no problem playing an RPG solo; it has always been an option from the beginning. I also have no problem setting up a one-shot scenario or digging into a campaign. Again, that has always been “just the way it is.” I also was very happy to see Jon Peterson call Traveller, “perhaps one of the most adaptable of the designs of the 1970s” (p. 173) though he says that because the game exemplifies the extremes of both open-ended (with a Gamemaster) and close-ended (no referee) systems. Without trying to ignite an “Edition Wars” argument discussion here I’ll just say that these days I am very happy with the Cepheus Engine version of Traveller which is very similar to the original Little Black Books Classic Traveller from decades ago.

In The Elusive Shift Peterson shows how Dungeons & Dragons grew out of both the wargaming and science fiction fan communities. Again, as I entered both genres of hobby gaming at the same time I didn’t really see any “legacy” issues . All of which means I never really got into the whole “D&D is a wargame” controversy discussion because RPGs and wargames were always two related-yet-distinct facets of hobby gaming to me.

To this day, the wargame community constantly grapples with the age-old question “What is a wargame?” Heck, even I took a stab at answering that question in an episode of the Mentioned in Dispatches podcast for the Armchair Dragoons. Peterson’s The Elusive Shift shows us how a closely related community grappled with a very similar defining issue. This book won’t give wargamers an answer to their question but it certainly can promote understanding of how the RPG community came to some agreement.

Coming together. In agreement. What a novel concept!

Citation

Peterson, Jon, The Elusive Shift: How Role-Playing Games Forged Their Identity, Cambridge: The MIT Press, 2021 (Apple Books electronic edition)


*I’m not sure what my second RPG was, but it may have been Commando by SPI (1979) which Peterson notes is both a wargame AND and RPG. I know my copy has marked up charts where we tried to convert Commando tables for use in our Traveller activities. Behind Enemy Lines (1st Edition, FASA 1982) is clearly my next RPG after Traveller, though some might argue that it is more a skirmish-level wargame adventure guide than a “true” RPG.

#Wargame Wednesday – Searching for My Strategic #TravellerRPG Wargame

In a recent post I discussed my search for a #TravellerRPG wargame for use in ground combat. In the course of that posting, I talked about several different wargames and what I liked, or didn’t like, about them. Since I started down that rabbit hole, I decided to dig a bit further by taking a deeper look back at the original combat systems from the Classic Traveller-era (1977-1981).

The Traveller Combat System

Along this voyage of (re)discovery I came to the realization that there is no one single “Traveller Combat System.” Between 1977 and 1981 Game Designers’ Workshop (GDW) gave us EIGHT (8) different ground combat systems “For Use with TRAVELLER.” Broadly speaking, I see the eight systems divided into two broad categories; Strategic and Personal/Tactical. The eight systems, many found within their own games, are:

  • Imperium, Classic Traveller Game 0, 1977 (Strategic)
  • Traveller Combat System, found in Classic Traveller Book 1: Characters and Combat, 1977 (Personal)
  • Mercenary, found in Classic Traveller Book 4: Mercenary, 1978 (Tactical?)
  • Snapshot, Classic Traveller Game 2, 1979 (Personal)
  • Azhanti High Lightning, Classic Traveller Game 3, 1980 (Personal)
  • Fifth Frontier War, Classic Traveller Game 4, 1981 (Strategic)
  • Invasion Earth, Classic Traveller Game 6, 1981 (Strategic)
  • Striker, Classic Traveller Game 7, 1981 (Tactical)

[Of note, Dark Nebula, Classic Traveller Game 5 (1980) is basically a reskinned Imperium and I don’t treat it as a separate game system.]

In this post I’m going to look at the Strategic combat systems for the Traveller roleplaying game. Let us begin by going back to the beginnings of the RPG hobby in the mid-1970’s and a little corner of Indiana with a group calling themselves Game Designers’ Workshop (and pay attention to where the apostrophe is placed).

Strategic Traveller Wargames

Imperium – Empires in Conflict: Worlds in Balance (1977)

Imperium (GDW 1990 Edition)

Imperium is known as Classic Traveller Game 0. The number reflects the fact the design predates release of the Traveller RPG system. As author Shannon Applecline tells us in Designers and Dragons: The ’70s

Meanwhile, GDW was still playing with science-fiction designs. In 1975 and 1976 they worked on the prototype of a wargame called Imperium (1977). They finally published it in 1977 in a very different form, but in its original incarnation Imperium imagined a war between humans and many alien races, among them the lion-like Aslan, the bee-like Hivers, the dog-like Vargr and the mercenary Dorsai. Imperium also provided rules for individual characters — the sons of the leaders of the war — who progressed through individual careers and provided bonuses to armies based on the careers selected.

Both the alien races and the careers would be incorporated into GDW’s second and most notable RPG: Traveller.

Shannon Applecline, Designers and Dragons: The 70’s, Evil Hat Productions, 2014, p. 158

Here is how Imperium introduces itself:

lmperium is a science-fiction game about interstellar war. Several hundred years from now, Terra reaches the stars, only to find that they are already owned by a vast, sprawling interstellar empire: the Ziru Sirka (the Grand Empire of Stars or Imperium). The heavy hand of the lmperium and the expansionism of Earth lead naturally and inexorably to interstellar war. lmperium is a boardgame of that conflict.

Imperium Rule Book, p. 2

Imperium is what I term a grand strategic wargame. The scale of the game is six-month turns and 1/2 parsec (1.67 light years) per hex. If you are a Traveller RPG aficionado, you probably recognize the map scale is different and not the usual 1-parsec per hex. In keeping with the grand strategy design, Imperium includes rules for economics and both space and planetary warfare. The game actually has three distinct combat subsystems; “Space Combat,” “Planetary Surface/Space Interactions,” and “Surface Combat.” In this post I am focusing on the ground warfare aspects of the design found in the rules for “Surface Combat” in the core Rule Book starting on page 8.

If one makes it past the Space Combat and Planetary Surface/Space Interactions phases of an Imperium game turn (representing the deep and close-space battles) then a Surface Combat action may be fought. The combat mechanic here is the very traditional “battleline” where opponents are paired up. There is a very Avalon Hill War at Sea-like vibe to this combat mechanic and given WaS was published in 1975 is it possible the GDW designers took some inspiration?

In Imperium, Surface Combat begins with both players taking their forces and “pairing them off” against each other. If the attacker is unable to pair-off against all the defenders, no planetary assault is possible. If all combatants have been paired, any excess combatants can be doubled or even tripled up against. Optionally, forces not engaged can be “screened” and will not participate in the battle.

[As I reread the Surface Combat rules closely, I realized I had missed an important element over the many years played. I always assumed that only Troops, Planetary Defense Markers, and Outposts participated in Surface Combat. However, ships also participate!]

Paired off Imperium combatants now fight a round of combat by first determining their combat differential and then rolling on the appropriate column of the Surface Combat Results table. Regular troops attacking jump troops are given a round of defensive fire before the jump troops fire back to simulate the lack of heavy firepower jump troops possess (i.e. jump troops are great on offense but poor on defense). Possible combat results are either “No Effect” or “Destroyed/Neutralized.” Surface combat continues in rounds until all committed troops of one side are eliminated.

Surface Combat in Imperium, indeed any combat in Imperium, does not factor in a tech level difference. In the history of the game, the combatants were actually balanced technologically (although they designed ships using different doctrines) until the advent of the Terran battleship which appears in an Optional Rule.

Fifth Frontier War: Battles for the Spinward Marches (1981)

Fifth Frontier War (GDW, 1981) Rule Book

The cover of the rule book for Fifth Frontier War (FFW) carries the tagline “For Use With TRAVELLER” above the title. Here is how the game introduces itself:

Poised just beyond the frontier of the Imperium stand the war fleets of the Zhodani Consulate. Four times in the past five hundred years, they have attacked in campaigns to wrest control of the vital resources and rich worlds of the Spinward Marches from the Third Imperium. Now they strike again, and the Fifth Frontier War begins in earnest.

Fifth Frontier War is a Traveller campaign game portraying the progress of a far-reaching interstellar war and its effects on the many worlds that are its battlefield. The game is playable independently as a tense, fast-moving simulation of interstellar war. Rules cover starship squadrons and space battles, troop units and worlds at war, and the details of long-range interstellar planning. Special rules cover the operation of ship fleets, the use of naval bases, troop carriers, and advanced technological levels. Special charts cover every aspect of combat during the game.

Fifth Frontier War includes a large, four-color map of part of the Spinward Marches, complete with planetary surface boxes detailing the many planets within the area. Three sheets totaling 720 die-cut counters provide starship squadrons, troop units, fleet markers, admirals, and other details essential to the game. The rules booklet details how to play the game, while charts provide reference information. Two dice are included to help generate random numbers for combat.

Fifth Frontier War is playable by itself, but familiarity with the Traveller science-fiction role-playing system will aid in understanding the background history. The game may be played in 4 to 6 hours, and can usually be finished in an evening of play. It is designed for two players, but up to four may be involved if desired.

Fifth Frontier War, Rule Book, p. 2

The line, “…familiarity with the Traveller science-fiction role-playing system will aid in understanding the background history” is very insightful. FFW is set in the Traveller universe, but it is not an essential part of the roleplaying game. Like Imperium before it, FFW is another grand strategic wargame. This time, however, the setting is more closely tied to the Traveller material.

Leveraging the closer ties to Traveller, the scale in FFW uses several for the roleplaying game’s conventions. Each turn in one week, the same as the time spent in jump space, and each hex is one parsec.

FFW, like Imperium before it, uses several different combat subsystems in play. “Surface Combat” comes after “Space Combat” and “Interface Combat” in the Combat Phase of each turn. “Surface Combat” specifically deals with troops present on a world engaging in combat.

Resolution of surface combat in FFW is again very simple. The combat factor of a unit can be split to attack multiple defenders or they may combine with other units. The total of attacking combat factors is compared to defending combat factors to derive attack odds. Using the Troop Combat Results Table both the attacker rolls 2d6 and cross-references the results. Combat results are applied after all battles are complete. The combat result is expressed as the percentage of the force destroyed with the results applied at the end of the phase.

Technology makes a difference in surface combat in FFW. The combat factor of armored units is doubled in surface combat. Elite units also have their combat factor doubled. (Mercenary units have their strength halved if currently at 50% or more casualties; their heart isn’t in it anymore.) Most importantly, after the combat odds are determined, but before any dice are rolled, the relative tech levels of the force are considered. The difference in tech level becomes a column shift on the Troop Combat Results Table. Of note, the atmosphere of the planet is also a consideration, but appears in the form of a die roll modifier, not a column shift like technology. Just as importantly, the tech level of the force is determined by the lowest tech level unit participating in the combat.

Let’s see how surface combat plays out using the example in the rule book from FFW. It’s a bit long and the numbers may look big but in reality it goes quick once you try it. Pay close attention to how dramatic the column shifts can be from different tech levels fighting each other:

The Zhodani player has landed two tech level 14, full strength 20-factor troop units on a tech level 10 Imperial world having a tech level 15, full strength 5-factor troop unit and a 150-factor defense unit at 20% losses (thus having a current strength of 120). The Zhodani player attacks the Imperial troop unit using 15 factors; the combat odds are 3:1 (15:5) and are shifted one column to the left (to 2:1 ) due to tech level difference (14 -15 = -1 ). The dice roll is 5 and is not modified, as the atmosphere of the world is normal. Thus, 40% losses are inflicted on the Imperial troop unit. The Zhodani player attacks the defense unit using his remaining 25 factors. The combat odds are 1:5 (25:120) and are shifted four columns to the right (to 1.5:1) due to tech level difference (14 – 10 = 4). A 6 is rolled, and the unit takes 20% losses, increasing its total losses to 40%. Losses to the Imperial units are not implemented until the end of the combat. The Imperial player attacks one of the Zhodani units with all 5 of his tech level 15 factors. The combat odds are 1:5 (5:20). He could have used some of the factors from the defense unit to raise the odds, but this would have meant an unfavorable tech level difference due to the defense unit’s lower tech level. The tech level difference is (15 -14 =) 1, which means the attack is resolved on the 1:3 column. The dice roll is 9, and thus the attack has no effect. The Imperial player attacks the other Zhodani unit with the 120 factors of the defense unit. The odds are 5:1 (120:20) and are shifted four columns to the left (to 1:1) due to tech level difference (10 -14 = -4). The dice roll is 7, resulting in 10% losses to the Zhodani unit. Surface combat resolution is now finished for this world, and the combat results are implemented: a 10 casualty marker is stacked under one of the Zhodani units, a 40 casualty marker is stacked under the Imperial troop unit, and the 20 casualty marker for the defense battalions is exchanged for a 40 casualty marker.

Fifth Frontier War, Rule Book, p. 15

Near the end of the rules for FFW the designers give some hints for using this wargame in a Traveller RPG campaign:

ROLE-PLAYING

Role-playing appears to Traveller players to be a simple series of adventures in which situations are presented, dealt with by the players, and resolved. The Traveller referee knows that there is a lot more to running a consistent, interesting Traveller campaign; preparation for each situation is required, contingencies must be foreseen, and background laid out. Fifth Frontier War is intended as a partial solution to the problems of presenting situations to Traveller players.

BASIC CONCEPT

Fifth Frontier War is a detailed adventure game of the progress of the current war between the Imperium and the Zhodani in the Spinward Marches. It progresses on weekly turns with forces representing squadrons of military starships and battalions or more of fighting troops. The game is intended to be played for enjoyment of and by itself. Indeed, in situations where no referee is available, or where only two Traveller players can get together, Fifth Frontier War allows them to play a form of Traveller without a referee.

Ultimately, the Traveller referee will have enough experience with the game and its rules to be able to use it in a Traveller campaign. At that point, Fifth Frontier War can be used to indicate the greater conditions that are happening in the Spinward Marches, often just beyond the knowledge of Traveller adventurers. Players can be idly exploring a world in the Spinward Marches and be suddenly confronted with a major space battle in the skies above them, or encounter major friendly or enemy troop units establishing bases. The point is that they cannot know ahead of time exactly what activity is taking place even one system away, and that activity could be deadly to them.

Fifth Frontier War, Rule Book, p. 19

Invasion: Earth – The Final Battle of the Solomani Rim War (1981)

Invasion: Earth (GDW, 1981)

Invasion: Earth (IE) was released in the same year as FFW but does not carry the “For Use With TRAVELLER” tag across the cover. Maybe this is because Invasion: Earth is a historical game in the Traveller setting, taking place some five years before the default start of the Traveller setting from the Little Black Books.

Once again, I’m going to let the introduction of Invasion: Earth explain itself:

INVASION: EARTH

Invasion: Earth is a two-player game of the assault on Terra by the forces of the Imperium; this battle was the last major campaign of the Solomani Rim War. (A section at the end of the rules gives a brief outline of this war.) One player represents the commander of the lmperial invasion force and controls all lmperial regular, colonial, and mercenary units in the game. The other player represents the commander of the Solomani forces assigned to the defense of Terra and controls all Solomani units in the game.

TRAVELLER

Invasion: Earth is a complete game, playable in itself. It may also be used in several ways to supplement or to provide a background for Traveller campaigns and adventures, as indicated in a section following the rules on the play of the game.

Invasion: Earth, Rule Book, p. 3

Invasion: Earth is a game that shows the strategic-level of warfare, but at a much smaller scale than either Imperium or FFW. One game of Invasion: Earth is a single planetary invasion; one complete round of surface combat at one planet in Imperium or Fifth Frontier War. Each turn in Invasion: Earth is two weeks. Here is how the rules describe surface units:

Troop units are the field formations which, through the use of manpower and firepower, are the ultimate defenders or attackers of a piece of terrain. Due to the high technological levels of the opposing forces, the basic transport vehicle is the anti-gravity vehicle; hence troop units are quite mobile. PD [Planetary Defense] units are collections of energy weapons and missiles capable of engaging naval units bombarding the surface of a world. Each has an intrinsic garrison assigned to it; hence, a PD unit is rated and treated similarly as a troop unit. Most PD units are large, static installations and are immobile, while a few small PD units are mounted on grav vehicles.

Invasion: Earth, Rule Book, p. 3

The combat system used in Invasion: Earth is near-identical to FFW. Adjustments for Armor, Elite, and Mercenary units are still here. Tech level differences shift columns on the Troop Combat Table. The major difference between Invasion: Earth and FFW is the introduction of movement rules.

Like FFW before, the rule book for Invasion: Earth includes extensive ideas for integrating the game with a Traveller RPG campaign. Additionally, though Invasion: Earth focuses on one (“historical”) planetary invasion, the end of the rule book also includes a section for taking the rules and using them for other campaigns, including troops not equipped with grav vehicles (the default in IE).

JTAS Articles

JTAS #9 Cover

A review of the first 24 issues of the Journal of the Traveller’s Aid Society reveals only a small handful of articles related to rules for these strategic wargames. Not surprising, in a way, given JTAS was intended to support the Traveller RPG game and not the wargame line of GDW.

JTAS 1 (1979)

This issue contained the article “Diplomacy in Imperium” which introduced a variant using Emissaries into the campaign. Meh.

JTAS 5 (1980)

This cover article in this issue is “Imperium: Ground Combat Module” by the same Roberto Camino that did the “Diplomacy” variant in Issue 1. The ground system he introduces is something between Imperium and Invasion: Earth with planets depicted on two hemispherical maps. This module is intended to replace the Surface Combat phase of Imperium.

JTAS 9 (1981)

This was a “special” Fifth Frontier War edition with lots of background material for the game (some of which was duplicative of the rule book).

What’s the Best Strategy?

As similar as two of these game are, all three of these strategic Traveller wargames offer very different approaches to the Traveller RPG universe. That said, all three of these games are clearly wargames-first and the integration with the Traveller RPG is difficult at best. This is very much unlike almost every Personal/Tactical combat game that is tightly tied to (even forming) the roleplaying game rules.

Imperium is by far the most abstract of the strategic models and unsurprisingly the easiest to learn and play. It also has no expressed technological aspect. Coming before the publication of Traveller, it is also probably the most difficult to “fit” into a Traveller RPG campaign setting as it uses many elements of the setting but in ways that are not directly relatable to the RPG.

Fifth Frontier War, regardless of the “For Use With TRAVELLER” tagline, is a separate wargame set in the Traveller RPG universe. FFW probably does the second-best job of capturing the technological difference of any Traveller wargame, either Personal/Tactical or Strategic. Although there are extensive notes describing how to use FFW in a Traveller RPG campaign, the truth to the matter is the two systems, though set in the same universe and sharing common foundations, are too different in scale to be combined.

Invasion: Earth is the best wargame/RPG system, either Personal/Tactical or Strategic, to capture the impact of technology on ground warfare in the Traveller universe. Like FFW, however, integrating Invasion: Earth into a Traveller RPG campaign is very challenging due once again to the differences in scale. Invasion: Earth is closer to an RPG than FFW, but fighting two weeks of battles between Regiments or Armies is far above the “personal view” that the Traveller RPG is built on.

Interestingly, even though there are more than few articles that discuss integrating the tactical-scale Striker (GDW, 1981) into Traveller campaign, I find no articles or rules about integrating Striker into Imperium, FFW, or Invasion: Earth. I realize Striker was published near-simultaneous to FFW and Invasion: Earth, but you would think even after the fact somebody might had made an attempt in JTAS. Guess not. Once again, the difference in scale is probably just too much to overcome.


*Interestingly, the Traveller Combat System was never called TCS. Within the Traveller rules system, TCS is the abbreviation for “Trillion Credit Squadron.”

#RPGThursday – Searching for My Personal/Tactical #TravellerRPG #Wargame

In a recent post I discussed my search for a #TravellerRPG wargame for use in ground combat. In the course of that posting, I talked about several different wargames and what I liked, or didn’t like, about them. Since I started down that rabbit hole, I decided to dig a bit further by taking a deeper look back at the original personal and vehicle combat systems for roleplaying games from the Classic Traveller-era (1977-1981). Along the way I discovered:

  • I didn’t remember as many things about early Traveller as I thought I did
  • There is more variety to the systems than I remember
  • Technology plays a much lesser mechanical role then I remember.

The Traveller Combat System

When I started my review, I immediately discovered there is not one single “Traveller Combat System” though, as you will see, there is a something called the Traveller Combat System. Indeed, between 1977 and 1981, Game Designers’ Workshop (GDW) gave us EIGHT (8) different ground combat systems. Broadly speaking, I see the eight systems divided into two broad categories; Strategic and Personal/Tactical. The eight systems, many found within their own game, are:

  • Imperium, Classic Traveller Game 0, 1977 (Strategic)
  • Traveller Combat System, found in Classic Traveller Book 1: Characters and Combat, 1977 (Personal)
  • Mercenary, or the Abstract System found in Classic Traveller Book 4: Mercenary, 1978 (Tactical?)
  • Snapshot, Classic Traveller Game 2, 1979 (Personal)
  • Azhanti High Lightning, Classic Traveller Game 3, 1980 (Personal)
  • Fifth Frontier War, Classic Traveller Game 4, 1981 (Strategic)
  • Invasion Earth, Classic Traveller Game 6, 1981 (Strategic)
  • Striker, Classic Traveller Game 7, 1981 (Tactical)

[Of note, Dark Nebula, Classic Traveller Game 5 (1980) is basically a reskinned Imperium and I don’t treat it as a separate game system.]

In this post I’m going to look at the five Personal/Tactical combat systems for the Traveller roleplaying game. A later post will look at the strategic systems. For now, let’s go back to the beginnings of the RPG hobby, and a little corner of Indiana with a group calling themselves Game Designers’ Workshop (and pay attention to where the apostrophe is placed).

Personal / Tactical Systems

The original Traveller

The Little Black Books (1977)

The original rules for the Traveller roleplaying game were laid out in the three Little Black Books first published by GDW in 1977. Book 1: Characters and Combat detailed the first iteration of what came to be known as the “Traveller Combat System.”*

The Traveller Combat System is a combat resolution model for personal combat or what many wargamers often refer to as “skirmish” scale. The system was designed to resolve combat actions between individuals or small groups (like a party of travellers). Each round of combat represented 15 seconds.

I term the Traveller Combat System “semi-abstracted.” The combat procedure in the Traveller Combat System is very simple and straightforward but lacks many usual wargame-like details. In every battle the players and referee step through a simple four-step process:

  • Determine surprise
  • Determine initial range
  • Determine escape/avoidance
  • Resolve combat wherein each character declares both a movement status and an attack.

The roll for surprise is subject to several modifiers. I was a bit surprised to see that three of the seven possible modifiers relate to military associated skills – which makes sense given the character generation rules that emphasize military experience. A further three modifiers relate to whether a vehicle is used and the size of the party. The last modifier is for Pouncer animals; very useful in wilderness encounters!

Terrain is a possible modifier for determining range. Encounter distances are broken down into five bands; Close (touching), Short (1-5m), Medium (pistol range, 6-50m), Long (rifle range, 51-250m), and Very Long (extreme range, 251-500m).

Rather than a square or hexagon-gridded map, the Traveller Combat System uses Range Bands. The rules recommend (and I clearly remember using) regular loose leaf lined paper. The number of lines away determines your range. Movement was by bands.

Combat in the Traveller Combat System is based on a simple “Roll 8+ on 2d6 to hit the target.” Die modifiers come in several flavors:

  • Melee Weapons require Strength with strong or weak characters gaining an advantageous or weakened blow modifier
  • Ranged Weapons require Dexterity, again with advantages for high Dexterity characters
  • Using the Weapons Matrix, cross reference the Attacker’s Weapon with the Defender’s Armor yields another DM
  • Using the Range Matrix, each different Attacker’s Weapon yields another DM; this is also where the damage (expressed in number of d6) is found.

Wounds in the Traveller Combat System are determined by different number of d6. The total of the first hit is applied to one personal characteristic and can be enough to render the character unconscious. After the first hit, the dice in subsequent attacks are spread out over the Strength-Dexterity-Endurance characteristics (i.e. if your attack scores 2d6 hits, the total of die #1 can be applied to one characteristic and the total of die #2 to another). When a single characteristic drops to zero the character is unconscious. When two are reduced the character is seriously wounded and if all three go to zero the character is killed. Bottom Line: The Traveller Combat System is DEADLY.

In keeping with the personal combat focus of the Traveller Combat System, the personal characteristics of strength, dexterity, and endurance are very important in combat. As already mentioned, strength and dexterity grant a bonus, or penalty, in combat. Endurance is essential in melee combat; every “blow” takes endurance. Once all your endurance is gone no more blows are possible until after a rest period.

Character skills also factor in the Traveller Combat System. Knowing how to use a weapon grants a bonus (with more skill granting a bigger bonus); untrained is a penalty. Expertise is also used to parry in brawling or blade combat.

One rule I did not remember in the Traveller Combat System is morale. Basically, when at least 20% of the party is unconscious or killed, you must start making morale throws. Failure means the party breaks and runs. I absolutely do not remember this rule; I think we ignored it because it took away player agency. Or maybe we just didn’t use it because the combat system is already deadly enough that we didn’t get into combat unless we were very sure of ourselves.

I also notice now that there is no vehicle combat rules in Book 1. A party can be in a vehicle at the start of combat, but there are no rules for fighting vehicle to vehicle.

Mercenary (1978)

In 1978, GDW published what nowadays we would call a splatbook for mercenary characters. Not only did Classic Traveller Book 4: Mercenary include expanded character generation rules, it also included new combat rules. Actually, it makes references to three different rules systems:

There are three means of resolving a mercenary mission: the standard Traveller adventure/combat system, the abstract system included later in this section, and a free-form system created by the referee. All three are discussed to a greater or lesser extent, but it should be born in mind that these are intended only as a general guide to the referee, not as a definitive miniatures rules set.

Book 4: Mercenary, “Battles”, p. 31

When introducing the Abstract System, the designers tell us, “The abstract mission resolution system is particularly valuable in resolving a mercenary mission involving large numbers of troops on one or both sides and in which player characters are not primary participants (serving as NCOs in an infantry battalion, for example).” It is telling that the Abstract System has no time or distance scale; it has all been abstracted out.

Combat resolution using the Abstract System in conducted in two broad parts: preparation and resolution. During preparation, the characteristics of the opposing forces is determined, to include the Mission, Tech Level, Size of the force, and Efficiency. This is accomplished through a series of die rolls. At this point the referee also needs to determine a preservation number for the force.

Once the two sides are prepared, the Abstract System moves to resolution. Once again, a series of die rolls determines the Element Engaged, the Encounter Type and then the actual Combat Resolution. Given the involvement of player characters, there is also a chance of Personal Casualties which is addressed at this point.

Although I call the Mercenary Abstract System a tactical-level battle system, the reality is a bit fuzzy. The size of the force and element engaged can range from a Fire Team nominally of four soldiers up to an entire Brigade of 1500 troops.

The Abstract System lives up to its name; it is highly abstracted to the point all the tables necessary for preparation and resolution are on one digest-sized page in Book 4. The combat results table is actually a Firing Matrix where the firing unit is cross-referenced with the Target Unit to get a die roll modifier (DM). At this point, the Tech Level difference of the two units is used as a +/- DM. Casualties are expressed in percentage of the force with personal casualties dependent upon how much of the force was put out of action. The battle continues in rounds until one side or the other reaches its preservation level and withdraws.

When it comes to vehicle combat, Mercenary is very silent on the issue. Like the Traveller Combat System, no vehicle combat rules are provided. The closest Book 4 comes is a discussion of military vehicles at different tech levels.

Snapshot (1979)

The next personal combat system in the Traveller universe is Snapshot: Close Combat Aboard Starships in the Far Future. The title alone should tell you the focus here; combat between individuals within the closed confines of starships. The rules even go so far as to state they are not intended for outdoor encounters or ranges greater than 50-60 meters.

In order to make Snapshot work, GDW uses the same 15 second rounds but instead of the range bands in the Traveller Combat System they introduce a square grid. Each grid square is 1.5m, conveniently the same scale used to draw starship deck plans. With the introduction of grid squares, many other wargame-like rules are introduced. There now are stacking limits and facing considerations.

Instead of the move/attack action in the Traveller Combat System, in Snapshot each character is allotted a number of Action Points (AP) equal to the sum of their Endurance and Dexterity (with a minimum of six). Every action has a different AP cost. This is where one of my favorite wargame rules, The Expletive, is found.

“Frak you!”

Combat resolution in Snapshot is virtually identical to the Traveller Combat System except the separate Weapons and Range Matrix tables is collapse into one table. Wounding is the same with hits being applied against personal characteristics.

Snapshot, being focused on close encounters aboard ships, has no vehicle combat rules.

Azhanti High Lightning

Azhanti High Lightning (1980)

The next combat system GDW gives us for Traveller is Azhanti High Lightning (AHL). AHL is both a sourcebook on a class of ships and a new combat game. It is a further progression of the Traveller Combat System and Snapshot. Like Snapshot, each combat round in AHL is 15 seconds and each square is the same 1.5m.

The major evolution of the AHL system is that each turn now consists of multiple action phases instead of the single action phase in Snapshot. In the Decision Phase the player secretly determines what the “strategy” of the turn will be: cover fire, aim, or move. Like Snapshot, players have AP to spend, but unlike Snapshot where the AP is determined by the sum of characteristics in AHL each character has a flat 6 AP in each of the five action phases.

The second major evolution in AHL is the combat system. The Weapons Table divides range into Effective, Long, and Extreme ranges each with its own base to-hit number. In many ways this new Weapons Table “builds in” many previous die roll modifiers. However, once a hit is made the resolution system from that point forward totally changes from pervious versions.

In AHL, once a hit is made you check the damage table. This die roll is modified by the Penetration Value of the weapon and any cover or armor for the target. Instead of applying damage to characteristics, wounds are described as Light, Serious, or Death with unconsciousness also possible. A new Melee combat system is also introduced using Melee Ratings of combatants.

Rules for integrating AHL with Traveller are provided. The formula for a Melee Rating is given, as well as other special rules about Danger Space for weapons. Interestingly, no skills are used as modifiers in AHL; here skill is subsumed into a single weapons skill rating on a counter. Morale and leadership bonuses are generated using the Mercenary system.

Again, I was very surprised to discover that AHL has no vehicle combat rules.

Striker (1981)

Striker (1981)

To understand what Striker represents to Traveller players, I think it is worth quoting the introduction at length:

Striker is a set of rules for science fiction ground combat using 15mm miniature figures. each player will command a force ranging from a platoon to several companies, consisting of a few dozen to over a hundred men, plus artillery, armored vehicles, and aircraft. The rules are intended to be easy for the beginning player to understand wile at the same time providing a comprehensive and detailed treatment of ground combat from the beginning of this century to the far future.

On important aspect in which Striker differs from previous miniatures rules is the role assigned to the player. In most games, a player simultaneously plays the role of every member of a military unit; no orders need to be given, and every man performs as the player likes. In Striker, realistic limitations have been put on the abilities of officers to command their units. Giving orders to subordinates is a time-consuming process; commanders will find it advisable to devise a simple plan and to give most orders in pre-battle briefings. Changes to this plan in the heat of action will be difficult except through on the spot leadership. For a more detailed discussion of this point, read Firefight, at the beginning of section II of this book.

The science fiction background of Striker is drawn from the universe of Traveller. All weapons and military technology described in Traveller (including Book 4, Mercenary) are included in Striker. These rules may be used in conjunction with Traveller or by themselves; no familiarity with Traveller is required.

In Striker, as in Traveller, technology is rated by tech levels; these rules cover weapons and equipment ranging from tech level 5 (about World War I) to tech level 15 (the level of Traveller’s Imperium). Present-day earth is about tech level 7.

Striker, Book 1: Basic Rules, “Introduction,” p. 4

Striker changed scales yet again, with each turn now representing 30 seconds and one millimeter on the table equaling 1 meter. Units are described principally by their morale (Recruit-Regular-Veteran-Elite) and an initiative rating. The sequence of play moved closer to a classic wargame with a Command Phase followed by First Player Movement – First Player Fire then Second Player Movement – Second Player Fire with a Panic Morale Check Phase at the end. As befits the core focus, command, communications, and morale all factor prominently in what a unit can, or cannot, do.

Instead of Action Points, units in Striker are assigned orders. The number of orders and how long it takes to communicate them are the heart of the command and communications rules. A single order can consist of three components: movement, fire, and a rally point. For example, an order might be, “Move to the crest of Hill 17, through the forest, at fastest speed. Fire at enemy units detected. Rally Point: Little Star crossroads.”

Fire combat in Striker is an evolution of the AHL system. Hits cause casualties (Light-Serious-Destroyed) like in AHL, but in Striker the impact to morale is also considered. Morale checks are made when proximate to an enemy, when taking casualties, or if a unit routed nearby (to avoid panic). Four different results of a failed morale check are possible: Suppressed, Fall Back, Forced Back, and Routed. Surrender is also possible.

I was absolutely dumbfounded to realize that it was not until the publication of Striker in 1981 that vehicle combat officially came to the Traveller RPG universe. The system is interesting; when shooting at a vehicle the firing player declares either a “high” (vs turret) or “low” (vs hull) shot. The angle of attack is also considered. After that the fire procedure is basically the same as any other combat in Striker.

[I went back and looked to see where vehicle combat may have had a start pre-Striker. I found the Judges Guild product Lazer Tank (1980) that has a very simple vehicle combat system but is unlike anything anywhere else in Traveller. I also identified vehicle rules in the Amber Zone article “Pursue and Destroy” from Issue 7 of the Journal of the Traveller’s Aid Society. This article, published in 1981 from Frank Chadwick, apparently still predates his Striker rules as it refers to using Mercenary and Azhanti High Lightning to resolve combat. A methodology for converting AHL wound levels to vehicle damage is provided. The first published adventure to feature the chance of vehicle combat is Adventure 7: Broadsword that was published in 1982 and recommends using Book 1, Mercenary, and Striker.]

Striker also includes sections describing Planetary Defenses (Book 2: Equipment, Rule 76: Planetary Defenses) as well as Rule 77: Jump Troops. Rule 79 is Integration with Mercenary while Rule 80 is Integration with Traveller. Both focus on skills or the impact of morale and changes necessary to move between different wound systems.

However, it is the Vehicle Design Sequence that truly sets Striker apart from its predecessors. This “game within a game” aimed squarely at Traveller “systems engineers” is the foundation of every vehicle design system used since in the Traveller universe. Here is a methodology to create a vehicle that is described in common game terms and comparable across multiple tech levels. Truly an astonishing achievement.

Which One Should I Use?

When I look back on the history of personal/tactical ground combat systems for Traveller, I don’t look at it pessimistically and see too many choices. Instead I am ever the optimist and see many good choices that as a referee I can mix and match to my hearts content.

I love the Traveller Combat System. It is the most pure and simple, and probably the most supportive of good narrative play. The rules are super light and easy.

The Abstract System from Mercenary is good for “background” action. It can also be the primary system for resolving mercenary tickets if the players are running a mercenary company.

Snapshot and Azhanti High Lightning are good at what their focus is; shipboard combat. Comparing them, Snapshot is more RPG-like whereas AHL is more “wargame-y.” What I mean here is Snapshot, with action points determined by characteristics, is closer to the RPG but Azhanti High Lightning is the more refined rules set.

Since forever, I always assumed that Striker was the miniatures rules set for the Traveller roleplaying game. Reading the introduction, Traveller does not get mentioned until paragraph three. Instead, what we actually have in our possession is a set of miniatures rules for 15mm figures suitable for playing out small scale/unit actions with a set of rules that allow one to simultaneously employ multiple levels of technology. As important a role technology plays, the true focus of the game is actually on Command and the ability of leaders to communicate and coordinate on the battlefield. This makes Striker the most “wargame-y” of the group. As I already mentioned, the vehicle design system is a truly foundational part of the Traveller universe. However, the focus on command and not characters makes Striker’s use in a Traveller campaign a bit questionable.

When I look back on the history of personal/tactical ground combat systems for Traveller, I don’t look at it pessimistically and see too many choices. Instead I am ever the optimist and see many good choices that as a referee I can mix and match to my hearts content.

RockyMountainNavy, Dec 2020

I also note that the vehicle combat rules found in the modern Cepheus Engine version of the Original 2d6 Science Fiction Roleplaying Game did not appear in the early years of the GDW era. The Striker -based rules were still in use through at least 1994 when Striker II: Miniatures Warfare in the Far Future was published as part of Traveller: The New Era. The modern rules for vehicle combat use the same “actions” approach of personal combat in Cepheus Engine where each crew member gets one significant and two minor actions in a combat round (six seconds of time). I’m not absolutely sure, but this mechanic may have first appeared in the Mongoose Traveller 1st Edition published in 2008.

JTAS 9

JTAS Journey

I also found it interesting to look at what happened to these games after publication. Looking through the first 24 issues of the Journal of the Traveller’s Aid Society (JTAS) brought some further enlightenment.

JTAS 2 (1979)

This issue contains a very interesting rebuttal to an article in the June 1979 issue of The Dragon. JTAS editor Loren K. Wiseman responds to criticism of Mercenary with the comment, “To criticize a set of rules or a game because it has omitted some vital aspect of its subject matter is one thing, but to downgrade rules because they do not cover something beyond their scope is a little like saying ‘Squad Leader is a fairly good game, but I would have liked to have more air-to-air combat in it.'”

JTAS 12 (1981)

This issue had two Striker-related articles; “Striker Errata” and “Strike it Rich” where author J. Andrew Keith talks about using Striker as a new combat system or as a valuable source book.

JTAS 14 (1982)

Articles include “Civilian Vehicles for Striker” and “Foxhound” by J.D Webster (later famous for his Fighting Wings series of air combat wargames). “Foxhound” is billed as a Striker variant but a close reading reveals this is really a system for fitting flying vehicles into the Traveller Combat System, especially since it uses the same range bands. That said, weapons fire uses Striker….

JTAS 16 (1983)

Contributor Michael Wharton serves up “Merging the Striker and Traveller Combat Systems.” He focuses on converting the Striker damage levels to the point system of Traveller and adjusting Striker “to hit” at short ranges. During the course of the article, he hits on the major difference between Striker and the Traveller Combat System:

By its own admission, Striker is designed to deal with fairly large scale actions fought at moderate-to-long ranges. At the short ranges of many Traveller firefights, however, confined as they often are within starships or barrooms, the Striker hit determination tables become somewhat unrealistic. That an 8+ is required to hit a target only two meters away seems unlikely. Also, the difficulty of using long arms at very short range is not addressed.

“Merging the Striker and Traveller Combat Systems,” JTAS 16, p. 43

JTAS 17 (1983)

Both feature articles in this issue are for ground-pounders (almost). “Air Strike: A Close Air Support Rules Module for Mercenary” by T. McInnes provides what I call a very loose set of rules for integrating air support into the Abstract System. The second article, “Hunting Bugs: Striker Meets Horde” by John Marshall explains how to use Striker when playing Double Adventure 5: The Chamax Plague/Horde. Hmm…

JTAS 21 (1984)

The feature article, “Striker Weapons Systems Analysis,” does not appear in the Table of Contents. Some useful design notes to consider here but nothing really in the way of combat rules mechanics.

JTAS 22 (1985)

Two feature articles are included. The first, “‘Til They Glow in the Dark: Nukes for Traveller/Striker Campaigns” seems out of place for the Traveller default setting when one considers the Imperial Rules of War that forbid the usage of nukes. I guess this article can support alternate Traveller universes. The second article, “Seastrike – Underwater Combat in Traveller” mixes Striker with the ship design system High Guard.

JTAS 23 (1985)

Whoops! Forgot to print the “Striker Expanded Nuclear Warheads List” in issue 22. Here it is!


*Interestingly, the Traveller Combat System was never called TCS. Within the Traveller rules system, TCS is the abbreviation for “Trillion Credit Squadron.”

Feature image courtesy Ian Stead

#Wargame Wednesday – Getting slammed by Mongoose Traveller’s Hammer’s Slammers vehicle combat for #CepheusEngine #TravellerRPG

Having gone on something of a Traveller RPG kick of sorts, I recently dug into the vehicle combat rules for the game. Doing so brought back some good memories, as well as some bad ones.

Combatting Traveller

When it comes to the Traveller RPG, combat historically was divided into two formats; personal and large-scale. For starships, the “personal” scale is what is known as “Adventure Class Ships (ACS).” ACS ship combat was first spelled out in Book 2: Starships (GDW, 1977). Larger ships, called “Battle Class Ships (BCS)” were detailed in Book 5: High Guard (GDW, 1977, 1980). Likewise, for ground combat, the personal scale was found in Book 1: Characters and Combat (GDW, 1977) and the corresponding ‘mass combat’ rules were in Book 4: Mercenary (GDW, 1978) written by one Mr. Frank Chadwick. However, for ground combat the publisher of Traveller, Game Designers’ Workshop, took it a step further. They published a set of 15mm miniatures rules by Mr. Chadwick called Striker (GDW, 1981). I was unable to buy Striker back in the day, but I did have a small Judges Guild game expansion, Lazer Tank, that whetted my appetite for more.

Striker from GDW

Mr. Chadwick also designed the planetary invasion game Invasion: Earth (GDW, 1981) that I lusted over but didn’t actually own until this year. Suffice it to say that when I thought of combat in the Traveller RPG setting, I viewed it though a Frank Chadwick set of lenses.

Striker II (GDW, 1994)

Over the years I was able to acquire Striker II (GDW, 1994), part of the Traveller: The New Era edition of Traveller. Striker II was also designed by Frank Chadwick and part of his GDW ‘house’ series that used the same basic miniatures rules for World War I in Over the Top (GDW, 1990), World War II in Command Decision (GDW, 1986+), and the modern era in Combined Arms (GDW, 1988+). It also didn’t hurt that Traveller-adjacent RPG games like Twilight: 2000 (GDW, 1986) used another Frank Chadwick design for their ‘mass combat’ rules, in this case a combination wargame/roleplaying game supplement called Last Battle: Twilight 2000 (GDW, 1989).*

Last Battle: Twilight 2000 (GDW)

Somewhere after Striker II, the vehicle combat rules for Traveller changed and Mr. Chadwick was forgotten. I first noticed this when I picked up the Mongoose Traveller edition of Book 1: Mercenary (Mongoose Publishing, 2008) and found a very abstract set of rules. Suffice it to say I found the “Battle System – Large Scale Conflict in Traveller” not to my liking. Further, it was obviously written by people that had NO IDEA about weapons. It was actually comical; in the first edition the furthest the heaviest support weapon (in this case a Tech Level 15 Meson Accelerator) could shoot was 1.5….kilometers. There were many reasons I came to dislike Mongoose Traveller, but as a wargamer this pathetic approach was a major reason for me to disengage from their product line.

It was actually comical; in the first edition the furthest the heaviest support weapon (in this case a Tech Level 15 Meson Accelerator) could shoot was 1.5….kilometers.

I fought. I resisted. This was the time I was finally, after all those years waiting, to get my hand on a copy of Striker. I vowed never to use the Mongoose Traveller, non-Chadwick approach. That is, until the 2009 release of Mongoose Traveller Hammer’s Slammers (Mongoose Publishing, 2009). I love David Drake’s Hammer’s Slammers series of stories. I mean, this obviously was a real sci-fi combat game with Mr. Drake writing the Forward. I was sure that this was going to make Mongoose Traveller ‘mass combat’ awesome!

Mongoose Traveller Hammer’s Slammers (2009)

Defanged by a Mongoose

I was severely disappointed in the Mongoose Traveller Hammer’s Slammers. Oh, I enjoy having the history and characters and equipment of Hammer’s Slammers translated into game terms. Combat was another matter, with two approaches used in the book, neither of which resonated with me.

“Chapter 9: Vehicle Combat” was an extension of the Mongoose Traveller personal combat rules. It introduced a new scale, “Vehicle Scale” into the game. This scale was supposed to be a bridge between the personal and starship scales. Vehicle combat also continued the “vehicle as a character” approach to game rules. Every turn, the player characters (PCs) or non-player characters (NPCs) got actions. The most important action was Attack which is a Skill Check. Let me show you an example of how it works:

Lieutenant Danny Pritchard with Gunner-Turrets 2 skill fires the 20cm Powergun of his M2A1 supertank against the side of a TR6BKU-1 Black Skorpion turretless tank killer. The range is 2km making this a Long Range shot (+0 DM). Pritchard’s tank is moving but less than half-speed (-1 DM) as he shoots. He rolls 10 on 2d6, modified to 11 (+2 Skill, -1 Moving) which is more than the 8+ required for a hit. The 20cm powergun rolls 20d6+20 Super Destructive damage. Super Destructive means the first 20 points of the target’s armor is obliterated; in this case the 132 points of side armor is reduced to 102. The 20cm powergun then scores 82 points of damage – which the 102 points of armor stops. The Black Skorpion has escaped destruction, this turn.

The Black Skorpion fires back (assume an average crew with Gunner 2). At Long Range the 22cm coilgun has a -1 DM. The 2d6 To Hit roll is 7, modified to 8 with the total +1 DM – barely a hit! The 22cm coilgun scores 14d6 MegaAP damage. The damage total rolled is 49. The MegaAP means that the coilgun ignores armor points equal to 4x the number of dice rolled – in this case 14×4 or 56 points of armor. However, the front of the M2A1 is a whopping 175 points.

Laughing, Pritchard halts his hovertank and lines up another shot. Hit on the side again, the Black Skorpion loses another 20 points of armor, leaving it with 82. The Slammer’s powergun scores 92 damage, of which 10 penetrate and convert to 3x Single hits. Rolling for hit location yields Weapon (1st Hit = No Effect) – Sensors (First Hit = -1 to all future sensor checks) – Hull (31 remaining).

In the example above I hope you can see that Pritchard’s tank is proof against the deadly “tank killer.” It’s also going to take another hit, or two or three more, to finally destroy the Black Skorpion. It all seems very undramatic. I even tried to recreate the epic final battle from Rolling Hot where Task Force Ransom takes on 35 Consie light tanks. I couldn’t. That’s because the major problem with the vehicle combat in Mongoose Traveller Hammer’s Slammers is that it doesn’t get the attack vs armor right.

It all seems very undramatic.

“Chapter 10: Conflict,” starts off by saying, “The aim of the rules is not to precisely simulate a conflict but to give the Referee a framework for designing adventures.” There is certainly enough in this chapter to create battle situations, but the section “Resolving the War” seems to me like it is an adjudication system for, well, resolving the war! Except this time the resolution is highly impersonal with leaders and factions and DMs for successful missions. This is a campaign game system not a combat resolution model.

Cepheus Engine Rebirth?

After the debacle of Mongoose Traveller Hammer’s Slammers I went in search of other rule sets for use in my Traveller campaigns. I experimented with both Dirtside II (1993) and Stargrunt II (1996) from Ground Zero Games. I tried Tomorrow’s War (Second Edition) from Osprey Publishing (2011). I really like Dirtside II as it has a vehicle design system like in Striker but it just feels a bit off when in play.

Tomorrow’s War (Ambush Alley/Osprey Publishing)

Following the legal wars over Mongoose Traveller, I fully embraced the Cepheus Engine edition of Traveller. I especially enjoy The Clement Sector setting from John Watts at Independence Games. So far, Cepheus Engine has not published a mass combat set of rules, instead preferring to stay focused on the personal or vehicle combat scale of conflict. Further, no Cepheus Engine publisher has released a set of mass combat or “Battle Scale” rules like those found in the Classic Traveller Book 4: Mercenary or Mongoose Traveller Book 1: Mercenary.

What do I want? I want a good, clean set of large scale combat rules that use skills and vehicles created in Cepheus Engine. I want an updated Chadwick; maybe a relook at Striker with modern publishing sensibilities and approaches to game mechanics. Sure, some will say, “It’s an RPG, focus on the CHARACTERS!” Well, if you pay attention to what Mr. Chadwick told us in Striker several decades ago it will:

One important aspect in which Striker differs from previous miniatures rules is the role assigned to the player. In most games, a player simultaneously plays the role of every member of a military unit; no orders need to be given, and every man performs as the player likes. In Striker, realistic limitations have been put on the abilities of officers to command their units. Giving orders to subordinates is a time-consuming process; commanders will find it advisable to devise a simple plan and to give most orders in pre-battle briefings. Changes to this plan in the heat of action will be difficult except through on the spot leadership.

Striker: Rule Book 1 – Basic Rules, Introduction, p. 4

*To be clear, Last Battle: Twilight 2000 was designed by Tim Ryan but used Frank Chadwick’s First Battle system.

My #TravellerRPG #Wargame – Using @IndependenceGa6 The Clement Sector setting in High Guard

Ever heard of Eurisko? If you played the (now Classic) Traveller RPG back in the early 1980’s, and especially if you played with capital ships or fleets in Book 5: High Guard or Adventure 5: Trillion Credit Squadron, then you probably heard of it. Eurisko is a representational language written in the Lisp Programming Language that learns through heuristics. Think of it as an early form of AI. Eurisko was used to design the 1981 winner of the Traveller Trillion Credit Squadron National Tournament at the Origins Game Fair that year. In 1982 Eurisko won again. Threatened with the end of the tournament if he entered again, Dr. Lenet withdrew Eurisko from further competition.

I bring up this history because the Eurisko incident often colors many peoples perceptions of High Guard. Since High Guard could be ‘gamed’ by a computer, many decry it as ‘broken’ and not a worthy version of a fleet battle game for the Traveller universe. I disagree. I enjoy High Guard and the companion Adventure 5: Trillion Credit Squadron. Sure, it’s a highly abstracted view of space combat in the Traveller universe, but that very abstraction is what makes it attractive.

The Traveller Itch

Having not picked up a Traveller book in a while, I recently had an itch to dive back into the rules. One awesome aspect of the Traveller series that I really enjoy is all the mini-games possible. From Character Generation (yes, I’ve died in CharGen), to world-building, to building ships, the rules of Traveller, and now the modern successor Cepheus Engine, allow you to create a wide diversity of elements in a system that ensures it all works together.

The Clement Sector: Core Setting Book from Independence Games

One setting for Traveller I really enjoy is The Clement Sector from Independence Games. The Clement Sector is a ‘small ship universe’ where the limits of the “Zimm Drive” keep ships, at least those that are jump capable, under 5,000 Tons. With the Wendy’s Guide series of sourcebooks that detail out entire fleets, I wondered if The Clement Sector and High Guard could mix. So I experimented.

Anderson & Felix, Meet High Guard

Ships in The Clement Sector are constructed using the Anderson & Felix Guide to Naval Architecture. If you are a Traveller RPG historian, you will know that A&F is basically the modern day version of Book 2: Starships updated for Cepheus Engine. This means that A&F is not closely coupled to High Guard like the original Book 2: Starships or Adventure 5: Trillion Credit Squadron were. For my experiment this meant that in some places a little “interpretation” is needed to convert ships from the A&F stats to High Guard which uses the original Universal Ship Profile (USP). The USP was a series of numbers that takes much the details of a ship design and renders it into a single line alpha-numeric characters.

Powerplants, Energy Points, and Agility

In the original High Guard, ships were built with Powerplants that in turn produced Energy Points. As Book 5 stated, “Energy points are used for four purposes: powering weapons, shields, for maneuver drives (for agility), and for computers.” The key factor for High Guard was that ‘Agility’ rating derived by taking energy points not used for computers or weapons or shields and plugging them into the formula A=E/0.01M (where E= Unused Energy Points and M= Mass of the Ship).

Agility is one of the most abstracted elements of the High Guard design in a design that is full of abstractions. Book 5 defines it as follows:

Agility is the ability of a ship to make violent maneuvers and take evasive action while engaging hostile targets. A ship’s agility rating may never exceed its maneuver drive rating.

Book 5: High Guard (2nd Edition 1980), p. 28

It’s clear that Agility is distinctly different that a ship’s maneuver rating. Seeing how it is based on “excess power” it (at least to me) symbolizes how much more you can throw your ship around beyond the usual M-Drive abilities.

Which is the heart of the problem. You see, in A&F the energy requirements in a ship design are actually more simplified than in High Guard. The concept of Energy Points is simply not used in A&F. Unlike High Guard, in A&F computers and turret weapons (presumably this includes barbettes too) are “Unlimited by Power” per the Capital Ship Armament Table on A&F p. 29. This same table specifies how many Bay Weapons per 1000 tons can be carried (based on the Power Plant Rating) as well as if a Spinal Weapon or how many Screens are allowed.

Without a direct translation between High Guard Energy Points and the Armament Power Table in A&F it is impossible to derive an Agility rating. So I asked myself, “How is Agility used in combat, and what would the difference be if it was not used?”

When resolving combat in High Guard, one nice part of the design is that there are actually very few modifiers to worry about (or remember). When making the initial To Hit roll, there really are only three modifiers:

  • + relative computer size
  • – target agility rating
  • + target size modifier

I was worried that, with this few modifiers to start with, simply removing the “- target agility rating” risked skewing the result. Wanting to preserve the intent of the design, I fell back on a lazy solution; change the modifier to “Minus Firers M-Drive Rating/Target M-Drive Rating (rounded down) IF RESULT IS POSITIVE – any NEGATIVE result becomes Target Agility= 0”.

For instance, say a Rattlesnake Attack Craft with M-Drive=5 from Ships of The Clement Sector 7 has jumped a Rucker-class Merchant from Ships of the Clement Sector 16 converted into the System Security/Escort Armament variant with M-Drive=2. When the Rattlesnake attacks the relative drive rating (5:2) computes to a factor of 2, giving the Rattlesnake a -2 DM on its To Hit rolls (better relative “agility”). On the other hand, when the Rucker shoots at the Rattlesnake the relative rating is 2:5 giving a result of -2 which becomes 0 DM modifier.

Armor

The second area that needed interpretation was armor. In Cepheus Engine ship combat, the armor rating directly reduces the number of hits. So when a ship is attacked with a salvo of three Basic Missiles (Damage = 1d6 each) launched by a Triple Turret, if the target ship has Armor = 8 then the first eight hits are offset. When designing a ship using A&F, the default armor for higher Tech Levels is Crystaliron which can be added to ships in increments of 5% of the ships tonnage. The maximum armor factor is the Tech Level of the design or 12, whichever is less.

In High Guard, the type of armor is unspecified. Given the rather large armor factors in A&F designs, I wondered it I was over-armoring the designs. A close look at the High Guard Hull Armor formula gave me my solution. The Hull Armor formula tells the designer the percentage of the ship required for that armor factor. At TL 11 (standard in The Clement Sector) the formula is 3+3a where a is the desired armor factor. Using a little backwards math I quickly discovered that the Armor Factor given in a A&F design was using too much space, but if I used the number of “layers”– those 5% elements- the number worked. So a Moltke-class cruiser (Ships of the Clement Sector 3) which is listed as “Crystaliron x2 / 8 points” when converted to High Guard has Armor=2. Unlike Cepheus Engine where armor directly reduces the number of hits, in High Guard armor is a +DM when rolling on the Ship Damage tables. Using this backwards derived formula, armor in The Clement Sector ranges from +1 to +4; a much more reasonable range of modifiers than the +4 to +16(!) using the A&F factors.

Torpedoes

Torpedoes are described in A&F as, “…true ship killers…heavy 2.5dT anti-ship missiles….” In A&F missiles inflict damage from 1d6 (Basic Missile) to 3d6 + Crew Hit (Nuclear Missiles). Comparatively, a Basic Torpedo will inflict 4d6 hits, a Nuclear Torpedo causes 6d6 hits, and the heaviest Bomb Pumped Torpedo scores 7d6 damage.

Assuming the High Guard missiles are nuclear, I was able to come up with approximated damage for each USP factor. I then reworked the table using the higher damage potential of the Torpedo. In the end it worked out that I could use the existing High Guard Turret Weapons table and, using the missile column, simply add +1 USP factor to get the Torpedo USP.

Rail Guns

Rail Guns were another weapon found in A&F but not in High Guard. Using the same approach as I did for Torpedoes, I basically figured out that the 50-ton Rail Gun Bay had nearly the same hitting power of a 50-ton Missile Bay, so I used the same USP factor. The primary difference is in combat; the Short range of the Rail Gun earned it a restriction of being unable to fire when at Long Range in High Guard. At Short Range, the Rail Gun earned a +2 DM To Hit but used the Attacking Meson Gun vs Configuration table. This generally means that, absent those other To Hit modifiers, a Rail Gun battery needs to roll an 8+ on 2d6 to hit a Needle/Wedge configuration, or a 6+ to hit a Standard configuration, or an 11+ to hit a Dispersed configuration ship. Sort makes sense, right?

Missile Stocks

In High Guard the number of missiles one had aboard a ship was not a consideration. I always found this interesting given that combat in High Guard usually depicted larger, longer fleet engagements. The ship descriptions in the Ships of the Clement Sector includes the number of missiles on hand. Usually it is a mix of Basic, Nuclear, and Smart Missiles. As any logistics planner will tell you, you can’t face the enemy with an empty quiver of bows! I toyed around with the idea of breaking the load out into the number of turns each missile type could be fired (assuming one round of firing in a turn) but ultimately decided that breaking it out by missile is just too granular for the High Guard system of abstractions. Instead I took the number of missiles available and divided it by how many can be fired in one ‘volley’. This is the number of ‘volleys’ the ship gets before the stores are depleted. Probably only useful in a campaign game or as a special rule like an SDB on patrol too long facing a pirate with a near-depleted stores of missile– make every shot count!

Into Battle?

So, now that I’ve done my homework, will I actually play a game of High Guard in The Clement Sector? Maybe. Like I said before, The Clement Sector is a ‘small ship universe’ meaning space battles are usually smaller affairs with few ships. High Guard is better at resolving larger fleet battles with larger combatants. In the The Hub Federation Ground Forces sourcebook, Appendix 1, some details of the “Battle of Beol” are provided. There may be enough there to make a fleet battle scenario.

Now that I think of it, the Battle of Beol also includes a ground campaign. Maybe I need to look at a Striker (GDW, 1980) campaign next?

Hmmm….


Feature image courtesy roleplayrescue.com

A Tiny Mayday -or- My #Boardgame Weekend Taking on the Galaxy in Tiny Epic Galaxies (@Gamelyn_Games, 2015) and Traveller: The Customizable Card Game (@TravellerCCG, 2017)

This weekends gaming selection at the RockyMountainNavy home was out of this world as two galactic titles landed on the gaming table. As far out as the game subjects were, they both did their job of making home an enjoyable place to be.

Tiny Epic Galaxies (Courtesy Gamelyn Games)

The RockyMountainNavy Boys wanted to play our traditional Saturday night boardgame but asked for something a bit shorter. So Tiny Epic Galaxies (Gamelyn Games, 2015) landed on the table. We had not played this game in nearly a year TWO YEARS (!) so it took a round to relearn the rules. That’s didn’t stop the RMN Boys; they both ended the game on the same turn with the needed 21 points. It fell to RMN Jr’s Secret Mission – Trader to give him two bonus points and the win. Awesome first play of 2020!

Traveller: The Customizable Card Game (Photo by RMN)

Afterwards, I pulled out my recently acquired Traveller: The Customizable Card Game Two-Player Starter Set (Horizon Games, 2017) and turned the rest of the evening into a learning session for myself. Generally speaking, over the decades I have stayed away from the collectible or living or customizable card genre of hobby gaming. Long ago the RMN Boys collected Pokemon cards, and RMN T still collects Magic: The Gathering cards, but we don’t play the games. So for myself, learning how to play a card game like Traveller: CCG is a whole new challenge.

Traveller: CCG also comes with a solo play mode. After stepping thru the rule book I set up a solo game and played it out. I took the classic Beowulf Free Trader and tried to make my way in the galaxy. The first contract I took, Bulk Hauling, ended up with a Buccaneer hazard attached. The call-back to the original Little Black Books of the Traveller RPG that I first got during Christmas 1979 with the iconic, “Mayday. Mayday” on the cover of the boxes set made me so giddy with joy I actually giggled out loud.

The original Traveller RPG Little Black Books box

I ended my first game of Traveller: CCG bankrupt (i.e. I lost), but gained much gameplay experience. Most importantly, I immediately wanted to play again.

Learning game…out in the black and in the red (Photo by RMN)

Much to my surprise, the Traveller: CCG feels incredibly thematic. I was just a little tramp freighter trying to make my way in the big galaxy, reaching for a job here and there, always living on the edge of losing it all. It was fun. I want to play it again. I want to get the expansion sets (I don’t think I’ll go for the play mats but instead use my Star Wars: X-Wing play mat).

My Star Wars: X-Wing Play Mat – At 3’x3′ it’s perfect for playing Traveller: CCG solo or with a second player (Photo by RMN)

It seems you can teach an old Grognard new tricks.


Feature image courtesy pexels

RPG Thursday – Soaring into battle with #TravellerRPG

“What’s that?”

Strom turned his attention from his mapping instruments and looked over at the panels that Ga’de, his co-pilot and fellow Scout, was now studying intently. The optical array had picked up something and flashed an alert. Whatever it was, it was unidentified for the moment.

“It’s small and cool,” Ga’de reported. “Maybe 5 dTons in size. Why is it in a retrograde orbit?”

“Yeah,” Strom thought out loud. “It’s coming straight at us.”

Ga’de glanced away from his instruments and over at Strom. His brow was furrowed. “They’re attacking?”

Strom was thinking out loud. “Since we got here, the western continent has not liked our presence. They’re the most vocal about the ‘danger’ of ‘outer space aliens’. They’ve made announcements that they are willing to fight to keep us out.”

Ga’de harrumphed. “What imbeciles. They just can’t accept that they’re not alone in the universe and somebody else made it to the stars before them. We offer them technology and they reject us because we threaten their ”culture’. Why can’t they see that we offer them the future?”

Inwardly, Strom agreed but talking about it was not the solution right now. “Can we get any sort of ID on it?” he asked.

Ga’de turned back at his instruments. “Hard to tell, optics seem to show something winged. Do they have manned small craft?”

Courtesy astronautic.com

On a small screen next to his station Strom consulted the few files they had on the planet so far. In a previous expedition they had raided what passed for a library on this planet and acquired an “Encyclopedia” but it was a physical paper document. It had taken a while to scan it into the computer and the cross-references were poor. Imagine that; a planet so backwards they didn’t even have the SmartNet yet!

“Yes, they are working on a crewed launch capability using capsules. But the only thing shown here is crude ballistic missiles, nothing more than TL5 at the best. Wings…that’s different,” Strom trailed off.

“Do we maneuver?” There was a nervous edge in Ga’de’s voice.

Strom considered. “We’re higher tech. And we have to finish this mapping mission. Besides, we can’t let them think they can push us around.” He paused for just a moment. “No. We maintain course.”

Optics continued tracking the black winged object. A bit nervous now, Strom nudged the thrusters a bit to slightly change their vector; a few moments later the black winged object adjusted too.

“That’s not right,” Strom thought. “It means it’s guided…by a hu-man?

The range was closing rapidly. The approach looked like it was going to be close.

Somewhat belatedly, Strom stirred into action. “Ga’de, get to the turret, fast.”

Ga’de got up and raced from the control cabin. The winged craft kept closing.

Strom watched his panel as the turret indicator light came on. His heart sank when Gade made his first call.

“Damn systems rebooting! Something about an urgent update!”

Strom strapped himself in as he started throwing switches. “Strap in, we’re gonna burn!”

Time seemed to slow to a crawl. Strom saw on the optics the winged beast release a smaller object that flared briefly and accelerated quickly towards his saucer. He saw out of the corner of his eye a warning from the radiation detector. He heard Ga’de cursing the Gods in the turret.

These Stars Are Ours, Stellagama Publishing, 2017

He reoriented the ship and punched the M-Drive. As Strom was slammed back in his chair by the acceleration he thought about his mission. The Quorum had sent them here to expand the frontiers of their small empire. Surely, this lesser-developed planet, just at the cusp of spaceflight, would welcome them. After all, they were a highly compatible species as secretive missions before had shown. Some of the specimens captured were still alive and helping the Quorum even now. Sure, some had resisted, but they were the exception, right?

The small missile flared again but brightly this time. It changed course to intercept Strom’s saucer. Before he could manuever again the small object exploded with a blinding flash of light. As the expanding atomic fireball rapidly washed over his saucer, Strom thought that, surely, their superior technology would save them. Surely….



Deep inside a bunker buried under a mountain, the General watched intently as the stream of information from SIDS, the Space Intruder Detection System, reported the nuclear detonation in orbit above. The Eastern Pact would be upset by the large EMP event above their continent, but setting them back while destroying the alien intruders was but a small price to pay for saving the planet.

The General watches (Courtesy Wargames)

The General glanced to his right at the two ‘Agents’ dressed in identical black suits. They kinda looked like that a-hole J. Edgar’s men, but something was not quite right. The older one had never smiled. The younger one kinda fidgeted until the older one glared at him then he too stood by emotionless. They didn’t even laugh at his spark plug joke. Shaking his head ever so slightly, the General swore under his breath that he would never understand why they wore sunglasses this deep inside the mountain.

Sighing, the General spoke up, “Control, take us to DEFCON 5. Ops, make sure all reports are are captured for Project Blue Book. Comms, get me a channel.”

“Ground Control to Major Tom….”

Courtesy collectorsweekly.com

This mini Traveller RPG adventure was inspired by a tweet by @pilliarscreatio showing a Boeing Dyna-Soar hot-staging into orbit.

Key materials referenced include:

#Coronapocalypse #RPG – A different #TravellerRPG future with @IndependenceGa6 #TheClementSector Earth sourcebooks

IN THE PAST FEW WEEKS, I PLAYED SEVERAL Traveller RPG-related wargames. Invasion: Earth (GDW, 1982) and Squadron Strike: Traveller (Ad Astra Games, 2018) are based on the Third Imperium setting. However, my modern “preferred” setting for my Traveller RPG is The Clement Sector from Independence Games (formerly Gypsy Knights Games) using their modified version of the Cepheus Engine ruleset.

A major reason I like The Clement Sector is that it is in the future, but not so far in the future (like the 56th Century of the Third Imperium) that I cannot relate. Here is how Independence Games describes the core setting:

In 2210, scientists discovered a wormhole allowing travel to the opposite side of the Milky Way galaxy.  Once across, exploration teams discovered worlds far more suited to human habitation than those in star systems nearer to Earth.  Were they terraformed by some unknown race?  Are they just a coincidence in the vast diversity of the universe?

Over the ensuing years humans left Earth and began to colonize these worlds.  Nation-backed colonies.  Corporate colonies.  People who simply no longer felt compelled to remain on Earth.  The best and brightest.

In 2331, the unthinkable happened.  The wormhole collapsed leaving those in Clement Sector cut off from Earth.  Now these new worlds and new civilizations must stand on their own.

The year is 2342.  Adventure awaits!

Originally, The Clement Sector focused in ‘the other side’ of the wormhole and the regions that grew up around there. I really like the setting because it has everything one may prefer; a subsector that is very Space Opera, another that is Space Western. I also absolutely enjoy how Independence Games makes their sourcebooks; a combination of wide topics with ‘seeds’ of adventure thrown in. They paint the broad strokes of the setting but leave plenty of space for you, the GM or players, to fill in. In an era when so many folks play IP-derived settings then complain of being ‘constrained’ by canon, The Clement Sector is a refreshing dose of freedom. Which is why I approached a few of the most recent releases with a bit of trepidation.

Earth Sector: A Clement Sector Setting

Earth_Sector_Cover_540xI actually talked about this sourcebook back in February 2020 and was not so keen on it then. Truth be told it has grown on me in the short time since. Earth Sector: A Clement Sector Setting focuses on the Earth Sector but AFTER the Conduit Collapse. I was concerned about this ‘alternate-future’ look and although there is certainly a good deal of ‘history’ in the product I am very pleased on the post-Collapse focus. Indeed, that is what saves the entire product for me – it is as much more of a look forward into the ‘future’ than a tie to the ‘past.’

A major reason Earth Sector has grown on me is another one of those Traveller games-within-games. As the ad copy for Earth Sector states:

Using the relationship matrix developed in Balancing Act: Interstellar Relations in Clement Sector, Earth Sector contains detailed reports on which nation is doing well, how much they are raking in from their colonies, and upon which nation they may yet declare war.

CTadv5Long ago, Classic Traveller Adventure 5: Trillion Credit Squadron included rules for determining budgets for a world. The idea was players could design and build fleets and fight with them. Over the years, this world budget concept has often cropped up in the game. Independence Games added their take on the concept with Balancing Act: Interstellar Relations in the Clement Sector:

It also includes a game within a game called “The Balancing Act”. This game will allow you to take on the role of a head of state in Clement Sector and go up against other leaders as you attempt to push your world ahead of your competition. These rules can easily be used in other settings and games where one might wish to become a leader of a world.

What I really like about Balancing Act is that it is not solely focused on the military (although that certainly makes up a large part of the ‘balance’). Although most RPGs are inherently very personal and focused on a individuals in a small group, as a GM I can use Balancing Act to ‘world-build’ the setting.

Subsector Sourcebook: Earth

EarthSectorFrontPromoCover_1024x1024@2xComplementing Earth Sector is Subsector Sourcebook: Earth. This product looks beyond the Earth and to the whole subsector. Again, the post-Collapse focus is what makes this product; there is enough history to broadly explain how the various locales came to be and how they are dealing with the post-Collapse situation. In addition to all the ‘details’ about the planets, this subsector book also includes the Balancing Act data meaning it is ready-set for GMs and players to start their own world-building adventure game.

Which brings me to the last new product this week…

Tim’s Guide to the Ground Forces of the Hub Subsector

Tims_Hub_Cover_Final_1024x1024@2x.pngIndependence Games already publishes their Wendy’s Guides for space navies in The Clement Sector. Tim’s Guide to the Ground Forces of the Hub Sector takes that same concept an applies it to non-space forces (ground, aerospace, naval) and organizations. Unlike the other products I talked about above, this first Tim’s Guide goes back to ‘other side’ of The Clement Sector and focuses on the Hub Subsector.

Like the Wendy’s Guides before, each planet has their non-space forces laid out. Planetary factors related to The Balancing Act are also included. As I so often say about Independence Games’ products, the depth of detail is just right. For example, one entry may tell you that the planet has a Tank Company equipped with FA-40 tanks, but they don’t tell you the details on that tank. It might be in one of the vehicle guides or, better yet, you can use the Cepheus Engine Vehicle Design System to build your own. [I guess it is just a matter of time until Independence Games publishes their own The Clement Sector-tailored vehicle design system too.]

The other part of this book that I appreciate is the fully detailed “Hub Federation’s Yorck-class Battlecruiser, a seafaring vessel capable of engaging forces both on the oceans and in close orbit.” The Traveller grognard in me wants to take this ship and place in a Harpoon 4 (Admiralty Trilogy Games) naval miniatures wargame scenario and see how it goes.

So there you have it; three new The Clement Sector books for YOUR game. That’s probably the most under appreciated part of Independence Games. Unlike so many other settings, The Clement Sector empowers the players and GM. There is lots of material to chose from, and many adventures to be created.

#Coronapocalypse #TravellerRPG #Wargame – Math lessons with Squadron Strike: Traveller (@AdAstraGames, 2018)

I HAVE BEEN A TRAVELLER RPG PLAYER SINCE 1979 when I got my Classic Traveller Little Black Books set. Over the years I also played many wargames based on the Traveller setting. Of those, I always had a soft spot for tactical starship combat. This week my #coronapocalypse wargame was Squadron Strike: Traveller (Ad Astra Games, 2018). What sets Squadron Strike: Traveller (SST) apart is its fully 3D model which uses Newtonian movement in space. Be warned – the back of the box rates the game as Moderate complexity and notes, “Players need to do addition and subtraction.” The last time I played SST was January 2019. At that time I was working my way through the tutorial booklet and was not past the 2D scenarios. Well, this weekend I worked my way through all four scenarios of the Tutorial and discovered SST is not for the faint of heart; there is a steep learning curve that will challenge (and burnout) your brain cells. You WILL need to do more than just addition and subtraction! However, if you persevere the payoff is a very good, playable-albeit-complex model of ship-to-ship combat in the Traveller RPG universe.

The Tutorial book in SST uses a programmed learning approach. If you are a player that just wants to read the rulebook and play you will fail. The 3D concepts used in SST almost defy writing – they really must be experienced in a structured manner to be understood. As designer Ken Burnside writes in the sidebar Don’t Just Read, Play:

The first tutorial is highly scripted – you pretty much follow along and mark boxes. Get in the habit of playing the tutorials; the verbiage is intended to be read while you’re doing things. If you just read the tutorial, there’s a non-zero chance you’ll find it tedious and overwhelming. If you play the tutorial as you read it, you’ll see how it all the pieces and parts fit together.

Tutorial 1 introduces the Sequence of Play and the 2D version of the Altitude Vector Information Display – AVID. The AVID is the heart of SST and to understand the game one has to master how to use the AVID. The tutorial walks the players though the 2D version of the Ship System Display, the SSD, as well as basic 2D movement and combat. At the end of Tutorial 1 the player is familiar with the basics of Plotting, Movement, and Combat.

avid+example
AVID. This ship starts facing hexsides B/C and is rolled 30 degrees right. The plot calls for pivoting 60 degrees to the right and pitching the nose up 30 degrees. Easy to read, yes? (Courtesy Ad Astra Games)

Tutorial 2 is another 2D scenario, but this time new concepts like Sandcasters (defenses in the Traveller universe), ECM (used to show technological advantages), Profile Numbers (harder to hit when a narrow profile is presented), missile combat and defense, Crew Rate (just how good are your redshirts?), Damage Control (Where’s Scotty?), and different damage allocation. The concept of Action Points (a combination of power allocation and command and control) is also introduced. For real Traveller RPG fans, there is a sidebar note about integrating character RPG skills into a portion of the game here.

At the end of Tutorial 2, Squadron Strike: Traveller looks to be a moderately-more-complex version of Mayday (GDW, 1978) or Power Projection: Fleet (BITS: 2003). Tutorial 3 changes all that with the introduction of 3D movement.

The first concept that one has to wrap their head around is the 3D AVID. One has to take the 2D graphic shown on the Movement Card (shown above) and imagine it as a sphere.

Avid+Ball
3D AVID imagined (Courtesy Ad Astra Games)

The tutorial makes it clear that there are a few skills are needed; skills that wargamers may not have:

There are three skills you’ll need to master with the the AVID. Unless you’ve been an astronomer, pilot, or driven a submarine for a living, none of them match things you’ve done in gaming or in real life before. It will take some repetition before things “click” The first skill, which we’ll go into now, is orientation. We’ll cover the other two (shooting bearings and mapping them to firing arcs) in the Combat Phase.

If you cannot handle this you will make it no further in learning the game. To help your imagination visualization, the game uses Tilt Blocks to show your ship’s altitude and orientation on the mapboard.

Box+Mini+Roll+and+Pitch
Left – Ship facing A, no pitch or roll, altitude 0. Right – Ship facing A, pitched up 60 degrees, rolled right 30 degrees, altitude +2

weapon+bear+2
Target is visible in red box so Mounts S & U bear but Mount T does not (Courtesy Ad Astra Games)

If you have not given up yet (and you shouldn’t because the Tutorial steps you through everything – although you may need more than one pass to grok it all) you now need to Shoot Bearings to see which weapons bear and can fire. This again requires some imagination math because you have to figure out which window the enemy is in and then see what weapons bear and can fire. Fortunately, the tutorial steps you through the process and there are many helpful tables on the Reference Card.

As “complex” movement is, I really appreciate the “simplicity” of combat resolution. For each attack you ALWAYS roll 4x d10 (1x red, 2x black, and 1x blue). The red die is your Accuracy– roll Accuracy or greater to hit (very few die mods). The two black are “2d10-” which means you subtract the smaller from the larger for a difference which is additional Damage added to the Base Damage number. The blue die is the Hit Location. I really like this streamlined combat approach – roll one die pool and you immediately have hit, damage, and hit location!

The end result of all that math work is a VERY good game of Traveller. Ken Burnside writes of the differences between generic Squadron Strike and Squadron Strike: Traveller:

  • The Traveller universe, set 3,500 years in the future, uses Mode 2 (Newtonian) movement and doesn’t use tactical fuel
  • ECM is turned on, but ECCM is deliberately not used; only the Imperials have ECM in this product, and it shows a Traveller tech-level advantage
  • The Traveller setting uses sand, hull armor, and component armor as the primary defenses of warships
  • Sandcasters, which are “burst mode” shielding with a name change, throw sand in the path of incoming fire
  • In a break from normal Squadron Strike usage, but consistent with Traveller, the “meson” weapon trait makes the weapon vulnerable to meson screens, but lets the weapon ignore sand and the surface armor of the ship
  • Traveller uses two SuperScience Defenses: The meson screen works against weapons with the Meson trait….Nuclear dampers work against missiles.

After I got thru all four tutorials I had several ships and SSDs ready, so I just played around with the system. Once you learn the game it plays fast. The tutorial mentions The Hockey Puck Analogy which is very appropriate:

One of the best explanations of Squadron Strike tactics came from a player named Patrick Doyle. Momentum movement games are about where the hockey puck will be; not where it is now. Always keep an eye on both the target’s ship and how far out their EoT (End of Turn) tent is from their current location.

Squadron Strike: Traveller is a game that will require regular play to maintain proficiency. As tough as the game is to learn, once learned it plays pretty quickly. Fortunately, the game support small engagements as well as larger squadron-level battles. That said, Ship Book 1 has 15 different ships (although many have variants) and there are a few extra ships available online. Like most every Traveller RPG player, I like to design my own ships and I would like to put them into this game. There is supposedly a ship design spreadsheet available for registered users (so…where is that login?). I guess this is also a good place to mention that there is an AVID app available for web/Android/iOS devices. I looked at it but it was not immediately intuitive to me so I just kept plodding along (and learning) the manual way.

Given the abundance of extra time from the Coronapocalypse I think a few battles may be shortly in order!