Silent Death: Overkill – The Ptolemean Wars thumbnail

Silent Death: Overkill – The Ptolemean Wars

Silent Death: Overkill – The Ptolemean Wars Rulebook

Table of Contents

Table of Contents

1.0 Introduction

1.1 What You Get

Overkill: The Ptolemean Wars provides Silent Death players with Starcraft Displays for six new fighter and gunboat designs. The module also contains a background to the conflict, information on the campaign's notable flight leaders, a unit-by-unit breakdown of the squadrons involved, a set of new playing guidelines in Rules Annex #1 (new weapons, torpedo loads, life pods, gunboats and pilot luck), and guidelines for generating Starcraft Displays for other starfighter miniatures.

A full counter sheet is included. These are the game markers and ship counters needed for the scenarios in this module, together with extra torps and missiles for large multi-player games and demo derbies.

The metal miniatures for the six new designs (Blizzard, Kosmos, Hell Bender, Death Wind, Glaive and Drakar) are sold separately as Silent Death blister packs. If miniatures are not used, the counter sheet supplies every fighter needed for the scenarios.

The Silent Death Boxed Set

Many scenarios use starfighters originally presented in Silent Death. The Starcraft Displays from that game and the counters in this module are needed to play them.

1.2 Some Background on the Empire

Background narrative (1.2) is not transcribed; see the source note in the Table of Contents.

1.3 A Note on Dates

Imperial Reckoning counts years from Year 0, the consecration of the Empire and the rise of the Imperial Dynasty Throne. Positive years are written "Imp" (for example, Imp 100) and negative years "Prelmp" (for example, Prelmp 100). Dates may include the day of the year after a colon: Imp 100:050 is the 50th day of the 100th year. There are 360 standard days in a year, so the day number never exceeds 360; Imp 475:360 is the last day of year 475 and Imp 476:001 the first day of year 476.

The galactic day is an imaginary twenty-five (Old Earth) hour day, and the year is three hundred and sixty days long.

2.0 The Ptolemean Wars

Sections 2.1 through 2.6 (Ptolemean space and system listings, the Dneprodzerkutsk expansionism, the Band of Iron, the invasions, the epilogue and the characterization of the combatants) are historical and descriptive narrative and are not transcribed. The campaign timeline they establish is reflected in the Date and Location lines of the scenarios and the squadron rosters in Sections 3.0 to 5.0.

Fighter and Gunboat Availability

The following published starcraft types are available to the various antagonists during the first year of the Ptolemean Wars.

PtolemusDneprodzerkutskColos
BlizzardEppingDrakar
Death WindNight HawkHell Bender
EppingPharsii IIKosmos
GlaiveRevengeNight Hawk
Pit ViperSalamanderPharsii II
SeraphSorensen IIIRevenge
Shryak ShuttleSpirit RiderSalamander
Thunder BirdThunder BirdSeraph
Teal Hawk

Role-playing note: for players who like to play the personas of their pilots, the Ptolemeans may be treated as Ancient Egyptians, the Dneprodzerkutsk as Mongols, and the Colosians as Cold War Soviets.

3.0 Ptolemean Fighter Units

Note: use of the Pilot Luck stat is optional, as per Section D.0 in Rules Annex #1.

Each unit entry gives the wing's designation, its nickname and commanding officer, and the squadron roster as of the date stated. A squadron roster lists each squadron leader (Pit = Piloting skill, Gnr = Gunnery skill, Luck = Luck stat where applicable), the assets (starcraft) and the typical crew. Narrative sections describing each unit's history are not transcribed.

3.1 33rd Independent Ptolemean Fighter Wing ("Hounds of Anubis")

Commanding Officer: Gorum Amhut Aziz

Squadron Summary, as of Imp 474:351

  • Atep Squadron. Squadron Leader: Demoss Amenophis (Pit 10, Gnr 8, Luck 4). Assets: 12 x Blizzard. Typical Pilot (Plt 7, Gnr 6).
  • Bast Squadron. Squadron Leader: Marem Tuthmol (Pit 9, Gnr 9). Assets: 12 x Death Wind. Typical Pilot (Plt 7, Gnr 5). Typical Gunner (Gnr 7).
  • Khensu Squadron. Squadron Leader: Hig Shepsut (Plt 9, Gnr 7, Luck 1). Assets: 8 x Death Wind, 2 x Glaive, 2 x Epping. Typical Pilot (Plt 6, Gnr 6). Typical Gunner (Gnr 8).

3.2 102nd Ptolemean Carrier Wing ("Charioteers")

Commanding Officer: Apu Aphrod Nagomi

Squadron Summary, as of Imp 474:351

  • Thrust Squadron. Squadron Leader: Mut Tahara (Plt 9, Gnr 8). Assets: 6 x Blizzard, 4 x Pit Viper. Typical Pilot (Plt 5, Gnr 6).
  • Parry Squadron. Squadron Leader: Saiyd Djer (Plt 8, Gnr 8). Assets: 10 x Death Wind. Typical Pilot (Plt 5, Gnr 4). Typical Gunner (Gnr 5).
  • Guard Squadron. Squadron Leader: Unis Udimi (Plt 7, Gnr 8). Assets: 8 x Glaive, 2 x Seraph. Typical Pilot (Plt 4, Gnr 5). Typical Gunner (Gnr 4).

3.3 1241st Home Defense Wing ("Hope's Constellation")

Commanding Officer: Haffar "Hope" Aman

Squadron Summary, as of Imp 475:002

  • Capital Squadron. Squadron Leader: Dendra Yasut (Plt 7, Gnr 7). Assets: 8 x Blizzard. Typical Pilot (Plt 4, Gnr 3).
  • Khanut Sea Squadron. Squadron Leader: Anjibra Seskaf (Plt 6, Gnr 6). Assets: 8 x Thunder Bird. Typical Pilot (Plt 3, Gnr 3).
  • Lake Tem Squadron. Squadron Leader: Bib Wadji (Plt 6, Gnr 7). Assets: 4 x Death Wind, 4 x Glaive. Typical Pilot (Plt 4, Gnr 2). Typical Gunner (Gnr 3).
  • Great Isthmus Squadron. Squadron Leader: Yasohtep Ay (Plt 6, Gnr 4). Assets: 4 x Death Wind, 2 x Seraph, 2 x Epping, 2 x Shryak Shuttle. Typical Pilot (Plt 3, Gnr 2). Typical Gunner (Gnr 4).

3.4 3447th Ptolemean Interceptor Group ("Great Zenith")

Commanding Officer: Kemu Terothath

Squadron Summary, as of Imp 475:081

  • Pole Star Squadron. Squadron Leader: Mi'a Semerkhet (Plt 5, Gnr 6). Assets: 12 x Blizzard. Typical Pilot (Plt 5, Gnr 2).
  • Spica Squadron. Squadron Leader: Ali Mentuhotep (Plt 5, Gnr 4). Assets: 12 x Thunder Bird. Typical Pilot (Plt 2, Gnr 2).
  • Nadir Squadron. Squadron Leader: Bes Khaba-Mentu (Plt 6, Gnr 4). Assets: 8 x Glaive. Typical Pilot (Plt 3, Gnr 1). Typical Gunner (Gnr 2).

4.0 Dneprodzerkutsk Fighter Units

Note: use of the Pilot Luck stat is optional, as per Section D.0 in Rules Annex #1.

4.1 4th Black Plague Fighter Wing ("Reign of Despair")

Commanding Officer: Yu Xiao-Ming

Squadron Summary, as of Imp 474:351

  • Asp Squadron. Squadron Leader: Jarik Koontz (Plt 8, Gnr 7, Luck 4). Assets: 12 x Spirit Rider. Typical Pilot (Plt 7, Gnr 6, Luck 2).
  • Boa Squadron. Squadron Leader: Misha Bakoyinnan (Plt 9, Gnr 7, Luck 5). Assets: 14 x Thunder Bird. Typical Pilot (Plt 6, Gnr 7, Luck 7).
  • Cobra Squadron. Squadron Leader: Hugo Khun (Plt 7, Gnr 8, Luck 3). Assets: 10 x Sorensen III, 2 x Thunder Bird (modified). Typical Pilot (Plt 6, Gnr 6, Luck 7). Typical Gunner (Gnr 7).

Note: the Thunder Birds of Cobra Squadron are modified to carry three (3) Mk20 torps instead of the normal five torpedo load.

On Imp 475:240 the 4th Black Plague Fighter Wing was disbanded.

4.2 Dneprodzerkutsk Fighter Attrition Unit 77-A ("Sacrificial Terror")

Commanding Officer: Bok Zhiding

Squadron Summary, as of Imp 474:351

  • Hunger Squadron. Squadron Leader: Mummar Chawla (Plt 6, Gnr 9, Luck 7). Assets: 16 x Thunder Bird. Typical Pilot (Plt 4, Gnr 6, Luck 7).
  • Thirst Squadron. Squadron Leader: Cali Kunhar Krishnan (Plt 7, Gnr 5, Luck 2). Assets: 16 x Night Hawk. Typical Pilot (Plt 5, Gnr 5, Luck 1).

