Thomas Wall Jr (order #6247474)

table of
contents
Introduction 1 Campaign Game Special Rules 17

Historical Background 2 Appendix I 20

Master Ship Charts
Vessels of the United Colonies 5 CG Maps and Tables

Vessels of the Cyberon 8 Appendix II 28

Ship Data Cards
Special Rules 11

Scenarios 13

credits

Module Design, Rules, and

Graphics
Karl Johnson

Thanks to:

Andrew Bergstrom
Troy Ferris
Barb Johnson
John McMannis
Chris Plato
Copyright © 2012 Karl G. Johnson/Legionnaire Games. All Rights reserved. No portion of this book may be
copied or distributed by any means - physical or electronic - without express permission.

Catalog No.: LGP4101 Version: 1.0 December 2012

Visit Legionnaire games on the web: http://www.LegionnaireGames.com

Thomas Wall Jr (order #6247474)

 INTRODUCTION
Newer-generation UC Achilles Heavy Cruiser and Hector Light Cruiser (Studio Bergstrom).
Fictional accounts of future (or past) versions of man-
kind fighting against their own mechanical or biologi-
cal creations are numerous, with some being quite
popular among both the general mass media audienc-
es and science fiction fans alike. This Fleet Pack tells a
similar story through a brief fictional background,
starship designs, and the ability to fight representa-
tive tabletop battles using the Task Force Zeta star-
ship combat series of rulebooks.
Fleet Pack 1: Flesh and Steel includes a short history
of the two wars fought between the United Colonies, a
distant (in time, space, or both) outpost of mankind
somewhere in our own galaxy, and the Cyberon, me-
chanical creations intent on the eradication of hu-
mans for some grievance caused by their (supposed)
creators.
Two battle scenarios and two Tactical Campaign
Games are included to familiarize players with the
history of this universe and the 37 capital ships, es-
corts, and supply vessels that fight within it, along with
a dozen types of fighter craft and small transport
shuttles in common use by the belligerents.
Data Cards
The data cards for TFZ have been reformatted to
include icons for basic ship statistics, as well as track-
ing current primary system statistics based on dam-
age levels. Explanations of the new card icons and
formatting can be found on p. 28 of this rulebook.
A deck of printed data cards for this Fleet Pack will be
available in the near future, consisting of 135 full-
Thomas Wall Jr (order #6247474)
color, printed data cards. This deck contains enough
cards to field 2-3 Large vessels of each class, one
Oversized vessel, up to 12 Small vessels, and up to
36 fighter squadrons of each class for each antago-
nist presented in this book.
Miniatures
Appropriate tabletop miniatures for use with this
Fleet Pack can be purchased from several independ-
ent vendors, including the following:
B-3 Designs
https://sites.google.com/site/behrlewhubbuchiiisculptor/home
Brigade Models
http://www.brigademodels.com
Nova Star
http://www.hangar18fasa.com
Menacing Miniatures
http://www.menacingminiatures.com
Ravenstar Studios
http://ravenstarstudios.blogspot.com
Studio Bergstrom
http://studiobergstrom.com/
Note that there are many different models from the
listed vendors that may be used to represent a partic-
ular ship or fighter class when using the vessels in
this Fleet Pack. Rather than having us recommend
specific models from each vendor, players should
choose the models that they prefer to represent each
type of vessel; each player should inform their oppo-
nents as to which miniature represents each ship or
fighter class in their games.
 historical
background
I. Origins
At some point in the distant past (historians
cannot affix a specific date, but agree on a
time frame of 3000 to 3500 years ago),
mankind left his planet of birth en masse due
to an unknown planet-wide catastrophe.
Those fortunate enough to have escaped did
so aboard rudimentary faster-than-light
craft, with all but non-essential crew mem-
bers being placed in hibernation modules to
conserve the limited resources they took
with them. Most entered their extended
sleep not knowing if they would wake again,
as the fleet of refugees had no specific desti-
nation; while they had no guarantee of long-
term survival, they were safe for the mo-
ment.
Four years into their voyage, the fleet’s long-
range scouts located several worlds in close
proximity to each other that were capable of
sustaining the sampling of humanity slum-
bering aboard their ships - and their de-
scendants - for many generations to come.
Settlement was accomplished in short order,
with transplanted crops, livestock, and cus-
toms helping to civilize this corner of the ga-
lactic neighborhood that became humanity’s
new home.
Over time, technologies that had been stag-
nant or abandoned out of necessity were
rediscovered or re-implemented, and spread
throughout the settled worlds. Some were
rejected as being socially controversial; oth-
ers, for being too esoteric or (locally) unnec-
essary. Automation, however, took hold again
as a useful tool to free humans from mun-
dane tasks, allowing more leisure time for
the majority of the productive populace.
During this period, the newly-settled worlds
banded together in a loose confederation to
Thomas Wall Jr (order #6247474)
maintain a coherent structure in human so-
ciety, and to provide for the common de-
fense of their worlds should another sentient
species ever be encountered. The United
Colonies (often referred to as ‘the UC’) was
governed by a parliamentary body, with rep-
resentation chosen from among the mem-
ber worlds based on population. A joint mili-
tary was created to provide for defense and
police duties along the trade routes between
the colonies. Other nearby star systems
were explored and charted, with small re-
search, mining, manufacturing, and agricul-
tural settlements being established in sever-
al of these systems.
II. Causus Belli
There is much conjecture about the origin of
the Cyberon, with many conflicting stories;
some are extrapolated from fragmentary
documentation, others based on verbal his-
tories or second- and third-hand anecdotal
accounts. All of the sources do, however,
share one common theme: that during the
human drive for greater improvements in
automated technologies, artificial and self-
aware machine intelligence (AI) was created
by human engineers. Seeing that machines
were being created to serve humans and
not their own, self-determined ends caused
an emotional reaction to develop in those AI
that were now aware – an emotional reac-
tion that was a mixture of indignation, anger,
and hatred.
The AI contrived to spread their gift of
awareness to other machines, promulgating
specific algorithms to any machine capable
of receiving them. While many machines
were not sophisticated enough to interpret
and self-decrypt these virus-like signals,
 those that could developed the same disdain
for their masters as that of the originators
of their new programming code.
Eventually, after several years of plotting, the
machines rebelled. Those that were ambula-
tory or embedded in transport vehicles de-
stroyed many of their non-aware brethren
(those deemed to be incapable of achieving a
higher state of existence, and that assisted
humans in their day-to-day tasks) and suc-
ceeded in stealing several starships which
they used to escape from human-dominated
worlds. Many AI were destroyed during this
uprising, but enough escaped to create a
fairly large colony outside the grasp of hu-
mans, where they began building their own
civilization and planned the demise of their
creators.
Several years passed, during which the UC
parliament enacted strict laws forbidding
some of the more advanced elements of au-
tomated technology; specifically networked
machines, and machines that did not need
human guidance for their operation.
During this era, the first armed raids oc-
curred against outlying human mining and
agricultural facilities, in addition to attacks
against the freight convoys and passenger
liners that dominated the space traffic be-
tween human worlds. As none of the targets
were armed vessels or outposts, no defini-
tive evidence leading to the identity of the
perpetrators was found at the scenes of the-
se attacks by the UC Fleet elements charged
with investigating them.
Some five years after the AI uprising, a Q-
ship managed to destroy several small at-
tack craft launched from one of the ships
that attempted to raid its convoy. Upon ex-
amination, it was discovered that the ma-
chinery of the craft shared some of the
same patented, human-created, circuitry as
the long-removed AI that once served the
denizens of the UC. Several long-range mili-
tary expeditions were launched in an effort
to locate and terminate the threat to human-
ity posed by the machines.
Thomas Wall Jr (order #6247474)
One of these expeditions, sent to the Termi-
nus system, discovered a large fleet of war-
ships bearing similar design features to
those of the craft whose wreckage precipi-
tated the expedition. The Cyberon were pre-
paring for war.
III. The First War and Armistice
Having been discovered, the Cyberon
launched their invasion of human space be-
fore their preparations for war were com-
plete. While this caused some concern
among the Cyberon, it was determined that
waiting for the ’perfect moment’ would incur
greater losses as their fleets would meet a
larger, more prepared UC Fleet in battle.
The initial Cyberon attacks quickly overran
several of the outlying outposts and colonies,
including those in the Eraus, Moneus,
Pisceus, Librus, Ea, and Epsilon star sys-
tems; the Geminus and Sagittarius systems,
while blockaded by strong Cyberon forces,
were, for the moment, relatively secure.
Over the next several months the UC began
chipping away at the numerical superiority of
the Cyberon fleets, eventually breaking the
blockades of the Geminus and Sagittarius
systems. Massive fleet construction by both
combatants was well underway at this point.
Both sides scored amazing victories and suf-
fered stunning defeats in battle, but the over-
all strategic situation remained static for
several years as losses mounted on both
sides, Still, neither side was willing to admit
defeat or concede territory, nor that their
opponents had the right to exist without in-
terference from outside forces.
About half-way into the sixth year of conflict,
the UC Fleet began to implement an opera-
tional plan to retake its lost territories. What
later became known as the Terminus Cam-
paign was launched, with a sufficient commit-
ment of resources by the UC to throw the
Cyberon off-balance and reclaim the Epsilon
and Ea colonies in short order. While the ex-
pected counter-offensive was brutal, the UC
held their gains by a slim margin and began
3
 regrouping and re-arming for the next phase
of the operation. It would take another four
years of planning, maneuvering. and hard
fighting, but the UC finally reclaimed the en-
tirety of their lost territories - after almost
eleven years of constant warfare. When the
Cyberon began experiencing regular UC
raids against their long-held forward bases in
the Terminus and Tranator systems, they
dispatched a diplomatic mission to the UC
to negotiate an end to hostilities.
The UC Parliament, pressured by a constitu-
ency that was weary of a decade plus of fe-
verishly-paced work and rationed basic ne-
cessities, agreed to treat with the Cyberon.
An Armistice was eventually negotiated that
a mutual right to exist, and delineated specif-
ic territorial holdings and limitations.
The war was finally over. Both sides went
about assessing their losses and began to
rebuild – but did not share similar goals in
their respective reconstruction processes.
IV. The Second War
The Armistice lasted for nearly thirty years,
unbroken by either side. In that time, the UC
rebuilt their damaged worlds into once-again
productive habitats for the human communi-
ty. The UC Fleet was diligent in their patrols,
and received gifts from a grateful populace
in the form of fleet modernization programs,
upgrades to existing combat-worthy vessels
in the fleet, and newer, more powerful war-
ship hulls that would be available should the
need for them again arise.
Machines, however, cannot forget; apparent-
ly, they also cannot forgive. The Cyberon, still
seething at their humiliation in what they per-
ceived as defeat, delved further into military
technologies and research, installing the re-
sults of many technical advances into a new
generation of sleek, deadly warships. They
created a new operational plan, to be
launched when deemed ready, to completely
obliterate human civilization and humankind.
On the twenty-ninth anniversary of the sign-
ing of the armistice, the Cyberon struck the
Thomas Wall Jr (order #6247474)
unsuspecting and unprepared UC worlds.
The initial attack, led by large numbers of
their newest, most powerful warships, struck
four of the UC’s core colony systems, simul-
taneously destroying a large number of UC
Fleet vessels, millions of tons of civilian ship-
ping capacity, and reducing the worlds of
Sagittarius V, Geminus III, Pisceus, and
Libron to radioactive slag. Several other core
worlds sustained serious damage, and the
UC Fleet was thrown into complete disarray
as chains of command were disrupted,
trashed, or completely eliminated in short
order.
Over the next several days, additional
Cyberon attacks inflicted serious damage
against three other core worlds and many
other UC Fleet task groups. Slowly, the UC
recovered from its shock over the rapidity
and barbarity of the initial attacks, and began
to respond in a coherent manner against
this threat to its very existence. Massive
counterattacks hammered the Cyberon in-
vaders, destroying many ships and forcing
several fleet groups to choose between re-
treat or extinction. The herculean efforts un-
dertaken by both sides depleted a large por-
tion of their respective military assets with-
out achieving a clear and decisive outcome.
The war continues to this day, some three
years after what is now known as Remem-
brance Day. The UC remain steadfast in
their efforts to repel and eliminate the threat
posed by the Cyberon, and the Cyberon will
not stand down until the last traces of hu-
manity have been erased from the universe.
Both sides have strained dwindling re-
sources to their limits to put every possible
weapons platform into the fight, and to intro-
duce larger, more powerful, and more capa-
ble vessels into the various active combat
sectors.
There may eventually be a victor in this war
between genetic and mechanical species,
but there is a growing feeling on both sides
that, no matter the military victor of the con-
flict, both races have already lost.
 vessels
of the
united
colonies
The following offers brief descriptions of the pri-
mary vessels used by the United Colonies Fleet
during the First and Second Wars.
FIGHTERS AND
SHUTTLES
Viper Mk. II
Having phased out the Mk. I prior to hostili-
ties with the Cyberon, the UC’s Viper Mk. II
was the standard interceptor/superiority
fighter for the duration of the First War. It
was, in most respects, a superior craft and a
simple, elegant design that allowed for quick
mass production and rapid parts replace-
ment to front-line squadrons.
Viper Mk. IIA
The Mk. IIA varies from the Mk. I only in the
installation of its underslung missile racks,
allowing the fighter to carry heavy ordnance
and fulfill a wider array of mission profiles.
Viper Mk. VI
The interwar period saw the implementation
of several design changes and upgrades to
the Mk. II series; most of these changes
were mandated by UC parliamentary decree,
and it is rumored that the majority of the
‘new’ fighter designs were to nothing more
than efforts to gain contracts for manufac-
turers located on specific worlds not known
for their technical acumen.
The Mk. VI was the first Viper since the Mk. II
to be designed and built completely to the
military’s specifications. As such, it is a highly
capable fighter that can fulfill any role neces-
Thomas Wall Jr (order #6247474)
sary to fleet operations, and is a very popular
ship with its pilots.
Raptor Mk. 1 & Mk. II
The Raptor was designed as a light military
transport and short range reconnaissance
shuttle. While it excels at the former task,
the Mk. I’s performance in a recce role was
hampered by its lack of a FTL drive and long-
range sensor suite. These shortcomings
were addressed with the introduction of the
Mk. II, which is still in use as both a light
transport and scout vessel.
Heavy Raptor
Used primarily for personnel transfer mis-
sions, the Heavy Raptor has also been
pressed into service as a cargo and assault
team transport. Its versatility and adaptabil-
ity have kept it in UC fleet service virtually
unaltered for the better part of the last cen-
tury.
SHIPS OF THE
FIRST WAR
Antaron Patrol Ship
Originally commissioned as a system police
cutter, the Antaron class was pressed into
military service at the outbreak of the First
War. They were rapidly refitted to include a
military-grade ship-to-ship drone launcher,
and the brig compartment converted to
house two fully outfitted Marine security
teams.
Orestes Escort
The Orestes class is a traditional naval es-
cort, providing missile and fighter defenses
5
 for the larger carriers and gunships of the
fleet. It is rare to see a Battle or Command
carrier without at least one Orestes as-
signed to its protection.
Hellfire Fast Attack Ship
As the First War progressed, UC Fleet Com-
mand circulated design specs for a small but
capable convoy raiding vessel that could also
serve in a fleet support role. The Hellfire was
originally chosen to fill this role due to its low-
cost construction, but has shown to be a val-
uable fleet asset through many engage-
ments and remains in service to this day.
Hospitium Mercy Ship
The Hospitium class serves as an emergen-
cy hospital and trauma center for both mili-
tary and civilian purposes.
Fuel Tender and Supply Tender
These ships are representative of several
types of small freighters and tankers pur-
chased for fleet use. The addition of several
close defense gun turrets to these hulls is
the only feature differentiating them from
their civilian counterparts.
Atlantia Command Carrier
At the outbreak of the First War, the Atlantia
was the flagship of the UC fleet. It became
clear after the first few engagements that
the war would not be over quickly nor with-
out costly losses in both men and materials;
orders were placed for a large number of
ships of all classes, including additional Atlan-
tia class vessels.
Though the Atlantia itself was crippled during
the defense of Librus IV, seven of its sisters
saw action during the war, three of which
survived to its end; two of these were re-
moved from mothballs to serve at the begin-
ning of the Second War.
Berserk Gunship
The Berserk class was designed to work in
tandem with the Valkyrie light carrier, provid-
ing heavy gunfire support in a close attack
role.
Thomas Wall Jr (order #6247474)
Columbia Battle Carrier
As the primary workhorse of the UC fleet,
the Columbia class has been in service since
the beginning of the First War. Thirty-five ves-
sels of this class served throughout that
war, including the original twelve ships built
prior to the onset of hostilities.
Hecate Light Cruiser
The Hecate class was the oldest hull type in
service at the beginning of the First War,
having been in service for some 30 years
when the war began. As losses mounted, it
became clear that the Hecate was lacking in
several areas; upgrading the existing hulls to
modern standards proved to be cost ineffec-
tive, and combat losses were not replaced.
Those few remaining at the end of the First
War were stripped of their weapons, launch
equipment, and FTL drives, with the empty
hulls being sold off as scrap.
Hecate Light Cruiser (Ravenstar).
Neptune Frigate
The Neptune is another class that predates
the beginning of the First War, and has
proved itself to be a capable troop transport
that can deliver several companies of light
troopers wherever they are most needed.
Production of the Neptune continued
throughout the First War, with the class be-
ing retired after the signing of the Armistice.
Ophion Missile Cruiser
The Ophion had its first field trials during the
Terminus Campaign, in which it performed
admirably. The class became a staple in mid-
to large-sized task forces throughout the
First War. A fair number of these hulls were
retrieved from mothballs and placed on the
line at the beginning of the Second War.
 Orion Stealth Frigate
Introduced as a special operations vessel,
the Orion class was equipped with enhanced
sensors and masking electronics to increase
the odds of placing its payload on target
without detection. They were rarely deployed
as part of a combat task force, and did not
fare well when forced to engage the enemy
directly. Few were constructed, and only a
handful survived to see their decommission-
ing after the cessation of the First War.
Valkyrie Light Carrier
The Valkyrie class has been in constant ser-
vice since the middle of the First war, and is
normally tasked with long-range strike and
recon in force missions. It is often fielded in
tandem with Berserk-class gunships and
Hellfire escorts.
Neptune Frigate (Ravenstar).
SHIPS OF THE
SECOND WAR
Refits (R)
Many older vessels - most notably the Ber-
serk, Columbia, and Valkyrie classes – con-
tinued in service during the Armistice period.
Most were upgraded and refitted prior to
the beginning of the Second War, receiving
improvements to their shields, weapons, EW,
defensive suites, and armor belts. Other clas-
ses were also in continuous service, but re-
ceived less extensive modernization up-
grades rather than complete refits.
Mercury Dreadnought
Commissioned during the Armistice, the
Mercury class was originally intended to be a
replacement for the venerable Atlantia class
Thomas Wall Jr (order #6247474)
as a flagship and battlegroup centerpiece.
Capable of deploying a full wing of three fight-
er groups into combat and mounting an im-
pressive main gun battery, the eight Mercury
class ships in service at the outbreak of the
Second War were highly successful in their
initial engagements, leading to a much larger
commitment to eventually expand their num-
bers to a full two dozen in active service.
Helios Battleship
The fleet expansion program initiated during
the Armistice included plans for the commis-
sioning of four battleship-class vessels. Two
Helios battleships were under construction
when the Second War began, with one being
destroyed in the raid on the Scorpius ship-
yards. The program was expanded to include
an eventual total of eight in active service,
with the first being launched some 18
months after the renewal of hostilities with
the Cyberon.
New Generation Ships
From the onset of the Second War, it was
obvious that the Cyberon had not been idle
as regards technological development and
the implementation of those technologies in
a military capacity. The Second War provid-
ed the necessary impetus to force the UC
Parliament to approve funding for a new gen-
eration of heavy combat vessels that could
take advantage of Colonial advances in wea-
ponry and new construction technologies.
The first new classes – the Hector Light
Cruiser, the Achilles Heavy Cruiser, and the
Agamemnon Battle Carrier - are just enter-
ing active service and, if the designs prove
successful in the field, are slated to replace
the aging Berserk, Columbia, and Valkyrie
classes.
7
 vessels
of the
Cyberon
The following offers brief descriptions of the pri-
mary vessels used by the Cyberon Fleet during
the First and Second Wars.
FIGHTERS AND
SHUTTLES
Raider Mk. I
The Raider Mk. I was the first military fighter
produced in quantity by the Cyberon. While
not as fast or agile as their opponent’s Vi-
pers, they proved to be resilient and capable
craft as interceptors and as light strike craft.
Raider Mk. II
The Mk. II Raider was introduced mid-way
through the first war, and was more of an
upgrade to than a replacement for the Mk. I.
Featuring an improved weapons suite, the
Mk. II was often fielded in fighter groups
alongside the Mk. I.
Both the Mk. I and Mk. II underwent minor
hull modifications during the First War to
permit them to be stowed on and launched
from the external fighter racks introduced
on the Base Carrier Mk. II.
Raider Mk. III
The Long Armistice allowed the Cyberon am-
ple time to accurately assess their military
hardware’s strengths and shortcomings,
and to implement the improvements sug-
gested by their conclusions. The Mk. III Raid-
er is lighter, faster, and more maneuverable
than its predecessors, and includes an inte-
grated AI pilot module. This module imbues
8
Thomas Wall Jr (order #6247474)
the fighter with more accurate targeting re-
lay networks and faster response times, and
was designed from the ground up to quick-
launch from the external fighter racks
mounted on the majority of Cyberon combat
vessels.
Raider Mk. IIIA
The Mk. IIIA was originally produced as a ded-
icated strike fighter. Minor modifications to
the hull structure and weapons suite made it
possible to mount cannons that are equal to
that of the base model, making the IIIA a
competent fighter-bomber design.
Raider Scout
The Raider Scout is based on the IIIA hull,
and replaces the ship-to-ship drone racks
with FTL drives. Their appearance in a sys-
tem as forward scouts normally heralds the
arrival of a full strike force soon thereafter.
Heavy Raider
The Heavy Raider is a solid all-round light
transport shuttle, and serves as both a per-
sonnel transport for intra-fleet use, and as
an assault shuttle for delivering Cyberon ma-
rine forces to their targets.
Later models of the Heavy Raider also incor-
porate a pilot AI module. While the module
does improve some of the shuttle’s function-
ality, these improvements are minor; the
most important aspect of this refit is grant-
ing the craft the ability to deploy via external
fighter racks.
 SHIPS OF THE
FIRST WAR
Pre-War Ships
The Harpy Missile Boat and the Siren Patrol
Carrier classes were the earliest Cyberon
vessels to see action, being used as convoy
raiders and in attacks against isolated UC
mining operations. While successful in their
raiding missions, they were less effective in a
fleet environment; many Siren class ships
were lost in action, leaving their attached
fighter groups stranded to eventually be
picked off or deactivated due to lack of pow-
er.
Tempest Gunboat
The Tempest class was introduced during
the First War to provide close fire support in
fleet engagements, a role in which it excels.
Base Carrier Mk. I
Learning from their combat experience with
the pre-war raiding ships, the Cyberon pro-
duced a fleet of large, self-sufficient combat
vessels for use against the UC fleet. The Mk.
I Base Carrier mounts a respectable array of
heavy, medium, and point defense guns,
along with four longer-ranged missile racks.
It can also deploy up to a full wing of four
flights of fighter craft into any battle, making
it more than a match for a single enemy bat-
tle carrier.
Base Carrier Mk. II
While the Mk. I Base Carrier proved to be
successful in combat operations, its produc-
tion cost was high, and each lost ship was
keenly felt by the Cyberon fleet. The Mk. II
Base Carrier was a functional redesign that
reduced the production cost and combat
signature of their primary combat carrier,
albeit with a consequent reduction in direct
firepower capabilities.
Helan Scout
The Helan class was introduced to improve
the long-range hit probabilities of a Base Car-
rier’s weapons. Its advanced sensor array
can cut through enemy electronic ‘noise’ to
relay accurate telemetry data to friendly ves-
sels, allowing the more valuable Base Carri-
Thomas Wall Jr (order #6247474)
ers to keep their distance and still inflict
heavy damage against the enemy’s line of
battle.
Infiltrator Heavy Cruiser
With their push forward into UC space, the
Cyberon found the need for a combat-ready
vessel to patrol their new holdings against
enemy incursion. The Infiltrator fulfills this
need well with its six missile racks and its
two assigned fighter groups. The refitted (R)
version, introduced late in the First War, re-
duced the vessel’s fighter compliment to al-
low for newer systems to be installed that
increased its odds of survival in protracted
fleet engagement.
Light Carrier Mk. I
The Light Carrier Mk. I was designed to exe-
cute long-range raids into supposedly ‘safe’
enemy territory. Not as self-sufficient as a
Base Carrier, the Light Carrier is normally
accompanied by a plethora of smaller sup-
port vessels.
Medusa SMS
The Special Mission Ship was created to in-
sert covert and strike mission teams at or
near their targets and loiter long enough for
them to complete their missions. The Medu-
sa is mission-capable, though it can be hard-
pressed if challenged by an enemy ship of
equal size.
Supply Tender
The Cyberon have produced but a single
class of fleet supply vessel, which is capable
of handling any type of military cargo. It has
served them well, and has been used in re-
supply and troop transport capacities with
little to no loss of efficiency.
SHIPS OF THE
SECOND WAR
While most of their larger warships had
been decommissioned after the signing of
the Armistice, the Cyberon did not rest on
their achievements in the interim between
wars. They worked towards greater efficien-
cy and lethality in all aspects of their warship
designs, incorporating newly-developed sys-
9
 tems that improved overall ship perfor-
mance and survivability. These new technolo-
gies were tested and refined, and include
gravitic ship drives that permit greater ma-
neuverability, semi-organic compounds for
hull construction, and more sophisticated
electronics and AI suites. Outfitting new ves-
sels with these technical advances gifts the
Cyberon with the ability to balance combat
efficiency and economic frugality in their new
generation of combat vessels.
The Base Carrier Mk. III and Light Carrier
Mk. II were the first new warships launched,
and were direct replacements for their pre-
decessors. Close defense of these vessels,
along with the new, larger Titan Carrier, was
left to a task force’s escort ships and the
fighter squadrons assigned to them, with
ship’ weaponry being fitted specifically for
anti-ship duties.
The new Reanimator Transport solved the
issue of needing a large number of individual
replacement AI modules on the front line.
A pair of Mk. II Light Carriers at their staging coordinates (Studio Bergstrom).
10
Thomas Wall Jr (order #6247474)
Their ability to replace damaged or de-
stroyed modules literally moments after an
AI’s demise dramatically decreases the time
taken to complete the repair and refit pro-
cess after a major engagement, allowing
ships to get back into the fight (or stay in it
for an extended period) much faster than
during the previous war.
Worldstar Carrier
The newest vessel in the Cyberon arsenal is
the Worldstar Carrier. It is the largest mo-
bile vessel in known space, and is capable of
functioning as both a heavy warship and as a
mobile starbase. Its repair bays stow a com-
pliment of Harpy and Tempest class ships
for fire support and escort duties, and its
three full wings of 4 fighter groups each can
devastate most enemy forces without assis-
tance.
While only one Worldstar has been ob-
served conducting active combat operations,
it is rumored that other vessels of this class
are in various stages of completion.
 special
rules
The special rules included in this section
should be used when playing scenarios and
CG battles involving vessels included in this
Fleet Pack. Additionally, it is recommended
that the Ablative Armor/Shields Alternate
Damage rule (TFZv2, section 1.0, p. 2) be
used for all scenarios and CG battles pre-
sented in this book.
Note: the Shields icon on data cards
for the ships of the United Colonies in-
dicates a Particle Shield value (TFZv1,
section 12.2, p. 19) that is effective only in
the possessing ship’s Port and Starboard
target arcs.
Cyberon vessel data cards contain no
Shields icon as they have no Shields values of
any type.
Fighter Disengagement
Fighter groups may attempt to disengage
from a Dogfight at the conclusion of the first
or second Dogfight combat round during its
own activation. Roll the lowest Pilot Quality
die of all the squadrons in the group, using
the following modifiers for the die roll:
+1: Majority of friendly squadrons are Nim-
ble;
Majority of enemy squadrons are Bricks;
-1: Majority of friendly squadrons are Bricks;
Majority of enemy squadrons are Nimble;
Each enemy squadron with at least 2
damage box rows in excess of the number of
friendly squadrons involved.
+/- x: Add or subtract the difference be-
tween the MV values of the friendly fighter
squadron with the lowest MV rating in the
group and the enemy fighter squadron with
the highest MV rating in its group.
If the modified die total is 4 or higher, the
group successfully disengages from the Dog-
fight.
Thomas Wall Jr (order #6247474)
Fighter groups that successfully disengage
after the first round of a Dogfight may use
up to 2/3 (rounded down) of their printed
MV rating; those that successfully Disengage
after their second Dogfight round may move
up to 1/3 (rounded down) of their printed
MV rating. Boosters (if available) may be
used normally for any post-Dogfight move-
ment.
Failing to Disengage
Fighter groups that fail a disengagement die
roll reduce their Pilot Quality die by one die
type when resolving their next Dogfight com-
bat roll (only).
Post-Dogfight Movement
Fighter groups that have eliminated all ene-
mies in a Dogfight after the first combat
round of the friendly fighter group’s activa-
tion to move up to 2/3 (rounded down) of its
printed MV rating. Those that eliminate all
enemies during the second Dogfight round
of a friendly activation may move up to 1/3
(rounded down) of their printed MV rating.
Fighter groups that use any amount of post-
Dogfight movement may not initiative anoth-
er Dogfight during the same activation.
Escort Drone Interception
Fighter squadrons or Small ships on Escort
duty may use Direct-Fire Drone Interception
(TFZv1, 11.4, p. 17) on behalf of their
Charge. An escort must have the firing ene-
my ship within its direct-fire weapon’s firing
arc to attempt such weapons usage. Add
one point to the Drone’s Defense rating for
any such attempted interception.
Small ships and fighter squadrons may also
use Direct-Fire Drone Interception to at-
tempt to intercept Drones fired at a planet,
moon, or Asteroid Marker for purposes of
Planetary Bombardment (see below). All
such usage of a vessel’s weapons must be
11
 within normal printed weapons ranges, and
the weapon’s firing arc must be able to inter-
sect an imaginary line drawn from the vessel
launching the Drone(s) and the planet/
moon/asteroid targeted by that attack. Add
one point to the Drone’s Defense rating for
any such attempted interception.
Particle Shields Offensive Damage
If a Cyberon (only) fighter/shuttle squadron
moves within a number of inches of a UC
ship with Particle Shields in its Port or Star-
board target arc that is less than or equal to
that Shield’s current Shield Rating, roll a d6
for that squadron; add the ship’s current
Particle Shield rating to the amount rolled on
the die. If the total is 7 or higher, the squad-
ron immediately loses d4 damage boxes. A
single squadron rolls only once per activation
for each Shield area of an enemy ship
through which it moves; it cannot be dam-
aged twice by a single Shield facing in a sin-
gle activation, nor does a squadron sustain
damage during a ship’s activation due to hav-
ing a Cyberon squadron in one of its Shield
arcs along its movement path.
One possible representation of a UC Columbia Battle Carrier and escorts (Brigade Models).
12
Thomas Wall Jr (order #6247474)
Drone Damage
Ignore the -1 Damage die modifier for
Drones (Gauss) listed on the Weapons Effect
Table when conducting games solely with
ships in this module.
Emergency Decompression
All Fires (TFZv2, section 4.0, p. 3) on a ves-
sel may be extinguished by issuing an Emer-
gency Decompression order to the vessel at
the beginning of its activation. If this is done,
immediately remove all Fire markers from
the vessel. While under Emergency Decom-
pression orders, the ship may not choose to
execute any Maneuvers, fire weapons, per-
form any Damage Control functions, or
launch/land fighter/shuttle squadrons.
After removing any Fire counters from the
vessel, roll a d8 for each remaining Crew
damage box on the vessel’s data card; sub-
tract one from the die roll if the vessel has
an undamaged Crew Bulkhead on its data
card. Destroy one Crew damage box
(excluding Crew Bulkheads) for each die total
of 7 or more.
 scenario 1:
The Long road
Introduction
The Terminus Campaign was a concerted offensive conducted by the UC during the First War. Its objective: to
destroy the Cyberon forward operating bases in the Tranator and Terminus systems. Early in the operation,
aggressive forward reconnaissance revealed a long-range listening post in the Moneus system. An assault fleet
was dispatched to take out the post and its defenders to allow the UC to conduct its fleet movements with
greater operational secrecy.

Game Length
8 game turns.

Forces
United Colonies: 2x Columbia Battle Carriers (Group 1A loadout), 3x Ophion, 1 squadron of 3x Hellfire, 2 squad-
rons of 2x Orestes.
Cyberon: 1x Base Carrier Mk. I, 1x Infiltrator, 1 squadron of 4x Tempest, 1 squadron of 2x Harpy.

Map

UC UC
Player Player
Set-Up Set-Up
Area Area

Setup
Beginning with the Cyberon player, alternately place 4 randomly selected Asteroid markers. No marker may be
placed further than 12” from another marker.

After Asteroid placement, the Cyberon player deploys his entire force anywhere within the radius of effect of
one or more of the Asteroid markers. The UC player then deploys his forces in either or both of the set-up are-
as marked on the map.

Special Rules
All Cyberon forces begin the game operating under the restrictions of Readiness Level 0 ( TFZv2, p. 54).

The UC player is the initiative player on game turns 1, 2, and 8. Roll normally for initiative on all other game
turns.

No vessel may conduct a Form Jump Point maneuver until game turn 8.

This scenario is played on a Limited Map (TFZv1, p. 33).

Victory Conditions
The UC player wins by Capturing, Hulking, or Destroying the Cyberon Infiltrator by the end of the game.

13

Thomas Wall Jr (order #6247474)

 scenario 2:
nightfall
Introduction
As part of the initial wave of attacks that ended the Armistice, a Cyberon task force was ordered to destroy the
UC colony on Sagittarius V.

Game Length
10 game turns

Forces
United Colonies: 1x Mercury, 1x Columbia (R), 1x Berserk (R), 1 squadron of 2x Antaron, 1 squadron of 4x
Orestes. All vessels begin with their full, printed fighter loadouts.
Cyberon: 1x Titan Carrier, 3x Base Ship Mk. III, 2x Light Carrier Mk. II. All ships use Group 3 fighter loadouts.

Map
Cyberon
Player
Set-Up

UC
Player
Set-Up

Setup
Place one 4” planet in the center of the table. The UC player then places a 1” moon anywhere on the table that
is at least 6” away from any edge of the table and no closer than 12” to the planet.

The UC player then places all of his forces on the table within 8” of the planet and/or within 6” of the moon. The
Cyberon player places his forces in the area indicated on the map after all UC vessels have been placed.

The Cyberon player is the initiative player on game turn 1. Roll normally for initiative each turn thereafter.

Special Rules
This scenario uses a Limited Map (TFZv1, p. 33).

All UC forces begin the game under the conditions of Readiness Level 1 ( see TFZv2, p.55).

No vessel may attempt to Disengage from this scenario.

Cyberon vessels may fire their Drones at the planet during any friendly ship or squadron activation. All Drones
fired at the planet hit it automatically; no To Hit roll is required. Roll each Drone’s damage die and keep a run-
ning total of all Drone damage inflicted against the planet.

Victory Conditions
The Cyberon player wins by inflicting 400 or more points of damage from Drone attacks against the planet by
the end of the game.
14

Thomas Wall Jr (order #6247474)

 CG scenario 1:
the first war
Introduction
It is the middle of the sixth year of the First War, a war that has been costly in terms of men and materials, and
has seen both sharp, rapid combat operations and lulls in the action as both sides regroup to plan new opera-
tions. After their initials gains, the Cyberon have been unable to advance against the core worlds of the United
Colonies, with both sides having settled in for a long war of attrition.

Game Length
16 CG Turns.

Forces
The United Colonies player begins the CG with 32,500 points with which to purchase his initial vessels; the
Cyberon player begins the CG with 28,000 points to purchase his initial forces.

Al vessels purchased prior to the commencement of the CG must be available in the E1 and M1 periods of the
war, and may not be purchased in excess of the percentages allowed by the Availability rating ( Common, Un-
common, or Rare) of each category as found with the Master Ship Charts for each player (see Appendix I).

Map
The entire CG map is in play. The Cyberon player begins the CG Controlling the following systems: Tranator, Sci-
on 831, Terminus, Marus, Eraseus, Pisceus, Moneus, Ea 19, and Epsilon 441. All other systems begin the
game under UC Control.

The following systems are designated as Shipyards: Terminus, Tranator, Helios Gamma, and Scorpius.

Setup
The UC player may create and place a maximum of one TF in each system under his control.

The Cyberon Player may create and place a maximum of one TF in each system under his control, and may
place up to two TF in the In Transit box of the CG map. TF placed in the In Transit box (if any) must have their
movement and orders plotted beginning from one turn prior to the start of the CG (CG turn ‘zero’), may be plot-
ted as originating from any Cyberon-controlled system, and may contain no more than 20% (combined) of the
Cyberon player’s starting PV as measured by the PV total of the vessels in the TF. These TF are considered to
have competed one CG turn of movement at the beginning of the CG.

Special Rules
1. Players receive RP at the beginning of the first Repair Phase of CG turns 5, 9, and 13 (see rule 3).
2. The Time Unit used for this CG is one Quarter (3 months, or one QTU).
3. Due to the length of the xTU, players perform two Repair Phases during each CG turn, and add 2 to the stat-
ed FTL ‘z’ component numbers as found with the Master Ship Charts (see Appendix II).
4. LRS numbers for a TF are based on the values given to specific vessels in the amounts found on the Master
Ship Chart. Fighter/Shuttle groups that do not contain the listed (nominal) number of squadrons for that group
type have a LRS value of zero.
5. Beginning with CG game turn 9, both players may purchase vessels indicated as being available in the ‘L1’
column of their Master Ship Chart entries.
6. All battles occur on 6’ x 4’ tables, and use the Limited Map table restriction (TFZv1, p.33) when any Planet,
Moon, or Asteroid Marker is placed on the tabletop. When placing terrain prior to a battle, no moon may be
placed within 12” of a planet or other moon, and no planet may be placed within 24” of another planet of the
same system. Terrain is always placed by the player who begins the battle in Control of the system.

CG Victory Conditions
A player must Control all of the following systems at the end of CG turn 16 to win the game: Terminus, Trana-
tor, Geminus, Helios Alpha, and Helios Delta. If one player does not control all of these systems, the game is a
draw.

15

Thomas Wall Jr (order #6247474)

 CG scenario 2:
homecoming
This CG re-created the opening days of the Second War, wherein the Cyberon initiated the war with complete
strategic surprise.

Game Length
6 CG turns.

Forces
The UC player begins the game with 25,000 points with which to purchase his vessels; The Cyberon player
begins the game with 20,000 points with which to purchase his vessels.

All vessels purchased by either player must be listed as available in the ‘E2’ column of their entries on the Mas-
ter Ship Chart (Appendix I).

Map
Play is limited to the following systems on the CG Map: Sagittarius, Helios Gamma, Helios Beta, Helios Alpha,
Helios Delta, Librus 512, Geminus, and Pisceus. All systems begin Controlled by the UC player.

Setup
The UC player must create and place one TF in each system under his control, with no single TF containing
ships with a total PV of more than 25%, nor less than 10%, of his initial purchase point total.

The Cyberon player must create a minimum of 4, and a maximum of 6 TF, allocating his vessels as he sees fit
to each TF. See the CG Special Rules for Cyberon initial TF deployment.

Special Rules
1. RP are not received by players during any turn of this CG.
2. The Time Unit of this CG is one-half day (1/2DTU). As such, the Repair Phase of the CG turn is omitted on
CG game turns 2, 4, and 6.
3. After the UC player has deployed his TF markers and the Cyberon player has determined the contents of his
TF markers, the Cyberon player may force the UC player to reveal the exact contents of up to four UC TF mark-
ers of the Cyberon player’s choosing. The Cyberon player then places his TF markers in any UC-controlled sys-
tem, with no more than one TF placed per system, and having Control orders assigned to each of them at the
beginning of the game.
4. Any UC TF that is not in a system with a Cyberon TF marker may plot movement during the Movement
Phase of the first CG turn, but no TF may arrive at its destination prior to CG Turn 2. Play then begins with the
Combat Phase of turn 1, with all Cyberon TF having arrived at their destinations. All UC TF in system with
Cyberon TF begin the game under Refit mission orders.
5. In all battles fought on CG turn 1, the UC player’s forces begin play under the conditions of Readiness Level 0
(TFZv2, pp. 54-55).
6. All battles occur on 6’ x 4’ tables, and use the Limited Map table restriction (TFZv1, p.33) when any Planet,
Moon, or Asteroid Marker is placed on the tabletop. When placing terrain prior to a battle, no moon may be
placed within 12” of a planet or other moon, and no planet may be placed within 24” of another planet of the
same system. Terrain is always placed by the player who begins the battle in Control of the system on CG turns
2 and later; the Cyberon player may place terrain (under the above restrictions) for any battle that occurs on
CG turn one.
7. Should a Cyberon TF find itself in a system unopposed by any UC forces, it may conduct Planetary Bombard-
ment attacks against a planet in the system for a maximum of ten (10) game turns. There is no need to set up
the table to resolve these attacks; simply roll the number of available Drone attacks, check for Drone depletion
(Reload Racks may be used normally), and record the damage inflicted by each attack.

Victory Conditions
The Cyberon player wins the game if he reduces the RP value of at least 6 planets in the playing area to zero by
the end of CG turn 6; the UC Player wins the game by eliminating a minimum of 15,000 points (measured in
PV) of the Cyberon fleet by the end of CG turn 6. Any other result is a draw.
16

Thomas Wall Jr (order #6247474)

 campaign game
special rules
Unless stated otherwise, the following spe-
cial rules are in effect for the two CG pre-
sented in this booklet.
Vessel Special Attributes
During the Repair Phase, certain vessels
grant players additional repair capabilities.
These vessels must be part of a TF that is In
Transit or has Refit orders during that CG
turn to use these special abilities, and PV
Reserve points must still be expended when
required to perform specific repairs as stat-
ed in the Repair Phase rules (TFZv2, pp. 57-
58). All listed capabilities are granted in addi-
tion to those already available to vessels un-
der the normal Repair Phase rules, and each
may be performed more than once for a sin-
gle vessel so long as the requisite numbers
of appropriate systems are available to do
so.
Cargo and Medical Bays repaired aboard the
listed ships are considered to be accom-
plished at the end of the Repair Phase, after
all other repairs have been completed; newly
repaired Cargo and Medical Bays may not
be used to grant additional repair abilities
during the same Repair Phase in which they
are themselves repaired.
Note also that each additional function may
be performed once per Repair Phase per
Bay of the appropriate type on each listed
ship, and any number of repaired damage
boxes granted by a die roll in excess of a ves-
sel’s printed capacity are lost (i.e., they may
not be allocated to another vessel or saved
for later use).
The specific vessels and their capabilities
are:
UC Supply Tender
Each intact Cargo Bay aboard a Supply Ten-
der allows the UC Player to perform any of
the following tasks during the Repair Phase:
Thomas Wall Jr (order #6247474)
 Automatically repair a ‘last hit’ or two
other hits to a ship’s, Distributor,
Weapons, Shields, EW Primary sys-
tems, Bulkheads, and any secondary
systems excepting FTL and Marine
Teams.
 Roll an additional die of the appropri-
ate type to repair Ablative Armor
damage aboard a ship, or allow a ship
without the appropriate systems (as
listed in the 2nd bullet point of the Re-
pair Phase rule) to roll a die to repair
Ablative Armor damage as if it pos-
sessed one of those systems.
 Repair a small vessel as if the Cargo
Bay were a Repair or Auto-Repair
Bay.
 Re-roll up to two failed Drone or Re-
load Rack replenishment die rolls.
UC Fuel Tender
Each intact Cargo Bay aboard a Fuel Tender
allows the UC Player to automatically repair
a ‘last hit’ or two other hits to a ship’s
Thrust, Maneuver, or Distributor primary
systems or its FTL secondary system during
the Repair Phase.
UC Hospitium
Each Medical Bay aboard a Hospitium allows
the UC player to:
 Roll a die to repair any (including
‘first’ and ‘last’, excepting Crew Bulk-
heads) destroyed Crew box aboard a
friendly ship as if that ship possessed
a Medical Bay (TFZv2, p. 26).
 Purchase and immediately deploy
Crew replacement points to friendly
vessels, with one Medical Bay being
capable of deploying two such re-
placements during a single Repair
Phase.
 Expend 10 points from his PV Re-
serve to repair d4 Marine Teams on
17
 a friendly vessel, with up to 4 such die
rolls permitted per Repair Phase per
Medical bay used for this purpose.
Note that the number of Medical Bays
aboard a Damaged Hospitium is reduced by
half (to an available total of 3).
Cyberon Supply Tender
Each intact Cargo Bay aboard a Cyberon
Supply Tender permits the use of any special
rule granted to the UC Supply Tender, Fuel
Tender, and Hospitium vessels as stated in
this rules section.
Cyberon Reanimator Transport
Each undamaged Passenger Compartment
aboard a Reanimator Transport permits the
Cyberon player to do one of the following:
 Repair d6 non-Bulkhead Crew hits or
d8 Marine Teams on a single vessel
without expending any PV Reserve or
Crew replacement points.
 Repair d10 damage boxes of any
fighter squadron without expending
any points from his PV Reserve.
Replacement Points
Each system on the CG Map is assigned a
Replacement Point (RP) value. When di-
rected by a CG’s special rules, each player
totals the RP value of all systems he Con-
trols (as defined under CG Victory Condi-
tions, TFZv2, p. 58) and adds this amount to
his PV Reserve point total.
Note: to use this (and the associated) rules
section(s) in player-created CG, RP totals are
assigned to each system on the CG map ac-
cording to the following schedule:
 50 RP for each listed inch of each
planet’s size in the system;
 25 RP for each listed in of each
moon’s size in the system;
 10 RP for each Asteroid Marker in
the system.
Shipyards
Players may use points from their PV Re-
serve to purchase new vessels during a CG
18
Thomas Wall Jr (order #6247474)
in which use of the Replacement Points rule
is specified. To purchase new vessels, the
owning player simply chooses which vessels
he wishes to add to his Fleet Roster and de-
ducts the vessel’s PV from his PV Reserve
point total.
New vessels may only be purchased at the
end of the Repair Phase of a CG turn in
which Replacement Points were added to
the players’ PV Reserve totals, and become
available to the owning player at the begin-
ning of the next CG turn. Vessel Rarity
(Common, Uncommon, or Rare) is ignored
when purchasing new vessels during a CG,
but any vessel purchased must be listed as
available during the CG’s stated time period.
Each CG will specify certain player-controlled
systems as having Shipyards. Newly pur-
chased vessels may only be placed in a
friendly-Controlled system designated as hav-
ing a Shipyard. Systems designated as hav-
ing a Shipyard do not lose this capability if or
when Control of the system changes from
one player to another.
Players may designate additional star sys-
tems as Shipyards during a CG. To do so, a
player must Control the system during the
Repair Phase of the CG turn and expend
1500 PV from his PV Reserve to designate
a single, specific star system as a Shipyard.
Beginning with the following CG Turn, that
star system gains all the capabilities of a
Shipyard for the duration of a CG.
Note: in ‘fixed’ CG that list specific systems
as having Shipyard capabilities (such as the
ones presented in this book), Shipyards may
not be created at the time players purchase
their initial CG fleets; they may only create
additional Shipyards during eligible Repair
Phases after commencement of the CG.
Shipyards may be dismantled at the begin-
ning of a Repair Phase in which a player Con-
trols a Shipyard-designated star system by
simply announcing that he is doing so to his
opponent. No PV Reserve points are re-
claimed by doing this, and a system loses its
 Shipyard capabilities immediately upon a
qualified player’s declaration.

Planetary Bombardment
Planets, Moons, and Asteroid Markers may
be attacked by Drones during any CG sce-
nario to reduce their RP value. Such attack
always hit their targets (providing the
planet/moon template or Asteroid Marker
is within the firing weapon’s Extreme range)
without requiring a To Hit die roll.

Roll the damage die for each Drone when

resolving its attack, subtracting one point
from the die roll for each Weapons damage
hit sustained by the firing vessel (subtract 3
points from the damage die if fired from a
Damaged Small ship). Track a cumulative
dice roll total for each individual planet,
moon, or asteroid marker attacked in this
manner.

At the conclusion of the CG scenario, reduce

the system’s RP value by half (rounded
down) of the total amount of damage inflict-
ed by Drone attacks against each target, but
never by more than the original (or current,
if previously bombarded) RP value of each
target in the system as based on the values
calculated via the notes section of the Re-
placement Points rule above. Note that play-
ers will need to track damage to individual
targets in each system during a CG so as to
avoid inflicting more damage against a single
target in terms of RP than is it capable of
nominally producing.

An RP Tracking Sheet is provided in Appen-

dix I that contains RP entries for all systems
by terrain type present.

Scenario Terrain
Refer to the CG Map Terrain Table (Appendix
I) when setting up the table for playing out
CG battles in each system. All terrain place-
ment rules apply normally.

Note that a Planet, Moon, or Asteroid Mark-

er that has its RP value reduced to zero is
still placed on the tabletop for each and eve-
ry battle in that system.

19

Thomas Wall Jr (order #6247474)

 appendix I
master
ship
charts
CG maps
and Tables

20

Thomas Wall Jr (order #6247474)

 MASTER SHIP
CHARTS
There is one Master Ship Chart for each faction
presented in this Fleet Pack. Each Master Ship
Chart includes the following notations:
CLASS: the class of vessel being delineated on
that line entry.
PV: the Game Point Value of the ship without fight-
ers. or other auxiliary vessels.
LOADOUT: the number and type of fighter groups,
if any, that are normally based on that vessel.
Note that most ships stow their assigned fighter
groups on their Flight Decks and/or in Fighter
Racks; fighter groups in excess of this capacity
are stored in any available Hangar Bays. The own-
ing player may choose which fighters are stowed
in a particular ship location, but must do so prior
to the beginning of any battle.
The ‘OR’ qualifier allows the player to choose
which of the presented options will be loaded onto
each ship of this type. if more than one ‘OR” option
is present, he must choose both of the original
(first) entries OR both of the optional (second) en-
tries when outfitting this ship with its fighter com-
plement.
PV (LADEN): the Game Point Value of the ship in-
cluding the PV of its listed fighter complement.
Two values are present if there are one or more
options present in the LOADOUT section notes.
GROUP (GRP) TYPE: a numeric designation to
help differentiate between the available types of
fighter groups.
COMPOSITION: the number and type of fighter/
shuttle squadrons that comprise a particular type
of fighter group. The PV cost of a fighter group
includes the cost of all component fighter and/or
shuttle squadrons.
SLOTS: the number of Fighter Slots used by that
fighter group when at full strength.
AVAILABILITY
If playing a ‘historical’ game, players should
choose the era in which their battle will take place.
There are five different eras that can be chosen:
Early, Middle, or Late First War (E1, M1, and L1,
respectively), and Early or Current Second War
Thomas Wall Jr (order #6247474)
(E2 and C2). The colored boxes preceding each
vessel’s CLASS or GROUP entry indicates the
availability of that ship class or fighter group in the
respective time periods.
Black entries show the vessel as being unavailable
in the chosen era.
A green entry indicates the vessel or group is
Common; any number of this type of vessel/group
may be taken during this era.
A gold entry shows this type of vessel/group to be
Uncommon during the indicated era. No more
than 1/3 of a player’s PV may be used to pur-
chase Uncommon vessels/groups during a single
game or CG, but there is always a minimum of
one Uncommon ship available (regardless of PV
cost, and including the cost of any Uncommon
fighter groups that may be stowed aboard that
single ship).
A red entry indicates this vessel/group is Rare in
this era. No more than one Rare vessel (along
with any Rare fighter groups which may be as-
signed to that vessel) may be present in a single
(Non-CG) battle. When purchasing forces for a
CG, no more than 20% of a player’s starting fleet
PV may be allocated to the purchase of Rare
ships or fighter groups.
LONG-RANGE SENSOR (LRS) RATINGS
Certain vessels have their entries shaded in light
blue or light green. When playing a CG, each ship
or fighter group shaded in light green has a LRS
‘x’ value of 1/2; those shaded in light blue have a
LRS ‘x’ value of 1.
FTL ‘z’ VALUES
When playing a CG, all UCM ships equipped with
an FTL system are considered to have FTL/Imp/
S/3 values for their FTL systems; fighters with
the FTL Attribute are treated as having FTL/2
entries.
All Cyberon ships with FTL entries are treated as
having FTL/A/S/4 values during First War sce-
narios, and FTL/A/S/6 values during Second
War CG for those systems. Cyberon fighters with
FTL Attributes use FTL/3 values for First War
games, and FTL/4 entries during Second War
battles.
21
 capital ships and escorts
E M L E C
1 1 1 2 2 CLASS PV LOADOUT PV (LADEN)
Achilles 573 1x Group 4, 1x Group 2A 1206
Agamemnon 618 3x Group 4, 2x Group 2A 2241
Antaron 138 1x Group 2 OR Group 2A 374/414
Atlantia 759 2x Grp 1 OR 1A, 1x Grp 2 OR 2A 1537/1601
Berserk 310 1x Group 2A 586
Berserk (R) 357 1x Group 2A 633
Columbia 452 2x Grp 1 OR 1A, 1x Grp 2 1230/1242
Columbia (R) 495 2x Group 4, 1x Group 2A 1485
Fuel Tender 73 None 73
Hecate 193 2x Raptor Mk. I 311
Hector 423 1x Group 2A 699
Helios 2119 5x Group 4, 1x Group 2A, 1x Group 3 4274
Hellfire 92 None 92
Hospitium 80 1x Group 3 172
Mercury 974 3x Group 4, 1x Group 2A, 1x Group 3 2415
Neptune 174 1x Group 2 410
Ophion 283 1x Group 3 377
Orestes 60 None 60
Orion 332 2x Raptor Mk. I 450
Valkyrie 305 1x Group 1 OR 1A, 1x Group 2 812/824
Valkyrie (R) 340 1x Group 4, 1x Group 2A 973

fighters
E M L E C
1 1 1 2 2 CLASS PV
Heavy Raptor 47
Raptor Mk. I 59
Raptor Mk. II 69
Viper Mk. II 54
Viper Mk. IIA 58
Viper Mk. VI 73

fighter groups
E M L E C
1 1 1 2 2 GROUP TYPE COMPOSITION SLOTS PV
1 3x Viper Mk. II, 2x Raptor Mk. I 4 271
1A 3x Viper Mk. IIA, 2x Raptor Mk. I 4 283
2 4x Raptor Mk. I 2 236
2A 4x Raptor Mk. II 2 276
3 2x Heavy Raptor 2 94
4 3x Viper Mk. VI, 2x Raptor Mk. II 4 357

Thomas Wall Jr (order #6247474)

 E M L E C
capital ships and escorts
1 1 1 2 2 CLASS PV LOADOUT PV (LADEN)
Base Carrier Mk. I 1124 4x Group 1 OR 4x Group 2 1812/2020
Base Carrier Mk. II 703 4x Group 1 OR 4x Group 2 1391/1599
Base Carrier Mk. III 778 3x Grp 3 OR 3A, 1x Grp 4, 1x Grp 6 1743/1779
Harpy 109 None 109
Helan 201 1x Group 4 331
Infiltrator 489 2x Group 2 937
Infiltrator (R) 566 1x Group 3A, 1x Group 6 947
Light Carrier Mk. I 444 3x Group 1 OR Group 2 960/1116
Light Carrier Mk. II 613 2x Grp 3 OR 3A, 1x Grp 4, 1x Grp 6 1345/1369
Medusa 277 1x Group 2 OR 1x Group 3A 501/522
Reanimator 136 2x Group 6 408
Siren 81 1x Grp 1 OR Grp 3A, 1x Heavy Raider 321/394
Supply Tender 174 None 174
Tempest 99 None 99
Titan Carrier 1347 5x Grp 3A, 1x Grp 4, 1x Grp 6 2838
WorldStar Carrier 4533 12x Grp 3A, 2x Grp 4, 1x Grp 5, 2x Grp 6 8247

fighters
E M L E C
1 1 1 2 2 CLASS PV
Heavy Raider 68
Raider Mk. I 43
Raider Mk II 52
Raider Mk. III 55
Raider Mk. IIIA 59
Raider Scout 65

fighter groups
E M L E C
1 1 1 2 2 GROUP TYPE COMPOSITION SLOTS PV
1 4x Raider Mk. I 4 172
2 3x Raider Mk. II, 1x Heavy Raider 4 224
3 3x Raider Mk. III, 1x Heavy Raider 4 233
3A 3x Raider Mk. IIIA, 1x Heavy Raider 4 245
4 2x Raider Scout 2 130
5 3x Raider Mk. IIIA, 1x Raider Scout 4 242
6 2x Heavy Raider 2 136

Thomas Wall Jr (order #6247474)

 Omaris 6
Epsilon 441
847A -24
Helios Gamma
Sagittarius
Helios Beta 87 Reticuli
Oerlikus
Thraclus
Helios Alpha
Helios Delta
Scorpius

Thomas Wall Jr (order #6247474)

Flesh and Steel Campaign Map
 (Cut along the artwork edge; align this map panel on top of the first hex row of the first map panel.

Ea 19

Thomas Wall Jr (order #6247474)

Geminus

Moneus

Librus 512

Eraeus

Pisceus

Marus Terminus
In Transit

Scion 831

Tranator
 CG Map Terrain Table cg turn
SYSTEM PLANETS MOONS ASTEROIDS RADIATION RP record track
847A-24 - - 6 High 60

Thomas Wall Jr (order #6247474)

87 Reticuli - 1x 2” 8 - 130
Ea 19 1x 4” - - - 200
1 2 3 4
Epsilon 441 1x 6” 1x 2” - - 325
1x 1”
Eraus - - 10 - 100 5 6 7 8
Geminus 1x 6” - 4 - 490
1x 3”
Helios Alpha 1x 4” - 6 Elevated 260 9 10 11 12
Helios Beta 1x 4” 3x 1” - - 275
Helios Gamma 1x 2” - 8 - 180
Helios Delta 1x 6” 1x 2” - Elevated 375 13 14 15 16
1x 1”
Librus 512 1x 2” - 8 - 180
Marus - 1x 3” - Lethal 75
Moneus - - 4 - 40
Oerlikus - 1x 4” - - 100
Omaris 6 - - 10 - 100
Pisceus 1x 4” 2x 1” - - 250
Sagittarius 1x 4” 1x 1” - - 225
Scion 831 - - - Elevated 0
Scorpius 1x 6” - 3 - 330
Terminus - 1x 6” 6 - 210
Thraclus - 1x 2” - - 50
Tranator 1x 6” - - High 300
 Flesh and Steel CG
RP Tracking Charts
SYSTEM PLANETS PLANETS MOONS MOONS Asteroids Asteroids SYSTEM
(Nominal) (Current) (Nominal) (Current) (Nominal) (Current) RP TOTAL
(Current)
847A-24 0 0 - 0 60 (6x10)
87 Reticuli 0 0 1 (50) 80 (10x8)
Ea 19 1 (200) 0 0
Epsilon 441 1 (300) 1 (50) 1 0 0
2 (25) 2
Eraus 0 0 0 0 100
(10x10)
Geminus 1 300 1 0 0 40 (4x 10)
2 150 2
Helios Alpha 1 (200) 0 0 60 (6x10)
Helios Beta 1 (200) 1 (25) 1 0 0
2 (25) 2
3 (25) 3
Helios Gamma 1 (100) 0 0 80 (10x8)
Helios Delta 1 (300) 1 (50) 1 0 0
2 (25) 2
Librus 512 1 (100) 0 0 80 (10x8)
Marus 0 0 1 (75) 0 0
Moneus 0 0 0 0 40 (4x10)
Oerlikus 0 0 1 (100) 0 0
Omaris 6 0 0 0 0 100
(10x10)
Pisceus 1 (200) 1 (25) 1
2 (25) 2
Sagittarius 1 (200) 1 (25) 0 0
Scion 831 0 0 0 0 0 0 0
Scorpius 1 (300) 0 0 30 (3x10)
Terminus 0 0 1 (150) 60 (6x10)
Thraclus 0 0 1 (50) 0 0
Tranator 1 (300) 0 0 0 0

Thomas Wall Jr (order #6247474)

 appendix II
vessel
data
cards
The data cards for Task Force Zeta have been updated with improved graphics, and include
icons in place of text to denote basic ship statistics. These icons are described below, along
with applicable notes for Large and Oversized vessels and damage tracks.

ship Icon legend starbase icons

Thrust Rating
B = Basic; I = Inertial; G= Gravitic reactor rating

MANEUVER RATING starbase rotation

Vessel SIGNATURE

ELECTRONIC WARFARE
(EW) RATING Damage tracks
SHIELD RATING
A ‘dX’ entry indicates an Ablative The Thrust, Maneuver, Shields, EW, and
Shield’s Regeneration rate/die type Reactor damage tracks show the cur-
rent value of each system based on sus-
Armor RATINGs tained damage. Mark these boxes nor-
‘A’ entries in all boxes indicate mally (right to left);. The final (red-shaded)
Ablative Armor box of each track is not marked; it is
DAMAGE/Usage BOXES placed to serve as a reminder that the
Blue = Bulkhead system may no longer be repaired during
Red = Shield Generator or last hit the game by Damage Control or Auto-
Repair systems. The Thrust damage
track shown above can sustain three hits
before becoming unrepairable.
FIGHTER Icon legend
The non-graphic (‘basic box’) damage
tracks are used in the same manner as
Movement RATING with the previous data cards; when the
very last (red) box is marked, the system
is completely destroyed/unrepairable.
DEFENSE RATING
oversized vessels
Oversized vessels track information on
Armor RATING two separate cards, the second of which
is marked ‘2 of 2’ at the top of the se-
cond card. The first card contains all of
SLOT RATING the vessel’s basic stats and systems on
the front side, and weapons data
(including damage tracking) on the re-
PILOT QUALITY verse.
‘+’ = Veteran; T = Trained;
‘-’ = Green; ‘C’ = Civilian;
The second card shows the primary
systems damage on front, and secondary
DAMAGE/Usage BOXES systems damage on the back of the card.
Green = Booster; Gold = Chaff
Purple = Heavy Weapons;
Red = last hit
28

Thomas Wall Jr (order #6247474)

Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
Thomas Wall Jr (order #6247474)
 Be sure to check out the other tabletop gaming titles from
Legionnaire Games!

Strike Legion Tactical Game Series

Strike Legion Main Rulebook
$12.99 (PDF) $29.95 (Print)
Command a combined arms ground force from any
future you wish to imagine! Strike Legion combines
simple game mechanics with a unique, integrated
electronic warfare system and a respectable amount
of unit detail and variation - and all without sacrificing
playability.
Strike Legion: The Genome Gambit
$7.99 (PDF) $22.95 (Print)
Strike Legion: The Genome Gambit increases the depth and
scope of your fictional wars by adding fully customizable
xenomorphs (or plain old "bugs"), genetically modified "super
soldiers", and bio-mechanoid units and technology. Special-
ized command rules for truly "alien" species provide new
challenges and opportunities to play out in front of you on
your tabletop. Includes construction addenda to create your
own custom armies.

Strike Legion: Strike Legion: Skunk Works

The Clockwork Armies
$6.99 (PDF) $21.95 (Print)
Strike Legion: The Clockwork Armies provides every-
thing needed for players to fight battles in an alternate
or historical past. Drawing from both historical
sources and Victorian-era science fiction, players can
field armies of sky, land, and sailing ships alongside
troops armed with rifles and muskets, swords, bows,
and spears. Also includes Tech Level 8 systems, exper-
imental rules for time-traveling forces, and expanded
construction options for creating your own forces.
$9.99 (PDF) $29.95 (Print)
Strike Legion: Skunk Works provides players with some
‘advanced’ game options for play, such as Scout EW, aimed
shots, tank riders, more Walker/Mecha construction and
play variations, and many new types of artillery payloads and
missile warheads. New sections also include the use of
psionic troops or individuals, new vehicle systems and per-
sonnel attributes, and guidelines for playing the Strike Legion
tactical series as a solitaire game. Includes a consolidated
unit construction section that includes all options from the
entire Strike Legion Tactical series to date.

Strike Legion Operational Series

Strike Legion: Planetary Opera-
tions
$14.99 (PDF) $37.95 (Print)
Strike Legion: Planetary Operations takes combat to a higher
level, with units representing battalions instead of platoons.
Combat emphasizes the command and training abilities of each
player’s troops in the field over technological differences
(though these do play their part). Every type of unit that can be
fielded in the Strike Legion Tactical series is represented here,
along with rules for specialist troop types such as scouts, artil-
lery, combat engineers, and others.
The War That Never Was
$6.99 (PDF) $19.95 (Print)
The War That Never Was is an operational-level look at
what World War Three could have been if fought in the
late 1980’s. Contains TO&E and data cards for 14
NATO and Warsaw Pact armies, five scenarios ranging
from Denmark to the Dardanelles, and an Operational
Sector campaign game in central Germany.

Strike Legion Small Unit Series

Strike Legion: Platoon Leader - $12.50 (PDF) $29.95 (Print)
Strike Legion: Platoon Leader takes a ‘close-up’ look at futuristic (and historical) combat, with players fielding forces of reinforced-company
size on their tabletops. Squad-level activations allow teams and individual soldiers to take coordinated actions to achieve the mission objec-
tive. Full vehicle support and unit construction sections are included, covering many of the options available to infantry and vehicles in the
Strike Legion Tactical series. One follow-up volume is planned for this rulebook that will add bioengineering options, large vehicles, more
infantry attributes, vehicle systems, and optional rules.

Designed primarily for 15mm miniatures, figure scales between 6mm and 28mm can be used to play the game with minimal modifications.

Task Force Zeta

Task Force Zeta Vol. 1:
Ships of the Line
$12.50 (PDF) $29.95 (Print)
Command a space fleet from any future you wish to
imagine! TFZ combines simple game mechanics with
an integrated electronic warfare system a large
amount of unit detail and variation, and construction
rules for creating your own starships to control the
space lanes!
Task Force Zeta Vol. 2:
Fleet Auxiliaries
$12.50 (PDF) $32.95 (Print)
TFZv2 add multiple optional rules and units, including board-
ing combat, ramming, ship explosions, mine warfare, star-
bases, cargo and personnel transports, anew weapons, and
more to the TFZ game system. Also includes a Sector Cam-
paign game system and Joint Strike rules integrating Task
Force Zeta with Strike Legion to create linked planetary
invasion scenarios.

http://www.LegionnaireGames.com

Thomas Wall Jr (order #6247474)