Silent Death: Black Guard – The Ptolemean Wars Continue thumbnail

Silent Death: Black Guard – The Ptolemean Wars Continue

Silent Death: Black Guard – The Ptolemean Wars Continue Rulebook

Table of Contents

Table of Contents

Product Notes

Black Guard's starcraft displays are printed in the center of the booklet on separate sheets. To remove them, loosen the staples in the center of the book and remove the pages which contain the displays. Cut the separate displays apart down the fold line and reclose the staples.

2.0 A Renewed Offensive

The Ptolemean Province consists of 14 individual star systems containing a total of 6 habitable worlds, 21 mineral-rich resource worlds, and innumerable outposts, stations, archaeological sites and industrial centers. As detailed in the first Silent Death expansion, Overkill, Ptolemean space has been invaded by House Colos and Warbands from House Dneprodzerkutsk. The Colosians received an Imperial sanction for their assault.

Overkill detailed a good portion of the actions which occurred between the Ptolemean, Colosian, and Dneprodzerkutsk fleets for the better part of the first year of the war. The Dneprozerkutsk, due to infighting and stunning military defeats, have been reduced to bands of annoying raiders. The Colosians lost Imperial support when they were unable to quickly bring about the fall of House Ptolemus, but they have continued to fight regardless.

Colosian offensives dwindled after the midyear of Imp 475 while they frantically resupplied their forces from their home territory dozens of light years from the action in Ptolemean space. But now, in the waning of 475, the Colosians are ready to renew their offensive.

House Colos has decided on the strategy of going for Ptolemae, their foe's Homeworld in the Hathor star system. Their attacks continue to be launched from Ascension, a star system they conquered early in the war as detailed in Overkill.

2.1 Battle for Hathor

The Colosians made their first raid into the Hathor star system on Imp 475:019, a mere seventeen days after the opening of hostilities with House Ptolemus. That first raid, which was made to test the defender's strength, was followed by a series of others, each with increasing intensity. But, as Imperial support for the invasion waned, so too did the state of Colosian supply.

A massive resupply effort was mounted from the Colosian home province and as the end of Imp 475 approached, the Colosian invasion fleet was ready to mount another major effort against the Ptolemean home system — the attack, launched once again from Ascension, was dubbed "Operation Hurricane". It would be the most serious threat to House Ptolemus during the first year of the war.

2.2 Dneprodzerkutsk Incursions

As chronicled in Overkill, the Dneprodzerkutsk Warbands which invaded Ptolemean space spent themselves early in the conflict. As Ptolemean attention becomes focused on Hathor during the last part of the year, the Black Plague and Behemoth Warbands are taking the opportunity to muster their strength for future operations.

During the time period covered by Black Guard, the Dneprozerkutsk hold Progeny, White Star, Dios Provanis and Sekhem systems, though their grasp on Sekhem is tenuous at best. The warriors of the Plague and Behemoth are content to consolidate their gains and perform minor raids against Beta Kynon, Aneb-Het and Lebanstar.

2.3 Fighter and Gunboat Availability

The following published starcraft types are available to the various antagonists as Imp 476 approaches. Note that this listing includes some new starcraft which were brought on-line with the commencement of Operation Hurricane on Imp 475:320. These have been marked with an asterisk (*).

Fighter and Gunboat Availability Chart

PtolemusDneprodzerkutskColos
Betafortress *EppingDrakar
BlizzardNight HawkHell Bender
DartPharsii IIKosmos
Death WindRevengeLance Electra *
EppingSalamanderNight Hawk
GlaiveSorensen IIIPharsii II
Pit ViperSpirit RiderRevenge
Sentry *Thunder BirdSalamander
SeraphSeraph
Shryak ShuttleStar Raven
Thunder BirdTalon *
Teal Hawk

3.0 Ptolemean Fighter Units

Here are two of the several Hathor Guardian Fighter Wings which bore the brunt of the Colosian assault during Operation Hurricane. Squadron compositions are given for the units just before first contact with the enemy's renewed offensive.

Note: Use of the Pilot Luck stat is optional as per Section D.0 in Rules Annex #1 which appeared in Overkill.

3.1 Black Guard

1313th Hathor Guardian Wing, dubbed "Black Guard". Commanding Officer: Prince M'har Ubash.

During the grim opening days of the Ptolemean Wars, several House Ptolemus fighter formations were swallowed up by the onrushing Dneprodzerkutsk and Colosian invaders. Out of these, only a few stragglers survived, gradually working their way back to Ptolemean mustering centers like Hathor, Scarab and Aneb-Het. Here they were reformed into new units, re-equipped with the hardware at hand, and sent back into the fray.

This is the origin of the Hathor Guardian Wings, of which no fewer than twenty-five were formed from mid to late 475. Of these, Black Guard was to become the most notable. Formed from flight crews and maintenance personnel representing every settled world in the Ptolemean Province, the 1313th became the focus of a nationalist propaganda campaign: "The 1313th — Bad Luck for the Barbarous Invaders." and "Fliers of The Black Guard — Reaping a Harvest of Fools" became common rallying slogans for the beleaguered peoples of Ptolemae during Operation Hurricane.

Squadron Summary, as of Imp 475:320

Black Fin Squadron

  • Squadron Leader: Kalib Pazdari (Plt 8, Gnr 10, Luck 5)
  • Assets: 16 x Dart
  • Typical Pilot (Plt 5, Gnr 6)

Black Flag Squadron

  • Squadron Leader: Balai Ayaisnif (Plt 8, Gnr 8, Luck 1)
  • Assets: 12 x Death Wind
  • Typical Pilot (Plt 6, Gnr 7)
  • Typical Gunner (Gnr 6)

Black Foot Squadron

  • Squadron Leader: Heka Ayankh (Plt 9, Gnr 8, Luck 2)
  • Assets: 8 x Glaive, 4 x Seraph
  • Typical Pilot (Plt 5, Gnr 7)
  • Typical Gunner (Gnr 5)

Determined to keep their capital world from falling to the enemy, Black Guard's fliers fought well and contributed to the overall effort which eventually ground Operation Hurricane to a halt. As the new imperial year dawned, the strategic initiative passed to the Ptolemeans. Plans were drawn for liberating offensives and some of the Hathor Guardian Wings were redesignated. Such was the case for Black Guard, which became the 1313th Shock Fighter Wing.

3.2 Brothers of Enmity

1341st Hathor Guardian Wing, dubbed "Brothers of Enmity". Commanding Officer: Lyon Barry Arahsammat.