Note: all starcraft of Attrition Unit 77-A suffer from Poor Mechanical Reliability (see Section F.0 in Rules Annex #1). The unit was declared destroyed on Imp 475:197.

4.3 89th Behemoth Heavy Interceptor Group ("The Winged Legion of Death")

Commanding Officer: Markus Huynh

Squadron Summary, as of Imp 474:351

  • Undertaker Squadron. Squadron Leader: Forrest Smychynsky (Plt 8, Gnr 8, Luck 8). Assets: 10 x Salamander. Typical Pilot (Plt 7, Gnr 4, Luck 2). Typical Gunner (Gnr 6).
  • Grave Squadron. Squadron Leader: Ram Shaswat (Plt 7, Gnr 8, Luck 4). Assets: 10 x Sorensen III. Typical Pilot (Plt 5, Gnr 5, Luck 0). Typical Gunner (Gnr 5).
  • Last Rights Squadron. Squadron Leader: Sturkie Das Gokul (Plt 8, Gnr 6, Luck 2). Assets: 8 x Pharsii II. Typical Pilot (Plt 6, Gnr 7, Luck 7). Typical Gunner (Gnr 6).
  • Reaper Squadron. Squadron Leader: Gyrlin Arganza (Plt 7, Gnr 6, Luck 2). Assets: 4 x Pharsii II, 4 x Epping. Typical Pilot (Plt 5, Gnr 4, Luck 7). Typical Gunner (Gnr 6).

On Imp 475:101 the 89th lost its ability to act as a cohesive fighting force.

4.4 1st Aerial Atrocity Regiment ("Overkill")

Commanding Officer: Hark Shapka

Squadron Summary, as of Imp 474:351

  • Dominator Squadron. Squadron Leader: Urgi Asami (Plt 10, Gnr 9, Luck 6). Assets: 4 x Spirit Rider, 4 x Thunder Bird, 4 x Revenge. Typical Pilot (Plt 6, Gnr 6, Luck 3). Typical Gunner (Gnr 5).
  • Beast Master Squadron. Squadron Leader: Hama Viadomov (Plt 9, Gnr 9, Luck 4). Assets: 8 x Pharsii II, 4 x Revenge. Typical Pilot (Plt 5, Gnr 6, Luck 4). Typical Gunner (Gnr 4).
  • Terminator Squadron. Squadron Leader: Yin Khun Wu (Plt 8, Gnr 7, Luck 3). Assets: 8 x Epping, 4 x Revenge. Typical Pilot (Plt 5, Gnr 5, Luck 2). Typical Gunner (Gnr 6).

On Imp 475:235 the regiment was recalled to Dneprodzerkutsk space for refit and took part in no further operations against House Ptolemus.

5.0 Colosian Fighter Units

Note: two of these units are Millennia Warrior sub-units flying for the Colosians. Use of the Pilot Luck stat is optional, as per Section D.0 in Rules Annex #1.

5.1 20th Colosian Strike Fighter Wing ("Mighty Thunder")

Commanding Officer: Urnst Faulconer

Squadron Summary, as of Imp 475:002

  • Bolt Squadron. Squadron Leader: Keri Tagtmeyer (Plt 8, Gnr 8, Luck 3). Assets: 12 x Kosmos. Typical Pilot (Plt 6, Gnr 5, Luck 7).
  • Crusher Squadron. Squadron Leader: Herman Zydanowicz (Plt 10, Gnr 6, Luck 2). Assets: 12 x Kosmos. Typical Pilot (Plt 5, Gnr 6, Luck 7).
  • Hurler Squadron. Squadron Leader: Mac Wroblewski (Plt 6, Gnr 5, Luck 7). Assets: 8 x Hell Bender, 4 x Revenge. Typical Pilot (Plt 5, Gnr 5). Typical Gunner (Gnr 7).

The 20th ceased combat operations on Imp 475:199.

5.2 2175th Millennia Warrior Medium SMAC Regiment

SMAC fighter component of the "Plasma Squad". Commanding Officer: Harald Van Rensselaer

Squadron Summary, as of Imp 475:002

  • Discus Squadron. Squadron Leader: Alex Shackman (Plt 9, Gnr 10, Luck 8). Assets: 12 x Kosmos. Typical Pilot (Plt 8, Gnr 8, Luck 3).
  • Javelin Squadron. Squadron Leader: Pietor Gies (Plt 8, Gnr 8, Luck 4). Assets: 12 x Hell Bender. Typical Pilot (Plt 7, Gnr 7, Luck 2).
  • Shot Squadron. Squadron Leader: Yardfellow Macklin (Plt 8, Gnr 7, Luck 3). Assets: 10 x Night Hawk, 2 x Teal Hawk. Typical Pilot (Plt 7, Gnr 6, Luck 2). Typical Gunner (Gnr 6).

The regiment was destroyed as of Imp 475:240.

5.3 4155th Millennia Warrior TMAC Regiment

Heavy fighter component of "Avalanche". Commanding Officer: Martin Eismann

Squadron Summary, as of Imp 475:005

  • Mercy Squadron. Squadron Leader: Arthur Mendicino (Plt 9, Gnr 8, Luck 6). Assets: 12 x Seraph. Typical Pilot (Plt 6, Gnr 7, Luck 4). Typical Gunner (Gnr 6).
  • Angel Squadron. Squadron Leader: Helmut Buchholz (Plt 9, Gnr 7, Luck 4). Assets: 10 x Pharsii II. Typical Pilot (Plt 7, Gnr 5, Luck 2). Typical Gunner (Gnr 6).
  • Deliverance Squadron. Squadron Leader: Jiles LeClare (Plt 8, Gnr 7, Luck 6). Assets: 10 x Drakar. Typical Pilot (Plt 5, Gnr 5, Luck 7). Typical Gunner (Gnr 6).

5.4 139th Colosian Carrier Wing ("Satan's Fulcrum")

Commanding Officer: Leonid Podolak

Squadron Summary, as of Imp 475:022

  • Jade Squadron. Squadron Leader: Vladimir Gregor (Plt 7, Gnr 7, Luck 1). Assets: 10 x Hell Bender. Typical Pilot (Plt 5, Gnr 6, Luck 7).
  • Topaz Squadron. Squadron Leader: Sergi Yasenchak (Plt 8, Gnr 6, Luck 3). Assets: 10 x Salamander. Typical Pilot (Plt 5, Gnr 5, Luck 7). Typical Gunner (Gnr 6).
  • Aquamarine Squadron. Squadron Leader: Kyle James Worsky (Plt 7, Gnr 6, Luck 7). Assets: 8 x Drakar. Typical Pilot (Plt 4, Gnr 5). Typical Gunner (Gnr 4).

The 139th was pulled from line duty late in Imp 475.

6.0 Scenarios

This section includes twelve scenarios set in chronological order. They cover many aspects of the fighter battles of the Ptolemean Wars, and together involve every fighter unit described in Sections 3.0 to 5.0. The scenarios cover fighter-on-fighter combat only; they are representative engagements, and the capital-ship battles of the same period are not modelled.

The narrative excerpts, situation paragraphs and battle reports that accompany each scenario are not transcribed.

Reinforcements

Some scenarios allow reinforcements to enter the playing surface during the game. Players keep track of game turns using the Game Turn Record Track printed along the bottom of several of the new Starcraft Displays.

When reinforcements are called for on a turn, they are placed along their entry Edge (on an edge hex) as the first action of that turn. They must face a hexside out toward the playing surface (not parallel with the map edge and not facing off the board). Entering reinforcements may be targeted with missile and/or torp attacks in the first Phase of their entry turn. A good pilot entering with reinforcements may use his Plt skill to influence the initiative die roll on his turn of entry.

Exiting Starcraft

Some scenarios call for vessels to exit the playing surface. Exiting costs 1 movement point from an edge hex in which the vessel is facing away from map hexes.

Unless a scenario specifically allows it, no units may exit the playing surface. A starcraft that does so without permission is considered destroyed, with credit for the kill going to the last opposing crewmember to fire at it.

6.1 Opening Moves

Black Plague vs Ptolemus. Date: Imp 474:351. Location: High orbit over Scion; Progeny system.

Forces

  • Ptolemean player. Patrol Element from Atep Squadron, 33rd Independent Ptolemean Fighter Wing. Set up first in Area F.
    • Blizzard A: Pilot (Pit 6, Gnr 6)
    • Blizzard B: Pilot (Pit 5, Gnr 5)
  • Black Plague player. Flight from Asp Squadron, 4th Black Plague Fighter Wing. Set up second along Edge 1.
    • Spirit Rider A: Jarik Koontz (Pit 8, Gnr 7, Luck 4)
    • Spirit Rider B: Pilot (Pit 8, Gnr 6, Luck 3)
    • Spirit Rider C: Pilot (Pit 7, Gnr 7)
    • Spirit Rider D: Pilot (Pit 4, Gnr 5)

Reinforcements

  • Ptolemean player. Lead Element from Khensu Squadron, 33rd Independent Ptolemean Fighter Wing. Enters on turn 3 from Edge 3.
    • Death Wind A: Hig Shepsut (Pit 9, Gnr 7, Luck 7), Gunner (Gnr 9)
    • Death Wind B: Pilot (Pit 6, Gnr 5), Gunner (Gnr 7)
  • Black Plague player. Element from Cobra Squadron, 4th Black Plague Fighter Wing. Enters on turn 4 from Edge 1.
    • Sorensen III A: Pilot (Pit 7, Gnr 9), Gunner (Gnr 7)
    • Sorensen III B: Pilot (Pit 5, Gnr 7), Gunner (Gnr 6)

Special Rules

  1. Due to the suddenness of the attack, the Black Plague player automatically has the initiative for the first two turns of the game. Squadron Leader Hig Shepsut then appears and stabilizes the situation. Starting on turn 3, when he enters the playing surface, Hig may use his Plt skill to influence the initiative die roll.

Victory Conditions

At the end of game turn 10, the Black Plague player totals the TPV of all enemy vessels destroyed and adds the following bonuses:

  • +10 points if Hig Shepsut is killed or his fighter is destroyed.
  • +5 points for each Black Plague fighter that received fewer than 5 hits of damage.
  • +2 points for each Mk20 torp from a Sorensen III that has not been fired.

Compare the modified total:

PointsResult
116+Decisive Black Plague victory
76-115Marginal Black Plague victory
66-75Draw
26-65Marginal Ptolemean victory
0-25Decisive Ptolemean victory

6.2 Clash at White Star

Behemoth vs Ptolemus. Date: Imp 474:351. Location: Deep space approach to Far Station; White Star system.

Forces

  • Ptolemean player. Patrol Element from Parry Squadron, 102nd Ptolemean Carrier Wing. Set up first along Edge 3.
    • Death Wind A: Pilot (Pit 4, Gnr 5), Gunner (Gnr 6)
    • Death Wind B: Pilot (Pit 3, Gnr 5), Gunner (Gnr 5)
  • Behemoth player. Scout Element from Undertaker Squadron, 89th Behemoth Heavy Interceptor Group. Set up second along Edge 1.
    • Salamander A: Pilot (Pit 7, Gnr 8), Gunner (Gnr 8)
    • Salamander B: Pilot (Pit 6, Gnr 6), Gunner (Gnr 7)

Special Rules

  1. Both fighter elements have nearby combat support craft. A single Standard Mk20 torp enters the playing surface during the Missile/Torp Launch Phase of every turn. Each time one is to appear, roll 1D10. On a 1-7 it is a Behemoth torp, placed on an edge hex along Edge 1. On an 8-10 it is a Ptolemean torp, placed on an edge hex along Edge 3. Entering torps are placed by their owning player and targeted as desired.
  2. The Ptolemean Death Winds have had their torpedo pylons modified to carry Standard Mk10 torps instead of Mk20s. Each Death Wind therefore carries 4 Standard Mk10 torpedoes.

Victory Conditions

At the end of game turn 10, the scenario is over and the Behemoth player totals victory points:

  • +20 points for the first Death Wind destroyed.
  • +10 points for another Death Wind destroyed.
  • +5 points for each Salamander that survives the scenario.
  • +1 point for each Ptolemean torp that entered the map under Special Rule 1.
PointsResult
40+Decisive Behemoth victory
30-39Marginal Behemoth victory
20-29Draw
10-19Marginal Ptolemean victory
0-9Decisive Ptolemean victory

6.3 First Emperor's Day

Black Plague vs Ptolemus. Date: Imp 475:001. Location: Outer reaches of the Progeny system.

Forces

  • Ptolemean player. Mixed Elements from the Charioteers, 102nd Ptolemean Carrier Wing. Set up first in Areas H, I and/or J.
    • Glaive A: Pilot (Pit 6, Gnr 7), Gunner (Gnr 7)
    • Death Wind A: Pilot (Pit 6, Gnr 6), Gunner (Gnr 6)
    • Pit Viper A: Pilot (Pit 4, Gnr 5)
    • Pit Viper B: Pilot (Pit 3, Gnr 4)
  • Black Plague player. Flight from Hunger Squadron, Attrition Unit 77-A. Set up second along Edge 1.
    • Thunder Bird A: Pilot (Pit 6, Gnr 8, Luck 7)
    • Thunder Bird B: Pilot (Plt 4, Gnr 6)
    • Thunder Bird C: Pilot (Plt 3, Gnr 5)
    • Thunder Bird D: Pilot (Plt 2, Gnr 4)
  • Black Plague player. Flight from Thirst Squadron, Attrition Unit 77-A. Enters on turn 2 along Edge 1.
    • Night Hawk A: Cali Krishnan (Pit 7, Gnr 5, Luck 2)
    • Night Hawk B: Pilot (Pit 5, Gnr 5)
    • Night Hawk C: Pilot (Pit 4, Gnr 4)
    • Night Hawk D: Pilot (Pit 3, Gnr 3)
  • Ptolemean player. Ad Hoc Reserves from the Charioteers, 102nd Ptolemean Carrier Wing. Enters on turn 4 along Edge 4.
    • Blizzard A: Pilot (Pit 5, Gnr 7)
    • Blizzard B: Pilot (Plt 3, Gnr 2)
  • Black Plague player. Black Plague Strike Fighter Element. Enters on turn 6 along Edge 1.
    • Revenge A: Pilot (Pit 4, Gnr 1), Gunner (Gnr 7)
    • Revenge B: Pilot (Pit 4, Gnr 1), Gunner (Gnr 6)
  • Ptolemean player. Ad Hoc Reserve from the Charioteers, 102nd Ptolemean Carrier Wing. Enters on turn 7 along Edge 2.
    • Seraph A: Pilot (Plt 2, Gnr 2), Gunner (Gnr 6)

Special Rules

  1. Both Black Plague Revenge strike fighters must be loaded with 10 Standard Mk50 torps.
  2. Both Black Plague Revenge strike fighters are attempting an attack run on the Bold Horizon, the Charioteers' carrier, which is nearby off-board. Before the end of the scenario, the Revenges should attempt to exit the playing surface from Edge 3 with as many of their loaded torps as possible. No other units may exit the playing surface.
  3. Fighters from the two flights of Attrition Unit 77-A suffer from Poor Mechanical Reliability (see Section F.0 in Rules Annex #1).
  4. The Thunder Birds are loaded with Standard Mk20 and Standard Mk10 torps only.

Victory Conditions

At the end of game turn 10, the scenario is over and the Black Plague player totals victory points:

  • +10 points for each torp-armed Revenge exited off Edge 3.
  • +5 points for each torpedo carried by a Revenge exited off Edge 3.
  • +5 points for each Ptolemean vessel destroyed.
  • +2 points for each undestroyed Ptolemean vessel reduced to Drive 5 or less.
PointsResult
140+Decisive Black Plague victory
100-139Marginal Black Plague victory
80-99Draw
70-79Marginal Ptolemean victory
0-69Decisive Ptolemean victory

6.4 A Second Front

Colosians vs Ptolemus. Date: Imp 475:002. Location: Outer reaches of the Lebanstar gravity well.

Forces

  • Ptolemean player. Defensive Elements from Hope's Constellation, 1241st Ptolemean Home Defense Wing. Set up first in Areas E and/or F.
    • Blizzard A: Pilot (Pit 5, Gnr 6)
    • Blizzard B: Pilot (Plt 5, Gnr 5)
    • Death Wind A: Pilot (Plt 3, Gnr 4), Gunner (Gnr 2)
    • Death Wind B: Pilot (Plt 2, Gnr 3), Gunner (Gnr 1)
  • Colosian player. Forward Elements from Mighty Thunder, 20th Colosian Strike Fighter Wing. Set up second along Edge 2.
    • Kosmos A: Pilot (Pit 7, Gnr 8, Luck 3)
    • Kosmos B: Pilot (Pit 5, Gnr 7)
    • Hell Bender A: Pilot (Pit 6, Gnr 6)
    • Hell Bender B: Pilot (Pit 5, Gnr 5, Luck 1)

Reinforcements

  • Colosian player. Follow-on Element from Hurler Squadron, 20th Colosian Strike Fighter Wing. Enters on turn 3 along Edge 2.
    • Hell Bender C: Pilot (Pit 4, Gnr 6, Luck 1)
    • Hell Bender D: Pilot (Pit 4, Gnr 5)

Special Rules

  1. At this early stage of the campaign the Ptolemeans are interested in conserving forces as well as inflicting casualties. Therefore, starting on turn 6, Ptolemean fighters may withdraw from the battle (exit the playing surface from Edge 4 without penalty), provided that: (i) only one Ptolemean fighter may be withdrawn for every Colosian fighter destroyed; and (ii) at the moment of withdrawal the Ptolemean fighter has a Drive value greater than 10. Colosian fighters may not exit the playing surface.

Victory Conditions

At the end of game turn 10, the scenario is over and both sides total the TPVs of enemy fighters destroyed. The Colosian player then applies these modifiers:

  • +15 points for each Ptolemean fighter left with a Drive value less than 10.
  • +10 points for each friendly fighter that has taken fewer than 5 hits of damage.
  • -10 points for each Ptolemean fighter withdrawn.

The Ptolemean player's TPV kill total is subtracted from the Colosian player's modified total. Compare the result:

PointsResult
180+Decisive Colosian victory
100-179Marginal Colosian victory
0-99Draw
(-60) to (-1)Marginal Ptolemean victory
(-61) or lessDecisive Ptolemean victory

6.5 Deep Strike

Colosians vs Ptolemus. Date: Imp 475:005. Location: Approach to Konrad; Ascension system.

Forces

  • Colosian player. Single Strike Vessel from Deliverance Squadron, 4155th Millennia Warrior TMAC Regiment. Set up each time along Edge 1.
    • Drakar A: Pilot (Plt 7, Gnr 7, Luck 2); Gunner A (Gnr 6), Gunner B (Gnr 9), Gunner C (Gnr 8), Gunner D (Gnr 5)
  • Ptolemean player. Various fighter units from the Konrad Civil Defense Network. Enter according to Special Rule 3, along the Edges indicated:
    • Force #1, along Edge 2: Blizzard A: Pilot (Pit 3, Gnr 5)
    • Force #2, along Edge 3: Blizzard B: Pilot (Plt 2, Gnr 5)
    • Force #3, along Edge 4: Thunder Bird A: Pilot (Plt 1, Gnr 2)
    • Force #4, along Edge 4: Pit Viper A: Pilot (Plt 2, Gnr 7)
    • Force #5, along Edge 5: Death Wind A: Pilot (Pit 5, Gnr 8), Gunner (Gnr 5)
    • Force #6, along Edge 6: Epping A: Pilot (Plt 7, Gnr 1), Gunner A (Gnr 10), Gunner B (Gnr 9), Gunner C (Gnr 8)

Map

Do not use the standard map configuration for this scenario. The map is a strip four hexes long, with Edge 1 at the left end and Edge 4 at the right end (the exit edge). Edges 2 and 3 run along the top of the strip, and Edges 5 and 6 along the bottom, as numbered on the printed diagram (source page 26).

Special Rules

  1. Do not use the standard map configuration. Use the map configuration above.
  2. The Konrad Civil Defense Network has been thrown into disarray and can no longer effectively direct its widely dispersed interceptor starcraft. The Ptolemeans therefore search for the Colosian intruder using their own limited tactical scanners. To simulate random Ptolemean interception of the Drakar, this scenario is played in six discrete "encounter periods". Each encounter period is played as its own mini-scenario: the Drakar enters the playing surface, meets intercepting Ptolemeans, and tries to cross the map. When the Drakar exits along Edge 4, that encounter period ends and a new one begins at game turn 1 with the Drakar setting up again along Edge 1. Only Edge 4 may be exited, and then only by the Drakar. After six encounter periods, the scenario is complete.
  3. At the beginning of each encounter period, the Ptolemean player rolls 1D6 and matches the result against the six forces listed above. He takes the force shown by the die roll and sets it up along the indicated Edge, and play proceeds normally. If the Drakar has not exited from Edge 4 by the end of turn 8, the Ptolemean player may roll for another force to enter as a reinforcement along its assigned Edge at the beginning of turn 9. Additional reinforcement groups may be brought in the same way every other game turn after that (at the start of turns 11, 13, 15, and so on). Because the Ptolemean forces represent specific individual searching units, once a force is in play the same force may not appear again in the same encounter period. If a force called for by the die roll is already in play or has previously been destroyed, no new force is added at that time. If the roll at the beginning of an encounter period indicates that no starting force is taken, no Ptolemeans appear until (possibly) the beginning of turn 9.
  4. All accumulated damage and munition expenditure for all vessels carries over to subsequent encounter periods. Damage Control (if used at all) may only be used successfully once by each vessel during the entire scenario, not once per encounter period.

Victory Conditions

At the end of six encounter periods, the scenario is over and the Colosian player totals the TPVs of enemy fighters destroyed. He then applies these modifiers:

  • +50 points if the Drakar has a Drive value of 5 or more.
  • -50 points if the Drakar survives with a Drive value of 3 or less.
  • -100 points if the Drakar is destroyed or ends with Drive 0.
PointsResult
150+Decisive Colosian victory
100-149Marginal Colosian victory
50-99Draw
0-49Marginal Ptolemean victory
(-1) or lessDecisive Ptolemean victory

6.6 Broken on Seb's Anvil

Ptolemus vs Black Plague. Date: Imp 475:009. Location: High orbit over Seb's Anvil; Virnak system.

Forces

  • Black Plague player. Element from Boa Squadron, 4th Black Plague Fighter Wing. Set up first in Area G.
    • Thunder Bird A: Misha Bakoyinnan (Plt 9, Gnr 7, Luck 2)
    • Thunder Bird B: Pilot (Plt 7, Gnr 7, Luck 1)
  • Black Plague player. Element from Cobra Squadron, 4th Black Plague Fighter Wing. Set up second in Area B.
    • Sorensen A: Pilot (Plt 7, Gnr 6), Gunner (Gnr 8)
    • Sorensen B: Pilot (Pit 6, Gnr 5), Gunner (Gnr 7)
  • Ptolemean player. Elements from Khensu Squadron, 33rd Independent Ptolemean Fighter Wing. Set up third: Death Winds in Area D and Glaives in Area J.
    • Death Wind A: Pilot (Pit 7, Gnr 6, Luck 2), Gunner (Gnr 6)
    • Death Wind B: Pilot (Pit 6, Gnr 5), Gunner (Gnr 4)
    • Glaive A: Pilot (Plt 7, Gnr 6), Gunner (Gnr 8)
    • Glaive B: Pilot (Pit 4, Gnr 3), Gunner (Gnr 7)

Reinforcements

  • Black Plague player. Element from Asp Squadron, 4th Black Plague Fighter Wing. Enters on turn 3 along Edge 3.
    • Spirit Rider A: Pilot (Pit 8, Gnr 9, Luck 2)
    • Spirit Rider B: Pilot (Plt 7, Gnr 6)
  • Ptolemean player. Element from Atep Squadron, 33rd Independent Ptolemean Fighter Wing. Enters on turn 5 along Edge 4.
    • Blizzard A: D. Amenophis (Pit 10, Gnr 9, Luck 5)
    • Blizzard B: Pilot (Pit 8, Gnr 6)

Special Rules

  1. In this confused battle both fighter wings have lost their Battle Directors (the fleet tactical controllers who direct units to battle locations and clear free weapons use). Electromagnetic and neutrino jamming has also rendered every fighter's tactical scanners temporarily inoperative, and intership communication is virtually impossible. As a result, each fighter must identify a target before any weapon may be fired at it. To identify a target vessel, a fighter must end a completed Movement Phase within 2 hexes of it and then roll 1D10 with a result equal to or less than the spotting crewmember's Gnr value. Only one spotting attempt may be made by each individual crewman per game turn (so SMACs make one spotting roll and TMACs may make two). Spotting attempts by all pilots and gunners may be made in any order agreed by the players. Once a target is identified by a fighter, it remains identified by that fighter (but not automatically by other fighters on the same side) for the rest of the scenario, regardless of later separation. Players keep a side record of which enemy vessels each of their fighters has identified.
  2. Due to severe electromagnetic interference, roll 1D6 for every torpedo that has not reached its target by the end of a Movement Phase. On a roll of 1-3 the torp's guidance is scrambled and it is removed from the playing surface. Make these rolls at the end of every Movement Phase for all torps still in flight.
  3. Due to confusion, no torpedoes may be fired at by cannons or missiles during the scenario.
  4. The Black Plague Thunder Birds are armed only with 2 Mk10 torps each.

Victory Conditions

At the end of game turn 12, the scenario is over and both sides total the TPVs of enemy fighters destroyed. The Ptolemean player then applies these modifiers:

  • +20 points if Misha Bakoyinnan is killed or his fighter is destroyed.
  • -10 points for each Black Plague fighter that remains unidentified by a surviving Ptolemean vessel.

The Black Plague player's TPV kill total is subtracted from the Ptolemean player's modified total. Compare the result:

PointsResult
100+Decisive Ptolemean victory
60-99Marginal Ptolemean victory
0-59Draw
(-30) to (-1)Marginal Black Plague victory
(-31) or lessDecisive Black Plague victory

6.7 Death of a Hero

Ptolemus vs Colosians. Date: Imp 475:024. Location: High orbit over Hexad II; Hexad system.

Forces

  • Colosian player. Diamond Flight from Angel Squadron, 4155th Millennia Warrior TMAC Regiment. Set up first in Areas E and/or F.
    • Pharsii II A: Helmut Buchholz (Pit 9, Gnr 9, Luck 2); Gunner A (Gnr 9), Gunner B (Gnr 8)
    • Pharsii II B: Pilot (Plt 8, Gnr 6); Gunner A (Gnr 8), Gunner B (Gnr 6)
    • Pharsii II C: Pilot (Plt 7, Gnr 4, Luck 7); Gunner A (Gnr 7), Gunner B (Gnr 5)
    • Pharsii II D: Pilot (Plt 5, Gnr 3); Gunner A (Gnr 6), Gunner B (Gnr 5)
  • Ptolemean player. Flight from Hexad II Home Defense Wing "Gamma Six". Set up second along any Edge(s).
    • Glaive A: Pilot (Pit 7, Gnr 9), Gunner (Gnr 7)
    • Glaive B: Pilot (Pit 6, Gnr 7), Gunner (Gnr 6)
    • Glaive C: Pilot (Pit 5, Gnr 6), Gunner (Gnr 6)
    • Glaive D: Pilot (Plt 4, Gnr 5), Gunner (Gnr 5)

Reinforcements

  • Ptolemean player. Element from Hexad II Home Defense Wing "Gamma Two". Enters by Special Rule 1 along any Edge(s).
    • Blizzard A: Pilot (Pit 2, Gnr 5)
    • Blizzard B: Pilot (Pit 1, Gnr 4)

Special Rules

  1. The Ptolemean player may call for reinforcements (the two Blizzards) during the course of the scenario. At the beginning of any game turn, the Ptolemean player may roll 1D6. The result is the number of game turns before the reinforcements arrive. Example: at the beginning of turn 8 the reinforcement die roll is made and the result is 4. The Blizzards enter at the beginning of turn 12, the last turn of the game.
  2. If the roll in Special Rule 1 indicates that the reinforcements arrive after the end of the game (after turn 12), they do not appear in the scenario, but they are still considered to have been called for for Victory Condition purposes.
  3. Helmut Buchholz is a heavily decorated and inspiring leader. Crewmembers of friendly vessels within 2 hexes of Buchholz's Pharsii II have their Gnr values temporarily raised by 1. This effect is lost when friendlies are out of the 2-hex radius. Helmut does not affect his own crew's skills.

Victory Conditions

At the end of game turn 12, the scenario is over and the Ptolemean player totals the TPVs of enemy fighters destroyed. He then applies these modifiers:

  • +50 points if Helmut Buchholz is killed or his fighter is destroyed.
  • +40 points if no Ptolemean vessels are destroyed.
  • -40 points if the reinforcements are called for.
PointsResult
200+Decisive Ptolemean victory
110-199Marginal Ptolemean victory
80-109Draw
0-79Marginal Colosian victory
(-1) or lessDecisive Colosian victory

6.8 A Case of Overkill

Ptolemus vs Behemoth. Date: Imp 475:035. Location: Low orbit over Necromus; Dios Provanis system.

Forces

  • Ptolemean player. Captured Ptolemean Evacuation Shuttles. Set up first in Area E.
    • Shryak Shuttle A: Pilot (Plt 1)
    • Shryak Shuttle B: Pilot (Pit 1)
  • Behemoth player. Guard Elements from Dominator Squadron, 1st Aerial Atrocity Regiment. Set up second in Areas E and/or F.
    • Spirit Rider A: Pilot (Plt 9, Gnr 8, Luck 2)
    • Spirit Rider B: Pilot (Pit 5, Gnr 5)
    • Thunder Bird A: Pilot (Pit 8, Gnr 7, Luck 3)
    • Thunder Bird B: Pilot (Plt 7, Gnr 6)
    • Revenge A: Pilot (Pit 5, Gnr 1), Gunner (Gnr 9)
    • Revenge B: Pilot (Plt 4, Gnr 1), Gunner (Gnr 8)
  • Ptolemean player. Rescue Group from the Charioteers, 102nd Ptolemean Carrier Wing. Set up third along any Edge(s).
    • Death Wind A: Pilot (Plt 8, Gnr 5), Gunner (Gnr 8)
    • Death Wind B: Pilot (Pit 7, Gnr 6), Gunner (Gnr 4)
    • Glaive A: Pilot (Pit 6, Gnr 7), Gunner (Gnr 9)
    • Glaive B: Pilot (Pit 5, Gnr 5), Gunner (Gnr 5)

Special Rules

  1. The shuttles hold the Ptolemean hostages and took significant damage during their capture. Mark off 21 hits on Shryak Shuttle A and 25 hits on Shryak Shuttle B. Do not roll for critical hits taken. Neither shuttle has any effective weapon system remaining, so neither may make attacks during the scenario. They have no decoys available. The Ptolemean player places and controls the shuttles.
  2. The Behemoth player may not fire cannons or torps at either Shryak until one of the following occurs: (i) one of the shuttles moves; (ii) three of the Behemoth player's vessels are destroyed; or (iii) four of the Behemoth player's vessels have each taken at least five hits of damage.
  3. Only Ptolemean vessels may exit the playing surface, and then only from Edge 4. Ptolemean fighters from the Charioteers may not exit until at least one Behemoth fighter has been destroyed.
  4. The Revenge fighters are armed with 4 Standard Mk50 torps each and carry no other torps.
  5. Neither the Spirit Riders nor the Thunder Birds are armed with any torps.

Victory Conditions

At the end of game turn 10, the scenario is over and the Ptolemean player totals victory points:

  • +50 points for each Shryak exited.
  • +10 points for each Ptolemean fighter exited.
  • +10 points for each Revenge destroyed.
  • +5 points for each Spirit Rider or Thunder Bird destroyed.
  • -3 points for each hit of damage scored against a Shryak Shuttle during the scenario.
  • -20 points for each Shryak Shuttle destroyed (scored in addition to the damage points above).
PointsResult
100+Decisive Ptolemean victory
50-99Marginal Ptolemean victory
30-49Draw
0-29Marginal Behemoth victory
(-1) or lessDecisive Behemoth victory

6.9 Caught in Satan's Fulcrum

Colosians vs Ptolemus. Date: Imp 475:081. Location: Approach to Orbital Station Iceman over Hexad III; Hexad system.

Forces

  • Ptolemean player. Partial Flight from Pole Star Squadron, 3447th Ptolemean Interceptor Group. Set up first (placed by the Colosian player) in Area D.
    • Blizzard A: Pilot (Plt 7, Gnr 3)
    • Blizzard B: Pilot (Pit 3, Gnr 5)
    • Blizzard C: Pilot (Pit 3, Gnr 2)
  • Ptolemean player. Element from Spica Squadron, 3447th Ptolemean Interceptor Group. Set up second (placed by the Colosian player) in Area C.
    • Thunder Bird A: Pilot (Plt 2, Gnr 3)
    • Thunder Bird B: Pilot (Plt 1, Gnr 1)
  • Ptolemean player. Member of Nadir Squadron, 3447th Ptolemean Interceptor Group. Set up third (placed by the Colosian player) in Area J.
    • Glaive A: Pilot (Plt 5, Gnr 6), Gunner (Gnr 5)
  • Colosian player. Various Interceptors from Satan's Fulcrum, 139th Colosian Carrier Wing. Set up fourth along Edge 4.
    • Hell Bender A: Vladimir Gregor (Plt 8, Gnr 8)
    • Hell Bender B: Pilot (Plt 5, Gnr 6)
    • Salamander A: Pilot (Plt 6, Gnr 6), Gunner (Gnr 6)
    • Salamander B: Pilot (Plt 5, Gnr 5), Gunner (Gnr 7)

Reinforcements

  • Colosian player. Interceptors from Satan's Fulcrum, 139th Colosian Carrier Wing. Enters on turn 2 along Edge 4.
    • Hell Bender C: Pilot (Plt 6, Gnr 5)
    • Hell Bender D: Pilot (Plt 5, Gnr 5)
  • Ptolemean player. Robotic Suicide Shuttle. Enters on turn 3 along Edge 4 (see Special Rule 3).
    • Shryak Shuttle: Pilot (Automated)
  • Colosian player. Gunboat from Satan's Fulcrum, 139th Colosian Carrier Wing. Enters on turn 4 along Edge 4.
    • Drakar A: Pilot (Plt 4, Gnr 5); Gunner A (Gnr 4), Gunner B (Gnr 5), Gunner C (Gnr 6), Gunner D (Gnr 4)

Special Rules

  1. The Colosian player places all starting forces in the game.
  2. Though in disarray, some Ptolemeans may still press on with their mission to attack Orbital Station Iceman. After game turn 5, one Ptolemean fighter may exit the playing surface per turn. Only Ptolemean starcraft may exit the map, and then only along Edge 2, the direction in which the Orbital Station lies.
  3. Special robotic suicide shuttles packed with explosives were part of the plan to attack Orbital Station Iceman. On turn 3 the Ptolemean player brings on a modified Shryak Shuttle. It has no crew, carries no weapons, and is restricted in its path of flight. During any Movement Phase it may face only directions 6, 1 and/or 2. It must use all of its available movement points every Movement Phase, and it may make only one turn (facing change) per hex entered. It may not dodge torps or use any other anti-torp measure. Its sole purpose in this scenario is to cross the playing surface and exit along Edge 2. It does not count against the limit on Ptolemean fighters that may exit the map under Special Rule 2.

Victory Conditions

When all Ptolemean vessels have been destroyed and/or have exited the playing surface, the scenario is over and the Colosian player totals victory points:

  • +10 points for each Ptolemean fighter or shuttle destroyed.
  • +5 points for each Ptolemean fighter exited with a Drive value of 6 or less.
  • +1 point for each hit of damage inflicted on the shuttle.
  • -2 points for each hit of damage remaining on the shuttle if it exits.
  • -4 points for each Colosian crewman killed without his fighter being destroyed.
  • -10 points for each Ptolemean fighter exited with a Drive value of 10 or more.
  • -20 points for each Colosian vessel destroyed.
PointsResult
100+Decisive Colosian victory
50-99Marginal Colosian victory
40-49Draw
30-39Marginal Ptolemean victory
-(29) points, as printed (read as 29 or fewer)Decisive Ptolemean victory

Note: the printed bottom bracket of this table reads "-(29) points" in the source; it is transcribed as printed. It is the lowest tier and is read as 29 or fewer.

6.10 Running Interference

Behemoth vs Ptolemus. Date: Imp 475:099. Location: Approach to Beta Kynon IV; Beta Kynon system.

Forces

  • Behemoth player. Flight from Grave Squadron, 89th Behemoth Heavy Interceptor Group. Set up first along Edge 1.
    • Sorensen III A: Pilot (Pit 7, Gnr 8), Gunner (Gnr 8)
    • Sorensen III B: Pilot (Plt 6, Gnr 6), Gunner (Gnr 7)
    • Sorensen III C: Pilot (Plt 5, Gnr 6), Gunner (Gnr 6)
  • Ptolemean player. Flight from Starman Squadron, 10th Provisional Beta Kynon Fighter Wing. Set up second along Edge 3.
    • Seraph A: Pilot (Pit 8, Gnr 7), Gunner (Gnr 10)
    • Seraph B: Pilot (Pit 6, Gnr 6), Gunner (Gnr 8)
    • Seraph C: Pilot (Pit 6, Gnr 2), Gunner (Gnr 6)
    • Seraph D: Pilot (Pit 5, Gnr 5), Gunner (Gnr 5)

Reinforcements

Behemoth player. Elements from Reaper Squadron, 89th Behemoth Heavy Interceptor Group. Enter as per Special Rule 3, along Edge 1.

  1. Pharsii II A: Gyrlin Arganza (Plt 7, Gnr 8, Luck 7); Gunner A (Gnr 8), Gunner B (Gnr 5)
  2. Pharsii II B: Pilot (Pit 5, Gnr 6); Gunner A (Gnr 7), Gunner B (Gnr 5)
  3. Epping A: Pilot (Pit 5, Gnr 4); Gunner A (Gnr 8), Gunner B (Gnr 7), Gunner C (Gnr 6)
  4. Epping B: Pilot (Pit 4, Gnr 3); Gunner A (Gnr 7), Gunner B (Gnr 7), Gunner C (Gnr 5)

Special Rules

  1. Beta Kynon is a hot Type A sub-giant blue star with severe solar flare activity. Just before the Missile/Torp Launch Phase of each game turn (after any reinforcements arrive), roll 1D10 for each vessel on the playing surface and consult the results:
    • 1 = Flight Controls Jam (the vessel flies straight at full speed this turn).
    • 2 = Cannon Weapon System Fried (eliminate one remaining cannon weapon system at random).
    • 3 = Missile Targeting System Malfunctions (may not fire one random remaining missile launcher this turn).
    • 4 = Torp Launch Mechanism Shorts Out (all remaining torp loads jettison harmlessly).
    • 5 = Crewman Weakened by Radiation Sickness (a random crewman has his skill level(s) drop by 1, to a minimum of 1).
    • 6-10 = No effect.
  2. Again due to severe solar radiation, roll 1D6 for every torp that has not reached its target by the end of a Movement Phase. On a roll of 1-3 the torp's guidance is scrambled and it is removed from the playing surface. Make these rolls at the end of every Movement Phase for all torps in flight, after normal jamming and decoy attempts.
  3. The Behemoth reinforcements are disorganized and enter the battle area at random. Starting with game turn 2, the Behemoth player rolls 1D6 at the beginning of each turn. If the result matches the number (1-4) of a reinforcement that has not yet entered (or was not eliminated by a previous roll of 6), that reinforcement appears that turn. A result of 5 means no reinforcement appears that turn. A result of 6 means no reinforcement appears that turn, and one remaining available reinforcement will never appear; randomize which one.
    • Example: at the beginning of turn 2 the Behemoth player rolls a 5 and nothing appears. On turn 3 he rolls a 1, and Pharsii II A appears on Edge 1. On turn 4 he rolls another 1; nothing appears, since that reinforcement has already entered. On turn 5 he rolls a 6; nothing appears, and one of the three remaining reinforcements (numbers 2, 3 or 4) will never make it to the playing surface. A randomized selection indicates reinforcement #3, Epping A, has no chance of entering, so later rolls of 3 produce nothing.
  4. Any vessel may exit the map from any Edge. Once exited, whether voluntarily or because of a "Flight Controls Jam" result, a starcraft may not re-enter.

Victory Conditions

The scenario continues until the end of the game turn in which only one player's vessel(s) remain on the playing surface, regardless of possible subsequent reinforcements. The game then ends and both players total the TPVs of all enemy vessels destroyed. Each player then modifies his own total:

  • -10 points for each friendly fighter that exited the map.
  • -5 points for each dead crewman in a surviving or exited friendly fighter.
  • -2 points for each individual crewman weakened by radiation sickness (see above).

The Ptolemean player's total is subtracted from the Behemoth player's total. Compare the result:

PointsResult
70+Decisive Behemoth victory
20-69Marginal Behemoth victory
(-20) to 19Draw
(-70) to (-21)Marginal Ptolemean victory
(-71) or lessDecisive Ptolemean victory

6.11 Reconnaissance Flight

Ptolemus vs Colosians. Date: Imp 475:112. Location: Outer reaches of the Lebanstar system.

Forces

  • Colosian player. Flight from Javelin Squadron, 2175th Millennia Warrior Medium SMAC Regiment. Set up first in Areas A and/or B. All must face direction 6.
    1. Hell Bender A: Pietor Gies (Pit 10, Gnr 9, Luck 6)
    2. Hell Bender B: Pilot (Pit 9, Gnr 8)
    3. Hell Bender C: Pilot (Pit 7, Gnr 7)
    4. Hell Bender D: Pilot (Pit 5, Gnr 2)
  • Colosian player. Elements from Shot Squadron, 2175th Millennia Warrior Medium SMAC Regiment. Set up second in Areas B and/or C. All must face direction 6. 5. Night Hawk A: Pilot (Pit 8, Gnr 8, Luck 2) 6. Night Hawk B: Pilot (Pit 5, Gnr 6) 7. Teal Hawk A: Pilot (Pit 7, Gnr 2), Gunner (Gnr 7) 8. Teal Hawk B: Pilot (Pit 4, Gnr 6), Gunner (Gnr 5)
  • Ptolemean player. Reconnaissance Element from Lake Tem Squadron, 1241st Home Defense Wing. Set up third in Area I.
    • Death Wind A: Pilot (Pit 8, Gnr 7), Gunner (Gnr 8)
    • Death Wind B: Pilot (Pit 7, Gnr 3), Gunner (Gnr 6)

Special Rules

  1. The Ptolemean Death Winds are special reconnaissance craft. Eliminate all of their torp loads. Instead they carry special sensor equipment that records the number and identity of enemy vessels for victory condition purposes. To scan an enemy vessel, a Movement Phase must end with a Death Wind within 2 hexes of an enemy vessel. The scan is automatic. Each Death Wind may scan up to 2 enemy vessels per game turn (the Ptolemean player's choice if more than two can be scanned). Keep a side record of which Death Wind has scanned which enemy vessels. A single enemy vessel may be scanned by both Death Winds.
  2. The Millennia Warrior starcraft are powered down at the start of the scenario and are not expecting the Ptolemean recon units. No vessel from the 2175th may move or fire any weapons (cannons or torps) until its activation roll has been made. At the end of every game turn, the Millennia Warrior player rolls a number of "activation D8s" equal to the number of his vessels that were scanned by the Ptolemean player during that turn, always rolling a minimum of 1D8 per turn. The results are the identities (the forces numbered above) of the Millennia Warrior vessels activated at the beginning of the following game turn. If an activation result indicates a vessel that has already been activated, no new vessel is activated by that roll. Once activated, a vessel may move and fire normally.
  3. The Death Winds should exit the map before the end of the scenario. They may exit only from Edge 3. No other vessels may exit the map.

Victory Conditions

At the end of game turn 10, the scenario is over and the Ptolemean player totals points:

  • +10 points for each Death Wind exited from the map with a Drive value of 8 or more.
  • +5 points for each individual enemy vessel scanned by an exited Death Wind (a single vessel is not counted twice if scanned by both Death Winds).
  • +2 points for each enemy vessel activated by the beginning of game turn 6.
PointsResult
70+Decisive Ptolemean victory
40-69Marginal Ptolemean victory
30-39Draw
17-29Marginal Colosian victory
0-16Decisive Colosian victory

6.12 All Foes Meet

Ptolemus vs Behemoth vs Colosians. Date: Imp 475:187. Location: Outer reaches of the Lebanstar system.

Forces

  • Ptolemean player. Mixed units from Great Isthmus Squadron, 1241st Home Defense Wing. Set up alternately with the Colosian forces as per Special Rule 3.
    • Death Wind A: Pilot (Plt 6, Gnr 5), Gunner (Gnr 2)
    • Blizzard A: Pilot (Pit 4, Gnr 3)
    • Epping A: Pilot (Plt 2, Gnr 1); Gunner A (Gnr 6), Gunner B (Gnr 4), Gunner C (Gnr 5)
    • Shryak Shuttle A: Pilot (Plt 1, Gnr 6), Gunner (Gnr 2)
  • Colosian player. Elements from Discus and Javelin Squadrons, 2175th Millennia Warrior Medium SMAC Regiment. Set up alternately with the Ptolemean forces as per Special Rule 3.
    • Kosmos A: Pilot (Plt 8, Gnr 8, Luck 5)
    • Kosmos B: Pilot (Plt 6, Gnr 7, Luck 2)
    • Hell Bender A: Pilot (Plt 7, Gnr 9, Luck 3)
    • Hell Bender B: Pilot (Pit 6, Gnr 5, Luck 7)
  • Behemoth player. Advance Fighters from Overkill, the 1st Aerial Atrocity Regiment. Set up last along Edge 4 (as per Special Rule 2 if this is a two-player game).
    • Pharsii II A: Pilot (Pit 5, Gnr 3); Gunner A (Gnr 8), Gunner B (Gnr 3)
    • Thunder Bird A: Pilot (Pit 4, Gnr 3, Luck 2)
    • Thunder Bird B: Pilot (Pit 3, Gnr 5)
    • Thunder Bird C: Pilot (Plt 2, Gnr 2)

Special Rules

  1. This scenario is best played as a three-player game: one Ptolemean, one Colosian (controlling the Millennia Warriors) and one Behemoth player. In a three-player game the initiative procedure is modified. Each player rolls the initiative die and adds the Pit value of his best pilot; reroll ties. During the Movement Phase the player with the worst initiative score moves one fighter first, the player with the second-worst score moves one fighter second, and the initiative winner moves one of his fighters third. Movement proceeds in this order, and the initiative winner may always hold back a fighter for the last move of the Phase. Any player may fire at any other player he desires.
  2. If played as a two-player game, control the Behemoth forces as follows. At the beginning of every game turn, roll 1D6 for each Behemoth fighter on the map. An even result means the Ptolemean player controls that fighter for the turn; an odd result means the Colosian player controls it. Control is rerolled every turn, so both players may control the same fighter at different times. The first control rolls of the game also determine who sets up which Behemoth fighters. Behemoth fighters may not attack their own forces, only those of the Ptolemeans or Colosians. (Deliberately setting up a Behemoth fighter as a kill for one's own craft is against the spirit of the scenario.)
  3. The Ptolemean and Millennia Warrior forces alternate their set-up at the beginning of the game. The Ptolemean player must place one vessel in each of Areas A, C, H and J; the Colosian player must place one vessel in each of Areas B, D, G and I. Each player rolls 1D10, and the lowest roller places one of his vessels first. Set-up then alternates between the two players until all eight craft are on the map. No vessel may be placed within 5 hexes of another vessel already on the map. After this alternating set-up, the Behemoth forces are deployed.
  4. The Behemoth fighters suffer from Poor Mechanical Reliability (see Section F.0 in Rules Annex #1).
  5. The Ptolemean/Colosian battle had been going on for some time before the Behemoth forces arrived. To represent this, each Ptolemean and Colosian vessel starts the game with 2D4 hits already marked off on its damage track. The Epping takes these hits in a randomly determined quadrant. Critical hits taken have no effect.

Victory Conditions

At the end of game turn 10, the scenario is over and each player totals the TPVs of enemy craft destroyed by his own force's fire (in a two-player game, kills made by Behemoth forces are ignored).

  • If a player has accumulated at least a 2-to-1 ratio of TPVs over his nearest competitor, he has won a Decisive victory.
  • If the ratio of TPVs is at least 1.5-to-1, the high-scoring player has won a Marginal victory.
  • All other results are Draws.

7.0 Campaigns

This section details two complete campaigns. The first plays the scenarios in Section 6.0 in chronological order. The second covers two opposing fighter wings during one heavy day of fighting over Kneset's World in the Lebanstar system.

7.1 The Chronological Campaign

This campaign is designed for two players, or two groups of players. One side always controls the Ptolemean forces, and the other side plays the invaders: Colosians, Millennia Warriors fighting for the Colosians, Dneprodzerkutsk Black Plague members, or Behemoth Warband members.

Players fight the scenarios from Section 6.0 in order, starting with "Opening Moves" (6.1) and ending with "All Foes Meet" (6.12).

Victory is based on points. Decisive victories are worth 5 points to the side that wins them. Marginal victories are worth 2 points to the side that wins them. Draws are worth 0 points. At the end of the campaign, each side totals the points it has earned through the twelve scenarios. The side with the highest total wins. To determine the decisiveness of the campaign, subtract the lower point total from the larger and compare the difference:

DifferenceResult
60 pointsYou are the ultimate tactical master.
25-50 pointsThe opposing side is so resoundingly defeated that it loses its Provincial status, is expelled from the Imperial Senate, and the Emperor takes all of its lands and titles. You gain a significant slave population from your foes.
15-24 pointsYour opponents have displayed tactical buffoonery. Imperial disfavor is showered upon them with regularity, and they have definitely lost this war. You are hailed across the Empire as a force to be reckoned with.
10-14 pointsYou have achieved victory in this war. As a concession of defeat, your opponents forfeit three star systems and pay restitution for the next 60 years.
5-9 pointsYou have weaseled out a victory from your opponent. Your efforts are credited for having brought about the ultimate end of the opposition.
2-4 pointsA close contest of man and machine. The space battles did not decide this war.
0-1 pointThis campaign was too close to call. The course of the war was decided on another front. Both sides fought well.

7.2 Mighty Thunder vs Hope's Constellation

This campaign covers a full day of combat between two fighter wings over Kneset's World, as the height of the Lebanstar fighter battles approaches. The Colosian unit is the 20th Colosian Strike Fighter Wing ("Mighty Thunder"). The Ptolemean unit is the 1241st Home Defense Wing ("Hope's Constellation"). Both wings are reduced in strength and many fighters are down for maintenance, so full squadrons are not available. See the force listings below.

The campaign is played as six scenarios, described below in abbreviated format. Before the campaign begins, each player secretly allocates his available forces to the six scenarios. A player may allocate any of his fighters to an individual scenario, but each fighter may be allocated to only one scenario. A player may allocate no fighters to a scenario, forfeiting any possible victory points in exchange for placing more forces in another scenario. Starcraft from no more than two different squadrons may be allocated by a player for use in a single scenario.

Once forces are allocated, the games are played in order, from scenario 1 to scenario 6. Victory points are accumulated in each scenario and totalled by each side at the end of the campaign to find the winner.

Scenario 1: Fighter Sweep. Date: Imp 475:020 0300 hours. Location: High orbit over Kneset's World.

  • Scenario Parameters: Ptolemean forces set up first along Edge 1; Colosians set up second along Edge 3. Starcraft from both sides may exit the map from their respective Edges after game turn 10. The scenario ends when vessel(s) from only one side remain on the map.
  • Victory Points: Players score 4 points for each enemy vessel destroyed and 2 points for each enemy vessel reduced to less than half of its starting Drive number. If a side flies the scenario unopposed (the enemy commits no forces to the battle), it scores 8 points.

Scenario 2: Penetration. Date: Imp 475:020 0410 hours. Location: High orbit over Kneset's World.

  • Scenario Parameters: The Ptolemean forces set up first in Areas D, E, F and/or G. The Colosians set up second along Edge 3. Colosian starcraft (only) may exit the map along Edge 1, but only on game turn 8 or later. The scenario ends when no Colosian vessels remain on the playing surface.
  • Victory Points: Players score 4 points for each enemy vessel destroyed and 2 points for each enemy vessel reduced to less than half of its starting Drive number. The Colosian player scores 2 points for each Hell Bender or Revenge that exits the map with a Drive number of 10 or more. No other ship type may score these exit points.

Scenario 3: Stand-off Attack. Date: Imp 475:020 0425 hours. Location: Low orbit over Kneset's World.

  • Scenario Parameters: The Ptolemean forces set up first along Edge 1. The Colosians set up second along Edge 3. In addition to the starcraft assigned to this scenario, the Colosian player may add one extra vessel to his starting forces: it must be a starcraft that exited the map during Scenario 2. All damage and munition expenditure is carried over from the previous scenario for this one bonus ship. Colosian vessels may exit the map along Edge 3 at any time. A Ptolemean troop transport (the subject of the Colosian attack) is just off Edge 1 after game turn 8. The scenario ends when no Colosian vessels remain on the map.
  • Victory Points: The Ptolemean player scores 4 points for each Colosian vessel destroyed and 2 points for each Colosian vessel reduced to less than half of its starting Drive number. The Colosian player scores 1/2 point for each Mk30 or Mk50 torpedo launched at the troop transport from Area B on game turn 8 or later. Such torps are launched during the Torp Launch Phase and removed from the map immediately; the attack on the transport is abstracted.

Scenario 4: Counter-Stroke. Date: Imp 475:020 0700 hours. Location: High orbit over Kneset's World.

  • Scenario Parameters: Colosian forces set up first along Edge 3, Colosians set up second along Edge 1. (Transcribed as printed. The second set-up entry reads "Colosians" in the source, which appears to be a misprint for the Ptolemeans, who are the defenders in this scenario. Players should confirm against the printed book.) Starcraft from both sides may exit the map from their respective Edges after game turn 10. The scenario ends when vessel(s) from only one side remain on the map.
  • Victory Points: Players score 4 points for each enemy vessel destroyed and 2 points for each enemy vessel reduced to less than half of its starting Drive number. If a side flies the scenario unopposed, it scores 8 points.

Scenario 5: Screening Action. Date: Imp 475:020 1030 hours. Location: Low orbit over Kneset's World.

  • Scenario Parameters: Colosian forces set up first in Areas H, I and/or J. Ptolemeans set up second along Edge 1. In addition to the starcraft assigned to this scenario, the Ptolemean player may add one extra vessel to his starting forces: it must be a starcraft that exited the map during Scenario 4. All damage and munition expenditure is carried over from the previous scenario for this one bonus ship. No forces may exit the map. The scenario ends when vessel(s) (with Drive greater than 0 and live pilots) from only one side remain on the playing surface.
  • Victory Points: The Colosian player scores 4 points for each Ptolemean vessel destroyed and 2 points for each Ptolemean vessel reduced to less than half of its starting Drive number. The Ptolemean player scores points based on the number of game turns it takes to "render ineffective" all of the Colosian forces. A vessel is rendered ineffective if it is destroyed, reduced to Drive 0, or its pilot is killed. If the Ptolemean succeeds by the end of turn 5 he scores 30 points; by the end of turn 10, 20 points; by the end of turn 15, 10 points; thereafter, 5 points. If the Colosian allocates no forces to this scenario, the Ptolemean automatically scores 30 points. If the Ptolemean allocates no forces to this scenario, the Colosian automatically scores 8 points.

Scenario 6: Final Melee. Date: Imp 475:020 1900 hours. Location: High orbit over Kneset's World.

  • Scenario Parameters: Colosian forces set up first in Areas G and/or J. Ptolemeans set up second in Areas A and/or D. No forces may exit the map. The scenario ends when vessels from only one side remain on the playing surface.
  • Victory Points: Players score 4 points for each enemy vessel destroyed and 2 points for each enemy vessel reduced to less than half of its starting Drive number. If a side flies the scenario unopposed, it scores 8 points.

Ptolemean Forces: 1241st Home Defense Wing, as of Imp 475:020

  • Capital Squadron. Blizzard A: Dendra Yasut (Plt 8, Gnr 8, Luck 1). Blizzard B: Nargol Mia (Plt 5, Gnr 6). Blizzard C: Ayha Aup (Plt 3, Gnr 5). Blizzard D: Meker Teptit (Plt 1, Gnr 2).
  • Khanut Sea Squadron. Thunder Bird A: Anjibra Seskaf (Plt 7, Gnr 8, Luck 2). Thunder Bird B: Khemennu Netherit (Plt 3, Gnr 2). Thunder Bird C: Ayam Sayd Abau (Plt 2, Gnr 2).
  • Lake Tem Squadron. Death Wind A: Bib Wadji (Plt 6, Gnr 9, Luck 7), Gunner (Gnr 9). Death Wind B: Teb Tebenaht (Plt 5, Gnr 7), Gunner (Gnr 6). Death Wind C: Nun Tebenaht (Plt 4, Gnr 4), Gunner (Gnr 3). Glaive A: Uher Anan (Plt 6, Gnr 5), Gunner (Gnr 7). Glaive B: Parthal Tchaiu (Plt 2, Gnr 3), Gunner (Gnr 7).
  • Great Isthmus Squadron. Seraph A: Bannar Kendu (Plt 5, Gnr 5), Gunner (Gnr 6). Seraph B: Bag Kamraya (Plt 1, Gnr 2), Gunner (Gnr 5). Epping A: Kher Shesh (Plt 3, Gnr 1), Gunner A (Gnr 7), Gunner B (Gnr 5), Gunner C (Gnr 4).

Colosian Forces: 20th Colosian Strike Fighter Wing, as of Imp 475:020

  • Bolt Squadron. Kosmos A: Keri Tagtmeyer (Plt 10, Gnr 9, Luck 5). Kosmos B: Max Gerishimov (Plt 9, Gnr 8, Luck 4). Kosmos C: Camden Selig (Plt 8, Gnr 8, Luck 2). Kosmos D: Sool Seftel (Plt 6, Gnr 7).
  • Crusher Squadron. Kosmos E: Herm Zydanowicz (Plt 10, Gnr 8, Luck 7). Kosmos F: Sonjay Shwartz (Plt 8, Gnr 9, Luck 3). Kosmos G: Marion Pechous (Plt 8, Gnr 5).
  • Hurler Squadron. Hell Bender A: Mac Wroblewski (Plt 9, Gnr 5, Luck 4). Hell Bender B: Tamov Reitz (Plt 8, Gnr 4). Hell Bender C: Harris Phan (Plt 7, Gnr 6). Revenge A: Geoff McMallietski (Plt 7, Gnr 1), Gunner (Gnr 9). Revenge B: Jerrel Jerz (Plt 6, Gnr 1), Gunner (Gnr 7).
  • Shock Provisional Squadron. Salamander A: Tasha Liebetter (Plt 8, Gnr 6, Luck 8), Gunner (Gnr 5). Salamander B: Sondra Lefkowitz (Plt 4, Gnr 7), Gunner (Gnr 8). Drakar A: Marco Shang (Plt 3, Gnr 5); Gunner A (Gnr 6), Gunner B (Gnr 8), Gunner C (Gnr 9), Gunner D (Gnr 5).

8.0 Starcraft Inventory and Nomenclature

Six new starfighters are introduced in Overkill: The Ptolemean Wars. They are listed in order of increasing tonnage. The commentary on each design is not transcribed.

Imperial Transtar 1010 series E "Blizzard"

  • Crew: 1. Mass: 150 tons. Armor: Crystanium with belt.
  • Maneuvering Thrust: 0.156 km/s/s. Translight Capability: None. Atmospheric Capability: Full.
  • Armaments: 1 x Mk10 Disruptorgun; 4 x Mk10 Torp Loads.

Ironhorse F/S 11-a "Hell Bender"

  • Crew: 1. Mass: 300 tons. Armor: Crysteel with belt.
  • Maneuvering Thrust: 0.142 km/s/s. Translight Capability: None. Atmospheric Capability: Full.
  • Armaments: 1 x Mk20 Meld Laser; 1 x Mk20 Autocannon (Ammo: 16,000 rounds); 2 x Mk9 Pulse Lasers; 2 x Mk30 Torp Loads.

Caladyne Industries BUUR-3 (export) "Kosmos"

  • Crew: 1. Mass: 250 tons. Armor: Crystanium with belt.
  • Maneuvering Thrust: 0.168 km/s/s. Translight Capability: None. Atmospheric Capability: Full.
  • Armaments: 1 x Mk9 Minigun (Ammo: 18,000 rounds); 1 x Missile Launcher (Magazine: 10 missiles).

Jasper Machines Y910a G1/U1 "Glaive"

  • Crew: 2. Mass: 900 tons. Armor: Reinforced Crysteel.
  • Maneuvering Thrust: 0.119 km/s/s. Translight Capability: None. Atmospheric Capability: None.
  • Armaments: 1 x Mk10 Plazgun; 2 x Mk10 Splatterguns; 1 x Protobolt Projector (Ammo: 2 protobolts); 2 x Missile Launchers (Magazine: 10 missiles each); 1 x Mk40 Torp Load.

Delta Combine PKM-221 "Death Wind"

  • Crew: 2. Mass: 400 tons. Armor: Crystanium with belt.
  • Maneuvering Thrust: 0.140 km/s/s. Translight Capability: None. Atmospheric Capability: Full.
  • Armaments: 1 x Mk15 Ion Ram; 2 x Mk10 Splatterguns; 1 x Mk10 Minigun (Ammo: 24,000 rounds); 4 x Mk20 Torp Loads.

Krote-Khol Systems SFX20-d "Drakar" (gunboat)

  • Crew: 5. Mass: 1000 tons. Armor: Crysteel Double Hull.
  • Maneuvering Thrust: 0.078 km/s/s. Translight Capability: None. Atmospheric Capability: None.
  • Armaments: 1 x Heavy Plazgun; 1 x Railrepeator (Ammo: 4000 rounds); 6 x Mk10 Pulse Lasers; 2 x Missile Launchers (Magazine: 9 missiles each); 2 x Mk10 Torp Loads.

8.1 Critical Hit Charts for the New Starcraft Displays

Each display carries a critical hit chart. Results are rolled on 1D10 unless stated. The Drakar's four quadrant charts follow the Gunboat rules in Annex Section C.

Blizzard (1D10)

  1. Shields damaged. Reduce Defensive Value by 2.
  2. Evade Thrusters hit. Reduce Defensive Value by 4.
  3. Major structural damage inflicted. Blizzard takes 1D4 more hits.
  4. Hull compromised. Reduce Defensive Value by 5.
  5. Electronic Warfare knocked out. Blizzard may no longer jam torps. Reduce Defensive Value by 3.
  6. Engines damaged. Blizzard reduced to a Drive value of 1. Reduce Defensive Value by 6.
  7. Torp Loads jettison. Remove any remaining torp loads.
  8. Pilot dazed. Blizzard may not move or fire until after the next game turn.
  9. Pilot killed. Blizzard may perform no further actions. Defensive Value drops to 5.
  10. Reactor hit. A blizzard of scrap metal is all that remains.

Kosmos (1D10)

  1. Shields damaged. Reduce Defensive Value by 2.
  2. Missile Launcher jams momentarily. Missiles may not be fired until after the next game turn.
  3. Minigun jams momentarily. Minigun may not be fired until after the next game turn.
  4. Forward hull cracks. Reduce Defensive Value by 3 and mark off 3 more hits.
  5. Electronic Warfare knocked out. Kosmos may no longer jam torps. Reduce Defensive Value by 4.
  6. One engine sputters. Reduce current Drive value by 3 until after the next game turn.
  7. One engine destroyed. Reduce current Drive value by half, ignoring fractions. Reduce Defensive Value by 3.
  8. Pilot dazed. Kosmos may not move or fire until after the next game turn.
  9. Pilot killed. Kosmos may perform no further actions. Defensive Value drops to 5.
  10. Reactor detonates. The destroyed vessel erupts in a flash.

Hell Bender (1D10)

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Meld Laser targeting damaged. Modify Meld Laser To Hit attempts by -3.
  3. Pulse Lasers lose power. Pulse Lasers may not be fired until after the next game turn.
  4. Minor hull breach inflicted. Reduce Defensive Value by 2.
  5. Electronic Warfare knocked out. Hell Bender may no longer jam torps. Reduce Defensive Value by 2.
  6. Torp Loads jettison harmlessly. Remove Hell Bender's torp loads.
  7. Engines sputter. Hell Bender may only use 3 movement points next game turn.
  8. Pilot dazed. Hell Bender may not move or fire until after the next game turn.
  9. Pilot killed. Hell Bender may perform no further actions. Defensive Value drops to 5.
  10. Reactor explodes. Hell Bender is completely destroyed.

Death Wind (1D10)

  1. Shields damaged. Reduce Defensive Value by 2.
  2. Ion Ram targeting malfunction. Modify Ion Ram To Hit attempts by -2.
  3. Maneuver Thrusters damaged. All turns, including Tight Turns, cost one extra movement point to perform.
  4. Hull buckles. Reduce Defensive Value by 3.
  5. Electronic Warfare knocked out. Death Wind may no longer jam torps. Reduce Defensive Value by 3.
  6. Gunner killed. Death Wind may no longer use Splatterguns.
  7. Engine sputters. Death Wind may only use 4 movement points next game turn. Reduce Defensive Value by 4 due to other damage.
  8. Controls lock up. Death Wind may not move nor fire until after the next game turn. Reduce Defensive Value to 5 during this period.
  9. Pilot killed. Death Wind may not move, and the pilot's weapons may not fire. Defensive Value drops to 5. The gunner may still fire Splatterguns and torps.
  10. Reactor detonates. Death Wind is destroyed.

Glaive (1D10)

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Protobolt misfire. Mark off one remaining Protobolt.
  3. Maneuver Thrusters damaged. All turns, including Tight Turns, cost one extra movement point to perform. Reduce Defensive Value by 2.
  4. Missile Launcher damaged. Lose 1D8 of remaining missiles in one random functioning, armed Missile Launcher.
  5. Electronic Warfare knocked out. Glaive may no longer jam torps. Reduce Defensive Value by 2.
  6. Plazgun targeter damaged. Modify Plazgun To Hit attempts by -2.
  7. Major structural damage inflicted. Mark off 2D10 more hits of damage.
  8. Controls lock up. Glaive may not move nor fire cannon and projector weapons until after the next game turn. Reduce Defensive Value to 5 during this period.
  9. Crew killed. Glaive may perform no actions. Reduce Defensive Value to 5.
  10. Catastrophic structural collapse. Glaive breaks up into several useless pieces.

Drakar (gunboat, 1D6 per quadrant)

Front

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Railrepeator jams. Weapon may not fire until after the next game turn.
  3. Plazgun power loss. No firing until after 2 game turns have passed.
  4. Gunner A killed. The Heavy Plazgun may not be fired.
  5. Pilot dazed. Drakar may not move nor fire Railrepeater until after the next game turn.
  6. Cockpit controls smashed. Drakar may not move, and Defensive Value drops to 5.

Left Side

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Missile Launcher B jams. Weapon may not fire until after the next game turn.
  3. Pulse Laser B damaged. Weapon suffers -2 To Hit.
  4. Gunner B killed. Lose use of Gunner B's weapons.
  5. Structural damage. Take 5 more hits on this Damage Track.
  6. Electronic Warfare knocked out. Drakar may no longer jam torps. Reduce Defensive Value by 2.

Right Side

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Missile Launcher C jams. Weapon may not fire until after the next game turn.
  3. Pulse Laser C damaged. Weapon suffers -2 on To Hit.
  4. Gunner C killed. Lose use of Gunner C's weapons.
  5. Structural damage. Take 5 more hits on this Damage Track.
  6. Electronic Warfare knocked out. Drakar may no longer jam torps. Reduce Defensive Value by 2.

Rear

  1. Shields damaged. Reduce Defensive Value by 1.
  2. Maneuver Thrusters damaged. All turns cost one extra movement point to perform.
  3. Heavy Plazgun power loss. Weapon may not fire until after 3 complete game turns have passed.
  4. Gunner D killed. Lose use of Gunner D's Pulse Lasers.
  5. Heavy structural damage. Take 15 more hits on Rear and 5 hits to Left and Right.
  6. Reactor detonates. Drakar is destroyed.

Silent Death Rules Annex #1

Many of the rules in this annex are optional for Silent Death players, particularly those in Section X.0. Before a game begins, decide which of these rules will be used.

A.0 Cannons and Projectors

The starcraft of Overkill introduce new cannon weapon systems to Silent Death, and a new category of weapon, the "projector". The characteristics of these weapons are given below. Weapons from Silent Death are referred to for completeness.

A.1 Cannon and Projector Characteristics

Mass Driver Cannons (Miniguns, Autocannons and Railrepeators) fire spreads of depleted-uranium slugs, so the damage they deliver is variable.

  • Whenever two of the three attack dice show the same number (doubles), multiply the base damage delivered by 2. Triples do not invoke this rule.
  • Example: a Minigun fires with Base Attack Dice 2D6 and Attack Dice Bonus 1D8, and the results are 4, 5 and 5. The 14 hits the target. A Minigun normally does Low damage, which would be 4 base hits; with the doubled 5s the base damage is doubled to 8. A roll of 4, 4 and 6 would deliver 16.
  • Mass Driver cannons have limited ammunition. Each Mass Driver mount on a Starcraft Display has ammunition cells, as with Missile Launchers. Mark off one cell each time the weapon fires. When the last cell is marked off, that weapon may no longer attack.

Laser Cannons. A full range of Laser cannons was presented in Silent Death. Lasers are accurate and compact but deliver less damage than comparable weapons.

Blast Cannons. Splatterguns and Blatguns (introduced in Silent Death) are rugged particle beams with good concussion damage and poor penetration.

Disruptor Cannons (Disruptorguns and Disintegrators) disintegrate portions of a target. They have a restricted effective range and their pulses have difficulty penetrating energy screens. Special rules:

  • If the target's Defensive Value has not been reduced by a previous critical hit, add +1 to its Defensive Value against Disruptor cannon fire only. (Example: a Disruptorgun fired at a Kosmos with Defensive Value 14, which has not taken a critical reducing its Defensive Value, resolves against 15. If a critical hit had reduced it by 2, the attack resolves against 12.)
  • Damage Reduction is ignored when determining hits marked off on the target's damage track. (Example: a Disintegrator delivering 8 hits to a Shryak Shuttle with Damage Reduction 5 delivers all 8.)

Ion Cannons. The Impulsegun (Silent Death) and the Ion Ram (new). The Ion Ram is larger and more destructive. Ion fire keeps its destructive power until an armor layer is penetrated.

Plasma Cannons (Plazguns and Heavy Plazguns). If a Plasma cannon's three attack dice roll triples, the weapon mount overloads and is destroyed (treat as a "w" result on the damage track). The target is not affected by the triples attack.

Energy Bolt Projectors. A new weapon category. Projectors fire self-arming protomatter bolts that are, in effect, hyper-velocity energy torps. They are resolved like cannon fire but must be fired from a significant distance: a bolt must travel a minimum arming distance (5 hexes for the Protobolt) before it arms, and targets inside that distance cannot be affected. Once armed, the bolt's damage falls with range. Instead of reading attack dice for damage, the bolt delivers a fixed amount at each range increment, summarized in the Master Weapon Table as s.10/m.8/l.6 (for example, 10 points at short range, 8 at medium, 6 at long). Projectors have a set ammunition limit; mark off bolts as they are fired. A projector may fire up to two bolts at a single target in one Cannon Fire Phase; the two To Hit attempts are rolled consecutively, and each bolt that hits is a separate attack subject to the target's Damage Reduction. A single crewman may not fire both a cannon and a projector mount in the same Cannon Fire Phase.

A.2 Multiple Cannon Weapon Mount Bonuses

Multi-cannon weapon mounts (Silent Death Section 7.0 parallel):

  • To Hit: every cannon beyond the first in a weapon system gives +1 To Hit. This applies to all cannons in this annex.
  • Damage: for each cannon beyond the first, add +1 to the base hits delivered (Mass Driver, Laser and Disruptor cannons) or +2 (Blast, Ion and Plasma cannons), when a hit is secured.
  • Multiple Energy Bolt Projectors (such as the Protobolt Projector) may not be mounted within the same weapon system.

A.3 New Damage Conventions

A damage code followed by a multiplier means the weapon scores more damage than usual: read the attack dice normally, add them, then multiply the total by the multiplier. Example: a Heavy Plazgun (All x2) rolling 5, 6 and 8 with a hit secured delivers (5+6+8) x 2 = 38 base hits.

If several cannons in one weapon system score double damage, add the base hits delivered by all of them before multiplying. Example: two Miniguns in one mount, rolling 5, 5 and 7, get +1 To Hit and +1 damage; the total is (5 + 5 + 1) x 2 = 22.

B.0 Warheads

The Z.2 Integrated Torp Table lists all available torps. The "Standard" entry for each torp size gives the Silent Death torp. Torp loads within the same Mk category are interchangeable without altering a vessel's BPV. Players should specify which torp loads each vessel carries before a scenario, and may record them on a Torp Inventory Display (a blank form, not transcribed).

B.1 Homing Systems

  • ALH (Auto-Lock Homer). The torp homes on the target selected at discharge. This is the Silent Death standard (Section 4.2).
  • CSH (Construct Scan Homer). The torp homes on the target selected at discharge. If that target is lost before detonation, the torp chooses the nearest identical target type (same vessel name, friend or foe) instead. If none exists, or no qualifying target is in the tracking cone, the torp is removed.
  • DTH (Directed/Terminal Homer). The firer moves the torp freely until any target (friend or foe) lies within 5 hexes in its tracking cone; the torp then homes on that target with terminal guidance. If the firer is destroyed, or the terminal target leaves the tracking cone, the torp flies straight until it locks on to another target or leaves the playing surface.
  • DXH (Directed Homer). The torp is moved entirely as the firer directs. If the firing craft is destroyed or all its crew are killed, the torp is removed. Each vessel may have only one DXH-guided torp in flight at a time.
  • FTH (Free Targeting Homer). The torp homes with terminal guidance on the nearest target other than the firer in its tracking cone at the beginning of the Movement Phase in which it activates (a random one if several are eligible). If no target is in the cone at the beginning of a later Movement Phase, the torp is removed.
  • IFH (Identified Foe Homer). The torp homes on the closest enemy target in its tracking cone at the beginning of each Movement Phase. If no such target exists, the torp is removed.

Note: torps that acquire their own targets will home in on another torp just as readily as on a vessel. Both torps and starcraft are "targets" for a torpedo.

B.2 Tracking Cones

Some torps have a restricted tracking cone rather than the 360-degree cone of the Silent Death standard game:

  • A 60-degree cone is identical to a "Forward" firing arc.
  • A 180-degree cone is the combination of the "Front Quarter Left", "Forward" and "Front Quarter Right" firing arcs.

A torp requiring an assigned target at discharge must have that target within its tracking cone. A torp's target must remain within its tracking cone at the beginning of every Movement Phase after activation, or the torp is usually removed (see the homing system descriptions for exceptions).

C.0 Gunboat Class Starcraft

Gunboat Class starcraft are larger than SMAC and TMAC fighters but smaller than Escort Class vessels such as frigates and destroyers. Examples are the Drakar and the Epping. The Epping is no longer treated as a fighter as it was in Silent Death; it is now a gunboat and uses these rules and its new Starcraft Display. Gunboats are usually used as heavy fighters or patrol ships.

  • Movement. Gunboats move as fighters do, except that a Normal Turn costs them 4 movement points (not 3) and a Tight Turn is modified by +4 (instead of +3).
  • Weapon firing. Gunboat cannons, projectors, missile launchers and loaded torps work exactly as fighter-mounted ones. Gunboats usually carry larger crews and so have more firing opportunities.

C.1 Gunboat Class Starcraft as Targets

Gunboats have a separate damage track and critical hit chart for each of four quadrants: front, rear, left side and right side. They cannot evade attacks as fighters can, so their Defensive Values reflect resistance to damage rather than avoidance. A gunboat may never dodge a torp. Players are advised to use optional rule 10.7 (Torpedo Defensive Systems, as updated in Section Z.0) to give gunboats defensive options against homing weapons.

C.2 Resolving Damage Against Gunboats

Determine which damage track is affected using the Gunboat Class Quadrant Diagram (a graphic, not transcribed).

  • Cannon and projector attacks mark hits on the track of the quadrant from which the firer attacks (front, left side, right side or rear).
  • Missile attacks. If the gunboat enters a new hex during the turn missiles are fired at it, roll 1D6 for each group of incoming missiles: 1 = Front, 2 = Left Side, 3 = Right Side, 4-6 = Rear. If it does not enter a new hex, determine the quadrant as for a cannon attack, using the target's facing during the Missile Results Phase with respect to the hex from which the missiles were launched.
  • Torp attacks. The quadrant depends on the direction from which the torp enters the gunboat's hex. A torp entering through either left-side hexside marks the left-side track; the right side, front and rear are handled likewise.
  • Hits are marked on each damage track just as for fighters: start at the top left corner and proceed by rows from left to right.

Special damage codes on gunboat tracks:

  1. Drive reductions are shown in small boxes and always reduce the Drive number by 1. If the Drive is already 0, a further boxed -1 has no additional effect.
  2. The highest unmarked diamond on a track is that quadrant's Damage Reduction number, applying only to attacks on that quadrant.
  3. Weapon hits are resolved normally, but cannons and missile launchers mounted in the attacked quadrant must be eliminated before other weapon systems are affected.
  4. Torp hits are resolved normally, with no directional bias in eliminating mounted torps.
  5. Critical hits occur whenever an asterisk is marked off, and the result comes from 1D6 on that quadrant's own critical hit chart.
  6. It takes two "X" results to destroy a gunboat. These may be on the same track or on two different tracks.

D.0 Pilot Luck

A fighter pilot's Piloting and Gunnery skills reflect his technical proficiency. Pilot Luck reflects renown and fate. The Luck stat applies only to pilots; gunner Luck is not tracked. Luck rises and falls in a number of circumstances. A pilot can spend accumulated Luck to avoid enemy fire, which lowers his Luck stat. A pilot can never spend more Luck than he has; Luck is never negative.

All pilots start with a Luck stat of 0 unless a scenario states otherwise, or unless a positive Luck is purchased for a design-your-own scenario or campaign (see D.2).

D.1 Gain and Loss of Luck Points

Luck is gained by inflicting damage on enemy vessels. A pilot may collect Luck only for damage delivered by cannon/projector weapon systems and/or missiles he alone fires. A SMAC pilot may also gain Luck for damage caused by torpedoes he fires. Luck totals are adjusted immediately after points are gained or spent.

Gaining Luck:

  • Deliver half or more of the damage points that ultimately destroy an enemy starcraft: +1 Luck.
  • Single-handedly deliver all the damage points that destroy an enemy SMAC (1 man) fighter: +2 Luck.
  • Single-handedly deliver all the damage points that destroy an enemy TMAC (2 or 3 man) fighter: +3 Luck.
  • Single-handedly deliver all the damage points that destroy an enemy MMAC (4+ man) gunboat: +5 Luck.

Losing Luck. Spending Luck is at the discretion of the pilot whose vessel is under attack. Each option below assumes the pilot's own vessel is being attacked. If one or more of an opponent's attack dice are rerolled, or a critical hit result is rerolled, the new result stands; no further Luck may be spent to force more rerolls. A reroll must be forced before the exact results of the attack's damage are determined.

  • Force an opponent to reroll one of his attack dice (your choice): -1 Luck.
  • Force a reroll of a critical hit result: -2 Luck.
  • Force an opponent to reroll two of his attack dice (your choice): -3 Luck.
  • Automatically dodge one incoming torp, even after a dodge attempt or a point-defense shot, and choose which torp is dodged; your current Drive must be above 0: -5 Luck.

D.2 Purchasing Pilots with a Luck Stat

In scenarios or campaigns of your own design, pilots may start with Luck above 0. Each point of Luck adds one point to the cost of the pilot. Luck does not add to the TPV of any starcraft flown. A pilot's Luck may never start higher than his Piloting skill.

Example: a pilot with Plt 6 and Gnr 5 may take Luck 6 (the maximum for that pilot), costing 17 points (Plt 6 + Gnr 5 + Luck 6).

E.0 Life Pods

All starcraft carry life pods that try to eject surviving crew when the starcraft is destroyed.

Deployment. A life pod fails to deploy if the starcraft is destroyed by a "starcraft destroyed" critical hit (usually a 10 on a fighter's critical hit chart), or if the starcraft takes 20 or more points of damage in the game turn it is destroyed. Otherwise, the pod jettisons on a 1D6 roll of 1-5, made immediately after the vessel is destroyed. On a roll of 6 the pod fails to clear the wreck and the crew is killed.

A life pod may also deploy from a non-destroyed starcraft, but only at the end of a game turn. When it does, remove the starcraft from the map and treat it as destroyed by the opposing side in the scenario.

Characteristics. A life pod stays in the hex it deploys into. Place a life pod counter there. It has a Defensive Value of 5, no Damage Reduction, and is destroyed (killing its occupants) by its first hit.

Campaign use. Crew in a life pod are recovered automatically by their own side only if that side wins the scenario. If the scenario is lost, the occupants are captured automatically by the winner and are unavailable for the rest of the campaign. For each friendly crewman recovered at the end of a scenario, roll 1D6: 1 = crewman dies of injuries; 2 = crewman misses the next scenario recovering from injuries; 3-6 = crewman is available for the next scenario.

F.0 Poor Mechanical Reliability

Some starcraft are designated as suffering from Poor Mechanical Reliability, from poor maintenance, inadequate repair, or out-of-date diagnostics.

Each time such a starcraft sustains its first damaging hit in a combat, it always takes a critical hit, in addition to the other damage from that hit. This special critical is rolled on 1D8 for fighters or 1D4 for gunboats. It prevents the most severe criticals from affecting such a vessel. A "first damaging hit" is any attack that hits the target and delivers enough damage to overcome its Damage Reduction value.

G.0 Designing Your Own Starcraft Displays

The Overkill Starcraft Display pack includes two blank forms, one for a fighter-class vessel and one for a gunboat-class vessel, for players who wish to design their own Silent Death starcraft. Three approaches are possible: use a fighter miniature from another game; vary an existing Silent Death model; or create an original vessel. The guidelines below are general, and designers must make judgement calls, keeping game balance and the spirit of the rules in mind.

Step 1: Select Starcraft Tonnage. Tonnage guides the later steps. Use the Fighter and Gunboat Tonnage Summary:

Vessel ClassCrewmenWeapon SystemsTypical Tonnage
Lt SMAC Fighter1150-200
Hvy SMAC Fighter12 or 3200-300
Lt TMAC Fighter21 or 2300-400
Med TMAC Fighter2 or 32 to 4400-700
Hvy TMAC Fighter33 to 5700-1000
Lt MMAC Gunboat3 or 44 to 7900-1100
Med MMAC Gunboat5 or 65 to 91000-1500
Hvy MMAC Gunboat7 or 86 to 121400-2000

If you design a display for a miniature you already own, choose tonnage by comparing its size with the Silent Death line. Note that the Pharsii II, Epping and Drakar miniatures are smaller than their game-scale size, to suit the hexes used on the maps.

Step 2: Select Crew Size. The first crewman is always the pilot, who flies the starcraft and may fire only weapons with a "Forward" firing arc. All other crewmen are gunners, and each gunner should have at least one weapon mount assigned to him (Step 6).

Step 3: Select Defensive Value. Defensive Value measures how hard a vessel is to hit (for small, manoeuvrable craft) or how hard it is to affect once hit (for large, well-protected ships). Factors include energy screens, electronic warfare and computer-directed evasion. Use the Defensive Value Guidelines:

Vessel CharacteristicsTypical Defensive Value
No drives5
Space junk6
Sitting duck7
Poor defenses all around8
Slow; minimal screens; antiquated EW9
Slow; archaic evasion computer programs10
Lumbering; overburdened with offensive systems11
Large vessel; deficiency in one defensive characteristic12
Superior in one defensive characteristic13
Fast; good screens and EW; very small14
Superior defenses all around; remarkable in one area15
Superfighter; represents a technological advance16
Would carry few, if any, weapons17
Completely unheard of18

For comparison, the Pit Viper (small, high Drive) has Defensive Value 15, and the Epping (slow, low screens, poor electronics) has 8.

Step 4: Select Damage Reduction. Damage Reduction represents armor and hull toughness. Use the Damage Reduction Guidelines:

Hull CharacteristicsTypical Damage Reduction
Simple steel hull; no armor to speak of0
Crysteel hull; poorly designed or manufactured1
Crysteel hull with minimal armor2
Crystanium hull; heavily fortified crysteel3
Crystanium hull with substantial armor belt; double hull4
Hull reinforced with special alloy plates5
No fighter is this well armored6

Gunboats may have a different Damage Reduction in each quadrant. The front is usually most heavily armored and the rear the least.

Step 5: Select Drive. Fill in the Drive number, using the Drive Number Guidelines:

Vessel ConfigurationTypical Drive Number
Garbage scow; heavy gunboat6-7
Shuttle; medium gunboat8-9
Light gunboat; heavily armed and armored fighter10-11
Heavy fighter; outdated fighter; strike vessel12-13
Medium fighter; multi-role vessel; fast shuttle14-15
Light strike fighter; attrition fighter16
Light fighter; interceptor17
Special speed modification18
Fighter is mostly engine19
More power than a pilot should handle20

Step 6: Select Weapons. Every crewman who fights needs a weapon mount. Blank displays show weapon mount boxes and torpedo cells; use only those needed. Each weapon is assigned to one crewman. A crewman may have several mounts but may fire only one cannon or projector system per Cannon Fire Phase. Pilots fire only "Forward" arc weapons. Weapon mounts, in order from most compact to most space-consuming:

  1. Minigun (Mag 4-8)
  2. Pulse Laser
  3. Splattergun
  4. Autocannon (Mag 4-8)
  5. Disruptorgun
  6. Missile Launcher (Mag 4-8)
  7. Meld Laser
  8. Missile Launcher (Mag 9-12)
  9. Blatgun
  10. Missile Launcher (Mag 13-16)
  11. Protobolt Projector (1-3 bolts)
  12. Missile Launcher (Mag 17-20)
  13. Railrepeator (Mag 4-8)
  14. Protobolt Projector (4-6 bolts)
  15. Turbo Laser
  16. Impulsegun
  17. Disintegrator
  18. Ion Ram
  19. Plazgun
  20. Heavy Plazgun

Torpedo allocation depends on role. Strike fighters should carry several heavy warheads; multi-role and stand-off fighters a mix; interceptors one or two Mk10s for dogfighting. Torps can also balance an inadequate design.

Step 7: Assign Special Characteristics. If using the optional rules, assign custom Torpedo Defensive Systems and Damage Control characteristics (optional rules 10.7 and 10.12). The generic critical hit charts on the blank displays may be altered to reflect a design's peculiar weaknesses (for example, a reactor that is more vulnerable, or a cockpit that prevents "pilot killed").

Step 8: Select the Number of Hits on the Damage Track. Blank displays have large damage tracks; reduce the boxes to the number of hits the fighter can take. Most fighters take hits equal to tonnage divided by 10 (a 100-ton vessel takes 10 hits). Good structural integrity may raise the total by up to 25%, with 10% the norm.

For gunboats, first calculate the total as if it were a fighter. Then allocate about 65% of the total to the front track, about 50% to each side track, and about 35% to the rear track. The distribution may vary, but the combined total on all four tracks should not exceed 200% of the fighter-equivalent figure.

Step 9: Distribute Special Damage Symbols. Fill the damage track with the special symbols:

  • Drive hits should be concentrated in the first half of the track if engines are exposed or poorly protected.
  • Damage Reduction diamonds should be placed to reflect armor quality.
  • "W" and "T" markers (upper and lower case) represent weapons and torps. Most weapons, and especially primary batteries, should be knocked out by half of the total hits, so place capital "W"s in the first half. A fighter needs as many "W" and "T" markers as it has weapon systems and torps. Gunboat tracks carry more "W"s and "T"s than strictly required, so that the loss of several weapon systems can be shown even if only one quadrant is repeatedly hit.
  • Critical hit asterisks. A fighter's critical hit carries about a 20% chance of incapacitation or destruction. A powerful vessel with a critical within the first five hits of its track has a serious weakness. Older or inferior designs may have up to four criticals on an average track; newer or more rugged designs have them grouped further down. Tracks of twenty or more boxes should have at least two critical asterisks.
  • Gunboat tracks. Put Drive hits more frequently on the rear track, side hits to reduce armor, torps and several weapons, and start special damage later on the front track, which is usually most heavily armored. Place two "X"s in each of the four gunboat tracks: one in the last box of each track and the other in the last half of the track.

Step 10: Choose Basic Point Value (BPV). There is no exact formula. Consider firepower and how much can be brought to bear in one turn; the limited ammunition of torps, missiles, mass drivers and projectors; how quickly weapons are lost and whether the powerful ones go first; the arcs of fire; crew size; speed against enemy weapons; how the damage track keeps speed; and the frequency and placement of criticals. Test the design in several scenarios against standard opponents with all skills at 5, and compare its BPV with existing designs.

X.0 Silent Death Optional Rules

These extend Section 10 of the original Silent Death rules. They may be added as players wish; none is compulsory. Before a scenario, players should agree which optional rules are in effect.

X.1 Easing Target Speed Restrictions for Heavy Weapons. A weapon with a target speed restriction may fire at faster targets, at a To Hit penalty of -1 for each Drive number the target exceeds the weapon's limit. This is cumulative with other To Hit modifiers, including multi-gun and range effects. Example: a Sorensen III's Blatguns (Target Drive 13 or less) fired at a Spirit Rider with Drive 15 take a -2 To Hit (13 - 15 = -2).

X.2 Firing More Than One Cannon/Projector Weapon System. A single crewman assigned several cannon or projector systems may fire all of them (up to four) in one Cannon Fire Phase, at -2 To Hit for each attack. All systems fired must target the same vessel. Example: a Hell Bender pilot fires all three of his systems at a Shryak Shuttle (Drive 8), each at -2 To Hit.

X.3 Sequential Resolution of Torp Attacks. In the standard game, torps striking a vessel together are resolved as one combined attack. With this option, each torp's damage is rolled and applied separately, starting with the least powerful and working up to the most powerful. Damage Reduction then applies to each blast, so armor can reduce each one. Example: a Night Hawk hit by a Mk40, a Mk20 and two Mk10s takes the Mk10s first (1D12 each), then the Mk20 (2D12), then the Mk40 (4D12), with Damage Reduction applied each time.

Y.0 Silent Death Questions

Rulings issued by the designers for Silent Death, arranged by rule number.

Silent Death Standard Game

  • 1.2 Dice. The 0 on a D10 represents 10.
  • 4.2 Torpedo Movement. The controlling player determines movement point expenditure and the exact flight path. A torp must always move so that its new hex is closer in range to its target. Given two closer hexes, the controlling player chooses, even if this costs extra movement points to turn. A torp that cannot make a final turn toward its target, and cannot decrease range by moving forward, ends its Movement Phase. A torp must move closer to its target even if that means entering an asteroid hex, which automatically eliminates it.
  • 4.2 Torpedo Tracking. A Standard Game torp follows and attacks only its assigned target; it cannot be diverted by flying another vessel in front of it. The new IFH homing system (Annex B.1) allows this effect in specific circumstances.
  • 5.2 Torpedo Turning. Yes, a torp may turn more than one hexside within a single hex, at a cost of 3 movement points per hexside turned.
  • 7.2 Damaging Multi-gun Weapon Systems. When a "w" result is applied to a multi-gun mount, the whole mount is eliminated. There is no partial reduction of weapon systems.
  • 7.2 Damage Reduction. Yes, Damage Reduction can completely negate an attack whose damage does not exceed the Damage Reduction number. Example: 2 points of damage against Damage Reduction 4 causes no damage.
  • 11.6 Laser Sats. Laser Sats (as described in the Screening Force scenario) have a BPV and TPV of 11.

Z.0 Consolidated Tables (Annex #1)

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 †
Railrepeator2D6+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
Stnd Mk10 Torp1D12N/AN/AN/ANoneAll
Stnd Mk20 Torp2D12N/AN/AN/ANoneAll
Stnd Mk30 Torp3D12N/AN/AN/ANoneAll
Stnd Mk40 Torp4D12N/AN/AN/ANoneAll
Stnd Mk50 Torp5D12N/AN/AN/ANoneAll

Notes: † Whenever two of the attack dice roll doubles, multiply base damage delivered by 2. § If the target's Defensive Value has not been reduced by a critical hit, add 1 to its Defensive Value; also ignore the 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 hexes only at the beginning of the Missile/Torp Launch Phase.

Z.2 Integrated Torp Table

Torp TypeSpeedDurationDamage DeliveredDefensive ValuePit SkillTracking ConeHoming SystemNotes
Mk10 Torp Loads
Standard Mk10 Torp12101D12105360°ALH
Express-110 Torp18101D12103360°ALH
Sentinel-210 Torp12101D12104180°FTHRemains 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 the firer or during unguided flight, and 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°FTHRemains 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 the firer or during unguided flight, and 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. The player who launched the J40 decides which decoy to negate that turn.
Mk50 Torp Loads
Standard Mk50 Torp12105D12105360°ALH
Ex50 (surplus) Torp *10105D1210560°FTH
Relock-550 Torp1155D12112180°IFH
Mayhem-750 Torp102—102—DXHA multi-warhead drone that carries 5 Relock 510 torps. At the beginning of the Movement Phase following its last turn of flight, these torps deploy, each facing a separate hexside (except rear).
Remote R-50 Torp855D1282—DXH

Key: Speed = movement points the torp may spend each Movement Phase (only DXH torps may spend fewer). Duration = maximum game turns the torp may move; if it has not detonated by then, it is removed. Damage Delivered = dice rolled on a hit, all of which are delivered. Defensive Value = the torp's Defensive Value against cannon, projector and missile attacks in flight. Pit Skill = the torp's ability to dodge incoming torps. Tracking Cone and Homing System: see B.2 and B.1. * Torp has severe disadvantages; scenario special rules indicate when it is used.

Z.3 Anti-Torpedo Capabilities Table

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

Bracketed figures are printed as shown on the source table; their meaning is not restated here.

Z.4 Damage Control Table

Vessel TypeDamage Control Success Spread (1D10)
Blizzard1-2
Death Wind1-5
Drakar1-8
Epping1-7
Glaive1-6
Hell Bender1-3
Kosmos1-2
Night Hawk1-3
Pharsii II1-5
Pit Viper1-2
Revenge1-5
Salamander1-6
Seraph1-6
Shryak Shuttle1-7
Sorensen III1-3
Spirit Rider1-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
Railrepeator12-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

  1. Missile Launch Phase: (i) attempt lock-ons, then launch.
  2. Torp Launch Phase: (i) allocate attacks, then launch.
  3. Initiative Phase: (i) roll 1D10, modified by best pilot.
  4. Movement Phase: (i) alternate movement of vessels; (ii) torps move after their targets do.
  5. Torp Results Phase: (i) attempt dodging, or fire point-defense system; (ii) resolve any torp damage; (iii) attempt jamming, or deploy decoys.
  6. Cannon/Projector Fire Phase: (i) gunners, in order, fire their weapon systems; (ii) pilots, in order, fire their weapon systems.
  7. Missile Results Phase: (i) resolve missile attacks; (ii) asteroids drift.