Like the other Hathor Guardian Wings, the 1341st was pulled together from shattered fighter groups. The Brothers of Enmity, as they decided to call themselves, were formed from flight crews that had experienced battle with each of the invading forces. There were Charioteers who had fought the Black Plague at Progeny, Swords of Destiny who battled Behemoth at Beta Kynon, and members of Great Zenith who escaped the debacle at Hexad III. The Brothers of Enmity were also drawn from such famous and infamous units as Set's Minions, Nemesis, and Right Retribution.

Anchoring their operations on their squadron of new Betafortress gunboats, the Brothers of Enmity generally achieved great success against Colosian fighter formations during Operation Hurricane. However, in the final battle for Ptolemae in the closing days of Imp 475, the Brothers became embroiled in the major fleet action over the province's capital world. There they were badly mauled, losing three quarters of their operational strength.

Squadron Summary, as of Imp 475:320

Disable Squadron

  • Squadron Leader: Fel Rimush (Plt 9, Gnr 6, Luck 1)
  • Assets: 8 x Blizzard, 8 x Dart
  • Typical Pilot (Plt 5, Gnr 5)

Disbar Squadron

  • Squadron Leader: Pulla Zakutu (Plt 6, Gnr 8, Luck 2)
  • Assets: 12 x Sentry
  • Typical Pilot (Plt 4, Gnr 5)
  • Typical Gunner (Gnr 6)

Discord Squadron

  • Squadron Leader: Mim Karaindash (Plt 7, Gnr 7)
  • Assets: 6 x Betafortress
  • Typical Pilot (Plt 6, Gnr 5)
  • Typical Gunner (Gnr 7)

With the end of the threat to Hathor, the 1341st is withdrawn from active duty for an extensive reformation. However, the Brothers of Enmity see action again later in Imp 476 starting with the liberation effort at Ptol 27, the Sekhem system.

4.0 Colosian Fighter Units

Here are two of the many Colosian Carrier Wings which took part in Operation Hurricane.

4.1 Gale Force

135th Colosian Carrier Wing, dubbed "Gale Force". Commanding Officer: Kristian Sclater.

As the preparations for Operation Hurricane were undertaken, several Carrier Wings of fighters were formed and assigned to newly-arrived transport vessels. Of these, the 135th was a prime example. Built upon a core of veteran pilots, this wing was expected to help spearhead the assault into the Hathor system. Most had already been fighting in this foreign province for the better part of a year and were ready to put an end to it.

In keeping with the theme of Operation Hurricane, many of these new Carrier Wings took on complementary names; hence the title Gale Force. Monsoon, described below, is another example.

Squadron Summary, as of Imp 475:320

Red Squadron

  • Squadron Leader: Gregor Narleski (Plt 10, Gnr 10, Luck 7)
  • Assets: 12 x Talon
  • Typical Pilot (Plt 6, Gnr 6)

Green Squadron

  • Squadron Leader: Alexis Hoskin (Plt 8, Gnr 7, Luck 2)
  • Assets: 10 x Talon, 2 x Kosmos
  • Typical Pilot (Plt 6, Gnr 7)

Blue Squadron

  • Squadron Leader: Karl Hrebik (Plt 6, Gnr 7)
  • Assets: 8 x Night Hawk, 4 x Teal Hawk
  • Typical Pilot (Plt 4, Gnr 4)
  • Typical Gunner (Gnr 5)

Violet Squadron

  • Squadron Leader: Achmad Shauki (Plt 6, Gnr 4)
  • Assets: 8 x Star Raven
  • Typical Pilot (Plt 5, Gnr 5)
  • Typical Gunner (Gnr 6)

Gale Force was critically short of manpower and hardware by the end of Operation Hurricane. At the beginning of Imp 476 it withdraws from Hathor with the bulk of the surviving Colosian task force elements.

4.2 Monsoon

197th Colosian Carrier Wing, dubbed "Monsoon". Commanding Officer: Steffon Vegodsky.

From the unit's inception, Monsoon pilots have had the reputation of being a rowdy band of hot shots. During Operation Hurricane, flights of these starfighters would often engage opponents even when severely outnumbered. Their brashness and offensive nature earned them the respect of their Ptolemean foes, but that wasn't enough to bring success to the overall Colosian effort.

Marshal Beznikov, Commander In Chief of Operation Hurricane, commented late in the campaign that if all of his fighter forces had the heart of Monsoon, the tide of battle might have been turned.

Squadron Summary, as of Imp 475:320

Tropic of Algol Squadron

  • Squadron Leader: Taylor Tedeschi (Plt 9, Gnr 9, Luck 8)
  • Assets: 16 x Lance Electra
  • Typical Pilot (Plt 7, Gnr 5, Luck 7)
  • Typical Gunner (Gnr 5)

Tropic of Belagris Squadron

  • Squadron Leader: Aran Vaclavicek (Plt 8, Gnr 3)
  • Assets: 8 x Pharsii II, 2 x Revenge, 4 x Star Raven
  • Typical Pilot (Plt 5, Gnr 4)
  • Typical Gunner (Gnr 7)

With their carrier vessel destroyed in the last battle of the campaign, Monsoon's surviving pilots and fighters evacuated the Hathor system on Gale Force's transport.

5.0 Scenarios

Here are four chronologically ordered scenarios. They cover several aspects of the fighter battles which took place during House Colos' Operation Hurricane, and concentrate on the fighter units described in Sections 3.0 and 4.0.

Note that these scenarios are representative vignettes of the more wide-sweeping battles which occurred during Operation Hurricane. Also, they only cover fighter-on-fighter combat. Often, these engagements were overshadowed by huge capital ship battles which were often underway at the same time. Nevertheless, fighter battles were decisive in their own right during Operation Hurricane.

Unless otherwise noted, each scenario uses the standard map set up shown in the Silent Death rules on page 18.

5.1 Operation Hurricane Begins

Colos vs Ptolemus

  • Date: Imp 475:320
  • Location: Approach to Ptolemae; Hathor system

Situation: With the renewed assault on Hathor by Colosian forces, the Ptolemean defenders were put to the test once again. Six previous Colosian efforts had failed to gain a toe-hold in the Hathor system, and the provincial capital, Ptolemae, escaped the repeated onslaughts relatively unscathed. With the unleashing of Operation Hurricane, the Colosians concentrated their efforts on the Ptolemean Homeworld in the hopes of delivering one final knock-out blow. This scenario depicts the over-running of a Ptolemean picket ship along one of the approaches to the capital world.

Forces

Ptolemean player. Picket Vessel from Discord Squadron, 1341st Hathor Guardian Wing: Set up first in Area E or F.

  • Betafortress A — Pilot (Plt 5, Gnr 2); Gunner A (Gnr 5); Gunner B (Gnr 3); Gunner C (Gnr 7); Gunner D (Gnr 7)

Colosian player. Advance Elements from Red and Violet Squadrons, 135th Colosian Carrier Wing: Set up second along Edge 3.

  • Talon A — Gregor Narleski (Plt 10, Gnr 10, Luck 7)
  • Talon B — Pilot (Plt 8, Gnr 7)
  • Talon C — Pilot (Plt 7, Gnr 6)
  • Talon D — Pilot (Plt 6, Gnr 9)
  • Talon E — Pilot (Plt 5, Gnr 5)
  • Star Raven A — Pilot (Plt 6, Gnr 7); Gunner A (Gnr 4); Gunner B (Gnr 6); Gunner C (Gnr 8)

Reinforcements

Ptolemean player. Reserve Element from Disbar Squadron, 1341st Hathor Guardian Wing: Enter on turn 2 along Edge 1.

  • Sentry A — Pilot (Plt 8, Gnr 5); Gunner A (Gnr 7); Gunner B (Gnr 6)
  • Sentry B — Pilot (Plt 5, Gnr 6); Gunner A (Gnr 8); Gunner B (Gnr 4)

Special Rules

  1. Colosian forces (only) are allowed to exit the map. They may do so only from Edge 1.

  2. Before the game begins, place 20 drifting asteroids as per Silent Death rule 10.5.

  3. This battle marked the operational debut of the Talon fighter. Previously untested in combat, the Talon was proving a little troublesome for its pilots to fly. To reflect this teething problem, the Ptolemean player picks one Talon at the beginning of every Movement Phase and rolls 3D6. The result is the maximum number of movement points that the chosen Talon may expend during that Movement Phase. If the roll equals or exceeds the selected Talon's current Drive number, there is no effect on the vessel's speed. The Ptolemean player is free to chose different Talons from turn to turn, or concentrate on the same one. Because this roll is affecting the Talon's actual Drive number, a low roll could bring the selected Talon into the firing parameters of "speed restricted" weapons, but only for the immediately following Cannon/Projector Fire Phase.

Victory Conditions

At the end of game turn 10 the scenario is over and the Colosian player tallies up victory points according to the following schedule:

  • +50 points — if the Betafortress is destroyed.
  • +10 points — for each Sentry destroyed.
  • +10 points — if the Star Raven exits the map with a Drive ≥6.
  • +3 points — for each Talon which exits the map with a Drive ≥8.
  • +1 point — for each Ptolemean crewman killed.
  • -50 points — if only two or fewer Colosian vessels exit the map.

Take the victory point total and compare it to the following outcomes:

PointsOutcome
80+ pointsDecisive Colosian victory
30-79 pointsMarginal Colosian victory
20-29 pointsDraw
10-19 pointsMarginal Ptolemean victory
0-9 pointsDecisive Ptolemean victory

Transcriber's note: the printed outcome bands are transcribed as printed.

Battlefield Report: This skirmish was the first contact between opposing fighter forces during Operation Hurricane. It was also the first time that the Talon SMAC Fighter was taken into combat. Unfortunately, the presence of the burgeoning Ptolemean Betafortress was an unfair test for the new Colosian fighters. Regardless of that, both sides fought well and proved the value of their latest war machines.

5.2 Playing Havoc

Colos vs Ptolemus

  • Date: Imp 475:320
  • Location: High orbit over Ptolemae; Hathor system

Situation: On the first day of Operation Hurricane, several Colosian fighter squadrons were given the task of knocking out Ptolemean communication satellites high over their opponent's Homeworld. In this scenario, members of the Black Guard fighter wing defend one such comm sat from an attack mounted by the 197th Colosian Carrier Wing (Monsoon).

Forces

Ptolemean player. Elements from Black Flag and Black Foot Squadrons, 1313th Hathor Guardian Wing: Set up first with one fighter in each of Areas D, E, F and G.

  • Glaive A — Pilot (Plt 8, Gnr 7); Gunner (Gnr 8)
  • Glaive B — Pilot (Plt 4, Gnr 4); Gunner (Gnr 6)
  • Death Wind A — Pilot (Plt 7, Gnr 8, Luck 1); Gunner (Gnr 6)
  • Death Wind B — Pilot (Plt 6, Gnr 5); Gunner (Gnr 5)

Colosian player. Flight from Tropic of Algol Squadron and Element from Tropic of Belagris Squadron, 197th Colosian Carrier Wing: Set up second along Edge 3.

  • Lance Electra A — Taylor Tedeschi (Plt 9, Gnr 9, Luck 4); Gunner (Gnr 8)
  • Lance Electra B — Pilot (Plt 7, Gnr 5); Gunner (Gnr 6)
  • Lance Electra C — Pilot (Plt 6, Gnr 6); Gunner (Gnr 5)
  • Lance Electra D — Pilot (Plt 3, Gnr 4); Gunner (Gnr 4)
  • Pharsii II A — Pilot (Plt 5, Gnr 4); Gunner A (Gnr 8); Gunner B (Gnr 7)
  • Pharsii II B — Pilot (Plt 4, Gnr 5); Gunner A (Gnr 7); Gunner B (Gnr 6)

Special Rules

  1. Prior to the set up of either side, the Ptolemean player places the Comm Sat counter (provided in Silent Death) anywhere in Area A. The Comm Sat will drift 3 hexes at the end of every game turn in direction 3 (refer to the map's compass rose). The Comm Sat may be attacked by the Colosian player. Its Defensive Value is 14, despite the fact that it effectively has Drive 0. It can jam tracking torps as vessels do except that it may attempt jamming against all tracking torps and succeeds on a 1D4 roll of 1-3 per torp. The Comm Sat carries no decoys. The Comm Sat may not dodge torps which make it to its hex and it carries no point-defense system. In addition, the Comm Sat may only be engaged by Cannon/Projector fire at a range of ≤15 hexes. The Comm Sat can take 20 points of damage before being destroyed. Starcraft may not perform a turn nor end a Movement Phase in the Comm Sat's hex.

  2. Two of the Ptolemean fighters are carrying an experimental electronic counter-measures (ECM) device. Before the game begins, the Ptolemean player secretly notes down the identities of the two equipped vessels for verification by the Colosian player at the end of the game. The ECM device has the following effects if the Ptolemean player declares that he is using it. The ECM device can scramble the tracking system of torps targeted on the equipped vessel on a 1D4 roll of 1-3. Let the Colosian player allocate all torp attacks during the Torp Launch Phase before declaring the use of the device. Roll for the use of the device against each targeted torp as desired. On the 1-3 roll, immediately remove the torp at the end of the Torp Launch Phase — it is jammed and does not even have the opportunity to start tracking. However, on a roll of a 4 the ECM device shorts-out, causing an internal fire which delivers 1-6 hits against the equipped vessel. After a short-out, the ECM device may no longer be used.

  3. The Colosian may exit his forces along Edge 3.

Victory Conditions

The scenario ends when no Colosian vessels or torps remain on the map. At that time the Colosian player tallies up victory points according to the following schedule:

  • +40 points — if the Comm Sat is destroyed.
  • +30 points — for each Glaive destroyed.
  • +20 points — for each Death Wind destroyed.
  • +1 point — for each torp still carried by an exited Colosian vessel.
  • -7 points — for each full or partial game turn that a Colosian vessel with a Drive >0 remained on the map after turn 2.
  • -15 points — for each Lance Electra destroyed.
  • -25 points — for each Pharsii II destroyed.

Take the victory point total and compare it to the following outcomes:

PointsOutcome
70+ pointsDecisive Colosian victory
40-69 pointsMarginal Colosian victory
30-39 pointsDraw
10-29 pointsMarginal Ptolemean victory
-(9) pointsDecisive Ptolemean victory

Transcriber's note: the printed outcome bands are transcribed as printed; the printed bands do not state a range for 0 to 9 points.

Battlefield Report: This dogfight marked the first use of Palomar-Lockheed's unconventional Lance Electra TMAC by Colosians against their Ptolemean foes.

5.3 Ultimate Sacrifice

Colos vs Ptolemus

  • Date: Imp 475:331
  • Location: Approach to Abydos, a moon of Hathor VII.

Situation: As Operation Hurricane grew into a fierce in-system battle, Hathor's other planets became hotly contested. Mendes, Cusae, Hathor VII and Hathor IX were the sites of cataclysmic battles involving large portions of both the Colosian and Ptolemean fleets. By 475:330, ten days into the campaign, Hathor IX had fallen to the invaders, and Ptolemean in-system communications were compromised. With their standard modes of communication down, the Ptolemean defenders of the Hathor system fell back on the practice of using hyper-velocity communication torpedoes to carry intra-system signals between main fleet units. On 475:331, one such Comm Torp malfunctioned while in transit. Unfortunately, it was carrying an important, top secret communique to the Ptolemean Hathor VII task force commander — it had to be recovered at all costs. With its hyper-drive out, the Comm Torp continued its flight to Abydos on its own limited maneuvering thrusters. As rapidly-deploying Colosian units closed in to capture the Comm Torp, fast fighters from the re-deployed Brothers of Enmity flew out to prevent just such an occurrence.

Forces

Ptolemean player. Two Flights from Disable Squadron, 1341st Hathor Guardian Wing: Set up first along Edge 1.

  • Dart A — Fel Rimush (Plt 9, Gnr 8, Luck 2)
  • Dart B — Pilot (Plt 5, Gnr 5)
  • Dart C — Pilot (Plt 4, Gnr 5)
  • Dart D — Pilot (Plt 2, Gnr 2)
  • Blizzard A — Pilot (Plt 6, Gnr 7, Luck 1)
  • Blizzard B — Pilot (Plt 5, Gnr 6)
  • Blizzard C — Pilot (Plt 2, Gnr 5)
  • Blizzard D — Pilot (Plt 1, Gnr 1)

Colosian player. Interception Flight from Tropic of Algol Squadron, 197th Colosian Carrier Wing: Set up second along Edge 2.

  • Lance Electra A — Pilot (Plt 7, Gnr 6, Luck 1); Gunner (Gnr 7)
  • Lance Electra B — Pilot (Plt 5, Gnr 5); Gunner (Gnr 6)
  • Lance Electra C — Pilot (Plt 5, Gnr 4, Luck 1); Gunner (Gnr 5)
  • Lance Electra D — Pilot (Plt 3, Gnr 1); Gunner (Gnr 5)

Reinforcements

Colosian player. Recovery Gunboat from Tropic of Belagris Squadron, 197th Colosian Carrier Wing: Enter on turn 3 along Edge 2 (see Special Rule 4).

  • Star Raven A — Pilot (Plt 8, Gnr 8); Gunner A (Gnr 6); Gunner B (Gnr 5); Gunner C (Gnr 8)

Ptolemean player. Recovery Gunboat from Discord Squadron, 1341st Hathor Guardian Wing: Enter on turn 8 along Edge 1 (see Special Rule 4).

  • Betafortress A — Pilot (Plt 7, Gnr 6); Gunner A (Gnr 6); Gunner B (Gnr 7); Gunner C (Gnr 9); Gunner D (Gnr 8)

Special Rules

  1. The standard map configuration is not used in this scenario. Instead, use the one indicated by the map diagram (Map Configuration for Ultimate Sacrifice) at the bottom of the next page. That diagram shows a Leading Map Section and a Trailing Map Section between Edge 1 and Edge 2, with the Comm Torp starting position in the center of the map area.

  2. The Ptolemean Comm Torp starts the scenario on the playing surface. To represent it, use a Mk50 torp counter of a color not used by either player. Place it in the very center of the map area, facing direction 1 (towards the Ptolemean forces). The Comm Torp moves automatically at the beginning of every Movement Phase. It moves 7 hexes per turn in direction 1. It will never veer from this path. The Comm Torp has a Defensive Value of 15, Plt 5, 0 Damage Reduction, and takes 2 hits.

  3. At the end of every even-numbered game turn (e.g., 2, 4, 6, etc.) pick up the Trailing Map Section and move it to the front end of the battle zone (i.e., abut it to "Edge 1", and it becomes the new Leading Map Section). Any vessels or torps which happen to be on the Trailing Map Section at the time of the move are considered to have dropped out of the battle. These units may not reenter the playing surface.

  4. Although map sections will be moved during the course of the scenario, the general configuration always stays the same, so Edges 1 and 2 always retain their relative positions.

  5. Neither player may undertake any form of attack against the Comm Torp until their opponent's gunboat comes within 10 hexes of it.

  6. The Comm Torp is captured by the first gunboat to end its movement in the Torp's hex. Immediately remove the Comm Torp from the map when this happens.

Victory Conditions

The game ends on the turn that the Comm Torp is captured or destroyed. After the last game turn is completed, both players total up the TPVs of enemy vessels destroyed and then adjust their totals according to the following schedule:

  • +150 points — player captured the Comm Torp
  • -100 points — player destroyed the Comm Torp

Subtract the Ptolemean's adjusted point total from the Colosian's. Compare the end result with the following outcomes:

PointsOutcome
200+ pointsDecisive Colosian victory
50-199 pointsMarginal Colosian victory
(-49)-49 pointsDraw
(-199)-(-50) pointsMarginal Ptolemean victory
-(-200) pointsDecisive Ptolemean victory

5.4 The Storm Breaks on Black Guard

Colos vs Ptolemus

  • Date: Imp 475:360
  • Location: High orbit over Ptolemae; Hathor system.

Situation: With Operation Hurricane running out of steam, the Colosians made one last ditch effort to crush the space units defending the provincial capital. A final main fleet engagement at Ptolemae was costly to both sides, and in the end, the Colosians were unable to send down their planetary assault vessels. As the capital ship battle waned, the remaining operational fighter units over the planet squared off for the final dogfight of Operation Hurricane. This scenario represents a small portion of the overall fighter battle which closed-out Imperial Year 475.

Forces

Ptolemean player. Mixed units from Black Guard, the 1313th Hathor Guardian Wing: Set up first anywhere on the map.

  • Glaive A — Pilot (Plt 7, Gnr 9); Gunner (Gnr 7)
  • Death Wind A — Pilot (Plt 6, Gnr 7); Gunner (Gnr 5)

Colosian player. Elements from Green Squadron, 135th Colosian Carrier Wing: Set up second along Edge 3.

  • Talon A — Alexis Hoskin (Plt 10, Gnr 7, Luck 1)
  • Talon B — Pilot (Plt 6, Gnr 7)
  • Kosmos A — Pilot (Plt 4, Gnr 7)
  • Kosmos B — Pilot (Plt 3, Gnr 6)

Reinforcements

Colosian player. Element from Blue Squadron, 135th Colosian Carrier Wing: Enter on turn 2 along Edge 3.

  • Teal Hawk A — Pilot (Plt 4, Gnr 4); Gunner (Gnr 5)
  • Teal Hawk B — Pilot (Plt 4, Gnr 1); Gunner (Gnr 4)

Ptolemean player. Flight from Black Fin Squadron, 1313th Hathor Guardian Wing: Enter on turn 3 along Edge 1.

  • Dart A — Kalib Pazdari (Plt 10, Gnr 10, Luck 6)
  • Dart B — Pilot (Plt 5, Gnr 6)
  • Dart C — Pilot (Plt 3, Gnr 3)

Special Rules

  1. This battle takes place among the hulks of capital ships destroyed during a previous battle. To represent the debris left behind by these huge vessels, players should take turns placing 8 two-hex groupings of asteroid counters. A two-hex debris grouping is 2 asteroid counters placed in adjacent hexes. Once on the map, these debris hexes should be treated as asteroid hexes for all purposes, except that they do not drift. Place all 8 debris groupings before setting up the vessels.

Victory Conditions

At the end of 12 game turns the scenario is over. Both players should total up the TPVs of enemy vessels destroyed. After doing so, the Ptolemean player's total is subtracted from the Colosian player's total. Compare the end result with the following outcomes:

PointsOutcome
100+ pointsDecisive Colosian victory
25-99 pointsMarginal Colosian victory
(-24)-24 pointsDraw
(-99)-(-25) pointsMarginal Ptolemean victory
-(-100) pointsDecisive Ptolemean victory

Battlefield Report: Colosian hopes of a victory over House Ptolemus within the first year of war were dashed with the failure of Operation Hurricane. Black Guard survived the campaign intact, and gave a good account of itself overall. The unit entered Imp 476 with a new operational designator: 1313th Shock Fighter Wing. There would be new battles against House Colos; battles in which Ptolemus' new Shock Fighter Wings would carry the fight to their enemy's conquered holdings.

6.0 Starcraft Inventory and Nomenclature

Here are the six new fighters and gunboats introduced in Black Guard. They are arranged in order of increasing tonnage. Each entry gives the printed stat lines; the commentary printed with each design is not reproduced.

Red Star Dynamics C.A.L. 220 Flash "Dart"

  • Crew: 1
  • Mass: 140 tons
  • Armor: Crystanium w/belt
  • Armaments: 2 x Mk10 Pulse Lasers; 1 x Mk10 Minigun (Ammo: 9,000 rounds)
  • Maneuvering Thrust: 0.194 km/s/s
  • Translight Capability: None
  • Atmospheric Capability: None

Bellicose Design Conglomerate T5a "Talon"

  • Crew: 1
  • Mass: 270 tons
  • Armor: Crystanium w/belt
  • Armaments: 1 x Mk10 Disruptorgun; 2 x Mk10 Pulse Lasers; 1 x Mk10 Torp Load
  • Maneuvering Thrust: 0.153 km/s/s
  • Translight Capability: None
  • Atmospheric Capability: None

Palomar-Lockheed CR5000 (export) "Lance Electra"

  • Crew: 2
  • Mass: 420 tons
  • Armor: Crysteel Alloy w/belt
  • Armaments: 2 x Protobolt Projectors (Ammo: 4 protobolts each); 1 x Mk10 Pulse Laser; 1 x Missile Launcher (Magazine: 18 missiles); 2 x Mk30 Torp Loads; 2 x Mk10 Torp Loads
  • Maneuvering Thrust: 0.12 km/s/s
  • Translight Capability: None
  • Atmospheric Capability: None

Pyramidis Shipyards 270 Model S/T "Sentry"

  • Crew: 3
  • Mass: 690 tons
  • Armor: Crystanium alloy belt
  • Armaments: 2 x Mk15 Blatguns; 8 x Mk10 Splatterguns
  • Maneuvering Thrust: 0.099 km/s/s
  • Translight Capability: None
  • Atmospheric Capability: None

Pyramidis Shipyards 340 Model B/C "Betafortress"

  • Crew: 5
  • Mass: 1500 tons
  • Armor: Rein. Crystanium
  • Armaments: 2 x Mk10 Plazguns; 4 x Mk15 Blatguns; 8 x Mk10 Splatterguns; 3 x Missile Launchers (Magazines: 20 missiles each); 5 x Mk50 Torp Loads; 10 x Mk10 Torp Loads
  • Maneuvering Thrust: 0.067 km/s/s
  • Translight Capability: 5 LY/day
  • Atmospheric Capability: None

Bellicose Design Conglomerate V27b "Star Raven"

  • Crew: 4
  • Mass: 1200 tons
  • Armor: Crysteel Double Hull
  • Armaments: 1 x Mk16 Disintegrator; 4 x Mk20 Meld Lasers; 11 x Mk10 Pulse Lasers; 1 x Missile Launcher (Magazine: 25 missiles); 2 x Mk50 Torp Loads; 4 x Mk20 Torp Loads
  • Maneuvering Thrust: 0.111 km/s/s
  • Translight Capability: None
  • Atmospheric Capability: None

Silent Death Rules Annex #2

The following rules appeared in the Silent Death Rules Annex #2 printed in Black Guard. They are transcribed in the order printed, with the Annex's own section numbers.

H.0 Standard Scenario Rules

The following rules for handling reinforcements and exiting starcraft appeared in Section 6.0 of Overkill. They are repeated here in a Silent Death Rules Annex to formalize their application. Unless stated otherwise by a scenario's special rules, these guidelines apply to all scenarios which specify the presence of reinforcements or allow the exiting of vessels from the playing surface.

H.1 Reinforcements

Some scenarios allow for reinforcements to enter the playing surface during the course of a game. In these cases it will be necessary for players to keep track of the game turns as they pass by. Use the Game Turn Record Track which appears along the bottom of many Starcraft Displays.

When reinforcements are called for on a particular turn, they are placed along their entry Edge (on an edge hex) as the first action of that turn. Such forces must be orientated so that they face a hexside out towards the playing surface (i.e., not parallel with the map edge or facing off board). Such entering reinforcements can then be targeted for missile and/or torp attacks in the first Phase of the entry game turn.

In addition, a good pilot entering with reinforcements can use his Plt skill to influence the initiative die roll on his turn of entry.

H.2 Exiting Starcraft

Some scenarios call for vessels to exit the playing surface. To do so costs 1 movement point from an edge hex in which the vessel is facing away from map hexes. A appropriate Sideslip maneuver (Silent Death Section 10.4) from an edge hex will also allow a starcraft to exit the map.

Unless specifically required by a scenario, no units may exit the playing surface. If a starcraft does so, it is considered destroyed with credit for the kill going to the last opposing crewmember to fire at it.

1.0 Silent Death in 3-D

Up until now, Silent Death has been restricted to the two-dimensional playing surface of the map. If players agree to use this rule, a third "altitude" dimension is added to the game.

What You Will Need

There are two recommended methods for indicating the altitude of a vessel in a 3-D Silent Death scenario.

First, and recommended, you can use a product called Grox-Blox™, produced by Dark Tower Enterprises (734 Roberts Rd, New Lenox, IL 60457). These are stacking, interlocking black hex blocks with a 1½" width, perfect for the Silent Death maps. A miniature can be placed on a stack of Grox-Blox to indicate its altitude.

Alternately, you can make a set of counters or chits individually marked with numbers from 0 to 5. Place a chit which corresponds to the vessel's altitude in the miniature's hex.

1.1 Altitude Levels

There are six altitude levels allowed by this rule. They are identified as 0, 1, 2, 3, 4, and 5, with 0 being the horizontal plane of the game map, and 5 being the highest horizontal plane above the map.

Each altitude level is best thought of as a superimposed hex grid above the base reference level (0) of the game map. A vessel can "climb" and/or "dive" during its movement, flying through and occupying various altitude levels.

A vessel may not "climb" above level 5 nor "dive" below level 0.

Setting Up for a 3-D Scenario

Players set up their starcraft at the beginning of a scenario as usual, but select their starting altitudes in secret. After all units have been set up, altitudes are revealed. Use the same procedure for reinforcements.

Effects of Altitude Levels on Range

One level of altitude difference between vessels equates to one hex of horizontal range. Therefore, when firing a weapon, horizontal range and vertical altitude difference will need to be added together to determine the effective range to a target.

Example: A target is 4 hexes away in the horizontal plane of the map. The firer is at altitude level 1, the target is at altitude level 4. Therefore, the target is 3 levels higher than the firer (4 - 1 = 3). The effective range from firer to target is 7 hexes (4 + 3 = 7).

Effects of Altitude Levels on Firing Arcs

A target may not have an altitude difference greater than its horizontal range from the firer. If this is the case, the target may not be hit. (Exception: Torpedoes, and weapon systems with 360° firing arcs can be discharged at a target regardless of altitude difference and horizontal range.)

Example 1: A Pit Viper wishes to fire its Pulse Laser at a Kosmos. The Pit Viper is at level 5 while the Kosmos is at level 2. The altitude difference is 3 (5 - 2 = 3). The horizontal range to the Kosmos is only 2 hexes. The range to the Kosmos is 5 (2 + 3 = 5), but the altitude difference (3) is greater than the horizontal distance (2). Therefore, the Kosmos is out of the Pit Viper's firing arc and may not be attacked. Essentially, the Kosmos is flying under the Pit Viper's firing envelope and can not be hit.

Example 2: If instead of the Pit Viper, a Shryak Shuttle was attacking the Kosmos in the previous example, the shuttle's 360° quad Pulse Lasers would be able to attack since 360° weapons are not restricted by altitude level difference.

Effects of Altitude Levels on Movement

Changing the altitude level of a vessel ("climbing" or "diving") can only be done in conjunction with a straight, forward move of at least one hex.

  • It costs 3 movement points for a fighter or torpedo to move forward one hex and either climb or dive one altitude level.
  • It costs 4 movement points for a gunboat to move forward one hex and either climb or dive one altitude level.

Turning maneuvers must be performed and paid for separately from any altitude changes during a move.

Changing altitude without moving forward is not allowed.

It is the responsibility of the moving player to make sure that the current altitude level of his vessel is clearly displayed to all other players. When moving, a player should call out the number of movement points he is expending in each hex, and the altitude level he occupies if there is a change.

Drift (as per Silent Death Section 10.2) occurs normally along the altitude level occupied at the beginning of the Movement Phase.

1.2 Depicting the Altitude Level Occupied

Players should quickly be able to tell which altitude level any vessel occupies on the game map.

If Using Grox-Blox: The number of Grox-Blox hex blocks below a miniature indicate that vessel's altitude level. Therefore, if a miniature's base is on the map surface, it is at altitude level 0. If the miniature has three Grox-Blox hex blocks placed beneath it, the vessel is at altitude level 3. The number of Grox-Blox hex blocks beneath a miniature should always represent a vessel's current altitude.

If Using Altitude Markers: If players have made a set of counters or chits with altitude levels written on them, then merely keep a marker with the appropriate number in a miniature's hex at all times.

Alternatively, in lieu of altitude markers, players may keep a small D6 in a vessel's hex. The face-up number on the D6 would indicate the altitude level of the starcraft. Remove the die when occupying level 0.

1.3 Restrictions on Occupying Hexes

The restrictions on occupying hexes as stated in the standard game rules are maintained.

Even though starcraft may now occupy one of six altitude levels in any hex, the restriction of allowing only one starcraft per hex at the end of movement is still in effect. So is the rule which prohibits turns being made in a hex occupied by another vessel. See rule 5.2 on page 10 of Silent Death. Therefore, it will not be possible to have two or more starcraft in a single hex occupying different altitude levels at the end of a Movement Phase.

Asteroids: When using asteroids in a 3-D game, randomize the altitude level of each one placed by rolling 1D6-1. This will give you a result between 0 and 5. Asteroids will maintain the same altitude level while drifting.

Asteroids block cannon and projector fire through their hex only if the firer and target occupy the same altitude level as the asteroid.

X.0 Silent Death Optional Rules

Here are some other optional rules which you can add to those first presented in the Silent Death rules and Overkill.

X.4 Point-Defense Weapon Systems vs Missiles

Ever feel completely helpless when your opponent makes three consecutive missile lock-ons? All those missiles fired will attack at the end of the current turn and there's not a single thing you can do about it. Until now.

This optional rule allows for the use of a vessel's point-defense anti-torp munition system against missile salvos, provided that the point-defense system was not used against a torp attacking previously in the game turn. This would, of course, mean that the point-defense system would be used during the Missile Results Phase instead of the Torp Results Phase as would usually be the case.

Mechanics: Each salvo of missiles from an individual launcher is treated as a torp for purposes of the maximum number of point-defense attacks which may be made. If the point-defense (P-D) die roll is within the kill spread, that die roll is the number of missiles destroyed from that particular salvo (i.e., dice may not be rolled for missiles eliminated in this way).

A fighter may dodge torps during the Torp Results Phase and then use the point-defense system against missiles in the Missile Results Phase without penalty.

X.5 Secrecy

When engaged in games where trust between the opponents is implicit, players may wish to institute the following rules.

Starcraft Displays: Keep your Starcraft Displays hidden from your opponent. Mark off ammunition expenditures and hits on the Damage Track as they occur, but don't let your opponent know the exact status of your forces.

Let your opponent roll for Critical Hits as usual, but don't let him know the exact results. No matter how good a player's memory, specific details of each Critical Hit may be forgotten.

Here are some things which you must tell your opponent:

  • Your vessel's current Drive value — remember, this value may fall and rise dramatically in the case of certain Critical Hits.
  • When your vessel has been destroyed — obviously.

Starcraft Crews: Since the displays will be hidden, crew values will be too. In the case of scenarios where crew values are set, it will be best to hide the real identities of vessels so that an opponent will not know which ship contains which crew. Do this by applying numbered stickers to the bottoms of the miniature bases, or painting ID numbers there. Number-code your crews and you'll be set.

Players may secretly roll their Initiative D10, add their current best pilot's score, and just tell their opponent the final modified Initiative Roll.

Y.0 Silent Death Questions

This section is dedicated to answering questions which have arisen during the play of Silent Death and Overkill.

Silent Death

6.1 Target Speed Restrictions: When figuring out whether a target can be hit by a weapon with a target speed restriction, do you use the target's current Drive number, or the number of movement points it expended during the preceding Movement Phase? As stated on page 11 of the Silent Death rules, you use the target's current Drive number. Any unused movement points are assumed to be expended in automatic, computer-controlled evasive maneuvering which can not be represented by the scale of the map.

10.2 Full Stop and Target Speed Restrictions: If a fast target has declared a Full Stop, can it then be hit by weapons with Target Speed Restrictions? Yes.

Overkill

D.1 Spending Luck Points: Can a Pilot with Luck points spend them to reroll a poor Critical Hit that he inflicts on an opponent? No.

Counter Sheet: Why were the exploding vessel counters provided on the Overkill counter sheet? We've always found it rather unsatisfying to just remove a miniature when it has been destroyed. Therefore, the exploding vessel counters have been provided so that a victor can make a silly exploding sound effect and mark the demise of his victim with a tacky, and psychologically devastating visual aid. If you want a real use for these counters, use them to mark the positions of destroyed vessels: the resulting debris will generate a 3D6 attack scoring Low damage to any starcraft or torp flying into the hex.

Z.0 Consolidated Tables (Annex #2)

Z.1 Master Weapon Table

Weapon TypeBase Attack DiceShort (+1)Mid (0)Long (-1)Target Speed RestrictionsDamage
Mass Driver Cannons
Minigun2D6+ADB1-23-56-12NoneLow †
Autocannon2D6+ADB1-34-1011-24Target Drive ≤10Medium †
Railpropeator2D6+ADB1-45-1516-36Target Drive ≤6High †
Laser Cannons
Pulse Laser2D8+ADB1-34-910NoneLow
Meld Laser2D8+ADB1-67-1819-20Target Drive ≤12Medium
Turbo Laser2D8+ADB1-910-2526-30Target Drive ≤8High
Blast Cannons
Splattergun2D6+ADB1-23-67-10NoneMedium
Blatgun2D6+ADB1-45-1011-15Target Drive ≤13High
Disruptor Cannons
Disruptorgun2D8+ADB123-6NoneMedium §
Disintegrator2D8+ADB12-34-12Target Drive ≤11High §
Ion Cannons
Impulsegun2D8+ADB1-34-89-10NoneHigh
Ion Ram2D8+ADB1-56-1314-15Target Drive ≤15All
Plasma Cannons
Plazgun2D6+ADB1-23-45-10NoneAll ¥
Heavy Plazgun2D6+ADB1-45-89-15Target Drive ≤11All x2 ¥
Energy Bolt Projectors
Protobolt2D6+ADB5-89-1213-16Target Drive ≤14s.10 / m.8 / l.6
Warheads
Missile1D6—1-10 *—NoneHigh
Standard Mk10 Torp1D12N/AN/AN/ANoneAll
Standard Mk20 Torp2D12N/AN/AN/ANoneAll
Standard Mk30 Torp3D12N/AN/AN/ANoneAll
Standard Mk40 Torp4D12N/AN/AN/ANoneAll
Standard Mk50 Torp5D12N/AN/AN/ANoneAll

Notes (as printed):

  • † Whenever two of the attack dice roll doubles, multiply base damage delivered by 2.
  • § If target's Defensive Value has not been reduced by a critical hit, add 1 to its Defensive Value. Also, completely ignore target's Damage Reduction when resolving a hit.
  • ¥ If the attack dice roll triples, the weapon mount overloads and is destroyed. The target is not affected.
  • * A missile's target must be within 10 hex range only at the beginning of the Missile/Torp Launch Phase.

Z.2 Integrated Torp Table

Torp TypeSpeedDurationDamage DeliveredDefensive ValuePilot (Plt) SkillTracking ConeHoming SystemNotes
Mk10 Torp Loads
Standard Mk10 Torp12101D12105360°ALH
Express-110 Torp18101D12103360°ALH
Sentinel-210 Torp12101D12104180°FTHTorp remains stationary after discharge, then activates when a target is within 10 hexes at the beginning of a Movement Phase.
DFWH-310 Torp8/15101D12122180°DTHSpeed is 8 while flight is directed by firer or during unguided flight, and increases to 15 the turn after guidance goes terminal.
Review-410 Torp10101D1284180°CSH
Relock-510 Torp1551D12112180°IFH
Deadlock-610 Torp1821D12102360°IFH
Remote R-10 Torp831D1282—DXH
Mk20 Torp Loads
Standard Mk20 Torp12102D12105360°ALH
Express-120 Torp16102D12103360°ALH
Review-420 Torp10102D1284180°CSH
Relock-520 Torp1452D12112180°IFH
Deadlock-620 Torp1622D12102360°IFH
Mk30 Torp Loads
Standard Mk30 Torp12103D12105360°ALH
Express-130 Torp14103D12103360°ALH
Sentinel-230 Torp12103D12103180°FTHTorp remains stationary after discharge, then activates when a target is within 10 hexes at the beginning of a Movement Phase.
Relock-530 Torp1353D12112180°IFH
Deadlock-630 Torp1423D12102360°IFH
Remote R-30 Torp843D1282—DXH
Mk40 Torp Loads
Standard Mk40 Torp12104D12105360°ALH
DFWH-340 Torp8/12104D12122180°DTHSpeed is 8 while flight is directed by firer or during unguided flight, and increases to 12 the turn after guidance goes terminal.
Review-440 Torp9104D1294180°CSH
Deadlock-640 Torp1824D12102360°IFH
J40 Decoy-X Torp121—102—DXHNegates the effect of one anti-torp decoy dispensed by an enemy fighter or gunboat. Player who launched the J40 decides which decoy to negate that turn.
Mk50 Torp Loads
Standard Mk50 Torp12105D12105360°ALH
Ex50 (surplus) Torp *10105D1210560°FTHTorp has severe disadvantages. Scenario special rules will indicate when this torp type is to be used.
Relock-550 Torp1155D12112180°IFH
Mayhem-750 Torp102—102—DXHThis is a multi-warhead drone which carries 5 Relock-510 Torps. At the beginning of the Movement Phase following its last turn of flight these torps are deployed with each facing a separate hexside (except rear).
Remote R-50 Torp855D1282—DXH

Key (as printed): Speed is the number of movement points which can be expended by the torp each Movement Phase; only DXH homing system torps may expend fewer movement points than their listed Speed value. Duration is the maximum number of game turns that the torp may continue to move; if at the end of its Duration a torp has not detonated, it is removed from the playing surface. Damage Delivered: if a torp hits its target, roll the dice indicated and deliver all damage. Defensive Value is the Defensive Value of the torp against cannon, projector or missile attacks while in flight. Pilot (Plt) Skill is a measure of the ability of the torp to dodge incoming torps. Tracking Cone indicates the angle through which the torp can track its target (see Section B.2). Homing System entry indicates the type of homer the torp uses (see Section B.1). Notes indicate special rules for torp use.

Z.3 Anti-Torpedo Capabilities Table

Vessel TypeDecoys AvailablePoint-Defense Kill Spread (1D10)
Betafortress61-7 [6]
Blizzard2—
Dart11-6 [1]
Death Wind21-4 [2]
Drakar41-6 [6]
Epping41-7 [3]
Glaive4—
Hell Bender2—
Kosmos21-5 [1]
Lance Electra21-4 [2]
Night Hawk21-3 [1]
Pharsii II31-6 [2]
Pit Viper1—
Revenge51-6 [3]
Salamander21-7 [2]
Sentry41-7 [3]
Seraph41-6 [2]
Shryak Shuttle21-4 [4]
Sorensen III1—
Spirit Rider1—
Star Raven41-7 [4]
Talon11-5 [2]
Teal Hawk21-3 [2]
Thunder Bird2—

Z.4 Damage Control Table

Vessel TypeDamage Control Success Spread (1D10)
Betafortress1-8
Blizzard1-2
Dart1-2
Death Wind1-5
Drakar1-8
Epping1-7
Glaive1-6
Hell Bender1-3
Kosmos1-2
Lance Electra1-5
Night Hawk1-3
Pharsii II1-5
Pit Viper1-2
Revenge1-5
Salamander1-6
Sentry1-4
Seraph1-6
Shryak Shuttle1-7
Sorensen III1-3
Spirit Rider1-3
Star Raven1-7
Talon1-3
Teal Hawk1-3
Thunder Bird1-3

Z.5 Luck Gain/Loss Table

Luck PointsCondition (See Section D.1)
+5Single-handedly destroy an enemy MMAC (4+ man) gunboat.
+3Single-handedly destroy an enemy TMAC (2 or 3 man) fighter.
+2Single-handedly destroy an enemy SMAC (1 man) fighter.
+1Deliver at least half of the hits which destroy an enemy vessel.
-1Force opponent to reroll 1 attack die (your choice).
-2Force reroll of a critical hit result.
-3Force opponent to reroll 2 attack dice (your choice).
-5Dodge a torpedo of your choice.

Z.6 Alternate Range Effects Table

Weapon TypePoint Blank (+2)Short (+1)Mid (0)Long (-1)Very Long (-2)Extreme (-4)
Mass Driver Cannons
Minigun123-56-1011-12—
Autocannon12-34-1011-2021-2223-24
Railpropeator12-45-1516-3031-3334-36
Laser Cannons
Pulse Laser1-234-8910—
Meld Laser12-67-1516-1718-1920
Turbo Laser12-910-1920-2526-2829-30
Blast Cannons
Splattergun123-45-67-10—
Blatgun12-45-78-1011-1314-15
Disruptor Cannons
Disruptorgun—123-45-6—
Disintegrator—12-34-67-12—
Ion Cannons
Impulsegun12-34-67-89-10—
Ion Ram12-56-131415—
Plasma Cannons
Plazgun123-45-67-89-10
Heavy Plazgun12-45-89-1011-1213-15
Energy Bolt Projectors
Protobolt—5-89-1213-16——

Z.7 Expanded Turn Sequence

  • Missile Launch Phase: i) Attempt lock-ons, then launch.
  • Torp Launch Phase: i) Allocate attacks, then launch.
  • Initiative Phase: i) Roll 1D10, modified by best pilot.
  • Movement Phase: i) Alternate movement of vessels. ii) Torps move after their targets do.
  • Torp Results Phase: i) Attempt dodging, or fire point-defense system. ii) Resolve any torp damage. iii) Attempt jamming, or deploy decoys.
  • Cannon/Projector Fire Phase: i) Gunners, in order, fire their weapon systems. ii) Pilots, in order, fire their weapon systems.
  • Missile Results Phase: i) Resolve missile attacks. ii) Asteroids drift.