Professional Documents
Culture Documents
BattleTech - Operation Lancaster V106
BattleTech - Operation Lancaster V106
BattleTech - Operation Lancaster V106
Dedicated to my parents, Rudy & Alice Ramsey, for without them this would not exist—namely because neither would I.
Thank you for everything that I am and everything that I will ever be. I love you both dearly.
- Devin
Bonus Material
Among other objectives, the intent of this large Blakist task force had been
to strike at the nearby Acala system. Once there they would take control of,
or, failing that, destroy the advanced war-making materiel manufacturing
capabilities of Dreadnought Interstellar Industries on Acala III. The Blakist
force would then spread outward like wildfire, opening an entire new theater
of war, dividing the resources of those who opposed the Word of Blake’s will.
While unaware of the true extent of the Blakists’ plans or the inbound elite
Shadow Division dispatched to join the Word of Blake force already present
in the Ashkum system, Dreadnought was acutely aware of the foothold
situation on their proverbial doorstep.
Given the challenge and complexity of the task at hand, as well as the
specific tactical requirements of the strike, the BattleCorps required outside
assistance for a strong chance of success. With Operation SCOUR in the
process of being organized and launched, assistance from House Davion’s
Armed Forces of the Federated Suns was not forthcoming. To accomplish
Operation LANCASTER’s mission, Dreadnought hired not one, but two
separate mercenary commands for their unique skillsets.
The first was the Ronin Free Companies Mercenaries’ “Oni Slayers” and
“Morningstar” Free Companies, working together under the command of
Free Colonel Donaldarus Meridius. This elite, defense-oriented combat unit
was no stranger to digging in and taking a beating while dishing out
horrendous punishment on whoever dared to attack them. Although
referred to as “Free Companies”, these seasoned units were closer to a
combined arms regiment in number when added together. With a potent
combination of ‘Mechs and armor, though only backed by limited aerospace
support, Meridius’ forces were a battlefield presence to be reckoned with.
The following historical articles are included in this document as they contain information pertinent to the various groups involved in Operation LANCASTER. These articles detail how these groups
initially formed (where available) and provide at least some information regarding their activities post-LANCASTER. These articles also provide some context for Operation LANCASTER itself, as they
detail numerous critical events leading up to LANCASTER. Most of the information contained within these articles is not covered in any other publicly-available documentation.
7 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
DREADNOUGHT INTERSTELLAR INDUSTRIES
In 2045, just months after the Sumaire-50 showcased just a small portion of Dreadnought Limited’s potential, the
manufacturer established a contract with the United States government for “Smart Weapons”. This contract led to
branching out into more advanced software, as well as development of more and more intelligent weapon designs for
numerous countries over the following years. In 2051, Dreadnought Limited contributed toward expanding and upgrading
fully automated turrets on orbital defense satellites for the purpose of military defense for multiple countries, preventing
several instances of potentially catastrophic meteor-strikes in the year 2053.
Ten years after moving their home base to Scotland in 2065, Dreadnought Limited made several breakthroughs in
different targeting & tracking systems for dealing with interstellar objects passing near Terra. The following year, in 2076,
significant uses for their targeting and tracking hardware and software were discovered in space exploration.
Dreadnought quickly secured a contract with the civilian International Space Exploration Cooperative, which was
absorbed into the Western Alliance later that year.
In 2083, Dreadnought Limited merged with the industrial manufacturing giant Sharon-Dawn Enterprises and became
an economic powerhouse manufacturer on the forefront of technological development under the new banner of
“Dreadnought Enterprises”. Four years later, Dreadnought was contracted to design and manufacture the first fully
manned, multipurpose orbital defense stations for the newly formed Terran Alliance. Six years later, in 2093, Dreadnought
Enterprises formed an “Interstellar Development Arm” to begin research into the scientific theories published in the early
21st Century by Kearny and Fuchida relating to the possibility of interstellar travel.
Dreadnought Enterprises’ Interstellar Development Arm made a computational modeling breakthrough in the potential
application of a Kearny-Fuchida Drive in 2101, contributing toward the K-F Drive being proven feasible a year later. Having
already invested much in the development of the K-F Drive’s theory and with massive resources at their disposal,
Dreadnought became a key contributor in the Deimos Project in 2103, designing and constructing large sections of the
first K-F Drive, known at the time as the Deimos Hyperdrive. A year later, Dreadnought Enterprises established their first
extraterrestrial manufacturing plant on Luna, geared toward further production of K-F Drive components.
In 2106, Dreadnought Enterprises began to suffer from economic problems toward the end of the Deimos project, as
investors in the massive corporation started to pull their support. Just one year later, Dreadnought Enterprises began to
see the success that some of their former investors had lacked the vision for, and immediately following the successful
jump of Deimos 2, Dreadnought Enterprises suddenly found itself with more financial backing than ever before.
Dreadnought Enterprises landed a long-term contract with the newly formed Terran Space Navy as a manufacturer of
weapons and, in association with Boeing Interstellar, K-F Drives for the then-new Aquilla-class JumpShips in 2120. Two
decades into their contract working on these JumpShips, Dreadnought Enterprises was contracted to handle portions of
a project massive in scale: the construction of the first full-scale orbital spacedock built for manufacturing and repairing
JumpShips in orbit over Terra. Though primitive in comparison to space stations and military shipyards built centuries
later, the massive station was state of the art for its time and measured more than two kilometers in length. The then-
impressive orbital facility was given the name “Terra-1”. The station was completed in 2150, becoming the first orbital
shipyard in human history.
“Dread not the limits of what is believed possible—exceed them instead.” 2172 marked Dreadnought Enterprises’ next great contribution to interstellar travel, as it assisted with the First Alliance
Grand Survey, helping to catalog more than 110 colonized worlds spread across an area of space more than eighty light -
A manufacturer that can trace its roots back to before the days of interstellar travel, Dreadnought Interstellar Industries years in diameter. Three years after the beginning of the First Alliance Grand Survey, Dreadnought Enterprises began
has not only stood the test of time but flourished. The megacorporation has managed to gain a hand in some form or focusing its corporate expansion into rapidly-constructed and prefabricated structure manufacturing, with an emphasis
another in seemingly every area of business and manufacturing in the Inner Sphere, from civilian ground vehicles to on creating structure designs that were best suited for a variety of different atmosphere types and could be either easily
interstellar WarShips, from creation of cutting edge new technologies to maintaining the oldest. What Dreadnought is transported or literally “poured” into place using three-dimensional printing equipment.
most known for, above all else, is their weapons production. Although they have grown more selective of who their
customers are in recent decades, historically the manufacturer would sell to virtually anyone who was buying, having After forty-two years of unfailing service, a catastrophic failure caused Terra-1 to suffer an explosion in 2192, resulting
once had manufacturing facilities located in territories held by each of the Great Houses and even some Periphery States. in the destruction of the station itself as well as the loss of two JumpShips undergoing maintenance. A total of 183 people
were killed in the incident. All companies involved in the construction of the station, including Dreadnought Enterprises,
Founding & Early Years were investigated for involuntary manslaughter over the following year. After extensive investigation, it was learned that
an internal failure within the fuel containment pod was to blame. As the fuel containment pod was not a component
Dreadnought Interstellar Industries can trace its origins back to the year 2041, when a merger between an Asian-based manufactured by them, Dreadnought Enterprises was acquitted.
software development company, British manufacturing firm and American weapons designer formed the company titled
“Dreadnought Limited”. The following year, the company began manufacturing the first GPS-assisted, rapid deployment Dreadnought Enterprises was contracted by the Terran Space Navy in 2199 to expand to Mars for the creation of new
foldout sniper rifle produced for military use. This weapon, known as the Sumaire-50, later went on to achieve an orbital construction facilities, making use of recently discovered resources on the red planet. This led to a considerable
astonishing, record-breaking kill-shot at 6,732 meters in 2044. increase in JumpShip production, as well as creating a marked increase in available jobs for Mars-born citizens, resulting
The T.H.S. Trinity disappeared, presumed lost to misjump in 2438, just thirty-nine years after Dreadnought Interstellar
Industries relocated their Operational Headquarters to New Earth. The loss of the Trinity with all hands prompted the
creation of the Dreadnought DiscoveryCorps later that year. The DiscoveryCorps was founded to aid in attempts to find
lost ships that had suffered the same or similar fates as the Trinity. Initially having little outside support or resources, the
DiscoveryCorps first formed as a collection of specially-modified “Abeona DiscoveryCorps” DropShuttles that would help
pay for the upkeep of individual JumpShips in exchange for riding along wherever the JumpShip happened to go.
The effectiveness of the DiscoveryCorps in its early days was unimpressive and, after being in operation for nearly thirty
years, it seemed that the entire DiscoveryCorps section of Dreadnought Interstellar was destined to be scrapped. All of
that changed in October of 2467. While in an uninhabited star system and just hours before a planned jump to another
system, the DiscoveryCorps DropShuttle D.I.I.S. Fetcher detected the wreckage of a JumpShip that had drifted so close to
the local star that no one would normally have detected it unless actively looking for such things—as the DiscoveryCorps
vessels did. Further investigation discovered two DropShips were on the surface of a barely habitable world. Both
DropShips were Jumbo-class cargo transports, but it turned out that one had been refitted to carry more than 640
passengers.
Both DropShips had been damaged during the fateful misjump of the JumpShip that had brought them to the system
on the way to their destination. The damage had left them stranded, having expended the last of their fuel landing on the
Dreadnought Enterprises was dealt a blow in 2242 when it lost its contract bid for the manufacturing of an early class world, and without functional communications systems to call for help. The rescue of the stranded civilians that followed
of DropShuttle for the Terran Alliance to Dramm-Chance Interstellar—Dramm-Chance Interstellar offering the “Saturn”- was the first true exhibit of the DiscoveryCorps’ value and ability.
class DropShuttle, while Dreadnought Enterprises had offered their “Abeona”-class (pictured). Although the Abeona did
not win the Terran Alliance contract, it did go on to earn several smaller private and military contracts elsewhere, with After this incident, the Dreadnought DiscoveryCorps gained considerable popularity and investor support, more than
hundreds eventually being produced—most of which were built as newer, more advanced “DropShip” type vessels, rather paying for itself, gaining Dreadnought Interstellar Industries sufficient resources to grow a large fleet of JumpShips. These
than “DropShuttles”. Over the next year, further expansions of their JumpShip production in the Sol system more than new JumpShips would operate independently of any faction, offering transport and passage to anyone who wished to
made up for the lost Terran Alliance DropShuttle contract. pay, forming the JumpShip Allied Transport Company. The JATC, operating under the Dreadnought banner, started out
with nearly thirty JumpShips. The JATC was nearly universally accepted, as they would only transport goods authenticated
2295 was a year of transformation and growth for Dreadnought Enterprises, in part because the manufacturer was by their own personnel, resulting in a surprisingly minimal number of known incidents of illegal smuggling. Although the
renamed “Dreadnought Interstellar Industries”, but more notably because it was awarded the greatest contract in the JATC would transport military DropShips, they would not carry them across a border between nations unless authorized
manufacturer’s history at the time. This landmark occasion was the contract with the Terran Alliance Navy to, in by the military of the nation whose territory was being entered.
Dreadnought relocated its headquarters once more in 2505, this time to the world of Skye, after construction of the It was decided to move the T.H.S. Trinity to the world of Skye in 2898 after the Battleship’s K-F Drive had been restored
new Skye Heavy IronWorks facility began. The first production vehicle manufactured by the facility was a civilian vehicle, and the ship was made worthy of interstellar travel, if only just. The Trinity operated as an orbital defense platform while
the Foundation Utility Truck. This vehicle began production just one year after the establishment of the facility and repairs continued, but the vessel eventually became a part of the Skye Interstellar Academy, as a live example of military-
remains in production even today (as of 3085). Just three years later, the massive Sledgehammer Artillery Vehicle was grade interstellar technology. While no further attacks against the world occurred while the Trinity was in orbit, a failed
the first combat vehicle to roll off the assembly lines. Many other combat vehicle designs followed. attempt by Kuritan operatives to steal the Trinity in 2916 eventually resulted in the closure of the academy in 2923.
Star League Era & Amaris Civil War In March of 2946, the D.I.I.S. Delara, a Mammoth II DiscoveryCorps-class JATA JumpShip operated by Dreadnought
Interstellar Industries, detected a faint trace of an SLDF distress signal in the ES-150/D star system (near the Elbar system).
Much of the historical data of Dreadnought Interstellar Industries has been either lost or covered up regarding many Two weeks later, the distress signal was tracked to the system’s asteroid belt. This became arguably the single most
of the years following the establishment of the Star League in 2570 through to the end of the Second Succession War in important discovery in Dreadnought’s history: the S.L.S. Phoenix, the unique Texas-LFR-class WarShip, was discovered
2864. Dreadnought Interstellar Industries continued the manufacturing of war materiel for the Star League (and then the within a partially hollowed out asteroid. The process of extracting the vessel took two months and was conducted with
Great Houses, following the Star League’s collapse in 2780), including involvement in the development of new types of the utmost secrecy, all under the guise of the establishment of a Dreadnought Interstellar Industries mining operation.
WarShips, JumpShips, and DropShips, as well as various ground-based combat vehicles and BattleMechs. During this time, All messages regarding the actual goal of the effort were hand-delivered to avoid any chance of a security breach.
the manufacturer also spread across the Inner Sphere, building facilities on numerous worlds.
During the initial investigation of the vessel, star charts were found aboard the Phoenix, leading to remarkable
Dreadnought became involved in the establishment of the Defiance Industries BattleMech Factory on Hesperus II in discoveries. The star charts sent the Dreadnought DiscoveryCorps exploring the long-dead Waycross system, a system
2577, although the specific details of their involvement in the establishment of this iconic facility are currently unknown. that had long since been removed from virtually every star chart. In the Waycross system, the Cameron MechWerks
The information has either been lost over the centuries and/or was not made public knowledge to begin with. facility and CrossWays Station were found. The Cameron MechWerks facility was at first believed to be a massive SLDF
depot, but it was quickly discovered to be a titanic underground modular manufacturing facility. Meanwhile, CrossWays
The JumpShip Allied Transport Company (JATC) was retitled as the JumpShip Allied Transport Association (JATA) in Station was discovered to be the location where the S.L.S. Phoenix had been built: a dry dock station and shipyard built
2583, with most of the association’s two-hundred-plus JumpShips being independently owned and operated vessels. The into a huge, deep crater on the surface of a particularly massive, highly metallic asteroid.
Dreadnought DiscoveryCorps continued to operate aboard all seventy of the vessels owned by Dreadnought Interstellar
Industries. Meanwhile, the very first BattleMech produced by Dreadnought Interstellar Industries, the DII-HMD-S1 While the departure of the Phoenix from the ES-150/D star system had been intended to be quiet and discreet, with
Hammerhai, entered production in 2612 and saw heavy use by the Star League Defense Force (SLDF). an additional month of slow work planned to extract the ship from the asteroid trapping her, it was not to be. After just
two months of work had been done, including what few repairs were needed to make the Phoenix jump-worthy, an
In 2622, Dreadnought Interstellar Industries unveiled the Firebrand-class Battleship, produced for the Star League unidentified JumpShip appeared at the jump point opposite the Delara, immediately deploying squadrons of stark-white-
Defense Force by Dreadnought’s own Mars Shipyards in the Sol system. Dreadnought’s Mars Shipyards were destroyed painted aerospace fighters running no IFF transponders. All attempts at communication with these “Mystery Ships” were
in February of 2767, ending the Firebrand’s production after ninety-six of the vessels had been manufactured. The ignored.
destruction and subsequent ending of the Firebrand-class Battleship’s production was deemed necessary to prevent
Stefan Amaris, the infamous “Usurper of the Star League”, from having access to examples of this remarkably powerful An emergency plan was enacted, utilizing the four tactical nuclear warheads found aboard the Phoenix to first blast
vessel. As of this writing, most other Dreadnought-related records during this timeframe, aside from specific production open the massive cavern that had trapped the ship, and then to give the impression of a misjump as the ship jumped
dates of certain types of combat vehicles and BattleMechs, are missing. away, using the remarkably still-charged Lithium-Fusion Battery. Three nuclear weapons detonated in an equidistant
pattern around the Phoenix’s position a fraction of a second after she jumped away, creating a very convincing impression
Third Succession War that the WarShip had suffered a catastrophic misjump and exploded.
The JATA JumpShip D.I.I.S. Rockturner, while investigating mining prospects in the GS-229 system in 2887, near the This became the cover story that Dreadnought used for decades, claiming that an attempted recovery of an intact Star-
Lamon system, stumbled across the severely damaged T.H.S. Trinity. The derelict vessel had been in orbit over GS-229’s League-era WarShip had ended in disaster. Even Dreadnought’s own extraction crews that had been left behind believed
third planet since 2438. Within three months, Dreadnought’s 12th EngineerCorps began constructing a temporary orbital it, as none of the crews of the Dropships or JumpShips who witnessed the event had been made aware of the “fallback”
dry dock to restore the vessel to functionality. The process of constructing the basic dry dock—at first in secret—took plan. Meanwhile, the “Mystery Ships” simply turned back and disappeared.
nearly two years, and the restoration of the vessel to interstellar capability, believed to be an impossibility by the
engineers sent by the Successor States, took a further nine years. The successfully recovered Phoenix had in fact jumped from the ES-150/D system to the Waycross system, and since
Waycross was not on any active star chart, the act of making the Phoenix “disappear” was complete. The ship was
To help combat the decay of knowledge across the Inner Sphere regarding interstellar transportation and jump drive immediately and quietly moored at CrossWays Station under lock and key in June of 2946. The Waycross system was
technology, Dreadnought Interstellar opened the Skye Interstellar Academy in 2892. The Skye Interstellar Academy quickly and quietly occupied by Dreadnought, although the real reason why was kept quite well hidden. Most were
focused on training JumpShip construction, maintenance, and operation, for future generations of engineers and crew. unaware of any of the occurrences altogether, as the system was kept off the star charts for decades to come. To help
Just three years later, in 2895, an assault on the world of Skye by House Kurita’s Draconis Combine resulted in significant keep attention away from the series of extremely fortuitous discoveries, as well as the funding going into claiming them,
damage to Dreadnought’s Skye Heavy IronWorks facility, effectively ending the production of the Kodiak Heavy Tank. The Dreadnought Interstellar moved its headquarters for the final time to the much closer Acala system in 2947. During this
Kuritan attack was the impetus that spawned the Dreadnought DefenseCorps 1st Skye Battalion, consisting of two same timeframe, to free up finances to make best use of their good fortune, Dreadnought Interstellar sold off fourteen
companies of combat vehicles and a single company of BattleMechs by 2897. This was the first of many DefenseCorps of its non-DiscoveryCorps JumpShips, quietly directing most of the funds toward the new assets in the Waycross system.
units that were formed to defend virtually every Dreadnought Interstellar Industries facility across the Inner Sphere.
The next several decades were spent solidifying Dreadnought’s hold over the Waycross and Acala systems. In early
The Kuritan attack also resulted in a demand by Dreadnought Interstellar Industries for reparations to be made by the 2954, in an event that left most to believe that the T.H.S. Trinity had suffered a misjump and had been lost forever while
In late 3069, both Dreadnought Interstellar Industries facilities on the Davion homeworld of New Avalon were Launching alongside the refitted D.B.C. Phoenix was the all-new WarShip, the D.B.C. Theris. This new vessel was the
destroyed during the struggle between the attacking Word of Blake and the defending Federated Suns. Dreadnought’s first Firebrand-class Battleship to exist in the Inner Sphere in three centuries, and she was named in honor of those lost
New Avalon personnel had been trapped on the world since the Blakist attack began in 3068. More than seven hundred on the world of the same name to the Word of Blake in 3075.
personnel were severely injured or killed, with a final death toll of 437 out of a total of 1,245 Dreadnought personnel.
After a mercenary unit, the Hounds of Artemis, had been all but annihilated trying to defend them, the surviving Hounds Jihad Aftermath
and Dreadnought personnel were forced to take shelter among the civilian population and wait for the siege to end. After
the Siege of New Avalon ended in 3075, most of the surviving Hounds of Artemis joined Dreadnought’s military. Economic growth began to take place for the first time in over a decade as Dreadnought Interstellar Industries finally
managed a partial recovery from the losses suffered over the previous two decades. The probability of ever fully
Just one year earlier, in mid-3074, many of Dreadnought Interstellar’s remaining JumpShips and even the D.B.C. recovering from the damages dealt during the Jihad is remote at best. As of this 3085 writing, Dreadnought Interstellar
Phoenix were recalled to assist in evacuating the world of Theris, as the Word of Blake Jihad seemed poised to soon Industries has facilities on more than thirty worlds, spread primarily across Davion space, with a handful in other
spread in the direction of the Waycross system. The stripping of the Cameron MechWerks facility on Theris began in territories. Most of these facilities are small and of economic benefit to the worlds on which they are located. These
earnest, in an attempt to salvage as much of the manufacturing equipment and tooling as quickly as possible. The smaller facilities are defended by small Dreadnought DefenseCorps units which are often assembled from the local
evacuees and equipment were transferred to the world of Acala III as quickly as possible, but it was still a lengthy process. population, helping to bolster local militias. The only major militarized star system under the Dreadnought banner is the
Acala system, now known as the Acala Semi-Autonomous Region (ASAR).
The manufacturing equipment taken from Theris was rapidly incorporated into Acala III’s own manufacturing facilities,
and the massive SLDF bunker that had been home to the DefenseCorps 1st Homeworld Regiment was repurposed into a The D.B.C. Theris has never left the Acala star system, but she has been involved in active wargames and other training
‘Mech factory known as the Dreadnought MechFoundry. The production of most BattleCorps-specific machines restarted with her “pseudo-sister ship”, the D.B.C. Phoenix. These powerful vessels are gradually being joined by a handful of other
in late 3075 to early 3076, albeit with reduced production rates. Eventually, this massive underground facility was WarShips being built by Dreadnought Interstellar Industries to bolster the ASAR’s defensive strength. In 3083, the Theris
expanded and began to resemble the larger Cameron MechWerks at its peak. and Phoenix were joined by a much smaller Jackal-class Destroyer, the D.B.C. Integrity. As of 3085, one additional
Firebrand-class Battleship is nearing completion and one more Jackal-class Destroyer is being constructed. There are no
In June of 3075, after several weeks of bloody fighting, the world of Theris was lost to a Word of Blake attack, along evident plans for Dreadnought Interstellar Industries to build any more WarShips once these vessels have been
with the forces assigned to protect it, including the entire Dreadnought DefenseCorps’ Theris Regiment as well as the completed.
D.B.C. Trinity. No survivors on either side were found after the nuclear devastation that followed. Adding to the tragedy,
two JumpShips carrying civilian evacuees from Theris, were destroyed with all hands. Protests regarding the possession and continued production of WarShips in any quantity by the ASAR have been made
by governments elsewhere in the Inner Sphere. These protests grew louder with the Inner-Sphere-wide disarmament
In 3077, Operation LANCASTER was carried out by the Dreadnought BattleCorps with the assistance of two mercenary process that began after the end of the Jihad. To maintain the peace, the ASAR has been officially designated as an
units: the Blackwood Templars and Ronin Free Companies. The purpose of LANCASTER was to eliminate a growing extension of the recently-founded Republic of the Sphere. Despite the official affiliation, it is unclear how willingly the
foothold situation in the Ashkum system by destroying a growing Word of Blake force that had been building in the system ASAR would respond to a call for help from outside its borders, unless the call came from one of Dreadnought’s own
over the previous year. After the successful conclusion of LANCASTER, and several months of salvaging war materiel in facilities—but even that could result in a political incident.
the aftermath, the BattleCorps returned home to the Acala system.
Given the delicate political balance required to maintain the peace, it is possible that Dreadnought Interstellar
Due to the significant damage dealt to Vyrie City (Ashkum IV’s capital city) and some of the surrounding infrastructure, Industries facilities outside of the ASAR that come under attack might be left completely dependent on their own local
Dreadnought Interstellar Industries attempted to assist with the rebuilding efforts. A massive effort was undertaken with Dreadnought DefenseCorps units to defend themselves, with no expectation of reinforcement. This is because the
a large contingent of Dreadnought EngineerCorps personnel and heavy equipment brought in to aid with the rebuilding Dreadnought BattleCorps, which was originally created to serve as mobile reinforcements, is now firmly associated with
process in April of 3077. A reinforced battalion from Acala III’s DefenseCorps 1st Homeworld Regiment was brought along the ASAR, and the mobilization of the BattleCorps outside of the ASAR’s borders may be seen as an act of aggression by
to provide security for the EngineerCorps personnel and to defend the world. other governments. This includes the BattleCorps’ WarShips. While politics might prevent Dreadnought’s own forces from
acting directly, there is nothing stopping Dreadnought Interstellar Industries from flexing its financial strength and hiring
With increasing civil unrest and a growing anti-Dreadnought movement, Comstar was brought in to act as a neutral mercenaries to reinforce the defenses of their at-risk facilities elsewhere.
party and intermediary to help quell the increasing tension between Dreadnought and the local population of Ashkum IV.
Protesting shifted into rioting, resulting in injury and even the death of some of Dreadnought’s personnel in July of 3077.
The unrest continued to spread, eventually resulting in an attack on the DefenseCorps’ temporary barracks. Following the
attack, Dreadnought Interstellar withdrew all assistance effectively overnight, not leaving a single piece of Dreadnought-
owned equipment behind. On the list of equipment taken when Dreadnought left the world were the industrial fusion
reactors that had served as temporary power generation stations for the capital city and many surrounding towns, as well
as the advanced tactical satellites that the BattleCorps had deployed over the world during planetfall at the beginning of
LANCASTER. These complex military satellites had since been serving as temporary replacements for the planet’s
destroyed communication satellite network.
After losing all support from Dreadnought, the already shaky economy of Ashkum IV effectively collapsed. Meanwhile,
Dreadnought simply washed their hands of any responsibility.
The second official unit formed under the Dreadnought DefenseCorps banner was the 1st Skye Battalion, created in
2897 in response to the Kuritan attack on the world of Skye just two years prior. Since the introduction of this unit, various
separate DefenseCorps units have been introduced across the inner Sphere to defend the holdings of Dreadnought
Interstellar Industries. Dreadnought DefenseCorps units have historically ranged from lance- to battalion-sized units at
smaller installations, all the way to overstrength regimental units on key worlds.
The core of most DefenseCorps units is generally formed from ex-military personnel sourced from the indigenous
population, and the equipment used by the unit is typically a mixture of Dreadnought-made and privately-owned
machinery. However, mercenaries have sometimes been temporarily employed when there has been a lack of manpower
or equipment—or both—available to build a sustainable defense unit. Some of the hired mercenary units have eventually
found themselves becoming permanent DefenseCorps units.
The two largest DefenseCorps units to ever exist were the 1st Homeworld and Theris Regiments. The former is still
based on the Dreadnought homeworld of Acala III. The latter, now destroyed, was based on Waycross II, the planet better
known as Theris.
Clan Invasion
One of the best-known soldiers of the Dreadnought DefenseCorps is also among the most unfortunate. In March of
3050, on the world of Toland, the members of the DefenseCorps’ 1st Toland Company were pitted against the might of
Clan Jade Falcon. Like the Twelfth Star Guards’ Second Regiment and the Toland Defense Force, the DefenseCorps’ 1st
Toland Company fell to Clan Jade Falcon’s Turkina Keshik and Ninth Talon Cluster. In the case of the DefenseCorps unit,
however, it was not a total annihilation of the unit. A handful of the unit’s personnel, along with the civilians and
Dreadnought Interstellar personnel that the unit had been tasked with defending, were all successfully evacuated.
This evacuation was successful as a direct result of a personal sacrifice made by Lieutenant Ellie Shaw. Shaw engaged
a Jade Falcon Star Captain in a one-on-one battle to buy time. Shaw fought alone in her modified Wolverine against the
Star Captain’s vastly superior Thor OmniMech. She managed to deal severe damage to the Thor before her Wolverine was
destroyed and the Lieutenant herself mortally wounded.
Shaw’s delaying action was enough for the survivors of the DefenseCorps unit and the civilians to cram themselves
into, and escape aboard, the only vessel available. This was the last of the three original prototype Abeona-class DropShips
in existence, and was known as the Salvation. Although the Salvation was a relic that was nearly eight hundred years old,
the ship had been undergoing restoration in the years preceding the Clan Invasion, and she had been rebuilt to near-new
“We hold.” condition. With the Jade Falcon aerospace fighters already engaged elsewhere on the world, the Salvation was able to
use its remarkable speed to escape the grasp of the Jade Falcons and reach a JumpShip that had been preparing to leave
Founding & Early Years the system. The high-G burn took its toll on the ship’s occupants, but it proved to be worth it. The JumpShip in question
was fortunate enough to have entered the Toland system a week prior to the attack at the opposite jump point to that
The Dreadnought DefenseCorps is not a single entity like most military units. Instead, it is the name used to designate of the attacking Clan vessels and had been in the process of furling its sails to escape when the Salvation reached it.
the various defense forces employed by the interstellar megacorporation Dreadnought Interstellar Industries. While
Dreadnought Interstellar had several defensive postings prior to the launch of the Dreadnought DefenseCorps program The sacrifice of Lieutenant Ellie Shaw on the world of Toland has made her into something of a legend among the
(which had been proposed as early as 2804), the first example of the DefenseCorps to be established officially was the Dreadnought BattleCorps and DefenseCorps. A statue of Shaw’s modified Wolverine, erected in her honor, stands in silent
1st Homeworld Battalion, on Acala III. This unit was established shortly after the end of the Second Succession War as a watch over the Trinity Memorial Hall in New Sydney, the capital city of Acala III.
result of how the world had been gutted of its defensive strength in 2863 when the Capellan Confederation ceded the
Acala star system to the Federated Suns. Operation BULLDOG
As the world of Acala III had no standing military after the Capellan Confederation’s withdrawal from the star system, In 3058, the newly-formed “Second Star League” formed Task Forces Serpent and Bulldog to repel the Clan Invasion by
the establishment of the Dreadnought DefenseCorps was initially intended to be a temporary defense force, a stopgap to taking the fight to the Clan homeworlds, specifically the Clan Smoke Jaguar homeworld of Huntress. Prior to Operation
eventually be phased out once Acala III had established a proper planetary militia or other form of self-defense force. The BULLDOG, three full battalions of Dreadnought DefenseCorps combat vehicles and support personnel were transferred
belief at the time was that the world was likely to form a small-but-active militia primarily to defend its citizenry from the from their defensive positions on the world of Theris. These forces were assigned as reinforcements for various units that
notoriously dangerous local wildlife on Acala III, with a secondary focus on planetary defense from outside threats. made up Task Force Serpent. These DefenseCorps personnel officially operated within the chain of command of the
Second Star League. However, they were also following secret orders that had been given to them by Dreadnought
What had not been predicted was how well the population of Acala III embraced a compulsory military service for all command. These orders were independent of any orders issued by the official chain of command during the fighting that
citizens after its people spent nearly two decades fighting the idea. It became clear that the people of Acala III intended took place on Huntress.
While the DefenseCorps personnel had managed to secure a not-insignificant stockpile of Clan technology and
manufacturing information, the most critical information that they had kept secret was the discovery of an until-then
unknown Smoke Jaguar world: Pantheress VI. Little did anyone know just what an instrumental role this world would play
in advancing Dreadnought’s military over the following decades. Many of the DefenseCorps personnel perished in the
process of securing this information, and all involved were given appropriate honors after the Dreadnought BattleCorps
returned home with the survivors.
In January, 3069, Colonel Thomas Lawrence, then commander of the DefenseCorps Theris Regiment and Dreadnought’s
Senior Colonel (overall commander of the entire Dreadnought military), was assassinated on Acala III while visiting Colonel
Ann Lawrence, for her birthday. This assassination was later tied to several other assassinations made against key
Dreadnought Interstellar Industries personnel, and a connection to the Word of Blake was established as a result.
Following her father’s death, Ann Lawrence was promoted to Senior Colonel.
Eight Dreadnought Interstellar Industries facilities and their accompanying DefenseCorps units were evacuated from
different worlds in 3069 by the Dreadnought BattleCorps 1st Regimental Combat Team. Last and most notably among
these units was the DefenseCorps’ Basalt IV Battalion, a reinforced battalion four companies in strength nicknamed the
“Salty Batty”. In October of 3069, during the last of these eight evacuation operations, the Word of Blake launched an
assault on the world of Basalt IV. While most of Dreadnought’s civilians were successfully evacuated from Basalt IV, the
Salty Batty was all but wiped out, and the BattleCorps 1st RCT themselves suffered significant damage to their ranks.
While the human casualties suffered by the BattleCorps were moderate, only sixty-three survivors of the Salty Batty
managed to escape. Most of these survivors were technicians, support personnel, and their families, as nearly all the
unit’s combat personnel had perished in the fighting. Thirty-seven of the DefenseCorps survivors later perished due to
exposure to chemical weapons used by the Word of Blake during the attack. Unfortunately, most of those who died due
to chemical exposure were members of the DefenseCorps personnel’s civilian families, as they were less prepared to deal
with such an attack.
The Theris Regiment was classified as a total loss in 3075 following a devastating Word of Blake attack on the world of
Theris. This event is commonly referred to as “Trinity’s Fall”. The event was given its name as the attack first resulted in
the destruction of the D.B.C. Trinity, the aging Dreadnought-class Battleship tasked with defending the planet. After
several weeks of combat and other horrific events on the planet’s surface, the attack ended with what can only be
described as the annihilation of all human life in the system. This included the Blakists themselves. High-yield
thermonuclear weapons were detonated not only on the icy world’s surface around the manufacturing and population
centers, but also within the system’s CrossWays Station, the massive asteroid-based black-water dry dock and shipyard
where the surviving Blakist WarShips had moored themselves for repairs.
Jihad Aftermath
The Dreadnought DefenseCorps 1st Homeworld Regiment (DDC-1HR for short), based out of Fort Farrell on Acala III,
remains active as of 3085 and is rated as a veteran overstrength Regimental Combat Team. A new “2nd Homeworld
Regiment” is in the process of being formed as of 3085 and has reached three mixed Battalions in strength, though unlike
the DDC-1HR, the DDC-2HR is primarily vehicle-centric and is largely comprised of green, untested troops.
The Acala DefenseCorps Aerospace Wings have nearly one thousand aerospace fighters in total, operating from the
world’s four Orbital Defense & Refit Platforms (ODRPs). These are largely older model craft, but as newer fighters are
gradually produced in Dreadnought Spec form, the oldest are being passed down to the Planetary Militia.
Colonel Jackson retired in 3009 after having to deploy the BattleCorps only five times. During his fourteen years as the
unit’s commanding officer, Jackson helped guide the unit to grow from a single battalion to a regimental combat team in
size. The unit is still most often referred to as the “Dreadnought BattleCorps” or simply the “BattleCorps” to this day, but
the unit gained the official designation of the Dreadnought BattleCorps 1st Regimental Combat Team with Jackson’s
retirement. The unit had grown to having one full-strength and two understrength battalions of BattleMechs and two
battalions of combat vehicles, as well as an entire company of artillery vehicles, supported by twelve aerospace fighters.
Shortly before Jackson retired, the BattleCorps moved their base of operations to the dilapidated Castle Brian, known
as Castle Ramsay, located near New Sydney, Acala III’s capital city. Basic repairs to Castle Ramsay took many years but
gradually the facility began to regain its former Star League glory. The full restoration of Castle Ramsay took place over
the following decades, and it gradually became a very respectable—and exceptionally defensible—base of operations. At
the same time as the BattleCorps’ move into Castle Ramsay, the DDC-1HR was relocated to operate out of the secondary
command center in the massive underground SLDF bunker several kilometers away. This was due to Castle Ramsay simply
not having the functional facilities to house both units, but it could house the BattleCorps with relative ease, while the
much more massive underground facility could easily accommodate the DefenseCorps several times over with significant
room to spare. (Eventually, decades later, in the mid-3050s, Castle Ramsay was finally fully restored and became capable
of housing and servicing both the BattleCorps and DefenseCorps with ease.)
Taking over for the retiring Colonel Jackson, Richard Hope was promoted to Colonel and assumed command. In dealing
with several skirmishes involving pirates and mercenary units, the BattleCorps gained further valuable combat experience
as well as increased financial support from the unit’s parent corporation, Dreadnought Interstellar Industries.
The BattleCorps also secretly gained control of two very special, exceedingly rare military assets: a pair of black-water
WarShips. The crew of the recently rechristened ancient and battered Dreadnought-class Battleship D.B.C. Trinity began
heavy training in the Waycross system in 3018, away from prying eyes. Dreadnought’s only other WarShip was the D.B.C.
Phoenix (formerly S.L.S. Phoenix). The Phoenix remained hidden away in the Waycross system’s asteroid belt, moored at
the secret CrossWays Station that had built the pristine ship centuries prior. The fact that the Waycross star system had
been absent for centuries on virtually all available star-maps was largely what kept the ships hidden—for a time.
Founding & Early Years Colonel Richard Hope died of an inoperable brain tumor on October 2nd, 3027. The tumor was discovered too late to
be countered effectively with noninvasive treatments. This left his executive officer, Diane Charmer, to be promoted to
In 2946, the Dreadnought DiscoveryCorps recovered the S.L.S. Phoenix, the unique Texas-LFR-class WarShip. The Colonel in his place. Almost exactly a year later, the BattleCorps was commanded by House Davion’s First Prince, Hanse
mighty, centuries-old Star-League-era vessel had been recovered intact, with multiple fully loaded DropShips mated to “The Fox” Davion, to assist in the war effort against the Capellan Confederation. The BattleCorps was given the task of
her hull. Restored equipment and machinery salvaged from the Phoenix’s DropShips allowed for significant expansion of attacking the world of Cordiagr V. The intelligence briefing given to the BattleCorps by the Federated Suns had indicated
the Acala-III-based Dreadnought DefenseCorps 1st Homeworld Regiment (“DDC-1HR” for short) in 2985. The considerable that the world was home to a new BattleMech manufacturing facility that was due to come online in the following months.
influx of advanced Star-League-era machines resulted in the DDC-1HR splitting into two separate units. The DDC-1HR
itself retained the strength of three battalions of mixed ‘Mechs and combat vehicles. Meanwhile, the new unit, designated Few knew the true motives behind The Fox’s actions, but deploying the BattleCorps behind enemy lines was an
the 1st Dreadnought BattleCorps, began as a single reinforced battalion under the command of Colonel Phillip Jackson. extremely calculated move on the part of the prince. Reports had come to his attention indicating that Dreadnought’s
home star system of Acala may have been planning to make a move for independence. With these reports in hand, Hanse
As stated by Jonathan Higgs, Dreadnought Interstellar Industries’ CEO at the time, the long-term purpose for this new Davion acted to undermine any such attempt. By being stripped of a considerable percentage of its military might, the
unit had been to create a more powerful offensive force to begin taking other worlds under the Dreadnought banner. Acala system would be forced to stay in line. To ensure the desired impact, the BattleCorps’ mission on Cordiagr V was
With Higgs’ “untimely passing” all but immediately following the public announcement of the BattleCorps’ mission selected because House Davion’s intelligence was sure it was a trap. With the BattleCorps eliminated or at least crippled,
statement, and the subsequent assumption of control over the corporation by the Fitzgerald family, the BattleCorps’ the Acala star system would need a long time to rebuild before even considering a push for independence. In the
mission was changed to that of a reactionary defensive unit, rather than a tool for forceful expansion. The DDC-1HR meantime, the BattleCorps tied up Capellan troops or at least mercenaries in their employ. For The Fox, it was a win-win.
remained on Acala III to act as the main guard for the homeworld, while the BattleCorps became a mobile force that could
be dispatched to reinforce threatened DefenseCorps units on nearby worlds, should the need arise. The sharp reversal of Two mixed understrength battalions of Capellan troops were assembled and assigned to Cordiagr V to defend against
the mission statement was, fortunately, sufficient to avert the political and military backlash that likely otherwise would any attempt to seize the world. At first, it appeared that the Capellans had either underestimated the force that would
Over a year after leading the BattleCorps’ to their first major defeat, Colonel Diane Charmer was found dead in her From the beginning of the Clan Invasion, Dreadnought Interstellar Industries ramped up BattleMech production. The
home on May 7th, 3030. The cause of death was found to be the poisoning of a bottle of wine. House Liao was believed BattleCorps’ and DefenseCorps’ aerospace fighters began to repel increasingly frequent pirate attempts to seize outgoing
to be responsible for the assassination, but no concrete link was ever established. Some in the intelligence circles have shipments of equipment and machinery. After learning of the Clan Invasion, the DDC-1HR saw heavy reinforcement in
suggested that the assassination may have been a standing order from Prince Hanse Davion, should the BattleCorps return 3050. This reinforcement was also part of the next step of Colonel Thomas Lawrence’s training program, which eventually
from Cordiagr V at all, but even less proof supports that theory. Jack “Ripper” Stephenson reluctantly accepted promotion included the temporary relocation of the BattleCorps off-world. Starting on Acala III at the end of 3052, more than two
to Colonel, officially taking command of the BattleCorps following Diane Charmer’s unfortunate passing. years were spent training with the Blackwood Templars Mercenaries to improve the BattleCorps’ combat capabilities,
using the veteran Templars’ impressive knowledge and skills in combat to help sharpen the BattleCorps’ own.
It was later learned that the Acala-based reports that Prince Hanse Davion had acted on were in fact falsified. Acala
had no intention of moving for independence. Oliver Kiernan-Davion, an extended member of the Davion family and the In May of 3053, the BattleCorps and the D.B.C. Trinity were relocated to the Waycross system, with the Blackwood
only Davion to ever hold a position of power in Acala III’s government, had falsified the reports in hopes that the prince Templars following them to the frozen world of Theris. The Templars were quite surprised to find themselves involved in
would eliminate Oliver’s political rivals for him, paving the way for Oliver to attain greater power and wealth. Instead, his simulated combat with not just one, but in fact two very real black-water WarShips, once the relatively new crew of the
actions resulted in the deaths of good soldiers. Oliver was summarily executed for treason shortly after this discovery. D.B.C. Phoenix joined in the training exercises that were conducted over the next twenty months. Unfortunately, events
on Acala III resulted in the Trinity being recalled to the Acala system in early 3054, cutting the Trinity’s involvement short.
War of 3039
By the end of the two-year-plus training program, concluding in February of 3055, the Blackwood Templars and
A chain of attacks by various mercenaries and pirates that began in 3041 pushed Colonel Stephenson to launch a rapid Dreadnought BattleCorps, as well as the Theris-based DefenseCorps, had all benefitted. The ground troops, WarShip
expansion of the Dreadnought BattleCorps to compensate for losses taken during the repeated defense of Acala III. With crews and aerospace fighter pilots of the BattleCorps had gained significant experience and sharpened skills. In exchange,
the DDC-1HR having weathered the attacks relatively intact, the expansion of the BattleCorps pulled from veteran the AeroFighters of the Blackwood Templars had been allowed their first opportunity to gain experience in dealing with
DefenseCorps personnel to bring the BattleCorps up to strength to deal with the increasing severity of the attacks. WarShips in combat, even if the experience was with depowered training weapons. Although it had been expected that
Meanwhile, the DefenseCorps replaced the personnel that been reassigned to the BattleCorps by pulling from Acala III the mercenaries would almost certainly leak the existence of the Phoenix following the conclusion of the training program,
Military Academy graduates and combat veterans from the Acala III Planetary Defense Militia. It was not long before both the Templars managed to effectively keep the secret safe for the next three years, by which point it no longer mattered.
the reorganized BattleCorps and DefenseCorps began to gel as units, and both gained combat experience repelling several
more attacks over the next eighteen months. Each attack on Acala III was more severe and savage than the last. Operation BULLDOG
Unfortunately, while the combination of the BattleCorps, DefenseCorps and militia managed to successfully repel the With the truce line that had been formed following the Battle of Tukayyid in 3052, and the Dreadnought IntelCorps
invaders each time, the casualties began to build as the losses inflicted only increased with each subsequent attack. The pointing toward a significant united military buildup by the Great Houses in 3058, it was pieced together that there was
attack that was repelled in October of 3042, proved to be the last straw for Colonel Stephenson. a counteroffensive against the Clans in the works. It was in November of 3058, on Tharkad, during a private face-to-face
meeting with Prince Victor Steiner-Davion, that Colonel Thomas Lawrence revealed the D.B.C. Phoenix, the Dreadnought
Knowing that yet another attack was sure to follow, Stephenson decided that enough was enough. He put in motion a BattleCorps’ unique Texas-LFR-class Battleship. Although there had been plenty of rumors regarding the Phoenix, only
plan to end the fighting through a show of overwhelming force. It proved to be a well-timed choice, as the hostile force Comstar’s intelligence arm, ROM, had managed to confirm the ship’s existence by then, having gleaned information from
deployed for the next attack was larger than anything that had been faced previously. This next attack, launched in the Blackwood Templars. It was only later learned that, knowing the importance of every ship available to combat the
December of 3042, consisted of what was believed to be two full regiments of Capellan line troops masquerading as invading Clans, Comstar had decided not to interfere with Dreadnought’s operation of the powerful vessel. Naturally, this
mercenaries to capture the planet once and for all, seizing the military manufacturing might of Dreadnought Interstellar decision was largely dependent on the vessel not being deployed in an offensive operation.
Industries in the name of House Liao’s Capellan Confederation. (As of 3085, Liao is still believed to be the origin of this
attack, but it has never been proven—and Liao has never registered any of the considerable losses taken during the conflict Bringing such a massive asset as the Phoenix to the table allowed Colonel Thomas Lawrence to negotiate certain aspects
that followed, leaving the question of responsibility unanswered.) Stephenson ended the next battle before it could truly of what the BattleCorps would and would not do during the counterassault against Clan Smoke Jaguar—aspects that later
begin by having the Dreadnought-class Battleship D.B.C. Trinity, which had been kept hidden for close to a century and proved critical to the future of Dreadnought as an entity. Three Dreadnought DefenseCorps armor battalions from Theris
only recently revealed to still exist, ambush the hostile DropShips during their approach to Acala III. were assigned to Task Force Serpent’s portion of Operation BULLDOG as reinforcements for various units. Meanwhile,
The few men and women who had escaped Son Hoa with the Blackwood siblings constituted a force roughly four lances
in strength. Tyr Blackwood, with Prandine’s guidance, realized that they needed to quickly build up finances to support
themselves and decided to bank on the one skill they all shared. Relying heavily on Tereza Prandine as Tyr’s advisor, the
Blackwood Templars Mercenaries were formed in late April of 3047, a scant few weeks after the attack. The fledgling unit
faced its first few tests in the Periphery through the rest of 3047 and into 3048, fending off bandit raids and showing
strength to petty dictators. During this time, Tyr Blackwood began to shine as a skilled MechWarrior and natural-born
leader. Meanwhile, his sister Sigrun began to learn about ‘Mechs, herself.
Clan Invasion
In June of 3049, the Templars signed on to a long-term contract with the Khadir Mining Corporation to protect the
corporation’s assets on the planet Anywhere. Almost a year later, it was on this world that the Templars were handed
their first major defeat at the hands of the invading Clans. Clan Jade Falcon were the first encounter that the Templars
had with these mysterious invaders from beyond the Periphery. The overwhelming technological advantage enjoyed by
the Clans forced Tyr Blackwood and his Templars to flee, much as they had done on their homeworld of Son Hoa. With
the fall of the Anywhere Militia and the recently stationed 2nd New Ivaarsen Chasseurs to the Jade Falcon assault, as well
as the loss of the mining company’s mercenary liaison, the Templars knew that they were not going to be paid.
Two other mercenary units of note were actively operating on Anywhere: a combined arms unit known as Storm of
Steel and an AeroFighter-centric unit called Arkadin’s Angels. Like the Templars, they were all in tatters. The employers
of all three mercenary units had disappeared. Dispensing with their contracts, the three mercenary units withdrew as
quickly as they could. Under enemy fire and constantly chided by catcalls of an irate Jade Falcon commander, Tyr
Blackwood managed to organize the tattered remnants of the three mercenary units and get them all off-world. This
quickly led to the merger of both the other units into the Templars after the escape.
The Templars spent much of the Clan invasion trying to recover from the damage sustained during the shocking first
encounter. After the Battle of Tukayyid in 3052 put in place a truce line, Blackwood’s Templars finally began to make a
name for themselves. They took on contracts for a lower fee than the competition and succeeded through a combination
of the unit’s formidable aerospace fighter wing and Tyr Blackwood’s natural charisma. The Templars gained a not-
inconsiderable level of both fame and infamy through their successful operations.
Later in 3052, during a raiding mission against Clan Smoke Jaguar for the Draconis Combine, they recruited a Combine
citizen named Yuki Nagata. Nagata quickly proved to be a key asset for the Blackwood Templars going forward, becoming
the unit’s tactical officer. The addition of Nagata compensated for Tyr Blackwood’s shortcomings as a strategic thinker, a
task that the combined efforts of the command staff had not quite been able to accomplish.
“You’re either the best or one of the rest.” – Colonel Tyr Blackwood
Learning from their experiences battling the Clans in the 3050s, the Blackwood Templars quickly became hit-and-run
Founding & Early Years specialists. Their favored strategy was to have their aerospace wing clear out any enemy aerospace assets and anti-aircraft
artillery first, then sweep the path clear for the troops coming in behind them with strafing runs. During an assault, most
The Blackwood Templars Mercenaries were the brainchild of the displaced noble Tyr Blackwood who, along with his often the Templars struck so quickly and hit with such fury that the defenders struggled to deploy in time to offer
sister, fled his homeworld Son Hoa in March of 3047. The Blackwood siblings fled Son Hoa in the face of a coup led by significant resistance. The Templars are known for often striking directly into the teeth of their foes, using their blitzkri eg
none other than their uncle, Douglas Blackwood. Douglas, supported by the mercenaries of Morrison’s Marauders, approach to quickly break their opponents before they can retaliate. When engaging with a Clan opponent that still
overran the palace guards and slaughtered Joseph and Lorraine Blackwood—the leading members of the Blackwood royal followed the Clan bidding system, Tyr Blackwood always abused the bidding system as much as possible to gain an
family, and Tyr’s parents. advantage. In some cases, Blackwood has specified a location for combat, luring the Clanners to deploy on one side of
the planet, then deployed the Templars directly on the Clan base of operations on the opposite side of the world. On the
On the of day the attack, young Tyr Blackwood and Sigrun, his younger sister, had been in the care of Tyr’s bodyguard, ground, the individual MechWarriors and tankers of the Templars operate in pairs, with no ‘Mech or combat vehicle
Tereza Prandine. Indulging Tyr’s fascination with BattleMechs, the three had been touring the hangar where Prandine’s running solo. This approach offers the Templars flexibility and combat effectiveness that even the mighty warriors of the
personal Highlander BattleMech, a rare surviving royal HGN-732b, was stored alongside a new ‘Mech prototype being Clans have had difficulty matching, whether they follow the honor-bound Zellbrigen rules of engagement or not.
developed by local manufacturer StarCorps Industries with funding from the Blackwood family.
The Templars recruit everywhere they go. No more is this exemplified than in their recruitment of a Jade Falcon Star
Once she realized what was happening, Prandine boarded her Highlander after helping Tyr hijack the prototype ‘Mech. of MechWarriors that surrendered to them. Tyr Blackwood had tricked the enemy Star Colonel into repositioning most
Meanwhile, Sigrun slipped into the prototype’s rumble seat. The two assault ‘Mechs eventually managed to lead the few of his ‘Mechs out in a relatively open field to fight the Templars, while the Templars themselves dropped directly on the
surviving palace guards to the spaceport. Despite picking up several reinforcements along the way—notably including the Falcon base of operations. This action resulted in the successful capture of the Falcons’ Scytha Heavy OmniFighters on
Banshee piloted by Blackwood loyalist Hank Cordova—Prandine’s Highlander was pushed to its limits and forced to take the ground and the one Star of ‘Mechs left behind. The Star’s commander, a Lyran-born MechWarrior named Keith Knox,
a beating to protect the inexperienced Tyr. She later admitted that despite his lack of real-world experience at the controls had been taken Bondsman and eventually became a MechWarrior for Clan Jade Falcon. Knox preserved his troops’ lives
To an outsider, the Templars give the appearance of an extended family, complete with the usual arguments and fights Consolidating the Blackwood Templars’ rulership over the world kept the Templars largely out of the FedCom Civil War.
one would expect from such an environment. The seemingly loose discipline has historically led many to sign on with the The Templars eventually became involved in the conflict, participating in the final assault on Tharkad, but even then, it is
unit, only to all but immediately quit as the Templars’ severe expectations for its members became painfully apparent. rumored that they only joined the fight because Prince Victor Steiner-Davion and Archer Christifori asked for their help.
Most of the veteran Templar warriors are considered on par with the more elite forces of the Successor States, and the Even if these rumors are true, the specifics are unclear. After the war’s conclusion, the Templars returned to Son Hoa to
Templars expect nothing short of the best from anyone on their roster. In terms of the lesser-experienced personnel that begin looking toward the future and resting on their well-earned laurels.
the Templars hire, the Templars have revived the ancient idea of squires, with seasoned pilots and technicians being
encouraged to take on the less experienced of the recently recruited troops and teach them. This hands-on training allows Word of Blake Jihad
the unit to directly craft the skills of their own personnel quite effectively. It also allows the unit to retain the high standard
to which they hold themselves. The relationships forged by this practice have given their personnel a shared hardship and The Blackwood Templars remained mostly isolated in the years that followed the FedCom Civil War, but after the attack
a common bond. As a result of this practice, whenever a Templar is nominated to become Red Arm, everyone else in the on the StarCorps headquarters on Son Hoa by the Word of Blake in 3074, the Templars held a severe grudge against the
unit knows that it was earned by the nominee having done something above and beyond what is expected of them. religious zealot organization. At the beginning of the Blakist Jihad, the Templars elected to stay out of the fighting, despite
this grudge, as the unit had received no contracts related to the conflict. They finally entered the war after a call to arms
The Templars’ friendly relationship with the troops of the Dreadnaught BattleCorps stems from a series of joint training from their old allies, the Dreadnought BattleCorps. While it is possible, even likely, that the desire for revenge over the
exercises the units participated in during the mid-3050s. Multiple sources have explained how the numerically inferior attack on Son Hoa may have influenced the choice to join the BattleCorps and Ronin Free Companies Mercenaries as
Templars won these war games through a combination of experience, cunning, and captured Clan equipment. Despite members of the Lancaster Coalition, this has never been confirmed. Officially, the Blackwood Templars Mercenaries
the drubbing the Templars are rumored to have inflicted on the BattleCorps, or perhaps because of it, the units remained simply answered the call to arms made by a unit that they considered to be an ally. Their loyalty to each other and their
close. Rumors abound that a recommendation by none other than Colonel Thomas Lawrence, then commander of the allies brought out the best in the Templars during Operation LANCASTER’s brutal fighting on Ashkum IV. Unfortunately,
Dreadnought BattleCorps, contributed to the Blackwood Templars being recruited for Operation BULLDOG. this loyalty also led to significant losses during said fighting.
Operation BULLDOG After the conclusion of Operation LANCASTER, the Templars joined Stone’s Coalition and participated in the Coalition’s
assault on Terra near the end of Operation SCOUR. Following the liberation of Terra from the Word of Blake, the
During Operation BULLDOG, the Blackwood Templars consisted of two fifteen-’Mech companies, one combined arms Blackwood Templars returned to their homeworld of Son Hoa. While it appears that the losses taken by the Templars
company, one tank company and the twenty-four aerospace fighters. They also fielded a platoon of infantry equipped during Operations LANCASTER and SCOUR have severely soured the Templars’ taste for battle, they remain a cohesive,
with Kage Light Battle Armor as well as a platoon of Kanazuchi Assault Battle Armor. Where exactly they acquired these elite unit. As of 3085, the Templars have actively maintained their combat readiness, ready to defend their home at a
Kuritan-made battle armor suits is a matter of debate and is a subject on which Colonel Tyr Blackwood has steadfastly moment’s notice. Records indicate that Colonel Tyr Blackwood himself holds a post as at least a Knight, if not Paladin, of
refused to comment. Just the idea alone that the Templars came into possession of these battle armor suits with no the newly formed Republic of the Sphere. This title appears to be honorary at best, however, as the likelihood of the
official documentation to prove legal acquisition created a rift between the Templars and many soldiers of House Kurita’s Blackwood Templars being called into action by the Republic of the Sphere is minimal at best.
Draconis Combine Mustered Soldiery (DCMS) operating in the same theater of combat during BULLDOG.
Organization & Tactics
The Blackwood Templars joined in the efforts of Task Force Bulldog to reinforce and rescue the tattered remains of
Task Force Serpent on the surface of the Clan Smoke Jaguar homeworld of Huntress in March of 3060. During these As they are quick-strike specialists, the Blackwood Templars will generally avoid defensive and garrison contracts
events, the Templars were responsible for saving many members of the 1st Knights of the Inner Sphere. The Templars altogether. The Templars prefer to hit their target hard, salvage all they can, and withdraw from the combat zone as
would have been decorated for valor but, as with so many of the Templars’ undertakings, an incident during these events quickly as possible. Their best-known approach to attacking a target is to make maximum use of their extensive aerospace
led to a rift forming between the mercenary unit’s personnel and their allies. This incident involved members of the assets to neutralize their opposition’s own aerospace and artillery capability, allowing the Templars to claim total control
Templars executing a Smoke Jaguar MechWarrior who, during the battle, had killed an ejected Templars pilot. This act of of the airspace over their target’s location. The Templars’ AeroFighters are then used to strafe and deal significant damage
summary justice contributed heavily to the mutual enmity between the Knights of the Inner Sphere and the Blackwood to remaining opposing ground forces in preparation for the Templars’ own ground units to move in. The Templars field a
Templars. Colonel Blackwood’s actions made many of the rescued Knights feel as though the Templars had violated their larger than average aerospace wing for a unit its size; fielding on average thirty aerospace fighters gives them superiority
honor, while the mercenaries felt it was justice at its simplest. over their opposition in most engagements. Additionally, this overabundance of aerospace assets has reduced the
Templars’ dependence on artillery units in their two tank companies to nothing, and the unit has none as a result.
The Blackwood Templars returned to the Inner Sphere richer and better equipped than when they had left. In addition
to the salvage they acquired on Huntress, their convoy made a “rest stop” on an abandoned world while travelling back Blackwood Templars Mercenaries originally created by Zach Schaffer.
With the invasion of the Clans in 3050, the Ronin Free Companies were contracted to help stem the tide, losing 2 full
Free Companies and most of the 3rd, with the Matriarch herself falling in the process. It was at this time that her son,
Donaldarus Meridius, was given overall authority over the Ronin and tasked with rebuilding the core Battalion. The
following five years saw the reformation of the Ronin Free Companies through shrewd business deals as well as
recruitment, along with favors called in from various gang sources and washed-up Solaris VII combatants.
With a moderate fortune at his disposal, Free Colonel Donaldarus Meridius managed to restore an additional Free
Company, mostly full of tanks, repurposed industrial mechs, and repurposed industrial vehicles.
The first real contract given to the rebuilt Ronin came courtesy of the Capellan Confederation for operations in the
newly formed Chaos March in an attempt to regain several lost worlds. Heavy looting and battlefield salvage led to the
acquisition of more modern equipment and the gathering of several dozen Gauss Pattern Rommel tanks.
3056-3059 saw the beginning of shadow campaigns against the Word of Blake, as well as operations in the Aurigan
Coalition and Magistracy of Canopus, gaining the Ronin a strong, generally positive reputation in both Periphery States.
Operation BULLDOG
For Operation BULLDOG, the Ronin Free Companies sent forth one main battalion-sized Free Company with Task Force
Serpent, resulting in moderate losses but also the acquisition of a reasonable amount of Clan-based equipment. During
this time, the unit also acquired several Roughneck BattleMechs, to include a lance of the first refitted examples known
as “Ronin Specials”.
The first half of the 3060s saw the Ronin gain access to equipment through less than noble means. Through a raid at
the behest of the Capellan Confederation, the Ronin Free Companies acquired both infamy and nearly a dozen suits of
Cavalier Medium Battle Armor, along with a surprise Mad Cat MK II, from a FedCom convoy. The incident was quickly
forgotten due to no loss of life on the part of the Federated Commonwealth, though several independent contractors
were killed. Nevertheless, a FedCom spokesperson released a statement that they would refuse to offer any contracts to
the Ronin for the next 50 years.
The end of 3067 saw the beginning of the Jihad and the start of the Capellan Confederation’s campaigns against the
Word of Blake, in which the Ronin Free Companies took part. Pulled in multiple directions, the other four Free Companies
“If you’ve got the C-Bills, you’ve got the Ronin.” – Free Colonel Donaldarus Meridius split their time between the Magistracy of Canopus, the Aurigan Coalition, and the Capellan Confederation.
Founding & Early Years The Ronin Free Companies were seemingly involved in anti-Blakist actions from the very beginning of the Jihad, all the
way through to its end. Their employment with the Capellan Confederation led them to the battlefields of the “Shadow
The founding world of the Ronin Free Companies is the Capital world of the Aurigan Coalition, Coromodir VI. Created Wars”, placing them squarely in the sights of the Blakists time and time again. During the Shadow Wars, the Ronin Free
by Hansen Meridius and Kio Yoshida, both immigrants from the larger Successor States (Meridius from the Lyran Companies proved particularly frustrating to their Blakist enemies because their tactics seemed to shift or change outright
Commonwealth, Yoshida from the Draconis Combine), the Ronin began official operations in 2890, largely as a garrison in every engagement, never once repeating the same pattern. Their unpredictability proved to be one of the Ronin’s
force for various worlds and occasional pirate hunting. Over the following decades, the Ronin gradually gained strength. greatest assets. Meanwhile, unofficial backing of a Great House, specifically House Liao, allowed the Ronin to bolster their
ranks and gain key technical advantages to let them compete properly with Blakist units.
In 3022, during the infamous coup by Santiago Espinosa that saw the royal Arano family overthrown, leading to the
creation of the Aurigan Directorate, the Ronin were split on whom to support. The Ronin instead began to fight amongst In the years leading up to Operation LANCASTER in 3077, the Ronin Free Companies were mostly united in fighting in
themselves over differing opinions as to the right course of action. The politically-charged infighting continued until 3025, the Siam system across several planets and stations. Though the fighting was thick, the Ronin still conserved a significant
ending with the reappearance of Kamea Arano, commonly known as Lady Kamea. By then, the Ronin had been reduced portion of their forces—in the form of their Oni Slayers and Morningstar Free Companies—to aid the Dreadnought
to an understrength battalion under the command of the unit’s Matriarch, Whitney Meridius. BattleCorps 1st Regimental Combat Team and Blackwood Templars Mercenaries in Operation LANCASTER.
Reuniting under the banner of Lady Kamea’s “Arano Restoration” movement, the Ronin were used to strengthen the This move by the Ronin Free Companies took the Word of Blake by surprise, as the only notable direct historical
hold on certain planets as well as to aid in some of the more prominent battles. Once Lady Kamea was restored to the connection between the Ronin Free Companies and the Dreadnought BattleCorps was when the two units battled each
throne and the Aurigan Coalition was reconstituted, the Ronin were broken up into seven Free Companies. Three of these other on Cordiagr V during the Fourth Succession War. This hostile engagement in 3028 had ended with the BattleCorps
formed a constant Ronin Free Companies force. The other four were largely free to operate as they saw fit within mostly being allowed to honorably withdraw from the world. While the Ronin’s choice to participate in LANCASTER weakened
legal means and met every other year for equipment assignments and general camaraderie. their efforts in the Siam system considerably, the Free Companies left behind were still able to free the system. This
In the years following Operation LANCASTER, the Ronin Free Companies suffered considerable casualties. This included The Ronin Free Company known as “Morningstar” is the 2nd Free Company, and as of 3085 it is currently out of action,
the effective destruction of several Free Companies. One Free Company was destroyed completely, another disbanded, pending an extended rebuilding period after a particularly devastating encounter against the Word of Blake in the final
while several more suffered catastrophic losses that removed them from being combat ready for several years. years of the Jihad, resulting in 73% losses across the entire unit.
Organization & Tactics The Ronin Free Company “Drunken Bandits” is the 3rd Free Company. Its location is unavailable but is currently
attached to elements of the Capellan Confederation’s Warrior House Imarra. This Free Company is known for its heavy
The Ronin Free Companies are organized into several different collections of units. The term “Free Companies” is used use of infantry and armor. It currently possesses only two lances of light to medium BattleMechs. The Drunken Bandits
as a direct reference to the ancient Terran term used to describe European mercenary units in the 13th-14th centuries. Free Company has historically been employed most often for urban security, escorts, and rescue operations. This unit is
These Free Companies consisted of a wide variety of soldier types and were beholden to no real master, hence the name. notable for its fleet of high-speed infantry delivery craft.
Currently led by Free Colonel Donaldarus Meridius, the “Oni Slayers” is seen, among the seven Free Companies, as the The “Dragon Riders” Free Company was the Ronin’s 4th Free Company. The unit was declared to be a total loss during
“command and control” Free Company. The Oni Slayers is comprised of three full BattleMech companies, three full armor the fighting against the Word of Blake in the final years of the Jihad. The unit was destroyed by an orbital bombardment
companies, and three mixed companies of infantry and combat engineers. Several DropShips and a JumpShip take care after successfully fending off Word of Blake Special Forces. The specifics of this event have yet to be released to the public.
The Ronin’s “Trebuchet” is the 5th Free Company. Fittingly named, the Trebuchet Free
Company primarily consists of long-range support and artillery-based units. This Free
Company is mainly a garrison unit. Two companies of mixed Arrow IV and Long Tom
Artillery vehicles, as well as units armed with heavy mortars and other indirect-fire
weapons, make up the bulk of the unit. There is one lance of quick reaction BattleMechs,
and an additional reinforced company of spotter and fire support vehicles of mostly light
and medium weights.
Ronin Free Company “Naginata” was the 6th Free Company. This company has been
effectively disbanded due to Word of Blake infiltration. Once the Blakist agents were
discovered, the Free Company erupted into a bloody period of infighting, culminating in a
pyrrhic victory for the loyal Ronin Free Company elements.
The Naginata has predictably been placed on garrison status as it rebuilds its equipment
and attempts to recruit. Free Colonel Donaldarus Meridius trusts the 6th Free Company,
but the unit continues to suffer low morale, largely due to lingering paranoia about having
missed any Word of Blake members in their ranks. The unit was once comprised of two
BattleMech companies, one armor company, and one infantry company. Roughly half of
these forces remain in the company after the infighting, with the Naginata having suffered
no less than 60% casualties. It is hoped that the unit will be reestablished as a proper Free
Company in the future, but as of 3085 the Naginata is years away from reaching this goal.
The 7th Free Company, the “Bastard Sword”, is seldom discussed or seen outside of the
meetings that it holds with Free Colonel Donaldarus Meridius. It has been suggested that
he directly commands this Free Company in addition to the Oni Slayers. Contracts taken
by this Free Company typically involve actions that fall into the categories of Black Ops
and Deniable Ops for several different intelligence organizations. Primarily under the
employ of the Aurigan Coalition, this unit has also seen action with the Magistracy of
Canopus against the Marian Hegemony as well as with the Capellan Confederation against
the Word of Blake.
The Bastard Sword Free Company was most recently reported to be comprised of one
BattleMech Company, one armor company, and one Infantry Company that employ
Nighthawk Power Armor. Equipment is typically considered top of the line, with the ability
to also test out many new weapon, vehicle, and BattleMech prototypes. One interesting
note about the Bastard Sword Free Company is that under most circumstances, no salvage
is ever taken; the unit insists on payment only in the form of C-Bills. This unit prides itself
on timely contract completion and maximum financial gain.
Ronin Free Companies Mercenaries created and written by Donald Butler with minor edits
and additions by Devin Ramsey.
The Word of Blake Protectorate Militia 102nd Provisional Division was comprised of both veterans and green troops,
as it was assembled from fresh troops as well as remnants of destroyed units. This combination proved to be both a boon
and a curse to the unit in the long run. It benefitted the unit in that the inexperienced troops were able to learn directly
from their more experienced veteran brethren. It was a curse in that, even with the experience brought to the table by
the veteran personnel, much of the unit lacked actual combat experience when it was deployed in 3076 to the world of
Ashkum IV.
Initially assembled haphazardly in early 3075 to serve as cannon fodder for the Word of Blake’s worsening war against
the rest of the Inner Sphere, the 102nd Provisional Division began as an Ad-Hoc Militia Level III force. The unit then quickly
found itself swelling with an influx of veteran soldiers before the unit saw actual combat. The Word of Blake leadership
quickly changed its attitude toward the unit just as the influx of soldiers began, and by mid-3075 the unit’s planned
utilization had shifted wildly from cannon fodder to that of a special task force.
By late 3075, the unit had reached a full-fledged Level IV in size, with more than two hundred ‘Mechs, combat vehicles
and aerospace fighters. These numbers were further enhanced by a sizable Motorized Infantry element, as well as two
Level IIs of Manei Domini MechWarriors piloting Celestial OmniMechs backed by a Level II of Tau Wraith Infantry. Some
theorize that the presence of the elite, cybernetically-enhanced Manei Domini may have meant that this unit was
intended to become a “56th Shadow Division”. However, this theory has largely been dismissed.
The 102nd Provisional Division is believed to have seen action as a unit only once: on Ashkum IV in January 3077.
Although it was unknown at the time, this unit had been deployed in preparation for the arrival of the 55th Shadow
Division. The 102nd was deployed with surprisingly little notice to the Ashkum system, tasked with quietly securing a
mixed nuclear and thermonuclear weapons stockpile discovered on Ashkum IV. The Word of Blake took control of the
local HyperPulse Generator Station, ostensibly offering services to help the economically challenged people of Ashkum
IV to regain some of their regressed civilization and bolster the planet’s defenses and economic strength. The 102nd were
generally accepted, if not welcomed, by the local population. For those who did not welcome the Word of Blake to
Ashkum IV, the presence of two Blakist Lola III-class Destroyers in orbit of one of Ashkum IV’s moons ensured that little
or no resistance stood in opposition to the 102nd’s occupation. Though later joined by a third ship of the same class, it
was the presence of these two WarShips in-system that drew the attention of the Dreadnought IntelCorps to the world
of Ashkum IV, given the Ashkum system’s proximity to the Acala system, the Dreadnought home star system.
Shortly before the 55th Shadow Division could reach the Ashkum system to rendezvous with the 102nd, the combined
forces of the Lancaster Coalition began their assault on the Ashkum system on New Year’s Day, 3077, with the goal of
uprooting and eliminating the 102nd Provisional Division. During the fighting that ensued, the 102nd’s lack of real combat
experience showed in their poor coordination and tactics. Though many of the 102nd’s troops demonstrated that they
were indeed seasoned veterans, the inexperienced troops were quicker to fall into disarray, playing directly into the hands
of the Lancaster Coalition. The nearly constant sleight-of-hand tactics played by the well-equipped and seasoned veterans
of the Dreadnought BattleCorps, Blackwood Templars and Ronin Free Companies simply overwhelmed and destroyed the
102nd before seizing military control of Ashkum IV. The forces of the Lancaster Coalition had no intention of staying on
Ashkum IV beyond the elimination of the 102nd Division, but the discovery of the nuclear arsenal that the 102nd had
been sitting on quickly destroyed any hopes for a quick end to the mission.
Some members of the 102nd Division survived the destruction of the unit after the Lancaster Coalition’s landfall and
worked to break down communications on-world through powerful jamming devices. A fortuitously timed powerful
storm settled over much of the continent of Capri, helping to complete the communications blackout by grounding
aerospace fighters and DropShips alike. While those responsible for jamming the communications of the Lancaster
Coalition forces were hunted down and eliminated, it cost the Coalition precious time that could have been used to
prepare for the arrival of the 55th Shadow Division, which had by then already entered the system.
By February of 3077, the Word of Blake’s 102nd Provisional Division was officially designated destroyed, with numerous
Prisoners of War captured and imprisoned. These POWs were eventually handed over to Comstar later that year.
Strangely, even as of 3085, none of the names of any personnel associated with the 102nd Provisional Division have
ever been made available to the public, despite the destruction of the unit. It is possible that this may have to do with the
current status of POWs taken during Operation LANCASTER, but it is unclear why this information has been withheld from
public record in its entirety—including the names of the dead.
Little is known of the 55th Shadow Division, the unit known as “Thanatos’ Grip”. The 55th Shadow Division was one of
the last Shadow Divisions created by the Word of Blake. Comprised entirely of elite, cybernetically-enhanced Manei
Domini soldiers, the 55th Shadow Division was a powerhouse of a unit and a most unwelcome late arrival during
Operation LANCASTER. Aside from the encounter in 3077 on Ashkum IV during LANCASTER, there is only one recorded
example of the unit being identified in combat, and that was during the Siege of Basalt IV in September 3069. It is curious
that in both cases, the opposition that they faced was primarily the Dreadnought BattleCorps. This link hints at least at
the possibility that the 55th Shadow Division may have been deployed to Basalt in anticipation of the BattleCorps’
appearance in-system. To what end is unclear. Speculation suggests it may have been either an attempt to prepare the
55th Shadow Division for a more significant future engagement with the BattleCorps or a genuine attempt to wipe out
the BattleCorps altogether in preparation for a future move on Acala III, the BattleCorps’ homeworld. Their failed attempt
to wipe out the BattleCorps on Basalt may have pushed back their plans to attack Acala III. None of the information
gathered is concrete when it comes to the 55th Shadow Division’s history or goals.
Various intelligence sources suggest that the 55th Shadow Division was assembled in secret, much like the Word of
Blake’s other Shadow Divisions, but as this unit was assembled specifically for the purpose of opening an entire new
theater of war, it was held in reserve until the time was right. This suggestion is contradicted, however, with the very
clear level of combat experience and coordination that was demonstrated when the unit landed on Ashkum IV. There is
little doubt that this Manei Domini unit was comprised entirely or almost entirely of seasoned veterans. Whether they
were assembled from other units, or the unit gained combat experience together in undocumented battles, no conclusive
proof has been forthcoming, even in the years following the end of the Word of Blake Jihad. All files regarding the 55th,
as with much of the documentation regarding the Word of Blake’s black ops in general, were deleted prior to the
liberation of Terra. As of 3085, the only name that has surfaced regarding leadership of this unit has been “Precentor
York”. No other information about this individual has surfaced, suggesting that even this name may only be an alias.
When first encountered on Basalt IV by the Dreadnought BattleCorps 1st Regimental Combat Team in September of
3069, the 55th Shadow Division was relatively well-equipped as a standard Level IV-Kappa; ‘Mech-heavy, but with
reasonable ground vehicle, battle armor and aerospace support. When engaged for the second recorded time in 3077 on
Ashkum IV, the 55th was exceptionally well-equipped, even for a Manei Domini unit. More importantly, their numbers
had nearly doubled. Many of the machines used by the unit were identified as being OmniMech configurations created
exclusively for the 55th Shadow Division, with the rest being variants of existing ‘Mech models utilized either only or at
least primarily by the Word of Blake. As this engagement occurred prior to the introduction of the Word of Blake’s own
Land-Air ‘Mechs, no LAMs were present during this engagement.
Of the cybernetically-enhanced Manei Domini soldiers that made up the 55th Shadow Division, nearly all of them
utilized fully augmented bodies that included some of the most advanced technology available. These enhancements
generally included not only physical strength and sensory augmentations, but also included aesthetic surgery typical of
most infiltration units. It is unclear why so much attention to detail was paid to the appearance of every soldier, from
MechWarrior to infantryman. It is equally unclear why even the MechWarriors received the same types of physical
strength augmentations and skeletal reinforcements that would be most often associated with Manei Domini infantry.
It is unfortunate that the long-term goals created for this unit by the Word of Blake have never been officially
confirmed. It is clear the 55th Shadow Division was meant to open an entirely new theater of war near the Capellan
Confederation/Federated Suns border. The likely intent was to split the attention of the militaries opposing the Word of
Blake, as multiple of the Great Houses had been pooling resources into the upcoming joint assault on the Blakists titled
Operation SCOUR. The sheer scope of the nuclear arsenal that the 55th were intended to be armed with after their
rendezvous with the 102nd Provisional Division makes it clear that they would most certainly have wreaked havoc had
they not been stopped by the Lancaster Coalition in 3077. It is likely that billions, perhaps tens of billions of lives would
have been lost or otherwise severely affected had the 55th Shadow Division succeeded in their mission.
Although hundreds of crew members manning the 55th Shadow Division’s DropShips were successfully taken prisoner
when a handful of their surviving DropShips were captured at the end of Operation LANCASTER, nearly all of the 55th
Shadow Division’s ground troops were killed in action during the fighting on Ashkum IV following Colonel Ann Lawrence’s
infamous “Take no prisoners” order. However, a handful of infiltration specialists escaped into the general population.
Once successfully hidden among the civilians of Ashkum IV, they sowed the seeds of discontent before being hunted
down and eliminated by newly arrived Comstar personnel. Although the 55th was officially designated as destroyed by
the end of February, 3077, it was several years before the final members of the unit were tracked down and terminated.
The following planetary profiles are included in this document as the information they contain helps to explain the political and military situation leading up to and setting the stage for Operation
LANCASTER. Most of the information contained within these articles is not covered in publicly available documentation elsewhere.
Geophysical
System Position: 3rd
Jump Point Distance: 6.31 Days
Moons: 2 (Mánagarmr & Máni)
Surface Gravity: 1.11
Atmospheric Pressure: 1.1 BAR (Breathable – High O2)
Equatorial Temperature: 32° Celsius (Temperate)
Surface Water: 76%
Highest Native Life: Mammals and Reptiles
Founding: 2475
Primary Landmasses/Continents: 11
Secondary Landmasses/Islands: 2,500 (Approximate)
Infrastructure
Ruler: George Fitzgerald
Capital City: New Sydney
Population: 1,434,700,000
Socio-Industrial Levels: A-A-A-B-B
HPG (Representative): A (Independent)
The land masses of Acala III are varied and numerous, with eleven primary continents and hundreds of smaller islands. Most of the continents have mountainous coastlines due to ancient tectonic movements. Some active
volcanoes do exist among a handful of the continents, although human civilizations for the most part have historically been built up in stable regions, away from these known dangers. For all intents and purposes, Acala III is
a Terra-like paradise world that has become a jewel of human technological development and military establishment. As of 3085, the Acala Semi-Autonomous Region is synonymous with Dreadnought Interstellar Industries
as well as Dreadnought’s own BattleCorps and DefenseCorps. The Acala system has recently become considered as one of the most heavily fortified star systems in the Inner Sphere.
The first ‘Mechs to set foot on Acala III were two BNC-1E
Banshees, an MCK-65 Mackie, an HEP-2H Helepolis, two CRS-
6B Crossbows, two SHD-1R Shadow Hawks and four WSP-1
Wasps. Though deactivated, many of these machines have
been restored and are on display at the New Sidney Historical
Museum. The notable exclusion from this group of ancient
machines on display is the entire lance of Wasps. The 20-ton
machines were quickly chewed up and torn apart by the large
local reptilian creatures known as gaatee, but the heavier
machines were able to withstand the ravages of the world.
The remains of one of the Wasps can be viewed at the “Gaatee Encounter Experience”, which is a part of the gaatee the most powerful local creatures were overtly hostile on contact.
exhibit of the Acala III Planetary Natural History Museum in New Sydney.
Star League Era
Acala III became home for tens of thousands of people within the following decade. It soon became planetary law that
all citizens were required to serve a minimum of one compulsory tour of duty in the military (far less than what is expected As the development of civilization proceeded on Acala III, so too did the perimeter defense systems. It became common
today). The reason for the choice to require military service of the citizenry is easily explained: the New Sydney Defense practice to have defensive turrets in place every kilometer around the growing cities. Eventually, instead of continuing to
Force was all that stood in the way between the citizenry itself and the more hostile indigenous life forms on the world. move the turrets and defensive walls every time the cities needed to expand, they would instead simply leave the walls
While it was quickly discovered that the magnificent Acalan dragons could be trained to serve with the military, none of and older turrets in place, while building better defensive perimeters up to several kilometers beyond the city’s perimeter
the other local fauna could be considered friendly. Some of the local creatures proved indifferent toward humans, but at that time. The result of this practice is a multilayered form of perimeter defense structure that makes attacking any of
The long-term result of Hanse Davion’s choice to deploy the BattleCorps was a reduced long-term faith in House Davion, The hastily deployed local militia forces quickly reinforced the surviving patrol units, turning the tide while test pilot
the Federated Suns, and the later Federated Commonwealth as a whole. The great irony is that there had been no prior Adrian Steele took his Mad Cat out to pursue the stolen Sumaire prototype. By the time the sun rose in the morning, all
interest in independence from Davion rule, but this one event was the first of a handful of events that eventually led to the pirates’ BattleMechs and other ground forces were dead or captured, and the DropShip had fled.
the founding of the Acala Semi-Autonomous Region.
The results of the raid were not-inconsiderable damage to the outskirts of New Sydney and significant damage to a
In early 3042, an extended series of raids carried out by mercenary units began to repeatedly test the defenses of Acala handful of areas farther into the city. The Eagle Proving Grounds also sustained considerable damage in the attack. The
III. These numerous attacks resulted in casualties, but the number of casualties was relatively low initially. Despite the worst was the loss of the orbital dry dock facility, destroyed in what appeared to be an accidental explosion that began
minimal losses, the frequent attacks began to take their toll. The viciousness and the zeal with which many of the inside of the pirate DropShip while it was docked to the facility, the pirates forcing the dry dock workers to assist with
outwardly unrelated units struck soon led to a belief that the identities of the mercenary units were in fact a cover for a repairing and refueling the DropShip under threat of destruction by the pirates’ guns.
House Military force probing Acala III, with the most likely culprit being the Capellan Confederation. Some of the attackers
were in fact desperate mercenaries who preferred to surrender rather than be killed to the last man, but all confirmed The funding for the pacifist movement was later traced back into Capellan Confederation territory, but beyond that
that their contracts were handled by an intermediary. An equal number of the supposedly independent units ensured the trail went cold. It was discovered that individuals associated with the pacifist movement were also responsible for the
that they left no survivors behind. This trait would not have drawn so much attention if not for an incident where a raider communications blackout that prevented rapid response by the DefenseCorps, as well as being responsible for acquiring
Warhammer ensured that a MechWarrior in an effectively disabled, lightweight Valkyrie could not be captured—by the landing codes used by Murphy’s Marauders to get past the early-warning systems. The individuals responsible for the
blasting the head section of the Valkyrie apart in a clearly intentional action. security breaches and outright betrayal from within were quickly apprehended and, in many cases, were convicted of
treason. In the aftermath of the attack, the pacifist movement effectively died overnight after being proven to be the
The Acalan government pleaded with House Davion for assistance, but after three increasingly intense attacks without Capellan-backed farse it was.
a response from House Davion’s Federated Suns, the Dreadnought BattleCorps took matters into their own hands to
ensure that the raids would finally come to an end. The Dreadnought-class WarShip D.B.C. Trinity was put into a position In light of these events, the “Falling Skies” project resumed. This project, originally launched in the 3030s and then
a single jump away from the Acala system and waited for the next raiding party in late 3042. cancelled in 3043, was focused on the development of Orbital Defense & Refit Platforms (ODRPs), which served as a
combination of planetary defense battle stations and orbital dry docks. In 3059, with the D.B.C. Phoenix away as part of
The raiding party in question turned out to be a large military assault force. Though the actual origin of the hostiles Operation BULLDOG and the D.B.C. Trinity reassigned to offer orbital defense over Theris in the Waycross system, the
was never conclusively determined, the hostile DropShips were no match for the Trinity. The entire group of DropShips first completed ODRP gave the people of Acala III a sense of security similar to that which had previously only been felt
was wiped out in a matter of minutes after the Trinity appeared at a pirate point directly in the path of the DropShips. All with the presence of a WarShip in orbit. Despite the extreme cost involved, the continued manufacture and deployment
four hostile JumpShips immediately jumped away, clearly risking damage to their jump drives to avoid capture. of more of the ODRPs was supported heartily by the population of Acala III for years to come.
An offer for the invaders to surrender peacefully was made, with no reply from the hostile forces. It is estimated that Federated Commonwealth Civil War
in total there may have been roughly two full regiments’ worth of troops aboard the DropShips that the Trinity intercepted
and destroyed. There were no survivors among the hostile vessels. Every one of the DropShips made sure that they were The buildup of armed forces on Acala III continued into the beginning of the Federated Commonwealth Civil War in
under high-G acceleration when they were destroyed, ensuring that the chance of salvaging anything from the 3064. By the midpoint of the war, in 3066, three ODRP stations were in place and active in Acala III’s orbit, providing
wreckage—including learning the true origin of the attackers—was effectively reduced to zero. impressive defensive capability in terms of anti-capital-ship firepower. The stations also served as home bases for rapid-
deployment aerospace fighter screens not seen in the Inner Sphere since the time of the Star League. In total, Acala III
With the raids stopped, the prosperity of the people improved considerably, and various industries began to truly show had approximately four hundred aerospace fighters, three hundred of which were split evenly between the trio of ODRPs.
progress for the first time in years. While the fighters themselves were largely older fighter craft that had been reconditioned, the sheer number of craft
made for a formidable and intimidating defensive screen. As a result of the brute defensive capability, Acala III was able
Clan Invasion to remain uninvolved in the FedCom Civil War.
A pacifist movement began to build strength in the late 3040s, reaching its peak shortly after the Clan Invasion began. Despite the lack of direct involvement of the Acala system in the Federated Commonwealth Civil War, Katrina Steiner-
The pacifist movement itself seemed to rise up from the relative peace that had settled over Acala III. The movement Davion’s actions toward the Dreadnought sister-world of Theris culminated in a three-month military occupation of the
protested the continued compulsory service in the armed forces on Acala III, as well as the manufacturing of military planet, which only served to increase the long-term distrust of the Great Houses among the populace of Acala III. This
equipment and gradual buildup of arms on the world. event also fueled an increased interest in separating Acala from the politics of the Great Houses as a whole. A proposal
for the creation of a Semi-Autonomous Region was put forward, but it was agreed that the time was not yet right to act.
With the Trinity away from the Acala system in 3053 for training purposes, a group of pirate raiders known as Murphy’s
Marauders took advantage of the reduced defensive capabilities of Acala III to make a well-planned attack on the world In 3065, large subterranean deposits of germanium ore were discovered on Máni, the larger of Acala III’s two moons,
with the goal of capturing prototype Sumaire Assault BattleMechs. The pirates supplied accurate clearance codes, after a large meteorite impact. It was 3068 before combined efforts between Dreadnought Interstellar Industries and
allowing an unchallenged landing at Acala III’s New Sydney Spaceport. In the dead of night, and under a communications their partner corporation Orbital Heavy Industries successfully established mining facilities on the surface of Máni.
blackout, the pirates moved in and managed to secure the DefenseCorps facilities, the Acala III Military Academy, and the
Eagle Proving Grounds. Word of Blake Jihad
With a massive protest organized around the Dreadnought DefenseCorps Vehicle Operations Center (VOC), and the An attempted assassination of George Fitzgerald (the Baron of Acala III, as well as the President of Dreadnought
communications blackout blanketing all military and civilian bands, there was no way for the DefenseCorps to organize a Interstellar Industries) in December of 3068 that resulted in the death of nearly his entire extended family—as well as the
response. Unfortunately for the protesters picketing the DefenseCorps VOC, many of them were killed by the pirates assassination of Colonel Thomas Lawrence the following month—were soon linked to the Word of Blake. These events,
seeking to secure the facility. It was in fact the sole actions of Shandra Jaeger, a woman who had retired from active as well as several other attacks on civilian Dreadnought Interstellar personnel, quickly turned the people of Acala III
Acala III hardened its defenses and prepared for war even as Dreadnought Interstellar Industries facilities on eight Historically there had been an average of approximately forty percent of Acala III Military Academy graduates moving
other worlds were evacuated in 3069. The horrific events on Basalt IV during the last of these evacuations severely mauled off-world to serve in House or independent militaries after their compulsory two-to-four years of service (depending on
the Dreadnought BattleCorps, leading to a time of recovery spent on Acala III. A sweeping investigation throughout all of application) in the Acala III Planetary Militia and/or Dreadnought DefenseCorps. In the second half of the 3070s, however,
Dreadnought led to the eradication of nearly all of the Blakist sleeper agents on the world. While this investigation was this percentage dropped to roughly one percent, with most who chose to serve beyond the compulsory time opting to
remarkably effective overall, it was not perfect, and it took several years. stay on with the DefenseCorps and some even applying to bolster the BattleCorps’ numbers.
In January of 3075, six months after the evacuation of the world of Theris had begun, evidence began to emerge that After the losses suffered by the Dreadnought BattleCorps during Operation LANCASTER, the bloody campaign that took
possession of the Comstar-operated HyperPulse Generator (HPG) on Acala III had been compromised, with the Word of place in the Ashkum system in early 3077, support for the BattleCorps only grew. This allowed the unit to rebuild within
Blake having taken over control of the facility. A series of murders of Comstar personnel were investigated by one of the two years back to nearly pre-LANCASTER strength.
Dreadnought IntelCorps’ newest and most resourceful intelligence officers, Misato “Cat’s Eye” Takahashi. Ms. Takahashi
quickly learned that these personnel all had a single connecting factor: none had been supporters of the Word of Blake. Jihad Aftermath & Semi-Autonomy
In fact, all of them had been staunchly opposed to the Blakist “splinter faction” that had broken off from Comstar.
With the rebuilding of the BattleCorps and production of new WarShips well under way, the Acala system moved to
The results of the investigations were sent by JumpShip courier to a known Comstar-operated facility, where the become a semi-autonomous state within House Davion’s territory. In December of 3080, amidst the meeting on Terra to
suspicions around the HPG’s compromise were confirmed. The facility had indeed been taken over by the Blakists. With form the Republic of the Sphere, George Fitzgerald, along with Colonel Ann Lawrence and her closest subordinates, met
the Word of Blake gaining total control over the HPG on Acala III, but unaware that the Dreadnought IntelCorps had with Victor Steiner-Davion, Yvonne Steiner-Davion, and Devlin Stone to present their case and make the declaration.
caught on to their actions, the HPG operators attempted to continue to operate outwardly as though nothing had Fitzgerald and Lawrence both pointed out the pattern of how House Davion’s Federated Suns had failed to aid Acala when
happened. it was most desperately needed, and the Federated Suns had in fact only caused problems for the Acalan people.
A carefully planned rapid strike operation took place just one week after the remaining HPG personnel were confirmed Together, Lawrence and Fitzgerald explained the reasoning, showing the pattern throughout history.
to be in the service of the Word of Blake. During this strike, every operator of the HPG and individual related to operation
of the facility, both on-duty and off, were simultaneously captured or killed in a matter of minutes. When the Capellan Confederation took over Acala from the Federated Suns of House Davion with Davion not lifting so
much as a finger to help, it was three centuries before the Federated Suns freed them, and even then, they did nothing
Of those captured, nearly all of them committed suicide while in confinement, most discovered to have at least some to help Acala recover. For Davion, it was just regained territory.
sort of cybernetic enhancement that was not cataloged in their public records. Two attempted to break out, using their
cybernetic enhancements to kill their guards and break free from their bonds with relative ease. One was stopped by a They cited how Hanse Davion had thrown the BattleCorps into the Fourth Succession War based on misleading
squad of battle armor, while the other was crushed under a ‘Mech’s foot. A handful of Comstar personnel that had information from a power-hungry politician (Lawrence and Fitzgerald emphasized how this individual had been the only
escaped death at the hands of the Word of Blake were kept in confinement, though treated quite respectfully and well politician to ever serve Acala III’s government who was a member of the Davion family) and that the BattleCorps had
cared for, until after the end of the Jihad. been sent on what effectively could be summarized as a suicide mission—a suicide mission that they had survived largely
because of the unusually honorable nature of the Ronin Free Companies Mercenaries that they faced, allowing the
With the HPG no longer under the control of Comstar or the Word of Blake, Dreadnought was presented with a unique BattleCorps to withdraw.
opportunity. Among the data recovered on Theris were partial operations and maintenance files for SL CommNet
HyperPulse Generators. The information had been recovered during the backup of the entire database on Theris a century When the world was under repeated attack from what was suspected to be Capellan-hired or actual Capellan forces,
before, albeit not actually discovered until shortly before the beginning of the Jihad as it had been in an innocuously Davion did nothing to help, and the forces of the Dreadnought BattleCorps and DefenseCorps were forced to take action
named file folder. The incomplete information would not have been possible to use were it not for some of the former to defend the Acalan people without any assistance from the Federated Suns.
Clan technicians and scientists with experience operating an HPG that had joined Dreadnought’s ranks during the time
spent on Pantheress VI following Operation BULLDOG. During the Federated Commonwealth Civil War, Archon-Princess Katrina Steiner-Davion had forced Acala III’s “sister
world” of Theris (Waycross II) to heel by force so that the Dreadnought facilities there were forced to produce machines
For the next several months, all messages had to be carried by JumpShip courier to and from the Acala system, slowing for her own war effort against her brother. Katrina’s loyalists captured the D.B.C. Trinity in orbit over Theris, and it was
communications rates, but allowing time to work out what to do with the HPG. The Acala III HyperPulse Generator was clear that she intended to take the Trinity for her own purposes. Were it not for the brave souls who spent months in
restored to full functionality in May of 3075. crawlways and ventilation shafts to retake the ship, she likely would have kept the world and vessel for herself. Yet again,
there was nothing from Davion in terms of recompense for the lives lost when Katrina attacked and seized Theris.
The first message received by the restored HPG was the report of a devastating attack on the sister world of Waycross
II (more commonly known as Theris). The message itself had been forwarded by the only Dreadnought JumpShip to The proverbial straw that broke the camel’s back had come when the Word of Blake had amassed on Ashkum IV to
escape the assault. A squadron of Word of Blake WarShips had attacked the Waycross system. It was later learned that strike. Once again, House Davion’s Federated Suns were nowhere to be seen, and again the BattleCorps was forced to
the D.B.C. Trinity had been destroyed in orbit over Theris after several of her critical systems were sabotaged, leaving the independently take up arms to defend the Acala system, even being forced to go so far as to hire mercenaries to reinforce
ancient Battleship in a poor state to fight the three Blakist vessels attacking her. Tragically, the Theris DefenseCorps, along their numbers to launch Operation LANCASTER and take on the Word of Blake directly.
with every civilian that had not been evacuated from Theris before the assault, were annihilated in thermonuclear hellfire
after a month of desperate resistance. The case made was clear: As the Acala system had been forced to protect itself time and time again with no assistance
from House Davion, it should not have to be considered a direct subject of House Davion. As a result of the utterly
The attack on Theris in 3075 came after a full year of evacuating the Waycross system in anticipation of a Blakist attack, smashed state of House Davion’s Federated Suns Military and the considerable military strength that had built up in the
and the destruction and loss of life only served to further harden the people of Acala III against the Word of Blake. The Acala system under the banner of the Dreadnought BattleCorps and DefenseCorps, the Federated Suns was in no position
loss of the Trinity and thousands of civilians and soldiers on Theris pushed the people of Acala III to actively work toward to oppose the declaration.
building themselves up to stand against any form of Word of Blake attack. A fourth ODRP to further augment Acala III’s
defenses began construction. The recovered Clan-based production capability taken from Theris was incorporated into Surprisingly, Stone recognized the claim, despite the sharp dismissal of any possibility of Acala III disarming itself. The
facilities on Acala III to continue the process of augmenting the Dreadnought BattleCorps 1st Regimental Combat Team people of Acala III had survived through their own resourcefulness and independent military, and they would not give it
Geophysical
System Position: 2nd
Jump Point Distance: 7.92 Days
Moons: 1 (Unnamed)
Surface Gravity: 1.27
Atmospheric Pressure: 1.3 BAR (Breathable)
Equatorial Temperature: -4° Celsius (Arctic)
Surface Water: 87%
Highest Native Life: Mammals
Founding: 2750
Primary Landmasses/Continents: Uncharted
Secondary Landmasses/Islands: Uncharted
Infrastructure
Ruler: None
Capital City: Cameron City (Ruins)
Population: 0 (Abandoned)
Socio-Industrial Levels: N/A
HPG (Representative): N/A
Waycross II, known more recently as “Theris”, was once home to a human society based around largely Star-League-era facilities. However, as of 3085, Theris is an ice-covered world devoid of human life. The greatest
areas of interest on the world are a handful of cities that were once home to the indigenous population. These cities are now irradiated severely enough to make human life impossible, thanks to numerous fifty-megaton
thermonuclear explosions. While still technically habitable elsewhere, and it is home to significant metallic ores and mineral deposits of interest, the future of this world is at best uncertain.
Kerensky was given a tour of the facility and was reportedly extremely impressed by what he saw there: a completely Rediscovery
modular ‘Mech and combat vehicle production facility the likes of which had not been seen outside of the Defiance
Industries facility on Hesperus II. If anything, the facility boasted higher standards of technology and quality than even When the long-dormant S.L.S. Phoenix was rediscovered by the Dreadnought DiscoveryCorps JumpShip D.I.I.S. Delara
the Hesperus II plant, albeit in a slightly smaller structure. The facility, called Cameron MechWerks, was capable of in the ES-150/D star system in 2946, among the vessel’s records were the coordinates for the home system from which
producing up to two ‘Mechs per day, even if they were different chassis types sharing the same assembly lines. the ship had originated. It did not take long for the DiscoveryCorps to find the great facilities there. Using the archived
data stored aboard the Phoenix, they were able to quickly track down the subterranean manufacturing facilities on the
The technology behind the factory was impressive, to say the least. It was also not the only facility to be shown to surface of Waycross II. Not long after, they were able to locate and begin exploring the hidden, asteroid-based dry dock
Kerensky during his visit. The other facility was that of CrossWays Station—a naturally hollowed-out metallic asteroid that and shipyard in the star system, CrossWays Station. The Phoenix was secretly returned to CrossWays Station—her original
had been used as the construction base for an all-new black-water capital ship. This new vessel, which had recently home base—in 2948. Once there, the ship was to remain hidden for the foreseeable future, kept under lock and key with
completed construction, was the Texas-LFR-class S.L.S. Phoenix. Records of the visit indicate that General Kerensky was only a small number of high-ranking Dreadnought personnel privy to any information regarding the vessel’s existence.
surprised and awed by the pristine Battleship, the powerful vessel having been spared the ravages of the war that had
claimed so much of the SLDF fleet. With the Waycross system entirely off the radar of any of the Great Houses and even Comstar, Dreadnought quickly
moved in to resettle Waycross II. As far as any of Comstar’s agents could figure at the time, large portions of the
Great Exodus DiscoveryCorps and EngineerCorps were moving on to an unknown project. By the time that Comstar caught wind of it,
it was too late to place any agents in their midst, as they were gone within a fortnight from the world of Acala III.
When Operation EXODUS was carried out by Kerensky’s Star League Army, the Waycross system was abandoned. Two
SLDF JumpShips rendezvoused with the Phoenix and transferred to her a total of six Colossus-class Assault DropShips, Comstar’s intelligence arm, ROM, began to probe hard into the sudden disappearance, but the investigations only
fully loaded with ‘Mechs and personnel. The Phoenix carried with her the entire population of the SLDF-founded colony resulted in four of their agents disappearing or otherwise becoming exposed and eliminated, though Dreadnought never
on Waycross II, leaving no one behind. The word was put out that a natural disaster had occurred on Waycross II and that learned of these agents’ ties to Comstar. One of the agents was killed entering a restricted area, while the other three
the planet had been abandoned. Warning beacons, set up at each jump point to indicate an uncontained biohazard, were simply disappeared, never to be heard from again. Comstar’s subsequent probing into the disappearance of the latter
convincing enough to deter any would-be raiders or colonists. agents resulted in the further compromise of three additional agents, who likewise disappeared, as well as a genuinely
innocent individual also vanishing after simply attempting to find out where his friend—one of the agents—had gone.
The JumpShips accompanying the Phoenix observed the vessel making a hyperspace jump from the Waycross system,
but when they arrived at the at the next rendezvous, the Phoenix was nowhere to be found. After waiting an appropriate These eliminations are suspected by Comstar to be, to-date, the most overt actions taken by what has become known
time for the ship to appear, the JumpShip crews were forced to conclude that the Phoenix had either taken a different in intelligence circles as Dreadnought’s own “ShadowCorps”. Seldom-mentioned and even lesser-known, this black ops
route or had suffered a misjump. It turned out to be the latter. The Phoenix never met with the rest of the SLDF “Exodus organization within Dreadnought’s private military is not officially recognized, and because of this it has no official
Fleet” to journey with General Kerensky into uncharted space. The WarShip was as lost to history as the system in which designation. It is only known by the colloquial nickname. Little is known about this organization by any intelligence agency,
the mighty vessel was built. including Comstar—much to the consternation of Comstar’s own ROM.
By 2791, the Waycross system had been claimed by the Draconis Combine as their territory expanded, yet none Eight years later, in 2954, the ancient and dilapidated T.H.S. Trinity, a Dreadnought-class Battleship recovered by
ventured into the system beyond the jump points, given the dire warnings from the beacons in the system. Just a decade Dreadnought Interstellar decades earlier, was covertly transported to the same star system, though the crew operating
later, the system was reclaimed by the Federated Suns for House Davion, but still no significant exploration of the system the Trinity were completely unaware of the other ship in-system. The Trinity herself had feigned a misjump in a very
was ever conducted beyond scans from the jump points. Stubborn Davion politics resulted in another attempt to colonize public fashion to disappear from the public eye, becoming a public tragedy—while the ship instead traversed through
the world. The outcry from the scientific community with regards to the apparent biohazard was only assuaged by an uninhabited and rarely-traversed star systems to make her way slowly and quietly to the Waycross system. There, the
agreement that the new colony would be set up on the opposite side of the world, far away from the abandoned city vessel resumed her role of orbital defense platform, this time for the world of Waycross II.
where an extremely lethal biological agent supposedly remained dormant.
In 2963, the restoration of the Cameron MechWerks facility under the surface of Waycross II was completed and the
The Screaming Eagles Mercenaries’ Storm Eagle Regiment was deployed to Waycross in 2801 to defend House Davion’s restoration of CrossWays Station began. Construction of a barebones orbital dry dock facility was started to mask the
claim to the system, as well as to provide support for the new colonization attempt. This new colony was located far away resources needed to complete the restoration of Crossways Station. This dry dock facility was designated Theris-One, in
from the supposed biological horrors lying in wait in the abandoned city where the previous civilization had lived. None honor of the man who had kept the DiscoveryCorps alive centuries prior, when it was in its greatest hour of need. By this
of the mercenaries or the new colonists managed to learn of the vast underground manufacturing facilities or the marvel time, the colony on the surface of Waycross II, which was kept to essential personnel only for the sake of security, had
that was the space station in the system’s asteroid field. The occupiers treated the world like the unpleasant, unimportant become self-sufficient. While message traffic was still being carried out through JumpShip courier, Dreadnought’s own
ice ball they believed it to be. Their opinions were tainted further by the losses of those among them whose lives were EngineerCorps began to unravel the secrets of operating the HPG station under the surface of Waycross II. Unfortunately
claimed by the harsh, unforgiving conditions of the world. To make matters worse, the world had entered an extended for the engineers in this era, the secrets of the operation of the HPG remained unknown until many decades later.
state of planetwide blizzards of terrifying severity. It was in fact these very storms that prevented further investigation
into the actual state of the abandoned city on the world. The abandoned structures were built to stand the test of time, Both the restoration of CrossWays Station and construction of Theris-One were completed in 2995. This new orbital
but the city also happened to be near the center of the most concentrated areas of the decades-long blizzards, making dry dock, while basic in comparison to the similar unit in orbit over Acala III, served as the home base for the Trinity upon
exploration too dangerous to attempt. completion. The Phoenix, meanwhile, remained hidden away at CrossWays Station and over the following year the vessel
underwent what little was needed to restore her to fully operational status. A stockpile of thermonuclear weapons was
Conflicts with the Draconis Combine reduced the Storm Eagles to roughly a third of their initial strength before they discovered in cold storage in CrossWays Station during the restoration process, hidden deep within the asteroid. The
were redeployed to the world of Robinson. From 2821-2831, the 21st Crucis Lancers were deployed to take the Storm section in which the weapons were discovered was sealed off, ostensibly due to concerns about the structure’s stability.
Eagles’ place. After an uncomfortable decade of occupation and considerable losses suffered due to numerous military The existence of the weapons was hidden from any official record. In all, there were seven thermonuclear weapons rated
In 3034, the completion of the new Theris IronWorks facility was carried out quickly enough that the first machines The D.B.C. Phoenix deployed with Task Force Bulldog later that year. The defensive capabilities of Theris were further
produced by it were already being transported by the DropShip-load shortly before Comstar traced the shipments of the reduced as a large portion of the DefenseCorps Theris Regiment’s vehicle assets was reassigned. These vehicle battalions
new machines coming from Waycross. To Comstar, it appeared that the Theris IronWorks had been the facility of the Theris Regiment were deployed as reinforcements for Task Force Serpent. The resultant reduction of forces on
manufacturing these new machines all along. As no one in their right mind would knowingly construct a military Theris necessitated the return of the D.B.C. Trinity to bolster the world’s defenses.
production facility directly above another facility that is designed to produce the same machinery, the plan —although
expensive—proved successful, and investigations into the source of the new machines ended. Federated Commonwealth Civil War
A few years later, with the War of 3039 looming, BattleMech production on Waycross II, the planet by then known In October, 3064, a team of operatives of unknown origin was killed while attempting to gain control of the D.B.C.
colloquially as “Theris”, became increasingly important for the newly-formed Federated Commonwealth’s military. Trinity. Some suspected that the attempted theft of the ship may have instead been an attempt to destroy it. Damage
was done to the Trinity’s sub-light drive system during the attack, stranding the vessel in dry dock for an estimated four
With the Waycross system back on the map and the world’s new name of Theris becoming official, the security and months. Just over three months later, in January 3065, Archon-Princess Katrina Steiner-Davion made a “request” for the
secrecy of the Cameron MechWerks became paramount, lest the world come under attack by a hostile Great House. The facilities on Theris to produce machines specifically for her side of the FedCom Civil War. The actual message sent
facility itself was reduced to largely automated function (one of the strengths of the factory), and output was reduced effectively boiled down to “obey or die”. It is believed to this day that these two events were related.
overall as a result. All personnel with access to, or knowledge of, the Cameron MechWerks facility were monitored even
more closely than before. The Theris IronWorks facility received upgrades to augment production, and the surface facility The DefenseCorps Theris Regiment stood down and complied with the Archon-Princess’ demands, as at this time the
continued producing machines for Dreadnought Interstellar Industries, with its output being augmented by the Trinity was nearly repaired but still disabled, and these demands were backed by the arrival of a pair of Fox-class Corvettes
underground factory. accompanying an Avalon-class Cruiser. While the Avalon departed to another system shortly thereafter, the Corvettes
remained. These ships settled into orbit to monitor the repair progress of the Trinity, which had been claimed by forces
With Waycross now public knowledge, Dreadnought made the public move to increase the workforce on Theris and serving the Archon, and maintained a military presence to discourage any uprisings on the planet’s surface.
form a local defense force. As nearly a quarter of the machines that had been aboard the Phoenix when she was
discovered had been shipped to Theris and locked away shortly after the vessel’s arrival in the system, the “SLDF Cache” The DefenseCorps were disarmed and placed under relatively light armed guard, knowing full well that any action taken
was claimed to have been found filled with Lostech equipment and machines. These machines quickly became the by them could result in the destruction of thousands if not tens of thousands of lives on the surface of Theris. With
foundation upon which the Dreadnought DefenseCorps Theris Battalion was based, allowing Dreadnought to quickly form Katrina’s followers more interested in the new machines being produced by Theris’ twin facilities, the DefenseCorps’ older
a defensive unit based on the world to further deter would-be raiders. The “SLDF Cache” also became the home base for machines were simply locked away and given low priority to transport off-world. Meanwhile, all available transport
the Dreadnought DefenseCorps Theris Battalion. Even the members of the newly founded unit were unaware of the true capability was focused on the factory-fresh machinery, intent on getting the new machines to the front lines to aid in
nature of the facility that they were using as a home at this point. maintaining Katrina’s hold on the throne.
In late 3042, the D.B.C. Trinity’s continued existence and relative restoration was revealed when the ship was sent from The people of Theris were forced to endure just over three months under Katrina’s rule. In June of 3065, an operation
the Waycross system to defend Acala III, which had been on the receiving end of numerous attacks believed to be funded was carried out that regained control of the Trinity. Personnel who had been in hiding aboard the Trinity since the vessel’s
by House Liao’s Capellan Confederation. After this event, the gradual process of assembling a proper crew for the D.B.C. capture, nearly starving and outnumbered, managed to use the environmental control system to subdue Katrina’s
Phoenix began. loyalists aboard the Trinity. This operation was timed to coincide with a shift-change aboard both Fox Corvettes. During
the narrow fifteen-minute window, the Trinity changed from FedCom control to Dreadnought control.
Comstar did attempt to intercept and destroy the Trinity en route to the Acala system. However, Dreadnought
managed to avoid contact altogether thanks to steps taken to counter a suspected internal security breach, even though Just as the crews of the Fox Corvettes began to suspect that something was amiss, the Trinity took aim at both vessels
they were unaware that Comstar was the source of the security breach and that Comstar had plans of their own. and issued the ultimatum for all Federated Commonwealth personnel on the surface to stand down and for the Fox
Corvettes to withdraw from the system.
Clan Invasion
Data recorders recovered from one of the Foxes indicate that one of the FedCom gunners opened fire on the Trinity,
In 3049, the Clan Invasion hit the Inner Sphere. The demand for new machines skyrocketed and Dreadnought was hard- possibly without orders. The damage sustained by the Trinity was minor. The return fire, however, was more than enough
pressed to keep pace. By late 3050, the difficult decision to bring the Cameron MechWerks facility fully online was made, to cripple the Foxes in an instant. Rescue efforts were attempted, though the events surrounding this tragedy resulted in
despite the inevitability that it would result in word getting out of the facility’s existence. The production of machines Dreadnought’s ability to scramble search and rescue being severely hamstrung. In the end, only a handful of survivors
By mid-3066, life on the world of Theris had returned to normal. The D.B.C. Phoenix and the Dreadnought BattleCorps The radioactive fallout from the detonation of the thermonuclear weapons in such close proximity to one another
1st Regimental Combat Team had returned home after Operation BULLDOG’s success and the subsequent capture of assured that nothing further could be salvaged from the Cameron MechWerks, Theris IronWorks, or any other facility on
assets from the former Clan Smoke Jaguar world of Pantheress VI. The salvaged technology and manufacturing equipment the surface of the planet, as all the facilities of the colony had been tightly clustered together.
from Pantheress began the year-long process of being incorporated into the Cameron MechWerks facility as well as
facilities on Acala III. Political Affiliation History
Orbital Heavy Industries, through their extremely close partnership with Dreadnought Interstellar Industries, began to - 2750 – Federated Suns
develop Clan-tech ExtraLight Fusion Engines for production in 3067. These new engines were initially used to upgrade - 2791 – Draconis Combine
several older machines employed by the BattleCorps, many of which had been damaged over the course of Operation - 2801 – Federated Suns
BULLDOG. With the new technology quickly proving itself reliable, attention turned toward incorporating it into new - 2862 – Abandoned/Uninhabited
production model ‘Mechs and combat vehicles. Many of these new machines were reworked versions of existing - 2946 – Dreadnought Interstellar Industries
machines, allowing for quicker development, easier introduction to production and significant reduction in tooling costs. - 3034 – Dreadnought Interstellar Industries/Federated Commonwealth
- 3067 – Dreadnought Interstellar Industries/Federated Suns
Word of Blake Jihad - 3075 – Abandoned/Uninhabited
- 3085 – Abandoned/Uninhabited (Present)
Combat preparedness exercises spiked sharply when news reached Theris of the Word of Blake’s Jihad in 3068. With
the Phoenix in orbit over Acala III, the Trinity’s crew prepared to defend Theris against a full-scale attack. The Theris Planetary Locations
Regiment’s depleted ranks were reinforced back to full strength over the following two years.
- Cameron City (Capital City) (Destroyed)
A massive evacuation on Theris began in mid-3074 when the Dreadnought IntelCorps reported that the Word of Blake - Theris-One Orbital Dry Dock (Destroyed)
were increasing their military presence in the nearby Schedar and Caselton star systems, just a single jump away. The - Waycross Alpha (Federated Suns Colony Site) (Destroyed)
stripping of Theris’ war-materiel production capabilities commenced much as it had on Pantheress VI a decade prior.
Additionally, large portions of the planet’s ancient underground HyperPulse Generator station were dismantled and Industrial Centers
quietly sent to Acala III.
- Cameron MechWerks (Destroyed)
The Word of Blake attacked the Waycross system in May of 3075. The Trinity was destroyed with all hands in orbit over - Theris IronWorks (Destroyed)
Theris, fighting until her last moment and taking one of the three attacking Blakist WarShips with her.
Notable Local Fauna
One Dreadnought Interstellar JumpShip, which had been anchored at the nadir jump point, opposite that of the zenith
jump point used by the incoming Word of Blake vessels, managed to escape to seek help. The other two JumpShips that - Crystal Fox
had been anchored at the zenith jump point when the Word of Blake arrived were not so fortunate. Both of these - Frost Wolf
JumpShips, which were laden with DropShips carrying civilian evacuees, were destroyed with all hands. - Rocket Hare
After four weeks of bloody fighting on the surface of the frozen world, seven fifty-megaton thermonuclear weapons
detonated simultaneously in the Waycross system.
Five of the explosions originated from the vicinity of the Cameron MechWerks facility, all but vaporizing the factory.
The massive compound explosion also killed all the remaining civilian population and DefenseCorps personnel on the
planet. The blasts wiped out all the Word of Blake forces on the ground and denied them access to the priceless facilities,
Geophysical
System Position: 4th
Jump Point Distance: 9.13 Days
Moons: 3 (Aspero, Atrox & Shikaris)
Surface Gravity: 1.03
Atmospheric Pressure: 0.9 BAR (Breathable)
Equatorial Temperature: 41° Celsius (Temperate)
Surface Water: 62%
Highest Native Life: Mammals and Reptiles
Founding: 2366
Primary Landmasses/Continents: 8
Secondary Landmasses/Islands: 1,500 (Approximate)
Infrastructure
Ruler: Julia Hawthorne
Capital City: Vyrie City
Population: 2,176,000,000
Socio-Industrial Levels: B-C-C-C-B
HPG (Representative): A (Comstar)
Ashkum IV Overview
Ashkum IV is a rather hot, Terra-like planet that was once home to a thriving civilization thanks to extremely successful germanium mining in the southern regions. The northern continents of Ashkum IV are littered wi th
slowly decaying cities that were once among the most awe-inspiring sights in the Inner Sphere. Once compared to Abu Dhabi of the early-to-mid 21st Century, Ashkum IV has been home to a large population living in near-
poverty ever since the supplies of germanium were mined into exhaustion. This situation has worsened severely in the aftermath of Operation LANCASTER in 3077.
The SLDF base, a Castle Brian not far from the planetary
capital city of Vyrie, completed construction in 2621. A mere
four years later, the largest deposit of germanium on Ashkum
IV was discovered. This was exceptionally timely, as virtually
all other known germanium deposits on the planet had begun
to dry up. The world had been bracing for an economic
downturn, but it instead experienced an economic boom.
The already impressive cities grew and became even more
extravagant over the following decade, and the planetary
population swelled to more than three billion.
Little of interest occurred on Ashkum IV during the Succession Wars, aside from a gradual deterioration of the It was later discovered by the Comstar personnel stationed on Ashkum IV in 3077 that both the rioting and the attack
economically challenged world. While the extravagant cities have stood the test of time, having been designed to last in on Dreadnought’s personnel had been the result of manipulations made by Blakist Manei Domini infiltrators who had
the face of significant storms for centuries, the cities themselves only housed a fraction of the populations that they once slipped into the general population post-LANCASTER. This handful of survivors from the 55th Shadow Division had worked
did. It would be easy to believe that the poverty-stricken people were extremely rich, given the average accommodations to undermine any chance of cooperation through careful manipulation of government officials, news outlets, and other
of the citizenry. key individuals. Despite this revelation being publicly revealed by Comstar, the hostility toward Dreadnought remains
very real for many on Ashkum IV, though it has lessened in recent years.
With little to offer in terms of wealth or strategic value, the Ashkum system unceremoniously changed flags to that of
the Federated Suns in the year 3025. Under Davion rule, the economy began to recover very gradually with the addition As of 3085, Ashkum IV has yet to recover from the damage done during the Word of Blake occupation and subsequent
of new industries such as Ashkum Armaments, an upstart supplier of Short Range Missile systems and ammunition, but events associated with Operation LANCASTER.
the planet would forever remain a mere shadow of what it once was.
Political Affiliation History
By the 3050s, the population barely tipped two billion.
- 2366 – Sarna Supremacy
Word of Blake Jihad - 2367 – Capellan Confederation
- 3025 – Federated Suns
Duke George Hasek launched an invasion of the Capellan Confederation under the name Operation SOVEREIGN JUSTICE - 3040 – Federated Commonwealth
in 3068. The purpose of this invasion was ostensibly to liberate the worlds of the St. Ives Compact. The Capellan - 3067 – Federated Suns
Confederation Armed Forces reacted with their own Operation THUNDERSTRIKE, which not only liberated the worlds - 3076 – Word of Blake Protectorate
seized by the Capellan March forces but also struck back at worlds under the banner of the Federated Suns. Ashkum IV - 3077 – Federated Suns
was one of the worlds attacked simultaneously, with the Capellans striking on the 18th of February 3069. Although the - 3085 – Federated Suns (Present)
world of Ashkum IV was spared the worst of it, as the Capellans had little reason to focus their attention on the planet,
the Planetary Militia suffered losses during the raid, further weakening the already frail defense force. Planetary Locations
The Word of Blake Protectorate’s 102nd Provisional Division occupied Ashkum IV under a theoretical banner of peace - Capri (Continent)
in 3076, promising economic and military assistance to the controlling planetary government. Faced with the choice of - Ashkum IV Primary Spaceport
accepting the Blakists’ assistance or potentially being ground under by the massive Blakist war machine, the government - Dover (City)
and most of the people of Ashkum IV sided with the Word of Blake. The people of Vyrie City knew nothing of the massive - Midmark Mountains
stockpile of both nuclear and thermonuclear weapons in their midst which were allowed to fall into the hands of the - Port Geoffrey (Coastal City)
Word of Blake as a result of siding with the Blakists and allowing them to take military control of the planet. - Port Vincent (Coastal City)
- Sutherland Forest
Information regarding the Blakist occupation of Ashkum IV was initially kept under wraps as the Word of Blake took - Suval River
control of the planet’s HyperPulse Generator, ensuring control over all outgoing interstellar communications, and - Vyrie City (Capital City)
simultaneously placed the world under a form of quarantine that restricted passage off-world. The occupation went
unnoticed for nearly half a year before a passing Dreadnought DiscoveryCorps JumpShip detected the presence of Blakist - Kirsala (Continent)
WarShips running in low-power mode in orbit around one of Ashkum IV’s moons. - Everglade City (City)
- Port Fredericks (Coastal City)
On New Year’s Day 3077, following nearly a year of occupation by the Word of Blake, the Dreadnought BattleCorps 1st - Fredricks’ Landing (First Colonization Site)
Regimental Combat Team, assisted by the mercenary forces of the Blackwood Templars and Ronin Free Companies, - Temptress Pass Canyon
launched Operation LANCASTER to remove the Word of Blake presence from the Ashkum system. While successful in the
mission objectives, LANCASTER resulted in the complete destruction of the orbital satellite network and significant - North Verona (Continent)
damage to the world’s greatest city, neither of which could be easily repaired by the locals. Immediately following the - The Great Landau Rainforest
completion of Operation LANCASTER, the tactical satellite network that had been deployed by the BattleCorps (deployed
during initial planetfall early in the operation) was repurposed to temporarily operate as Ashkum IV’s planetary - South Verona (Continent)
telecommunications network. - Galahad (City)
- The Great Chasms (Depleted Germanium Mines)
After the completion of Operation LANCASTER, Dreadnought Interstellar Industries attempted to help with repairs to - The Great Expanse (Desert Territory)
the planet’s capital city and general infrastructure. Even as Comstar’s control over the Ashkum IV’s HyperPulse Generator
station was re-established, protests, riots, and an outright attack on the Dreadnought personnel caused Dreadnought to Industrial Centers
withdraw altogether from Ashkum IV.
- Ashkum Armaments Production Facility
With Dreadnought’s departure, so went the satellites that had been serving as the world’s telecommunications
systems, as well as the mobile industrial fusion powerplants that had been brought in to serve as sources of electricity Notable Local Fauna
(the fighting during LANCASTER had destroyed one of the most critical powerplants in the region). Ashkum IV’s planetary
economy collapsed overnight as the worldwide infrastructure was crippled due to the intercontinental communications - Kite Chameleon
blackout. This situation was made all the worse due to the lingering, unrepaired damage done to the capital city and - Rainbow Sparrow
surrounding region during LANCASTER. - Thunder Skunk
Geophysical
System Position: 6th
Jump Point Distance: 11.4 Days
Moons: 2 (Rea & Sura)
Surface Gravity: 0.93
Atmospheric Pressure: 0.88 BAR (Breathable)
Equatorial Temperature: 23° Celsius (Cool-Temperate)
Surface Water: 83%
Highest Native Life: Mammals
Founding: 3003
Primary Landmasses/Continents: 6
Secondary Landmasses/Islands: 4,000 (Approximate)
Infrastructure
Ruler: Unknown (Clan Snow Raven, as of 3064)
Capital City: Udaan
Population: Unknown
Socio-Industrial Levels: B-C-C-C-C (As of 3064)
HPG (Representative): Unknown
Pantheress VI Overview
Pantheress VI is a heavily cratered but habitable world that was located after the colonization of the Clan Pentagon worlds. This planet later became a center for weapons manufacturing and advanced weapons
development—away from prying eyes—under the banner of Clan Smoke Jaguar. With the fall of Clan Smoke Jaguar and the subsequent takeover of the system by the Dreadnought BattleCorps, the world has been largely
stripped of its more advanced technology and manufacturing capabilities. Upon Dreadnought’s departure with a small percentage of the world’s population in 3064, Clan Snow Raven took possession of the Pantheress star
system. As of 3085, no further data is available on the status of this world.
Located just shy of ten light years from the Clan Smoke
Jaguar homeworld of Huntress, the Pantheress star system
lies roughly in the middle of the space between the Huntress
and Strana Mechty star systems. While the rest of the worlds
in the Pantheress star system are nothing short of hostile to
any kind of human life (with either hostile atmospheres or
lacking atmosphere altogether), Pantheress VI is a nearly
Terra-like planet with a slightly low atmospheric pressure.
Almost overnight, Dreadnought absorbed into their own ranks nearly all the Jaguar scientists and technicians who had - P4 Sigma Manufacturing Facility
been stationed on Pantheress VI, along with numerous other Freeborn support personnel. Meanwhile, all the warriors of - P7 Sigma Facility
the Obsidian Jaguars were taken as bondsmen. The four-year-long process of stripping Pantheress VI of military
equipment manufacturing facilities began just weeks after the Dreadnought BattleCorps gained possession of the star Notable Local Fauna
system. During this time, the BattleCorps opened trade relations with Clan Diamond Shark and quickly grew strong ties
with the Diamond Sharks as respected trading partners. - Bombardier Wasp
- Demon Squirrel (Pictured)
In March of 3061, representatives of Clan Snow Raven arrived and challenged the BattleCorps to a Trial of Possession - Shadow Panther
for the system. With their official claim on the eighth planet in the system as an existing foothold, the Snow Ravens looked
to expand their claim to the entire system following the demise of Clan Smoke Jaguar. Given that Clan Snow Raven could
easily overwhelm and crush the BattleCorps if they did not restrain themselves according to Clan customs, the BattleCorps
had little choice but to accept the challenge and conduct themselves according to Clan rules of engagement to have any
hope of retaining control of Pantheress VI. The BattleCorps’ only other option was to flee, which would label them as
cowards and lose most if not all credibility with any of the Clans, as well as the warriors that had just been absorbed into
their ranks. Coincidentally, the commanders of both the BattleCorps and the Snow Raven force shared a common passion
and highly respected skill in the same form of competition: chess. To prevent loss of life, Colonel Lawrence selected this
as the form of the contest, as was her right as defender. In a narrow victory, Colonel Ann Lawrence defeated Star Colonel
Ann Lankenau two-to-one in what became known as the “Match of the Colonels Ann”.
The terms of this Trial of Possession were highly unorthodox, and though the terms were within the letter of Clan law,
no historical precedent had existed. With Colonel Lawrence emerging victorious, not only did the Dreadnought
BattleCorps remain in possession of the Pantheress system, which is all that a Trial of Possession such as this would
normally entail, but a set of additional terms was agreed to by both parties.
Clan Snow Raven was officially named as possessor of the Pantheress system, though the BattleCorps remained the
physical occupiers until they departed to return to the Inner Sphere. Upon the BattleCorps’ departure, the Snow Ravens
would be allowed to take physical possession of the star system altogether. This included the orbital dry dock and all
facilities and equipment the BattleCorps did not take with them, with a guarantee that Dreadnought would not damage
or sabotage anything they left behind. As Clan Snow Raven was already officially designated the future owners of the star
system, the agreement between the BattleCorps and the Snow Ravens also meant that the Snow Ravens were responsible
for defending their future interests in any Trial of Possession declared by another Clan for the Pantheress system. This
freed the BattleCorps to continue their efforts of stripping Pantheress VI of much of its war materiel manufacturing
equipment. However, the BattleCorps now had to be far more careful so as not to cause unnecessary damage to the
structures housing said manufacturing equipment or anything that was not to be taken with them when they departed.
Both parties held to all the terms that had been agreed to, and a surprisingly amicable relationship between the two
formed over time. In 3064, with representatives of Clan Snow Raven present to monitor the BattleCorps’ departure, the
BattleCorps began the long journey back to the Inner Sphere. The cargo holds of Dreadnought’s ships were packed full of
advanced technologies and manufacturing equipment, as well as massive quantities of supplies and a few thousand more
people aboard than when they had departed the Inner Sphere some five years prior.
As of 3085, no further information on the status of the Pantheress system is available. Following the Wars of Reaving,
Clan Snow Raven departed Clan Space and moved to the Inner Sphere, where they merged with the Outworlds Alliance
to form the Raven Alliance in 3083. The Raven Alliance maintains active trade relations with Dreadnought today.
OPERATION LANCASTER
December 3076 – February 3077
45 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
OPERATION LANCASTER – ASSAULT ON ASHKUM IV
Assault on Ashkum IV: Planning and Preparation One more possible goal was determined. The Word of Blake may have been setting out to finish what they started over
a year prior when they assaulted the Dreadnought world of Theris, in the Waycross system. The assault had ended in the
On the 10th of January, 3077, the forces of multiple Great Houses, Clan Wolf-in-Exile, Clan Nova Cat and Comstar total nuclear annihilation of the entire system’s population, and this fact was far from forgotten. The presence of the
launched a massive cooperative effort to destroy the Word of Blake. This cooperative effort would span virtually the Word of Blake in the Ashkum system meant that a hostile force was a mere two jumps from the Acala system, where the
entirety of the Inner Sphere and was known as Operation SCOUR. Just six months prior to the launch of SCOUR, it came Dreadnought homeworld of Acala III resides. A difficult decision was made. On September 12th, a plan was put into action
to the attention of the Dreadnought IntelCorps that a buildup of Blakist forces had been covertly taking place on the world to gather the necessary military strength to destroy the built-up Word of Blake’s holdings on Ashkum IV. Continued
of Ashkum IV for several months. monitoring of the 102nd Division’s status was achieved through passive scans by Dreadnought Interstellar transport
JumpShips passing through the system every couple of weeks.
Ashkum IV was once a shining jewel of humanity where many rich and powerful people lived in lavish, awe-inspiring
cities. The heavily industrialized world experienced a sharp decline in population during the early Succession Wars, when To prevent the Blakist force built up in the Ashkum system from accomplishing whatever their mission may have been,
the planet’s extremely rich germanium deposits ran dry. The rich and wealthy left the world almost overnight, and the a planetary assault was planned. This assault involved the combined forces of the Dreadnought BattleCorps’ 1st
planetary economy effectively collapsed. While far from the thriving world it was once known for being, Ashkum IV still Regimental Combat Team and two mercenary units: the Blackwood Templars and the Ronin Free Companies. This assault
had a moderate population of just over two billion. Despite centuries of neglect, the great cities of Ashkum IV still stood is considered to have been one of the greatest military deployments in the Inner Sphere that did not involve any of the
tall in the 31st Century, though the population was but a shadow of what it once was. The Word of Blake’s interest in Great Houses, Comstar, or the Clans. This assault was known as Operation LANCASTER.
Ashkum IV was unclear.
In late October, a DropShip travelling to Ashkum IV from a world in Lyran space dropped off its passengers just as any
On August 19th, 3076, acting on the intel gathered almost a month prior, a scouting mission was sent to the Ashkum other routine drop. Among these passengers were a specialist team of infiltration and demolition experts from the
system via the JumpShips D.I.I.S. Razorback and D.I.I.S. Stardancer. The Stardancer entered
the system via the zenith jump point with her IFF running a false identification so that she
could not be appropriately identified, giving the appearance of an independent vessel.
Meanwhile, the Razorback remained in the Goshen system, one jump away, awaiting the
return of the Stardancer. The mission of these ships was simple: carry out several
concentrated, but mostly passive scans of Ashkum IV, escape the system without being
identified, and relay the information back to Dreadnought Command.
Being a DiscoveryCorps variant of the Mammoth II-class JumpShip, the Stardancer was
equipped with a powerful array of telescopes and astonishingly powerful sensor systems and
other remarkable technologies, some of which were considered by many to be Lostech.
These systems were designed for exploration and recovery of Star League technology, and
made the vessel perfectly suited for this reconnaissance mission. What the Stardancer’s
scans showed was disconcerting to say the least. During the time spent in-system running
scans, military-grade fusion engine signatures numbering in the hundreds were identified,
suggesting a full-fledged reinforced Division of Blakist ‘Mechs, vehicles and aerospace
fighters were present. This Division was eventually identified by the Dreadnought IntelCorps
as the Word of Blake Protectorate’s 102nd Provisional Division. Compounding the threat
severely, two Lola-III type Destroyers were detected running in low-power mode, apparently
attempting to remain undetected in orbit of one of the planet’s moons. If not for the
Stardancer’s specific capabilities, they likely would have remained unnoticed.
The Stardancer remained on station after completing her recharge cycle, keeping an active
jump plot to rendezvous with the Razorback. Once an incoming vessel was detected entering
the system at the zenith jump point near the Stardancer, she jumped away. At the very last
second before initiating the jump, however, active scans determined the incoming vessel to
be yet another Lola III, bringing the total to three of the same class of ship in the system. No
doubt another Word of Blake vessel.
The Stardancer’s report was fast-tracked back to Dreadnought Command in the Acala
system via the awaiting Invader-class JumpShip, the D.I.I.S. Razorback.
This buildup of Blakist forces was by all reports the largest Blakist force operating outside
of the Word of Blake Protectorate at that time. How the buildup had been achieved without
any notice until that point was never determined, but the likely goals of the buildup were
obvious. It was clear that the Word of Blake were aware that Operation SCOUR was coming
and had begun putting together military assets powerful enough to split the attention of the
forces of Operation SCOUR, or, at the very least, assault their supply lines and civilian
populace. This Blakist force could possibly even work toward assaulting House Davion
directly while much of the Armed Forces of the Federated Suns’ assets were tied up
elsewhere.
Two days later, shortly after detecting the three Blakist Lola III-class Destroyers breaking
orbit and moving to intercept her, the Phoenix shed her cargo of DropShips: the two Fortress-
class Himeji and Matsumoto, the Overlord-class Gekokujo and Cathedral, the Miraborg-class
Archangel and the Excalibur-class Malta. These DropShips carried all the collective forces of
the Blackwood Templars and Ronin Free Companies mercenary units intended for their part
in Phase Four of Operation LANCASTER. Meanwhile, the remaining two Blackwood Templars
DropShips were set to accompany the rest of the Dreadnought BattleCorps during Phase
Three.
The DropShips separated from the Phoenix without utilizing anything but the lightest of
maneuvering jets, doing everything possible to avoid giving off any kind of a thermal
indication of their presence, and allowing momentum to slowly carry them toward Ashkum
IV. Simultaneously, the D.B.C. Phoenix began to ramp up her engines somewhat, but not more
than roughly half her maximum thrust, and maintaining the appearance of a damaged drive
system. The alteration in the drive output masked the effect of the sudden reduction in
weight on the ship’s thrust-to-acceleration readings taken by the Word of Blake. As she
accelerated, the Phoenix also changed course slightly, hoping to give the impression of an
inexperienced commander as she moved to engage the Lola IIIs.
Though it was savage for those aboard the DropShips, the harsh late deceleration burn
was worth it for the element of surprise, as the sudden thermal signatures would
seemingly appear out of nowhere–and that was only if there were any satellites still in
operation by the Word of Blake to see them (satellites that would have had to be missed
by the BattleCorps’ fighters during their escort of the BattleCorps DropShips to the planet
surface, and then missed again during the second pass that they made while they were
on their return trip to the Phoenix).
As it was, the arrival of the mercenaries was a complete surprise to the remaining Word
of Blake forces in Vyrie City, the center of which was exactly where the mercenaries
landed. After the Blackwood Templars’ aerospace fighters had flown over the city, taking
out anti-air batteries and military communications antennas, the Templars’ fighters
seemingly vanished just as quickly as they had first appeared.
The Templars led the way during landing operations. Two of the Templars’ DropShips
dropped down to within one hundred meters of the ground over the Vyrie City Central
Park even as they finished decelerating from orbital reentry, dropping ‘Mechs off as they
went. The Templars, who were geared more toward rapid hit-and-fade combat, charged
into the city, blazing through any and all Word of Blake forces that remained. The
defenders that met them were all but a skeleton defense with armored defensive
positions literally facing the wrong direction to defend against the attack starting from
the center of the city.
During the sudden attack by the mercenaries in the city, the Dreadnought BattleCorps
found themselves engaged with the mainstay of the Word of Blake’s 102nd Division in a
full-on assault. This assault quickly turned into a running battle after a failed attempt at a
surprise flanking maneuver by a Manei Domini Level II. The six Celestial OmniMechs,
acting as headhunters, had used a wedge of thirty-six ‘Mechs to punch a hole into the
Dreadnought line and sweep around toward the center-rear flank. The flanking force had
clearly been intent on killing Colonel Ann Lawrence, the commander of the Dreadnought
BattleCorps. It was unclear at that time how they had known exactly where the Colonel
was, given that most of the BattleCorps’ ‘Mech companies each had a ‘Mech nearly identical to hers at its head. Though the battle had only been raging for just over thirty minutes, the 102nd began an increasingly organized
withdrawal toward the city, their coordination clearly improving the further they pulled away from the almost-casually-
Even as the headhunters came within sight of their objective, they discovered firsthand not only just how surprisingly pursuing Dreadnought BattleCorps. The BattleCorps had suffered only mild-to-moderate damage and minimal actual
powerful the Dreadnought BattleCorps’ new war machines were, but also just how coordinated the unit was and, as a casualties. Much more significant damage had been done to the 102nd Provisional Division resulting from the failed push.
result, how quickly the BattleCorps was able to adapt and maneuver. The BattleCorps closed in around the Manei Domini This was only made worse as the Blakists’ own battle computers were constantly misidentifying and underestimating the
‘Mechs and crushed them before they could do any substantial damage to Colonel Lawrence’s Neugen. The attempted machines being fielded by the BattleCorps. Most of the BattleCorps’ machines were being identified as far older and less
direct attack ended with the left fist of Captain Melissa Tor’s Atlas caving in the head section of an enemy Archangel dangerous variants, resulting in numerous unpleasant surprises for the Blakists.
OmniMech. In the minutes that followed, the lack of coordination before the 102nd Division began to fall back in the
direction of the city made clear what had just happened: Captain Tor had just killed the enemy commander. By the time that the Word of Blake had just ten kilometers of forest to navigate before reaching the other side, contact
had been broken from the BattleCorps, but the Word of Blake held no illusions that they were not being pursued. The
After several minutes of confusion, the new provisional commander of the 102nd Division had clearly received word BattleCorps’ 1st, 2nd, and 4th Battalions followed the withdrawing Blakists, while the 5th Irregular Battalion remained on
about the attack happening in the city, despite the nigh-impenetrable curtain of long-range communications-jamming station at the spaceport to provide security. Despite the exceptionally fast pace of the 102nd Division’s withdrawal along
because of their proximity to the BattleCorps and their overwhelming level of electronic countermeasures. It was believed the paths through the forest that they had created for themselves earlier, it was more than six hours after engagement
that someone in the 102nd had spotted the DropShips coming down in broad daylight (most likely a VTOL craft, given the began before the Blakists finally escaped the Sutherland Forest and reached the Suval River.
dense forest that the ground troops were moving through and fighting in) and had finally gotten through the BattleCorps’
jamming to inform the individual who had taken command. Night had fallen by that time, and it had begun to rain. A storm was brewing.
Battered and bruised as they were, the Word of Blake did attempt to make the Ronin pay
for it, however, with their broadly similar numbers and the ability to better concentrate their
numbers. The 102nd attempted to punch through between the northern-most Fortress
DropShip, the Matsumoto, and the Overlord-class Gekokujo, where the spacing between the
DropShips was greatest, and where a weakness in the defensive line had seemed to form.
The 102nd suddenly seemed to gather their strength and dive forward toward that point,
centered on a main highway into the city, just a little over two kilometers north of the
Gekokujo, more than a kilometer-and-a-half south of the Matsumoto, in what appeared to
be a blind spot for both DropShips.
Only once it was too late did it become evident that it was a trap. The remaining members
of the 102nd Division had no idea that there was an entire additional mercenary unit standing
by in reserve–right where they needed to go. The spacing between the DropShips had been
intentional, the placement of the vehicles precise. When the Word of Blake funneled straight
into that point in the defensive line, the closest Ronin Gauss Rommels pulled back, the drivers
giving the impression that they were retreating out of panic as the tanks took heavy fire,
before swerving in reverse behind thick-walled buildings and disappearing from view. In the
next two heartbeats, the remaining members of the Word of Blake’s 102nd Division knew
only fear and surprise, as all of the mercenary aerospace fighters began strafing that specific
area in perfect coordination, laying down a heavy barrage of fire that consumed many of the
remaining Blakist machines. The barrage from above ended as quickly as it began, the fighters
having to fly off to turn around and come back for the next strafing run. As the lights of the
city began to show through the clearing smoke where the path into the city should be, instead
of an open highway, the path was filled with nothing but the silhouettes of dozens of charging
‘Mechs and combat vehicles pouring straight out of the city onto the massive highway that
the Blakists had intended to use to get in.
The Blackwood Templars tore through whatever the Ronin Free Companies did not smash
to pieces. In a matter of minutes, the battle for the city was effectively over.
Even as Colonel Lawrence began to comprehend the implications of the discovery and
ponder the likely uses that the Blakists had in mind for these weapons of mass destruction,
communications jamming began to scramble all long-range communications between the
Lancaster Coalition forces on the planet surface and the Dreadnought WarShip and
JumpShips in-system. The jamming similarly hindered local communications between the
BattleCorps and the two mercenary units, as well as the uplinks to the satellites in orbit.
Given the communications difficulties, Colonel Lawrence immediately started using her
aerospace fighters to establish contact with Colonel Blackwood and Free Colonel Meridius to
give instructions via messenger.
Upon finishing off the last of the hostile stragglers, the mercenaries were tasked with
immediately separating their primary forces into three groups. The first group was the least
damaged of their heavier machines, and they were to proceed immediately to the city’s
capital, where the planet’s HPG was located, to begin securing a defensive line around the
area and ensuring the Lancaster Coalition’s possession of the nukes. The second group was
the more severely damaged machines, and they were to proceed immediately back to their
DropShips for rearm and refit. The third group consisted of the light, fast-movers, primarily
VTOLs and ground combat vehicles that were minimally damaged. This third group was
tasked with rotating patrols with similar vehicles that were being transferred from the
BattleCorps to the city as quickly as possible.
With the bridges over the Suval River destroyed, the Dreadnought BattleCorps 1st RCT
withdrew back to their DropShips and began their own processes of repair and rearmament.
Even as these processes were being carried out, Colonel Lawrence had to make the
distasteful order to rig the D.B.C. Basilisk, the crippled Fortress-class DropShip, to explode if
it were successfully captured by the Word of Blake. After offloading all the Basilisk’s supplies,
the DropShip was then abandoned at the spaceport, while the other Dreadnought DropShips
transported the BattleCorps ground forces to the edge of Vyrie City. Once landed, the
BattleCorps’ remaining two Colossus-class Assault DropShips, the D.B.C. Dragon and D.B.C Wyvern, remained on-station ship to lighten the Ryūjin’s load, leaving the Wildcards spread out and vulnerable on the ground. Lieutenant Windleaf,
at the city’s edge, continuing to repair and refit the BattleCorps, as did two of the unit’s four Overlord-class DropShips, unfortunately, was not among those who survived the landing. The flexing of the ship’s frame on impact had caused
the D.B.C. Temperance and D.B.C. Perseverance. Fortunately, the BattleCorps’ pair of Cargomaster-class DropShips—the buckling around the bridge, jamming the doors shut and damaging the fire suppression system in that area, leaving the
D.B.C. Mercury, and D.B.C. Osiris—had both survived planetfall with their many thousands of tons of needed spare parts entire bridge crew to perish in a fire.
intact. The D.B.C. Fafnir, the BattleCorps’ sole remaining operable Fortress-class DropShip, accompanied the D.B.C.
Indomitable Spirit and D.B.C. Shelby, the unit’s other Overlord-class DropShips, to join the Caladrius at the Ryūjin’s crash The Caladrius was quickly overwhelmed by the sheer number of wounded survivors from the crash, so the Shelby was
site to begin the operations to salvage the ill-fated vessel. Meanwhile, the remaining BattleCorps units in and around loaded with all the survivors that the Caladrius could not handle. The Shelby made a quick sub-orbital hop to Vyrie City,
Vyrie City assisted the Blackwood Templars and Ronin Free Companies in routing out any remaining Word of Blake where the remaining near-seven-hundred survivors from the Ryūjin were transferred off the ship. Some four hundred of
holdouts in the city as well as searching for the jamming devices preventing long-range communications. them were transported to various hospitals across the vast city, while the remaining three hundred were either allowed
time to rest or given the option to be put to work, depending on their conditions and needs. The Caladrius likewise
Though the work was already well under way by the ‘Mechs and Elementals of the 3rd “Wildcards” Battalion, which relocated to Vyrie City, landing in the large park near the city’s largest hospital, New Livingston Hospital, just a few
had regrouped at the crash site of the Ryūjin, it took an additional two full days to evacuate those that survived the kilometers to the southeast of the defensive perimeter surrounding the city’s capitol building and HPG station.
Ryūjin’s crash, and a further three to catalogue those who had not. The final tally of survivors was an impressive eight-
hundred-thirteen of the roughly one-thousand personnel that had been aboard the ship, although more than half of them An entire additional day was required to pry open the Ryūjin’s ruined hull just to begin the process of retrieving what
had injuries ranging from severe to critical. Virtually all the survivors credited the pilot, Lieutenant Windleaf, for his could be salvaged, and an additional two days to get most everything of value freed and offloaded. While the overall
impressive skill in bringing the ship down softly-enough that so many could survive the impact, though they did not conditions of the ‘Mechs were generally good, as all of them had escaped the DropShip prior to the crash-landing, a good
overlook the actions of the ‘Mechs and Elementals of the Wildcards Battalion making the move to jump from the stricken number of the Ryūjin’s vehicles were in far worse condition than had been first believed. None of the twelve support
A considerable amount of the ship’s supplies, including food, ammunition, and spare parts had been lost during the The Zechetinu-class Corvette was dispatched ahead of the rest of the Blakist fleet shortly after the Crusader’s arrival to
crash, much of it spread across the countryside. What could be salvaged was loaded aboard the Fafnir and Indomitable intercept the new JumpShip, presumably to destroy it. Four days before the Blakists would reach the Crusader, Colonel
Spirit, along with the salvaged vehicles of 8th Battalion, and ‘Mechs of the Wildcards Battalion. The Fafnir and Indomitable Lawrence gave the order for the Phoenix to engage the incoming vessels and defend the Crusader. The Dreadnought
Spirit then made sub-orbital hops back to join the rest of the BattleCorps around Vyrie City, landing near the north-east BattleCorps’ WarShip broke from orbit, heading toward the defenseless JumpShip and, as a result, straight into the maw
edge of the city, where repairs to the salvaged gear continued. These were the last movements made by any of the of the enemy. In response, the Zechetinu was recalled to regroup with the Sovetskii Soyuz-class Heavy Cruisers to prepare
DropShips, as the Fafnir and Indomitable Spirit barely made the trip safely through the worsening weather. After that, the for the impending engagement against the Texas-LFR-class Battleship. In addition, the bulk of the Blakists’ DropShips
increasingly severe winds of the building storm forced all the DropShips and AeroFighters to remain grounded. Despite quickly broke away from the WarShips escorting them, ensuring that they avoided the imminent conflict between the
the worsening weather, ‘Mechs, combat vehicles and battle-armor-equipped infantry continued to search the city for the powerful WarShips. The roundabout flight path gave the ground forces a desperately needed two more days to prepare.
source or sources of the communications jamming, even as the storm overhead became bad enough that communications
with the satellites would have been sketchy at best even without the jamming in play. Meanwhile, the Ronin Free Meanwhile, during the few remaining days before the Blakist DropShips were due to arrive, Colonel Tyr Blackwood,
Companies continued their work to further fortify the Lancaster Coalition’s defensive position in the city center. commander of the Blackwood Templars Mercenaries, rallied volunteers from the Ashkum IV Planetary Militia to the
Lancaster Coalition’s cause. With little to work with, the Templars’ technicians managed to overhaul several dilapidated
Heavy LRM Carriers with “locally sourced” Short Range Missile launchers from the stocking warehouses of the Ashkum
Defense of Ashkum IV: Part Two – The Skies Darken Armaments facility that had been disabled early on during the first wave of Operation LANCASTER. These refitted vehicles,
though very nearly the textbook definition of “Glass Cannons”, added a considerable punch to the militia’s Hetzers,
After the Dreadnought BattleCorps ground forces had drawn the Word of Blake’s defending troops out of the city and Goblins, Bulldogs, and Vedettes, Ballista Self-Propelled Artillery vehicles and Ferret Light Scout VTOLs, allowing the
into the carefully laid trap, the Phoenix had followed through with her part of the planned operation. Having used the assembled Ad Hoc Militia to reach an understrength battalion in size.
days adrift to repair some of the light damage done by the Lola IIIs, the Phoenix ceased ‘playing dead’ and powered up
her engines to begin a relatively gentle 1-G acceleration burn toward Ashkum IV. Shortly after beginning to move toward
the planet, communications were be cut off by blanket frequency jamming. With the intensity of the building electrical Defense of Ashkum IV: Part Four – Battle Among the Stars
storm, there was no way of establishing contact until the storm had cleared, even without the communications jamming.
The mighty Texas-LFR-class WarShip D.B.C. Phoenix was indeed an amazing vessel, with an astonishingly thick armored
Just hours after establishing geosynchronous orbit on January 19th, new sensor contacts of vessels completing an hide and devastating weaponry, but she was outnumbered three-to-one against ships that could inflict considerable
interstellar jump to enter the system at the nadir jump point were detected. As per standard procedure, the Lancaster harm. Worse, though her crew had restored full function to the few systems damaged in her battle with the Lola IIIs just
Coalition JumpShips immediately went to alert status, beginning jump preparations to return to the Goshen system if weeks prior, the Phoenix still had residual hull damage, most notably to her port-aft quarter where one of the Lola IIIs
needed. From there they would make an emergency jump to the Acala system if they encountered hostiles. had managed to inflict multiple direct hits. Even with the damage to the Phoenix’s armor, she still had considerably greater
armor protection that any one of her opponents did, but the difference in armor was not quite as significant as it might
Upon completing the interstellar jump into the Ashkum system, the new vessels were identified as Word of Blake ships. have otherwise been. The Sovetskii Soyuz-class Heavy Cruisers, identified as the W.O.B.S. Illuminated Path and W.O.B.S.
The new vessels included four Invader-class JumpShips, two Sovetskii Soyuz-class Heavy Cruisers and a Zechetinu-class Purity of Thought, were problematic. Even if they could not last long in a straight fight with the Phoenix, they could inflict
Corvette, as well as numerous DropShips and indications of considerable aerospace fighter support. While the Blakists’ considerable damage and could use their numbers to possibly flank her to get to her weakened port-aft armor. The nimble
four Invader-class JumpShips unfurled their sails and begin recharging their jump drives, their DropShips detached and Zechetinu-class Corvette, the W.O.B.S. Due Diligence, presented an additional problem because it could easily
moved toward the planet, as did the three WarShips that had accompanied them. outmaneuver the much slower Phoenix, becoming yet another threat to her damaged flank.
With an approximate travel time of nine days to the planet and just over seven days to the location of the Lancaster The only areas where the Phoenix could hold an advantage over her opponents was in her sheer level of armor
Coalition JumpShips, orders were given to the JumpShips to return to the staging ground in the Goshen system and protection and fighter support. The Phoenix carried more advanced fighter-craft than the regular Word of Blake fleet
recharge their jump drives there. All the Lancaster Coalition JumpShips successfully jumped away later that day. could boast. With fifteen fighters lost or knocked out of commission, the Phoenix still carried with her forty-five of the
exceptionally lethal Dreadnought Spec aerospace fighters. Meanwhile the two Overlord-A3A-class DropShips escorting
Unable to communicate with the ground forces below, the Phoenix was forced to remain in geosynchronous orbit over the Phoenix still carried with them their twelve additional aerospace fighters. The BattleCorps’ AeroFighters were novel
Vyrie City, anticipating a stalemate with the newly arrived Word of Blake vessels. to the Word of Blake, as the only prior engagement with these new craft had been earlier that month—against Blakist
forces that had been destroyed before being able to report anything of value. The BattleCorps’ pilots were also highly
experienced in battles involving WarShips, and even with the losses taken in the battle with the Lola IIIs earlier in the
Defense of Ashkum IV: Part Three – Flashpoint month, the BattleCorps AeroFighters roughly evenly matched the Blakist fleet’s AeroFighters in numbers.
By January 21st, the Lancaster Coalition was five days away from being fully rearmed and refitted. Their positions in However, the BattleCorps’ two Overlord-A3A-class DropShips, the D.B.C. Shepherd and D.B.C. Yosemite, needed to be
the city had been considerably fortified in the meantime. The Ronin Free Companies had stopped several attempts to remarkably careful to avoid being destroyed by the vast firepower of the nearby battling WarShips. As a result, the
gain access to the nuclear weapons stockpile by Blakist operatives still within the city and had refined their security to the Overlords were ordered to hold back, while the Phoenix engaged with her fighter screens alone for direct assistance.
point where it had become virtually impossible to get to the weapons in the care of the Coalition. The sources of the long- Meanwhile, the Overlords were prepared to pounce upon any ships that appeared to be making a move for the Phoenix’s
range communications jamming had been located and destroyed the previous day, but the storm was only beginning to weakened port-aft flank or, alternatively, move in quickly to help finish off any of the enemy vessels that appeared to be
reduce in intensity. Fortunately, long-range communications had begun to clear by the end of the day, but all Lancaster nearly crippled, allowing the Phoenix to focus her attention on the greater threats. At least, that had been the plan.
Coalition forces were still effectively grounded for another two to three days.
Unfortunately, the plan was ruined before it could even be attempted due to a mechanical failure. The tactic used to
On January 23rd, the storm had cleared sufficiently for the Coalition’s DropShips to possibly lift off if the need were to lure the Lola IIIs into a false sense of security through making the D.B.C. Phoenix’s engines appear to be severely damaged
arise, and the coalition’s VTOLs were expected to be able to join in the patrols of the city the following day. The command before engaging the smaller ships had resulted in very real damage to the ship’s propulsion system. This required a
The Phoenix arrived at the pirate point near the Crusader with just minutes to spare before the Blakist WarShips The moment the BattleCorps WarShip completed her roll, bringing her port weapons array into line with the smaller
reached weapons range. The Dreadnought vessel deployed all her fighters and uncoupled her DropShips in less than a Corvette, the Phoenix’s response shattered the Due Diligence like glass. A concentrated burst from all the Phoenix’s port-
minute after completing the jump. Even as she deployed her support craft, the Phoenix herself quickly maneuvered to side guns at extremely long range, followed by a salvo of capital-class missiles, completely ripped the smaller Zechetinu-
bring herself alongside the Crusader, placing her 1.3-kilometer bulk such that the virtually immobile 750-meter JumpShip class Corvette apart, leaving nothing but barely identifiable debris. In performing the roll to present her now-fresher port
was kept in the shadow of the much larger vessel, using the Phoenix for cover. Unfortunately,
it was at this point that the Crusader’s attempt to furl her jump drive’s solar sail failed, with
a sail retraction system jamming, leaving the fragile sail roughly twenty percent deployed.
With the Phoenix all but tied down and unable to maneuver, despite the restored primary
drive engine, the huge WarShip was left with no choice but to remain stationary and take
the punishment that the Word of Blake dealt to her. Fortunately, the massive ship was at
least able to choose which side initially faced the enemy, and thus was able to initially
present her fresher starboard side to the Blakist vessels. This meant that the Phoenix could
indeed protect the Crusader successfully, but the Word of Blake knew full well that so long
as the harmless and vulnerable JumpShip remained intact, the Phoenix was stuck in place,
allowing them to dictate the strategy taken by the BattleCorps sole WarShip.
The engagement between the Phoenix and the Blakist reinforcement WarShips was far
more devastating than the battle with the Lola IIIs had been. Predictably, the Word of Blake’s
fastest fighters scouted ahead to inspect the Phoenix’s otherwise hidden port side. The
fighters used the proximity to the Crusader against the Phoenix to prevent her from opening
fire on them even as they strafed along the WarShip’s damaged hide, lest the powerful
WarShip miss the fighters and strike the Crusader. After reporting their findings, the Blakist
scout fighters came about to join their brethren in engaging the Dreadnought BattleCorps’
Aerospace Fighter Wing. The two Sovetskii Soyuz began to flank the Phoenix, forcing her and
the Crusader to execute a rotation to keep the Phoenix between the JumpShip and the
attacking Heavy Cruisers. The W.O.B.S. Due Diligence, however, broke away and made a
surprise run straight for the Shepherd and Yosemite, the faster-moving Corvette able to
accelerate far more rapidly than the Overlord-A3A DropShips she was bearing down on.
Acting quickly to protect those onboard the Overlords, the Phoenix began to focus her fire
on the more distant, harder-to-hit Due Diligence. During this time, the Illuminated Path and
Purity of Thought were able to savagely attack the Phoenix, their combined fire tearing into
the ship’s extremely durable hull. The Due Diligence’s agility, speed and distance resulted in
only a handful of grazing hits, but even then, the heavy weapons of the Phoenix inflicted
significant damage to the Corvette’s comparably thin armor. The heavy hits that the Phoenix
sustained required her to disengage momentarily and roll herself over, bringing her now-
better-condition port side to bear. Even as she began the rolling maneuver, however, the
Phoenix unleashed one salvo of heavy weapons-fire on the Sovetskii Soyuz-class Heavy
Cruisers that had been savaging her side.
The salvo was effectively a snapshot as her starboard-side weapons arrays were being
pulled out of their firing arc and losing their targeting solution on the Illuminated Path and
Purity of Thought. Even with the nearly careless nature of the barrage directed at the two
Sovetskii Soyuz Heavy Cruisers bearing down on her, the Phoenix’s heavy weapons managed
With the Zechetinu destroyed, the Phoenix quickly shifted the attention of her weapons
to the two Sovetskii Soyuz now tearing into her port flank even as the Leopards savaging
the Phoenix’s increasingly vulnerable starboard side aft continued their assault. The
BattleCorps fighters, which had been working hard to eliminate as much of the Blakist
fighter screen as possible, were forced to turn their attention toward the Leopards, as was
the D.B.C. Shepherd, the remaining Overlord-A3A. Realizing that they were no longer being
ignored, the Leopards attempted to break off into pairs, trying to draw their new assailants
toward one group or the other, while the second group continued its assault on the
Phoenix’s vulnerable flank. This attempt, however, was not successful for long, as the
Shepherd quickly destroyed one of the Leopards, and the BattleCorps’ fighters destroyed
another almost simultaneously.
The two remaining Leopards attempted to get in one last strafing run—or so it seemed
at first. Even as the Illuminated Path violently exploded under a heavy barrage of the
Phoenix’s combined port-side weapons, one of the Leopards rammed itself straight into
the Phoenix’s most critically damaged starboard-aft section, part of the vessel managing
to impact the main propulsion system of the mighty WarShip. Having been holding
approximately stationary to begin with, the impact had no immediate effect on the
Phoenix. The problem of the damage to the main drive system presented itself as the
remaining Sovetskii Soyuz, the Purity of Thought began to maneuver around to attack the
Phoenix’s opened aft side. The Phoenix was suddenly unable to maneuver to keep her
fresher port side facing the enemy or keep the Crusader protected. Seeing that the
remaining Leopard was about to repeat what the other one had done, the Shepherd and
nearly forty aerospace fighters simultaneously opened fire upon the Leopard, all but
disintegrating the small DropShip in a matter of seconds.
The final Blakist WarShip, the Sovetskii Soyuz-class Heavy Cruiser W.O.B.S. Purity of
Thought, continued its arc, trying to stay out of the Phoenix’s primary firing solution, taking
hit after hit from the larger ship’s guns that could still be brought to bear upon it. By the
time that the Purity of Thought was in position to open fire upon the stricken Phoenix’s
vulnerable flank, the Blakist vessel’s hull was in tatters, with the ship venting atmosphere
from breaches all along the ship’s length. Even as the Purity of Thought had begun to line
up a broadside, all the BattleCorps fighters swarmed the ship.
As the Phoenix slowly tried to roll herself to avoid taking a direct hit to her opened side,
the Purity of Thought opened fire with what few weapons she had left; a cluster of naval
lasers and a handful of mixed naval missiles. The lasers failed to find their mark, hitting
various other sections of the battered ship’s hull. Two of the missiles, however, were
perfectly lined up to punch through the hole in the Phoenix’s flank—had the Shepherd not
intercepted them directly by putting herself in the path of the missiles.
armor to the enemy, however, she had exposed her beaten and battered starboard side to a previously unnoticed threat.
The missiles, designed to deal significant damage to full-fledged WarShips, savaged the DropShip’s relatively thin
The Word of Blake had brought with them four Leopard-class DropShips, which had remained undetected as they had armor. The Shepherd barely survived the direct hits. The DropShip’s hull was punched open, venting atmosphere, her
stayed in the shadow of the larger Blakist WarShips. These DropShips chose that moment to enter the fray, flanking the drive systems were barely operational, and her weapons array was entirely offline.
Phoenix and positioning themselves between the WarShip and the JumpShip under her protection. Normally these would
barely constitute a threat to the mighty Battleship, but these were not normal Leopards, but in fact what were known as The Purity of Thought would not get a second chance. Even with the remaining handful of surviving Blakist fighters
“Pocket WarShips”. The Leopards began to fire Killer-Whale-type Capital Missiles into the Phoenix’s already savaged attempting to chase them down, the BattleCorps fighters finished off the Sovetskii Soyuz. The combined firepower of
starboard flank, tearing through what armor was left. This presented a very real problem, as the Phoenix had no real way more than thirty fighters swarmed over the vessel, picking it apart and setting off secondary explosions within the ship,
to target the attacking DropShips, and her disabled anti-missile systems could not destroy the inbound missiles. the last of which shattered the Purity of Thought. The BattleCorps fighters then immediately turned upon their pursuers,
downing all the remaining Word of Blake fighter assets and ending the battle in short order.
As the Purity of Thought and Illuminated Path came about to pour their combined firepower into the Phoenix’s port
side, the BattleCorps’ ship was forced to hold her position. If she were to maneuver, she would risk exposing her even Immediately following the battle’s end, the Crusader quickly rendered all possible aid to those who had come to her
more severely damaged starboard side to the even more dangerous pair of Sovetskii Soyuz Heavy Cruisers bearing down rescue. The Dreadnought BattleCorps worked to pick up the pieces and save as many of their comrades as possible first.
upon her—or worse, expose the defenseless Crusader. With some exceptions, only after search and rescue operations for friendly units had been completed, did they turn their
attention to saving the few who had survived the battle among the Word of Blake forces, grudgingly offering medical
Meanwhile, the Leopards continued to fire their missiles into the Phoenix’s weak-and-weakening starboard side, assistance to those who needed it.
Even with their reduced numbers, the bombardment that the BattleCorps’ Sledgehammers provided was spectacular The Ceòlmhor troopers stormed the hospital by crashing through a section of the roof. One of the battle armor troopers
and effective. In just over two minutes, they laid down a severe barrage that crippled two of the Blakists’ Overlord-class grabbed the bomber and immediately jumped back out again, throwing the man in the direction of an open field before
DropShips and one of their Aurora DropShips and destroyed another Aurora, damaged or destroyed two dozen ‘Mechs attempting to get clear of the blast. The resulting airborne explosion damaged the Dreadnought battle armor suit, but
and nearly as many combat vehicles, and wiped out several squads of battle armor and infantry. The artillery units were not sufficiently to disable it. The other two Ceòlmhor troopers immediately incapacitated the pair of armed assailants,
forced to cease fire and withdraw to escape a series of strafing runs conducted by Word of Blake fighters zeroing in on even as a third armed individual, previously unknown, opened fire on the patients collected in the room. Four patients
their position. The timing was in a way fortuitous as the extremely limited ammunition supply had been severely depleted. were hit, three critically, but the two battle armor troopers were able to immediately put an end to the attack. The third
The 4th Battalion’s commanding officer was immediately killed by concentrated heavy
weapons-fire. Immediately after this information had been communicated to the rest of
the battalion, the Blakist operative jammed all friendly communication within the
battalion, feeding confusion and panic. (It was later confirmed that this individual had
been responsible for the 102nd Provisional Division’s knowledge of Colonel Lawrence’s
location during the fighting weeks earlier.)
The 4th Battalion was routed and crushed in a matter of minutes. One of the few
surviving members of the Battalion managed to track down the Omniscience Command
Vehicle occupied by the operative and use his ‘Mech to destroy it, before being himself
killed in action. The other three survivors of the 4th Battalion finally rendezvoused with
the Blackwood Templars’ 3rd Company to try to warn them of what was heading their
way. Unfortunately for the Templars’ 3rd Company and the three BattleCorps ‘Mechs that
joined them, it was too little, too late. The Word of Blake were already in the process of
closing in around them from all directions and had already begun their attack.
In the end, the sole survivor of the Templars’ 3rd Company was a female MechWarrior,
the pilot of a Ryoken who was rescued by the only members of the BattleCorps’ 4th
Battalion to survive the onslaught: the same Ceòlmhor Battle Armor squad that had
stormed the hospital. The hospital itself sustained severe damage during the fighting. It
was this damage, caused intentionally by the 55th after the 3rd Company had given
everything they had to try to protect the hospital, which claimed the lives of fifty-two
patients, doctors and nurses who had not been successfully evacuated. Of the lives lost,
the majority had been surviving members of the D.B.C. Ryūjin’s crew, though eleven were
natives of Vyrie City.
With a large gap now in the defensive line between the Word of Blake’s 55th Shadow
Division and the Ronin Free Companies, who stood as the protectors of the nuclear
weapons stockpile, the 55th quickly rushed to attack the defensive line surrounding the
capitol building and HPG station. Given the circumstances, the order from Colonel Ann
Lawrence to Free Colonel Donaldarus Meridius of the Ronin Free Companies was to hold
the line until the Dreadnought BattleCorps and Blackwood Templars could move into a
position to counterattack. In addition to the Ronin’s own pair of Fortress-class DropShips,
which had been landed near the city center to offer additional fire support, the
mercenaries had considerable help in the form of the Ad Hoc Militia Battalion, the 5th
Irregular Battalion of the Dreadnought BattleCorps, and a handful of BattleCorps anti-air
artillery vehicles. Despite this, it was clear that the Ronin Free Companies were going to
sell many of their lives dearly to buy desperately needed time. Free Colonel Meridius had
promised Colonel Lawrence that he could hold for thirty minutes, and he intended to hold
to his word.
assailant was reduced to a smear on the wall as the return fire from the Ceòlmhor Battle Armor troopers obliterated him.
The situation worsened as the Word of Blake’s 55th Shadow Division engaged the defensive line formed by the Ronin
As the Blackwood Templars’ 3rd Company moved in to provide security for the hospital for the restarted evacuation, Free Companies and those reinforcing them. Just as contact was made, a part of the Ad Hoc Militia Battalion, Chipper
the Dreadnought BattleCorps’ 4th Battalion shifted its position to try to provide protection for the Templars on-site. The Lance, which consisted of three Goblin Medium Tanks and one of the refit Heavy Missile Carriers, turned their weapons
plan had been to stall the Word of Blake for as long as possible, initiating a slow withdrawal while holding up the incoming on friendly units, sowing momentary chaos and nearly creating a break in the defensive line. Minutes after they began to
hostile force—or at least diverting the Blakists toward either defensive flank so that the incoming friendly reinforcements fire on friendly machines and personnel, the lance of turncoat militia units was destroyed, but not before they managed
might have a chance to engage them sooner as the rest of the friendly units moved to pincer the Word of Blake. In either to destroy three friendly Ad Hoc Militia Missile Carriers and one of the artillery vehicles. They also damaged one of the
case, it would provide the Templars’ 3rd Company the time that they needed to complete the evacuation and regroup, Ronin Free Companies’ Gauss Rommels and crippled a BattleCorps Tyrant BattleMech.
then reinforce the 4th Battalion as the BattleCorps troops gradually fell back. It was not to be.
In truth, the results of the betrayal by Chipper Lance could have been far worse. With the attention of the Dreadnought
A Word of Blake sleeper agent hidden within the Dreadnought BattleCorps’ ranks, acting as a communications officer BattleCorps’ 5th Irregular Battalion solely on the attacking 55th Shadow Division machines, as the backstabbing Militia
in the 4th Battalion’s own Omniscience Command Vehicle, chose this moment to strike. Shortly after the 4th Battalion vehicles were behind them, it was only the quick actions and excellent gunnery of the Ronin Free Companies’ Gauss
engaged the 55th Shadow Division, the agent killed the rest of the vehicle’s crew. He then scrambled the 4th Battalion’s Rommels that put down the betrayal within seconds of realizing what was happening, destroying the traitors in their
TDN (the Dreadnought’s own proprietary Target Data Networking System), sending every unit in the BattleCorps 4th midst without hesitation.
Battalion garbage data that only harmed their aim, rather than helping it. Simultaneously, he activated a transmitter that
shared all the telemetry collected by the command vehicle and, using the TDN’s own processing system, also shared the With the turncoats annihilated, the momentum of the Word of Blake’s push dissipated rapidly and, after considerable
The Ronin Free Companies had an established supply line within the city center and while
their units were largely immobile, they had entrenched themselves well. The survivability of
the unit was amplified by the presence of the BattleCorps’ Triton Repair Vehicles, which
offered locations for quick ammunition resupply and hastily-made armor patches. They were
not without losses of their own, but the Ronin were holding the line admirably, with their
heavily fortified Gauss Rommels dealing severe blows to whatever crossed their paths. While
their ground units were largely intact, their Fortress-class DropShips had taken a beating and
their durable armor was wearing thin.
The Word of Blake’s 55th Shadow Division, their advance having been blunted and stalled
out by the defensive line around the city center, had taken severe casualties of their own.
For every one of the Lancaster Coalition units that the Blakists had downed, the Coalition
had returned the favor. Unfortunately for the Ronin Free Companies and the remains of the
BattleCorps’ 5th Irregular Battalion, the battle of attrition was favoring the greater numbers
of the Word of Blake.
In terms of the battle in the skies above, though the Blakist fighters had largely been
destroyed and many of those that remained were getting dangerously close to running on
fumes. Most of the active Blackwood Templars and Dreadnought BattleCorps AeroFighters
Most disturbingly, at least from the perspective of those making up the 55th’s rear guard,
it might have seemed as though the Clans had appeared on the world of Ashkum IV. The
Dreadnought BattleCorps’ 3rd Battalion, the Wildcards, consisting entirely of former Clan
warriors, many of whom piloted reconstituted Clan ‘Mechs and assisted by Elemental Battle
Armor, swept up from the south, assaulting the 55th’s rear flank. The Wildcards Battalion
proceeded to wreak havoc on the enemy, sowing chaos into the Blakist lines with a single-
minded fervor.
Most of the Templars continued to push out from the Ronin Free Companies’ defensive
line like a tidal wave, moving through and away from the Ronin to inflict maximum damage.
The Ronin, after dispatching the few enemy ‘Mechs that had gotten uncomfortably close to
their goal, were allowed a brief respite to regroup before they had to deal with hostiles
attempting to break down their defenses once more. Fortunately, this time, it proved to be a
mere trickle of enemy units versus the flood that they had been forced to hold back for so
long, and the Ronin had far less trouble holding their own. Nevertheless, the badly battered
and bruised defenders had their hands full.
The 55th rallied once more as it seemed to regain its composure, a new commander clearly
taking over for the one who had fallen. The 55th turned its attention back to the Ronin Free
Companies once more in a desperate move to seize the nuclear weapons stockpile. The
Blakists surged forward, leaving the Wildcards Battalion behind and initially unable to catch
up. It was in this moment that the Demi-Precentor who had taken command of the 55th
Shadow Division was engaged in close-range combat against the infamous machine known as
Bloodbath, piloted by none other than Colonel Tyr Blackwood of the Blackwood Templars.
This moment was one that the Templars’ Colonel would later only recall with a feeling of
annoyance. Bloodbath’s hatchet became so firmly lodged in the head of the Demi-Precentor’s
OmniMech that it had taken extraordinary effort to pull the melee weapon free. By the time
he had successfully extricated it, his stalled progress had left him momentarily separated
from the rest of his lance, as his lancemates had continued to carry out his most recent
command: “Charge!”
Aside from this momentary inconvenience, Colonel Blackwood had dismissed the existence
of the Word of Blake Manei Domini MechWarrior without hesitation, intent on killing as many
of the 55th Shadow Division as he could. Like the rest of the Templars, Colonel Blackwood
was fueled by a rage stemming from the loss of his 3rd Company and the numerous casualties
taken by his Aerospace Wing. The Templars were like family, and the Word of Blake had
claimed many of their number on that day. Colonel Lawrence had done well to keep the
The disarray of losing their leader twice in short order was remarkably short-lived
before the 55th Shadow Division reorganized once again. The different sub-units within
the 55th quickly turned their attention toward breaking out of the encirclement that the
Lancaster Coalition had created around them. That is, right up until the Sumaire Assault
OmniMech piloted by one of Colonel Ann Lawrence’s lancemates, Major Adrian Steele,
annihilated a damaged Blakist Deva Celestial OmniMech in the effort to protect the
Colonel. The loss of overall unit cohesion within the 55th was considerably longer and
more extensive following the destruction of that machine. This loss, in addition to the
simultaneous push from all sides, as well as the confused reports of Clan units appearing
at the rear of the Blakist lines, seemed to cause a total (if momentary) lapse in direction.
Shortly after the pincer had begun to close around the 55th Shadow Division, Colonel
Ann Lawrence issued an unusual order. The Manei Domini ‘Mechs and vehicles that were
destroyed were to be immediately tagged for the BattleCorps’ Ceòlmhor and Elemental
Battle Armor squads to terminate the pilots and crews. The order was uncharacteristic of
Lawrence, and it was not something the BattleCorps was accustomed to being ordered to
do.
Many of the battle armor units accepted the task somewhat grudgingly, though
fulfilling the task just as quickly as those who genuinely used the order as a release of
restraint, allowing them to headhunt the enemy to avenge their lost comrades. They were
aware of the threat that the Manei Domini could pose if they were allowed to escape into
the civilian population, but the order still seemed extreme. Only after word had circulated
of the death of a trooper in full Kitsune Medium Battle Armor at the hands of an unarmed
Manei Domini MechWarrior near the capitol building did even the most hesitant of the
battle armor troopers fully understand why Colonel Ann Lawrence had issued what had
amounted to a “Take no prisoners, kill them all” order. It had not been an act of a vengeful
commander, but in fact one trying to protect the lives of her troops.
The battle for Vyrie City lasted roughly fifteen more hours, even with the ability for the
Lancaster Coalition’s ground forces and aerospace fighters to cycle their damaged and
munitions-depleted units away from the battlefront for refit and reloading, while the
exhausted Word of Blake 55th Shadow Division had no such liberties. Several Word of
Blake’s DropShips were forced to surrender, either intact or crippled by artillery.
However, four of the DropShips were either crewed and/or commanded by Blakists so
loyal to the cause that they refused to allow their ships to fall into the hands of the
Lancaster Coalition. Instead, they chose to self-destruct their ships, killing everyone
aboard these four vessels. Although the last of the Blakist ‘Mechs, AeroFighters, combat
vehicles and battle armor had been tracked down and destroyed, sporadic fighting
occurred for nearly a week as more and more of the 55th Shadow Division’s personnel were found and accounted for. further contracts.
After successfully recharging her jump drive and Lithium-Fusion Battery, despite the hindrance of a mildly damaged
Operation LANCASTER Aftermath: “We Won...” solar sail, the D.B.C. Phoenix managed to make the trip home without further incident. The great vessel was battered and
scarred, and her primary propulsion system had been ruled irreparable short of work that could only be done at a dry
It took weeks for all the dead to be collected and cataloged, though priority was given to the collection of Lancaster- dock, but her functional jump drive meant that she could make the interstellar trip back to the Acala system safely.
Coalition-associated bodies. The initial cataloging of Word of Blake Manei Domini corpses was generally a double tap to
the cranium with a high-powered rifle to ensure that the dead opposition was indeed dead and would stay that way. The Phoenix carried with her those who had fallen in service of the BattleCorps as well as the unit’s wounded and those
Meanwhile, sweeps to eliminate any Manei Domini survivors continued. who had been released from treatment at local hospitals in Vyrie City. While the DropShips carrying the dead and
wounded made their way to Acala III, the Phoenix was ever-so-slowly towed to one of the Orbital Defense & Refit
As the dead were gathered, the members of the Lancaster Coalition mourned their respective dead in their own ways. Platforms in orbit over the planet. Once there, the lengthy process of repair and refit began.
In the case of the Dreadnought BattleCorps and the Blackwood Templars, Operation LANCASTER caused the greatest
death toll ever suffered by either unit in a single deployment. In the case of the Templars, it is believed that this event Salvage operations on Ashkum IV were ongoing for nearly a month for the Ronin Free Companies and Blackwood
was the beginning of the end for the unit in terms of their operations as mercenaries, with a feeling of having “run out of Templars prior to their departure from the world. In the case of the Ronin Free Companies, they directly replaced the
luck”. Although the Templars went on to assist Stone’s Coalition in the operation to liberate Terra from the Word of Blake, DropShip that was all but destroyed during the late defense of the city center with one of the Word of Blake ships of the
the unit returned home to Son Hoa immediately afterward. As of the latest reports, they appear to have not taken any same class, albeit not before spending weeks effectively turning the ship inside-out searching for sabotage or any kind of
Operation LANCASTER Aftermath: One Step Forward, Two Steps Back What the people and government of Ashkum IV had managed to forget was just how dependent on Dreadnought they
had become for their day-to-day lives. Early during Operation LANCASTER, when the Dreadnought BattleCorps was first
The reinforced 3rd Battalion of the Dreadnought DefenseCorps 1st Homeworld Regiment arrived on Ashkum IV on the arriving on-world and destroying Blakist communications and tactical satellites, the entire telecommunications satellite
26th of April, 3077, more than two months after the official end of Operation LANCASTER. With their arrival as a relief network had been destroyed to ensure that the Word of Blake could not use the civilian systems for their own purposes.
force, the Dreadnought BattleCorps 1st Regimental Combat Team officially departed Ashkum IV. This departure did not As a result, the entire telecommunications network across the world had been dependent purely on the highly
take place until after the entire nuclear weapons stockpile had been carefully loaded onto the BattleCorps’ DropShips for sophisticated tactical satellites that the BattleCorps had deployed during planetfall. Given the expense of these units and
transport with the intent of safe disposal. The BattleCorps returned home to Acala III on the 17th of May, after an eight- disinterest in anyone outside of Dreadnought’s military gaining access to them, these satellites were recovered by the
day layover in the Axton system. DefenseCorps as they left.
The DefenseCorps force of an overstrength Battalion of troops put in place for the stated purpose of protecting the During the fighting, the primary fusion power plant that was responsible for powering Vyrie City, as well as numerous
EngineerCorps personnel helping to rebuild Vyrie City was at first received with only slightly-hesitant acceptance. The other smaller surrounding areas of civilization, had been destroyed by a Word of Blake heavy aerospace fighter that had
departure of the BattleCorps from the world was perceived as sufficient reason to believe that no long-term occupation crashed into it. This impact had been followed by a massive secondary explosion that ripped apart all six of the fusion
was intended. This opinion gradually began to change over the following months, however, with a negative sentiment reactors that made up the powerplant. As a result, power had been supplied via several mobile power generation stations
toward Dreadnought beginning to take root. Given the souring relations with the indigenous population, Dreadnought that the EngineerCorps had brought with them. In a move that is still considered by some as “somewhat vindictive” to
contacted Comstar, asking them to retake control over the damaged local HyperPulse Generator station. this day, these mobile power generation stations were recalled, leaving the region without a primary source of electricity.
A secondary result of this was that the HyperPulse Generator station, which had been damaged months prior, was
Although Comstar had their hands full with the recently-launched Operation SCOUR—the massive, allied multinational temporarily disabled until the station’s powerful internal fusion reactor could be restored. It was more than three weeks
operation to destroy the Word of Blake and eventually liberate Terra—they eventually managed to provide an operations before Comstar restored power to the facility. One of the first messages to be received by the HPG was an apology from
team to run the HPG on Ashkum. In addition to ensuring that the HPG was occupied by a neutral organization, even one Dreadnought Interstellar Industries for the inconvenience, and a request to put the repair costs on the tab of Ashkum’s
as suspicious as Comstar, the presence of Comstar on-planet was intended to ensure that there was a third, neutral party local government.
present to act as an intermediary between the local government and Dreadnought’s own personnel. Unfortunately, the
presence of Comstar proved to be insufficient to stop the wheels already in motion from continuing to turn. The powerful fusion reactor at the heart of the HPG station was capable of powering large portions the surrounding
city at a time. Comstar took advantage of the situation to gain control over not just the planet’s only means of interstellar
Negative sentiment among the population toward Dreadnought’s continued presence only continued to worsen the communications, but to also take control over power generation for the greatest city on the planet, granting them control
longer that they remained, even though the government continued to state publicly that their presence was welcome over much of Ashkum IV’s remaining infrastructure. Unfortunately, Comstar could not stop the downward spiral that had
and that they appreciated the help. The anti-Dreadnought sentiment grew to the point where protests were held around begun on the world. In the time following Dreadnought’s departure and before restoration of independent local power
areas where they were working. These protests quickly escalated to riots within weeks, and in the middle of the night on generation was completed, the planetary economy on Ashkum IV crashed. The lack of rapid intercontinental
the 15th of July, an attack took place on the hotel that had been provided for the DefenseCorps and EngineerCorps to use communication, the loss of power in the world’s largest city as well as several surrounding towns, combined with the
as a temporary barracks. damage that had been inflicted elsewhere by the massive storm that swept over much of the northern continent of Capri
shortly after LANCASTER began, topped by the other damage done by both sides during the fighting—it was all too much
The attack on the barracks was carried out by more than thirty individuals who had been long-time citizens of Ashkum for the economy to sustain itself, despite Comstar’s best efforts.
IV, civilians all, though some had history serving in one form of armed forces or another. The armed civilians had donned
armor and armed themselves with weapons that had been reported as stolen from a militia depot the prior week. A The nearby spaceport had also been primarily dependent on the massive fusion powerplant that was destroyed in the
firefight ensued within the hotel for nearly fifteen minutes. The DefenseCorps and EngineerCorps personnel sustained fighting, though it mattered little as the spaceport was all but deserted following Dreadnought’s departure. The Lancaster
thirteen casualties, four of which proved fatal. Of the attackers, thirteen died during the fighting, while a further six Coalition had made sure to take with them every salvageable DropShip that had been brought to Ashkum IV by the Word
perished either en route to hospital or after arriving. A further fifteen lived to be arrested later in various states of health. of Blake. The only DropShip that had still been present was the Mule-class DropShip that had brought the Comstar HPG
Dreadnought was forced to hand the attackers over to the local authorities—unlike the hundreds of Word of Blake station crew and their support staff to the world, and even that vessel had departed a short while after the Dreadnought
prisoners of war captured by the Lancaster Coalition who had been quickly picked up by Federated Suns representatives. ships did. Months passed before any sort of normal traffic began to flow through the spaceport once more.
The military forces that made up the Lancaster Coalition, as well as the Word of Blake’s 102nd Provisional and 55th Shadow Divisions, were considerable. In total, 7 WarShips, 11 JumpShips, 48
DropShips, 300 aerospace fighters, 582 ‘Mechs, 20 ProtoMechs, 61 VTOLs, 553 ground vehicles, hundreds of battle armor troopers and hundreds more conventional infantry were involved in the
violent events that took place on Ashkum IV. Listed in this section are the Tables of Organization & Equipment for each of the different units involved in the fighting during Operation LANCASTER.
63 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
OPERATION LANCASTER – TABLES OF ORGANIZATION & EQUIPMENT
Lancaster Coalition Capital Ship & JumpShip Allocation
D.B.C. Phoenix (Texas-LFR-Class WarShip) D.I.I.S. Nikolaus Armstrong (Invader-Class JumpShip [2631—PPC])
– Crippled (Combat Damage) Personnel: 23 Crew, 10 Bay Personnel
Personnel: 579 Crew, 120 Marines, 220 Bay Personnel – 49 Injured, 37 Dead Capacity: 3 DropShips, 2 Small Craft, 522 tons Cargo
Capacity: 6 DropShips, 60 AeroFighters, 16 Small Craft, 232,655 tons Cargo - 2 Skua Recovery Craft (2 Small Craft)
- Firebird Aerospace Fighter Squadron (6 AeroFighters) - Cargomaster-class DropShip – D.B.C. Osiris
- Hammer Aerospace Fighter Squadron (6 AeroFighters) - Condor-Dove-Class DropShip – D.B.C. Caladrius
- Havoc Aerospace Fighter Squadron (6 AeroFighters) - Overlord-Two-Class DropShip – D.B.C. Temperance
- Hellfire Aerospace Fighter Squadron (6 AeroFighters) - 521 tons Spare Parts, Equipment & Other Supplies
- Lightning Aerospace Fighter Squadron (6 AeroFighters)
- Reaper Aerospace Fighter Squadron (6 AeroFighters) D.I.I.S. Razorback (Invader-Class JumpShip [2631—PPC])
- Spicy Aerospace Fighter Squadron (6 AeroFighters) Personnel: 23 Crew, 10 Bay Personnel
- Striker Aerospace Fighter Squadron (6 AeroFighters) Capacity: 3 DropShips, 2 Small Craft, 522 tons Cargo
- Talon Aerospace Fighter Squadron (6 AeroFighters) - 2 Skua Recovery Craft (2 Small Craft)
- Thunder Aerospace Fighter Squadron (6 AeroFighters) - Overlord-A3A-Class DropShip – D.B.C. Shepherd
- SAR Upsilon (8 Small Craft) - Overlord-A3A-Class DropShip – D.B.C. Yosemite
- SAR Omega (8 Small Craft) - 519 tons Spare Parts, Equipment & Other Supplies
- Excalibur-Class DropShip (2786) – Malta
- Fortress-Class DropShip (3058) – Himeji D.I.I.S. Sunbeam (Invader-Class JumpShip [2631—LL])
- Fortress-Class DropShip (3058-Custom) – Matsumoto Personnel: 23 Crew, 10 Bay Personnel
- Miraborg-Class DropShip – Archangel Capacity: 3 DropShips, 2 Small Craft, 522 tons Cargo
- Overlord-Class DropShip (2762-Custom) – Gekokujo - 2 Skua Recovery Craft (2 Small Craft)
- Overlord-Class DropShip (2762) – Cathedral - Borealis-Class DropShip (Battle Armor Carrier) – Bohemond
- 232,649 tons Spare Parts, Munitions, Equipment & Other Supplies - Cargomaster-class DropShip – D.B.C. Mercury
- Union-Class DropShip (2708) – 8-Ball
D.B.C. Fractured Fang (Odyssey-Class JumpShip) - 502 tons Spare Parts, Equipment & Other Supplies
Personnel: 39 Crew, 65 Bay Personnel
Capacity: 4 DropShips, 2 Small Craft, 10 Battle Armor, 488 tons Cargo D.I.I.S. Stardancer (Mammoth-II DiscoveryCorps-Class JumpShip)
- 2 Skua Recovery Craft (2 Small Craft) Personnel: 72 Crew, 40 Marines, 20 Bay Personnel – 2 Injured
- Colossus-Class Assault DropShip (Dreadnought BattleCorps Refit) – D.B.C. Dragon Capacity: 8 DropShips, 4 Small Craft, 2,121.5 tons Cargo
- Colossus-Class Assault DropShip (Dreadnought BattleCorps Refit) – D.B.C. Ryūjin - 2 (Unnamed) Borealis-Class DropShips (AeroFighter Carrier) Note: Each of the D.I.I.S. Stardancer’s two
- Colossus-Class Assault DropShip (Dreadnought BattleCorps Refit) – D.B.C. Wyvern - 4 Skua Recovery Craft (4 Small Craft) Borealis-class DropShips carried six DII-SBT-AS-
- Overlord-Class DropShip (2762) – D.B.C. Indomitable Spirit - 1,458 tons Spare Parts, Equipment & Other Supplies Y1 Sabretooth Medium Aerospace Fighters (12
- Fang Alpha Elemental Point (5 Battle Armor)
AeroFighters in total).
- Fang Beta Elemental Point (5 Battle Armor)
- 485 tons Spare Parts, Munitions, Equipment & Other Supplies
Lancaster Coalition JumpShip Fleet Organization:
D.B.C. Leaping Leopard (Odyssey-Class JumpShip)
Personnel: 39 Crew, 65 Bay Personnel – 1 Injured Lancaster Special Task Force
Capacity: 4 DropShips, 2 Small Craft, 10 Battle Armor, 488 tons Cargo
- 2 Skua Recovery Craft (2 Small Craft) “Peekaboo” Scout
- Fortress-Class DropShip (2613) – D.B.C. Basilisk - Mammoth II DiscoveryCorps-Class JumpShip – D.I.I.S. Stardancer
- Fortress-Class DropShip (2613) – D.B.C. Fafnir
- Overlord-Two-Class DropShip – D.B.C. Perseverance Relay Messenger
- Overlord-Two-Class DropShip – D.B.C. Shelby - Invader-Class JumpShip – D.I.I.S. Razorback
- Leopard Alpha Elemental Point (5 Battle Armor)
- Leopard Beta Elemental Point (5 Battle Armor) Lancaster Transport Groups
- 482 tons Spare Parts, Munitions, Equipment & Other Supplies
Lancaster Transport Group Alpha
- Odyssey-Class JumpShip – D.B.C. Fractured Fang
- Odyssey-Class JumpShip – D.B.C. Leaping Leopard
Black-Water Forces
Phoenix Assault Group DropShips
- Overlord-A3A-Class DropShip – D.B.C. Shepherd – **//^^(7)^^^(9)
- Overlord-A3A-Class DropShip – D.B.C. Yosemite – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Intercept Lance
- Hammerhai DII-HMD-BC1 “Amarok” – Ostego, Grayson, LT – **
- Lancer (Memory Knight) DII-LNR-BC1 “Caliburn Prime” – Herschel, Viktor, SGM – **//^^
- Tyrant DII-TYR-BC1 “Fox Ache” – Verrak, Jens, SGT – **
Support Lance
- Gemini DII-GMN-O BC-A “Tasha” – Howard, Jessica, LT – ****
- Mattock II DII-MTK-2-BC1 “Rocket’s Redemption” – Shaw, Zarya “Z”, 2LT
- Reckoning DII-RCK-BC2 “Rum Cully” – Mercier, Marton, 2LT – ****
Beta Company
Recon Lance
- Ravage II DII-RVG-2-O BC-A “Angel” – Drake, Cora, SGM – **
- Ravage II DII-RVG-2-O BC-A “Bob” – Drummer, Keenan, 2LT – ***//^^
- Ravage II DII-RVG-2-O BC-A “Stiletto” – Xavier, Jackie, LT – **
Intercept Lance
- Tyrant DII-TYR-BC1 “Delta” – Bellman, Mark, LT – **//^^
- Tyrant DII-TYR-BC1 “Martinet” – Glover, Neil, SGT – ***//^^
- Tyrant DII-TYR-BC1 “Omega” – Burns, Burnie, 2LT – ****
Support Lance
- Lancer (GunKnight) DII-LNR-BC2 “Gun Bunny” – Visitor, Tolan, LT – **//^^^
- Marauder DII-MAD-3R(BC) “Bunty Hounder” – Fawkes, Michael, 2LT
- Reckoning DII-RCK-BC1 “Second Chance” – Davros, Alex, SGM
Command Lance
- Mattock II DII-MTK-2-BC1 “Thunderball” – Sisko, Jadzia, LT – ****
- Neugen DII-NGN-O BC-C “Revelation” – O’Brien, Peter, MAJ; Jensen, Kris, LT/TAC – **
- Sumaire DII-SMR-O BC-A “Ceòl” – Yesmar, Ydur, LT
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Recon Lance
- Ravage DII-RVG-O WC-B “Comet” – Franz, MW – ****
- Ravage DII-RVG-O WC-B “Siren” – Lorelei, MW – ****
- Ravage DII-RVG-O WC-B “Skids” – Yami, MW(LL) – ***//^^
Intercept Lance
- Goshawk (Vapor Eagle) “Ainneamhag” – Jenna, MW(LL)
- Shadow Cat PRIME “Pantheress” – Vincent, MW – **//^^
- Stalking Spider “Charlotte” – Wilbur, MW
Stalking Spider “Charlotte”:
Support Lance Modified Standard/1 variant. Upgrades to
- Hammerhands IIC 3 – Benjamin, MW – ***//^^ 250-rated ExtraLight Fusion Engine, adds 2-
- Hammerhands IIC 4 – Fruneker, MW(LL) – **//^^ ton Targeting Computer to the right torso,
- Supernova “Star Burst” – Larissa, MW – ** replaces the SRM-4s with Streak-SRM-4s
with one ton of ammunition, adds two
Battalion Command Lance double heat sinks (one installed in each side
- Daishi (Dire Wolf) “Obsidian” – Jorge, CMDR “WildCard Actual” torso) for a total of thirteen. It is otherwise
- Gemini DII-GMN-O WC-B “Great Vision” – Asya, MW unmodified. (Battle Value: 2,755)
- Kodiak “Goober” – de Randamie, Tolga, MW – **
Kappa Company
Recon Lance
- Ravage DII-RVG-O BC-A “Radish” – Cornish, David, LT – ****
- Ravage DII-RVG-O BC-A2 “Leg Day” – Humby, Evan, SGT – ****
- Ravage DII-RVG-O BC-B “Scram” – Zenko, Brent, SGT – ****
Intercept Lance
- Tyrant DII-TYR-BC2 “Flasher” – Gratton, Ulysses, SGT – **//^^^
- Tyrant DII-TYR-BC2 “Rave” – Parker, Jacob. LT – ****
- Tyrant DII-TYR-BC3 “Sucker-Punch” – Wyatt, Belinda, SGM – ****
Support Lance
- Hammerhai DII-HMD-BC1 “Hop” – Gill, Ryan, SGM – **//^^^
- Hammerhai DII-HMD-BC1 “Skip” – Metcalfe, Brian, LT – ****
- Hammerhai DII-HMD-BC1 “Jump” – Zbryski, Geoff, SSGM – ****
Command Lance
- Mattock II DII-MTK-2-BC1 “Silencer” – Jameson, Gini, SSGM– **//^^^
- Neugen DII-NGN-O BC-A “Mastermind” – Szilagyi, Jan, MAJ; Ratner, Milli, 2LT/TAC – ****
- Sumaire DII-SMR-O BC-A “Minion” – Marks, Samuel, 2LT – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Pi Company – 5th Irregular Battalion Rapid Response Team Alpha Sigma Company – 5th Irregular Battalion Assault Battle Armor
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Seven-Three Company
Dreadnought BattleCorps 1st RCT – 7th Armor Battalion
Airborne Recon Lance Alpha
Seven-One Company - Albatross Light Attack VTOL DII-AB-VT-BC1 “Peeping Tom”
- Albatross Light Attack VTOL DII-AB-VT-BC2 “Seeker” – **//^^(2)
- Albatross Light Attack VTOL DII-AB-VT-BC2 “The Moth” – ****
Recon Lance
- Streaker Recon Buggy DII-SRB-WV-BC1 – ****
Airborne Recon Lance Beta
- Streaker Recon Buggy DII-SRB-WV-BC1 – ***//^^(1)
- Albatross Light Attack VTOL DII-AB-VT-BC1 “Qepleacoptor”
- Streaker Recon Buggy DII-SRB-WV-BC3 “Wind-Up Mobile” – ****
- Albatross Light Attack VTOL DII-AB-VT-BC2 “The Observer” – **//^^(1)
- Albatross Light Attack VTOL DII-AB-VT-BC2 “Weasel” – **
Battle Lance
- Kodiak Heavy Tank DII-KHT-TV-BC1 “Bullseye” – **
Airborne Recon Lance Gamma
- Kodiak Heavy Tank DII-KHT-TV-BC1 “Death’s Ambassador”
- Albatross Light Attack VTOL DII-AB-VT-BC1 “Witness” – ****
- Kodiak Heavy Tank DII-KHT-TV-BC1 “The Manager” – ***//^^(3)
- Albatross Light Attack VTOL DII-AB-VT-BC2 “Spirit” – ****
- Albatross Light Attack VTOL DII-AB-VT-BC2 “The Wasp” – ****
Support Lance
- Sledgehammer Assault Vehicle DII-SAV-TV-BC2 “Aftershock” – ****
Airborne Recon Lance Delta
- Sledgehammer Assault Vehicle DII-SAV-TV-BC2 “Double-Tap”
- Albatross Light Attack VTOL DII-AB-VT-BC1 “The Falcon” – ***//^^(1)^^^(1)
- Sledgehammer Assault Vehicle DII-SAV-TV-BC2 “Tooth Fairy” – **
- Albatross Light Attack VTOL DII-AB-VT-BC2 “Supersonicopter”
- Albatross Light Attack VTOL DII-AB-VT-BC2 “The Wraith”
Battalion Command Lance
- Omniscience Command Vehicle DII-OCV-WV-BC1 “The Umpire”
- Sprinter Light Tank DII-SLT-TV-BC1 “The Batter”
- Sprinter Light Tank DII-SLT-TV-BC2 “The Pitcher”
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Eight-Three Company
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
D.B.C. Wyvern (Colossus-Class Assault DropShip [Dreadnought BattleCorps Refit]) D.B.C. Temperance (Overlord-Two-Class DropShip)
Personnel: 60 Crew, 20 Marines, 756 Bay Personnel – 25 Injured Personnel: 43 Crew, 156 Bay Personnel – 2 Injured
Capacity: 36 ‘Mechs, 72 Heavy Vehicles, 72 Battle Armor, 2 Dedicated Satellite Bays, 662 tons Cargo Capacity: 24 ‘Mechs, 12 Heavy Vehicles, 6 AeroFighters, 732.5 tons Cargo
- 2nd Reinforced Battalion Delta, Epsilon and Zeta Companies (36 ‘Mechs) - 2nd Battle Wing Red Aerospace Fighter Squadron (6 AeroFighters)
- 2nd Reinforced Battalion Support Company (12 Vehicles) - 5th Irregular Battalion Rho Company (12 ‘Mechs)
- 2nd Reinforced Battalion Battle Armor Company (12 Vehicles, 36 Battle Armor) - Support-Twelve Company (12 Vehicles)
- 5th Irregular Battalion Tau Support Battle Armor Company (36 Battle Armor) - 2 Precognition Type-VII Tactical Satellites (45 tons each—40-ton satellite and 5-ton thruster—occupying ‘Mechbays)
- 6th Armor Battalion (36 Vehicles) - 732.5 tons Spare Parts, Munitions, Equipment & Other Supplies
- Support-Sixteen Company (12 Vehicles)
- Wyvern Security Team - 2 Squads Dreadnought Elite Marines (20 Marines)
- 2 Precognition Type-VII Tactical Satellites (45 tons each—40-ton satellite and 5-ton thruster) Dreadnought BattleCorps 1st RCT – Ground Forces Support DropShip Allocation
- 662 tons Spare Parts, Munitions, Equipment & Other Supplies
Flag Lance
- Berserker BRZ-A3 “Crossbones” – Cordova, Hank, LT – **
- Bloodbath BLD-BT-4 – Blackwood, Tyr, COL – **//^^
- Highlander HGN-733 “Honor” – Shiro, Daisuke – **
- Marauder II MAD-4A “Blackwood” – Blackwood, Sigrun; Nagata, Yuki, TAC
- Sagitaire SGT-8R – Blackwood, Morgan, CAPT – **//^^^
1st Company
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
Asahi Lance
- Banshee BNC-1E “Lumberjack” – Cho, Anton, CPT – **//^^
- Cyclops CP-12-K “Warcrime” – Derius, Maximus Braccus, MAJ –**
- Mad Cat Mk II “Sandstorm” – Jordan, Mike, LT. COL – **
- Sumaire DII-SMR-O PX – Meridius, Donaldarus, COL – **//^^
Kawase Lance
- Charger CGR-SA5 – Smith, Marcus, MSGT
- Warhammer WHM-9S – Staker, Peter Ian, SGT – **//^^^
- Thug THG-13K – Imoto, Kiru, SSG – **//^^
- Akuma AKU-2XK – Algrin, Nathan, 2LT – **
Sakura Lance
- Archer ARC-4M “Tempest Fury” – Adams, Jezebel, SSG – **//^^
- Rifleman RFL-3N “Gravy” – Garrels, Horace, SSG
- Roughneck RGH-1RF “Ronin Special” – 185974381 “Eight”, SGT – **//^^
- Roughneck RGH-1RF “Ronin Special” – 185967531 “Three”, 1LT – ****
Tabako Lance
- Rommel Tank (Gauss) “Firebrand” – **
- Rommel Tank (Gauss) “Hornet” – **
- Rommel Tank (Gauss) “Little Alice” – **//^^(1)
- Rommel Tank (Gauss) “Big Alice”
Nagoya Lance
- Rommel Tank (Gauss) “I Hate Haggis” – ****
- Rommel Tank (Gauss) “Emu”
- Rommel Tank (Gauss) “Elephant” – **//^^^^
- Rommel Tank (Gauss) “Crazy Carmen” – **//^^(2)
Hagaki Lance
- Rommel Tank (Gauss) “Fat Bastard” – **//^^(1)
- Rommel Tank (Gauss) “Firebat” – **//^^(3)
- Rommel Tank (Gauss) “Fightin’ Foxes” – **//^^^^
- Rommel Tank (Gauss) “Rough Riders” – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
1 – Insists on only using their old serial number from their military service.
Phalanx Platoon 1 “Rabbit” Blood Clot Platoon 1 “Tiger” Blood Clot Platoon 6 “Lighthouse”
- Heavy Weapons (28) – ^^(7)^^^(13) - Mixed Infantry (28) – ^^(13)^^^(8) - Mixed Infantry (28) – ^^^^(28/Entire Platoon)
Phalanx Platoon 2 “Snake” Blood Clot Platoon 2 “Hare” Blood Clot Platoon 7 “Barracuda”
- Assault (28) – ^^(11)^^^(9) - Mixed Infantry (28) – ^^(15)^^^(13) - Mixed Infantry (28) – ^^(3)^^^(21)
Phalanx Platoon 3 “Fox” Blood Clot Platoon 3 “Carver” Blood Clot Platoon 8 “Viper”
- Marksman (28) – ^^(3)^^^(1) - Mixed Infantry (28) – ^^(23) - Mixed Infantry (28) – ^^(6)^^^(17)
India Lance
- Bandit Hovercraft (CLAN 2-RS Replica) Ronin Free Companies Mercenaries Ground Forces DropShip Allocation
- Bandit Hovercraft (CLAN 2-RS Replica) – **//^^(2)
- Bandit Hovercraft (CLAN 2-RS Replica) – **
- Bandit Hovercraft (CLAN 2-RS Replica)
Himeji (Fortress-Class DropShip [3058])
– Crippled (Combat Damage), Scuttled Post-Operation
Personnel: 43 Crew, 204 Bay Personnel – 71 Injured, 23 Dead
Dragon Slayers VTOL Company Capacity: 12 ‘Mechs, 12 Heavy Vehicles, 84 Infantry, 353 tons Cargo
- Tanto Light Reaction Reinforced Company (12 ‘Mechs and 12 Vehicles)
Juliet Lance
- Tanto Infantry Company “Phalanx” (84 Infantry)
- Hawk Moth Gunship (Armor) “Busy Bee”
- 350 tons Spare Parts, Munitions, Equipment & Other Supplies (Approximate)
- Hawk Moth Gunship (Armor) “Mega Moth”
- Hawk Moth Gunship (Armor) “Stinger” – **//^^(1)
- Hawk Moth Gunship (Armor) “Toothpick”
Matsumoto (Fortress-Class DropShip [3058—Modified])
Personnel: 43 Crew, 144 Bay Personnel – 19 Injured, 2 Dead
Capacity: 12 ‘Mechs, 12 Heavy Vehicles, 16 Battle Armor, 336 tons Cargo
Oscar Lance
- Tetsubo Assault Reinforced Company (12 ‘Mechs and 12 Vehicles)
- Hawk Moth Gunship (Armor) “Blade” – **//^^(2)
- 35th Infantry Company “Bandits” Cavalier Squads (4 Battle Armor)
- Hawk Moth Gunship (Armor) “Hammer” – **
- 35th Infantry Company “Bandits” Fa Shih Squads (12 Battle Armor)
- Hawk Moth Gunship (Armor) “Anvil” – **//^^(1)
- 330 tons Spare Parts, Munitions, Equipment & Other Supplies (Approximate)
- Hawk Moth Gunship (Armor) “Coal” – ^^(1)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
102nd Provisional Division - Lola III-Class Destroyer – W.O.B.S. Enlightened Glory – ****
- Lola III-Class Destroyer – W.O.B.S. Guiding Hand – ****
“Divinity’s Shield” - Lola III-Class Destroyer – W.O.B.S. Sword of Faith – ****
Black-Water Forces
102nd Provisional Division DropShips
- Overlord-Class DropShip – W.O.B.S. Inviolable Reason – ****
- Overlord-Class DropShip – W.O.B.S. Resolute Devotion – ****
- Overlord-Class DropShip – W.O.B.S. Staunch Resolution – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Gamma Heavy Sniper Level II Armor-One Level II Epsilon Armor-Two Level II Epsilon
- Cerberus MR-6B – **** - Zhukov Heavy Tank (WoB) – **//!!(5) - Beagle Hover Scout (C3i) – ****
- Cerberus MR-6B – **//!! - Zhukov Heavy Tank (WoB) – **** - Beagle Hover Scout (C3i) – **//!!
- Galahad GLH-3D – **** - Zhukov Heavy Tank (WoB) – **** - Galleon Light Tank GAL-103 – ****
- Galahad GLH-3D – **** - Zhukov Heavy Tank (WoB) – **//!!!!(5) - Galleon Light Tank GAL-103 – ****
- Vanquisher VQR-2A – **** - Zhukov Heavy Tank (WoB) – **//!! - Magi Infantry Support Vehicle (UCSV) – ****
- Vanquisher VQR-2A – **//!! - Zhukov Heavy Tank (WoB) – **//^^^(2)!!(3) - Magi Infantry Support Vehicle (UCSV) – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
55th Shadow Division - Sovetskii Soyuz Heavy Cruiser – W.O.B.S. Illuminated Path – ****
- Sovetskii Soyuz Heavy Cruiser – W.O.B.S. Purity of Thought – ****
“Thanatos’ Grip” - Zechetinu-Class Corvette – W.O.B.S. Due Diligence – ****
Black-Water Forces
55th Shadow Division Black-Water DropShips
- Leopard “Pocket WarShip”-Class DropShip – ****
- Leopard “Pocket WarShip”-Class DropShip – ****
- Leopard “Pocket WarShip”-Class DropShip – ****
- Leopard “Pocket WarShip”-Class DropShip – ****
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Battle Armor Level II Twelve-Beta Battle Armor Transport Level II BAT-2 AeroFighter Level II Dog
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Striga S-STR-O Invictus (PRIME) – ****
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Striga S-STR-O Invictus (PRIME) – ****
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Striga S-STR-O Dominus (A) – ****
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Striga S-STR-O Dominus (A) – ****
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Striga S-STR-O Luminos (D) – ****
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Striga S-STR-O Luminos (D) – ****
Battle Armor Level II Twelve-Gamma Battle Armor Transport Level II BAT-3 AeroFighter Level II Echo
- Se’irim Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Invictus (PRIME) – ****
- Se’irim Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Rusalka S-RSL-O Invictus (PRIME) – ****
- Se’irim Medium Battle Armor (Capture) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Comminus (C) – ****
- Se’irim Medium Battle Armor (Capture) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Rusalka S-RSL-O Comminus (C) – ****
- Se’irim Medium Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Luminos (D) – ****
- Se’irim Medium Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Luminos (D) – ****
Battle Armor Level II Twelve-Delta Battle Armor Transport Level II BAT-4 AeroFighter Level II Foxtrot
- Shedu Assault Battle Armor (Capture) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Invictus (PRIME) – ****
- Shedu Assault Battle Armor (Capture) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Invictus (PRIME) – ****
- Shedu Assault Battle Armor (Recon) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//!!(3) - Rusalka S-RSL-O Comminus (C) – ****
- Shedu Assault Battle Armor (Recon) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Comminus (C) – ****
- Shedu Assault Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Luminos (D) – ****
- Shedu Assault Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Rusalka S-RSL-O Luminos (D) – ****
Battle Armor Level II Twelve-Epsilon Battle Armor Transport Level II BAT-5 AeroFighter Level II Golf
- Nephilim Assault Battle Armor (Capture) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Shade S-HA-O Invictus (PRIME) – ****
- Nephilim Assault Battle Armor (Gauss) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Shade S-HA-O Invictus (PRIME) – ****
- Nephilim Assault Battle Armor (Gauss) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Dominus (A) – ****
- Nephilim Assault Battle Armor (NARC) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Dominus (A) – ****
- Nephilim Assault Battle Armor (Seeker) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Shade S-HA-O Infernus (B) – ****
- Nephilim Assault Battle Armor (Support) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Infernus (B) – ****
Battle Armor Level II Twelve-Zeta Battle Armor Transport Level II BAT-6 AeroFighter Level II Hotel
- Tengu Heavy Battle Armor (C3i) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Invictus (PRIME) – ****
- Tengu Heavy Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Invictus (PRIME) – ****
- Tengu Heavy Battle Armor (Standard) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Dominus (A) – ****
- Tengu Heavy Battle Armor (Support) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Dominus (A) – ****
- Tengu Heavy Battle Armor (Support) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **** - Shade S-HA-O Infernus (B) – ****
- Tengu Heavy Battle Armor (Support) (6) – ****(6/Entire Squad) - Maxim Heavy Hover Transport (WoB) – **//^^^^ - Shade S-HA-O Infernus (B) – ****
Support AeroFighter Level II Bravo W.O.B.S. Holy Crusader (Aurora-Class DropShip [Battle Armor]) W.O.B.S. Manifest of Destiny (Overlord-Class DropShip [2762])
- Ahab AHB-MD – **** – Captured (Crippled – Artillery Bombardment), Scuttled Post-Operation – Captured (Taken by the Dreadnought BattleCorps 1st RCT)
- Ahab AHB-MD – **** Personnel: 7 Crew, 184 Bay Personnel – 133 Injured, 27 Dead Personnel: 43 Crew, 28 Marines, 76 Bay Personnel – 71 Injured, 49 Dead
- Ahab AHB-MD – **** Capacity: 96 Battle Armor, 8 Light Vehicles, 148 tons Cargo Capacity: 36 ‘Mechs, 6 AeroFighters, 132.5 tons Cargo
- Ahab AHB-MD – **** - 55th Shadow Division Battle Armor Level IIs Twelve-Gamma/Delta - 55th Shadow Division ‘Mech Level III Three
- Ahab AHB-MD – **** - 55th Shadow Division Battle Armor Transport Level II BAT-3 - 55th Shadow Division AeroFighter Level II Echo
- Ahab AHB-MD – **** - 148 tons Spare Parts, Munitions, Equipment & Supplies - 132.5 tons Spare Parts, Munitions, Equipment & Supplies
W.O.B.S. True Believer (Aurora-Class DropShip [Battle Armor]) W.O.B.S. Opus Blake (Overlord-Class DropShip [2762])
55th Shadow Division Support Battle Armor Groups – Destroyed (Self-Destruction) – Destroyed (Self-Destruction)
Personnel: 7 Crew, 184 Bay Personnel – 191 Dead (No Survivors) Personnel: 43 Crew, 28 Marines, 76 Bay Personnel – 147 Dead (No Survivors)
Support Battle Armor Group I Capacity: 96 Battle Armor, 8 Light Vehicles, 148 tons Cargo Capacity: 36 ‘Mechs, 6 AeroFighters, 132.5 tons Cargo
- Asura Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad) - 55th Shadow Division Battle Armor Level IIs Twelve-Epsilon/Zeta - 55th Shadow Division ‘Mech Level III One
- Asura Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad) - 55th Shadow Division Battle Armor Transport Level II BAT-5 - 55th Shadow Division AeroFighter Level II Charlie
- Asura Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad) - 143 tons Spare Parts, Munitions, Equipment & Supplies - 125 tons Spare Parts, Munitions, Equipment & Supplies (Approximate)
- Asura Medium Battle Armor (Anti-Infantry) (6) – ****(6/Entire Squad)
W.O.B.S. Blake’s Veneration (Fortress-Class DropShip [3058]) W.O.B.S. Virtuous Wrath (Overlord-Class DropShip [2762])
Support Battle Armor Group II – Captured (Taken by the Blackwood Templars Mercenaries) – Captured (Crippled – Artillery Bombardment), Scuttled Post-Operation
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) Personnel: 43 Crew, 204 Bay Personnel – 29 Injured, 19 Dead Personnel: 43 Crew, 28 Marines, 76 Bay Personnel – 19 Injured, 121 Dead
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) Capacity: 12 ‘Mechs, 12 Heavy Vehicles, 84 Infantry, 353 tons Cargo Capacity: 36 ‘Mechs, 6 AeroFighters, 132.5 tons Cargo
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - 55th Shadow Division ‘Mech Level IIs Five-Epsilon/Zeta - 55th Shadow Division ‘Mech Level III Four
- Djinn Light Battle Armor (Stealth) (6) – ****(6/Entire Squad) - 55th Shadow Division Armor Level IIs Nine-Quebec/Romeo - 55th Shadow Division AeroFighter Level II Foxtrot
- 55th Shadow Division Infantry Level IIs Ten-Alpha/Beta - 131 tons Spare Parts, Munitions, Equipment & Supplies
- 352.5 tons Spare Parts, Munitions, Equipment & Supplies
55th Division Ground Forces DropShip Allocation W.O.B.S. Ordination of Duty (Overlord-Two-Class DropShip)
W.O.B.S. Consecrated Faith (Fortress-Class DropShip [3058]) – Captured (Crippled – Artillery Bombardment), Scuttled Post-Operation
W.O.B.S. Exalted Apotheosis (Assault Triumph DropShip [3062]) – Captured (Taken by the Ronin Free Companies Mercenaries) Personnel: 43 Crew, 156 Bay Personnel – 36 Injured, 158 Dead
– Captured (Taken by the Blackwood Templars Mercenaries) Personnel: 43 Crew, 204 Bay Personnel – 67 Injured, 42 Dead Capacity: 24 ‘Mechs, 12 Heavy Vehicles, 6 AeroFighters, 732.5 tons Cargo
Personnel: 12 Crew, 252 Bay Personnel – 119 Injured, 97 Dead Capacity: 12 ‘Mechs, 12 Heavy Vehicles, 84 Infantry, 353 tons Cargo - 55th Shadow Division Battle Armor Transport Level IIs BAT-4
Capacity: 6 ‘Mechs, 24 Heavy Vehicles, 24 Battle Armor, 6 AeroFighters, - 55th Shadow Division ‘Mech Level IIs Six-Epsilon/Zeta - 55th Shadow Division ‘Mech Level IIs Five-Alpha/Beta/Gamma/Delta
854.5 tons Cargo - 55th Shadow Division Armor Level IIs Seven-Echo/Foxtrot - 55th Shadow Division AeroFighter Level II Golf
- 55th Shadow Division Armor Level IIs Seven-Able/Baker/Charlie/Dog - 55th Shadow Division Infantry Level IIs Ten-Gamma/Delta - 700 tons Spare Parts, Munitions, Equipment & Supplies (Approximate)
- 55th Shadow Division Support AeroFighter Level II Able - 349.5 tons Spare Parts, Munitions, Equipment & Supplies
- 55th Shadow Division Support Battle Armor Group I W.O.B.S. Praised Deliverance (Overlord-Two-Class DropShip)
- 852 tons Spare Parts, Munitions, Equipment & Supplies W.O.B.S. Illumination of Piety (Hercules-Class DropShip [3053]) – Destroyed (Self-Destruction)
– Captured (Taken by the Ronin Free Companies Mercenaries) Personnel: 43 Crew, 156 Bay Personnel – 199 Dead (No Survivors)
W.O.B.S. Reverent Adoration (Assault Triumph DropShip [3062]) Personnel: 43 Crew, 204 Bay Personnel – 13 Injured, 207 Dead Capacity: 24 ‘Mechs, 12 Heavy Vehicles, 6 AeroFighters, 732.5 tons Cargo
– Destroyed (Self-Destruction) Capacity: 45 Heavy Vehicles, 336 Infantry, 1,381 tons Cargo - 55th Shadow Division Battle Armor Transport Level IIs BAT-6
Personnel: 12 Crew, 252 Bay Personnel – 267 Dead (No Survivors) - 55th Shadow Division Armor Level III Eight - 55th Shadow Division ‘Mech Level IIs Six-Alpha/Beta/Gamma/Delta
Capacity: 6 ‘Mechs, 24 Heavy Vehicles, 24 Battle Armor, 6 AeroFighters, - 55th Shadow Division Battle Armor Transport Level II BAT-2 - 55th Shadow Division AeroFighter Level II Hotel
854.5 tons Cargo - 55th Shadow Division Infantry Level IIs Ten-Epsilon/Zeta - 720 tons Spare Parts, Munitions, Equipment & Supplies (Approximate)
- 55th Shadow Division Armor Level IIs Nine-Mike/November/Oscar/Papa - 55th Shadow Division Infantry Level III Eleven
- 1,371.5 tons Spare Parts, Munitions, Equipment & Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
- 55th Shadow Division Support AeroFighter Level II Bravo ** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
- 55th Shadow Division Support Battle Armor Group II Supplies
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
- 850 tons Spare Parts, Munitions, Equipment & Supplies (Approximate) **** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
!! Pilot/Crew Captured; !!!! Pilot/Crew Status Unconfirmed
Asher Lance
- Heavy LRM Carrier (SRM Refit) – ***//^^(3)^^^(2)
- Heavy LRM Carrier (SRM Refit) – **
- Heavy LRM Carrier (SRM Refit) – ****
- Heavy LRM Carrier (SRM Refit) – **//^^(2)
Badger Lance
- Heavy LRM Carrier (SRM Refit) – **** +
- Heavy LRM Carrier (SRM Refit) – **
- Heavy LRM Carrier (SRM Refit) – **** +
- Heavy LRM Carrier (SRM Refit) – **** +
Chipper Lance
- Goblin Medium Tank (SRM) – **//^^^^ +
- Goblin Medium Tank (SRM) – **** +
- Goblin Medium Tank (SRM) – **** +
- Heavy LRM Carrier (SRM Refit) – **** +
Digger Lance
- Bulldog Main Battle Tank (Standard) – **//^^(1)
- Bulldog Main Battle Tank (Standard) – ****
- Vedette Medium Battle Tank (Standard) – ***//^^(2)^^^(2)
- Vedette Medium Battle Tank (Standard) – **
Exeter Lance
- Hetzer Medium Combat Vehicle (AC20) – **//^^(3)
- Hetzer Medium Combat Vehicle (AC20) – **//^^(1)
- Hetzer Medium Combat Vehicle (AC20) – ****
- Hetzer Medium Combat Vehicle (AC20) – **
Flicker Lance
- Ferret Light Scout VTOL – ****
- Ferret Light Scout VTOL – ****
- Ferret Light Scout VTOL – ***//^^(1)
- Ferret Light Scout VTOL – ****
Gopher Lance
- Ballista Self-Propelled Artillery Tank – ***//^^(1)
- Ballista Self-Propelled Artillery Tank – **** +
- Ballista Self-Propelled Artillery Tank (Nonfunctional) – **//^^(3)
Legend: Post-LANCASTER Status of Unit (‘Mech, Vehicle, etc.) (Asterisks) // Status of Pilot or Crew Member(s) (Chevrons)
** Unit Severely Damaged/Crippled; *** Unit Destroyed (Pilot/Crew Uninjured unless noted otherwise)
^^ Pilot/Crew Member Injured; ^^^ Pilot/Crew Member Killed; ^^^^ Entire Crew/Squad Killed
**** Total Loss (Machine(s) Destroyed, All Associated Personnel/Crew Killed)
+ Vehicles damaged or destroyed during betrayal by Chipper Lance
Dreadnought Interstellar Industries has been a trusted name in the civilian vehicle market for centuries. The manufacturer has produced machines that are considered benchmarks for both the
private and commercial sectors since the early 26th Century. From the Oxen Heavy Hauler’s reputation as a reliable and capable commercial ground transport to the impressive performance of the
Successor Armored Supercar and the newer Vector-series sport vehicles, the iconic “Dragon’s Head” has proven itself to be an industry leader time and again.
100 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
VECTOR STORM VI HIGH PERFORMANCE MOTORCYCLE
Variants broken, thanks to regulation changes since his retirement and the damage
inflicted by the Word of Blake during their attack on Solaris VII in 3068.
Storm IV (ICE) – Introduced in 3015, this entry-level variant of the Vector
Storm features a Class-10 Internal Combustion Engine for a top speed of 248 The last motorcycle to be raced by Munro has been kept on display in the
km/h. This motorcycle weighs 326 kilograms, and costs 2,034 C-Bills. The Dreadnought Interstellar headquarters building on Acala III. This particular
Vector Storm IV also lacks the active aerodynamic and gyro-stabilization motorcycle features a unique livery that was hand-painted by Munro himself
systems of the higher trim levels. (Battle Value: 8) as an homage to an ancient, animated movie from pre-space-flight Terra.
This motorcycle is also the one that Munro rode to his sixth-and-final rider’s
Storm V (Fuel Cell) – A step up from the Storm IV, the Vector Storm V was championship, having collected enough points to clinch the championship
introduced in 3021. It features a Fuel Cell Engine and weighs 327 kilograms. despite not competing in the last three of the twelve races due to his stroke.
While the fuel range is significantly reduced versus the internal combustion A reproduction wrap of this famous livery is available as a factory option.
engine of the Storm IV, the Storm V boasts a top speed exceeding 291 km/h.
At 2,802 C-Bills, this model is often the choice for motorcycle enthusiasts Munro was critical to the development of the competition motorcycles
who want improved off-the-shelf performance but do not wish to pay the used by the Dreadnought Interstellar Racing Team. Dreadnought went on to
full price of the fusion-powered Vector Storm VI. (Battle Value: 8) win two more constructors’ championship titles thanks to Munro’s
contributions toward perfecting the seemingly invincible Vector Storm VII.
Storm VII (Supercharged Fusion) – The absurdly powerful and obscenely Over the five decades of their involvement in the sport, the Dreadnought
Mass: 381 kg high-speed option package for the Storm VI, introduced in 3060, is the Vector Interstellar Racing Team has claimed sixteen manufacturers championships,
Movement Type: Wheeled Storm VII. Visually identical to the Storm VI for homologation purposes, this nine of which came as a direct result of Munro’s contributions to the team.
Power Plant: Orbital Heavy Industries OHI-10F Type A Fusion Engine rare and expensive option package was developed by the Dreadnought
Cruising Speed: 226.8 km/h Interstellar Racing Team for competition on Solaris VII. This motorcycle is not It is believed that when the Word of Blake struck Solaris VII in 3068, the
Flanking Speed: 345.6 km/h for the faint of heart. The Storm VII weighs 407 kilograms, marking it as the destruction caused to the racing circuits and infrastructure for the series was
Armor: Vector-Series Ultralight-HMB BAR 2 heaviest of the breed. The boosted top speed of this motorcycle, well in too much for Munro to handle. He died peacefully in his sleep the night after
Armament & Equipment: excess of 450 km/h, while impressive, is essentially irrelevant, as it will never the announcement had been made that the racing series had been cancelled
None be reached during competition. Early rumors suggested that the Storm VII indefinitely because of the attack. The Solaris VII HyperBike Championship
Manufacturer: Dreadnought Interstellar Industries would cost 100,000 C-Bills new, which drew a strong buzz—both positive and has yet to recover from the attack, but local racing championships using
Primary Factory: Dreadnought Vehicle Manufacturing Complex; Acala III negative—in the mainstream media, leading to most considering the temporary circuits on airfields and even spaceports have been popular on
Communications System: InterComm Type 8S Sport machine to be far too expensive to be worth even considering for anything numerous worlds for centuries. Some worlds even have permanent circuits
Navigation and Tracking System: SporTrack GPS PinPoint Version-IV other than racing. However, when the HyperBike Competition Spec Vector established for multiple forms of motorsport, but these are only typical of
Storm VII hit the open market, it turned out to cost just 7.4 thousand C-Bills— wealthier planets.
Overview plus dealer markup, which at first was extreme. This eventually calmed down
once Dreadnought Interstellar Industries put their foot down and made it
The Vector Storm VI is a fusion-powered model of the Vector Storm series clear that any dealership that was caught marking the bike up more than Type: Vector Storm VI (Fusion) High Performance Motorcycle
of sport motorcycles manufactured by Dreadnought Interstellar Industries. twenty-five percent would be cut off from the manufacturer altogether. Classification: Civilian Sport Motorcycle (Mass Production)
The premium-level Vector Storm V and VI include state-of-the-art active Technology Base: Inner Sphere (Support Vehicle)
suspension systems and chassis aerodynamics, a gyroscopic roll-stabilization For the teams looking to win the racing series that the Vector Storm VII Equipment Rating: D/X-E-D-D
system, and a suite of extremely intelligent, customizable computerized was built for, the absurd acceleration of the Supercharged OHI-10F/SC Type Tonnage: 381 kg
control systems that seamlessly improve both the riding experience and B Fusion Engine, in conjunction with the highly advanced active chassis, Battle Value: 9
overall performance. made this machine the “king of the hill” for the top level 400-450-kilogram Notes: Features Ultra-Light and Bicycle chassis modifications.
class of the Solaris VII HyperBike Championship Racing Series. Should the
The successful fuel-cell-powered Vector Storm V brought much attention HyperBike Championship Racing Series ever be reestablished, Dreadnought Equipment Mass (kg)
to the Dreadnought-branded sport motorcycle in the early-to-mid 31st Interstellar Industries has promised to return with their famous factory- Chassis/Controls: 87
Century, and the Storm VI’s newer Micro Fusion Engine was a remarkable backed Dreadnought Interstellar Racing Team. (Battle Value: 9) Engine: 10 Fusion 250
step up in terms of performance and range. The most significant downside Type: Wheeled (Small/Support)
of the Fusion model was that the powerplant increased the overall weight of Notable Riders Cruising MP: 21
the machine by roughly twenty percent over previous models. At 4,788 C- Flanking MP: 32
Bills, the Storm VI is also nearly twice as expensive as its predecessor. Most Bart Munro – Vector Storm VII: The famous six-times Solaris VII HyperBike Heat Sinks: 0 0
consider the performance to be worth the cost of entry, however. Champion himself. Munro was known for two things in his life: his absurd Fuel: 0
speed on the track, and his eccentric personality. A truly kindhearted man, Armor Factor (BAR 2): 4 44
Capabilities he was almost oblivious to the ills of society around him. The only things that Internal Armor
ever mattered to him were speed and racing, and he made his impact on the Structure Value
The Vector Storm VI was Introduced in 3033 to much critical acclaim. The history books thanks to his single-minded devotion to motorsport. Front 1 1
Storm VI is powered by a proprietary Orbital Heavy Industries Fusion Engine, R/L Side 1 1
and it is virtually unrivalled in the production motorcycle market in terms of Unfortunately, Munro’s career in racing came to an abrupt halt after he Rear 1 1
raw performance. Between its remarkable stability and agility even when suffered a stroke in 3065, losing much of his bodily coordination. Later
approaching its astonishing top speed of nearly 350 km/h, the Vector Storm passing away from natural causes, he is remembered for his part in helping Cargo & Other Equipment Location Mass (kg)
VI is an already amazing performance motorcycle that has only become more the Solaris VII HyperBike Championship Racing Series thrive in the 3050s and None – –
impressive with seamless improvements made yearly since its introduction. 3060s. He still holds several track lap records that are likely to never be
Type: Foundation Utility Truck (ICE) Type: Foundation Utility Truck (Deluxe Package) Type: Foundation Utility Truck (Military)
Classification: Civilian Utility Vehicle (Mass Production) Classification: Civilian Utility Vehicle (Mass Production) Classification: Military Armored Light Utility Vehicle (Mass Production)
Technology Base: Inner Sphere (Support Vehicle) Technology Base: Inner Sphere (Support Vehicle) Technology Base: Inner Sphere
Equipment Rating: D/C-C-C-B Equipment Rating: E/C-E-D-C Tonnage: 10
Tonnage: 10 Tonnage: 10 Battle Value: 106
Battle Value: 34 Battle Value: 40 Notes: Features the following Design Quirks: Rugged, Trailer Hitch.
Notes: Features the following Design Quirks: Trailer Hitch. Notes: Features Dune Buggy chassis modification, Environmental Sealing
special equipment, and the following Design Quirks: Rugged, Trailer Hitch. Equipment Mass
Equipment Mass Internal Structure: 1
Chassis/Controls: 1.725 Equipment Mass Engine: 60 Fusion 2.5
Engine: 40 ICE 4.5 Chassis/Controls: 1.725 Type: Wheeled
Type: Wheeled Engine: 50 Fusion 3 Cruising MP: 8
Cruising MP: 6 Type: Wheeled Flanking MP: 12
Flanking MP: 9 Cruising MP: 7 Heat Sinks: 10 0
Heat Sinks: 0 0 Flanking MP: 11 Control Equipment: 0.5
Fuel: 0.5 Heat Sinks: 0 0 Armor Factor (Standard): 32 2
Armor Factor (BAR 7): 11 0.5 Armor Factor (BAR 8): 11 0.5 Internal Armor
Internal Armor Internal Armor Structure Value
Structure Value Structure Value Front 1 9
Front 1 3 Front 1 3 R/L Side 1 8
R/L Side 1 3 R/L Side 1 3 Rear 1 7
Rear 1 2 Rear 1 2
Cargo & Other Equipment Location Tonnage
Cargo & Other Equipment Location Tonnage Cargo & Other Equipment Location Tonnage Cargo Body 4
Cargo Body 2.5 Cargo Body 2 Trailer Hitch Rear –
Trailer Hitch Rear – Trailer Hitch Rear –
Environmental Sealing – 1.5
The rugged and easily serviced 300-rated Shipil Fusion Engines used in the Fuel Cell – In 2573, a new civilian-grade variant of the Oxen Heavy Hauler
Oxen Heavy Hauler since the first of the fusion-powered examples rolled off was introduced to satisfy the market’s demand for a more powerful, reliable,
Mass: 40 tons (tractor; up to 80 tons w/Trailer) the assembly lines in 2525 has remained largely unchanged for 535 years of long-range, and—most importantly—still affordable transport vehicle. What
Movement Type: Wheeled continuous production. However, Dreadnought Interstellar Industries finally Dreadnought Interstellar did to satisfy these criteria was to introduce an all-
Power Plant: Cyclops PowerPull 260 (ICE); ceased outsourcing the Oxen’s Fusion Engines to Shipil Company in 3060, new Fuel Cell powerplant. While still priced a full hundred-thousand C-Bills
Shipil 300 Fusion Engine or Orbital Heavy Industries OHI-300F instead turning to its partner company, Orbital Heavy Industries, for their below the price of the fusion-powered unit, at 340,843 C-Bills, the Fuel Cell
Standard Fusion Engine (Fusion) new series of Fusion Engines. The move to OHI-produced Fusion Engines Oxen delivers the same performance as the Fusion unit with an estimated
Cruising Speed: 75.6 km/h (ICE); 86.4 km/h (Fusion) granted Dreadnought a noticeably improved profit margin while producing maximum range of 1,300 kilometers between fill-ups. The only downside is
Flanking Speed: 118.8 km/h (ICE); 129.6 km/h (Fusion) an even more rugged and durable vehicle than had been possible prior to the reduced internal cargo space, as the four-ton fuel tank necessitates the
Loaded Flanking Speed (Max. Load): 54.0 km/h (w/40-ton trailer [ICE]); switch. Today, all three versions of the Oxen Heavy Haulers have become so reduction of cargo capacity to just two tons. (Battle Value: 174) Features
64.8 km/h (w/40-ton trailer [Fusion]) common in the Inner Sphere that they are some of the easiest ground-based Armored Chassis and Tractor chassis modifications, as well as the following
Armor: Dreadnought Interstellar BAR-10 Commercial Vehicular Armor commercial transport vehicles ever made to find parts for. Design Quirks: Ubiquitous; Poor Performance (when towing).
Armament & Equipment:
None Capabilities Related Equipment
Manufacturer: Dreadnought Interstellar Industries
Primary Factory: Dreadnought Heavy Iron Works Facility; Skye (Skye IV) With its powerful 300-rated Fusion Engine, the forty-ton Oxen Heavy Standard Cargo Trailer – The most common civilian sector trailer used with
Communications System: InterComm Type 6C Commercial Hauler can tow a trailer of equal weight at speeds exceeding 60 km/h near- the Oxen Heavy Hauler is the standard “box” cargo trailer. The armored shell
Navigation and Tracking System: Pinpoint Commercial Adaptive GPS effortlessly. With power being delivered to all four of its axles and equipped of the box is comparable to the civilian variant Oxen Heavy Hauler, but it is
with a chassis designed to handle both tarmac and off-road surfaces, the otherwise just a featureless box trailer classified as having a rated maximum
Overview Oxen is seemingly unstoppable in most conditions. The standard civilian loaded weight of 40 tons. This hollow, enclosed trailer has a 30-ton cargo
issue Oxen is protected by 2.5 tons of Dreadnought Interstellar Industries’ capacity and is typically equipped with a simple rear door. (Battle Value: 110)
Dreadnought Interstellar Industries’ Oxen Heavy Hauler is a general- own BAR-10-rated Commercial Vehicular Armor, which was developed in Features Armored Chassis and Trailer chassis modifications, as well as the
purpose commercial transport vehicle that has been in production in one 2503 specifically for the Oxen. As of 3085, this appears to be the only vehicle following Design Quirks: Easy to Maintain, Rugged, Ubiquitous.
form or another since the establishment of the Dreadnought Heavy Iron using this armor type—as even the militarized versions use entirely different
Works Facility on the world of Skye in 2505. While it has undergone modest armor—but it has remained the only type of armor that the civilian sector Standard Salvage Trailer – The second most ubiquitous trailer for the Oxen
aesthetic and mechanical improvements over the years, the Oxen has Oxen has ever been produced with. This vehicle features a sleeper cab and Heavy Hauler—aside from simple flatbed trailers—is a modified flatbed that
remained relatively unchanged over the vehicle’s centuries of production. can be equipped with any number of creature comforts to make it far more features a simple crane, installed at the front of the trailer, for cargo loading
pleasant to operate for extended periods. The fusion-powered variant of the and unloading. It is generally equipped with stabilizer legs that extend out
Initially produced exclusively with an internal combustion engine that Oxen also features a full six tons of onboard cargo capacity. from the sides of the trailer and typically features ramps that either fold
slowly gained notoriety for being sometimes difficult to maintain, the Oxen down or extend out of the back, allowing salvaged vehicles to be unloaded
received an upgraded Fusion Engine variant in 2525. The new powerplant Variants by simply rolling them off the trailer. Unlike the standard “box” cargo trailer,
was more powerful, easier to service, and nearly maintenance-free. This the Salvage Trailer has a small internal powerplant, allowing it to operate
upgrade was also considerably more expensive. Still in production today, the ICE – Introduced in 2505, discontinued in 2584, and then reintroduced with even when disconnected from the tractor. This trailer has a total of 24.5 tons
original internal combustion engine variant of the Oxen costs less than a more dependable powerplant in 2593, the original Oxen Heavy Hauler was of cargo capacity in fusion-powered form and 23.5 tons in ICE-powered
300,000 C-Bills, while the fusion-powered version is a full 433,000 C-Bills. powered by a 260-rated (Tech E) PowerPull Internal Combustion Engine. This form—the latter of which is equipped with a half-ton fuel tank. (Battle Value:
variant of the Oxen had a top speed exceeding 118 km/h unloaded but could 129) Features Armored Chassis and Trailer chassis modifications, as well as
Later, to offer a machine that would slot into the market between the only reach 54 km/h when towing a fully loaded 40-ton trailer. This vehicle the following Design Quirks: Rugged, Ubiquitous.
other engine options, a fuel-cell-powered variant was created. It had nearly features an onboard three-ton cargo bay and 2.5-ton fuel tank, providing the
the same range on a single tank as the first-generation conventional internal vehicle with an estimated 1,190-kilometers of range between fill-ups. The Military-Grade Trailers – Naturally, military-grade versions of both above
Type: Oxen Heavy Hauler (Tractor – Military) Type: Military Cargo Trailer Type: Military Salvage Trailer
Classification: Military Transport Tractor (Mass Production) Classification: Military Trailer (Mass Production) Classification: Military Salvage Trailer (Mass Production)
Technology Base: Inner Sphere Technology Base: Inner Sphere Technology Base: Inner Sphere
Tonnage: 40 Tonnage: 40 Tonnage: 40
Battle Value: 266 Battle Value: 174 Battle Value: 211
Notes: Features the following Design Quirks: Easy to Maintain, Rugged Notes: Features Trailer chassis modification, as well as the following Design Notes: Features Trailer chassis modification, as well as the following Design
(3060+), Trailer Hitch, Ubiquitous; Poor Performance (when towing). Quirks: Easy to Maintain, Rugged, Ubiquitous. Quirks: Rugged, Ubiquitous.
During the latter half of the massive megacorporation’s thousand years of history, Dreadnought Interstellar Industries has produced several different BattleMech types for export across the Inner
Sphere. Many of these designs are well known and have been used by various militaries, ranging from the armies of the Great Houses to smaller, independent mercenary units. Some of these
machines have even been in continuous production since before the fall of the Star League.
117 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
DII-GDM-1 GUARDSMAN LIGHT BATTLEMECH
This relatively simple light BattleMech was created to serve as a bridge ExtraLight Fusion Engine for a top speed exceeding 160 km/h. It is protected
between the cost-effectiveness of the UrbanMech and the mobility of the by four tons of Dreadnought TitanPlate Standard Armor. This nimble ‘Mech
Stinger BattleMech. The hope had been that the cost of this machine would is notorious for its extremely thin rear armor, even for its weight class.
be somewhere in the middle of the two, but unfortunately the final product
proved to be more expensive than either. However, at 1.7 million C-Bills, the The Ravage Light BattleMech is armed with six ChisComp 39 Medium
price has generally been easy for most militias to justify. Lasers—three in each side torso—and a single center-torso-mounted Zippo
Flamer. With twenty double heat sinks, the cooling system of the Ravage is
The Guardsman proved to be more durable and more heavily armed than vastly superior when compared to the original Guardsman. While a relatively
a Stinger, and nearly as fast as the lighter ‘Mech. While the Guardsman rare sight—all the rarer since many of them were destroyed during the Clan
lacked the singular heavy-hitting punch of the UrbanMech’s Autocannon, the Invasion—the Ravage BattleMech has been noted to still be in active use in
clustered weapons in the Guardsman’s torso, as well as fully articulated arms various militaries across the Inner Sphere. (Battle Value: 993) Features the
and much higher mobility, granted considerably greater versatility. Even if its following Design Quirks: Narrow/Low Profile; Weak Legs.
weapons operate at a shorter range, the Guardsman can easily overcome
this deficiency with its ability to rapidly close into range with a target. DII-RVG-O Ravage & DII-RVG-2-O Ravage II – The descendent OmniMechs
created exclusively for use by Dreadnought’s BattleCorps and DefenseCorps.
Serviceability proved to be a bonus for the buyers of this machine, as the These are considered the ultimate evolution of the Guardsman’s design.
mechanical simplicity of the Guardsman quickly gained the BattleMech
considerable favor with technicians and maintenance budgets alike.
Type: Guardsman (DII-GDM-1)
Capabilities Classification: Light BattleMech (Mass Production
Technology Base: Inner Sphere
Powered by a reliable and easily maintained Defiance 125-rated Fusion Tonnage: 25
Engine, the Guardsman is capable of a top speed of 86 km/h. The Guardsman Battle Value: 609
is also jump capable—unlike the later Ravage based on it—and its five torso- Notes: Features the following Design Quirks: Easy to Maintain, Easy to Pilot,
mounted jump jets give it a 150-meter jump range for quick relocation. Narrow/Low Profile, Rugged, Ubiquitous; Cooling System Flaws, Weak Head
Armor (2), Weak Legs. Arm Actuators: Lower & Hand (Right & Left).
The Guardsman is armed with two Defiance B3M Medium Lasers and four
Kicker Machine Guns, providing it an effective mix of both antimateriel and Equipment Mass
Mass: 25 tons antipersonnel firepower. The Guardsman is built on the easily serviced GDM- Internal Structure: Standard 2.5
Chassis: Dreadnought Dura-Frame Standard GDM-25/43S 25/43S Standard Chassis platform, and its 5.5-ton shell of ArcShield Light Engine: 125 Fusion 4
Power Plant: Defiance 125 Fusion Engine MkII Standard Armor provides acceptable protection for a light BattleMech. Walking MP: 5
Cruising Speed: 54.0 km/h The Guardsman is cooled by just eleven single heat sinks. Although this is Running MP: 8
Maximum Speed: 86.4 km/h normally sufficient—even when the ‘Mech is being pushed to its limits— Jumping MP: 5 2.5
Jump Jets: Rawlings Model 52 flaws in the cooling system have been reported to result in occasional Heat Sinks (Single): 11 1
Jump Capacity: 150 meters spontaneous heat spikes if the chassis is exposed to sudden stresses or a Gyro: Standard 2
Armor: GDM-Pattern ArcShield Light MkII Standard Armor heavy impact. Cockpit: Standard 3
Armament & Equipment: Armor Factor (Standard): 88 5.5
2 B3M Medium Lasers Additional Information Internal Armor
4 Kicker Machine Guns Structure Value
Manufacturer: Dreadnought Interstellar Industries A common sight in militias and low-budget mercenary outfits alike, the Head 3 9
Primary Factory: Skye Heavy Iron Works Facility; Skye (Skye IV) Guardsman is ubiquitous across the entire Inner Sphere and Periphery States Center Torso 8 12
Communications System: Cyclops SkyeComm Able alike as a patrol and general-purpose light BattleMech. This ‘Mech has also Center Torso (rear) 3
Targeting & Tracking System: Pinpoint Version-I proven to be a popular choice among pirates in the Periphery, no doubt due R/L Torso 6 9
to its easy service and simple construction. Interestingly, as was discovered R/L Torso (rear) 3
Overview during the Dreadnought BattleCorps’ time spent in Clan space following R/L Arm 4 8
Operation BULLDOG, this machine does not appear to have been among the R/L Leg 6 12
Dreadnought Interstellar Industries’ Guardsman Light BattleMech was ‘Mechs taken with Kerensky’s Exodus Fleet, as no Guardsman BattleMechs
designed from the ground up as an affordable machine for use primarily by have ever been recorded in the history of the Clans. Weapons and Ammo Location Critical Tonnage
militias and smaller-budgeted militaries. Inspired in part by the popularity of Jump Jet CT 1 –
Orguss Industries’ UrbanMech but seeing the potential for a machine that Related Designs Ammo (MG) 100 CT 1 0.5
had more overall combat flexibility in a similar price bracket, the Guardsman Medium Laser RT 1 1
development project began in 2681. DII-RVG-X1 Ravage – The Ravage BattleMech was the first ‘Mech to be given 2 Machine Guns RT 2 1
the Ravage name, but it could just as easily be referred to as the “Guardsman 3 Heat Sinks RT 3 –
Due to the limitations of a relatively small budget and an equally small II”, as that was the development name for this machine. The DII-RVG-X1 was 2 Jump Jets RT 2 –
development team allocated to the project, it was not until 2698 that the produced in 3052-3055, with just over six hundred examples ever built. Medium Laser LT 1 1
first production Guardsman began walking off the assembly lines. The 2 Machine Guns LT 2 1
production of this ‘Mech has been nearly uninterrupted since then, without This 25-ton ‘Mech is based on the RVG-25/43E Endo Steel Chassis co- 3 Heat Sinks RT 3 –
a single known standardized alternate variant ever having been introduced. developed by Orbital Heavy Industries, and powered by a 250-rated Magna 2 Jump Jets LT 2 –
The original specifications for the Dorgas were destroyed in 2895 during Additional Information
the Draconis Combine’s assault on the world of Skye. The damage dealt to
Dreadnought Interstellar’s Skye Heavy Iron Works Facility included a total Few Star-League-era Dorgas BattleMechs remain in active use in their
loss of some of Dreadnought’s data libraries, where the information on the original specifications today, and those examples are scattered across known
‘Mech had been kept despite the technology to produce it being absent in space. Most of these appear to be in the service of higher-profile Great
the Inner Sphere for decades. The destruction of this valuable information House military units. The only other known examples are independently
effectively eliminated the ability to produce replacement parts for the owned in well-off mercenary units—and even then, they are often in poor
‘Mech, as the section of the facility that housed the construction jigs for said condition, or have been refitted or jury-rigged with different weapons and
parts had been destroyed, along with the Kodiak Heavy Tank production line. engines. The newer production run allowed the Dorgas to be reintroduced
This event proved to be the final straw for the Dorgas, and the ‘Mech was primarily to the militaries of Houses Steiner and Davion during the Word of
rendered effectively obsolete after 2895. Blake Jihad. However, increasingly frequent sightings of the ‘Mech have
begun to occur in front-line forces elsewhere.
The production information for the Dorgas had been believed lost forever.
Mass: 50 tons However, just eleven years before the Kuritan attack, a complete library of Variants
Chassis: E22 Endo Steel DGS-50/83E technical specifications and detailed manufacturing information for the
Power Plant: Lockheed 300 ExtraLight Fusion Engine Dorgas (among many others), as well as a handful of intact examples of the DII-DGS-S2 – Having entered production in 2674, just one year after the
Cruising Speed: 64.8 km/h ‘Mech, had been taken with the SLDF’s Exodus Fleet when they left the Inner introduction of the original -S1 Dorgas, the -S2 variant was designed to
Maximum Speed: 97.2 km/h Sphere in 2784. In 3060, when the Dreadnought BattleCorps 1st Regimental provide improved versatility over the original. The -S2 removes the Gauss
Jump Jets: Rawlings Model 55 Combat Team took possession of the Clan Smoke Jaguar world of Pantheress Rifle and associated ammunition to directly replace it with an LB 20-X
Jump Capacity: 270 meters VI, they learned that the Clans had copies of everything that had been feared Autocannon and two tons of ammunition. It also adds a Beagle Active Probe
Armor: DGS-Pattern ArcShield V Standard Armor lost. Not only was there a fully intact original DII-DGS-S1 Dorgas found in the in the left torso as well as a TAG designator in the right torso. Given the
Armament & Equipment: possession of the Smoke Jaguars on Pantheress, but all of the information explosive nature of the Autocannon ammunition, CASE is installed in the left
1 M-7 Gauss Rifle necessary to produce the ‘Mech was discovered along with it. torso. One additional single heat sink is installed in the -S2’s ExtraLight Fusion
1 Omicron 3000 Medium Laser Engine for a total of eleven, making the -S2 Dorgas perfectly heat-efficient.
1 Guardian Electronic Countermeasures Suite In addition to the library of data and the intact original SLDF-era machine, Unfortunately, in the minds of most, the more advanced electronics of the
Manufacturer: Dreadnought Interstellar Industries two related BattleMechs were soon discovered on Pantheress. The first was -S2 do not make up for the range limitations of its main gun when compared
Primary Factory: Skye Heavy Iron Works Facility; Skye (Skye IV) a Clan-tech-augmented variant of the Dorgas, designated the Dorgas C. The to the original -S1’s Gauss Rifle. (Battle Value: 1,194) Features the following
Communications System: Cyclops SkyeComm Bravo second machine turned out to be an abandoned prototype Dorgas IIC, or Design Quirks: Cowl, Directional Torso Mount (RT), Narrow/Low Profile;
Targeting & Tracking System: Pinpoint Version-I Dorgas “Mark-2 Clan”. The derelict Dorgas IIC Prototype had been partially No/Minimal Arms, Obsolete (2895-3073), Weak Head Armor (1), Weak Legs.
stripped for parts and left to gather dust for nearly a century as an empty
Overview shell. Unfortunately for the prototype, it had failed to improve sufficiently Dorgas C – This upgraded variant of the Dorgas was developed by Clan
over the Dorgas C to warrant producing it as an all-new BattleMech type. Mongoose and introduced in 2863. In 2888, Clan Smoke Jaguar emerged
Nearly four centuries before the introduction of lighter ‘Mechs such as victorious after a Trial of Possession over the rights to produce the upgraded
Coventry Metal Works’ Hollander or Clan Wolf-In-Exile’s Pack Hunter, the Production of a new variant of the Dorgas commenced in 3073 on Acala version of the venerable Star League BattleMech. A more advanced upgrade
Dorgas Medium BattleMech was created to fulfill the role of a fast-moving, III, at Dreadnought Interstellar Industries’ MechFoundry. Though the new than most “C” variants, the Dorgas C blurs the line between a “C” and a “IIC”,
hit-and-run sniper. Although other variants have been introduced as “follow- machine was given the chassis code of DII-DGS-D1, the -D1 is a nearly as the former generally uses the exact chassis as originally produced and just
ups” to the original DII-DGS-S1, few have proven as iconic as the original identical reproduction of the Star-League-era -S1 variant, though the newer upgrades it with newer Clan weapons, while the latter of which is typically
variant and its deadly M-7 Gauss Rifle. machine does feature a handful of seamless upgrades. an all-new machine from the ground up.
The first-generation Dorgas BattleMech began production on the planet Capabilities The Dorgas C utilizes replicas of the original E22 Endo Steel DGS chassis,
of Skye in 2673, at Dreadnought Interstellar Industries’ own Skye Heavy Iron ArcShield V Standard Armor, Rawlings 55-Series Jump Jets and Cyclops
Works. It was a state-of-the-art BattleMech for its time. As this machine was The DII-DGS-S1 Dorgas Medium BattleMech features a Star-League-era SkyeComm Bravo communications system, exactly as the original DII-DGS-S1
primarily intended for use by House Steiner’s Lyran Commonwealth military, E22-series Endo Steel chassis and is sheathed in nine tons of standard armor. Dorgas did. Much of the rest of the ‘Mech has been directly upgraded using
the Dorgas was given the chassis code DII-DGS-S1—however, it soon became Built almost entirely around its primary armament of a single M-7 Gauss recently developed technology. The ExtraLight Fusion Engine, Guardian ECM
a favorite among Star League Defense Force (SLDF) troops. Although the Rifle, the same found in the famous and coveted HGN-732b Highlander, the Suite, and Gauss Rifle have all been directly upgraded to Clan-tech units, and
Dorgas was considered an exceptional ‘Mech for its era, this machine’s Dorgas can deliver a deadly strike from long range. The Gauss Rifle is fed by the original head-mounted Medium Laser has been upgraded to a Clan-tech
production numbers were somewhat limited, as it was also rather costly for two tons of ammunition. As a backup weapon, the Dorgas is armed with a Extended Range unit. The aging Pinpoint Version-I targeting & tracking
a fifty-ton BattleMech. This high cost stemmed largely from its massive head-mounted Omicron 3000 Medium Laser. system has been replaced with an advanced Tri-Sight 43 Targeting Computer,
Equipment Mass
Internal Structure: Endo Steel 2.5
Engine: 300 Fusion 19
Walking MP: 6
Running MP: 9
Jumping MP: 6 3
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 168 10.5
Internal Armor
Structure Value
Head 3 9
Center Torso 16 24
Center Torso (rear) 7
R/L Torso 12 19
R/L Torso (rear) 5
R/L Arm 8 16
R/L Leg 12 24
Equipment Mass
Internal Structure: Endo Steel 2.5
Engine: 250 Light Fusion 9.5
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 161 9
Internal Armor
Structure Value
Head 3 9
Center Torso 16 24
Center Torso (rear) 6
R/L Torso 12 19
R/L Torso (rear) 5
R/L Arm 8 16
R/L Leg 12 21
In 3044, Dreadnought Interstellar Industries representatives negotiated The Taurian-produced versions of the Oryx can be found in various forms
for the rights to produce the ‘Mech for the open market, allowing the Oryx across the Taurian Concordat, Capellan Confederation, and Free Worlds
to finally be sold across the entire Inner Sphere. Dreadnought’s first new League. Additional examples have been spotted among the holdings of the
Mass: 60 tons variant, the DII-OX-1G, was rolling off the massive assembly lines of Magistracy of Canopus and Aurigan Reach. The Dreadnought Interstellar
Chassis: Orbital Heavy Industries Sphere Spec Endo Steel OX-60/99E w/CASE Dreadnought Interstellar’s MechFoundry on Acala III by 3047. Demand for variants are common in garrison forces of the poor- to middle-class worlds
Power Plant: Magna 240 Fusion Engine the ‘Mech later proved to be so great that it also began to be produced by within all the Successor States. The Oryx is also popular among mercenary
Cruising Speed: 43.2 km/h Dreadnought’s Skye Heavy Iron Works Facility. The -1G continued to be units, regardless of manufacturer. Some mercenary outfits pick up examples
Maximum Speed: 64.8 km/h produced without any significant modification or upgrade for another eleven of this ‘Mech because it is cost-effective, while others looking to put up the
Jump Jets: Rawlings 60 years before a second Dreadnought-produced variant began production in appearance of being better-financed and better-equipped than they actually
Jump Capacity: 90 meters 3058. This second-generation Oryx was designated, rather predictably, the are by having a brand-new ‘Mech or two to show to their potential clients.
Armor: OX-Pattern Dreadnought Heavy Titan-Plate Standard Armor DII-OX-2G. The -2G rapidly became just as popular as its predecessor.
Armament & Equipment: Development of the Oryx by both Taurus Territorial and Dreadnought Variants
2 Defiance Shredder LB 2-X Autocannons Interstellar Industries has been ongoing since, with new variants being
2 Defiance Model XII Extended Range Medium Lasers introduced for production every few years, with Dreadnought-made variants OX-1T – Introduced in 3007, the OX-1T is the original Oryx. Developed and
2 TharHes Maxi Short Range Missile 6-Racks given their signature “DII-” chassis code. produced by Roushan Heavy Industries, the -1T has continued production by
Manufacturer: Dreadnought Interstellar Industries Taurus Territorial Industries after absorbing Roushan in 3009. The original
Primary Factory: Dreadnought MechFoundry; Acala III Capabilities Oryx is built on the Roushan OX Heavy standard chassis and is powered by a
Communications System: Neil 7000-J General Motors 180-rated Fusion Engine for a top speed of 54 km/h. The
Targeting & Tracking System: Garret D2JB Although it is often thought of as a “heavier Blackjack”, the Oryx is a chassis of the OX-1T is protected by a respectable eleven tons of Durallex
remarkable machine—especially for a design originally created by a small Heavy Standard Armor. With three jump jets, mounted evenly across the
Overview manufacturer based in the Periphery. The DII-OX-2G variant, despite all its torso, the -1T can jump up to ninety meters at a time. This first production
upgrades over the original Oryx design, costs just over five-and-a-half million model of the Oryx is armed with an Imperator Smoothie-2 Autocannon/2
The Oryx was the first BattleMech type to be produced by Roushan Heavy C-Bills. This makes it a bargain for a reasonably advanced and effective heavy paired with a Shannon Six-Shooter Short Range Missile system in each arm,
Industries. It also proved to be the last. The upstart manufacturer, based on ‘Mech. Despite its affordability-oriented manufacturing origins, this heavy backed by an Omicron 3000 Medium Laser and an Omicron 1000 Small Laser
the Taurian Concordat capital world of Taurus, had been producing knockoff BattleMech is a respectable defense unit when used appropriately. When in each side torso. One ton of ammo in each side torso feeds the SRMs, while
IndustrialMechs and even some light-duty combat vehicles for nearly three Dreadnought Interstellar began production of the Oryx, several components a single ton of ammo installed in the center torso feeds the autocannons.
decades before the corporate executives decided to take the plunge and had to be replaced for easier acquisition from closer suppliers, such as the Seven of the fourteen single heat sinks that cool the Oryx housed within the
produce a BattleMech. Unfortunately, it took far longer than expected to get Fusion Engine and weapons systems. While the chassis is still compatible powerplant, three are installed in each side torso, and last is mounted in the
the complex war machine up and running. The delays and snowballing with most of the original Taurian-made components, the electrical systems head. (Battle Value: 1,156) Features the following Design Quirks: Anti-
development costs effectively bankrupted the small manufacturing firm. and some of the mounting hardware would have to be modified to use them. Aircraft Targeting (AC/2s Only), Easy to Maintain, Easy to Pilot, Rugged.
Equipment Mass
Internal Structure: Endo Steel 3
Engine: 240 Fusion 11.5
Walking MP: 4
Running MP: 6
Jumping MP: 3 3
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 184 11.5
Internal Armor
Structure Value
Head 3 9
Center Torso 20 28
Center Torso (rear) 7
R/L Torso 14 22
R/L Torso (rear) 6
R/L Arm 10 20
R/L Leg 14 22
Leftenant Parker Llewelyn “Ladies’ Man” Bowls created and written by Tim
“Critical Rocket” with minor additions by Devin Ramsey.
The raids during the FedCom Civil War left few survivors and the
whereabouts of The Headsman and The Executioners after the war ended is
still a mystery. Some claim The Headsman vanished once again into the
Periphery. Others claim they saw the individual die in combat. Numerous
worlds are claimed as the gravesite of this MechWarrior. The mystery of this
individual is intriguing and may never be solved, but one thing is certain: The
Headsman’s skill and ferocity in combat were truly terrifying to behold.
Equipment Mass
Internal Structure: Standard 8
Engine: 320 Fusion 22.5
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Single): 20 10
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 232 14.5
Internal Armor
Structure Value
Head 3 9
Center Torso 25 34
Center Torso (rear) 11
R/L Torso 17 26
R/L Torso (rear) 8
R/L Arm 13 26
R/L Leg 17 29
“The Headsman” created and written by Tim “Critical Rocket” with minor
additions made by Devin Ramsey.
Equipment Mass
Internal Structure: Standard 8.5
Engine: 255 Fusion 13
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 12 (24) 2
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 240 15
Internal Armor
Structure Value
Head 3 9
Center Torso 27 37
Center Torso (rear) 12
R/L Torso 18 27
R/L Torso (rear) 9
R/L Arm 14 27
R/L Leg 18 28
Equipment Mass
Internal Structure: Standard 9.5
Engine: 285 Fusion 16.5
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 17 (34) 7
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 288 18
Internal Armor
Structure Value
Head 3 9
Center Torso 30 45
Center Torso (rear) 14
R/L Torso 20 30
R/L Torso (rear) 10
R/L Arm 16 32
R/L Leg 20 38
* One ton of ammunition in the right torso is commonly filled with Inferno
missiles.
As a result of this goal of affordability, the production model was limited The DII-MTK-2-A1 Mattock II is, on a technical level, a downgrade of the
to a standard Fusion Engine, whereas the original BattleCorps variant of the high-tech-centric unit produced for use by the Dreadnought BattleCorps and
Mattock II had been equipped with a Clan-tech-based ExtraLight Fusion DefenseCorps. Despite the limitations, the armament of this machine is quite
Engine. The engineers initially believed they had been given an impossible similar. For long-range punch, a Grizzard Gauss Rifle is housed in each lower
task due to the sheer weight of the OHI-300F Fusion Engine that they had arm, with each gun fed by two tons of ammunition installed in the arm with
been saddled with. To make matters worse, the weapons to be used with the the weapon. For medium-range engagements, the ‘Mech carries a total of
mass production model of the Mattock II were limited to easily-sourced four BrightBloom Extended Range Medium Lasers, which are installed in
equivalents of the in-house manufactured Clan-tech weaponry used in the pairs in the side torsos. A Harpoon-6 Short Range Missile 6-rack housed in
original BattleCorps machine. This restriction in terms of the Mattock II’s the right torso provides a boost to the -A1’s firepower in close quarters. The
Mass: 100 tons armament meant the Gauss Rifles were far heavier, and the missile system SRM system has only a single ton of ammunition to feed it. As the missile
Chassis: Dura-Frame II Standard MTK-2-100/152S w/CASE had to be downgraded. The combination of all these components being so system is generally considered to be a backup weapon, a common choice is
Power Plant: Orbital Heavy Industries OHI-300F Fusion Engine much heavier than what the chassis was originally designed to be equipped to use Tandem-Charge ammunition for increased damage potential, though
Cruising Speed: 32.4 km/h with seemed to spell doom for the entire project from day one. it does reduce the number of salvos carried by half. A total of fourteen
Maximum Speed: 54.0 km/h double heat sinks ensure that the Mattock II remains cool in combat,
Jump Jets: None Despite the hurdles, what Dreadnought’s engineers managed to create regardless of how hard the ‘Mech is pushed.
Jump Capacity: 0 meters was nothing short of impressive. While the mass-production Mattock II was
Armor: MTK-2-Pattern StarSlab-4 Ferro-Fibrous Armor certainly more limited in terms of combat effectiveness versus the original Defensively, the Mattock II is equipped with a Garrett-Guardian Interface
Armament & Equipment: high-tech BC-Series unit, the restrictions placed on the mass-production 2B-series Guardian Electronic Countermeasures Suite. This helps prevent
2 Grizzard Gauss Rifles model miraculously resulted in it being more durable than the original. This enemy missile locks and serves to jam hostile C3 Networks. The Dura-Frame
4 BrightBloom Extended Range Medium Lasers increased durability was a direct result of the largest difference between the II standard chassis of the Mattock II is protected by a very respectable 16.5
1 Harpoon-6 Short Range Missile 6-Rack two: the powerplant. While the weight of the Fusion Engine was the largest tons of StarSlab-4 series Ferro-Fibrous Armor. To protect the core of the
1 Garrett-Guardian Interface 2B Electronic Countermeasures Suite difficulty to overcome in refitting the Mattock II for mass production, it ‘Mech from potential internal ammunition or Gauss Rifle explosions, both
Manufacturer: Dreadnought Interstellar Industries proved to be the reworked design’s greatest advantage over the BattleCorps- side torsos feature Cellular Ammunition Storage Equipment. As with the
Primary Factory: Dreadnought MechFoundry; Acala III exclusive original. Even if completely savaged to the point where both side -BC1 variant it is based on, the -A1 Mattock II suffers from sluggish initial
Communications System: Interconn-Comm VI torsos have been destroyed, the new DII-MTK-2-A1 Mattock II could still responsiveness when maneuvering from a standstill. However, even with the
Targeting & Tracking System: Pinpoint Version-IV return to base under its own power, whereas the more powerful BC-Series lower-tech Orbital Heavy Industries OHI-300F Fusion Engine powering it, the
design used by the Dreadnought BattleCorps would be unable to do so. -A1 can match the -BC1’s maximum groundspeed of 54 km/h.
Overview
Despite the extremely careful work done to limit the costs of production Additional Information
In a peculiar reversal of the normal order of a design’s introduction by and ensure that everything needed to maintain the ‘Mech was easily
Dreadnought Interstellar Industries, the Mattock II was a design first created sourced, most believed that the ‘Mech would still be outrageously expensive. As of 3085, the Mattock II is still a relatively new machine to the
for exclusive use by the Dreadnought BattleCorps, but it was later reworked This belief was further reinforced when someone within the Dreadnought battlefields of the Inner Sphere. However, it has already found itself
using more common technology for mass production, intended for general Interstellar leaked that if the BC-Series of the Mattock II were to ever be sold deployed in direct fire-support roles of one form or another by Houses
market sales/export. Like the BattleCorps’ BC-Series machine upon which it on the open market, the cost would most likely be around twenty-seven- Davion, Marik, Liao, and Steiner. House Kurita appears to be slow to adopt
is based, Dreadnought Interstellar Industries’ DII-MTK-2-A1 Mattock II million C-Bills. When this information was spread by the media, it caused the machine, but recent reports suggest that they may be acquiring a handful
Assault BattleMech is a descendent of Mango-Twee MechWorks’ 70-ton most potential buyers to turn away—until Dreadnought took it upon by mid-3086. The Mattock II has also made its presence known by many
Mattock Heavy BattleMech, which was introduced in the years leading up to themselves to announce that the mass-production unit would cost less than mercenary units looking to boost their battlefield effectiveness, using the
the Federated Commonwealth Civil War. eleven million C-Bills. With the first production models of the ‘Mech still Mattock II as a lynchpin unit for their forces—or even as a command ‘Mech.
months away from being manufactured, the media worked hard to cast
After the BC-Series Mattock IIs produced for the Dreadnought BattleCorps doubt on Dreadnought Interstellar’s claims. However, true to their word, the Variants
proved exceedingly effective during the intense fighting of Operation production-model DII-MTK-2-A1 Mattock II’s final price upon introduction in
LANCASTER in 3077, Dreadnought Interstellar Industries knew that they had 3079 was 10,808,000 C-Bills, making this assault-class BattleMech a relative DII-MTK-2-A2 – Introduced in 3080, the -A2 is the first alternate export
something special. If the manufacturer played their cards right, the heavy- bargain. variant of the Mattock II. Based directly on the -A1 variant, the -A2 uses the
Equipment Mass
Internal Structure: Standard 10
Engine: 300 Fusion 19
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 18 (36) 8
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 304 19
Internal Armor
Structure Value
Head 3 9
Center Torso 31 46
Center Torso (rear) 15
R/L Torso 21 32
R/L Torso (rear) 10
R/L Arm 17 34
R/L Leg 21 41
Captain Jean “Cap” Roussimoff created and written by Tim “Critical Rocket”.
Most of the combat vehicles manufactured by Dreadnought Interstellar Industries are produced for export purposes. Although the following articles focus primarily on the more powerful variants
of these machines that were used during Operation LANCASTER—variants produced by Dreadnought Interstellar Industries exclusively for the Dreadnought BattleCorps and DefenseCorps—these
articles will also fully explain all known production variants of these machines.
148 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
DII-AB-VT-BC2 ALBATROSS LIGHT ATTACK VTOL
Shipil Company—the intended engine for this craft—turned out to be flawed weaponry and armor. This, combined with the introduction Dreadnought’s
on a fundamental level, and the entire engine production line had to be new Target Data Networking (TDN) System, the Albatross can serve far more
scrapped. This setback, in conjunction with the appearance of the Clans in effectively as a “team player” in combat situations. Though the armored skin
the Periphery, was enough for the project to be put on indefinite hold. It was of the BC-Series Albatross is a half-ton lighter than the original design,
believed at the time that the Albatross Light Attack VTOL might never see a totaling at just three tons, the effective armor protection is virtually
finished production model. identical—and even gains a slight improvement to the rear—thanks to the
upgrade to Dreadnought’s Clan-derived ExoShield Ferro-Fibrous Armor. The
In 3055, with no knowledge of the existence of these heartless helicopters Floatation Hull—a safety feature present since the very first production
gathering dust, Orbital Heavy Industries built their first-ever ExtraLight models of this craft—is naturally retained in all BC-Series variants.
Fusion Engine as a proof of concept for their all-new proprietary Fusion
Engine design and manufacturing process. This new ExtraLight Fusion Engine The DII-AB-VT-BC2 is the most common of the four production BC-Series
took the form of a 165-rated unit. The new engine proved to be so tough that variants of the Albatross Light Attack VTOL manufactured exclusively for
it survived torture tests that would break most production ExtraLight Fusion Dreadnought’s BattleCorps and DefenseCorps. The -BC1, with its powerful
Engines used in military applications, and it soon became the basis upon electronic warfare suite and twin Medium Pulse Lasers, was built specifically
Mass: 20 tons which all future OHI ExtraLight Fusion Engines were built. This included their with combating the Word of Blake in mind. The -BC2 takes this design and
Movement Type: VTOL later Clan-tech-based examples used in ‘Mechs and vehicles produced refines it, but also shifts the design focus of the craft from disrupting enemy
Power Plant: Orbital Heavy Industries OHI-165XL ExtraLight Fusion Engine primarily for the Dreadnought BattleCorps and DefenseCorps. operations to target designation.
Cruising Speed: 140.4 km/h
Flanking Speed: 216.0 km/h Seeing the success of the newly engineered powerplant created by their In place of the -BC1’s Medium Pulse Lasers, the -BC2 is armed with a pair
Armor: AB-VT-Pattern Dreadnought ExoShield Ferro-Fibrous Armor very own partner company, Dreadnought Interstellar Industries was quick to of Clan-tech Flash Sword VII Extended Range Medium Lasers, tied to an
Armament & Equipment: arrange exclusive rights for the new engines built by Orbital Heavy Industries. Enhanced Pinpoint Version-V Targeting Computer. The altered armament
2 Flash-Sword VII Extended Range Medium Lasers The first complete Albatross Light Attack VTOLs began to be assembled and improved targeting system gives the Albatross -BC2 a solid punch with
1 Garrett Mole Target Acquisition Gear shortly thereafter. The first variant, the DII-AB-VT-D1, featured a massive accuracy that nearly rivals the -BC1’s pulse-type lasers, but with moderately
1 Dreadnought BC Special Mk-II Target Data Networking System nose-mounted Parti-Kill Heavy Cannon supplied by New Earth Trading increased range. Unfortunately, though the switch from Medium Pulse
Manufacturer: Dreadnought Interstellar Industries Company. The Federated Commonwealth virtually dove on this first version Lasers to Extended Range non-pulse units does free up two tons of chassis
Primary Factory: Acala Advanced Avionics Facility; Acala III of the Albatross, and the craft quickly became a common sight on the battle weight capacity, the new weapons produce more heat, necessitating the
Communications System: Interconn-Comm VII lines of the Clan Invasion in Steiner space. installation of two heat sinks.
Targeting & Tracking System: Enhanced Pinpoint Version-V T.C. w/TAG
Initially so overwhelmed by the demand after the FedCom contract was The most notable addition in the -BC2, however, is the inclusion of a
Overview written and signed virtually overnight, Dreadnought nearly breached their Garrett Mole Target Acquisition Gear pod housed in the nose just above the
new contract to build the Albatross, because they had yet to finish rebuilding twin lasers, allowing the fast-moving VTOL to not only feed direct targeting
The design goals behind Dreadnought Interstellar Industries’ Albatross the production line to produce the craft’s chassis—said line having been telemetry to friendly units via the TDN System, but also paint targets for
Light Attack VTOL were to create a lightweight, adaptable, high-speed scout repurposed for nearly half a decade. Once the assembly line came back semi-guided artillery munitions. Lastly, though the -BC2 lacks the -BC1’s
helicopter for use by the Armed Forces of the Federated Commonwealth, as online nearly a month later, Dreadnought was able to produce the craft in Angel Electronic Countermeasures Suite it retains the Dreadnought TDN
well as independent units such as mercenary outfits and planetary militias— just enough numbers to satisfy the requirements of the contract in the time System.
and, of course, Dreadnought’s own BattleCorps and DefenseCorps forces. allowed. From then on, Dreadnought had no major issues meeting the
contractual production goals. Additional Information
The design of the twin-rotor helicopter was carefully crafted so that it
could be easily adapted to future upgrades, such as advanced electronic With the popularity of the Albatross Light Attack VTOL, alternate variants Though the “Davion” designated chassis variants—the -D1, -D2, -D3 and
warfare packages, ExtraLight Fusion Engines, and virtually any energy-based were explored, and new versions of the craft began to be produced just one -D3A models—of the Albatross Light Attack VTOL are relatively common in
weapons systems. Additionally, the Albatross was designed around a rather year later. These new variants quickly began to take full advantage of the both front line and garrison forces of Houses Steiner and Davion, they have
clever floatation hull to improve crew survivability in the event of a water modularity of the weapon mount and the space for advanced electronic yet to truly catch on elsewhere. Scattered examples have been reported in
landing after being shot down. With these specific criteria in mind, the warfare components. Following in the footsteps of the -D1, virtually all of various mercenary units and even House Kurita—the latter of which
Albatross was not designed with any internal space to store ammunition. these went straight into battle with the Clans, but many of the newer eventually commissioned their very own variant of the craft.
Instead, it had a clever modular weapons mount. This was an assembly variants found their way to several other Federated Commonwealth worlds.
rigged into the nose of the craft, allowing for exceptionally easy interchange Due to being slated toward anti-Blakist buyers on the open market during
of energy-based weaponry, such as lasers or PPCs. To support the modular 3073 saw the first of the new “BC-Series” Albatross Light Attack VTOLs roll the Word of Blake Jihad, the DII-AB-VT-X1 has become by far the most prolific
weapon mount in terms of fire control compatibility, the Albatross was off the assembly lines. These special variants were produced for use by the variant of the Albatross Light Attack VTOL in the Inner Sphere. It is commonly
equipped with Dreadnought Interstellar’s own Pinpoint Version-IV Targeting Dreadnought BattleCorps, and they were primarily designed to be employed seen in operation within the militaries of all the Great Houses and numerous
& Tracking System. This system allowed for plug-and-play operation of against the Word of Blake. They were mechanically nearly identical to tried- mercenary units alike. Many of the independently-operated examples of this
virtually any of the weapons the craft was capable of being equipped with, and-true existing variants. However, what set them apart was that they were craft have since had their electronic warfare packages downgraded due to
leading to the creation of numerous undocumented field refit variants. reskinned with newer armor and equipped with Dreadnought’s newer Clan- damage sustained in combat, winding up often becoming equipped similarly
based weapons, as well as recently-developed electronic warfare packages. or even identically to the -D3 variant.
The first prototype had a flanking speed exceeding 200 km/h and was
armed with twin Medium Lasers bracketing one Small Laser. In less than a Capabilities Predictably, the BC-Series variants remain exclusive to the Dreadnought
year, it had been approved for production. However, in 3049, just two BattleCorps and DefenseCorps forces. Though several of these craft were
months after chassis frames had begun production on Dreadnought’s Theris- The newer BC-Series Albatross Light Attack VTOL variants take an already destroyed during the violent events of Operation LANCASTER in 3077, they
based assembly line, the new 165-rated Fusion Engine to be produced by superb vehicle and improve its combat effectiveness with far more advanced have since been replaced.
The shell of the -BC1 Sprinter is made from a five tons of Dreadnought’s DII-SLT-TV-S2A – After discovering that the -S2 variant had a significant anti-
ExoShield Ferro-Fibrous Armor, providing significantly improved protection infantry deficiency in comparison to the -S1, this field refit was introduced.
over the original -S1 Sprinter. Replacing the original Kinslaughter PPC is a The refit removes one of the three tons of LRM ammunition and installs a
Thunderstruck XV Extended Range Particle Projector Cannon. The choice of Machine Gun mounted in the turret. The Machine Gun is fed by a half-ton of
Mass: 35 tons this main weapon was made with some apprehension, as the intense cooling ammunition. The tank was otherwise unmodified. (Battle Value: 723)
Movement Type: Tracked requirements necessitated that the tank be stripped of all secondary weapon Features the following Design Quirks: Easy to Maintain, Rugged.
Power Plant: Orbital Heavy Industries OHI-175XL ExtraLight Fusion Engine systems. The upside of the new particle cannon is that the vehicle does not
Cruising Speed: 54.0 km/h require an ammunition supply—and it hits harder than ever—the downside DII-SLT-TV-D1 – In 3040—long after Dreadnought Interstellar Industries had
Flanking Speed: 86.4 km/h being that it is unable to defend itself against infantry, unlike the original -S1 relocated its headquarters to Acala III and began manufacturing war materiel
Armor: SLT-TV-Pattern Dreadnought ExoShield Ferro-Fibrous Armor variant. Like all BC-Series Sprinters, the -BC1 is equipped with Dreadnought’s there—House Davion needed effective and affordable light tanks to replace
Armament & Equipment: own Target Data Network (TDN) System, allowing it to share its targeting those lost during the War of 3039. Dreadnought Interstellar responded by
1 Thunderstruck XV Extended Range Particle Projector Cannon telemetry with friendly Linked units much like a C3 Network, but without the offering a new Sprinter Light Tank variant. Mechanically based on the original
1 Dreadnought BC Special Mk-II Target Data Networking System susceptibility of being jammed—although the TDN System has its own -S1 variant, the -D1 replaces the turret-mounted Particle Projector Cannon
Manufacturer: Dreadnought Interstellar Industries limitations. The TDN System also provides the -BC1 with limited electronic with a ChisComp 43 Special Large Laser and a ChisComp 39 Medium Laser.
Primary Factory: Dreadnought PanzerWerks; Acala III warfare capacity. Though the older versions of the Sprinter were built more The paired lasers in the turret necessitate the installation of an additional
Communications System: Interconn-Comm VII toward functioning independently on the battlefield, all BC-Series variants heat sink to cope, but the -D1 is otherwise identical to the -S1. The -D1
Targeting & Tracking System: Pinpoint Version-IV are designed to fight in teams with other vehicles—including ones with anti- Sprinter also has the “claim to fame” of being the least-expensive Sprinter
infantry weapons, which usually compensates for the Sprinter’s lack of them. variant ever created. (Battle Value: 609) Features the following Design
Overview Quirks: Easy to Maintain, Rugged.
With a top speed of 86 km/h, this light tank is designed with the idea of
Dreadnought Interstellar Industries’ Sprinter Light Tank was designed to fire-relocate-fire-repeat strategies in mind. Alternatively, it can rapidly take DII-SLT-TV-BC2 – The Dreadnought BattleCorps’ BC-Series Sprinter Light
serve as a rapid-response, long-range support vehicle. The first generation up a defensive position and hit an attacking force hard at long range for Tanks began production in October of 3070 with the DII-SLT-TV-BC1, with
Sprinter began rolling off the assembly lines of Dreadnought’s own Skye however long the tank remains functional. Additionally, the new BC-Series two more BC-Series variants introduced in the following months. The -BC2
Heavy Iron Works Facility in 2655. The Sprinter quickly gained a reputation variants of the Sprinter Light Tank—like most of the known BC-Series combat was designed as a more multipurpose battlefield support unit. It features an
for being a remarkably rugged and well-rounded combat vehicle—with the vehicles—include environmentally-sealed hulls, making the atmospheric impressive array of advanced onboard electronics, with an EW-Special Mk-
added advantage that it was built using nearly all commonly available or at composition of a planet no longer a deciding factor in deployment. As the IV Angel Electronic Countermeasures Suite in addition to its Dreadnought
least easily adaptable parts for ease of maintenance and repair. -BC1 Sprinter requires neither ammunition nor fuel, a well-maintained TDN System. The -BC2 is armed with a brace of three Flash-Sword VII
example of this tank can operate through multiple campaigns with minimal Extended Range Medium Lasers, backed by an Achernar Industries “Double-
The Sprinter Light Tank quickly became a favorite of House Steiner’s Lyran servicing—mostly limited to just battle damage repairs. Gun” Machine Gun—the latter weapon notably not derived from Clan
Commonwealth Armed Forces. The combination of mobility and impressive technology—all of which are mounted in the turret. A half-ton of IS-tech-
firepower for its weight, reasonable cost (around one million C-Bills in Variants CASE-equipped ammunition feeds the Machine Gun. The -BC2 is often used
today’s money), relatively minimal required maintenance, and simplicity of as a short-to-medium-range support tank for larger forces, as it can function
construction—all of this made the Sprinter an understandably attractive DII-SLT-TV-S1 – Introduced in 2655, the original -S1 Sprinter is the most as a harasser and a solid ECM/ECCM unit. (Battle Value: 1,045) Features
combat vehicle for any military. prolific variant of this light tank ever created. The five-ton armored shell of Environmental Sealing special equipment, as well as the following Design
the tank provides superb protection. The -S1 is well armed, with a Quirks: Dreadnought Spec (Tier-2)*.
Despite having chassis variant codes marked for House Steiner, it was not combination of a Kinslaughter Particle Projector Cannon and a trio of
long before the Sprinter began to appear in militaries outside Lyran territory. Machine Guns—typically Coventry Light Autoguns, but this varies from year DII-SLT-TV-BC3 – The third, and final, known BC-Series Sprinter Light Tank
In a matter of decades following the vehicle’s introduction, Sprinters could to year of production—all of which are installed in the turret, backed by a variant is defined by its unique boxy turret, which sports a pair of Clan-tech
be found in the service of most military forces—be they large or small— single forward-facing Omicron 3000 Medium Laser installed in the hull. A Reacher-Series Long Range Missile 15-racks. The missile systems are fed by
across the entire Inner Sphere and Periphery. Dreadnought Interstellar half-ton of shared ammunition feeds the Machine Guns. Powered by a a combined five tons of ammunition equipped with IS-tech CASE. As with the
Industries was taken by surprise not only by how prolific the Sprinter Defiance 175-rated Standard Fusion Engine, the -S1 Sprinter is capable of other BC-Series Sprinters, the -BC3 includes a Dreadnought TDN System to
became, but how quickly it did so, resulting in the creation of an entire speeds exceeding 80 km/h. (Battle Value: 618) Features the following Design assist with targeting enemy units near Linked friendly combatants. Designed
second production line on Skye to keep up with demand—just two years Quirks: Easy to Maintain, Rugged. for shorter engagements due to its heavy dependence on ammunition, this
after the vehicle’s introduction. variant is primarily meant for long-range harass-and-retreat roles. Another
DII-SLT-TV-S2 – Introduced in 2667, this variant of the Sprinter came to be unique feature of this variant is a rear-mounted Vehicular Mine Dispenser,
Capabilities because of a supply shortage of Kinslaughter Particle Projector Cannons and which allows the -BC3 Sprinter to plant devastating minefields. (Battle Value:
an excess stock of Omicron 3000 Medium Lasers and TharHes Reacher 15 1,068) Features Environmental Sealing special equipment as well as the
By late 3069, Dreadnought Interstellar Industries had gained the ability to Long Range Missile systems. The resulting -S2 Sprinter is a long range missile following Design Quirks: Dreadnought Spec (Tier-2)*.
Equipment Mass
Internal Structure: 3.5
Engine: 175 Fusion XL 5.5
Type: Tracked
Cruising MP: 5
Flanking MP: 8
Heat Sinks: 17 7
Control Equipment: 2
Turret: 1
Armor Factor (Ferro-Fibrous (Cl)): 96 5
Internal Armor
Structure Value
Front 4 24
R/L Side 4 19
Rear 4 15
Turret 4 19
The model design of the Sprinter Light Tank is a copyrighted original creation
by Michael Szita as a collaboration with Devin Ramsey. It is used here with
permission. Mr. Szita’s store “Metal Core Collectibles” can be found here:
https://www.metalcorecollectibles.ca/
Equipment Mass
Internal Structure: 4.5
Engine: 225 Fusion XL 7.5
Type: Tracked
Cruising MP: 5
Flanking MP: 8
Heat Sinks: 12 2
Control Equipment: 2.5
Turret: 1.5
Armor Factor (Ferro-Fibrous (Cl)): 134 7
Internal Armor
Structure Value
Front 5 36
R/L Side 5 26
Rear 5 20
Turret 5 26
Foster and his crew were awarded appropriate medals that reflected their
courage under fire. In addition, they were given the opportunity to choose
their next vehicle assignment, as Shoebox had been so irreparably damaged
that it had to be scrapped. The crew chose to stay with the same type of
vehicle that they had already served together—and survived together—in. It
seems only natural that the crew has nicknamed their new tank “Shoebox II”.
The model design of the Kodiak Heavy Tank “Tarmac King” is a copyrighted
original creation by Michael Szita as a collaboration with Devin Ramsey. It is
used here with permission. Mr. Szita’s store “Metal Core Collectibles” can be
found here: https://www.metalcorecollectibles.ca/
This heavily armored anti-air tank saw uninterrupted production all The unique features of the BC-Series variants of the Fusillade Flak Tank are
throughout the Succession Wars. While somewhat infamous for its sluggish limited but important. Most critically, the chassis weight capacity freed up
acceleration, the reliability of the VOX 255-rated Fusion Engine and Defiance by the ExtraLight Fusion Engine and Ferro-Fibrous Armor allow for these
Model F Class-5 Autocannons have become legendary among military vehicle variants of the Fusillade to be equipped with Environmental Sealing special
technicians. The Fusillade requires surprisingly minimal maintenance in its equipment. The importance of the Environmental Sealing equipment is that
factory-standard form—and whenever this tank does require repairs or it protects the crews of these vehicles from the biological weapons often
maintenance, it is remarkably easy to service. The same unfortunately could employed by the Word of Blake—as well as allowing these vehicles to
not be said for the line combat refits—such as the urban variants—as they operate in vacuum and hostile environments. The BattleCorps variants of the
required altered ammunition feed systems, and in some cases added energy Fusillade trade the standard TharHes Calliope Hm10 communication systems
weapons that the vehicle was not originally designed to carry. to incorporate Dreadnought’s Target Data Networking (TDN) Systems and
PinPoint Version-IV-AAA (Anti-Air Artillery) targeting & tracking systems.
During the Word of Blake Jihad, Blakist aerospace fighters quickly began
to pose a very real threat to any who opposed them. Their Spectral Series Introduced in 3072, the -BC1 Fusillade Flak Tank is—like the common
Mass: 85 tons OmniFighters proved to be powerful assets in the Blakist arsenal. Despite the export variants—dependent on outsourced weapons due to Dreadnought
Movement Type: Tracked Dreadnought BattleCorps having developed powerful aerospace fighters of Interstellar’s inability to reproduce Clan-tech-based Autocannons. To allow
Power Plant: Orbital Heavy Industries OHI-255XL ExtraLight Fusion Engine their own to match—and arguably best—the Spectral OmniFighters, it was for equal ability to shoot down VTOL craft as well as both conventional
Cruising Speed: 32.4 km/h clear that the BattleCorps desperately needed anti-air artillery support. With fighters and AeroFighters alike, the -BC1 Fusillade features pairs of Defiance
Flanking Speed: 54.0 km/h the Fusillade Flak Tank still in production on Skye but with standard variants LB 5-X Autocannons and Defiance Model-F Autocannon/5s, produced on
Armor: FFT-TV-Pattern Dreadnought ExoShield Ferro-Fibrous Armor vulnerable to the kinds of biological weapons that were commonplace in Hesperus II by Defiance Industries. In terms of ammunition supply, the -BC1
DII-FFT-TV-BC1 (Pictured, Foreground) Armament & Equipment: Word of Blake assaults early in the Jihad, a new variant was developed. carries three tons of ammunition to feed each autocannon pair. The most
2 Defiance LB 5-X Autocannons typical CASE-equipped ammunition load is two tons of Cluster rounds and
2 Defiance Model-F Class-5 Autocannons Utilizing the pre-existing chassis and internal mechanicals, the Fusillade one ton of Slug rounds for the LBX Autocannons—along with two tons of
1 Dreadnought BC Special Mk-II Target Data Networking System chassis used to produce the “Dreadnought Spec” BC-Series variants were Flak-type and one ton of Flechette-type ammunition for the Model-Fs.
DII-FFT-TV-BC2 (Pictured, Background) Armament & Equipment: adapted to include an Environmentally Sealed interior. However, the BC-
3 Spin-Werx Type A10 Rotary-5 Autocannons Series Fusillade Flak Tanks were not shipped from Skye with an engine It was only with the introduction of the Spin-Werx Type A10 Rotary-5
1 Dreadnought BC Special Mk-II Target Data Networking System installed. The BC-Series Fusillades were essentially shipped as rolling chassis. Autocannon that the BC-Series of the Fusillade finally hit its stride. The -BC2,
Manufacturer: Dreadnought Interstellar Industries The new ExtraLight Fusion Engine, the electronics suite, the targeting system, introduced in late 3074, is mechanically identical to the -BC1 in every sense
Primary Factory: Skye Heavy Iron Works Facility; Skye (Skye IV) and the Ferro-Fibrous Armor shell were all installed after being received on except for its armament and turret configuration, as it features a total of
(BC-Series Units Completed at Dreadnought PanzerWerks; Acala III) the Dreadnought homeworld of Acala III to prevent any of the advanced three of these powerful, rapid-fire weapons. The thirsty autocannons are fed
Communications System: Interconn-Comm VII components being intercepted and stolen during shipping. by a total of eight tons of CASE-equipped ammunition. Although this
Targeting & Tracking System: Pinpoint Version-IV-AAA (Anti-Air-Artillery) ammunition supply is significant, the rate at which the Type A10 Rotaries can
Unfortunately, thanks to the Word of Blake Jihad making transport more consume ammunition does generally require a -BC2 Fusillade to remain
Overview and more difficult through the core of the Inner Sphere, most of the BC- relatively close to a supply line.
Series units used by the Dreadnought BattleCorps between 3075 and 3080
The Fusillade Flak Tank was introduced in early 2632. This assault-class were in fact older Fusillade variants that were torn down and rebuilt to The -BC1 Fusillade Flak Tank is generally considered the BattleCorps’
anti-air tank was created primarily for service in the Star League Defense Dreadnought Spec. The BC-Series Fusillade Flak Tanks employed by the staple anti-air artillery vehicle. Meanwhile, the -BC2 will typically be assigned
Force but quickly saw considerable proliferation across the Inner Sphere. Dreadnought BattleCorps—and then later the DefenseCorps—have been as defense for SupportCorps units, as it presents an intimidating opponent
historically by far and away the most expensive variants of the breed, though for ground and air units alike, with impressive suppressing fire capability. As
During the Amaris Coup, great respect for the Fusillade Flak Tank was not as expensive to Dreadnought Interstellar Industries as most tend to a result of being the basis for the far more common export-model -D2
earned as these anti-air defense platforms were responsible for shooting believe. As the OHI-255XL powerplant was manufactured by Orbital Heavy variant, the -BC2 registers as a -D2 on most battle computers, often leading
down several Rim Worlds Republic AeroFighters armed with nuclear Industries (Dreadnought Interstellar Industries’ manufacturing partner) the opponents to underestimate the range of its rapid-fire autocannons.
weapons. The intercepted nuclear weapons had been intended for use on a cost to Dreadnought to build these machines was a fraction of what it would
portion of the relatively small number of Star League Defense Force bases have been otherwise. Even with the significant cost reduction, however, the Despite the DII-FFT-TV-BC2’s relatively impressive overall capabilities in
still being manned by loyal SLDF troops within the Terran Hegemony. The BC-Series Fusillades were still expensive machines, and at first glance they combat, the introduction of the considerably less-expensive DII-OX-BC2 Oryx
destruction of these nuclear weapons bought valuable time for a handful of had few additional features to justify the rather prohibitive cost. This cost Heavy BattleMech has rendered this variant of the Fusillade Flak Tank nearly
loyal SLDF troops to attempt to set up a defense against their Rim Worlds proved to be prohibitive enough, in fact, that even as the BattleCorps began obsolete. The existing models are continuing to be used, but most have been
Republic attackers. Unfortunately, while the Fusillades managed to buy the to receive their first Fusillades, alternatives began to be investigated—with reallocated to be used by Dreadnought DefenseCorps forces, and by all
SLDF forces time, that time was simply not enough in any of these cases. eyes soon turning to the Oryx Heavy BattleMech. indications very few have been built in recent years.
The SLDF’s Fusillade Flak Tanks stationed in the Terran Hegemony were Capabilities Deployment
inevitably all destroyed or captured during the betrayal by the Rim Worlds
Republic troops under the command of Stefan Amaris—the infamous With a top speed of 54 km/h, the BC-Series Fusillades are neither faster Due to its unimpressive speed and even less impressive acceleration
usurper of the Star League. nor more maneuverable than other variants, and the vehicle is still plagued characteristics, Fusillades will most often be deployed to a heavily defensible
Equipment Mass
Internal Structure: 8.5
Engine: 255 Fusion XL 10
Type: Tracked
Cruising MP: 3
Flanking MP: 5
Heat Sinks: 10 0
Control Equipment: 4.5
Turret: 3.5
Armor Factor (Ferro-Fibrous (Cl)): 192 10
Internal Armor
Structure Value
Front 9 48
R/L Side 9 37
Rear 9 30
Turret 9 40
The model design of the Fusillade Flak Tank is a copyrighted original creation
by Michael Szita as a collaboration with Devin Ramsey. It is used here with
permission. Mr. Szita’s store “Metal Core Collectibles” can be found here:
https://www.metalcorecollectibles.ca/
Equipment Mass
Internal Structure: 8.5
Engine: 255 Fusion XL 10
Type: Tracked
Cruising MP: 3
Flanking MP: 5
Heat Sinks: 10 0
Control Equipment: 4.5
Turret: 3
Armor Factor (Ferro-Fibrous (Cl)): 201 10.5
Internal Armor
Structure Value
Front 9 48
R/L Side 9 37
Rear 9 30
Turret 9 49
Equipment Mass
Internal Structure: 10
Engine: 200 Fusion 13
Type: Tracked
Cruising MP: 2
Flanking MP: 3
Heat Sinks: 12 2
Control Equipment: 5
Turret: 3
Armor Factor (Ferro-Fibrous (Cl)): 240 12.5
Internal Armor
Structure Value
Front 10 58
R/L Side 10 48
Rear 10 38
Turret 10 48
Though best known for the innovative and powerful technology utilized in their war machines—ranging from conventional combat vehicles to Black-Water WarShips—Dreadnought Interstellar
Industries has worked to ensure that even the individual members of the Dreadnought BattleCorps’ infantry are offered the best training and equipment possible. Likewise, the BattleCorps ensures
that their AeroFighter pilots and MechWarriors are exceptionally well-prepared to survive in the event of their machines being destroyed in combat, even in exceptionally hostile environments.
180 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
LIBERATOR MK VI LASER PISTOL
itself from any perceived connection with Amaris, and the Liberator became increasingly rare as the later Succession Wars
ravaged the Inner Sphere. What would likely have become a common addition to most gun collections instead faded to
the dim memory, with many examples of this weapon foolishly being destroyed over the following centuries by those
who identified the Liberator with the evil that was Stefan Amaris. Many others were discarded during the Succession
Wars due to a lack of available quality replacement Drum Power Packs. By the early-to-mid 31st Century, the combination
of these actions led to the Liberator being virtually impossible to find anywhere outside of serious gun collectors’
collections and museums—and most museum examples were either unserviceable units or nonfunctional replicas.
The Liberator Mk VI Laser Pistol resumed production in 3072 on Acala III, once the weapon’s construction techniques
were able to be replicated based on schematics discovered by the Dreadnought BattleCorps on the former Clan Smoke
Jaguar world of Pantheress VI. The Drum Power Pack technology utilized in the Liberator later found its way into the
specialized Cluster Power Packs designed for use with the PAARR-15/GL Infantry Assault System. While the Liberator
continues to be manufactured and is readily available on the open market as of 3085, this weapon has become the choice
sidearm of Dreadnought’s private military forces, as well as a typical backup weapon for Dreadnought’s own Elite Marines.
Other features of the Liberator Mk VI Laser Pistol include a variable power setting that can allow the pistol to be used
as a less lethal tool by firing at half power—and using only half a charge at a time—such as for use as an ignition source
for a fire or shooting smaller rodents. This laser pistol also features a three-shot burst-fire mode, taking advantage of the
remarkably high charge capacity of the Drum Power Pack. It should be noted, however, that if fired in burst-fire mode
three times consecutively, the pistol will overheat and refuse to fire for several seconds. This is an automatic safety
feature designed to give the weapon time to cool down, as it could otherwise burn out or even explode its power pack.
In a rather stark contrast to the highly advanced technology of this weapon, the Liberator is most often used with a
Liberator Mk VI Laser Pistol conventional “Iron sight”. The bolt-on iron sight can be quickly and easily swapped for a universal mounting rail, allowing
for any number of different sight options—or even scopes—for owners to choose from.
Developed by Dreadnought Interstellar Industries with reliability, durability, ease of operation, ease of maintenance
and versatility in mind, the Liberator Mk VI Laser Pistol has proven itself a choice personal weapon. The Liberator, In its normal configuration, the Liberator includes an underslung attachment rail cast into the forward section of the
however, had a particularly difficult birth. The design process took nearly a decade to sort the weapon out, and it was barrel. The most common attachment used with the Liberator is a “Masterkey” attachment, which is essentially an
nearly cancelled several times prior to reaching its sixth form—the form that was finally put into production. underslung single-shot reloadable shotgun. Masterkey attachments are commonly used with most pistols for blowing
open conventional door latches. However, in the case of this weapon, it often finds use as a backup option if the operator
First introduced in late 2722, and produced on the world of Skye, the Liberator was developed primarily for use by the needs to be able to fire the pistol in self-defense, but it is overheated from repeated burst-fire discharges.
Star League Defense Force. This weapon saw significant use across Cameron territory prior to the Amaris Civil War and
subsequent fall of the Star League. Though limited production of the Liberator continued for high-paying private To make the Liberator Mk VI Laser Pistol that much more adaptable for different users, it is designed for easy swapping
customers even after the fall of the Star League, the production line was finally shuttered altogether in 2783. of grips to accommodate virtually any user’s hand size, as well as left-handed or right-handed users. Any grip made for
use with the Liberator must be designed to fit the integrated fingerprint sensor security system, which is fitted to scan
The most unique feature of the Liberator is its “Drum” Power Pack design—shaped similarly to a revolver’s ammunition the middle finger of the user whenever the weapon is gripped. It should be noted, however, that the examples of this
cylinder—giving this highly advanced weapon its signature blend of modern and retro aesthetic. While the pistol itself pistol that are issued to Dreadnought’s Elite Marines, MechWarriors, and AeroFighter pilots require an alternate security
was discontinued in 2783, the production of these bespoke Drum Power Packs continued for close to two decades. unlock. This alternate unlock mechanism is required because these personnel would need to be able to use their weapon
Unfortunately for enthusiasts of the Liberator, the only replica Drum Power Packs produced by other manufacturers were while wearing gloves, so the pistol is supplemented with an identification system that is programmed to verify the user’s
of generally poor quality, though a few respectable specialists did regularly rebuild original units to like-new condition. identity through the user’s body armor whenever the weapon is gripped but no fingerprint can be detected.
Each of the Liberator’s Drum Power Packs housed a total of ten High Capacity Micro Battery Packs, allowing the weapon
to fire a total of fifty times before the quick-swap rechargeable battery unit had to be replaced. A simple, compact digital Item: Liberator Mk VI Laser Pistol Equipment Rating: E/D-F-E/E
display showing the battery’s charge level is installed at the back of the weapon, facing the user, where the hammer of a
conventional pistol would be. This allows the user to easily see the display at the back of the gun while aiming. Laser Pistol – Armor Piercing/Base Damage: 4E/4 Masterkey Attachment – Armor Piercing/Base Damage: 1/6D6
Laser Pistol – Range: 15/40/90/200 meters Masterkey Attachment – Range: 4/8/16/30 meters
Strangely, this laser pistol has often been misrepresented in various holodramas and trivid programs as the type of Laser Pistol – Power Points per Shot: 4 Masterkey Attachment – Shots: 1
weapon that was used by Stephan Amaris to kill Richard Cameron. The origin of this misconception has been traced back
to a holograph of a customized Liberator Mk VI Laser Pistol being used as a headline filler image in a 2782 news article Cost/Reload: 1,500 (without Power Pack or attachments; 300 per Drum Power Pack) / 10 “Masterkey Attachment” (1 per
detailing the death of the Cameron dynasty at Amaris’ hands. Though the news article used accurate information from a Shotgun round)
recovered journal kept by Stefan Amaris himself, the image of the modified Liberator had been used as a substitute Mass: 1.55kg (without attachment or Drum Power Pack) / 0.25 kg (Drum Power Pack) / 0.2kg (“Masterkey Attachment”)
because the writers of the article could not acquire an image of the actual weapon used. They instead found a weapon
that resembled the jewel-encrusted laser pistol described in Amaris’ journal as the one he used to execute the young First Notes:
Lord Cameron at the start of the Amaris Civil War. The unscrupulous writers clearly believed that the accuracy of the Laser Pistol: Single shot or Burst 3; Recoil 0. Utilizes “Drum Power Pack” containing 10 High Capacity Micro Battery
image used with their article did not matter. Unfortunately for the Liberator, it did. Packs (200 charges, 0.25kg, 330 C-bills each). Cannot be fired for a full turn if used in burst-fire mode three turns in a row
(one turn cooldown).
These depictions have resulted in severe damage to the reputation of the weapon over the centuries. Following the Masterkey Attachment: -1 penalty to Attack Roll. Splash damage.
release of the news article, Dreadnought Interstellar chose to discontinue the Liberator Mk VI Laser Pistol to distance
A far more dramatic example of the TISAAA being used to great effect beyond the designed parameters is a specific
event that took place during Operation LANCASTER. A Dreadnought Elite Marine who was temporarily deafened, severely
wounded, half-buried in rubble, and separated from the rest of his squad, was about to be swarmed by Word of Blake
infantry. Knowing that the path the enemy infantry had to use was narrowed down at a certain point where he could hit
them as they appeared, he swapped the Cluster Power Packs and aimed his PAARR-15/GL IAS in the direction of the
narrow corridor that was the only way in or out of his location. Whenever he saw any signs of enemy troops in the
corridor, he fired. Despite his inability to accurately aim his rifle, the TISAAA was able to compensate well enough to strike
and incapacitate a hostile with nearly every pull of the trigger. When the rest of his own squad arrived, he tried to fire at
them as well, unable to see well enough to know they were in fact friendlies. However, the rifle recognized the friendlies
even though the Marine could not, and it refused to fire. The PAARR-15/GL IAS’ TISAAA system saved more than just the
Marine’s life—it also saved the lives of those who had come to rescue him.
The TISAAA can be disabled manually, and the rifle will function as a normal pulse laser rifle without any aim assistance.
Though exceedingly rare, in the event of a system failure, the focusing lens actuation system automatically recenters the
focusing lens and the TISAAA is disabled. The TISAAA’s micro-actuation system and the laser’s focusing lens are replaced
as a single compact unit combined with the rifle’s barrel. Meanwhile, the TISAAA control unit is replaced as a separate
rectangular box—roughly the same size as a 25mm grenade—located above the trigger and below the scope. Despite its
complex electronics, the entire rifle is designed to be relatively easy and quick to tear down and service, and replacement
of these crucial electronic components is a relatively simple task for a trained soldier familiar with the weapon.
Power for this rifle comes in multiple forms. The most basic and inexpensive power supply for the PAARR-15/GL IAS is
a Satchel Battery, with installation ports on each side of the weapon allowing two to be used simultaneously, though only
PAARR-15/GL INFANTRY ASSAULT SYSTEM one need be installed at any one time for the weapon to function normally. When the weapon was first being distributed
Pulse Aim-Assisted Rapid-fire Rifle – 15-shot-maximum variable burst fire / pump-action 4-shot Grenade Launcher to Dreadnought’s infantry forces, troopers using PAARR-15/GLs often chose to use one 3-kilogram High Capacity Satchel
Battery to have 75% of the power capacity of two standard Satchel Batteries, as this combination brought the weight of
Dreadnought Interstellar Industries utilized a combination of Clan Technology and Inner Sphere ingenuity to create a the weapon down to 10.5 KG—one kilogram lighter than it would be with two standard Satchel Batteries—though this
highly effective infantry combat weapon for the Dreadnought BattleCorps’ Elite Marines in 3073. The PAARR-15/GL practice did result in a weight imbalance. Troopers commonly loaded the weapon with two fully charged High Capacity
(typically pronounced “Par-Fifteen-Gee-Ell”) Infantry Assault System was the result of Dreadnought Interstellar’s efforts, Satchel Batteries to maximize fighting time only when entrenched and expecting heavy fighting in a relatively static
and it has become the primary heavy personal weapon of the Dreadnought BattleCorps and DefenseCorps forces. location, as the weapon would then weigh as much as 13.5 KG. With the Satchel Battery mounting ports being on the
sides of the rifle, it ensures that at least one of the batteries is quick and easy to replace, regardless of whether the trooper
Though built around a titanium-alloy frame, this rifle is constructed largely of polymer compounds. Thanks to the using the rifle is right-handed or left-handed. The Satchel Batteries are mounted such that they are extremely easy to
extendable stock’s integrated shoulder strap, the PAARR-15/GL IAS is far more easily carried than the Mauser 960 and remove but have a well-engineered securing mechanism to ensure that they will not be released from the weapon
Mauser IIC Infantry Assault Systems that it is loosely based upon. However, at 7.5 kilograms—without power packs—it is accidentally. Adding to the weapon’s user-friendliness, the user selects which battery the weapon depletes first, ensuring
by no means a lightweight weapon. The integration of the 25mm grenade launcher into the frame of the rifle was a point that if the user needs to quickly drop weight to move, the battery that the user can remove most quickly and easily—the
of contention among designers and actual operators, as it was felt that the added weight was significant enough to battery on the side of the rifle that faces the user when being carried normally—is the first battery that is depleted.
warrant making it a detachable component. When a prototype of the PAARR-15/GL was dismantled, however, operators
understood the choice once they realized that the integrated grenade launcher only added 0.95 kilograms to the weapon An early result of the inconvenience caused by significant weight of the Satchel Battery Packs was an optional backpack-
because of the construction techniques used—and much of this added weight was in fact the 0.16-kilogram grenades based power-pack. This unit required development of an entire infantry backpack to be built around it to function
loaded into the weapon. The integrated pump-action grenade launcher holds up to four 25mm grenades and is reloaded appropriately. It housed four tightly-packaged High Capacity Satchel Batteries in an armored housing, with the batteries
through the underside of the weapon identically to a conventional bottom-fed pump-action shotgun. all connected to the same circuit. The armored casing was nearly as tough as the helmet used in the Dreadnought
BattleCorps’ DEMICK Infantry Kit. A power cable, complete with adapter, was used to plug directly into one of the side
The most unique and clever aspect of the PAARR-15/GL IAS is the weapon’s aim-assistance system, known as “TISAAA”, ports where a Satchel Battery would normally be attached. The combined weight of the High Capacity Satchel Batteries,
which stands for Target Identification Sense & Automatic Aim Assistance. Using a grouping of micro-actuators around the adapter cable, and the armored casing made for a heavy base weight of 13.5 kilograms in the bottom half of the backpack,
focusing lens assembly within the rifle, combined with an advanced version of the complex target identification system but the weight of the weapon itself was reduced to a far more manageable 7.5 kilograms. This backpack unit allowed for
first pioneered by Dreadnought’s engineers in the 21st Century, the PAARR-15/GL is essentially a “Smart Rifle”. The the rifle to fire 150 shots before requiring recharge. The adapter cable by itself soon began to see use in adapting the
TISAAA system can identify hostile targets rapidly and alter the aim of the weapon to hit an enemy target with what would PAARR-15/GL IAS to battle armor—such as the Vixen Light Battle Armor—among the Dreadnought BattleCorps and
have otherwise been a missed shot. The TISAAA can only function when firing in single-shot or five-shot-burst mode, and DefenseCorps in 3076.
the degree of automatic target adjustment is limited. Despite its limitations, the system has proven to be the difference
between life and death for many users. In mid-3076—months before the launch of Operation LANCASTER—a proprietary “Cluster Power Pack” designed for
use with the PAARR-15/GL began to be widely distributed to Dreadnought troops, starting with the BattleCorps. This
The TISAAA system has been used by soldiers in the field to great effect in a multitude of ways that the original Cluster Power Pack was based on the unique “Drum Power Pack” used with the Liberator Mk VI Laser Pistol. These new
designers had not intended. An example of an unorthodox use of the TISAAA system has occurred during multiple hostage Cluster Power Packs are roughly a quarter the size and half weight of a standard Satchel Battery, making for far easier
situations. While it is not recommended to be used in such a way, the TISAAA is able to differentiate friend and foe well handling and stowage, but they also had more than six times the charge capacity of even a High Capacity Satchel Battery.
enough that it has been used in hostage situations to target and hit the hostile while avoiding hitting a hostage being Cluster Battery Packs are armored casings that include fifty coin-sized High Capacity Micro Battery Packs, and the total
used as a human shield. It takes time to manually designate the target and the hostage, but once the rifle has this weight of each of these units is just 1.1 kilograms fully loaded. Cluster Power Packs are expensive, at a per-unit cost of
The PAARR-15/GL IAS weighs “just” 9.7 kilograms with two Cluster Power Packs installed, each of which holds enough
charges to fire the weapon 250 times. This combination first saw heavy combat use by the Dreadnought BattleCorps 1st
Regimental Combat Team during Operation LANCASTER—most notably during the siege of Vyrie City. Although many of
the Dreadnought Elite Marines who were deployed as part of the defensive line around the city’s capital during the siege
were killed in action, most of the survivors openly credit the extended capacity of the new Cluster Power Packs and the
accuracy of the TISAAA System as reasons for their survival.
Laser Rifle – Armor Piercing/Base Damage: 4E/5 Grenade Launcher – Armor Piercing/Base Damage: (A)
Laser Rifle – Range: 100/300/600/1200 meters Grenade Launcher – Range: 15/40/90/150 meters
Laser Rifle – Power Points per Shot: 4 Grenade Launcher – Shots: 4
Notes: Single shot or burst 5, 10, or 15; Recoil 0; Includes compact grenade launcher (pump-action reload, 4 round
capacity); +2 bonus to Attack Roll (Laser only, 5-shot-burst maximum); Up to two Satchel-class Batteries simultaneously
or a single backpack unit carrying twin High Capacity Military Power Packs (Encumbering, 3067+). May also use up to two
1.1-kilogram proprietary “Cluster Power Packs” (1,000 charges each), which cost 1,600 C-bills each (3076+).
A High Capacity Micro Power Pack is required to power the helmet, and it will drain one such Micro Power Pack in
approximately 6.6 hours during peak use. The helmet includes slots for nine Micro Power Packs to be used simultaneously
to extend this operational time to 60 hours. A durable, high-quality Combat Knife is sheathed into the side of either shin
as standard. Designed to work in conjunction with the PAARR-15/GL Infantry Assault System, the advanced rifle’s
targeting system can directly interface with the helmet’s heads-up display, allowing direct interaction between the soldier
and the weapon. In addition to creating a weapon sight overlay in the heads-up display for the soldier, this bolsters the
effectiveness of the I.F.F. feature of the rifle’s “TISAAA” smart targeting & tracking system. This is accomplished by utilizing
real-time data from friendly troopers as well as increasing the number of sources of data collected by the rifle. The spine
of the armor is also designed to support the weight of the weapon, which is why the carrying strap of the rifle is designed
to wrap around one of the soldier’s shoulders. As a backup weapon, the choice sidearm of the Dreadnought BattleCorps
Elite Marine is the reliable and versatile Liberator Mk VI Laser Pistol.
The DEMICK made its combat debut during Operation LANCASTER in 3077, where it proved its worth during the fierce
fighting in and around the capital of Vyrie City. Where many other Infantry Kits used by the Great Houses of the Inner
Sphere would have failed to protect the troopers wearing them, the DEMICK body armor reduced the number of potential
casualties considerably. Casualties suffered by Dreadnought’s Elite Marines were still severe, but there is no doubt in the
minds of any of the survivors that the losses would have been far worse without their advanced DEMICK armor.
Notes:
Helmet: Airtight. Laser-Enhanced Military Communicator; Infrared Scanner; Night Vision; Filter Mask; Rangefinder;
Requires HC Micro Power Pack (3PPH), includes nine Micro Power Packs as standard; +2 Perception; AV 8 vs Flash.
Suit: Airtight. Includes combat knife and typically one-or-more days’ worth of rations; compact 15-hour air supply
mounted in lower back section of body armor’s torso in the shape of a cylinder mounted horizontally. Numerous storage
pouches for grenades, tools, and other mission-related equipment.
The middle layer of the suit is composed of thin and lightweight fire-resistant Nomex-VIII. In the case of aerospace The DAPS Kit’s backpack is fitted with a pressurized CO2 gas cartridge installed to instantly purge the bodysuit’s coolant
fighter pilots, this portion of the suit also functions as a G-Suit, with pressure cuffs and air bladders built in. Meanwhile, supply as a pilot begins to eject. This is to prevent coolant poisoning in the event of a suit breach suffered during or after
the outermost layer of the suit is an environmentally-sealed body sleeve that includes the CCS’ part of the collar seal ring, ejection. Fitted into the ejection seat is three spare liters of coolant to replace the lost fluid if the heating or cooling
as well as attachment points for the body armor panels. elements are needed later. If the pilot is unconscious or unresponsive and extreme temperatures are detected, the seat
will automatically inject the replacement coolant and activate the relevant heating/cooling system to sustain the pilot.
Once the multilayered bodysuit of the CCS is fitted to the wearer, lightly armored flexible boots and very lightly armored
gloves are fitted to seal up with the rest of the suit’s body. The heavier, stiffer armor components covering the legs, The DAPS Kit’s combination of sealed construction, integrated life support systems, and insulated/thermally-controlled
forearms, and shoulders are installed, along with the chest piece and integrated backpack. Finally, the helmet/collar bodysuit combine to form a survival suit that can protect the wearer in extreme conditions, up to and including the
assembly is fitted over the head of the user, with the collar component completing the chest armor as it clips into place. vacuum of space. This also means that if a ‘Mech’s cockpit is breached underwater, the pilot is protected from drowning.
Due to the constraints of the six-point restraint harness of the pilot seat—and the pilot seat itself—the placement of While not built into the helmet like the DEMIC Kit, the DAPS Kit includes a military grade communicator housed within
attached accessories such as combat knives and personal sidearms is restricted. The most common location for a personal the ejection seat. Like the DEMIC Kit, in the event of capture, the communicator has an automatic purge subroutine. The
sidearm’s holster is on the front of the thigh. Likewise, the placement of a combat knife’s sheath is either near the radio also has an emergency beacon setting that can be manually activated—and will automatically engage with an
shoulder—on the bicep or the outer edge of the chest piece, so that it does not interfere with the shoulder straps of the altered distress code in the event of the purge subroutine being triggered.
harness—or along the side or front of one of the shins. In any case, these weapons need to be exceptionally well-secured,
as the violence of an ejection can easily cause a loosely-secured item to be knocked free. In addition to the communicator and a limited amount of personally selected supplies, a large survival backpack stored
inside the ejection seat contains the following items, prepacked: a Basic Field Kit, complete with a compact thermal
Much like the DEMIC Kit used by Dreadnought’s Elite Marines, the DAPSK CCS includes a relatively compact, integrated sleeping bag; the micro-refrigeration unit for the DAPSK CCS; filters that can be plugged into the helmet’s ambient air
“backpack” that houses the core of the bodysuit’s life support systems. The backpack features an air supply and filtration vents; a field medical pack; one rifle of choice and ammunition (most commonly a PAARR-15/GL IAS with two fully charged
system that can provide the wearer with up to thirty hours’ worth of breathable air—approximately twice that of the Cluster Power Packs and four 25mm grenades, all preloaded before a mission); a spare combat knife; twenty-four spare
standard DEMIC Kit. The suit’s air supply and recycling/purification system is divided into two horizontally-mounted High-Capacity Micro Power Packs; two additional life support cylinders (each good for 15 hours of life support time); nine
cylinders, stacked vertically, that make up much of the backpack itself. The backpack also includes an adjustable lumbar meals’ each worth of fluid and solid ration packs—the former of which can be consumed without removal of the helmet;
support. When the ULCN is unpowered and has no external oxygen supply, the normally-open vents on the sides of the four one-liter bottles of fresh water; water purification tablets; emergency stims; a basic multipurpose toolset; two
helmet just below the faceplate allow unfiltered ambient air to circulate easily. Once provided with either internal or emergency beacons; and a flare gun with six flares, as well as three conventional long-burn emergency flares.
external power and air supplies, these vents close and prevent contamination of the pilot’s air supply. The proprietary
anti-fog treatment of the faceplate “bubble” prevents any internal fogging in virtually any conditions. The survival backpack is made to fit snugly over the integrated life support pack built into the back of the DAPSK CCS,
with a quick-disconnect latching system designed to attach the backpack to the suit’s back without needing to use the
The ejection seats installed in the ‘Mechs and AeroFighters of the Dreadnought BattleCorps—and the Dreadnought straps to carry it. Alternatively, depending on the user’s preference, the survival backpack’s straps can be used to carry
DefenseCorps, to a lesser but growing extent—are specially designed to suit the DAPS Kit. As it would normally be the pack conventionally with relative ease. Anything not prepacked is designed to easily clip into place on the suit itself.
impractical to wear a backpack like that of the DAPSK CCS while piloting a ‘Mech or AeroFighter, the associated pilot seat
had to be specially designed to fit it. Much of the typical lumbar support area of the seat has been removed, making room A variant of the DAPSK/Dreadnought Spec ejection seat makes the bulky addition of a floatation ring—effectively an
for the bodysuit’s backpack to slip into the gap in the seat’s back and seamlessly interface or “dock” with the seat. Once integrated, tough-skinned inflatable raft—for use in the event of a water landing. Upon completing a controlled ejection
docked with the ejection seat, the backpack feeds directly from the onboard power supply and life support system of the burn and deploying the parachute, the guidance system, gyroscope, propulsion system and propellant tanks are ejected
machine. This allows the suit to not only reserve its air supply for emergency situations, but it can also use the external automatically to reduce weight, and the floatation ring auto-deploys on contact or if it is manually triggered by the pilot.
supplies provided through the seat to recharge its own internal power and air supplies. The UltraLight Combat The floatation ring is nearly four meters in diameter once fully inflated, offering considerable space for the pilot to move
Neurohelmet also connects with the onboard systems of the ‘Mech or AeroFighter through the docked backpack, as does about and access the supplies in the sides of the ejection seat itself. A floatation vest is also added with this version of
the CCS bodysuit’s internal cooling system with the machine’s refrigeration system for the pilot. Additionally, the docking the seat. The original design had attempted to integrate the floatation vest as part of the chest-piece of the CCS, but it
of the backpack to the seat helps to secure the pilot in place that much more firmly and securely—though the standard proved impractical. The installation of this variant of the seat is difficult and time consuming, limiting it to mission-specific
six-point pilot restraint/harness is still required. Due to the size and fitment requirements of the specialty pilot/ejection applications only. (Additionally, any ‘Mech equipped with this automatically gains the “Cramped Cockpit” quirk.)
seat used with the DAPS Kit—it is significantly bulkier than a conventional ejection seat—only Dreadnought-manufactured
machines can equip them without considerable modification (‘Mechs and AeroFighters modified to meet what is referred Development of the DAPS Kit is ongoing, with additional functions being added over time. An upgrade currently being
to as “Dreadnought Spec” standards will have undergone such modifications). developed for both the DAPS Kit and the DEMIC Kit is an integrated water reclamation system that utilizes the built-in
Notes:
Helmet (DAPSK UltraLight Combat Neurohelmet/ULCN): Airtight. Infrared Scanner; Night Vision; Rangefinder. ULCN’s
optical functions require HC Micro Power Packs (3PPH), six pre-installed as standard. +1 Perception; AV 8 vs Flash.
Suit (DAPSK Combat Coolant Suit/CCS): Airtight. Integrated Life Support System w/2x15-hour cylinders; Integrated
Heating System, requires HC Micro Power Packs (3PPH), six pre-installed as standard. Optional Pistol and/or Combat Knife.
Ejection Seat (DAPSK Standard): Heavy Duty Backpack; Basic Field Kit; Climbing/Rappelling Kit; Basic Tool Kit; Medical
Kit; Military Communicator; One Fully-Loaded Rifle w/2-4 Magazines/Power Packs; Combat Knife; Filtration Masks (2); HC
Micro Power Battery Packs (24); Spare 15-hour Life Support Cylinders (2); Emergency Rations (Solid & Fluid, 9 each); Four
Liters Bottled Fresh Water; Water Purification Tablets (10); Three Liters Spare Coolant; Electronic Compass; Emergency
Beacons (2); Flare Gun (6 flares); Conventional Flares (3); Emergency Stims (10); Micro-Refrigeration Unit, requires HC
Micro Power Packs (3PPH), three pre-installed as standard.
Some of the battle armor types used by the Dreadnought BattleCorps and DefenseCorps—such as the Vixen and Kitsune—are largely produced for export sales by Dreadnought Interstellar Industries.
However, the BattleCorps employs some heavier battle armor types and even a handful of ProtoMechs that appear to be bespoke to themselves—or, at the very least, are rarely seen outside of their
ranks. The mass-produced export designs are already potent and dangerous by any standard, but the machines that Dreadnought has kept to themselves have proven to be even more so.
189 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
DII-VX-BA-X1 VIXEN LIGHT BATTLE ARMOR
hand can be used to aim the weapon, but the weapon pod itself needs to be The Dreadnought BattleCorps lost a handful of these suits during the
installed on the shoulder corresponding with the preferred hand. The second fighting on Ashkum IV in 3077, but their numbers have since been rebuilt.
option for the weapon pod, the -X2 variant, is a Heavy Grenade Launcher. Although no other significant engagements have been recorded specifically
The installation and removal of the third option, the -X3, is slightly more involving Vixen Light Battle Armor, they no doubt have seen considerable use
involved. It replaces the entire gun-pod with a Light Recoilless Rifle. The -X3 during the Word of Blake Jihad elsewhere in the Inner Sphere. Vixens have
also adds a Battle Claw to whichever hand the trooper is not using to aim the proven to best serve as peripheral harassers, especially in environments such
weapon, allowing the trooper to more effectively latch onto enemy ‘Mechs as cities and mountainous terrain. They make best use of their jump capacity
and perform swarm attacks. by constantly leaping from cover to cover to maximize the difficulty in hitting
them, though this often necessitates alternating between targets every time
Having entered production in mid-3074, it was less than three years they jump from point to point. Given the speed with which they can cover
before the Vixens of the Dreadnought BattleCorps 1st RCT saw heavy action difficult terrain, Vixens have also proven to be effective rapid-response units
during Operation LANCASTER in 3077. The Vixen Light Battle Armor squads when ‘Mechs and combat vehicles are unavailable. However, because of
fighting to defend the HPG building at the capital of Vyrie City on Ashkum IV their exceedingly light armor, troopers operating these suits should be
spent most of the siege constantly jumping between buildings and generally cautious when directly engaging most enemy battle armor types without
changing positions as frequently and rapidly as possible. During the fighting, support—not to mention heavier combat vehicles or ‘Mechs.
the Vixens proved that their slim profiles and high mobility were their keys
to success when fighting in the city. Many of the BattleCorps’ Vixens were Variants
damaged before the end of the siege, but the losses taken by the squads of
Vixen Light Battle Armor were relatively light when compared to the squads DII-VX-BA-X2 (Heavy Grenade Launcher) – The Vixen Light Battle Armor has
in the same area using the slower and heavier Kitsune Medium Battle Armor. three known primary variants, all of which can be quickly swapped back and
forth thanks to the modularity of the weapons mount designed into the suit.
Mass: 750 kg Due to the limitations and restrictions on operator size leaning more The -X2 is armed with a combination David Gauss Rifle and Heavy Grenade
Chassis: VXBA Generation 1 Light specifically toward female and lithe male users, the Vixen is arguably the Launcher, packaged into an over-under assembly almost identical to the
Power Plant: DreadTech MiniFus Type 132 Power Pack least-popular design ever produced by Dreadnought Interstellar in terms of more popular -X1 variant and its twin David Gauss Rifles. This version of the
Maximum Speed: 10.8 km/h export. All the Great Houses of the Inner Sphere have purchased them, but Vixen is otherwise unmodified from the -X1. (Battle Value: 23; 83/3, 122/4,
Jump Jets: PreciHop 584 Light-BA w/Jump Booster only in limited numbers. The number of Vixens sold to the Successor States 165/5, 212/6) Features the following Design Quirks: Modular Weapons.
Jump Capacity: 120 meters would not have made the creation of the design financially feasible were if
Armor: StealthyDread BA-Type-4 Stealth Armor not for the Dreadnought BattleCorps themselves making excellent use of it. DII-VX-BA-X3 (Light Recoilless Rifle) – As the designation suggests, the -X2 is
Armament & Equipment: However, the largest buyer of the Vixen Light Battle Armor turned out to be armed with a single Light Recoilless Rifle for ranged combat. The removal and
2 Type 148-A “David” Gauss Rifles none other than the Magistracy of Canopus, who, without a battle armor to installation of the Light Recoilless Rifle is more involved than the other
Manufacturer: Dreadnought Interstellar Industries call their own as of 3085, felt that the Vixen represented their state well. weapon options, but it is still a quick swap. Additionally, this variant replaces
Primary Factory: Goldsmith Armored Wardrobe BA Facility; Acala III one of the armored gloves with a Battle Claw to aid in swarm attacks. It is up
Communications System: D-Comm BA V1.8 Capabilities to the user’s personal preference as to which glove is replaced. The -X3 is
Targeting & Tracking System: Pinpoint Compact-A1 otherwise identical to the -X1 variant. (Battle Value: 27; 97/3, 141/4, 189/5,
With its surprising agility and impressive 120-meter jump range, 244/6) Features the following Design Quirks: Modular Weapons.
Overview Dreadnought Interstellar Industries’ DII-VX-BA-X1 Vixen Light Battle Armor is
by far one of the most mobile battle armor suits ever created. Armed with DII-VX-BA-X4(X) (Anti-Personnel Gauss Prototype) – This Vixen Light Battle
The DII-VX-BA-X1 Vixen Light Battle Armor began development in 3071, twin David Gauss Rifles, the Vixen can snap off multiple shots in rapid Armor variant is a direct upgrade from the -X1. The twin David Gauss Rifle
just six months after the DII-KT-BA-X1 Kitsune Medium Battle Armor did. The succession into enemy infantry and armor alike. Unfortunately, in the event assembly is replaced directly with Dreadnought Interstellar Industries’ own
Vixen was designed to be an ultra-high-mobility stealth unit with as slender of accurate return fire, the protection provided by the Vixen’s armored shell duplicate of the Clan-developed Anti-Personnel Gauss Rifle. This weapon is
a profile as possible to maximize the effectiveness of what little armor the is limited at best, with just 240 kilograms of standard battle armor class based almost directly on the units installed in Ceòlmhor Heavy Battle Armor,
suit had. The desire to minimize the suit’s profile as much as possible resulted Stealth Armor protecting the trooper inside. but it has a more compact construction. The original intent of this revised
in the suit’s frame undergoing numerous redesigns until a balance between variant was to include an upgrade to Improved Stealth Armor, but due to
structural integrity and compact size was finally reached. The final shape of There are also significant limitations on the size of the troopers that can packaging constraints within the compact suit, this proved to be impractical.
the suit is undoubtedly feminine in nature, and although it is by no means a fit in the suit, which absolutely rule out its use by Elementals or other “bulky”
requirement, most Vixen Light Battle Armor troopers tend to be female. individuals. The slenderer the build of the user, the easier the suit is to use. Although still in the prototype phase as of 3085, it is all but guaranteed
Ironically, while the intent had not been to emphasize the suit’s use by that all active Vixen Light Battle Armor suits used by the Dreadnought
The repeated leaping back and forth with the Vixen’s jump jets and the female troopers, that was exactly the result of the suit’s final design. BattleCorps and DefenseCorps will be upgraded to this specification once
speed with which the suit changes direction has proven to be quite taxing on development has been completed. However, with more recent reports of a
the stamina of the trooper using it. Given the thinner nature of the suit’s Additional Information new “Vixen II” Light Battle Armor in development, the BattleCorps will likely
frame, as well as the demands of its operation, the Vixen Light Battle Armor be replacing their original Vixens with the newer second-generation units,
is better-suited for more agile, lithe, athletic users—especially those who Vixen Light Battle Armor suits are used by military forces across the Inner once the Vixen II becomes available. (Battle Value: 35; 126/3, 182/4, 245/5,
have trained with an emphasis on endurance over brute strength. Sphere, including the armies of the Great Houses, the Periphery, and 315/6) Features the following Design Quirks: Modular Weapons.
independent units alike—but only to a limited extent. Meanwhile, the
Three different armament options were created that, should the need Magistracy of Canopus has seen fit to import these suits by the DropShip- Additional Notes: A common practice to augment the combat effectiveness
arise, could be quickly interchanged in the field. The first option—designated load, and as of 3085, the Magistracy is believed to have multiple times as of the Vixen Light Battle Armor is to equip the suit with a PAARR-15/GL
the -X1—incorporated a pair of David Gauss Rifles into a single assembly that many of these suits serving in their own military forces as most of the rest of Infantry Assault System, as the heavy rifle can be handled easily with one
could be aimed almost like a pistol with either of the user’s hands. Either the Inner Sphere combined. hand by a powered battle armor suit such as the Vixen, once a modification
These threats have seemed to snap the troublesome Elementals into line,
making clear that violent slugging matches between the former Clan warriors
should only be for matters that simply cannot be decided another way—and
ensuring that they only resort to it when they feel it is absolutely necessary.
In the end, it appears that this has struck an exceptional balance between
what is expected of an Inner Sphere soldier, while still allowing the former
Clan warriors to express themselves in the manner they were taught for most
of their lives. This has not been lost on Colonel Ann Lawrence. The Colonel
initially questioned Kabir’s methods in private, but she has since come to
accept that Kabir has an unusually effective knack for dealing with the former
Clan troopers, and the Colonel supports her completely.
The model design of the Ceòlmhor Heavy Battle Armor is a design created by
Jason Spykerman as a commission for Devin Ramsey based on Devin’s
original art, and the Copyright is owned by them. Mr. Spykerman’s Facebook
page “Orbital Heavy Industries” can be found here:
https://www.facebook.com/orbitalheavyindustries/
Even when they were successfully spotted in the ferrocrete jungle of the As Dreadnought Interstellar Industries has historically not tended to
city, the Breakwater suits were so durable that they survived direct hits from export their more powerful designs that utilize Clan technology, it is possible
Gauss Rifles, although the Capacitor-boosted Clan Extended Range Particle that this variant may go into production under the chassis variant code of
Projector Cannons being fielded by the 55th Shadow Division did prove to be “-BC1”, rather than the “-X3” that the designated experimental chassis code
an effective one-shot kill. Fortunately for the BattleCorps, the Manei Domini “-X3(X)” would normally suggest. (Battle Value: 90; 324/3, 467/4, 628/5,
MechWarriors were slow to realize that the nearly invisible battle armor 808/6) Features the following Design Quirks: Difficult to Maintain.
could survive hits from such deadly weapons.
Related Designs
Capabilities
Kanazuchi Assault Battle Armor – Breakwater units often register as
With its astonishingly durable shell made from state-of-the-art Mimetic Kanazuchi when their mimetic armor is disengaged. The reasons for this are
Armor, the Breakwater Assault Battle Armor is one of the toughest battle twofold—the design bears a none-too-subtle resemblance to the Kuritan-
armor types ever created. Able to survive a direct hit from a Gauss Rifle and designed Kanazuchi, and most battle computers do not have the Breakwater
still capable of enduring further punishment before failing, the Breakwater in their identification registry, leading to a common misidentification.
Mass: 2,000 kg is a praiseworthy piece of engineering indeed. Groundspeed is a modest ten
Chassis: BWBA Type 3 AssaulTrooper kilometers per hour, but speed is not the focus of the design. In fact, the slow Notable Troopers
Power Plant: DreadTech MiniFus Type 132 Power Pack speed of this battle armor only aids in the function of its Mimetic Armor. The
Maximum Speed: 10.8 km/h slower it moves, the harder it is to see or detect on sensors. As a result, a Captain Kent Jones – DII-BW-BA-X2 Breakwater Assault Battle Armor: Not
Jump Jets: None static defense position is an ideal application, because for all intents and much is known about Captain Kent Jones’ history, although intelligence
Jump Capacity: 0 meters purposes, the Breakwater can hide in plain sight. reports suggest that the man might have once been a member of the
Armor: DII-Mi Mk 2.1 BA-Class Mimetic Armor Federated Suns’ special forces.
Armament & Equipment: The Breakwater is primarily armed with a pair of shoulder-mounted
2 Federated-Barret Magshot Gauss Rifles Magshot Gauss Rifles, backed by a Flamer installed in the right arm. This Jones seemingly materialized out of nowhere in August of 3075—
1 Infernal Hellfire Type D Flamer combined armament results in a versatile machine, with the Magshots giving immediately following the assault on Theris—swearing his allegiance to
Manufacturer: Dreadnought Interstellar Industries medium-range punch while the Flamer offers solid close-range damage Colonel Ann Lawrence so long as she promised to strike back at the Word of
Primary Factory: Goldsmith Armored Wardrobe BA Facility; Acala III potential against vehicles and infantry alike. Both arms feature Heavy Battle Blake. Investigations discovered that Kent Jones was the brother of Ezra
Communications System: D-Comm BA V1.9 Claws to assist in melee combat should the need arise. Jones—the Colonel in command of the D.B.C. Trinity when the vessel was
Targeting & Tracking System: Pinpoint Compact-A1 destroyed while defending the world of Theris against a Blakist assault in
Additional Information June of 3075. Worse still for Kent Jones, his mother, father, and two sisters
Overview had all been among the civilians not yet evacuated before the assault. He
Since its introduction, the Breakwater Assault Battle Armor has become a would later learn that his family had all elected to decline offers of early
The Breakwater Assault Battle Armor was first designed in 3073, and the design associated with the Dreadnought BattleCorps and DefenseCorps, who evacuation, not wishing to be given special treatment.
first prototypes were built on Theris (Waycross II) in early 3075. These were commonly employ these battle armor suits when defending a stationary
destroyed during the Word of Blake assault on Theris in June the same year. target. Intel reports indicate that Breakwaters have begun to be fielded by During Operation LANCASTER in 3077, Captain Jones’ squad, known as
Newly-built production models of this design first emerged on Acala III in Davion and Steiner forces, but as of 3085 these have yet to see widescale “The Gargoyles”, cut down close to eighty of the Word of Blake’s enhanced
early 3076, as Dreadnought continued to lick its wounds after the attack. deployment. infantry attacking the capital—Jones killing half that number by himself. His
These new units included all-new technology that not used in any previous ferocity in combat only further spurred those under his command and those
battle armor built by Dreadnought Interstellar Industries. The Blackwood As a result of their significant contribution to the development of the around him to greater levels of heroism in combat. After witnessing the
Templars Mercenaries salvaged several examples of Purifier Medium Battle Breakwater’s design, several examples of this machine have recently been terrifying effectiveness of the Breakwater Assault Battle Armor in combat—
Armor from the Word of Blake following a repelled Blakist attack on the added to the Blackwood Templars Mercenaries’ arsenal. especially Captain Jones’ Gargoyles—members of the Blackwood Templars
Templars’ homeworld of Son Hoa in September, 3074—where the Templars’ Mercenaries jokingly nicknamed them “Murderer Battle Armor”.
considerable aerospace assets eventually forced the Blakists to withdraw. Variants
Jones’ actions were critical in the defensive efforts of the Dreadnought
Utilizing the Purifiers salvaged by the Templars, Dreadnought Interstellar DII-BW-BA-X1(X) (Prototype) – The prototypes destroyed on Theris in 3075 BattleCorps’ regular infantry and battle armor troops in the face of their
was able to reverse-engineer the Mimetic Armor used in the Purifiers and were nearly identical to the -X2 production model except for being equipped opposite number from Word of Blake’s 55th Shadow Division. However, he
apply the technology to Dreadnought’s own assault-class battle armor during with basic BA-type armor of comparable integrity. They were also much less blames himself for the loss of many of the troops under his command—and
its continuing development. The DII-BW-BA-X2 Breakwater Assault Battle refined than the production variants. (Battle Value: 69; 248/3, 361/4, 487/5, many of those who were around him during the fighting—as he feels that, in
Armor was the resulting production model. This revised design experience 626/6) Features the following Design Quirks: Prototype. the heat of the moment, his own lust for revenge against the Word of Blake
its combat debut during Operation LANCASTER on Ashkum IV in early 3077, led him to be far more reckless than he should have been. Despite his regrets,
to startling effect. The powerful and absurdly durable Breakwater troopers DII-BW-BA-X3(X) (Anti-Personnel Gauss Prototype) – While still under he remains the commander of the 5th Irregular Battalion’s Sigma Company
aided considerably in the defense of the capital during the assault by the development as of 3085, it is believed that this more powerful variant of the as of 3085—a position he has held since 3076.
The Dreadnought BattleCorps—and more recently the DefenseCorps—utilize several highly advanced BattleMech and OmniMech types manufactured by Dreadnought Interstellar industries. Most
are adapted from existing designs that continue to be manufactured primarily for export, but a few are entirely new designs, purpose-built to serve in Dreadnought’s own military forces. These
powerful machines are enhanced with Clan-tech-based equipment, materials, and weaponry, as well as all-new technologies developed in-house by Dreadnought Interstellar themselves.
204 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
DII-QUN-O QUENN LIGHT OMNIMECH
follow common themes for ease of maintenance and operational efficiency; salvaged—which is unlikely, given how the BattleCorps operates—or a
one or more Short Range Missile systems (and sometimes enhanced configuration other than the known four BC-Series examples has been
electronics) installed in the torso, coupled with a right-arm-mounted energy created, but has not yet been made public knowledge.
weapon. Useful for varied, specialized tasks, the Quenn is arguably the best
example of Dreadnought Interstellar Industries’ use of Omni-technology in a Virtually never seen operating independently, if a Quenn is spotted, it is
light ‘Mech chassis, even if it is also considered the “weakest” of the three almost a guarantee that at least one or two more are nearby, although the
production light ‘Mech types fielded by the Dreadnought BattleCorps. others are not necessarily equipped identically. Often, a lance of Quenn
OmniMechs will be diverse in their configurations, as each of them can help
The Quenn can be equipped to operate as a rapid-deployment long range to compensate for the shortcomings of the others.
sniper and harasser, with enough punch to worry even the largest of
opponents—then, in a matter of hours, can be reconfigured as a close-range Configurations
brawler, with a heavy emphasis on targeting infantry and battle armor. Just
as quickly, it can be reconfigured to be a pinpoint striker with the ability to BC-A – The BC-A or “BattleCorps-Alpha” configuration—which is referred to
designate targets for artillery and semi-guided munitions. The Quenn has as the “Sniper” configuration—was the basis upon which the Quenn was
proven able to provide solid performance across the board, although with originally designed. It features a Sniper-Blazer IX Extended Range Large Laser
the significant drawback that most configurations are rather specialized, and installed in the right arm, backed by a Double-Take Version 3 Short Range
without the downtime to swap the weapons loadout around, it has difficulty Missile 2-rack mounted on the top of the left torso—fed by a single ton of
adapting to a role other than the one intended. This critical drawback, as well ammunition. Like all known BC-Series Quenn OmniMech configurations, the
as a handful of other issues, is what led to the development programs for the BC-A is equipped with a Dreadnought TDN System, and its ammunition is
Ravage and Ravage II Light OmniMechs being launched all but immediately protected by the chassis’ integrated Clan-tech Cellular Ammunition Storage
after the Quenn entered service. Equipment. While not terribly devastating, the BC-A has enough range and
punch to be of concern to even the largest enemy unit, allowing the Quenn
After the Ravage and Ravage II Light OmniMechs were introduced in 3073, BC-A to either act as a decoy or a long-range harasser. In either role, the BC-
Mass: 20 tons the Quenn remained in reduced production until the destruction of the A has shown itself to be nuisance with its ability to hit from a long distance
Chassis: OHI Special Type-C QUN-20/33ESC Endo Steel w/Integrated CASE Cameron MechWerks facility on Theris in 3075. It is unclear if Dreadnought and fade quickly, disappearing before the enemy can close in.
Power Plant: Orbital Heavy Industries OHI-180XLC ExtraLight Fusion Engine Interstellar will resume production elsewhere in the future or not. Although
Cruising Speed: 97.2 km/h it appears the Quenn OmniMech is gradually being phased out from use in BC-B – The BC-B is known as the “Spotter” configuration. This version of the
Maximum Speed: 151.2 km/h the Dreadnought BattleCorps, it still sees active use in the DefenseCorps. Quenn retains the missile system of the BC-A but features a Flash-Sword VII
Jump Jets: None Extended Range Medium Laser in the right arm. The BC-B is unique in that it
Jump Capacity: 0 meters Capabilities carries an Angel Electronic Countermeasures Suite, installed in the center
Armor: QUN-Pattern Dreadnought ExoShield Ferro-Fibrous Armor torso, providing this variant of the Quenn with superb electronic warfare
DII-QUN-O Fixed Equipment & Base Pod Space: The DII-QUN-O Quenn Light OmniMech has three configurations that are capacity. Most importantly—and the reason why this configuration is
7 tons of pod space available relatively specialized: the BC-A “Sniper”, the BC-B “Spotter”, and the BC-C referred to as the “Spotter” configuration—the BC-B mounts a Target
DII-QUN-O BC-C (Pictured) Armament & Equipment: “Close-Support/Anti-Infantry”. Meanwhile, the BC-D configuration is Acquisition Gear package in the right torso, allowing it to designate targets
4 Double-Take Version 3 Short Range Missile 2-Racks considered a “General-Purpose” unit. As is typical of Dreadnought’s “BC- for guided munitions and artillery strikes. This configuration is designed for
1 Laserwerks Strobe Type 2 Extended Range Small Pulse Laser Series” ‘Mechs and combat vehicles, all known Quenns are equipped with pinpoint, medium-range maneuvers, as it is meant to get somewhat close to
1 Dreadnought BC Special Mk-II Target Data Networking System Dreadnought’s own Target Data Networking (TDN) System. This allows the enemy to designate targets. The BC-B is the least-armed variant of the
Manufacturer: Dreadnought Interstellar Industries friendly “Linked” units to share targeting telemetry and increase weapons- Quenn, but it still packs enough firepower to at least contend with most
Primary Factory: Cameron MechWerks Facility; Theris (Waycross II) accuracy when firing on a target in closer proximity to a friendly Linked unit— lightly-armored opponents that may get in its way.
Communications System: Interconn-Comm VII (TDN System Compatible) much like a C3 Network, but without susceptibility to jamming by hostile
Targeting & Tracking System: Pinpoint-Series TTS electronic countermeasures. The TDN System also generates a short-range BC-C – The “BattleCorps-Charlie” Quenn is the Close-Support/Anti-Infantry
electronic countermeasures bubble, or it can serve as a short-range Active configuration. The BC-C is the brute of the Quenn lineup. Instead of mounting
Overview Probe, although these secondary functions cannot operate simultaneously. just a singular SRM rack like the BC-A and BC-B configurations, the BC-C packs
a total of four Double-Take Version 3 Short Range Missile 2-racks, mounted
The Quenn Light OmniMech was created during a transitionary phase for The Quenn is fast, but it is fragile, even if it is covered in as much armor as in pairs in the side torsos. Each side torso also houses a full ton of CASE-
the Dreadnought BattleCorps and began production in late 3071. The Quenn its engineers could manage pack on—a total of three-and-a-half tons of equipped ammunition. It is a common practice to have one of the two tons
was designed to be a multirole-capable lightweight combat platform, and to- Dreadnought’s own ExoShield Ferro-Fibrous Armor plating. Regardless of of missiles be dedicated to specialty munitions—most commonly Inferno-
date it is the quickest machine to develop from the design floor to production configuration, the Quenn is exceptionally heat efficient, and never has to type missiles. Like all other configurations of this OmniMech, the BC-C
by Dreadnought Interstellar. Capable of speeds exceeding 150 km/h, the worry about overheating unless it is operating in remarkably hot configuration Quenn features a single energy-based weapon installed in the
Quenn is an effective reconnaissance machine regardless of configuration. It environments while being continuously pushed to the limit—a confidence- right arm—in this case, a Laserwerks Strobe Type-2 Extended Range Small
is well-armored for a 20-ton ‘Mech, but it relies much more on its speed, inspiring aspect that any MechWarrior can appreciate. Pulse Laser.
agility, and compact size rather than its armor to protect it from harm. The
Quenn is designed to be so compact that two of these machines can be fitted Additional Information This configuration is a solid unit to deploy around slower-moving ‘Mech
into a single DropShip ‘Mechbay cradle, where normally only one ‘Mech can and vehicle assets. This was originally considered to be a generally useful unit
allocated for transport, allowing Recon Lances of Quenn Light OmniMechs to As of this writing, no Quenn has been confirmed to have been seen to deploy in urban or canyon-type environments. However, between the
be transported with much greater efficiency. operating outside of the Dreadnought BattleCorps or DefenseCorps forces, Quenn’s lack of jump jets and the later introduction of the highly jump-
although unsubstantiated reports do exist that suggest otherwise. If true, it capable Ravage II, this role has largely fallen to the newer, more deadly
The Quenn’s weapons configurations have some diversity, but all of them is possible that either some of these machines have been either stolen or machine whenever it is available.
The Ravage and Ravage II Light OmniMechs are visually identical in many BC-B – The only known alternate configuration of the Ravage II in active use
respects, and they even share the same armor allocation. However, the five- by the Dreadnought BattleCorps as of 3085 is the BC-B. Though rarely
ton-heavier Ravage II features a lightly reinforced chassis and a set of eight employed, this is a slightly more complex version of the ‘Mech, designed to
Kangaroo Model VII jump jets, which are installed in tightly-grouped sets of serve as an anti-armor and anti-infantry unit in mountainous or urban
four in each side torso. The large wing assemblies built into the side torsos environments. It replaces two of the four Extended Range Medium Lasers
just above the shoulders are the most significant visual difference between with a pair of Extended Range Small Lasers and a pair of Flamers. Like the BC-
the two generations of Ravage OmniMech. From some angles, the wings A, the lasers are tied to an Enhanced Pinpoint Version-V Targeting Computer.
look more like they belong on an aircraft—or even aerospace fighter—rather
Mass: 30 tons than on a ‘Mech. Hinged at the bases, these Partial Wing assemblies can fold BC-C(X) – As of 3085, the BattleCorps-Charlie (Experimental) configuration is
Chassis: OHI Special Type-C RVG-2-30/51ESC Endo Steel w/Integrated CASE downward for easier transportation or when the wings are not needed for still undergoing testing. This configuration of the Ravage II features a pair of
Power Plant: Orbital Heavy Industries OHI-240XLC ExtraLight Fusion Engine longer-distance jumping. This articulation allows the Ravage II to jump in and the new Improved Heavy Medium Lasers being developed by Dreadnought
Cruising Speed: 86.4 km/h out of heavily wooded areas with ease, as the wings deploy as soon as the Interstellar Industries. These new weapons are based on examples first built
Maximum Speed: 129.6 km/h ‘Mech clears the treetops and then fold in to avoid catching on trees when by the Blackwood Templars Mercenaries. Tucked under the Improved Heavy
Jump Jets: Kangaroo Model VII w/Partial Wing landing. This also reduces the ‘Mech’s normal target profile considerably. Medium Laser in each side torso is an Extended Range Medium Laser.
Jump Capacity: 240 meters (300 meters) Improved accuracy comes courtesy of the Enhanced Pinpoint Version-V
Armor: RVG-2-Pattern Dreadnought ExoShield Ferro-Fibrous Armor The armament of the exceptionally jump-capable DII-RVG-2-O Ravage II Targeting Computer. The BC-C(X) is a purpose-built hit-and-run design that—
DII-RVG-2-O Fixed Equipment & Base Pod Space: Light OmniMech is quite simple in all its configurations—especially when due to the severe waste heat produced by its weapons—is limited to jumping
6.5 tons of pod space available compared to most other ‘Mechs produced exclusively for the Dreadnought into range with a target, firing, and then jumping away to cool down.
DII-RVG-2-O BC-A (Pictured) Armament & Equipment: BattleCorps. In both configurations that the Ravage II has been deployed in,
4 Flash-Sword VII Extended Range Medium Lasers the ‘Mech specializes in short-to-medium-range engagements. As with the Notable Pilots
1 Dreadnought BC Special Mk-II Target Data Networking System BC-Series configurations of the Ravage Light OmniMech, the BC-Series
1 Enhanced Pinpoint Version-V Targeting Computer Ravage II configurations are equipped with Dreadnought’s own Target Data Captain Sienna “Red-Eye” McLaren – DII-RVG-2-O Ravage II “Defiance”: The
Manufacturer: Dreadnought Interstellar Industries Networking (TDN) System. This allows it to share its targeting telemetry with diminutive Sienna McLaren has a rather striking figure—athletic, though
Primary Factory: Dreadnought MechFoundry; Acala III friendly Linked units. The TDN System also includes a short-range Electronic shapely—with full, dark brown hair and amber-orange eyes that appear
Communications System: Interconn-Comm VII (TDN System Compatible) Countermeasures Suite or—should the situation require it—the ECM almost red under certain light. Born on Skye, this smaller woman was the
Targeting & Tracking System: Enhanced Pinpoint Version-V T.C. function can be deactivated in favor of a limited-range Active Probe. child of two retired members of the Fourth Skye Rangers. Her mother, a
former Jenner pilot, and her father, a former Spider pilot, had been
Overview With only 3.5 tons of Dreadnought ExoShield Ferro-Fibrous Armor, the lancemates for years before the two became engaged all but overnight
survival of a Ravage II Light OmniMech is dependent on agility and mobility following their nearly simultaneous retirements. Both parents had been the
Although the DII-RVG-O Ravage Light OmniMech was extremely promising to prevent being hit, as the thin armor provides limited protection at best. products of long lines of MechWarriors in service of House Steiner. Raised in
in early testing, it soon became clear that it still suffered from similar Thankfully, this ‘Mech has enough jump capacity and agility to make it one such a military household, Sienna and her two brothers were all but expected
difficulties as the Quenn Light OmniMech that it was meant to succeed: harsh of the hardest-to-hit ‘Mechs ever built. As mobility well and truly is the name to grow up to be MechWarriors, continuing the family tradition.
terrain slowed it down far too much. As a result, a jump-capable “winged of the game when it comes to the Ravage II, it comes as little surprise that
twin” soon joined the Ravage in testing. Together the two evolved, each the MechWarriors selected to operate these machines are generally quite When her older brothers washed out of the Nagelring, her parents’ hopes
pushing the other to become excellent war machines. Entering production exceptional when it comes to their piloting skill ratings. rested squarely on her shoulders—and, unlike her brothers, Sienna McLaren
at different points in 3073, the Ravage and Ravage II soon became the did not disappoint. Graduating the academy with honors in 3058, she was all
Dreadnought BattleCorps’ most iconic light OmniMechs. Additional Information but immediately assigned to the secret Task Force Bulldog, as a member of
the 10th Lyran Guards, where she piloted her mother’s Jenner—refitted to
The winged Ravage II was first deployed in real-world combat conditions Although designed to be employed exclusively by the Dreadnought JR7-F specifications and affectionately known as “Flashbulb”. Even as a
in 3077, during Operation LANCASTER. It immediately left its mark when the BattleCorps, rumors have recently begun to circulate that the Ravage II relative “FNG”, McLaren proved herself an exceptional MechWarrior to her
Dreadnought BattleCorps’ Ravage IIs leapt back and forth, using the dense might go into production for export by 3088. However, it certainly would not superiors in the 10th Lyran Guards—and an even greater scout-in-force pilot.
Hope for the project faded rather sharply after a similar chassis failure was Encased in nine tons of Dreadnought ExoShield Ferro-Fibrous Armor, the
suffered by the second prototype, even though significant reinforcements Crusher is relatively well protected for its weight, but packaging constraints
had been added. Despite this, the engineers insisted that it was possible to have led to the incorporation of weapons being mounted to the OmniMech’s
make a better version of the chassis using Clan-developed materials— Partial Wing. Unfortunately, this does create potential for problems, namely
materials that Dreadnought had recently acquired the ability to produce. that if the Partial Wing itself is damaged, the weapons mounted there may
After months of lead engineer Gerard Francis constantly bothering anyone be damaged or lost altogether as a result.
who he could pull into a conversation about giving the Crusher project
another chance, he was given approval. Strangely, instructions were given to As with all known examples of Dreadnought’s machines that feature a BC-
Mass: 55 tons Francis to build the third prototype as an OmniMech. As a result, Crusher Series chassis variant or configuration code, the “BattleCorps-Series” Crusher
Chassis: OHI Special Type-C CRR-55/91ESC Endo Steel w/Integrated CASE prototype number 03 was not only the testbed for a renewed attempt to configurations include Dreadnought’s Target Data Networking (TDN) System.
Power Plant: Orbital Heavy Industries OHI-275XLC ExtraLight Fusion Engine build a ‘Mech equipped with a Partial Wing, but the design was also the This allows the Crusher to network with friendly Linked units similarly to a C3
Cruising Speed: 54.0 km/h company’s first foray into building an OmniMech chassis, making the project Network, but with its own unique advantages and disadvantages.
Maximum Speed: 86.4 km/h useful even if the Partial Wing segment of the prototype ultimately failed.
Jump Jets: Kangaroo Model VIII w/Partial Wing Additional Information
Jump Capacity: 150 meters (210 meters) To the delight of all involved, prototype 03 did not fail. In fact, using the
Armor: CRR-Pattern Dreadnought ExoShield Ferro-Fibrous Armor better materials for construction—in addition to reinforcing the chassis with Used all but exclusively in the Intercept Lances of the Dreadnought
DII-CRR-O Fixed Equipment & Base Pod Space: a revised bracing configuration within the machine’s ‘spine’—worked quite BattleCorps when it was introduced, the Crusher is a rare sight—and
20.5 tons of pod space available well to make the chassis’ structure remarkably sound. However, the unfortunately only becoming more-so as the limited production machine’s
DII-CRR-O BC-A (Pictured) Armament & Equipment: reworking of the Crusher did not end there, but in fact continued into numbers dwindle with the loss of each example in battle. According to a
2 Reacher-Series Long Range Missile 10-Rack redesigning the actuators and myomer bundle layout with the help of former report filed in 3085, the total number of these machines still in the service of
4 Laserwerks Strobe Type 7 Medium Pulse Lasers Clan scientist Douglas Malone, whose continued work extended into Dreadnought’s military forces are less than thirty. Because of its increasing
1 Dreadnought BC Special Mk-II Target Data Networking System completely redesigning the shock-absorption characteristics of the legs. rarity and specific parts requirements, the remaining examples of Crusher
1 Enhanced Pinpoint Version-V Targeting Computer OmniMechs have all been reassigned to Dreadnought DefenseCorps units.
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite All the painstaking work of the engineers collectively allowed the Crusher
Manufacturer: Dreadnought Interstellar Industries OmniMech prototype to be remarkably successful and durable in testing. The It should be noted that, as of this writing, rumors have begun to circulate
Primary Factory: Cameron MechWerks Facility; Theris (Waycross II) redesigned prototype was so successful that one of its chief test pilots—Jerry that KSND Industries—the Crusher’s original manufacturer—might be
Communications System: Interconn-Comm VII (TDN System Compatible) Peterson—became stuck with the nickname of “Bouncer” for how rapidly, attempting to recreate the Crusher LAM (Land-Air ‘Mech) utilizing a
Targeting & Tracking System: Pinpoint-Series TTS roughly, and awkwardly he jumped the machine around trying to break, just combination of newer Inner Sphere and Clan-based technologies.
to have it take all the punishment he had to offer and seem to ask for more.
Overview Configurations
All throughout the testing phase of the third Crusher prototype, different
While “on loan” to Task Force Serpent, serving as reinforcements for some weapons were slotted in and out of the OmniPods whenever the ‘Mech was BC-A – At long range, the “BattleCorps-Alpha” configuration Crusher’s fairly
of the various units associated with the Task Force, many members of the down for service or inspection, allowing Dreadnought Interstellar Industries’ light long-range armament of twin Reacher-Series Long Range Missile 10-
Dreadnought DefenseCorps Theris Regiment experienced and saw many technicians and engineers to learn more and more about how to use an racks tend to leave the ‘Mech seeming rather underwhelming. This is
unique and curious things—from fighting ProtoMechs to inspecting Clan OmniMech chassis platform most efficiently. Eventually, after live-fire especially true as it only has enough ammunition to fire twelve volleys before
scientific facilities. One of the things that stood out as having potential to be testing had concluded, a few relatively ideal weapons systems configurations running out of missiles. However, long range combat is not what the BC-A
expanded upon was the Partial Wing used in House Kurita’s Kage Light Battle were selected. Though it faced delays outside of the engineering team’s Crusher configuration is primarily designed for. With its quartet of Clan-tech
Armor. After seeing the Partial Wing assembly on the back of the scout suit, control, the Crusher OmniMech eventually reached production-ready status. LaserWerks Strobe Type-7 Medium Pulse Lasers coupled to an Enhanced
the idea was spawned for Dreadnought’s engineers to create a similar piece Pinpoint Version-V Targeting Computer, this medium OmniMech takes
of equipment—but for a BattleMech. Years later, the Crusher was the first With its chassis officially designated as DII-CRR-O, the first production- advantage of its mobility to hunt down light- and medium-class enemy units
attempt at integrating a Partial Wing into a full-fledged ‘Mech chassis. model Crusher OmniMech was created and assembled in the Cameron over rough or even nearly impassable terrain, then tear apart its targets with
MechWerks facility on the world of Theris (Waycross II) in October of 3071. exceptionally accurate laser-fire. The BC-A configuration is also equipped
The reason the Crusher was chosen as the testbed for the new design It continued to be produced until the facility’s destruction in 3075 during the with an Angel Electronic Countermeasures Suite to jam hostile missile locks
feature was simple: it was originally developed by KSND Industries to be a infamous Word of Blake assault on the planet. As of 3085, it is unclear if and C3/C3i Networks—and scramble enemy communications—all while
Land-Air ‘Mech. Unfortunately, like all of the Land-Air ‘Mech designs of old— production of the Crusher will ever restart on Acala III or not, as the tooling helping to ensure that the Crusher itself is protected from suffering similar
even the ones that are far better known than this ill-recognized 55-ton for the Crusher was unable to be removed before the facility was destroyed. hinderances.
Although the Fusillade Flak Tank has long been the Dreadnought Nearly two weeks were wasted trying to get the Garret targeting system The Oryx -BC2’s cooling system is arguably the design’s “Achilles’ Heel”.
BattleCorps’ standard for anti-air artillery purposes, the slow, ponderous to correctly interact with the powerful autocannons, as well as struggling to Though the Dreadnought-made, Clan-tech-enhanced Rotary Autocannon/5s
assault tanks left much to be desired in terms of mobility and versatility— get the system to appropriately connect to the Dreadnought Target Data cannot fire as rapidly as the Mydron units installed in the -1FC variant that
especially given how resource-intensive the more recent BC-Series Fusillades Networking (TDN) System altogether. Finally, one of the engineers realized the -BC2 is directly based on, the combination of the energy weapons and
proved to be. By spring of 3075, even as the Rotary-Autocannon-equipped that the third, and final, “key factor” to the project’s success had been staring autocannons can quickly overheat this ‘Mech when pushed to the limit. So
-BC2 variant Fusillade had begun to roll off the assembly lines on Acala III, it the team in the face from the start. The -BC2 Fusillade Flak Tank was long as the pilot is mindful of this issue, however, the -BC2 Oryx can be a
became clear that a better option was needed. equipped with the same Type A10 Rotary Autocannons, and they worked consistently devastating war machine.
perfectly well with the targeting system it used. While not exactly a “plug
However, resources available for developing and manufacturing an all new and play” installation, once it had been adapted for the new application, the Though slower than the earlier proposed -BC1(X) variant of the Oryx, as
anti-air artillery platform were limited at best. The evacuation of the world Pinpoint Version-IV-AAA Targeting & Tracking System from the Fusillade was the -BC2 is powered by a 240-rated powerplant instead of the 300-rated unit
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3
Engine: 240 Fusion XL 6
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 201 10.5
Internal Armor
Structure Value
Head 3 9
Center Torso 20 32
Center Torso (rear) 8
R/L Torso 14 22
R/L Torso (rear) 6
R/L Arm 10 20
R/L Leg 14 28
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3.5
Engine: 325 Fusion XL 12
Walking MP: 5
Running MP: 8
Jumping MP: 4 4
Heat Sinks (Double): 18 (36) 8
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 192 10
Internal Armor
Structure Value
Head 3 9
Center Torso 21 30
Center Torso (rear) 9
R/L Torso 15 22
R/L Torso (rear) 7
R/L Arm 10 20
R/L Leg 15 23
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3.5
Engine: 350 Fusion XL 15
Walking MP: 5
Running MP: 8 (10)
Jumping MP: 0
Heat Sinks (Double): 17 (34) 7
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 211 11
Internal Armor
Structure Value
Head 3 9
Center Torso 22 33
Center Torso (rear) 9
R/L Torso 15 23
R/L Torso (rear) 7
R/L Arm 11 22
R/L Leg 15 28
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3.5
Engine: 350 Fusion XL 15
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks (Double): 15 (30) 5
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 211 11
Internal Armor
Structure Value
Head 3 9
Center Torso 22 33
Center Torso (rear) 9
R/L Torso 15 23
R/L Torso (rear) 7
R/L Arm 11 22
R/L Leg 15 28
The model designs of the Lancer “Memory Knight” and Lancer “GunKnight”
are original copyrighted creations by Jason Spykerman and are used with
permission. Mr. Spykerman’s Facebook page “Orbital Heavy Industries” can
be found here: https://www.facebook.com/orbitalheavyindustries/
Production of the -BC1 Reckoning halted in mid-3074, as evacuation of the Notable Pilots
population and facilities in the Waycross system began—which included the
dismantling of the Cameron MechWerks facility on Theris (Waycross II). The Lieutenant Alex Davros – DII-RCK-BC1 Reckoning “Second Chance”: Alex
pause was brief, however, as production restarted in 3076 on Acala III. The Davros is a Caucasian male of average height with prematurely graying hair
first units off the production line were soon used in Operation LANCASTER. and blue eyes. A native of Acala III, Davros was born in 3038 into a lower-
middle-class family, with parents who had met while they were serving as
Unfortunately, the new Magna-Rail-16B series of Gauss Rifles—which had logistical support personnel in the Acala III Planetary Defense Militia. Alex
been installed in all the newest -BC1 Reckoning BattleMechs—were soon idolized his uncle Jamie from a young age, as Jamie had been a MechWarrior
discovered to be defective. While the defect was not catastrophic, it resulted of House Davion during the War of 3039, piloting an AWS-8V Awesome.
in an inevitable capacitor failure after repeated discharges. This caused the Davros’ earliest childhood memories are of wanting to be a MechWarrior.
electromagnetic propulsion systems to fail to engage, leaving the weapon
useless. After the first surface battle of Operation LANCASTER, the defective Unfortunately, an accident at a young age left Alex Davros with both legs
Mass: 85 tons Gauss Rifles were removed and replaced with tried-and-true Magna-Rail-15 amputated just above the knee. Too poor for quality prosthetics, the aspiring
Chassis: Dura-Frame II Standard RCK-85/130S w/Integrated CASE units. The reliable Magna-Rail-15 has since been the choice Gauss Rifle for all young MechWarrior was forced to come to terms with his dreams being
Power Plant: Orbital Heavy Industries OHI-340XLC ExtraLight Fusion Engine BattleCorps and DefenseCorps forces. crushed long before he had a chance to realize them. He slowly came to
Cruising Speed: 43.2 km/h accept that he would likely follow in the footsteps of his parents, serving as
Maximum Speed: 64.8 km/h Capabilities logistical support for Acala III’s planetary defense militia once he was old
Jump Jets: Kangaroo Model IX enough to serve the compulsory military service required of all of Acala III’s
Jump Capacity: 120 meters When the -BC1 Reckoning restarted production on Acala III, the -BC2 was citizenry. He received a good education, and despite his circumstances, he
Armor: RCK-Pattern Dreadnought Titan-Plate Standard Armor introduced alongside it. The -BC2 is based on the jump-capable -O2 series of studied very hard. He was well-liked by his peers and was considered an
Armament & Equipment: variants made for export, but with more advanced weaponry and electronic extremely good friend to just about all who knew him.
3 Thunderstruck XV Extended Range Particle Projector Cannons warfare suites. As with the -BC1 variant, the -BC2 is protected by 15.5 tons
1 Dreadnought BC Special Mk-II Target Data Networking System of Dreadnought’s own Titan-Plate Standard Armor, and it features an Angel Knowing it was the closest he would ever get to experiencing his lifelong
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite Electronic Countermeasures Suite that allows it to jam hostile missile locks dream, Davros frequented the ‘Mech-sims at the local arcade whenever he
Manufacturer: Dreadnought Interstellar Industries and nearby enemy communications—including C3 Networks. could. He was such a regular that the arcade’s owners allowed him to create
Primary Factory: Dreadnought MechFoundry; Acala III his own customized machines to use in the sims. A chance encounter there
Communications System: Interconn-Comm VII w/TDN System Armed with a trio of Clan-tech Thunderstruck XV Extended Range Particle in 3055 changed the direction of his life forever.
Targeting & Tracking System: Pinpoint Version-IV Projector Cannons, the -BC2 Reckoning can deal significant damage at range,
while making great use of its jump jets to reposition quickly between salvos. Davros had not left the simulator for well over an hour, participating in
Overview With a total of twenty-five double heat sinks, this BattleMech can fire all its several consecutive battles, piloting his customized, Supercharger-equipped
weapons continuously, only needing to occasionally rest its jump jets to AWS-9M Awesome. Nearly twenty minutes into a tense engagement, Davros
Dreadnought Interstellar Industries’ Reckoning Assault BattleMech was bleed off some excess heat. As a result, the -BC2 Reckoning is a textbook managed to personally take out two of the three enemy ‘Mechs that had
already a formidable war machine when it was introduced in 3056. However, example of a “jump sniper”. With the added advantage of their Dreadnought been downed by his lance. He then learned that he was the sole remaining
more powerful “BC-Series” variants made exclusively for Dreadnought’s own Target Data Networking (TDN) Systems, the BC-Series Reckonings can fire pilot of his lance-sized team. Every opponent in this match had been more
military forces began to be produced in late 3071. These newer machines from range with impressive accuracy when providing direct fire support for challenging than anyone he had faced before, but somehow that only pushed
were built using advanced Clan technology and manufacturing methods with friendly Linked units that are engaging the enemy at closer range. him to perform better than ever. Coming face-to-face with his last opponent,
the help of several former Clan scientists who were brought back from Clan Davros was faced with the greatest challenge he had ever encountered. His
space with the Dreadnought BattleCorps in 3066—as well as the addition of Variants opponent was piloting a customized black and red Mad Cat—one that Davros
Alex Davros to the development team as a test pilot, the following year. happened to notice resembled a machine that had made headlines after a
DII-RCK-BC1 – The first BC-Series Reckoning is built on a bespoke CASE-II- foiled pirate attack on Acala III two years prior. It was moving with an almost
As one of Dreadnought’s early forays into building machines using all Clan- equipped Orbital Heavy Industries Special Type-C RCK-85/130ESC Endo Steel impossible grace through a wooded area as it shifted to flank his Awesome.
based technology, the manufacturer took a more conservative approach to chassis. However, the -BC1 shares the -BC2’s armor, head-mounted TDN
the design and construction of these new BattleMechs, while at the same System, OHI-340XLC powerplant, and Angel ECM Suite. The visibly damaged Mad Cat, already missing much of its right side, was
time trying to make best use of the new resources and technology. At first using its remaining missiles to suppress the Awesome as it maneuvered for a
considered a competitor to the DII-SMR-O Sumaire OmniMech, which was Armed primarily with a pair of arm-mounted Thunderstruck XV Extended better position to engage. Davros chose to deny his opponent the chance to
being developed at roughly the same time, the new DII-RCK-BC1 Reckoning Range Particle Projector Cannons and a Magna-Rail-15 Gauss Rifle installed gain any such advantage. Instead of holding back behind cover to avoid the
At last report, Mercier’s youngest son is training at the Acala III Military
Academy. He shows great promise to be a skilled aerospace fighter pilot.
Equipment Mass
Internal Structure: Standard w/C-CASE 8.5
Engine: 340 Fusion XL 13.5
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Double): 25 (50) 15
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 248 15.5
Internal Armor
Structure Value
Head 3 9
Center Torso 27 38
Center Torso (rear) 13
R/L Torso 18 27
R/L Torso (rear) 9
R/L Arm 14 28
R/L Leg 18 30
After learning that the Blakist regime had been responsible for attacks on Capabilities
multiple branches of Dreadnought—both corporate and military—the mega-
corporation turned its assets inward to prepare for the seemingly inevitable The Sumaire Assault OmniMech has an exceptionally broad operational
conflict with the Blakists. The Dreadnought BattleCorps 1st RCT became the range for a machine originally designed for such a specific task. It has quite
focus of these preparations. The BattleCorps had been historically successful respectable groundspeed for an assault ‘Mech and has armor coverage that
with the use of existing standard-issue military equipment, a small portion of rates as among the best of its weight class. With its various configurations of
Mass: 95 tons which had been upgraded using advanced Clan technology. However, it was powerful weapons systems and electronic warfare suites, the Sumaire is a
Chassis: OHI Special Type-C SMR-95/145ESC Endo Steel w/Integrated CASE clear the BattleCorps needed more than captured, adapted, and lightly true powerhouse on the battlefield. It comes as no surprise that the Sumaire
Power Plant: Orbital Heavy Industries OHI-380XLC ExtraLight Fusion Engine upgraded equipment if they were to contend with the likes of the Word of has arguably become Dreadnought’s most iconic assault ‘Mech—with only
Cruising Speed: 43.2 km/h Blake. They needed equipment specifically built to combat the Blakist threat. the Neugen understandably rivalling it in this regard.
Maximum Speed: 64.8 km/h This fact was emphasized in 3069 with the BattleCorps’ near-crippling defeat
Jump Jets: None at the hands of the Word of Blake’s 55th Shadow Division on Basalt IV. The Spin-Werx Type A10 Rotary-5 Autocannon was originally created and
Jump Capacity: 0 meters developed primarily with the Sumaire OmniMech in mind. However, this
Armor: SMR-Pattern Dreadnought Titan-Plate Standard Armor In late 3070, just over a year after the choice was made to upgrade the powerful, rapid-fire weapon system—even with its impressive range—was
DII-SMR-O Fixed Equipment & Base Pod Space: Dreadnought BattleCorps 1st RCT’s machines, the first of the new ‘Mechs overshadowed by the development of the radical new “OmniBow” series of
37 tons of pod space available and vehicles created for the BattleCorps entered production. For most of Streak-fire Advanced Tactical Missile systems. The 12-tube OmniBow missile
DII-SMR-O BC-A (Pictured) Armament & Equipment: these new “BC-Series” machines—built to meet what has become known as systems have since become all but synonymous with this OmniMech, as they
2 OmniBow Streak Advanced Tactical Missile 12-Racks “Dreadnought Spec” standards—Dreadnought Interstellar took their existing are prominently featured in its “Primary” BC-A and BC-A2 configurations. The
4 Laserwerks Strobe Type 7 Medium Pulse Lasers production-model designs and completely reworked them from the ground OmniBow missile systems are capable of outranging nearly anything else on
1 Scorched-Earth Type 2 Flamer up with Clan technology to create even more powerful war machines. These the battlefields of the 31st Century, short of full-fledged artillery. As a result,
1 Dreadnought BC Special Mk-II Target Data Networking System formidable new machines were developed by Dreadnought’s best engineers the Sumaire OmniMech can inflict moderate damage on hostiles before most
1 Enhanced Pinpoint Version-V Targeting Computer working side-by-side with former Clan scientists. Most of Dreadnought’s can hope to return fire. With its Dreadnought Target Data Networking (TDN)
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite current military machinery resulted from this collaborative effort. System, the Sumaire can use shared targeting telemetry supplied by friendly
Manufacturer: Dreadnought Interstellar Industries Linked scouts to get an “easy shot”, even at remarkably long range.
Primary Factory: Dreadnought MechFoundry; Acala III Two of the heaviest initial ‘Mech designs built for the BattleCorps were
Communications System: Interconn-Comm VII (TDN System Compatible) the Sumaire and Neugen Assault OmniMechs. Although the BattleMechs on With a deep ammunition store and multiple warhead types for use at
Targeting & Tracking System: Pinpoint VariTrac-Series TTS which these two were based were introduced decades apart, these new different ranges for its powerful 12-tube missile systems, backed by a quartet
powerhouse OmniMechs were specifically designed to operate together. The of arm-mounted Clan-tech medium-class lasers tied to an Enhanced Pinpoint
Overview Neugen OmniMech was purpose-built as a command-oriented machine with Version-V Targeting Computer, the Sumaire only becomes more dangerous
powerful long-range weaponry. Meanwhile, the Sumaire OmniMech was the closer an enemy gets. For instance, in either BC-A or BC-A2 configuration,
In 3066, three Dreadnought Interstellar executives and members of their primarily designed as an effective “area denial” machine built to serve as a the Sumaire can demolish a full third of even a pristine Atlas’ armor in a single
families were targeted and assassinated by an agent hired by the Word of defensive “companion” for the Neugen. In many of its configurations, the salvo at close range, and it can keep delivering that level of punishment
Blake. At the time, the assassin escaped capture. Two years later, on 22 Sumaire serves as an extremely heavily armed escort, built primarily to constantly without risk of overheat until it runs out of ammunition. Even if a
December, 3068, George Fitzgerald—Dreadnought Interstellar Industries’ engage at short-to-medium-range, with some longer-range support capacity. hostile ‘Mech survives a full barrage, most pilots on the receiving end will
president and Baron of Acala III, the “Homeworld of Dreadnought”—was The Sumaire ensures that any hostile that manages to break through to typically find themselves with a particularly stunning view of either the sky
Equipment Mass
Internal Structure: Standard w/C-CASE 10
Engine: 300 Fusion XL 9.5
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 15 (30) 5
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 307 19.5
Internal Armor
Structure Value
Head 3 9
Center Torso 31 44
Center Torso (rear) 18
R/L Torso 21 30
R/L Torso (rear) 12
R/L Arm 17 34
R/L Leg 21 42
The model design of the Mattock (used here as the Mattock II) is a
copyrighted original creation by Kirk Alderfer, Zach Braham and “Maddog”.
It is used here with permission. Mr. Alderfer’s Shapeways store “Arbron
Imagineering” can be found here:
https://www.shapeways.com/shops/arbron_imagineering/
Dreadnought Interstellar Industries has a long history of pushing the limits of aerospace engineering. However, prior to the mid-3050s, the greatest weakness of the Dreadnought BattleCorps was
arguably their limited aerospace assets—especially their AeroFighter support. Hard lessons, learned both vicariously and first-hand, have since been taken to heart. The BattleCorps now wields an
impressive array of advanced and powerful aerospace assets, ranging from state-of-the-art tactical satellites and support craft to devastating aerospace fighters and exceptional DropShips.
260 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
CLAIRVOYANCE TYPE-V TACTICAL SATELLITE
exposes the satellite to a far greater risk of detection. The configuration of Type: Clairvoyance Type-V Tactical Satellite
the data transmissions can be altered remotely but the signal to alter the Classification: Medium Satellite (Mass Production)
setting does increase the risk of detection of both the user and the satellite. Tonnage: 30
Equipment Rating: C/D-E-D/D
With its extended onboard fuel supply—capable of lasting approximately
four hundred days—the Clairvoyance Tactical Satellite generally requires Dimensions
minimal maintenance. If a campaign lasts longer than a standard year, Length: 8 meters
however, a commander must be aware that the satellite will soon require Width: 4 meters
refueling to remain active. Height: 3.5 meters
The searchlight mounted on the aft section of the Clairvoyance is present Equipment Mass
purely for the satellite to have a powerful visual signal beacon for Chassis/Controls: 6.5
maintenance crews to find it and for retrieval operations. The beacon will Engine/Trans: Fusion 4.5
only activate if triggered by the appropriate access code. If too many Station-Keeping Thrust: 0.1G (0.2 Thrust)
erroneous access code entries are detected or antitamper programming is Structural Integrity: 1
triggered, the satellite may initiate an “Asset Denial Protocol”—a self- Heat Sinks: 0 0
destruct sequence—overloading its power core and maneuvering system, Fuel: 400 Days 2
resulting in the satellite severely damaging itself and sending the remaining Armor Factor (BAR 10): 19 3
components hurtling into the atmosphere to burn up on re-entry. Armor
Value
The Asset Denial Protocol must have its trigger parameters set and be Nose 4
enabled before the satellite is deployed. It cannot be remotely enabled. The R/L Side 5
The Clairvoyance Type-V Tactical Satellite is commonly used by Davion and Asset Denial Protocol can be configured to include a small internal explosive Aft 5
Steiner forces alike. The satellite’s was first introduced shortly after the device if one is installed, ensuring destruction of onboard data and other
alliance between the Federated Suns and Lyran Commonwealth to form the critical internal systems, and preventing virtually any chance of recovery. Electronics & Onboard Systems Location Tonnage
Federated Commonwealth in the early 31st Century. High-Rez Imager Camera Nose 2.5
While hardly considered tough, the Clairvoyance has sufficient armor with Infrared Imager Camera Nose 5
The creation of the Clairvoyance was originally commissioned in 3025 by a Class-10 Barrier Armor Rating to survive a single hit from a light autocannon Communications Equipment Body 6
none other than “The Fox” himself, Hanse Davion. It was later learned that or a standard Medium Laser to its sides or aft sections. However, such a hit Mounted Searchlight Aft 0.5
the commissioning of this design was in preparation for the coming Fourth to the front of the satellite—assuming the armored cover doors are open—
Succession War that lasted from 3028-3030, where the compact satellite’s will destroy it instantly. Cargo & Other Equipment: Optional Explosive Charge (for use with Asset
minimal sensor profile helped to prevent it being detected in orbit by Denial Protocol).
opposing Capellan Confederation forces. The Clairvoyance Type-V Tactical Satellite is still being produced in 3085 at
Dreadnought Interstellar Industries’ SatComm Manufacturing Facility on Additional Notes: Features Armored Chassis and Controls Modification; the
The Clairvoyance was designed to be deployed into orbit by DropShips Acala III. With the help of Orbital Heavy Industries, the Clairvoyance received Mounted Searchlight is used as a beacon when triggered.
preparing for planetfall, and it can be all but literally blown out an airlock an upgrade in 3073 that included a more efficient powerplant and power
during maneuvering to begin descent into the planet’s atmosphere. After distribution system, as well as a more sensitive sensor array that improved
being ejected from a DropShip, a five-ton single-use thruster attached to the the resolution of the data collected by the satellite by nearly fifteen percent.
front of the satellite handles the task of rapid deceleration. The RCS thrusters
establish a stable orbit before the single-use thruster is jettisoned. With the As of 3085, most Clairvoyance satellites are in use by Houses Steiner and
disposable thruster detached, the cover doors on the front of the satellite Davion. However, a not-insignificant number of them found their way into
can finally be opened, revealing the forward-facing array of sensors and Kuritan hands during Operation BULLDOG—and a handful of older units were
cameras. captured intact by Liao during the Fourth Succession War.
Once in stable orbit and activated, the Clairvoyance offers friendly troops
exceptional optical and thermal views of the planet’s surface, as well as an
impressive ability to track opposing troop positions and movements.
The Vertigo was never intended for mass production, having originally been planned for a limited production run of
approximately fifty units. Because of how effective the fighter proved itself to be as a rapid strike craft, however, the
number of Vertigos that have been produced is several times the original planned production run. Until 3082, all of these
craft were specifically built for use by the Dreadnought BattleCorps and DefenseCorps forces. In 3082, however, a limited
production export model was introduced. Data collected by Comstar suggests that there is a new variant of this fighter
that has just begun development and testing as of 3085, but no further information is yet available.
Capabilities
Impressively fast and nimble, the Vertigo Light Aerospace Fighter is counted among the most agile and quickest
AeroFighters ever to be produced. Powered by an Orbital Heavy Industries OHI-280XLC Clan-tech ExtraLight Fusion
Engine, the Vertigo is capable of acceleration rates up to 7.5-G. With a mere four tons of fuel, however, the pilot of a
Vertigo must be cautious not to become too heavily mired in a battle for too long, or risk being forced to break off abruptly
when the fuel supply runs low.
Mass: 35 tons
Chassis: Crossplane VTG-9 w/Integrated CASE Armed primarily with a Thunderstruck XV Extended Range Particle Projector Cannon, backed by a pair of Flash-Sword
Power Plant: Orbital Heavy Industries OHI-280XLC ExtraLight Fusion Engine VII Extended Range Medium Lasers—all housed together in the nose of the craft—the Vertigo brings a considerable
Armor: VTG-AS-Pattern Orbital Heavy Industries Special Type-C Ferro-Aluminium Armor forward-firing punch. With only a single Short-Beam IV Extended Range Small Laser serving as a rear-firing defensive
Armament & Equipment: weapon, it is admittedly not the most heavily defended against an opponent that manages to outflank it—however, given
1 Thunderstruck XV Extended Range Particle Projector Cannon the craft’s sheer speed and maneuverability, the chances of this are relatively slim. The armament is reminiscent of the
2 Flash-Sword VII Extended Range Medium Lasers larger BC-Series Sabretooth Heavy Aerospace Fighters, but this is not without good reason. The engineers worked hard
1 Short-Beam IV Extended Range Small Laser to simplify the logistical requirements needed to operate these craft simultaneously, in terms of repair and maintenance.
1 Dreadnought BC Special Mk-II Target Data Networking System
Manufacturer: Dreadnought Interstellar Industries As with other BC-Series fighters that the Vertigo is designed to operate alongside, it is equipped with a Dreadnought
Primary Factory: J.S. Space Superiority Labs; Acala III Target Data Networking (TDN) System to assist with making accurate strafing runs by using shared targeting telemetry
Communications System: Interconn-Comm VII provided by Linked ground units. The TDN also offers improved communications and limited electronic countermeasures
Targeting & Tracking System: Pinpoint Version-IV-ASF capabilities. With thirteen double heat sinks, the Vertigo can constantly operate at or near peak efficiency without issue.
Though built largely with speed and maneuverability in mind, the Vertigo can survive considerable punishment for a
Overview fighter of its class, thanks to its seven-ton shell of Orbital Heavy Industries’ Special “Type-C” Ferro-Aluminium Armor.
With the introduction of the Word of Blake’s deadly Spectral Series OmniFighters, it quickly became clear that the Additional Information
formidable Steel Cobra Heavy Aerospace Fighter could not stand on its own as the sole aerospace fighter type utilized by
Dreadnought’s military forces. There needed to be supplemental craft of different weight classes and capabilities to Used primarily as high-speed harassers, interceptors, and reconnaissance craft, the Vertigo Light AeroFighter quickly
maximize the potential of Dreadnought’s BattleCorps and DefenseCorps Aerospace Fighter Wings. Two new aerospace become a favorite among Dreadnought BattleCorps and DefenseCorps forces, and dozens of these craft are used by the
fighters were created in the mid-3070s to fulfill these requirements. These new “BC-Series” or “Dreadnought Spec” Dreadnought BattleCorps 1st Regimental Combat Team. As of 3085, however, the reported proliferation of these fighters
AeroFighters, were the Vertigo Light Aerospace Fighter and the Sabretooth Medium Aerospace Fighter—the latter of among the Dreadnought DefenseCorps forces in the Acala system is wildly greater—to the point of seeming almost too
which was a significant upgrade of a preexisting design, while the former was an all-new craft inspired by a captured Clan severe for the reports to be accurate—with indications that at least seventy examples of this craft have been assigned to
AeroFighter which had been uniquely modified for one of Dreadnought’s pilots. each of the four orbital defense platforms orbiting the Dreadnought homeworld of Acala III.
Purpose-built initially for use by the Dreadnought BattleCorps, but later adopted by DefenseCorps forces, the Vertigo Variants
was developed to serve as a multirole light attack, intercept, and reconnaissance aerospace fighter. Introduced in 3074
and created all but directly in response to the Shade Light OmniFighter—one of the potent Spectral Series OmniFighters DII-VTG-AS-BC2 – Made for dogfighting, much like the DII-SBT-AS-BC2 Sabretooth, the -BC2 variant of the Vertigo drops
favored by the Word of Blake’s Manei Domini—the Vertigo matches or exceeds the Blakist fighter in nearly every way. the long range punch of the nose-mounted Particle Projector Cannon to add three more Flash-Sword VII Extended Range
Medium Lasers, for a total of five—with one installed where the PPC was, and one mounted to each wing. The -BC2 also
The design of the Vertigo was heavily influenced by the modifications done to the Chaeronea Light Aerospace Fighter upgrades the rear-mounted ER Small Laser to a Laserwerks Strobe Type 2 Extended Range Small Pulse Laser. Significant
known as “Spicy”. Dreadnought Interstellar Industries took what had been learned when the unique fighter was modified improvements to the targeting & tracking system are made via an Enhanced Pinpoint Version-V-ASF Targeting Computer.
and applied it to an all-new fighter design meant for production. The resulting craft, the Vertigo, is remarkably fast and The -BC1’s thirteen double heat sinks, seven tons of Ferro-Aluminium Armor, and the TDN System are retained in the
powerful for its weight. It has proven itself capable of not only outmaneuvering, outrunning, and at times even outgunning -BC2. (Battle Value: 2,112) Features the following Design Quirks: Dreadnought Spec (Tier-2)*, Modular Weapons.
the best that the Word of Blake had to offer, it can also outrange most of the Blakist fighters with its Clan-derived
Extended Range Particle Projector Cannon. These advantages are even more important because of the one significant DII-VTG-AS-X1 – This is one of the few examples of Clan-tech machinery produced for export by Dreadnought Interstellar
shortcoming that the Vertigo has in comparison to its Word of Blake counterpart: it only has eighty percent of the fuel Industries. Introduced in 3082, the DII-VTG-AS-X1 Vertigo is effectively a refined version of the prototype originally
capacity of the Shade. As a result, the Vertigo is required to be deployed closer to the fighter’s intended target and it developed in 3073. The -X1 Vertigo Light Aerospace Fighter has found limited use in some Great House militaries, but the
cannot last quite as long in a prolonged dogfight. This flaw was not an issue that surfaced as being truly problematic until largest purchaser has been the Raven Alliance. Aside from its advanced Targeting Computer, the -X1 Vertigo features no
the final space battle of Operation LANCASTER in 3077, where many of the Vertigos assigned to the D.B.C. Phoenix, advanced electronics worthy of note. It is armed with a trio of Flash-Sword VII Extended Range Medium Lasers in the nose
running low on fuel, were forced to break off shortly before the battle’s conclusion. It was fortunate that the BattleCorps’ and a Laserwerks Strobe Type 7 Medium Pulse Laser in each wing, as well as twin tail-mounted Short-Beam IV Extended
Equipment Mass
Engine: 280 Fusion XL 8
Safe Thrust: 10
Maximum Thrust: 15
Internal Structure: 10
Heat Sinks (Double): 13 (26) 3
Fuel: 320 4
Cockpit: Standard 3
Armor Factor (Ferro-Aluminium): 134 7
Armor
Value
Nose 44
R/L Wing 33
Aft 24
Weapons and Ammo Location Tonnage Heat SRV MRV LRV ERV
ER PPC Nose 6 15 15 15 15 –
2 ER Medium Lasers Nose 2 10 14 14 – –
ER Small Laser Aft 0.5 2 5 – – –
Dreadnought TDN System* Fuselage 1.5 2
With the introduction of the Word of Blake’s Spectral Series OmniFighters in the early 3070s, it was decided that the
Steel Cobra Heavy Aerospace Fighter could not rule the skies and stars by itself as Dreadnought’s sole AeroFighter type.
The Steel Cobra, though formidable and multi-mission-capable to say the least, was expensive and still had its own
limitations. To support the Steel Cobra and give Dreadnought greater numbers, two additional AeroFighters were created.
In 3072, development began on the first “Dreadnought Spec”, or “BC-Series” AeroFighter engineered specifically for
Dreadnought’s own military forces: the all-new Vertigo Light Aerospace Fighter. Just a year later, new BC-Series variants
of the Sabretooth Medium Aerospace Fighter began development as well. Both craft simultaneously began production in
3074. Though less varied in terms of armament compared to the Steel Cobra, these new fighters proved to be just the
added support that the Steel Cobra so desperately needed, rounding out Dreadnought’s aerospace assets nicely.
Capabilities
The DII-SBT-AS-BC2 Sabretooth Medium Aerospace Fighter is among the most aggressive medium-class AeroFighters
ever devised. It is fast enough to quickly bring its medium-range weapons array to bear on a target and, with thirteen
tons of Ferro-Aluminium Armor, it has more than enough protection to survive the punishment it may endure while
closing in on its enemy. In combat, the -BC2 Sabretooth is the definition of a brutal dogfighter craft. Armed with an array
of ten forward-firing Flash-Sword VII Extended Range Medium Lasers—all tied to an Enhanced Pinpoint Version-V-ASF
Targeting Computer—the Sabretooth can deliver a devastating barrage with impressive accuracy. With just a single Short-
Beam IV Extended Range Small Laser to act as a rear defense weapon, the Sabretooth’s engagement capabilities outside
of its forward firing arc are limited at best, but the craft is agile and capable enough that this is rarely cause for concern.
While most aerospace fighters and ‘Mechs that mount the kind of firepower that the Sabretooth carries are generally
prone to suffering from severe heat management issues, such is not the case with this craft. Twenty-six double heat sinks
cool the Sabretooth, allowing it full use of its weapons systems without any risk of excess heat buildup. If supporting
Mass: 65 tons ground troops, the Dreadnought Target Data Networking (TDN) System allows the pilot of this fighter access to targeting
Chassis: Winged-Fang Series 12 SBT-AS w/Integrated CASE telemetry supplied by Linked ‘Mechs and combat vehicles on the ground. This shared targeting telemetry considerably
Power Plant: Orbital Heavy Industries OHI-325XLC ExtraLight Fusion Engine improves precision and effectiveness during strafing runs on ground targets near friendly Linked units. However, if a TDN
Armor: SBT-AS-Pattern OHI Special Type-C Ferro-Aluminium Armor Control Unit is not present among the Dreadnought ground forces, the fighters cannot be Linked into the TDN network.
Armament & Equipment:
10 Flash-Sword VII Extended Range Medium Lasers Additional Information
1 Short-Beam IV Extended Range Small Laser
1 Dreadnought BC Special Mk-II Target Data Networking System The mass-production Y-Series variants of the Sabretooth have proven to be successful in military forces across the Inner
Manufacturer: Dreadnought Interstellar Industries Sphere, with the -Y1 being a particular favorite among cash-strapped mercenary units and Periphery-based militaries.
Primary Factory: J.S. Space Superiority Labs; Acala III Following the introduction of the craft’s BC-Series variants to Dreadnought’s Aerospace Fighter Wings, the Sabretooth
Communications System: Interconn-Comm VII has become a favorite—especially as it is half the cost of a Steel Cobra and requires considerably less maintenance.
Targeting & Tracking System: Enhanced Pinpoint Version-V-ASF Targeting Computer
Variants
Overview
DII-SBT-AS-Y1 – Introduced in 3008, the first-generation Sabretooth is armed with a pair of Kinslaughter Particle Projector
With an almost alien-looking silhouette and heavy armament, the Sabretooth Medium Aerospace Fighter is a design Cannons installed in the nose and a Magna Mk II Medium Laser mounted to each wing. A single aft-mounted Magna Small
that a pilot tends to not forget after their first hostile encounter with one—assuming they survive it, that is. Introduced Laser is installed to provide some limited measure of point defense in the fighter’s rear arc. The cooling system’s twenty-
in 3008, Dreadnought Interstellar Industries’ Sabretooth appeared on the open market rather suddenly, with no prior three single heat sinks are nearly enough to keep up with the demands of the craft’s weapons when operating at
information regarding the craft’s development having been publicized. It was later learned that the Sabretooth had maximum output, but gradual heat buildup is a very real concern when pushed. This variant of the Sabretooth is powered
existed as a classified prototype created for the Star League Defense Force shortly before the Star League’s collapse. The by an InterFus 260-rated Fusion Engine for a maximum acceleration capability of 4.5-G. The -Y1 is protected by thirteen
“alien” silhouette had been the direct result of an experimental AeroFighter cloaking technology being developed by tons of standard armor. (Battle Value: 1,311) Features the following Design Quirks: Easy to Maintain, Rugged.
Dreadnought in conjunction with the SLDF. The cloak itself was a boondoggle, but the fighter was a sound design; it just
never completed development due to the failed cloak system. The prototypes were mothballed, and the design shelved. DII-SBT-AS-Y2 – Two updated variants of the Sabretooth Medium Aerospace Fighter were introduced in 3055, designated
-Y2 and -Y3, respectively. Both feature a more powerful 325-rated ExtraLight Fusion Engine, a recent development by
Just after the turn of the 31st Century, the Sabretooth was finally put into production thanks to a commission by House Orbital Heavy Industries at the time, improving the craft’s acceleration considerably. The -Y1’s paired Kinslaughter Particle
Davion’s Armed Forces of the Federated Suns for an affordable, upper-medium-to-heavy space superiority fighter. Given Projector Cannons are upgraded to Johnston High Speed Extended Range units, and the number of Medium Lasers
that most of the engineering had been completed centuries prior, and the design itself was still sound, Dreadnought mounted to the wings is doubled to a total of four. The rear-facing Small Laser is retained, and a Guardian Electronic
DII-SBT-AS-BC3 – The -BC3 variant of the Sabretooth Medium Aerospace Fighter was introduced in late 3076 as a multi- Mattias would never forget that moment. Despite having not shown any prior interest in his parents’ love of fighter
range engagement variant to improve combat flexibility. Unfortunately, this flexibility came at the cost of overall craft and flight, he quickly became obsessed with anything that could fly. His parents understood that obsession all too
firepower, and it proved to be less popular. It was also introduced too late to participate in Operation LANCASTER. The well, despite the unique circumstances under which that obsession was founded in their son. As a result, he soon began
-BC3 Sabretooth is primarily armed with twin Sniper-Blazer IX Extended Range Large Lasers, backed by a pair of Flash- learning how to fly an aircraft. By the time he was of age to begin his compulsory service in the military, he was already
Sword VII Extended Range Medium Lasers, all installed in the nose. The ER Large Lasers provide reasonable punch at an accomplished pilot in his own right, having considerable experience in small civilian aircraft with many flight hours
extreme range and the secondary ER Medium Lasers increase damage output at medium range. However, at short range, logged—far more than what is ever expected for someone his age. At the Acala III Military Academy, he proved his
this version of the Sabretooth truly shows its fangs. Each wing is equipped with a quartet of eight Short-Beam IV Extended experience and skill quickly, becoming one of the best pilots that the academy has ever turned out. His application to join
Range Small Lasers, for a total of eight, providing a devastating close-quarters punch. A ninth ER Small Laser is installed the elite Dreadnought BattleCorps was accepted soon after his graduation in 3067.
aft-facing to provide rear defensive capability while dogfighting. The Enhanced Pinpoint Version-V-ASF Targeting
Computer utilized in the previous BC-Series variants is retained, allowing for highly accurate strikes. As with other BC- Major Mattias Dicey’s Sabretooth, nicknamed “Acaroc” after his childhood encounter, was one of the few Sabretooths
Series variants, the -BC3 is equipped with a Dreadnought TDN System. Even with twenty-two double heat sinks, cooling to survive Operation LANCASTER fully intact. Dicey, then a Captain, claimed three kills during the fighting in the skies of
is a greater concern for the -BC3 than it is for any other BC-Series variant. Though still relatively cool-running under most Ashkum IV during LANCASTER. As of 3085, Major Dicey commands the Dreadnought BattleCorps’ 2nd Battle Wing,
conditions, this fighter can overheat if pushed too hard once it has closed in on a target and all its weapons are in range. consisting of Green and Red Flights – six Sabretooth and six Vertigo Aerospace Fighters, respectively.
(Battle Value: 2,974) Features the following Design Quirks: Dreadnought Spec (Tier-2)*, Rugged.
DII-SBT-AS-BC4(X) – The -BC4(X) is an experimental prototype variant that is designed for use by Dreadnought’s own Type: Sabretooth (DII-SBT-AS-BC2)
military and is currently undergoing testing as of last report. This experimental variant is armed similarly to the -BC2, but Classification: Medium Aerospace Fighter (Limited Production)
it utilizes a new type of experimental laser weapon. This new laser is based on a form of modified Heavy Medium Laser Technology Base: Clan/Dreadnought
first seen used in the Blackwood Templars Mercenaries’ Peregrine BattleMech known as “Havoc”. These weapons are Tonnage: 65
essentially a near-perfect parallel development of the Clans’ own Improved Heavy Medium Lasers. Once the weapons Battle Value: 3,256
themselves have been fully developed for production, and assuming that the completed fighter variant itself is adopted Notes: Features the following Design Quirks: Dreadnought Spec (Tier-2)*, Rugged.
for use, the -BC4(X) will be redesignated as “-BC4” for production purposes.
Equipment Mass
The experimental -BC4(X) is armed with four Flash-Sword VII Extended Range Medium Lasers housed in the nose of the Engine: 325 Fusion XL 12
craft, backed by an equal number of the new Improved Heavy Medium Lasers, with a pair of the new weapons mounted Safe Thrust: 7
to each wing. The -BC4(X)’s rear arc is defended with a Laserwerks Strobe Type 2 Extended Range Small Pulse Laser. The Maximum Thrust 11
-BC4(X) is equipped with twenty-six double heat sinks, an Enhanced Pinpoint Version-V-ASF Targeting Computer, and a Internal Structure: 7
Dreadnought TDN System. Unique to the -BC4(X) is the addition of an Angel Electronic Countermeasures Suite. (Battle Heat Sinks (Double): 26 (52) 16
Value: 2,774) Features the following Design Quirks: Dreadnought Spec (Tier-3)*, Rugged. Fuel: 480 6
Cockpit: Standard 3
Notable Pilots Armor Factor (Ferro-Aluminium): 249 13
Armor
Major Mattias Dicey – DII-SBT-AS-BC2 Sabretooth “Acaroc”: Born in 3046, Mattias Dicey is a native of Acala III. His Value
parents, Jolene and Trip Dicey, were both skilled aerospace fighter pilots who met during their time serving in the Nose 80
Dreadnought DefenseCorps. Although Mattias would grow up to be an excellent second-generation pilot himself, it was R/L Wing 60
not his parents’ history that served as the initial catalyst for him to become one. Aft 49
The original design not been planned around access to a high-power ExtraLight Fusion Engine—in this case, the same
OHI-380XLC unit utilized in the Sumaire Assault OmniMech. The upgraded fighter mounted far more armor than initially
designed, and at the same time gained vastly greater acceleration and maneuverability than the original plans had
intended. This required a sturdier and more heavily reinforced spaceframe to handle the added stresses of the engine
output and maneuvering capability. Unfortunately, this oversight was not caught before the first prototype was tested to
its limits—and, as a result, far beyond. The first prototype’s frame suffered a severe structural failure during a peak
maneuvering test, effectively snapping in half. Fortunately, the test pilot suffered only minor injuries. The front half of
the craft was sent spiraling, but it shed most of its momentum and the pilot was able to use the nose-mounted reaction-
control thrusters to eventually stop the dizzying spin. After this incident, the frames of all following prototypes —and, by
extension, the later production models introduced in 3071—were reinforced heavily, becoming a 95-ton craft, and this
problem has never resurfaced. After the structural integrity issue was resolved, an impressive 4.5-G of thrust has been
safely and consistently measured when operating at maximum output, despite the mass of the heavy fighter.
The incident of the first prototype snapping in half did result in an additional design change to the fighter during the
developmental process, however. After discovering that the front portion of the prototype had been able to maneuver
and slow by itself after the craft had sheered in half, a full cockpit ejection system was devised. With all the survival gear
associated with the Dreadnought Armored Pilot Survival Kit (DAPSK) integrated into it, this full cockpit ejection system
became known as the AeroFighter Survival Pod, or “AFSP”.
The AFSP consists of the cockpit itself with a lightly armored shell housing critical systems below and to the front and
Mass: 95 tons sides of the cockpit, as well as a portion of the hull to the rear of the cockpit. During ejection, the AFSP blasts clear of the
Chassis: Viper Flyer Version 39-Delta w/CASE-II fighter’s body and becomes an escape pod with a miniature drive thruster and a handful of reaction control thrusters for
Power Plant: Orbital Heavy Industries OHI-380XLC ExtraLight Fusion Engine maneuvering. The fuel capacity of the AFSP is quite limited, but it is sufficient to perform limited maneuvers to escape a
Armor: SCB-AS-Pattern Orbital Heavy Industries Special Type-C Ferro-Aluminium Armor combat area, arrest momentum, and then set a course to rendezvous with friendlies for retrieval. The AFSP contains not
Armament & Equipment: only the entire life support system of the fighter, but also includes a micro fusion reactor derived from the Vector Storm
2 OmniBow Streak Advanced Tactical Missile 9-Racks series motorcycles, as they proved to be the most compact and inexpensive units available, as well as the only design that
1 Thunderstruck XV Extended Range Particle Projector Cannon could be easily fitted within the confines of the small pod. For an ejection in space, this does mean that the occupant can
3 Flash-Sword VII Extended Range Medium Lasers essentially survive for as long as they have food and water, of which they typically have a two-week supply. In the event
1 Short-Beam IV Extended Range Small Laser of an ejection in atmosphere, the RCS thrusters and small drive thruster are nearly useless as the escape pod does not
1 Dreadnought BC Special Mk-II Target Data Networking System have any kind of useful aerodynamic stability. The pod does have parachutes to control descent, however.
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite
Manufacturer: Dreadnought Interstellar Industries After the development of the AFSP for the Steel Cobra, it found its way into all future Dreadnought Spec AeroFighters,
Primary Factory: J.S. Space Superiority Labs; Acala III such as the BC-Series variants of the Vertigo and Sabretooth. As the Vertigo Light Aerospace Fighter was designed from
Communications System: Interconn-Comm VII the ground up after this system had been created and implemented, it shares much of its cockpit design with the Steel
Targeting & Tracking System: Enhanced Pinpoint Version-V-ASF Targeting Computer Cobra. This shared design allows the cockpit module to be essentially interchangeable with just a swap of the armored
rear cowling directly behind the cockpit—much like the full-head ejection system in the Hatchetman and Axman
Overview BattleMechs allows the same head to be used interchangeably. Unfortunately, the same could not be said for the
Sabretooth. Although it performs the same function, the physical construction of the pod itself had to be radically altered
Originally the brainchild of a small group of former Clan Steel Viper scientists, this unfinished design effectively became for the mediumweight Sabretooth, and as a result the cockpit module is not compatible with the other two craft.
the property of Clan Smoke Jaguar when the scientists themselves were taken as “Isorla” (the Clan term for the spoils of
war), as part of a Trial of Possession for a Steel Viper research and development facility in 3045. The Steel Cobra remained Though the considerable arsenal of underbelly-mounted weaponry does cause considerable drag in atmospheric flight
unrealized in the hands of the Smoke Jaguars, and the scientists themselves were shipped off to the Smoke Jaguar facilities conditions, the overall design is relatively stable when flying in an atmosphere. The thrust of the Clan-derived OHI-380XLC
on the world of Pantheress VI, where they joined a team of scientists researching experimental technologies. Eventually ExtraLight Fusion Engine is enough to hurtle the craft through the air with ease despite the drag—although it should be
they became involved in the development program for the Prowler Ultraheavy ProtoMech. Many years later, after the noted that the VSTOL thrusters underneath the craft are required to be used at lower speeds, especially at lower altitudes.
Dreadnought BattleCorps took possession of the Pantheress system, following the end of the brutal campaign on Huntress
that would see Clan Smoke Jaguar disbanded, the scientists in question found themselves changing allegiance once again. Since its first combat deployment during Operation LANCASTER in 3077, it has become a common tactic for the pilots
of Dreadnought’s Steel Cobra Heavy Aerospace Fighters to remain at cruising speeds when first approaching a combat
After nearly all the personnel, war materiel, and advanced manufacturing equipment and tooling had been effectively zone. The lower thrust makes the Steel Cobra appear on many sensors as though it is instead a Stuka or another heavy-
uprooted and taken from the world of Pantheress VI, the Dreadnought BattleCorps returned to the Inner Sphere in 3066. end AeroFighter with a comparable agility and thrust profile. With their battle computers misidentifying the Steel Cobra’s
Like many of the now-former Clan personnel that had been absorbed into Dreadnought, the scientists were initially weight and thrust output, many opponents will underestimate it. Typically, a Steel Cobra pilot will wait until nearing
Defensively, the Steel Cobra is encased in sixteen tons of Clan-derived Ferro-Aluminium armor. It is also equipped with DII-SCB-AS-X2 – The only known export variant of the Steel Cobra began production in 3080. The -X2 is a mass production
an Angel Electronic Counter Measures Suite to jam hostile communications and protect the fighter from hostile missile fighter, designed and manufactured for general market sales. This variant of the craft takes the DII-SCB-AS-X1 and
locks, as well as helping to counter hostile electronic countermeasures. In addition to its defensive measures and modifies it to directly replace the Streak-ATM-9 missile systems with Reacher-Series Long Range Missile 15-racks
accurate, formidable weapons array, this fighter is equipped with Dreadnought’s own Target Data Networking (TDN) augmented by Artemis IV Fire Control Systems, fed by a shared seven tons of CASE-II protected ammunition. The ER PPC
System. Although this system is generally useless in air-to-air or space combat, the ability to lend precision fire support is retained, but all of the fighter’s lasers are replaced with Laserwerks Strobe Type 7 Medium Pulse Lasers—both forward-
with the assistance of shared targeting telemetry from Linked ground forces while making strafing runs is exceptionally and aft-firing—all of which are tied to an Enhanced Pinpoint Version-V-ASF Targeting Computer. To make room for the
devastating. Between its considerable fuel and ammunition supply, as well as many weapons not requiring ammunition additional equipment onboard, two double heat sinks are removed, but because of the reduced demand on the cooling
at all, the Steel Cobra is capable of extended combat deployments and engagements far exceeding most rivals. With system, the -X2 is the most heat efficient of the line.
twenty-three double heat sinks housed within the Steel Cobra’s spaceframe, the heavy aerospace fighter can operate its
TDN System while firing all of its weapons continuously without any concern of overheating. With a growing popularity as a long-term campaign fighter, the -X2 Steel Cobra has been observed most often in service
of the Raven Alliance and House Davion, but it has appeared in a small number of various other deployments across the
Additional Information Inner Sphere. (Battle Value: 3,389) Features the following Design Quirks: Rumble Seat; Difficult to Maintain.
The sighting of a Steel Cobra in-system or flying overhead anywhere outside the Acala system is effectively an Notable Pilots
announcement of the presence of the Dreadnought BattleCorps’ Aerospace Fighter Wing, as it is the signature space- and
air-superiority fighter of the BattleCorps. In the years following Operation LANCASTER, however, the fighter has also Lieutenant Colonel Garrett Wilder – DII-SCB-AS-BC1 Steel Cobra “Black Mamba”: The charismatic and fun-loving
become synonymous with the Dreadnought DefenseCorps forces in the Acala system—and, by extension, the recently commander of the Dreadnought BattleCorps’ Aerospace Fighter Wing, Garrett Wilder is a rather attractive middle-aged
formed Acala Semi-Autonomous Region (ASAR)—with dozens of these craft assigned to each of the orbital defense man. He has a mixed—if not somewhat obscure—ethnic background, with an olive skin color and wild-looking naturally
platforms orbiting Acala III. In the cases of both the BattleCorps and DefenseCorps, the Steel Cobra will often be deployed orange eyes. With a shaved head, thin black eyebrows, and a combat scar across his right cheekbone, he is unmistakably
together with smaller fighters, such as the Vertigo and Sabretooth—however, the introduction of the new Firestar Heavy a warrior. Most who see him for the first time expect him to be a stereotypical hard-ass but are generally surprised when
Aerospace Fighter has only further strengthened the power wielded by the DefenseCorps forces in the Acala system. they discover that he is a remarkably down-to-earth individual with unfathomable reserves of patience.
Prior to the 3080 introduction of the DII-SCB-AS-X2 variant, which is made for export sales, it was effectively unheard- Wilder grew up on the Steiner homeworld of Tharkad before the Clan invasion, and he always wanted to fly. He had
of for a Steel Cobra Heavy Aerospace Fighter to sport anything but the signature black and red livery of the Dreadnought just completed training as a civilian pilot when he was drafted into the AFFC in 3050 at the age of twenty. He was thrust
BattleCorps—however, a silver-and-red-liveried example has been reported on a few occasions operating apart from the into the conflict with the invading Clans, desperately hoping to defend against the might of Clan Jade Falcon.
BattleCorps. There have also been reports of others in a wholly different livery as well, these ones suspected to be
operating with the Mercenary unit known as the Blackwood Templars. None of these have yet to be confirmed. After having lost his wing mate in an attempted strafing pass against Jade Falcon ground forces while trying to provide
support for Prince Victor Steiner-Davion during the heavy fighting on Trellwan in 3050, Wilder’s own 90-ton TFN-2A
Variants Typhoon was shot down as well. He was taken in as a Bondsman by the Jade Falcon warrior who had shot him down,
named Charles, but was eventually released from his bondcord. At that moment, in May of 3053, he declared a Trial of
DII-SCB-AS-X1(X) – Records regarding the 90-ton prototype that preceded -X1(X) Steel Cobra have yet to be uncovered, Possession for something rather unique: His freedom from the Clan, and the right to choose his path without obstruction.
so this is the only preproduction prototype of the fighter that is known. The -X1(X) is almost identical to the -BC1 variant, The audacity, as well as the unusual goal of the trial—having the benefit of apparently having never been tried—was
but it was never equipped with the Dreadnought TDN System, and in its place instead has an Active Probe. The only other surprising enough to the Jade Falcon leadership that they actually recognized his challenge. Though he had grown fond
noted difference is that the -X1(X) variant mounts a more powerful rear-firing ER Medium Laser in place of the -BC1’s ER of Charles, Wilder was forced cripple the man in combat to earn his freedom. Charles’ fate is unknown.
Small Laser. (Battle Value: 3,944) Features the following Design Quirks: Rumble Seat; Difficult to Maintain, Prototype.
Wilder’s unusual story caught on with the media. News outlets played again and again the tri-vid shot taken of the man
DII-SCB-AS-BC2 – Developed originally under the chassis variant code of “-BC1CC”, a command-oriented BC-Series Steel on Arc Royal, walking across an open field from a Clan Jade Falcon DropShip and into the welcoming arms of the Kell
Cobra variant was introduced in the form of the -BC2. This variant removes one double heat sink and downgrades the Hounds Mercenary unit—which was, for the purpose of this event, representing the Inner Sphere—before the DropShip
advanced Targeting Computer in favor of the specialized electronics and space required to fit a Command Console and lifted back off again without incident. Having spent close to five years in captivity, he was given veterans’ pay and POW
tactical officer. Only a handful of this variant have reportedly ever been built, and only one was ready in time for Operation compensation. Due to his popularity in the media, he was also given a supposedly-scripted meeting with Prince Victor
LANCASTER—the fighter in question being assigned to Commander Annika Rhys to command the Phoenix Aerospace himself, where Garrett knelt before the prince, unscripted, and all but begged for forgiveness for having failed him. The
Fighter Wing. (Battle Value: 3,657) Features the following Design Quirks: Dreadnought Spec (Tier-2)*. prince, genuinely moved by the action, lifted him up and stated flatly that there was nothing to forgive.
The Firestar is a 100-ton brute of an AeroFighter designed entirely around its missile systems. The quartet of OmniBow
Streak Advanced Tactical Missile 12-racks define not only the fighter’s function but also give it its unique silhouette. Nearly
a full quarter of the craft’s total weight is dedicated entirely to the ammunition feeding these missile systems, with a total
of 1,440 missiles with mixed warhead types housed within the bulky fuselage. The array of missile systems is backed by
five Flash-Sword VII Extended Range Medium Lasers—two of which are rear-firing—tied to an Enhanced Pinpoint Version-
V-ASF Targeting Computer. With seventeen double heat sinks, the Firestar can fire all four of its missile systems constantly
without issue, though it does risk overheating if the lasers are fired simultaneously with them. The Firestar’s heavily
armored hull is composed of 16.5 tons of Clan-tech-derived Orbital Heavy Industries Special Type-C Ferro-Aluminium,
giving it an impressive ability to survive several direct hits by even heavy autocannons or Gauss Rifles. Given this fighter’s
primarily spaceborne application, the inclusion of a Dreadnought Target Data Networking (TDN) System is seemingly
superfluous—its improved communications capabilities and limited ECM aside—but it is standard kit for “Dreadnought
Spec” AeroFighters, ‘Mechs, and combat vehicles. Though rarely used in this application, the TDN allows the Firestar to
lay waste to ground targets using targeting telemetry provided by friendly Linked ground forces to enhance its accuracy.
Aside from issues regarding atmospheric flight stability, the Firestar suffers from two primary weaknesses. The first is
its relatively limited range. With only four tons of fuel, the Firestar is best suited to defensive or relatively short-range
deployment use. The second is that it is quite expensive to produce. While the actual production cost numbers have not
been released to the public, there is no doubting that the cost of these fighters will be a limiting factor in the number of
examples produced. A less-expensive variant may yet be forthcoming, but as of 3085, it has yet to begin development.
Mass: 100 tons
Chassis: J.S. Space Superiority Firestar w/CASE-II
Power Plant: Orbital Heavy Industries OHI-300XLC ExtraLight Fusion Engine Type: Firestar (DII-FST-AS-BC1)
Armor: FST-AS-Pattern Orbital Heavy Industries Special Type-C Ferro-Aluminium Armor Classification: Heavy Aerospace Fighter (Limited Production)
Armament & Equipment: Technology Base: Clan/Dreadnought
4 OmniBow Streak Advanced Tactical Missile 12-Racks Tonnage: 100
5 Flash-Sword VII Extended Range Medium Lasers Battle Value: 5,258
1 Dreadnought BC Special Mk-II Target Data Networking System Notes: Features the following Design Quirks: Dreadnought Spec (Tier-2)*, Fast Reload; Atmospheric Flight Instability.
Manufacturer: Dreadnought Interstellar Industries
Primary Factory: J.S. Space Superiority Labs; Acala III Equipment Mass
Communications System: Interconn-Comm VII Engine: 300 Fusion XL 9.5
Targeting & Tracking System: Enhanced Pinpoint Version-V-ASF Targeting Computer Safe Thrust: 5
Maximum Thrust: 8
Overview Internal Structure: 10
Heat Sinks (Double): 17 (34) 7
The Firestar is the newest AeroFighter to be developed by Dreadnought Interstellar Industries’ J.S. Space Superiority Fuel: 320 4
Labs on Acala III. Designed specifically around the 12-tube Streak Advanced Tactical Missile System, and mounting four Cockpit: Standard 3
of them in total, the Firestar is a devastating fighter. Conceptualized in late 3072, funding for the Firestar’s development Armor Factor (Ferro-Aluminium): 316 16.5
was cut down to a bare minimum in 3077, slowing the program to a crawl shortly before it would have been ready to Armor
produce a prototype. This severe reduction in funding was due to the heavy losses taken by the Dreadnought BattleCorps Value
1st RCT during Operation LANCASTER, requiring the funds to be reallocated to the rebuilding of the BattleCorps. Nose 95
R/L Wing 80
In 3083, the same year that the rebuilding process for the Dreadnought BattleCorps 1st Regimental Combat Team was Aft 61
completed, the Firestar program was granted the funding to finally build its first prototypes. Because the design had spent
several years being refined and perfected in simulations by the core development team as they awaited the opportunity Weapons and Ammo Location Tonnage Heat SRV MRV LRV ERV
to build their fighter, these prototypes performed almost flawlessly right from the start. The testing program for any new 3 ER Medium Lasers Nose 3 15 21 21 – –
aerospace fighter is normally a grueling process where engineers and programmers alike discover errors in their work. 2 Streak-ATM-12s* (ER/S/HE) R. Wing 14 8 24/48/72 24/48/– 24/–/– 24/–/–
However, the Firestar was notable for being virtually unbreakable from day one. The sole blemish on its otherwise perfect 2 Streak-ATM-12s* (ER/S/HE) L. Wing 14 8 24/48/72 24/48/– 24/–/– 24/–/–
record during more than a year of testing was a singular incident where a fire control malfunction aboard one of the two 2 ER Medium Lasers Aft 2 10 14 14 – –
prototypes rendered two of the four missile systems nonfunctional during the first simulated combat mission. This Dreadnought TDN System* Fuselage 1.5 2
problem was corrected in days, and after months of rigorous torture of the craft, it never again resurfaced. Targeting Computer Fuselage 1 –
Ammo (S-ATM-12 S) 40 Fuselage 8 –
The Firestar Heavy Aerospace Fighter began production in mid-3084. Given its rather unwieldy nature when fighting in Ammo (S-ATM-12 ER) 40 Fuselage 8 –
atmosphere, these fighters are primarily stationed at the Orbital Defense & Refit Platforms (ODRPs) orbiting Acala III. It Ammo (S-ATM-12 HE) 40 Fuselage 8 –
is likely that other examples of this craft may find use with the BattleCorps’ small fleet of WarShips. The sheer firepower CASE-II Fuselage 0.5 –
that the Firestar brings to a combat zone is astonishing, but given their limited range and operational scope, these craft
are far more likely to be used in defensive positions where they can easily return to static bases to refuel and rearm. * See Special Dreadnought / Lancaster Specific Rules (Pages 428-431)
Following directly in the footsteps of the original -J1 Skua Recovery Craft, the DII-SKRV-SV-DC1 Skua is a purpose-built
recovery vessel with a DefenseCorps chassis variant code. In addition to a fifty-ton cargo bay for internal cargo storage,
the Skua’s salvage arms can securely grapple objects, such as an aerospace fighter weighing up to one hundred tons, and
safely carry it back to the Skua’s home base. Alternatively, the Skua can also be used in-atmosphere as a transport vessel
for combat vehicles and even ‘Mechs. As a result of this, Skua Recovery Craft are often used to transport disabled ‘Mechs
and vehicles off a battlefield after combat, and they have even—rarely—seen use in rapid deployment tactics. To enhance
the Skua’s ability to search a battlefield or debris field in space for survivors or disabled craft, the Infrared Satellite Imager
fitted to the standard -J1 has been augmented with the addition of a Clan-tech-derived Active Probe in the -DC1.
In addition to its primary function as a recovery vessel, the Dreadnought-exclusive -DC1 Skua is armed with a total of
eight Clan-tech Flash-Sword VII Extended Range Medium Lasers, installed in pairs to provide overlapping firing arcs around
the vessel. Twenty double heat sinks provide sufficient cooling to allow all the weapons to fire continuously. As with the
original -J1 Skua, the -DC1 is protected by nine tons of armor—however, unlike the original -J1, the -DC1’s armor is the
same Clan-tech Ferro-Aluminium Armor used in the Dreadnought BattleCorps’ own aerospace fighters, giving the -DC1
Skua considerably greater protection than even the reinforced -J1P refit variant common to Pirate organizations.
The first-generation Skua Recovery Craft, designated DII-SKRC-SC-J1, was introduced in 2485, just two years after the A popular choice for every JumpShip company in the Inner Sphere, the DII-SKRC-SC-J1 and -J1C Skua Recovery Craft are
introduction of the Mammoth II JumpShip. The official designated purpose of the Skua was—and still is—that of a general- common sights among commercial JumpShips everywhere. As the design was introduced long before the Great Exodus,
purpose recovery craft, hence its name. The real purpose of the mass-production Skua is slightly more involved. When the Clans make equal use of these vessels to assist with cleanup after trials fought in space, as well as aiding in general
the DiscoveryCorps variant of the Mammoth II entered production, it became readily apparent that a more capable rescue and recovery operations. Although it is well known that a Skua armed with anything other than Medium Lasers is
recovery craft was needed to operate with their Mammoth IIs in order to fulfill the DiscoveryCorps’ mission statement of almost certainly a Pirate vessel, that has not deterred the common use of the -J1P refit by Periphery and other Pirate
seeking out and recovering vessels that had suffered misjumps, as well as to recover Lostech assets for Dreadnought organizations throughout the Inner Sphere. The -DC1 and -BC1 variants are used exclusively by the Dreadnought’s private
Interstellar Industries. The Skua offered better capabilities in this regard than any Small Craft in production at the time. military organizations, with an increasing number of -BC1 “Raptor” variants of the Skua being proliferated among the
By the time that the Dreadnought-operated JumpShip Allied Transport Company (JATC) was retitled as the JumpShip Dreadnought BattleCorps and DefenseCorps—specifically among Dreadnought’s WarShips and orbital defense platforms.
Allied Transport Association (JATA) in 2583—as the majority of the JumpShips in the association were independently
owned—the Skua had become a remarkably popular design with nearly every JumpShip company. It is believed that Variants
nearly half of all JumpShips in the Inner Sphere were supported by at least one Skua by the middle of the 27th Century.
DII-SKRC-SC-J1 – Celebrating six centuries of uninterrupted production in 3085, the original variant of the Skua Recovery
A common modification to the Skua has been to repurpose it as a rescue craft, modifying the cargo bay to fit several Craft was introduced in 2485. The original Skua is remarkably barebones compared to the newer, highly advanced units
small cabins to be occupied by rescued survivors of a disaster. Similar modifications have been made to fit different used by Dreadnought’s militaries, but it still has much in common. It has the same powerplant and engines, cockpit, living
combinations of cargo space and compact cabins to fit recovery teams. These types of refits became increasingly popular quarters spaceframe, and Infrared Satellite Imager as the -DC1, but that is where the similarities end. The standard -J1
as the -J1 Skua’s fifty-five-ton cargo bay—tucked into the rear half of the forward section—was often considered by some Skua is coated in nine tons of Standard Aerospace Armor, which provides adequate protection in most circumstances.
to be excessive or unnecessary with the large capacity of the massive salvage arms lining the underbelly of the craft. Offensively, this craft is armed with a total of eight Medium Lasers, with two being forward-facing, two mounted to each
wing and a further two installed facing aft. The -J1 Skua Recovery Craft features a fifty-nine-ton cargo bay, and a total of
Unfortunately, the Skua also became quite popular with pirates, who perverted the vehicle into a pseudo-gunship and twenty-four single heat sinks are fitted into the spaceframe to provide ample cooling. (Battle Value: 742)
boarding craft. The most common pirate variant replaces a handful of the lasers with an array of Particle Projector
Cannons, sufficient to threaten most commercial JumpShips into standing down. After forcing a surrender, the vessel’s DII-SKRC-SC-J1C – A basic “Cabin” refit of the original -J1 Skua, the -J1C variant is not technically a uniform refit. This refit
sizable infantry compliment serves as a boarding party to storm the JumpShip and usually seize control of the vessel with repurposes the fifty-nine-ton cargo bay to fit up to twelve compact cabins for a well-equipped recovery team, with the
ease. Ironically, a variant armed with PPCs was in the works by Dreadnought Interstellar Industries themselves when news remaining tonnage being allocated to cargo. Alternatively, this variant has been used as a rescue vessel with room for up
of these refits began to surface in the media as being favorites among pirate groups. In an act to try to at least give the to twelve survivors, again with the remaining tonnage being allocated to cargo. (Battle Value: 742)
JumpShip crews some warning if there was a Pirate-refitted version of a Skua heading their way, Dreadnought Interstellar
made a public announcement stating that the production models of the Skua would only ever be equipped with medium- DII-SKRC-SC-J1P – The most popular “Pirate Refit” of the Skua was first identified in the Periphery in 2633, but then quickly
class lasers, and no other type of weapon system. spread to the Inner Sphere. It has since been given the official chassis variant designation of “-J1P”. This refit removes the
Infrared Satellite Imager and strips the cargo bay down to a mere two tons. Room for twenty tons of infantry for boarding
True to their word, in the four-hundred-fifty years since the announcement in 2633, no factory Skua variant armed actions is then fitted. The nose-mounted pair of Medium Lasers, as well as one of the rear-firing units, are removed. The
with any offensive weaponry other than medium-class lasers has ever been built. While the literal letter of that promise -J1P’s iconic trio of Particle Projector Cannons are installed in place of the forward-firing lasers. Defensively, the -J1P
has been kept to the public over the generations, there is a variant that has recently become the source of a small level mounts a full twelve tons of Standard Aerospace Armor to improve durability dramatically over the normal design. Forty-
of controversy, with some even claiming that Dreadnought has begun to create factory Skua gunships. The DefenseCorps- five single heat sinks allow this craft to fire all its weapons continuously without issue. (Battle Value: 1,275)
coded -DC1 variant—used with Dreadnought’s own WarShips, orbital defense platforms, and even some JumpShips—is
armed with advanced Clan-derived technology that adds roughly half-again the firepower and armor protection to the DII-SKRC-SC-BC1 “Raptor” – In 3078, the first—and so far, only—BC-Series variant of the Skua was introduced, with intent
craft. The controversial claims have been largely ignored, as Dreadnought has actively refused to take up an aggressive to provide electronic warfare support for an aerospace fighter squadron. Although not a particularly effective combat
stance against its neighbors and has historically only acted in the best interests of the Inner Sphere. After the introduction craft on its own, the -BC1 Skua can provide strategic support. The -BC1 Skua, based on the -DC1 variant, fills the entirety
of the BC-Series “Raptor” variant of the Skua in 3078, however, there has been a slowly growing unrest. Some even feel of the cargo bay full of advanced electronic warfare and defensive equipment. The -DC1’s Active Probe is removed, and
that the Raptor is just one more example of Dreadnought flexing its muscle through its private military. the rear-facing, under-slung cargo bay is packed full, with four Chaff Pods, an Angel Electronic Countermeasures Suite, a
Dimensions
Length: 45 meters
Width: 32 meters
Height: 7 meters
Armor
Nose: 70
R/L Side: 58
Aft: 50
Cargo
Bay 1: Cargo (50 tons) 1 Door
Escape Pods: 0
Life Boats: 0
Crew: 1 Officer, 2 enlisted / non-rated, 2 gunners, 1 passenger
Ammunition: None
While there were three first-class cabins for the ship’s officers, the Abeona’s quarters for the rest of the crew and its
fifteen marines were all standard crew quarters—a step up compared to normal accommodations for shipboard marines.
As it was designed with rescue operations in mind, the Abeona was also equipped to handle up to fifty passengers,
although the quarters for the passengers were small and tight, and quite sub-par when compared to the crew quarters.
Given that these cramped conditions would surely be an improvement over whatever likely dire situation the passengers
would have been rescued from, the minimalist accommodations were considered sufficient for the purposes of the vessel.
To aid in search and rescue operations, the Abeona-class DropShuttle was equipped with a Look-Down Radar, a High-
Resolution Imager, and an Infrared Imager. It also featured three powerful Mounted Spotlights—one installed in the nose
and one at each wingtip—for close inspection purposes in space, as well as significantly improved visibility when landing.
Variants
DiscoveryCorps (DropShuttle) – An upgraded version of the Abeona DropShuttle was introduced in 2438 to serve as the
workhorse of the then-newly-formed Dreadnought DiscoveryCorps. Though it had no noteworthy differences in terms of
maneuverability or engine performance, it featured a newer, more efficient powerplant and engines—albeit not quite up
the standard of the units used in the later DropShip versions of the Abeona. The Abeona DiscoveryCorps DropShuttle used
Overview the same armor as the original vessel, but its armament was upgraded with the same newer Autocannon/5s later featured
normally in the later DropShip refit. Taking advantage of the more compact, newer powerplant, the Abeona
The Abeona-class DropShuttle was first introduced in 2242 by Dreadnought Interstellar Industries—then known as DiscoveryCorps DropShuttle featured first-class cabins for the ship’s entire crew, though the fifteen marines aboard still
Dreadnought Enterprises. Named after the Roman Goddess of Safe Travels, the Abeona was Dreadnought’s bid to win a had to make do with the standard-class cabins. This variant also featured an enlarged cargo bay, with capacity for up to
production contract from the Terran Alliance for a patrol and rescue vessel. Dreadnought’s chief competition for the 221 tons of cargo. The Abeona DiscoveryCorps DropShuttle had space for up to eighty passengers for rescue operations—
contract was Dramm-Chance Interstellar Technologies and their Saturn-class DropShuttle. though these cabins were still far more cramped than even the quarters for the marines. However, even with an added
sixth Escape Pod, this vessel could only support its crew and marine compliment in an emergency requiring evacuation.
In comparison to the 1,200-ton Saturn, Dreadnought’s far heavier 2,500-ton Abeona was suitably more heavily armed
and armored. Despite the difference in mass, the Abeona had comparable maneuverability and acceleration to the smaller What most set the DiscoveryCorps variant of the Abeona DropShuttle apart, however, were the systems installed to
vessel, and the Abeona boasted a considerably longer range thanks to its larger fuel capacity. The aerodyne nature of the carry out its core mission of rediscovering lost technology, finding lost ships, and saving lives whenever possible—chief
Abeona also meant that it had significantly greater in-atmosphere flight capability and stability than the Spheroid Saturn. among which was its Small Naval Comm-Scanner Suite, which extended its sensor range considerably. Only seventy
Additionally, the Abeona offered capacity for up to forty-five passengers in the event of a rescue operation, which was examples of this craft were ever built, and starting in 2465, they all eventually received a DropShip refit to make them
something that the Saturn simply could not match. The Abeona’s not-insignificant list of combined advantages netted compatible with modern JumpShips. (Battle Value: 2,090)
Dreadnought Interstellar’s vessel far greater operational flexibility.
DropShip/DropShip Refit (Standard) – The K-F Boom and the universal docking collar used with modern DropShips and
The Abeona was more impressive than the Saturn in nearly every single measurable way. That is, except for the one JumpShips started to become standard equipment by 2465. Because these were features that had not existed at the time
that made the largest difference at the time. The Saturn cost—in converted money—107 million C-Bills per ship, while a of the Abeona’s original introduction, a standardized “DropShip Refit” was created to keep the existing Abeonas relevant.
single example of the far more capable Abeona cost 199 million. In the end, the decision was made by the Terran Alliance The installation of a K-F Boom and universal docking components make this vessel compatible with modern JumpShip
to award the contract to Dramm-Chance Interstellar Technologies for their Saturn-class Patrol Ship. docking collars, allowing the Abeona DropShip to be carried through hyperspace by all classes of JumpShip going forward.
As most of the Abeonas in service had seen considerable wear and tear, and the installation of the K-F Boom required the
Despite losing the primary contract with the Terran Alliance, the Abeona drew the attention of a handful of hulls of these ships to be pulled apart, their Primitive Aerospace Armor was replaced with outer hulls composed of a much
independent transportation companies, resulting in as many as five hundred examples of this vessel being produced. The more durable Standard Aerospace Armor during this refit. Many of these ships’ sub-systems were upgraded as well.
original three prototypes were refitted to production specification, joining a handful of examples that were used as patrol
vessels by Dreadnought Interstellar Industries themselves. Most of the Abeona DropShuttles that had been produced by The Primitive Autocannons were replaced with modern units, improving the reliability of the ship’s primary weapons,
late 25th Century were upgraded with K-F Booms, as well as being retrofitted to use standard docking collars, making as well as significantly increasing the autocannons’ ammunition load without increasing the tonnage. The most significant
them compatible with JumpShips. These refitted vessels were then reclassified as DropShips by the standards of the era. upgrade was to the engines, which were replaced with considerably more efficient, less expensive, and more compact
units. Using the interior space freed by the more compact engines, the cargo bay and cramped passenger compartments
Capabilities were expanded dramatically. Gone were the cramped cabins for fifty, and in their place were more spacious second-class
cabins for eighty. Even with thirteen Escape Pods added with the refit—18 in total—the cargo capacity nearly tripled to
Armed with a total of twenty-four Machine Guns and twelve Autocannon/5s—the latter of which are considered by 172 tons. It had been hoped to use the Abeona DropShips to relaunch the ship class for mass production as a transport
modern standards to be “Primitive” examples of the weapon—the Abeona-class DropShuttle was a remarkably well- vessel, but it was not to be. The market barely seemed to notice the modernized Abeona DropShip. (Battle Value: 2,738)
armed vessel for its class at the time of its construction. The weapons were installed in an even spread around the vessel’s
perimeter to provide defense in all directions, allowing the Abeona to ably defend itself when necessary. DiscoveryCorps (DropShip Refit) – In 2465, the Abeona DiscoveryCorps DropShuttles began to receive DropShip refits—
eventually all of these were refitted. This refit included most of the standard upgrades, but with some notable differences.
With more than enough ammunition for a prolonged battle, as well as enough fuel for sixty-seven days of continuous It retained its Small Naval Comm-Scanner Suite, and while the number of passenger cabins was increased from fifty to
operation at a comfortable 1-G of acceleration, the Abeona was capable of functioning for extended periods without eighty, these cabins themselves were not upgraded from the cramped, tiny units used in the original DropShuttle—and it
During the short time that Shaw died to provide, the civilians of the Dreadnought facility—including Shaw’s own two
Type: Abeona DiscoveryCorps (DropShip Refit)
children and their father—crammed themselves aboard the recently-restored Salvation, along with the few surviving and
Classification: Military Aerodyne DropShip (Refit/Mass Production)
mostly wounded members of the DefenseCorps. Despite the Salvation carrying far more people aboard her than she was
Use: Patrol, Escort, Search & Rescue
designed for, the remarkably fast vessel managed to evade the Jade Falcon AeroFighters and make a hard burn for the
Technology Base: Inner Sphere
last remaining JumpShip in the star system. If not for the fact that the Salvation had been restored at the Dreadnought
Introduced: 2483
Interstellar Industries facility, rather than at the spaceport proper, the civilians and wounded DefenseCorps personnel
Mass: 2,500 tons Dimensions
would never have escaped.
Battle Value: 2,738 Length: 70 meters
Fuel: 200 tons (8,000 points) Width: 73 meters
As of 3085, the Salvation is one of the handful of known remaining fully intact examples of the Abeona-class DropShip—
Tons/Burn-day: 2.94 Height: 17 meters
retired and active DiscoveryCorps variants aside—and she is the only one of the original three prototypes still in existence.
Safe Thrust: 5 Armor
The Salvation has been kept in good working order since her restoration on Toland, and she is available for viewing with
Maximum Thrust: 8 Nose: 225
a guided tour at Dreadnought Interstellar Industries’ Aerospace Museum, near the New Sydney Spaceport on Acala III.
Heat Sinks: 44 Single Sides: 190
Kept next to the Salvation is the D.I.I.S. Fetcher, the DiscoveryCorps vessel famed for being responsible for the rescue of
Structural integrity: 10 Aft: 155
the crews of two DropShips—and hundreds of passengers—stranded in an uninhabited system in 2467. This rescue is
lauded for launching the Dreadnought DiscoveryCorps into the highly respected organization that it has become today. Cargo
Bay 1: Cargo (232 tons) 2 Doors
Two additional Borealis DropShips did see extremely limited use by the Dreadnought BattleCorps during Operation
LANCASTER. These DropShips were pulled directly from the production line as soon as their assembly was completed.
They had not yet even been assigned names or given any kind of livery. They were simply given a standard coating of
black thermal-insulating ceramic paint and designated “Alpha” and “Beta”. Both were equipped in Aerospace Fighter
Carrier configuration, fueled, armed, then stocked with older aerospace fighters from the Dreadnought DefenseCorps.
These DropShips were then assigned to the Mammoth II DiscoveryCorps-class JumpShip D.I.I.S. Stardancer, to provide
the JumpShip with a small defensive force in the event that her scouting mission to the Ashkum system went awry.
Fortunately for all involved, they were not needed. The two DropShips in question have since been sold to third parties.
It is unclear, however, if Dreadnought interstellar Industries ever informed the buyers that the vessels were involved in
such an historic event before their first registration.
Capabilities
Overview
Built with an impressive blend of speed, firepower, and durability, the 2,900-ton Borealis is among the most versatile
In 3062, the construction of the first prototypes of the Aurora-class DropShip began. These were built for the purpose and capable types of compact DropShip ever created. Although the Borealis is relatively small and somewhat limited in
of evaluation by the Armed Forces of the Federated Commonwealth. The Aurora was a vessel created as a joint project terms of operational scope, it is built to succeed in carrying out whatever mission it may be tasked with.
between Dynamico, Ltd. of Delavan and Shipil Company of Skye—the latter being a company that Dreadnought
Interstellar Industries had prior business dealings with. Shortly after these prototypes began to be built, the development Dreadnought Interstellar Industries is known for generally elegant and clever design solutions. In many critical aspects
program for Dreadnought Interstellar’s Borealis-class DropShip was launched, codenamed “Project Dark Fox”. The choice of the Borealis, however, a somewhat “brute-force” approach has been applied. The Borealis-class DropShip features
to name the new DropShip class “Borealis” was no doubt Dreadnought Interstellar Industries’ way of openly remarkably powerful Thunderhead-SST Rodger-Y Series Engines, propelling the boxy vessel with up to an impressive 4-G
acknowledging what inspired the ship. It is also believed that the obvious name is also Dreadnought’s way of giving their of acceleration force. In addition, it can create a comfortable 1-G environment during intra-system transit using its VTOL
competitors at Dynamico and Shipil a good ribbing. engines at low power. This craft also features a heavily reinforced spaceframe and an exceptionally well-armored hull.
It is unclear if Dreadnought Interstellar acquired the schematics for the Aurora through legitimate means or some form The Borealis is well-armed, with a total of ten Gauss Rifles and ten Extended Range Particle Projector Cannons, as well
of corporate espionage, but early conceptual designs of the Borealis were nearly identical to the original Aurora prototype as four Long Range Missile 20-racks augmented with Artemis IV Fire Control Systems. A turret installed at each corner of
schematics, strongly suggesting a link between the two designs. However, it is somewhat ironic that the Borealis began the ship houses a pair of Extended Range Particle Projector Cannons combined with a pair of Gauss Rifles, giving the ship
as a clear “copycat” of the Aurora, because the evolution of the Borealis’ design shows that Dreadnought Interstellar omnidirectional firing capability. Meanwhile, the missile systems and the final pairs of Gauss Rifles and ER PPCs are
noticed several significant design flaws in the Aurora before they assembled any physical parts. Meanwhile, Shipil and installed in a forward-firing position in the nose of the vessel.
Dynamico only discovered these same flaws after physically building the first test prototypes—and, unfortunately for
them, these very flaws stalled the development of the Aurora itself for years. The most significant of the Borealis’ long list of features is its ability to be adapted for different missions. Thanks to the
four modular “pods”—the bays that attach to the spine of the vessel, arranged in pairs along the ship’s sides—the Borealis
After nearly a year was wasted attempting to develop their own DropShip from the “stolen” design schematics, can be reconfigured to handle a variety of different mission profiles relatively quickly and easily. In the most common
Dreadnought Interstellar Industries abandoned their design based directly on the Aurora altogether and nearly started configuration—serving as a ‘Mech Carrier—the Borealis can carry up four ‘Mechs and still handle more than four hundred
from scratch to create a similar type of vessel. This new class of DropShip took the original concept presented by the tons of additional cargo in the bay built into the ship’s nose.
Aurora and worked to improve every facet of its design. The resulting vessel was considerably faster, featured improved
range, increased cargo capacity, significantly better hull armor protection, and markedly greater firepower. This new Variants
DropShip was also half-again the weight of the Aurora, but with surprisingly smaller exterior dimensions, thanks to its
tightly packaged design. Predictably, at over 440 million C-Bills, this vessel was also roughly twice the price of the Aurora. Aerospace Fighter Carrier – As its indicated by its designation, this configuration of the Borealis is equipped with
AeroFighter bays instead of ‘Mechbays, with room to carry six fighters in total. The forward modular pod on each side of
The Borealis-class DropShip is built around a modular construction much like that of the Aurora that inspired it, and it the ship houses an over-under bay with space for two fighters. The rear pods are laid out similarly, but with only a single
is designed to carry a total of four multipurpose “pods”. These pods are designed to be reconfigured at a dry dock station fighter bay in each pod—housed in the upper level—while a battle armor bay is housed in the lower section of each rear
with relative ease—as with the weaponry of an OmniMech—to handle different mission parameters. Admittedly, in most pod. Each battle armor bay has space for up to twelve suits—enough to perform a basic boarding action. In this form, the
cases, these pods will never be swapped from their original purchased configuration, but it is a useful feature for those Borealis can only handle up to 61.5 tons of cargo in the nose-mounted cargo hold. (Battle Value: 10,452)
who need flexible transport capabilities. In terms of operation and accommodation, the Borealis is designed with
remarkable creature comforts in mind. Although the bay personnel make do with standard quarters, the accommodations Battle Armor Carrier – A battle-armor-centric configuration featuring two large battle armor bays occupying the forward
for the ship’s main crew are remarkably plush, with upscale first-class cabins for all twelve crewmen. The Borealis-class modular pods. Each battle armor bay can house up to eighty battle armor suits. Meanwhile, each rear pod houses two
DropShip, with its no-expense-spared design, has gradually become a semipopular ship class. Though some have criticized light vehicle bays, each of which can handle up to three light vehicles. The light vehicle bays are typically used to carry a
it, referring to it as being an “overpriced Leopard”, the merits of the vessel appear to have drawn the attention of many full company of twelve ground vehicles capable of transporting the battle armor troopers. The nose cargo bay is reduced
with the C-Bills to afford it. As this class of DropShip is relatively new to the market—only having been introduced in early to a maximum capacity of 89.5 tons. (Battle Value: 10,452)
3069—the ship’s popularity is still on the rise. Time will tell if the Borealis lives up to the hype surrounding it long term.
Cargo Carrier – The simplest configuration of the Borealis repurposes the four modular pods on the sides of the ship into
One of the first production-model examples of the Borealis was sold to the Blackwood Templars for a price that Colonel general-purpose cargo containers, each of which can carry up to 200 tons of cargo. In this configuration, the Borealis can
Blackwood himself quoted as “a steal”. The reported half-price deal was contingent on the Templars reporting back any carry up to 209.5 tons of cargo in the nose-mounted hold. (Battle Value: 10,452)
Vehicle Carrier – This Borealis configuration features capacity for a company-sized group of combat vehicles, with each Type: Borealis (‘Mech Carrier)
forward pod housing a pair of heavy vehicle bays and each rear pod housing four light vehicle bays. The cargo bay in the Classification: Military Aerodyne DropShip (Mass Production)
ship’s nose has a maximum 209.5 tons of capacity in this form. (Battle Value: 10,452) Use: ‘Mech Carrier DropShip (Multirole-Capable Vessel)
Technology Base: Inner Sphere
Pocket WarShip – This is by far and away the Borealis’ most dangerous configuration in terms of direct space combat Introduced: 3069
capability. The “Pocket Warship” configuration of the Borealis was introduced as a refit in 3072, during the Word of Blake Mass: 2,900 tons Dimensions
Jihad, by the Blakists themselves. It soon became semi-popular among other military forces as the Jihad continued to Battle Value: 10,452 Length: 100 meters
intensify. It eventually became an optional factory configuration manufactured by Dreadnought Interstellar themselves Fuel: 150 tons (6,000 points) Width: 58 meters
in 3074. As with virtually everything Dreadnought Interstellar Industries built during this era, the factory-built examples Tons/Burn-day: 1.84 Height: 20.5 meters
of this configuration were only made available to militaries that opposed the Word of Blake during the Jihad. Building on Safe Thrust: 5 Armor
the Borealis’ already rugged and durable combat-oriented design, each forward pod houses a Barracuda-Type Capital Maximum Thrust: 8 Nose: 320
Missile Launcher, each of which is fed by an independent ten-missile magazine installed in the forward pods with the Heat Sinks: 92 Double (184) R/L Side: 300
launchers. The rear pods house battle armor bays, each with space for 24 battle armor suits. This configuration also Structural integrity: 14 Aft: 264
features two modifications not typical of most other Borealis DropShips: an Angel Electronic Countermeasures Suite is
installed in the central hull, and a dedicated Space Mine Dispenser is built into the aft lower section of the ship, below Cargo
the engine cluster. The nose-mounted cargo bay can fit a maximum of 101.5 tons of cargo. (Battle Value: 13,109) Bay 1: ‘Mech (1) 1 Door
Bay 2: ‘Mech (1) 1 Door
Artillery Support – This unique configuration of the Borealis is designed to help provide support for a planetary assault Bay 3: ‘Mech (1) 1 Door
force. The Artillery Support configuration of the Borealis DropShip first saw use during Operation SCOUR by members of Bay 4: ‘Mech (1) 1 Door
Devlin Stone’s Coalition forces which were involved in the fighting along the Federated Suns and Lyran Alliance fronts. Bay 5: Cargo (409.5 tons) 1 Door
This configuration retains the normal armaments present in the standard vessel, though the forward cargo bay is Escape Pods: 4 Life Boats: 0
limited to 106 tons of capacity. Although limited, the addition of a Guardian Electronic Countermeasures Suite installed Crew: 2 officers, 3 enlisted/non-rated, 5 gunners, 8 bay personnel
in the ship’s hull does provide some advanced electronic warfare capacity. The forward modular pods of this configuration
are repurposed to house a total of eight Long Tom Artillery Pieces, with four mounted on heavily reinforced retractable Ammunition: 400 rounds Gauss Rifle ammunition (50 tons), 120 rounds Artemis-IV Capable LRM-20 ammunition (20 tons)
turrets on each side of the ship. Each Long Tom has an independent ten-ton ammunition supply—giving each artillery
piece fifty rounds of ammunition. Each rear pod houses a transport and maintenance bay for a single aerospace fighter Notes: Mounts 63 tons Ferro-Aluminium Armor.
in its upper section, allowing the Borealis to carry a lance of two aerospace fighters to provide limited defense against
any enemy fighters that attempt to strafe the DropShip while it is landed. Below each of these aerospace fighter bays is Weapons: Capital Attack Values (Standard)
a large battle armor bay. Combined, the two battle armor bays have space for 96 battle armor suits. This configuration of Arc (Heat) Type Short Medium Long Extreme Class
the Borealis DropShip is capable of far more than its “Artillery Support” designation might seem to suggest. Depending Nose (56 Heat)
on the mission objectives, this vessel can either drop its vast load of battle armor on a combat zone before landing at 2 Gauss Rifles (80 rounds) 3 (30) 3 (30) 3 (30) – Autocannon
range to provide artillery support from afar—or it can land first, shelling a target area from a safe distance, then lift off 2 LRM-20 w/Artemis IV FCS (60 rounds) 2 (24) 2 (24) 2 (24) – LRM
and fly over to drop its battle armor to assist in securing the area. Although it was originally created as an admittedly 2 LRM-20 w/Artemis IV FCS (60 rounds) 2 (24) 2 (24) 2 (24) – LRM
rather wild field refit, Dreadnought Interstellar Industries introduced this as a factory configuration in 3078 to help put 2 ER PPC 2 (20) 2 (20) 2 (20) – PPC
an end to the Jihad. (Battle Value: 15,125) LW/RW (32 Heat)
2 Gauss Rifles (80 rounds) 3 (30) 3 (30) 3 (30) – Autocannon
Dreadnought BattleCorps – This recently proposed Borealis configuration is intended for use by the Dreadnought’s own 2 ER PPC 2 (20) 2 (20) 2 (20) – PPC
military forces. Unlike the standard Borealis configurations produced for export, the entire vessel has been upgraded with RW/LW Aft (32 Heat)
Dreadnought’s own Clan-based technology. In the case of the ER PPCs and Gauss Rifles, these weapons have been directly 2 Gauss Rifles (80 rounds) 3 (30) 3 (30) 3 (30) – Autocannon
upgraded, while the quartet of Artemis-enhanced Long Range Missile 20-racks have instead been replaced with a total of 2 ER PPC 2 (20) 2 (20) 2 (20) – PPC
In addition to the improved weapons systems themselves, the ammunition supply for the weapons array has been As of 3085, the D.B.C. Dragon and D.B.C. Wyvern remain in the service of the Dreadnought BattleCorps. Reports coming
significantly increased over the original design. The original Arrow IV Missile Artillery batteries only had enough missiles from within the Acala Semi-Autonomous Region indicate that replicas of these DropShips may begin construction by as
to fire each launcher fifteen times, but the refit Colossus has sufficient ammunition to fire each of its massive twin Long early as 3087. If accurate, these reports suggest that it is likely the BattleCorps is looking to replace the lost Ryūjin at the
Tom Artillery Pieces fifty times. Meanwhile, the ammunition supply for the dual Gauss Rifles has been increased from very least. However, if they build one, they are very likely to build more. Some in the intelligence circles believe that
ninety-six rounds to a total of one-hundred-twenty. Lastly, despite the new Long Range Missile 15-racks having a reduced Dreadnought Interstellar Industries might be creating AeroFighter-centric variants of this vessel, with the intent to allow
ammunition consumption rate compared to the original 20-racks, the supply of missiles has been increased significantly. the BattleCorps 1st Regimental Combat Team to significantly increase the number of AeroFighter assets at their disposal.
Given the outcome of the initial landing engagement during Operation LANCASTER, this would be a logical choice.
The Dragon, Ryūjin and Wyvern all received significant internal upgrades during the refit. The galleys were completely However, the establishment of the Acala Semi-Autonomous Region and subsequent increased focus on locally-based,
remodeled and upgraded to a considerably higher standard with improved fit and finish. The onboard medical facilities Acala-centric defensive forces may yet preclude the choice to manufacture many examples of such a DropShip—if any.
Cargo
Bay 1: Heavy Vehicles (72) 2 Doors
Bay 2: ‘Mechs (36) 4 Doors
Bay 3: Battle Armor (72 Suits) 2 Doors
Bay 4: Cargo (662 tons) 0 Doors
Bay 5: Satellite Bay 1 (50 tons) 0 Doors*
Bay 6: Satellite Bay 2 (50 tons) 0 Doors*
Ammunition: 100 rounds Long Tom ammunition (20 tons), 120 rounds Gauss Rifle
ammunition (15 tons), 288 rounds LRM-15 ammunition (36 tons), 576 rounds AMS
ammunition (48 tons)
Notes: Mounts 72 tons Clan Ferro-Aluminium Armor. Features an Angel ECM Suite,
10 tons of Communications Equipment, an aft-mounted dedicated Space Mine Dispenser,
an expanded medical Facility (8.5 tons of MASH Equipment), and an improved mess hall for
the crew (equal to a Field Kitchen).
Dreadnought Interstellar Industries’ history in larger-scale aerospace design began with militarized defense satellites in orbit over Terra in the early years of humanity’s reach for the stars. Following
the manufacturer’s involvement in development and construction of the earliest JumpShips, Dreadnought Interstellar had its name permanently scribed into the history books because of their heavy
involvement in the creation of the first class of black-water WarShip: the Dreadnought-class Battleship. It comes as no surprise that they have not been idle since these impressive accomplishments.
286 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
ORBITAL DEFENSE & REFIT PLATFORM (ODRP)
The group known as Murphy’s Marauders— whenever one of these stations is approached.
former mercenaries turned pirates—attempted
a raid on Acala III in December of 3053, with the The exterior hull of the entire station is encased in an almost obscene 8,100-ton shell of Lamellor Ferro-Carbide Armor,
goal of stealing the prototype Sumaire Assault providing excellent protection against even the most powerful naval-class weapons. In addition to the extremely dense
BattleMechs in the process of being developed armor of the station’s hull, an ODRP features an impressive double-array of Anti-Missile Systems, giving the station superb
by Dreadnought Interstellar Industries. Normally defensive capabilities. It is also equipped with a Large Naval Comm-Scanner Suite and an array of telescopes and long
the Dreadnought-class Battleship D.B.C. Trinity range sensors, allowing it to track any ships in-system with clarity. In the event of an enemy boarding action, the station
would have been in orbit of Acala III, providing is equipped to support seventy-two marines and forty battle armor marines to defend itself from within.
planetary defense. However, at the time that
the pirates conducted the raid, the Trinity had Each ODRP has a total of five aerospace fighter bays housed in the station’s central spire—often referred to as the
been deployed to the Waycross star system as station’s “apple core”—with each bay capable of supporting up to forty-eight AeroFighters. This allows the station to act
part of an extensive training exercise involving as a primary base of operations for orbital aerospace assets defending the planet. To assist with guiding damaged vessels
the Blackwood Templars Mercenaries and the into the repair bays, as well as to assist the station in conducting any needed repairs to itself, an ODRP is equipped with
Dreadnought BattleCorps. It was only through bays to support a total of eighty Small Craft. Most of the Small Craft assigned to ODRP stations are DII-SKRC-SC-DC1 Skua
the valiant actions of those on the surface of the Recovery Craft. However, examples of the newer -BC1 “Raptor” variant Skua Recovery Craft have recently begun to be
planet that the pirates were thwarted. assigned to these stations to support the aerospace fighter wings with their electronic warfare suites and decoys.
Although Murphy’s Marauders were defeated With six DropShip docking collars, each ODRP is most often supported by four Model-97 Octopus-class DropShips to
on the surface of Acala III, the pirate group’s only aid in capital ship repairs and construction. The Octopus-class DropShips typically use the docking collars located at the
DropShip, an Overlord, managed to lift off under ends of the four arms protruding from the station’s central spire, while the remaining pair of forward-mounted docking
heavy fire. The Overlord sustained damage collars are used for more general purposes.
during the escape, and shortly after exiting the
planet’s atmosphere, suffered a decompression The accommodations aboard an ODRP are exceptionally comfortable. The total of 1,769 crew members, medical
resulting in the loss of most of the ship’s fuel. The damage itself was easily repairable, but without more fuel, the DropShip personnel, marines, and bay personnel all have separate first-class quarters comparable to high-end officer’s quarters on
would not be able to reach the JumpShip that awaited its arrival at the nadir jump point. In an act of desperation, the a capital ship. Two hundred additional first-class quarters are available for personnel from any Dreadnought Interstellar,
heavily armed Overlord forced the defenseless dry dock orbiting Acala III to refuel the ship. During the refueling process, BattleCorps, or DefenseCorps JumpShip, DropShip or WarShip who are required to leave their ship but must remain on
an explosion occurred within the DropShip, setting in motion a chain reaction that destroyed the entire dry dock. The standby while repairs are being conducted. All personal quarters are housed within the pair of heavily armored 1.5-
explosion claimed three-hundred-eighty-nine lives, not including the pirates. The loss of Acala III’s orbital dry dock also kilometer-diameter gravity deck “rings” that are spun at a rate to produce 0.93-G. In addition to the personal quarters of
crippled Dreadnought Interstellar Industries’ ability to maintain their fleet of JumpShips. As this event occurred years the station’s personnel and guests, there is a lavish food court capable of handling the daily requirements of well over a
before the unveiling of the operational naval facilities in the Waycross star system to the public, this incident also disabled thousand people in each of the armored gravitational rings. Each ring also houses a complete medical facility. Should an
Dreadnought’s ability to service the D.B.C. Trinity—a vessel that was notorious for requiring near-constant maintenance. ODRP need to be evacuated, the station is equipped with nearly twice as many Escape Pods as would be needed to
evacuate everyone aboard the station—guests included.
The development program for the Orbital Defense & Refit Platforms (ODRPs)—titled the “Falling Skies” project—was
originally launched in the 3030s. In 3043, one year after the D.B.C. Trinity arrived in the Acala system to put a stop to a Due to the orbital nature of an ODRP, the station’s onboard Energy Storage Battery—ESB for short—receives a slow
series of attacks that had been plaguing the world, the project was cancelled. Only a partial central spire of one station charge, rendering the station a very ineffective JumpShip recharge hub. The reasoning behind the inclusion of an ESB in
had been built. The Falling Skies project resumed in 3054 in direct response to the new problems. The scope of the project the ODRP’s design is twofold. The primary purpose of the ESB is to store excess energy generated by the onboard fusion
was vast, but it was carefully planned with an accelerated construction schedule that could be accomplished safely. The reactors, allowing it to act as an emergency backup power supply in the event of a loss of primary power. Fully charged,
construction of the partially-built station resumed immediately, and various refinements were implemented. the ESB allows the station to operate for more than three months without use of its onboard reactors, even at peak non-
combat demand. If operating under peak combat conditions, the fully charged ESB will allow the station to operate for a
In the end, the first ODRP took just over four years to complete, and it went online in 3058, becoming the central base minimum of just over a week. The secondary purpose of the ESB is more in keeping with its original designed intent, and
of Acala III’s orbital defenses. The station cost over eighty-one billion C-Bills to build—and surprisingly, this was under that is to charge the K-F Drive of a docked vessel, but due to the slow recharge rate of the ESB combined with the station’s
budget. Although criticism arose over the exorbitant cost of the station, all but the most rabid critics were quieted when lack of a solar sail, this use of the ESB is generally for emergency use only.
the D.B.C. Trinity was reassigned to the Waycross system after the D.B.C. Phoenix—Dreadnought’s only other black-water
WarShip—departed the Inner Sphere with Task Force Bulldog in 3059. Without the Trinity standing as defender over Acala Research into much smaller and far less expensive orbital defense satellites designed for mass production began in the
III, the world’s inhabitants suddenly felt considerably more vulnerable. After various pirates and a handful of mercenaries early 3060s. The handful of resulting designs are simple weapon platforms intended to be part of a large-scale networked
began to probe the defenses of the world in 3060, the feeling of the general population shifted from discontent with the and automated planet-wide orbital defense system. These automated defense satellites are designed to help complete
perceived unnecessary spending toward the need for more effective planetary defenses. ODRPs Beta and Gamma were an orbital defense network modeled vaguely on Terra’s SDS system during the height of the Star League. As of 3085,
completed six years later, in 3066, marking the end of the planned Falling Skies project. construction has yet to begin due to difficulties in attempting to recreate the automated control system itself. Examples
of the Caspar II and Caspar III Command Automated Robotic System developed by the Word of Blake—and salvaged post-
An ODRP is a massive, largely hollow, heavily armed, heavily armored, dual-ringed space station. It is designed to serve Jihad—have contributed significantly toward a new Automated Orbital Defense System (AODS) being developed by
as a combination of dry dock facility and orbital defense battle station. In terms of its shipbuilding and maintenance Dreadnought Interstellar Industries for the defense of Acala III. Until the development of the central operating system
facilities, the forward section of the station houses an internal pressurized bay that can construct and service as many as has been completed, these orbital defense satellites—tentatively nicknamed “Gun-Sats”—remain on the drawing board.
five DropShips simultaneously; and at the station’s aft, there is an exterior dry dock capable of constructing and repairing
capital ships of virtually any class. To prevent any future losses like that of the planetary dry dock in 3053, the station is In 3067, the choice was made to construct a vessel that had not been seen in the Inner Sphere since the middle of the
outfitted with a heavy weapons array. It is primarily armed with a total of forty-eight Heavy Naval Gauss Rifles, while two- 29th Century: A Firebrand-class Battleship. A deadly class of WarShip designed and built by Dreadnought Interstellar
hundred-forty Extended Range Particle Projector Cannons provide an effective defense against smaller targets. Most of Industries during the time of the Star League, the Firebrand had been all but forgotten. However, during the Dreadnought
the station’s weapons are normally retracted into armored coverings to avoid unnecessary risk of high-speed impacts BattleCorps 1st RCT’s extended stay in Clan space following Operation BULLDOG, the BattleCorps managed to acquire the
with space debris. However, it is standard procedure that two of the primary turrets are deployed as a precaution vessel’s complete technical specifications and construction blueprints from Clan Snow Raven.
DropShips docked to the Mammoth II via unconventional “nose-in” docking collars which featured extremely heavy-
duty docking arms that locked down around the DropShips to hold them in place. It was so strongly believed that the
innovation would become common practice that, even in the 31st Century, all spheroid DropShips manufactured in the
Inner Sphere—be they military or civilian—are still required by interstellar law to be produced with latching points for
the nose-in docking ports that remain unique to the Mammoth II. (It has since been learned that even Clan-made
DropShips include these attachment points.)
Soon after the introduction of the Mammoth II, most of the original Mammoth JumpShips were refitted to the same
specifications as the newer vessel. Both the refit Mammoth and the newly produced Mammoth II were armed with a total
of twelve Particle Projector Cannons, spread evenly around the ship to act as meteor-deflectors and light point-defense.
During the refit, the original Mammoth-class JumpShips were equipped with the upgraded docking modules mounted to
the nose of the vessel; meanwhile, the unused obsolete docking ports along the JumpShip’s spine were removed. The
armor of nearly all these older vessels had sustained damage due to impacts with high-speed objects and debris, so they
were reskinned with the same modern Standard Aerospace Armor used in the newer Mammoth IIs. However, a handful
of the refitted Mammoths were in good-enough condition that they retained their original Primitive Aerospace Armor.
Created long before the introduction of standard DropShips, the Mammoth “Colonial JumpShip” was manufactured by As with most JumpShips, the original Mammoth was designed with a larger rear engineering section and sleek, long
Dreadnought Enterprises—now Dreadnought Interstellar Industries—as an early interstellar colonization vessel. The first main hull fitted with four docking ports on each side. The unique lower pylon and upper observation lounge areas that
ship of the class finished construction in 2231. These JumpShips soon became well-known workhorses, commonly used sprout from the rear engineering section help to positively identify this vessel in a lineup of JumpShips. However, the
for transporting prefabricated structures and colonization-related resources from the Sol system out into the void design of the Mammoth II has significant physical differences. The iconic “hammerhead” twin docking assemblies that
beyond. These vessels were produced at Dreadnought’s shipyards orbiting Mars and Venus, with as many as five different sprout from the sides of the vessel’s nose—each ending in four docking collars—set the Mammoth II apart from any other
dry dock facilities being simultaneously tasked with manufacturing these massive JumpShips. known JumpShip; and it has smoother sides amidships, as it lacks the older style docking ports of the previous generation.
The five-hundred-thousand-ton Mammoth-class JumpShip was by far the most impressive interstellar vessel ever built By the early 25th Century—prior to the introduction of the Mammoth II—an ever-increasing number of JumpShips and
at the time of its introduction, and it is still considered as one of the greatest leaps forward in the history of JumpShip WarShips were recorded as “Lost, Presumed Destroyed” due to misjumps, most of which were credited to navigational
design. The list of features that set the Mammoth apart from any other class of JumpShip is lengthy. The luxurious errors. In 2438, because of this increasing tally of lost crews and vessels, Dreadnought Interstellar formed what soon
accommodations were far above the standards expected of any interstellar vessel. Every one of the personal quarters for became known as the Dreadnought DiscoveryCorps. The DiscoveryCorps was tasked with seeking out lost and derelict
the fifty-six crew—including the bay personnel—and seventy-six passengers were all exceptionally comfortable first-class interstellar vessels, the search and rescue of stranded ships and those aboard them, and discovery of untapped resources.
cabins. Additionally, the Mammoth featured a remarkable onboard eatery that included a well-equipped kitchen and a
nicely furnished mess hall, both of which were housed on the inner levels of the artificial gravity decks. Although the The first iteration of Dreadnought’s DiscoveryCorps consisted of seventy Abeona DiscoveryCorps-class DropShuttles,
gravity generated on those levels was considerably reduced compared to the outer levels, it allowed the crew and each fitted with special sensor suites and telescopes. These DropShuttles were transported by independently owned and
passengers to eat in a comfortable environment with at least some gravity. operated JumpShips in exchange for covering the operating costs of the JumpShips themselves. As the JumpShips simply
continued their normal business with the DiscoveryCorps having no real control over where they were going, the early
The aptly-named Mammoth featured eight docking ports located along the ship’s spine, as well as a forward landing days of the DiscoveryCorps were not particularly impressive.
bay that fits four Small Craft. The massive vessel’s cavernous cargo bays had capacity for more than 2,400 tons of supplies
and equipment, and it carried enough fuel to function continuously for more than eight months. Combined, these features After nearly thirty years of operating with little to show for it, the Dreadnought DiscoveryCorps was on the verge of
gave this vessel an unprecedented operational time between resupply stops. Defensively, the Mammoth was armed with being shut down. However, the crew of the D.I.I.S. Fetcher—one of the first Abeona DiscoveryCorps-class DropShuttles to
a total of eight Primitive Autocannon/5s, installed in pairs along the forward- and aft-sides of the vessel. The exterior hull receive a DropShip refit—made a discovery in an uninhabited star system in 2467 that changed everything.
of the ship was exceptionally heavily armored for a commercial JumpShip. The attention to detail in every aspect of the
Mammoth’s construction set Dreadnought Enterprises ahead of the curve in comparison to all its market competitors, Shortly before the JumpShip transporting the Fetcher was due to jump to the next system on its route, the Fetcher
leading to considerable financial success and future contracts from various business ventures. detected a crippled JumpShip so close to the system’s star that it would never have been detected were it not for the
Fetcher’s specialized sensors and scopes. The derelict JumpShip appeared to have suffered catastrophic damage, later
The technological innovation, engineering, and manufacturing capability displayed in the creation and production of learned to be the result of a misjump. The Captain of the JumpShip transporting the Fetcher agreed to stay to investigate.
the Mammoth is often credited for Dreadnought Enterprises being awarded the contract to produce the first interstellar
WarShip by the Terran Alliance in 2295. Dreadnought Enterprises was renamed Dreadnought Interstellar Industries that The Fetcher soon found the derelict to be damaged beyond repair—the JumpShip’s spine broken—and abandoned. Its
same year. The manufacturer later christened the first-ever interstellar WarShip the T.A.S. Dreadnought, the first in the emergency beacon had been damaged and was not transmitting. After boarding the derelict, the Fetcher’s crew learned
line of Dreadnought-class Battleships. Some criticized the manufacturer as being “egotistical” for using their own name that the DropShips being transported by the crippled JumpShip had departed and headed to the only potentially habitable
for the title of the vessel and class, but Dreadnought Interstellar Industries stuck with its decision. world in the star system in hopes of surviving long enough to be rescued.
After assembling a fleet of thirty JumpShips, Dreadnought Interstellar Industries formed the JumpShip Allied Transport To provide them with the ability to conduct investigations, an Abeona DiscoveryCorps DropShip was assigned to each
Company (JATC) in 2480. The JATC operated under the Dreadnought banner, independent from any other organization, of Mammoth II DiscoveryCorps JumpShips as a support vessel. In 2485, it became common practice to also supply each
and held no allegiance to any of the Great Houses or Periphery States. Equally, the JATC did not seek to become involved of these JumpShips with four DII-SKRC-SC-J1 Skua Recovery Craft, as these small ships allowed DiscoveryCorps crews to
in any of the internal or external conflicts within or between the often warring nations. respond quickly and easily to any new discoveries, as well as conduct any needed repairs to the JumpShip while in transit.
The JATC offered fairly-priced transport and passage to any who wished to make use of their services. As part of their Starting in 2597, all fifty Mammoth II DiscoveryCorps-class JumpShips underwent an unusual exterior hull refit for a
operational principles, the JATC would not transport military DropShips across borders unless authorized by the military civilian vessel: Ferro-Carbide Armor. Though expensive, this tough armor effectively doubled the protective quality of the
of the nation whose borders were being entered. They would also only transport goods that had been inspected and exterior hull, helping to protect the already expensive investment that this JumpShip represented.
authenticated by their own personnel, resulting in a surprisingly minimal number of incidents involving illegal smuggling
and arms-trafficking. Numerous discoveries have been made and many lives saved by the crews of Mammoth II DiscoveryCorps JumpShips
over the six centuries since their introduction, but two of these ships made discoveries that stand above all others: the
The purpose of the JATC was made clear through these limitations: the JATC was to be first and foremost a civilian D.I.I.S. Rockturner and the D.I.I.S. Delara. In 2887, while exploring the GS-229 star system—near the Lamon system—the
transport company intended to enhance interstellar trade. In exchange for the increased trade and economic prosperity Rockturner discovered a centuries-old derelict vessel. This derelict would turn out to be none other than the T.H.S. Trinity,
that the JATC would assist in building, Dreadnought Interstellar itself was allowed to freely transport their own ships and the last of the Dreadnought-class Battleships produced. She was adrift, but salvageable. Almost sixty years later, in 2945,
goods across the territories of the governments that had signed the JATC charter, without any tariffs or unreasonable the Delara discovered the S.L.S. Phoenix, a unique type of Texas-class WarShip which had been preserved in near-perfect
restrictions. The JATC was universally accepted by all the Great Houses, the Terran Hegemony, the Magistracy of Canopus, condition, effectively cocooned inside of an asteroid for more than two centuries in the ES-150/D star system.
and most other Periphery States—all of whom signed the charter of the JATC. However, some of the smaller Periphery
States refused to sign the charter for various reasons. Forty-three Mammoth II DiscoveryCorps-class JumpShips remain in active service of the Dreadnought DiscoveryCorps
as of 3085. Five were destroyed during the First and Second Succession Wars and one was lost to a tragic misjump in
Through Derrick Theris’ astonishing continued financial support, the choice was soon made to expand the size of the 2909, never to be heard from again. The D.I.I.S. DiscoveryCorps—the prototype and first ship of her class—was retired
JATC fleet considerably. This expansion included the introduction of a specially-modified class of JumpShip, refitted to from service in 3064 after more than five centuries of service. Unfortunately, as a prototype, certain aspects of the vessel
with all the equipment and supplies needed to carry out the mission statement of the Dreadnought DiscoveryCorps. With inevitably led to her becoming unserviceable, resulting in the ship’s “early” retirement. Only one surviving example of an
the Mammoth’s perfect record of never having suffered a misjump, the Mammoth II was selected to receive this special all-original Mammoth Colonial JumpShip—the Pathway To The Stars—is known to still exist. Although their Kearney-
refit. In 2493, the first Mammoth II “DiscoveryCorps” JumpShip was launched. Due to the enormous cost of each vessel, Fuchida Drives have long since been deactivated, both the D.I.I.S. DiscoveryCorps and the Pathway To The Stars are kept
and the need to focus manufacturing resources on building ships that could be sold for profit, it would be nearly a century in orbit over Acala III. Both vessels can be toured as part of a 2,000 C-Bill Exclusive All-Access Tour Pass of Acala III’s
before the fiftieth, and final, example of this very specialized ship class was completed, in 2582. Naturally, various Interstellar Museum.
refinements and seamless improvements were made with each vessel.
The Mammoth II DiscoveryCorps JumpShip was broadly the same as the standard Mammoth II, but it featured some
noteworthy differences. The most striking aesthetic difference was the installation of a highly sophisticated Large Naval
Comm-Scanner Suite, as well as a broad array of advanced telescopes—including a High-Resolution Imager and an
Infrared Imager. This suite of sensors and scopes allowed the DiscoveryCorps personnel aboard the vessel to continuously
search for any signs of stranded vessels, detect distress signals that otherwise might have gone unheard, and any signs of
lost or derelict vessels that may contain valuable technology.
Twenty-seven specialized DiscoveryCorps personnel were assigned to each of these vessels to operate the suite of
sensors and telescopes. To help protect the very specialized—and very valuable—onboard equipment, a Mammoth II
Docking Ports: 8 Gravity Decks: 3 (85-meter diameters, all) Type: Mammoth II DiscoveryCorps (Ferro-Carbide Refit)
Escape Pods: 0 Life Boats: 23 Classification: JumpShip (Limited Production)
Crew: 6 officers, 28 enlisted/non-rated, 2 gunners, 20 bay personnel, 76 passengers Technology Base: Star League Introduced: 2597
Mass: 500,000 tons Heat Sinks: 154 Single
Ammunition: 240 rounds Primitive Prototype Autocannon/5 Ammunition (16 tons) Length: 820 meters Structural Integrity: 1
Sail Diameter: 1,520 meters Battle Value: 4,795
Notes: Equipped with 277.5 tons of Primitive Aerospace Armor. Also equipped with an improved mess hall (equivalent to Fuel: 1,000 tons (2,500 points)
a Field Kitchen). Features the following Design Quirks: Docking Arms. Tons/Burn-day: 39.52 Armor
Safe Thrust: 0 Fore: 38
Weapons: Capital Attack Values (Standard) Maximum Thrust: 0 Fore-Sides: 38
Arc (Heat) Type Short Medium Long Extreme Class Sail Integrity: 6 Aft-Sides: 36
FL/FR (2 Heat) K-F Drive Integrity: 10 Aft: 36
2 Primitive Autocannon/5 (60 rounds) 1 (10) 1 (10) – – Autocannon
AL/AR (2 Heat) Cargo
2 Primitive Autocannon/5 (60 rounds) 1 (10) 1 (10) – – Autocannon Bay 1: Small Craft (4) 2 Doors
Bay 2: Cargo (1,300 tons) 4 Doors
Bay 3: Cargo (481.5 tons) 4 Doors
As a result of the limited firing arcs of the ship’s main guns, the Jackal is most effective when attacking a target head-
on, where it can simultaneously fire all its main guns on a single target. To help make best use of its forward-firing heavy
weapons, the design of the Jackal incorporates particularly powerful engines, as well as reaction control thrust systems
that are augmented by massive gyrostabilizers, allowing for impressive acceleration and maneuverability. When pushed
to their maximum, these potent engines can produce enough thrust to generate as much as 4-G of acceleration.
Defensively, the Jackal has a total of forty-eight standard Particle Projector Cannons. The original intent had been for
there to be twice as many of these weapons, to have them divided into eight separate firing arcs, and for them to be
spread out more evenly along the hull to provide overlapping firing arcs. Unfortunately, design limitations and cost-cutting
resulted in a reduced number of these weapons being installed, even on the prototype. Despite this, the Jackal has ample
point defense firepower, with multiple braces of four PPCs to defend each quadrant of the ship’s perimeter.
As the Jackal is an exceptionally aggressive vessel built with a focus on engaging an opponent head-on, it has been
intentionally designed to present a small frontal target profile in combat. In addition, the ship’s armor protection is heavily
reinforced along the ship’s bow and front-sides. Due to the design decisions made to emphasize the Jackal’s strengths,
the vessel’s aft is not only lightly armed, but it is also the most vulnerable in terms of relative armor protection.
Historically, the success and survival of a Jackal-class Destroyer in combat has generally been most dependent—command
decisions aside—on the skill of the ship’s helmsman and main gun operators, as the vessel needs to be maneuvered to
maintain a targeting solution for the gunners and keep the ship’s heavier armor facing its opponent. Given the Jackal’s
sheer firepower, the accuracy of the main guns’ first volley will typically be most telling as to an engagement’s outcome.
Each of these ships has the capacity to carry and support up to twenty-four AeroFighters and eight Small Craft. Twin
Some of the information regarding the original commissioning of the Jackal-class Destroyer has been lost to the ravages fly-through fighter launch bays are housed in the outermost port and starboard sections of the vessel’s hull, with twelve
of time, but all indications point to the vessel being first commissioned by House Steiner as a heavily armed patrol vessel fighters assigned to each bay. The fighters themselves are launched via electromagnetic catapults installed in the “floor”
in the late 26th Century. In the end, this class of black-water Destroyer was used primarily by the SLDF, but it did also see and “ceiling” of each bay. The fighters can only be launched two at a time from each launch bay, but the deployment rate
significant use by Steiner forces. is remarkably rapid, ensuring the fighters are moving fast enough that they cannot be easily targeted immediately upon
launch. Although intended primarily as the method by which fighters are to return to the bays, the fighters can also exit
Following their previous success in the rapid development and manufacturing of the first class of black-water WarShips, through the aft-facing doors under their own power. Meanwhile, the two launch bays for the Small Craft are forward-
Dreadnought Interstellar Industries was tapped to create this new class of combat vessel. It had been two centuries since facing, located directly below the main guns, low down near the vessel’s ventral hull, with each bay supporting up to four
the Dreadnought-class Battleships were built, but the manufacturer proved to still be up to the task. Repeated budget Small Craft—typically DII-SKRC-SC-J1 Skua Recovery Craft.
cuts throughout the project led to considerable delays in development, and in the end resulted in the new ship class being
less well-equipped than originally planned. Despite the cut corners, the Jackal proved to be an effective combat vessel. The nature of the Jackal’s relatively compact design results in the twin 50-meter-diameter gravity decks being fitted
inboard, a fair distance aft of the ship’s midline, ensuring no structural integrity weaknesses result from the inclusion of
Development of the Jackal began in 2579. The original prototype completed testing in 2589, and the first production the gravity decks. It should be noted that in the event of a prolonged maximum acceleration burn, the aft gravity deck
vessels entered service in 2597. There were a handful of significant differences between the original prototype Jackal— can become severely overheated due to the packaging of the main engines around it. Depending on how long the engines
the S.L.S. Jackal—and the final production design of the ship class. The prototype also lacked many of the conveniences remain at full power, it can be several hours to nearly an entire standard day before the rear gravity deck can cool down
featured in the production model vessels, such as the improved mess hall, and the corridors of the prototype were also to a comfortable level once the engines have been throttled down. As the crew quarters, mess hall and general living
noted to be slightly more cramped. Additionally, the production model Jackal-class Destroyers all featured Small Naval areas are housed forward of the gravity decks, this design defect does not impact the overall livability aboard the vessel.
Comm-Scanner Suites, improving their sensor range, while the prototype S.L.S. Jackal did not. Last, but certainly not least,
the S.L.S. Jackal only featured a single DropShip docking collar, while all other examples of the vessel added a second Between 2617 and 2622, all known Jackal-class Destroyers in service received a refit, equipping them with Anti-Missile
docking collar to the ship’s ventral hull. After completing trials and testing, the S.L.S. Jackal entered service in 2595, two Systems. This increased the survivability of these vessels dramatically. This refit installed a total of 80 Anti-Missile Systems,
years before the first “standard” ships of her class were completed. an equal number of additional heat sinks to cool them, and four hundred tons of ammunition to feed these thirsty point-
defense guns, as well as improved fire control systems to manage it all. Although various issues had resulted in them
The Jackal-class Destroyer is a surprisingly capable vessel for its size. Weighing in at “just” 500,000 tons, this class of being initially omitted, the Jackal had been designed with such countermeasures in mind from the start. Because of this,
WarShip has historically been often underestimated by those less familiar with the ship’s specifications and feel it to be the installation of these additional defensive systems was a very straightforward affair. Naturally, all Jackals built during
a more typical “patrol boat”. However, the Jackal is not only impressively mobile, but also terrifyingly well-armed as an or after 2617 included these systems as standard.
offensive craft, capable of dispatching some ships even twice its size with as little as a single concentrated volley or two
at medium range. Special Jackal-class Destroyers equipped with Lithium-Fusion Batteries started to be built exclusively for the Star
League Defense Force in 2677. As each was nearly twice the cost of the standard Jackal, the number of ships built to this
With twin forward-firing Heavy Naval Particle Projector Cannons mounted under the vessel’s bow, as well as a third specification was extremely limited. It is believed by most historians that only six of these vessels were ever constructed,
installed between the ship’s massive engine clusters facing aft, the Jackal-class Destroyer has acceptable long-range although some incomplete intelligence records from that era point to the possibility that there might have been as many
firepower for use while closing in on a target. Once the Jackal has closed range with its opponent, however, that is when as nine. The reason for this inconsistency in records-keeping has yet to be determined.
Additional Notes: Four additional variants of the Jackal-class Destroyer are known to exist.
Type: Jackal (2617-Spec)
Classification: Black-Water Destroyer (Mass Production) The original mass-produced 2597-Spec Jackal-class Destroyer lacked Anti-Missile Systems altogether until these vessels
Technology Base: Star League were refit to 2617-Spec. This variant was equipped with 1,965 single heat sinks and featured a larger cargo bay capacity
Introduced: 2617 Reintroduced: 3083 of 29,009 tons. (Battle Value: 95,171)
Mass: 500,000 tons Heat Sinks: 2,045 Single
Length: 655 meters Structural Integrity: 80 The prototype of the ship class, the S.L.S. Jackal (2589-Spec Prototype), is identical to the 2597-Spec production variant
Sail Diameter: 865 meters Battle Value: 99,267 with the following exceptions: It has Ferro-Carbide Armor instead of Lamellor Ferro-Carbide Armor (identical allocation).
Fuel: 5,000 tons (12,500 points) It only has a single DropShip docking collar (dorsal mount). It does not have a Small Naval Comm-Scanner Suite and does
Tons/Burn-day: 39.52 Armor not feature an improved mess hall. It has a crew of 27 officers, 118 enlisted/non-rated crew, 17 gunners, 88 bay personnel,
Safe Thrust: 5 Fore: 200 36 marines, and 6 passengers. Its main cargo hold has a maximum capacity of 30,214 tons. (Battle Value: 95,171)
Maximum Thrust: 8 R/L Fore-Side: 155
Sail Integrity: 4 R/L Aft-Side: 125 The 2677-Spec Lithium-Fusion Battery variant is based directly on the 2617-Spec variant of this vessel. It features a
K-F Drive Integrity: 9 Aft: 88 Lithium-Fusion Battery and has a 22,553-ton cargo capacity. It is otherwise unmodified. (Battle Value: 99,267)
Cargo The 3083-Spec of the Jackal-class Destroyer, otherwise known as the Dreadnought BattleCorps variant, is based on the
Bay 1: Fighters (12) 2 Doors standard 2617-Spec variant of the vessel. It directly replaces all the standard PPCs with an equal number of Clan-tech ER
Bay 2: Fighters (12) 2 Doors PPCs and adds 200 heat sinks to handle the added stress on the cooling system. This increases the range band of the PPCs
Bay 3: Small Craft (4) 1 Door to “Long” and boosts the damage value of each bracket of four ER PPCs to 6 (60). The onboard marine count is reduced to
Bay 4: Small Craft (4) 1 Door 30. 24 battle armor marines are added, along with a single-door ventral bay to house their suits. Bay personnel count is
Bay 5: Cargo (27,553 tons) 4 Doors increased to 124, while the ship’s cargo capacity is reduced to 27,298 tons. (Battle Value: 104,769)
Without the ability to produce or acquire new parts to maintain the Firebrands still in service, many of these ships had
to be gutted for parts to maintain and repair others. By the time the SLDF launched the final assault on Terra in 2777,
they had a mere thirty-two Firebrand-class Battleships still in service. Shortly before the assault on Terra, a diversionary
task force of forty ships was assembled to jump to a pirate point near Mars to draw away the bulk of the SDS drone ships
defending the system. Of Task Force Leonidas’ forty WarShips, roughly fifteen of them were reportedly Firebrand-class
vessels. The crews of these Firebrands volunteered to join the diversionary task force because they knew well the sheer
firepower their vessels carried. They were able to destroy numerous enemy ships before being at risk of destruction, and
the diversion had to succeed, regardless of the cost. It did. While none of the vessels of Task Force Leonidas survived the
mission, they opened the door for the rest of the Star League Defense Force to enter the system and complete the mission.
The Firebrand is armed with a forward-firing brace of three Heavy Naval Gauss Rifles, giving it a powerful initial punch.
While impressive by themselves, the Naval Gauss Rifles pale in comparison to the real focus of this vessel—its vast capital
missile array. A total of sixty-four AR-10 Missile Systems are installed in twin clusters of thirty-two in the ship’s sides.
Backing all these powerful primary weapons at long range is a respectable array of forty NL55 Naval Lasers spread around
the vessel to provide overlapping fields of fire. To dissuade any hostile ships from getting too close, the Firebrand boasts
a total of twelve Class-30 Naval Autocannons, with three pairs of the powerful cannons on either side of the ship’s forward
hull. With a total of ten Barracuda Missiles, ten White Shark Missiles, and ten Killer Whale Missiles for each individual AR-
10 Missile System, as well as comparable supply of ammunition for its Gauss Rifles and autocannons, the Firebrand carries
enough ammunition to participate in an extended military campaign without much need for resupply. Defensively, the
Following Dreadnought Interstellar Industries’ heavy involvement in the creation of the Dreadnought-class Battleship Firebrand is equipped with a total of ninety-six Anti-Missile Systems, as well as eighty Particle Projector Cannons spread
at the turn of the 24th Century, the manufacturer turned its attention to other endeavors. However, Dreadnought never across the vessel’s sides, creating an extremely effective point-defense screen. The Firebrand’s capabilities are further
lost its association with the iconic vessel, as even the manufacturer’s very name was a reminder of the groundbreaking enhanced by a Large Naval Comm-Scanner Suite, tripling the vessel’s effective sensor range.
vessel class. Nearly three centuries later, in 2597, all but immediately after the introduction of the Jackal-class Destroyer,
the Star League Defense Force commissioned Dreadnought to produce a more powerful WarShip. The requirements for The Firebrand is considered one of the most terrifying black-water WarShips ever created, but it is not flawless. Though
the vessel made up a daunting list, but the project’s goal was clear—it was not at all required to be the biggest capital remarkably heavily armored, the vessel’s design inherently makes it somewhat difficult to disengage from an opponent
ship ever built, but this was to be the single most terrifying class of WarShip ever created. Where another company would without exposing its considerably thinner aft armor to the enemy. The thinner aft armor was logically justified through
have been hesitant to take on such a project, Dreadnought Interstellar Industries embraced the SLDF’s challenge. the belief that if a Firebrand was forced to disengage and withdraw from battle, it most likely would have taken severe
damage to its armor elsewhere, resulting in the aft section becoming quite possibly the heaviest armor the ship had left.
After more than two decades was spent developing it, Dreadnought Interstellar Industries’ Firebrand-class Battleship The aft armament, however, is the true “Achilles’ Heel” of the Firebrand. While it does have aft-mounted weapons, they
was introduced in 2622—and immediately became a benchmark by which all other WarShips could be judged. The easily primarily consist of just a handful of NL55 Naval Lasers. Compared to the weapons elsewhere on the vessel, the lasers
recognizable silhouette of the vessel was a double-edged sword. Although the vessel could easily turn the tide of a battle, alone are virtually ineffective in capital ship combat. The one saving grace the Firebrand has is that the AR-10s’ capital
or even prevent one by its very presence, any time one or more of these easily identifiable vessels were involved in a missiles, once fired, can change direction to target a vessel behind the ship. Still, the lack of effective rear weapons and
combat situation, they quickly became the highest-priority targets for the opposition. The immense destructive force that thinner rear armor together mean that—by its very design—once engaged, it can be difficult for a Firebrand to break off
a Firebrand could bring to bear on an opposing vessel became well known throughout the Inner Sphere within a fortnight and withdraw from combat. This problem is compounded by a lack of a Lithium-Fusion Battery, leading to a situation
of its introduction, and the ship class quickly became every commander’s worst nightmare. The Firebrand became all but where a Firebrand that has just jumped into a star system cannot jump away to escape unless it has had time to recharge
synonymous with the human fight-or-flight reflex, in that the enemy either engaged it directly, or all but immediately before entering battle. Such a casual recharge opportunity is a rarity if the vessel is on the offensive.
withdrew from battle. This effect allowed the Firebrand to become something of a legend in terms of military history.
With first class cabins for every member of the crew—bay personnel aside—and standard quarters for up to twenty
With its devastating weapons array, astonishingly durable armored hull, powerful engines, and good maneuverability, passengers, the Firebrand-class Battleship is equipped with superior accommodations for its crew than virtually any
the Firebrand is arguably the single most dangerous class of manned black-water WarShip ever devised. Despite having military vessel in history. While initially this may seem wasteful, the closer one investigates the specifications of the vessel,
performance rivaling—if not far exceeding—any of its contemporaries in nearly every other respect, the one single the more significant these design decisions become. In addition to a remarkably abundant ammunition supply for a
characteristic that stands out most with the Firebrand-class Battleship is its armament. The Firebrand can destroy virtually WarShip, the Firebrand also has a massive fuel capacity, allowing it to maintain a comfortable 1-G of thrust constantly for
any enemy vessel that it encounters with an expediency that left all the SLDF representatives and evaluators shocked into well over a year before needing resupply. The Firebrand also carries within its heavily armored hull a total of three eighty-
silence for a long moment after the first demonstration of the prototype’s sheer firepower on June 9th, 2622. This first five-meter-diameter gravity decks and an extremely well-equipped, comfortable mess hall to feed the crew. Between all
vessel, the S.L.S. Firebrand, entered service of the SLDF Navy on Christmas Day of that year. these accommodations and facilities—as well as considerable attention to detail given to the operation of the most basic
“The ship and crew of the D.B.C. Trinity are to be remembered with reverence. On 27 May, 3075, In the face of impossible at Dreadnought’s feet. Di Tron alleged that Dreadnought’s design revisions were the cause. Despite both ships being more
odds, they gave all they had to try to save the soldiers and civilians who had yet to be evacuated from Theris. May their than a century old, Dreadnought was investigated for possible sabotage. Many experts pored over the revised design
sacrifice, as well as that of those stationed on the world they fought to save, never be forgotten.” schematics—which by then had long since been declassified and entered into public record—as well as the library of
– Trinity Memorial Hall Dedication Plaque, New Sydney, Acala III holovid recordings and other records regarding the construction of the Trinity and Challenger. None of the investigators
were able to find any fault with the revisions that could cause such a catastrophic outcome, and the case was dismissed.
Of the seven Dreadnought-class Battleships built, the T.H.S. Trinity was one of only two lightly-revised examples. Centuries later, on September 12th, 2887, the T.H.S. Trinity was found, as were many answers to the question of the
Launched in August of 2318, the Trinity was the last ship of her class ever built. Like all Dreadnought-class Battleships, the ship’s disappearance. The onboard computer logs, surprisingly discovered intact after more than four hundred years,
Trinity was constructed by Dreadnought Interstellar Industries, who worked in conjunction with Di Tron Heavy Industries detailed a power management malfunction as the ship initiated an interstellar jump from the Rahne system. Intending to
to design and build this powerful first class of interstellar WarShip. jump to the Lamon system, 25.9 lightyears away, the Trinity instead emerged from its fateful jump in the uninhabited GS-
229 system in a crippled condition. The GS-229 system was a full seventeen lightyears farther away than the Lamon
The T.H.S. Trinity served the Terran Hegemony during the early years of what would become known as the Age of War, system, meaning that the Trinity had managed to far exceed the known maximum safe jump range of thirty lightyears.
only to be lost in 2438 to a misjump. Strangely, the Trinity’s “twin sister” vessel, the T.H.S. Challenger—the only other This limit is shared by all known Kearny-Fuchida Drives—the backbone of all interstellar travel—even today.
ship designed to the same specifications—suffered the same misfortune soon after, suggesting the two incidents may
have been related. Di Tron was quick to point fingers at Dreadnought Interstellar, laying the blame for the terrible losses With numerous hull breaches and failing life support systems, the crew attempted to find safe harbor on the barely
The D.B.C. Trinity’s automatically-ejected log buoy later indicated that—following reports of gunfire inside the ship’s DropShip Capacity: 0 Gravity Decks: 2 (both 150-meter diameters)
ammunition magazine, as well as an explosive device being spotted—Colonel Ezra Jones, the Trinity’s commander, Escape Pods: 60 Life Boats: 60
ordered the ship into a full-on ramming maneuver against the slow-moving third Pinto. Unfortunately, the nearly-crippled Crew: 146 officers, 518 enlisted/non-rated, 98 gunners, 128 bay personnel, 20 first-class passengers, 50 second-class
Trinity was destroyed just before she could complete the maneuver. The log shows that shortly after the ship accelerated passengers
to ram the stricken Pinto, a massive explosion was registered by internal sensors, originating in the ammunition magazine.
The log then immediately cut off as the buoy was ejected. The Trinity’s ammunition stores, detonated by an explosive Ammunition: 240 rounds NAC/10 ammunition (48 tons), 360 rounds NAC/20 ammunition (144 tons), 1,440 rounds AC/2
planted by a Blakist operative aboard the vessel, nearly blew the ship in half. The lack of additional impact damage to the ammunition (32 tons), 1,280 rounds AC/5 ammunition (64 tons)
ship’s bow made clear that the explosion had thrown the Trinity off her intended collision course with the enemy vessel.
Notes: Equipped with 1,147.5 tons of Primitive Aerospace Armor.
Over the next four weeks, the Dreadnought DefenseCorps Theris Regiment was systematically torn apart, and the
mostly gutted Cameron MechWerks facility was captured by the Word of Blake. The existence and location of CrossWays Weapons: Capital Attack Values (Standard)
Station was shortly thereafter discovered by the Blakists—an added prize in the eyes of the attackers. The remaining pair Arc (Heat) Type Short Medium Long Extreme Class
of Word of Blake Pinto-class Corvettes moored themselves at CrossWays Station to claim it as their own, as well as to Nose (376 Heat)
conduct repairs to their vessels using the station’s remaining facilities. On June 25th, two days after the ships docked with 3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
the station and began repairs, twin thermonuclear explosions occurred within CrossWays Station, instantly obliterating it 3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
and the Pintos. Several more thermonuclear detonations were recorded on the surface of Theris, some originating within 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
the Cameron MechWerks facility. The crews of the Word of Blake JumpShips sitting at the zenith jump point were unable 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
to do anything but bear witness as all other human life in the star system was annihilated in a matter of minutes. 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
The D.I.I.S Renegade nearly burned out her jump drive to reach the D.B.C. Phoenix to notify her of the Word of Blake FL/FR (136 Heat)
attack on Theris. The Phoenix returned to the Waycross system on June 26th, but arrived too late. Officially, immediately 4 NAC/10 (60 rounds) 40 (400) 40 (400) 40 (400) 40 (400) Capital AC
after entering the star system at the zenith jump point, the Phoenix ordered the Word of Blake JumpShips to stand down. 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
The Blakist JumpShips were reported as having refused to comply, instead maneuvering to turn their station-keeping 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
particle fountain drives toward the Phoenix to act as powerful weapons against the WarShip. In response, the Phoenix 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
destroyed both JumpShips. Years later, this rather improbable official story is still the subject of much scrutiny. 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
LBS/RBS (376 Heat)
An extended search for any survivors in the Waycross system was conducted, be they friend or foe. None were found. 3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
On 27 May, 3078, three years to the day after the destruction of the D.B.C. Trinity, the Trinity Memorial Hall opened 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
on Acala III to honor and remember those lost in the horrific events that occurred in the Waycross system in 3075, as well 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
as all those who have lost their lives and/or served with distinction under the Dreadnought BattleCorps and DefenseCorps 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
banners. The massive, cathedral-like structure is centered around a large sculpture depicting the D.B.C. Trinity as she was 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
before her final battle over a large wall of small dedication plaques, each honoring an individual crew member who was AL/AR (136 Heat)
aboard the Trinity when she was destroyed—except for those who were reported in the ship’s logs to have been traitors 4 NAC/10 (60 rounds) 40 (400) 40 (400) 40 (400) 40 (400) Capital AC
during the ship’s final days and hours. Forever standing guard over the front entrance of the Trinity Memorial Hall is a 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
fully detailed, nearly-full-scale statue of Lieutenant Ellie Shaw’s Wolverine BattleMech, known as “Rocket’s Revenge”. This 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
is a recreation of the original memorial that had been on Theris in front of the Cameron MechWerks main gates. 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
Aft (376 Heat)
Type: Dreadnought (T.H.S. Trinity / D.B.C. Trinity) 3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
Classification: Black-Water Battleship (Individual Limited Production) 3 NAC/20 (45 rounds) 60 (600) 60 (600) 60 (600) 60 (600) Capital AC
Technology Base: Star League 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
Constructed: 2318 4 AC/5 (80 rounds) 2 (20) 2 (20) – – Autocannon
Mass: 960,000 tons Heat Sinks: 2,048 Single 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
Length: 890 meters Structural Integrity: 60 4 AC/2 (90 rounds) 1 (8) 1 (8) – – Autocannon
Sail Diameter: 1,050 meters Battle Value: 134,832
Fuel: 5,000 tons (12,500 points) Additional Notes: From her restoration in the early 30th Century until she was destroyed in 3075, the Trinity had reduced
Tons/Burn-day: 39.52 Armor armor protection along the ship’s starboard bow and stern sections (-6 points to Fore-Right and -4 points to Aft-Right).
Safe Thrust: 3 Fore: 85 This reduced armor protection was due to the patched armor that was never fully restored. In addition, the starboard-aft
Maximum Thrust: 5 R/L Fore-Side: 85 Naval Autocannon/10s were never restored to operational capacity. (Adjusted BattleValue: 130,840)
Sail Integrity: 5 R/L Aft-Side: 80
K-F Drive Integrity: 19 Aft: 80
It is believed the reason for the Phoenix’s rediscovery and eventual release from her tomb of metallic rock was that a The backup plan involved making use of all four tactical nuclear warheads found aboard the Phoenix. The first nuclear
small high-speed object struck the asteroid containing the WarShip. The impact managed to crack the surface around the device was used to blast away the partially-separated smaller asteroid that had once sealed the cavern containing the
edge of the cavity containing the vessel sufficiently for the automated distress signal, still active after the better part of Phoenix, opening the gigantic cavern to space. The Phoenix used her Anti-Missile Systems and defensive PPCs to clear
two centuries, to finally transmit out into open space shortly before the D.I.I.S. Delara jumped to the star system. debris as she travelled through the opening, then rapidly accelerated to clear the debris field.
In 3053, an intense multi-year training program for the Dreadnought BattleCorps was launched. This training program The Dreadnought fleet remained in Clan space far longer than most of the members of Task Forces Serpent and Bulldog.
included a long series of wargames against the Blackwood Templars Mercenaries that began in the Acala system and During the BattleCorps’ extended stay, they managed to make strong connections with the mercantile Clan Diamond
eventually moved to the Waycross system. This included the D.B.C. Trinity, and the D.B.C. Phoenix was unveiled in the Shark—and even the recalcitrant Clan Snow Raven. While Clan Diamond Shark was open to trade without any qualms,
Waycross system when she finally joined in. The Trinity was recalled to the Acala system in January of 3054 due to a pirate and in fact provided the BattleCorps with a variety of advanced weaponry and technology during their time in Clan space,
attack that occurred during the Trinity’s absence, but the Phoenix continued her participation until the conclusion of the the contact with the Snow Ravens proved to be far riskier and potentially more dangerous. Six months after the
training program in 3055. It was expected that the Blackwood Templars, being mercenaries, would quickly spread word BattleCorps had occupied the Pantheress system, Clan Snow Raven learned of the occupation. Roughly three months
of what they had seen and experienced immediately after departing. However, the Templars managed to keep quiet later, the Snow Ravens arrived in force. Star Colonel Ann Lankenau of Clan Snow Raven challenged Colonel Ann Lawrence
about the entire affair until after Dreadnought themselves revealed the existence of the Phoenix three years later. to a Trial of Possession for the system’s assets and population.
Later, after confirming the chess set’s history and authenticity, Star Colonel Ann Lankenau visited Colonel Ann Lawrence In 3072, Colonel Robert Chamberlain, the commander of the D.B.C. Phoenix since 3051, retired from service. Lieutenant
on Pantheress VI. They spoke at length about developments in the Inner Sphere and the Clans over several friendly, albeit Colonel Kai Kelderman was promoted to full Colonel and assumed command over the vessel. Kelderman already had
highly competitive rounds of chess. Before departing, Lankenau left Lawrence with an object of historical value to Clan strong support thanks to his enthusiastic personality, natural charisma, and love for his crew. Support for the new Colonel
Snow Raven as a gift, remarking about how strong the relationship between the Snow Ravens and BattleCorps had grown. was bolstered by his renowned tactical and strategic expertise—and an uncanny ability to calmly keep track of a seemingly
impossible number of different variables during combat, which seemed to give him a near inhuman situational awareness.
On 26 December, 3064, the Dreadnought fleet departed the Pantheress system. In addition to thousands more people
than had been aboard the ships of the fleet when it left the Inner Sphere, the fleet also included two more capital ships, In anticipation of a Word of Blake attack on the Waycross system—likely to be launched from either the Schedar or
both former Smoke Jaguar Odyssey-class JumpShips. One of these JumpShips, the Leaping Leopard, had been present in Caselton star systems—a full year of evacuations of Theris (Waycross II) and CrossWays Station began in mid-3074. In
the Pantheress system with a crippled navigational computer when the BattleCorps first arrived; the other, the Fractured June of 3075, just twenty days after a fleet of JumpShips escorted by the D.B.C. Phoenix departed the Waycross system
Fang, had arrived months later and was quickly captured. to transport refugees to Acala III, the fleet was intercepted in the Goshen system by the Invader-class JumpShip D.I.I.S.
Renegade. The Renegade, which had been in the Waycross system when the Word of Blake arrived, had nearly ruined
Surprisingly, despite a handful of incidents on the way, including one of the Mammoth II DiscoveryCorps JumpShips her K-F Drive to reach the Phoenix to report that the Blakists had attacked in force, with three Pinto-class Corvettes and
suffering damage from a direct high-speed impact with space debris, the fleet made it back to the Inner Sphere with only numerous DropShips. The Blakists had already destroyed two other civilian JumpShips before heading toward Theris.
a handful casualties—only to discover that it had arrived in the midst of the Federated Commonwealth Civil War. Not in
a position to take sides in the war, Dreadnought elected to remain militarily neutral and stay out of the fighting. After the The D.B.C. Phoenix returned to the Waycross system as quickly as possible, and after two jumps she arrived back at the
BattleCorps returned to the Acala system in 3066, Dreadnought focused on integrating into their own facilities on Acala Waycross system’s zenith jump point on June 26th. Upon arriving, the crew of the Phoenix discovered two Blakist Invader-
The Lancaster Coalition was comprised of three very different military units working together—the Blackwood Templars Mercenaries, the Dreadnought BattleCorps 1st Regimental Combat Team,
and the Ronin Free Companies Mercenaries—each of which had associated with it unique machinery not seen elsewhere. Most of the machines featured in the following articles were involved in the
fighting on Ashkum IV in 3077, during Operation LANCASTER. Most of these machines are modified examples of existing designs, while some are limited production variants or refit packages.
311 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
CHAERONEA LIGHT AEROSPACE FIGHTER “SPICY”
Mass: 25 tons consciousness while pushing the fighter to its maximum for too long, his body being so heavily compressed by a mind-
Chassis: Pattern IIA (Reinforced) w/Integrated CASE numbing 10-G of acceleration. According to witnesses, upon returning to the flight deck, the grin could not be removed
Power Plant: Orbital Heavy Industries OHI-275XLC ExtraLight Fusion Engine from his face—and he could not stop laughing, crying tears of joy. After thoroughly enjoying Jones’ reactions, when the
Armor: CH-Custom-Pattern OHI Special Type-C Ferro-Aluminium Armor technicians finally got him to quiet down enough to ask how it was to pilot the fighter, he simply answered, “Spicy.”
Armament & Equipment:
1 Thunderstruck XV Extended Range Particle Projector Cannon Capabilities
1 Dreadnought BC Special Mk-II TDN System
Manufacturer: Clan Smoke Jaguar or Clan Mongoose The Chaeronea Light Aerospace Fighter was originally developed by Clan Mongoose, and then later adopted by Clan
Primary Factory: Unknown Smoke Jaguar. Armed only with a single Extended Range Particle Projector Cannon, the fighter can deliver a solid punch
Modified By: Dreadnought BattleCorps; Acala III to whatever target happens to fall under its crosshairs. This is made even more devastating by how quickly the fighter
Communications System: Interconn-Comm VII can swoop in, strike, and break off before the enemy can retaliate. Speed is life for this craft, as its relatively thin armor—
Targeting & Tracking System: Pinpoint Version-IV-ASF even though it has been lightly improved over the original specifications—is unable to withstand much punishment. The
original Clan-made Series 1B ER PPC served well for years after the fighter’s refit, but the weapon was directly replaced
Overview with one of Dreadnought’s own Clan-tech Thunderstruck XV units shortly before the launch of Operation LANCASTER.
While piloting his signature STU-K5 Stuka Heavy Aerospace Fighter as a freelance mercenary during Operation During fighter-to-fighter engagements and space combat in general, where this fighter spends most of its time, the
BULLDOG, AeroFighter pilot George “Bubba” Jones claimed this Chaeronea as a trophy. Its engine had been shot out of it Dreadnought Target Data Networking (TDN) System is limited to providing improved communications and light electronic
during a brilliantly executed strafing run by George, crippling this and several other fighters before they could get off the warfare support. However, during strafing runs against ground targets, the TDN allows the fighter to be Linked with
ground. This precision surprise attack was the greatest single moment of George’s career as a pilot, and it rendered the nearby friendly ground units, allowing it to utilize friendly targeting telemetry to improve accuracy.
targeted Clan Smoke Jaguar aerospace wing unable to respond, turning a potentially hazardous contract into easy money.
Pilot
The aging Stuka, in the near-constant state of all but falling apart that it was, was sold off years later to Garrett Wilder,
a Kell Hounds pilot, to pay off family debts that George’s career as a mercenary could not hope to cover once his health Captain Stephen “Stumpy” Jones – Chaeronea “Spicy”: Stephen Jones is an average height male with gray-green eyes
began to fail. The Chaeronea remained in storage for nearly a decade, as George had promised his son, Stephen “Stumpy” and ebony skin that is noted for being dark enough that photographing the man is a difficult proposition. His black hair is
Jones, that its engine would be replaced, and that the Clan-made craft would be passed down to him. Though George typically kept short. He was severely wounded in 3067, during the FedCom Civil War, when his military-issued SYD-Z4
was never able to afford the engine replacement, he made sure to keep the fighter otherwise intact for his son to inherit. Seydlitz was shot down. The crash resulted in amputation of both of his legs close to the hip and his left arm at the elbow.
The origin of his nickname is something of a mystery, having gone by “Stumpy” long before the term had literal meaning.
George had been an excellent pilot in his own right, but his son proved to be one of the best in the Inner Sphere.
Unfortunately, Stephen’s career in the Armed Forces of the Federated Commonwealth came to a literal crashing end in The Chaeronea that has become Jones’ signature craft was originally taken by his father as a trophy during the Clan
3067 when his Seydlitz was shot down in the final stages of the FedCom Civil War, leaving Stephen as a triple amputee. Invasion. His father died while Jones was still recovering from the crash that nearly killed him, and he inherited the fighter.
Stephen suddenly found his life in shambles and his dreams all but destroyed. Worse, his father died later that year. He At the time, it seemed to Jones as though the universe was rubbing salt in his wounds. The fighter was without an engine,
inherited the fighter of his dreams, but it had no engine; and given the financial state of the Federated Commonwealth and he was unable to afford quality prosthetics that would allow him to fly even if the fighter had been flightworthy.
following the FedCom Civil War, he could not acquire the quality prosthetics needed to let him fly again.
Jones wanted nothing more than to fly again. It was what he was best at, and what he loved to do more than anything
In May, 3069, Stephen Jones was contacted by Garrett Wilder, the man who purchased the Stuka from his father, after else in life. After close to two years spent in a wheelchair with a miserable archaic prosthetic left arm “claw”, it seemed
Wilder had learned of Stephen’s situation. It turned out that after purchasing the Stuka, Wilder had remained in contact as though the universe finally decided to take pity on him. He was contacted by Garrett Wilder, a pilot in the Dreadnought
with George until the older Jones died. Wilder had since kept tabs on Stephen. In the time since he bought the Stuka, BattleCorps, and a friend of sorts to Jones’ late father. Wilder had learned of Jones’ situation and offered him an
Wilder had left the Kell Hounds and joined the Dreadnought BattleCorps. It only took the one conversation between them opportunity to fly again, this time under the banner of the BattleCorps. Jones graciously accepted almost without thinking.
for Jones to choose to join the BattleCorps as well, bringing the engineless Chaeronea with him.
After adapting to the new prosthetic limbs that had been provided to him by the BattleCorps, he learned to control the
It had been planned to replace the engine with a 225-rated Fusion Engine comparable to the original to restore Jones’ advanced form of direct input/interface control routed through his prosthetic left arm. This new direct input control
Chaeronea to its original specification after he arrived on Acala III in November of 3069. In the time between Jones’ choice allowed him to connect with any fighter adapted to accept the specialized connector as though the fighter were an
to join the BattleCorps and his arrival, however, the situation changed somewhat. The BattleCorps had been handed a extension of his own body. Though it took time to learn and adapt to, his abilities truly began to shine once he mastered
severe defeat by the Word of Blake on Basalt IV in September, and the unit had just begun to rebuild and refit itself. New it. Thanks to the astonishingly improved response times provided by the direct control system—combined with the fact
machines designed especially for the BattleCorps, made to suit a new “Dreadnought Spec” were soon to begin production. that his body was able to sustain far greater G-forces than just about any other pilot in service, as a direct result of his
In the meantime, the order went out to refit many of the machines within the BattleCorps to meet the new standard. In amputated limbs—Jones quickly showed even more skill and capability than he had during his time with the AFFC.
the Chaeronea, this involved the installation of new electronic warfare systems, requiring weight reduction elsewhere.
It was clear to all involved that Jones required a fighter that could match his piloting abilities, and so the technicians
Jones finally received quality prosthetics. He also quickly adapted to the advanced direct input/interface adapter that responsible for refitting the Chaeronea he had brought with him decided to create one. With its absurd speed and agility,
allowed his nerve impulses to be read directly by the fighter in a way that he had never dreamed possible. After seeing “Spicy” suits Jones perfectly, allowing him to outmaneuver any enemy he encounters—sometimes even showboating in
how good a pilot Jones was, his technician team hatched a plan to rebuild the Chaeronea into something truly special. the process. Fortunately, his daredevil antics and showboating settled quickly once he realized that he was negatively
The result was a monster. With a lighter and more powerful OHI-275XLC ExtraLight Fusion Engine adapted from a Crusher influencing those around him, illustrating that he has gained a maturity that he did not have in his time serving the AFFC.
OmniMech as a heart, the fighter’s thrust output was significantly greater than what it had originally been created with.
Coupled with a reinforced spaceframe to handle the added stress, it was much faster and nimbler than ever before. Though he is no doubt the best fighter pilot that Dreadnought has to offer, Captain Stephen Jones holds no illusions
about his own mortality. He knows that every time he and his fighter leave the deck, he could die, but it only presses him
After the latest direct input/interface adapters were equipped into the cockpit specifically for Jones’ use, he took the to strive for greater and greater excellence in the cockpit. It is possible that Jones, especially at the controls of “Spicy”,
craft out for its maiden flight. Accompanied by the best fighter pilots in the Dreadnought BattleCorps’ Aerospace Fighter may in fact be the best aerospace fighter pilot in the Inner Sphere. His technicians ensure that this unique craft, as with
Wing, he was soon outrunning and outmaneuvering every one of them effortlessly. Jones soon felt himself start to lose Jones’ own prosthetics, is maintained in perfect working order.
Equipment Mass
Engine: 275 Fusion XL 8
Safe Thrust: 13
Maximum Thrust: 20
Internal Structure: 13
Heat Sinks (Double): 10 (20) 0
Fuel: 240 3
Cockpit: Standard 3
Armor Factor (Ferro-Aluminium): 67 3.5
Armor
Value
Nose 19
R/L Wing 17
Aft 14
Lieutenant Vera Restel created and written by Paul “The Bro” with edits and
additions (mostly the later history with the BattleCorps) by Devin Ramsey.
Following her singlehanded success, and given the expediency with which
she foiled the assassination attempt, Kaname Fujiwara was offered a position
as a personal bodyguard for Mr. Fitzgerald—an offer she quickly accepted.
As of 3085, only one other assassination attempt has ever been made on Mr.
Fitzgerald. This attempt ended just as abruptly for that assassin as it did for
the Hatchetman’s hijacker. Ms. Fujiwara has been noted to primarily stick to
her BattleCorps-issue Dorgas Medium OmniMech whenever she has needed
to pilot a ‘Mech to fulfill her duties. However, Thunder Chicken has been seen
on several occasions taking to Castle Ramsay’s training grounds.
Equipment Mass
Internal Structure: Endo Steel 2
Engine: 210 Fusion XL 4.5
Walking MP: 6
Running MP: 9
Jumping MP: 0
Heat Sinks (Single): 10 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 98 5.5
Internal Armor
Structure Value
Head 3 9
Center Torso 11 18
Center Torso (rear) 4
R/L Torso 8 12
R/L Torso (rear) 3
R/L Arm 6 12/1
R/L Leg 8 12
Capabilities Expecting to end up in a direct and possibly violent confrontation with his
commander, Masters was shocked to learn that the money he had been
Aces High is powered by a 225-rated VOX Light Fusion Engine, propelling paying to get his ‘Mech back had all been deposited into a private account.
the 45-ton machine up to 86 km/h. The upgraded powerplant was salvaged Specifically, an account that Colonel Blackwood had been maintaining while
from a Cobra BattleMech during a particularly lucrative contract fulfilled by he waited for Masters to realize he had been cheated. Blackwood even went
the Blackwood Templars in the mid-3060s. Although the greater output of so far as to laughingly comment that he was surprised it took Masters so long
the VOX powerplant results in a considerably increased groundspeed over to figure it out. Masters’ rage quickly turned to uncontrollable laughter when
the original 180-rated General Motors Fusion Engine, Aces High retains its he learned that he had never actually lost his Blackjack—Blackwood had
original Whitworth Jetlift jump jets and the 120-meter jump range that they never filed a change to the machine’s official registration—but in fact had
provide. simply been tricked into becoming a well-paid member of the Templars.
In addition to the improved groundspeed, the weapons systems of Aces It was at this point when the Colonel asked what Masters planned to do
High have been modified to better suit Mr. Masters. The twin Autocannon/2s now that he knew the truth of his situation. Masters reflected on the last two
that the Blackjack was originally armed with have been stripped away in years he had spent under Blackwood’s leadership. He came to the realization
favor of a single right-arm Defiance Disintegrator LB 10-X Autocannon. The that before Masters joined the Blackwood Templars Mercenaries, he had
autocannon is fed by two tons of mixed Slug- and Cluster-type ammunition wondered aimlessly, never feeling at home anywhere. However, the Colonel
housed in the arm with the weapon. Aces High retains the standard had given Masters a home where, for the first time in his life, he felt that he
Blackjack’s secondary armament of four Medium Lasers, but the torso- belonged.
mounted pair have been upgraded from the aging Intek units to newer
Extended Range models produced by Defiance Industries. Masters answered the Colonel that evening. He had chosen to remain with
Mass: 45 tons the Blackwood Templars for the foreseeable future. That night, both Masters
Chassis: GM BJ-1 Although it is only cooled by ten double heat sinks, Aces High is extremely and Colonel Blackwood engaged in several games of Poker with a handful of
Power Plant: VOX 225 Light Fusion Engine difficult to overheat. Only when pushed to its absolute limits—repeatedly the unit’s command staff. Masters won nearly every game, fair and square.
Cruising Speed: 54.0 km/h firing all its weapons and making full use of its jump jets—does it slowly build
Maximum Speed: 86.4 km/h up any noteworthy excess heat. Known for being a risk taker, the man known as “Gambler” knows exactly
Jump Jets: Whitworth Jetlift how far past the factory recommendations—and indeed those made by his
Jump Capacity: 120 meters The entire BattleMech has been reskinned with eight tons of Ferro-Fibrous own technicians—he can push his ‘Mech. It is worth noting that Masters has
Armor: Durallex Super Medium Ferro-Fibrous Armor Armor, reducing the overall weight of the exterior armored shell while refused all offers to upgrade his beloved Blackjack with Clan-tech weaponry
Armament & Equipment: simultaneously improving protection over most of the upper body. and equipment. Additionally, he has rebuffed all offers to replace the ancient
1 Defiance Disintegrator LB 10-X Autocannon BattleMech.
2 Defiance Model XII Extended Range Medium Lasers Pilot
2 Intek Medium Lasers Masters continues to insist that his Blackjack can do anything a Clan ‘Mech
Manufacturer: General Motors MechWarrior Nero “Gambler” Masters – BJ-1 Blackjack “Aces High”: Driven can—and that neither he nor his machine need any “overengineered trash”
Primary Factory: Kathil Production Plant; Kathil III by a sort of wanderlust, Masters travelled the Inner Sphere for much of his (Clan technology) to do it.
Modified By: Blackwood Templars Mercenaries; Location Unknown life, his BattleMech providing more safety than would otherwise be available
Communications System: Dalban Micronics to a man of his profession. Early in his life, he discovered a knack for all kinds
Targeting & Tracking System: Dalban AQ of gambling, but especially-so when it came to cards. It was during a high
stakes game of poker in a nondescript bar on a forgettable world when he
Overview first encountered Colonel Tyr Blackwood of the Blackwood Templars.
“Aces High” Is a heavily customized BJ-1 Blackjack Medium BattleMech The Colonel, ever on the lookout for gifted pilots to recruit, made a bet
owned and operated by Nero “Gambler” Masters, a MechWarrior of the involving Masters signing on with the Templars for several years. Masters,
Blackwood Templars Mercenaries. Prior to its current ownership, the history certain of victory with the hand he had—and seeing a massive pot of C-Bills
of this ‘Mech was uneventful. It has been involved in very little combat over in front of him—put his future on the line. Much to Masters’ surprise and
the centuries, and it has been passed down from one generation to the next chagrin, Blackwood produced a hand that trumped his own.
within the Masters family since the time of the Star League.
True to his nickname, Masters challenged the Colonel to another round—
To say that the trend of uninteresting ownership has come to an end double or nothing—putting his family’s ‘Mech on the line. Of course, he lost
would be quite the understatement. again. With Masters’ employment in the Blackwood Templars Mercenaries
Equipment Mass
Internal Structure: Standard 4.5
Engine: 225 Light Fusion 7.5
Walking MP: 5
Running MP: 8
Jumping MP: 4 2
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 143 8
Internal Armor
Structure Value
Head 3 9
Center Torso 14 19
Center Torso (rear) 9
R/L Torso 11 16
R/L Torso (rear) 6
R/L Arm 7 14
R/L Leg 11 17
Through fate and unusual circumstance, Jenna, her Vapor Eagle, and the Lieutenant Jenna and Ainneamhag serve together as Lance Leader of the
whole of the Obsidian Jaguars became part of the Dreadnought BattleCorps Intercept Lance of “Spades” Company—the Command Company of the
in 3060 when the BattleCorps laid claim to the Pantheress system. Jenna and BattleCorps’ 3rd “Wildcards” Battalion. This lance is used as a rapid strike-
the other former Clan warriors who had been absorbed into the BattleCorps and-withdraw unit. Most commonly they are tasked with hitting an enemy’s
formed the BattleCorps’ 3rd ‘Mech Battalion in late 3069, becoming known flank heavily, often taking out a couple ‘Mechs and/or vehicles immediately,
as the “Wildcards”. putting the enemy off balance and opening a hole in their flank. This allows
the rest of the company to strike the enemy during the moment of confusion.
During the intense fighting on Ashkum IV of Operation LANCASTER in
3077, Jenna proved herself time and again, with repeated resupply-and- Variants
redeploy actions. Her devastating and jump-capable BattleMech—if short-
ranged—proved to be one of the most potent weapons in the Wildcards “Ainneamhag” (3050 UAC) – The first refit for Clan Steel Viper MechWarrior
Mass: 55 tons Battalion’s arsenal for fighting in the tight confines of Vyrie City. Although Jenna, created in 3050, featured a Devastator Ultra Autocannon/20 instead
Chassis: Viper MR 6 Endo Steel w/Integrated CASE many of the Wildcards were killed in action during the events of Operation of the LB-X unit that was installed later, fed by two tons of ammunition
Power Plant: New Kent Type 105 330 XL LANCASTER, Jenna and her lancemates stood tall after the dust had settled. housed in the right torso with the weapon. (Battle Value 1,896) Features the
Cruising Speed: 64.8 km/h following Design Quirks: Nimble Jumper.
Maximum Speed: 97.2 km/h Capabilities
Jump Jets: Prizhok WM 5 “Ainneamhag” (3079 TDN Refit) – As part of the refit program launched in
Jump Capacity: 180 meters Known as “Ainneamhag” (“Enya-Vahkhh”—Traditional Scottish Gaelic for 3077 to upgrade the Clan-made ‘Mechs of the BattleCorps’ 3rd “Wildcards”
Armor: VE-Custom-Pattern Dreadnought ExoShield Ferro-Fibrous “Phoenix”) this Goshawk—or Vapor Eagle, as the Clans originally named it— Battalion to meet modern “Dreadnought Spec” standards, Ainneamhag saw
Armament & Equipment: is a unique ‘Mech. Originally built to crush opponents in Clan trial-based moderate refit in 3079 to suit the installation of a Dreadnought Target Data
1 Type J 203mm LB 20-X Autocannon combat, Goshawks gradually found their way into standard combat units. On Networking (TDN) System*. The targeting & tracking system was replaced
4 SEP Class Short Range Missile 4-Racks paper, the Goshawk known as “Ainneamhag” is a brutal, close-combat ‘Mech with a Pinpoint Version-IV unit to suit the head-mounted TDN System and
Manufacturer: Clan Steel Viper that almost seems to take the machine’s original design philosophy and push the cockpit was modified to suit Dreadnought Spec standards—including the
Primary Factory: Novy Minsky Armaments Plant; New Kent II it to the extreme, creating something rather special in the process. Dreadnought Armored Pilot Survival Kit (DAPSK). An additional half-ton of
Modified By: Obsidian Jaguars Garrison; Pantheress VI armor has been applied to the ‘Mech—for a total of ten tons—allowing for
Communications System: Mercer 950 It was armed with a right-torso Ultra-20 Autocannon when it was refitted light reinforcement of the legs and rear center torso.
Targeting & Tracking System: GEG Pattern 500/2b for the first time for Jenna, but the powerful weapon proved to be unreliable.
It was later replaced with a massive LB 20-X Autocannon when the ‘Mech The most significant difference is the removal of the massive autocannon
Overview was refitted a second time on Pantheress VI. Retained from the original refit and its ammunition. Replacing the removed weapon is one of Dreadnought’s
are the quartet of arm-mounted Short Range Missile 4-racks, which are Clan-tech Thunderstruck XV Extended Range Particle Projector Cannons.
In most cases, when a MechWarrior is considered a “Ristar” (the Clan term housed in pairs in the arms. Ammunition placement and routing proved to Using design specifications captured during Operation LANCASTER, the ER
for “Rising Star”) among a Clan’s Touman, they tend to select OmniMechs for be the most difficult issue during the second refit on Pantheress, as the LBX PPC has been enhanced with a reproduction of the Word of Blake’s
their superior ability to be adapted to various combat scenarios, providing Autocannon was bulkier than the Ultra-20 that it replaced. Only a single ton Experimental Clan ER PPC Capacitor*, giving it an impressive punch at range.
themselves with the maximum tactical advantage possible regardless of of ammunition for the LB 20-X Autocannon could be fitted in the right torso The number of double heat sinks was increased to fifteen, with most housed
circumstances. This was not true of MechWarrior Jenna of Clan Steel Viper. with the autocannon itself. The decision was made to house the ‘Mech’s in the powerplant, and one in each side torso. (Battle Value 2,308) Features
The rising Steel Viper warrior purposefully chose a Second-Line BattleMech single ton of Slug-type ammunition in the head, because the hole-punching the following Design Quirks: Dreadnought Spec (Tier-3)*, Nimble Jumper.
as she felt it suited her far better than any of the OmniMechs available. She rounds were would typically be consumed first. After most or all the Slug
selected a Vapor Eagle that had recently been “vacated” through the death rounds had been fired, the Cluster-type rounds housed in the right torso with * See Special Dreadnought / Lancaster Specific Rules (Pages 428-431)
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3
Engine: 330 Fusion XL 12.5
Walking MP: 6
Running MP: 9
Jumping MP: 6 3
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 182 9.5
Internal Armor
Structure Value
Head 3 9
Center Torso 18 30
Center Torso (rear) 5
R/L Torso 13 21
R/L Torso (rear) 5
R/L Arm 9 18
R/L Leg 13 25
This was not the case with the Shadow Hawk known today as “Defender”. When unveiled, the clean integration of all the weapons and equipment—
Severe damage had been dealt to this Shadow Hawk’s powerplant, armor, once best described as a scrap pile of spare parts—was what shocked the
and most of its weaponry. The ‘Mech had clearly not been appropriately command staff most. The Caldwells’ Shadow Hawk looked factory-new, as
secured aboard the Colossus DropShip Wyvern before the misjump and though the cobbled together weapons and parts had been an original factory
subsequent collision occurred. Many of the machines salvaged nearly intact build. Given the rough patch that Dreadnought’s military forces were going
from the Phoenix’s DropShips were later used to significantly reinforce and through, the completion of the machine was cause for a small celebration for
expand the Dreadnought DefenseCorps on Acala III, and more still were both the DefenseCorps and BattleCorps. The morale boost was desperately
pressed into service when the unit had grown enough to split and form the needed, and the BattleMech that the Caldwell brothers and their friends had
Dreadnought BattleCorps. However, this Shadow Hawk was set aside, surely come to call “Defender” became something of a mascot for the 2nd Battalion
destined to be scrapped. The broken ‘Mech was kept in storage for more of Acala III’s Dreadnought DefenseCorps 1st Homeworld Regiment—where
than an additional century, eventually becoming all but forgotten. Jason Caldwell and his new machine were soon assigned.
It was not until Samuel Caldwell—a member of one of the Dreadnought Defender remains in the service of the DefenseCorps on Acala III as of
DefenseCorps’ technician teams based on Acala III—stumbled across the 3085, with now-Lieutenant Jason Caldwell at the helm. A proposal has been
broken and forgotten Shadow Hawk that the ‘Mech was given a new chance put forth to refit Defender in 3086, bringing the ‘Mech up to “Dreadnought
at “life”. One of the very few positives from the Dreadnought BattleCorps’ Spec” standards through integrating newer technology. Though the proposal
unfortunate encounter with the Word of Blake’s 55th Shadow Division on is still on the drawing board, it appears it will be approved. This is because
Basalt IV in 3069 was a limited amount of salvage. This salvage happened to the Dreadnought DefenseCorps 1st Homeworld Regiment is in the process
include a wrecked SHD-11CS Shadow Hawk. The Blakist SHD-11CS had been of gradually upgrading all their equipment to meet the same Dreadnought
gunned down just as it managed to board one of the BattleCorps’ DropShips, Spec standards first exclusively associated with the Dreadnought BattleCorps
just seconds before the BattleCorps had lifted off Basalt IV to escape the 1st Regimental Combat Team. It is unclear, however, whether Lieutenant
Mass: 55 tons Word of Blake. With no time to throw it overboard, the technician crews had Caldwell and Defender will remain with the DefenseCorps or instead transfer
Chassis: SLDF Royal Shadow Hawk Endo Steel w/CASE rapidly secured the fallen ‘Mech in place to keep it from tumbling about the to the BattleCorps once the refit is completed.
Power Plant: Defiance 275 Light Fusion Engine DropShip’s interior. Much of the SHD-11CS was smashed beyond repair, but
Cruising Speed: 54.0 km/h its Light Fusion Engine was intact. As it was not compatible with any of the Capabilities
Maximum Speed: 86.4 km/h BattleCorps’ newly-built machines, it was likely to eventually be scrapped.
Jump Jets: None On paper, Defender is an inferior Shadow Hawk in many ways. The ‘Mech’s
Jump Capacity: 0 meters With Samuel Caldwell’s brother Jason being a recent graduate of the Acala mobility is significantly reduced due to its lack of jump jets, and with only
Armor: Custom-Fitted Valiant Ringmail Light Ferro-Fibrous III Military Academy’s MechWarrior program, and having no ‘Mech to call his ammunition-based weaponry, it has limited battlefield staying power. For all
Armament & Equipment: own, Samuel did the easy math and saw the potential for something special. its flaws, Defender is still a remarkable achievement by a group of friends
1 Oriente Model O LB 10-X Autocannon Together, the Caldwells proposed to rebuild the ancient SHD-2Hb Shadow working with what amounted to leftover scraps and salvaged parts. With its
4 Holly Short Range Missile 4-Racks Hawk in storage. Unfortunately for the Caldwells’ proposed pet project of 275-rated Defiance Light Fusion Engine pulled from a salvaged Word of Blake
Manufacturer: Majesty Metals and Manufacturing rebuilding the ancient Star League ‘Mech, the budget for the DefenseCorps SHD-11CS Shadow Hawk, Defender can reach a maximum groundspeed of 86
Primary Factory: MMM Complex; Dunianshire VI had taken a significant hit as a direct result of the severe losses suffered by km/h, which is respectable enough for a 55-ton machine—regardless of age.
Modified By: Dreadnought DefenseCorps; Acala III the BattleCorps on Basalt IV. Despite the spending cuts, the brothers were
Communications System: O/P 300 COMMSET given the green light to proceed with their idea. However, they were told Armed primarily with its original Star-League-era LB 10-X Autocannon,
Targeting & Tracking System: O/P 2000A that they would be getting virtually no outside assistance. They were on their backed by a quartet of Short Range Missile 4-racks, Defender can deal
own. With little more than the broken Star-League-era SHD-2Hb Shadow reasonable damage at medium range, but has a devastating impact on
Overview Hawk, a pile of Light Ferro-Fibrous Armor, the Light Fusion Engine, a handful targets at closer ranges. Two tons of ammunition is housed in the left torso
of spare Short Range Missile 4-racks found lying around, and permission from feed the autocannon, with a half-and-half mix of Slug- and Cluster-type
In 2946, the WarShip S.L.S. Phoenix (later rechristened the D.B.C. Phoenix) their superiors to somehow put it all together and make something that rounds. Two single-ton ammunition bins feed the SRMs. The first bin of CASE-
was rediscovered after it had been missing for more than two centuries, lost hopefully worked—and the help of a few friends—the Caldwell brothers got equipped missile ammunition is housed in the right torso and is responsible
Equipment Mass
Internal Structure: Endo Steel 3
Engine: 275 Light Fusion 12
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Light Fe-Fibrous): 169 10
Internal Armor
Structure Value
Head 3 9
Center Torso 18 28
Center Torso (rear) 8
R/L Torso 13 20
R/L Torso (rear) 6
R/L Arm 9 16
R/L Leg 13 20
Equipment Mass
Internal Structure: Standard w/C-CASE 6
Engine: 300 Fusion XL 9.5
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks (Double): 12 (24) 2
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 163 8.5
Internal Armor
Structure Value
Head 3 9
Center Torso 20 23
Center Torso (rear) 7
R/L Torso 14 16
R/L Torso (rear) 7
R/L Arm 10 16
R/L Leg 14 23
Space Allocation
Location Fixed Components Spaces Remaining
Head 1 Ferro-Fibrous 0
Center Torso None 2
Right Torso 2 XL Engine, 2 Ferro-Fibrous 8
Left Torso 2 XL Engine, 2 Ferro-Fibrous 8
Right Arm 1 Ferro-Fibrous 9
Left Arm 1 Ferro-Fibrous 9
Right Leg None 2
Left Leg None 2
Space Allocation
Location Fixed Components Spaces Remaining
Head 1 Ferro-Fibrous 0
Center Torso 1 Endo Steel, 1 Ferro-Fibrous 0
Right Torso 2 XL Engine, 1 Ferro-Fibrous 9
Left Torso 2 XL Engine, 1 Endo Steel, 1 Ferro-Fibrous 8
Right Arm 2 Ferro-Fibrous 8
Left Arm 2 Ferro-Fibrous 8
Right Leg 2 Endo Steel 0
Left Leg 2 Endo Steel 0
The RGH-7RF has nearly identical armament to the RGH-1RF, with the
exception that it drops the Martell ER Large Lasers and directly replaces them
with CeresArms Striker Light Particle Projector Cannons. The finalized result
is nearly a half-million C-Bills less-expensive to build, as well as considerably
improved heat efficiency and ease of maintenance. (Battle Value: 1,340)
Features the following Design Quirks: Easy to Maintain, Easy to Pilot, Stable.
Equipment Mass
Internal Structure: Endo Steel 3.5
Engine: 260 Fusion 13.5
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 211 12
Internal Armor
Structure Value
Head 3 9
Center Torso 21 32
Center Torso (rear) 10
R/L Torso 15 22
R/L Torso (rear) 8
R/L Arm 10 20
R/L Leg 15 30
Even today, so much regarding Jezebel Adams and her Archer remains Ms. Adams’ combat career was one that she insists on describing as being
unknown, redacted, and/or classified. However, it is clear that Tempest Fury “of unremarkable note” prior to her service with the Ronin Free Companies
Mass: 70 tons has received considerable modification since joining the ranks of the Ronin Mercenaries. She still refuses to answer questions regarding her unexplained
Chassis: Earthwerks Archer II Endo Steel w/CASE Free Companies Mercenaries—where it continues to serve as of 3085. and sudden disappearance in 3068, or her equally unexplained and sudden
Power Plant: VOX 280 Fusion Engine reappearance three years later in the Ronin’s employ. The significant gap in
Cruising Speed: 43.2 km/h Capabilities her history has proven perplexing for many intelligence agencies. However,
Maximum Speed: 64.8 km/h some unsubstantiated reports indicate that her disappearance might have
Jump Jets: None Although it began life as a standard ARC-4M Archer Heavy BattleMech, been part of some form of trade—possibly as part of a contractual fulfillment
Jump Capacity: 0 meters “Tempest Fury” is an atypical Archer in that its specialization is in close- for the Ronin. Further inquiry has netted no results, and Ms. Adams has been
Armor: Light Ferro-Fibrous Armor quarters combat, as opposed to the more typical long-range fire support. noted to become extremely tight-lipped whenever the subject is raised.
Armament & Equipment: This machine also demands of its pilot particularly above-average gunnery
2 Shigunga Medium Range Missile 30-Racks skill, as the Medium Range Missile systems are notorious for being difficult In the time that Ms. Adams has spent with the Ronin Free Companies, her
2 Magna Mk II Medium Lasers to use accurately. Archer has been repaired and refitted on several occasions, and it has
2 Magna Mk IV Extended Range Small Lasers gradually evolved into its current state. In combat, Ms. Adams is perhaps
Manufacturer: Earthwerks Incorporated Gone are the Archer’s original twin twenty-tube Long Range Missile best known for her tendency to burst through buildings to catch an opponent
Primary Factory: Earthwerks-FWL, Inc.; Calloway VI systems, and in their place are a pair of Shigunga Medium Range Missile 30- in a surprise ambush, crippling her target in a spectacular barrage of missiles.
Modified By: Ronin Free Companies Mercenaries; Location Unknown racks. Each MRM-30 is fed by an independent two-ton supply of ammunition, This combination of pilot and machine often leave little behind to salvage, as
Communications System: Neil 9000 housed in the same location as the launcher it feeds. Although this means the recipient of Tempest Fury’s ire is often left in utter ruin after having salvo
Targeting & Tracking System: RCA Instatrak Mark XII that Tempest Fury only carries enough ammunition for sixteen full salvoes, after salvo of missiles poured into it.
the sheer volume of missiles fired in each salvo is typically enough to wreak
Overview havoc on any target. Meanwhile, Cellular Ammunition Storage Equipment is
installed in both side torsos to ensure that an internal ammunition explosion
The exceedingly few existing historical records regarding this specific will not incapacitate the ‘Mech.
Archer Heavy BattleMech indicate that it was acquired in mid-3059 by House
Liao’s Capellan Confederation Armed Forces—though specifics of its actual In terms of secondary weapons, the Magna Mk II Medium Lasers normally
service are classified, as are the those of the machine’s acquisition. housed in the Archer’s arms have been replaced with less-powerful Magna
Mk IV Extended Range Small Lasers. Meanwhile, the normally rear-firing twin
Originally built by Earthwerks Incorporated in 3053, by Earthwerks’ Free Medium Lasers in the center torso have been relocated to be forward-facing
Worlds League factory on Calloway VI, it is unclear if this ARC-4M Archer was and installed directly under the relatively low-slung cockpit. A Guardian
either purchased by an independent unit, or if it served in House Marik’s own Electronic Countermeasures Suite is installed to give Tempest Fury a measure
Equipment Mass
Internal Structure: Endo Steel 3.5
Engine: 280 Fusion 16
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks (Double): 12 (24) 2
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Light Fe-Fibrous): 217 13
Internal Armor
Structure Value
Head 3 9
Center Torso 22 34
Center Torso (rear) 10
R/L Torso 15 24
R/L Torso (rear) 6
R/L Arm 11 22
R/L Leg 15 30
Capabilities By the time that Operation LANCASTER was launched, the Blackwood
Templars Mercenaries’ Charlie Lance was already known as “Heartbreaker
This WHM-6R Warhammer Heavy BattleMech’s original StarCorp 100- Lance”, due to the iconic ‘Mech at its head. During the final critical battle of
Series Standard Chassis is largely unmodified, though Cellular Ammunition LANCASTER, both of the other Warhammers in Heartbreaker Lance suffered
Storage Equipment has been installed wherever ammunition is housed. severe damage—and one of them, a -6K variant, was lost entirely when its
Heartbreaker’s armored shell was rebuilt using the same Light Ferro-Fibrous powerplant suffered a rare containment failure, vaporizing the upper body
Armor used later in the -8K Warhammer, albeit with some visible differences of the ‘Mech and instantly killing the pilot. Heartbreaker itself and the other
thanks to the mechanical modifications this ‘Mech has received. In addition two BattleMechs of the five-’Mech lance (the typical lance arrangement of
to its heavily reinforced armor, Heartbreaker features a Guardian Electronic the Blackwood Templars) weathered the events relatively intact, albeit all
Countermeasures Suite installed in the right torso. requiring significant repairs after the fighting was over. Heartbreaker Lance’s
lost WHM-6K Warhammer and its MechWarrior have since been replaced
The Warhammer’s original VOX 280-rated Fusion Engine was damaged with another modified WHM-6D and a younger pilot that recently joined the
beyond repair during Operation BULLDOG. It has since been replaced with a Blackwood Templars. As of 3085, the rest of Heartbreaker Lance remains as
Mass: 70 tons comparably-rated, Clan-made ExtraLight Fusion Engine salvaged from a it was in 3077, during Operation LANCASTER.
Chassis: StarCorp 100 w/CASE wrecked Jagatai Heavy OmniFighter. This replacement powerplant—which
Power Plant: Clan 280 ExtraLight Fusion Engine turned out to be a surprisingly straightforward swap—marked the beginning Pilot
Cruising Speed: 43.2 km/h of a heavy refit of the entire BattleMech that was carried out during the
Maximum Speed: 64.8 km/h Blackwood Templars’ time spent in Clan space following the conclusion of Lieutenant Candace Killian – WHM-6R Warhammer “Heartbreaker”: Killian
Jump Jets: None BULLDOG. Despite its new Clan-made powerplant, Heartbreaker continues is hardly a model soldier for any potential pilot to look up to. This woman is
Jump Capacity: 0 meters to use the more easily-sourced Inner-Sphere-made double heat sinks that often referred to as the Templars’ “Albino Bombshell”, and the term has just
Armor: Valiant Ringmail Light Ferro-Fibrous Armor the ‘Mech had already been converted to use prior to the engine upgrade. as much to do with her exquisitely attractive physical appearance as it does
Armament & Equipment: her attitude. The Lieutenant is remarkably belligerent and aggressive, even
2 Clan Extended Range Large Lasers Heartbreaker can easily be categorized as a classic “Jack of all trades, Ace for a member of the Blackwood Templars. She can usually be found in the
1 Clan LB 10-X Autocannon of none”. Despite this, the ‘Mech can be summarized by a conversation that middle of a brawl as often on the battlefield as off. Failing that, she is often
2 Clan Extended Range Medium Lasers once took place between a curious employer and members of the Blackwood found cooling her heels in a local holding cell for “disorderly conduct”. None
1 Clan Streak Short Range Missile 6-Rack Templars Mercenaries. After spotting the unique Warhammer, the employer of these character traits take away from either her skill as a MechWarrior or
2 Defiance Model XII ER Medium Lasers asked what all was installed in it. Before anyone else could answer, a passing her willingness to put herself on the line for her fellow Templars, however.
4 Sperry Browning Machine Guns MechTech blurted out “Firepower. All of it.” and just kept walking.
1 Guardian Electronic Countermeasures Suite Lieutenant Killian is one of several among the Blackwood Templars who
Manufacturer: Olivetti Weaponry The heavy weapons array installed in Heartbreaker is impressive and takes grew up as orphans. Although she and a handful of the other Templars are
Primary Factory: Olivetti Weaponry Facility; Sudeten IV full advantage of the freed weight capacity of the chassis thanks to its newer clearly aware of her planet of origin, it is officially recorded as unknown.
Modified By: Blackwood Templars Mercenaries; Huntress II lightweight powerplant. Heartbreaker’s most prominent weapon system is Presumably, this intentional oversight is to distance herself from her original
Communications System: O/P 3000 COMSET its high-mounted left-torso Clan-tech LB 10-X Autocannon, which is fed by homeworld as much as possible. She earned her place among the elite “Red
Targeting & Tracking System: O/P 1500 ARB two tons of mixed Cluster- and Slug-type ammunition. Replacing the iconic Arms” of the Blackwood Templars Mercenaries faster than any other
twin Particle Projector Cannons normally installed in the arms is a pair of Clan member in the history of the unit. In just her second deployment, Killian
Overview Extended Range Large Lasers. The Clan-made lasers provide Heartbreaker managed to singlehandedly down four hostile ‘Mechs to protect an injured
with comparable punch to the original PPCs, but often surprise opponents Templars MechWarrior who had been forced to eject.
Heartbreaker was first deployed in combat by the Blackwood Templars with their significantly increased range.
Mercenaries at the beginning of Operation BULLDOG in 3059. Heartbreaker’s A curious note about Killian is that she can often be heard singing softly
pilot, Candace Killian, was a relatively recent addition to the ranks of the As it closes in on its opponent, Heartbreaker’s lethality only increases. before combat. In fact, the Lieutenant is said to be quite a talented singer. In
Blackwood Templars’ combat units at the time. Although Killian accounted Twin Clan-tech Extended Range Medium Lasers are installed in the center the moments leading up to a hot-drop into a combat zone for one of her first
for herself well, her ‘Mech was nearly destroyed during BULLDOG. However, torso as an introduction to its short-to-mid-range firepower. A Short Range combat missions, she had believed that she was simply singing to herself in
Heartbreaker was soon rebuilt using many salvaged and restored Clan-made Missile 6-rack is mounted high up on the right torso, as is typical of WHM-6R her cockpit. She eventually realized that the Templars’ intra-unit comms had
Equipment Mass
Internal Structure: Standard 7
Engine: 280 Fusion XL (Cl) 8
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks (Double): 13 (26) 3
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Light Fe-Fibrous): 217 13
Internal Armor
Structure Value
Head 3 9
Center Torso 22 34
Center Torso (rear) 10
R/L Torso 15 22
R/L Torso (rear) 8
R/L Arm 11 22
R/L Leg 15 30
Equipment Mass
Internal Structure: Standard (IS) 7.5
Engine: 300 Fusion (IS) 19
Walking MP: 4 (5)
Running MP: 6 (8)
Jumping MP: 0
Heat Sinks (Double): 18 (36) 8
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 220 11.5
Internal Armor
Structure Value
Head 3 9
Center Torso 23 33
Center Torso (rear) 10
R/L Torso 16 24
R/L Torso (rear) 8
R/L Arm 12 24
R/L Leg 16 28
Emilia Kharlynn, Second Lieutenant Mallus Kharlynn and custom Black Knight
Heavy BattleMech “Carver” originally created by Michael Szita.
Equipment Mass
Internal Structure: Standard 7.5
Engine: 300 Fusion 19
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 231 13
Internal Armor
Structure Value
Head 3 9
Center Torso 23 34
Center Torso (rear) 12
R/L Torso 16 22
R/L Torso (rear) 10
R/L Arm 12 24
R/L Leg 16 32
Capabilities With much of the Ronin in disarray, their united leader dead, and multiple
Free Companies destroyed or crippled, the remaining Free Companies were
A powerhouse of a heavy BattleMech, the Lao Hu known as “Rusty” is a on the verge of fracturing altogether. Over the next five years, Donaldarus
modified version of the LHU-4E variant. Armed primarily with a potent one- Meridius proved that he could not only unite the Ronin Free Companies once
Mass: 75 tons two punch of a left-arm Magna Supernova Heavy Particle Projector Cannon more, but even help to restore some of what had been lost. With a small
Chassis: Chariot Type II Endo S w/CASE and a right-arm Shengli LB 20-X Autocannon, Rusty can deliver crippling fortune to his name and many contacts to call upon, he worked to rebuild an
Power Plant: GM 375 Fusion XL Engine damage to an opponent in short order. The autocannon is fed by three tons entire Free Company using whatever and whoever he could get his hands on.
Cruising Speed: 54.0 km/h of ammunition—most often two tons of Slug-type rounds backed by a single
Maximum Speed: 86.4 km/h ton of Cluster rounds—all housed in the right torso and equipped with The Ronin’s contracts in House Liao’s Capellan Confederation in 3055
Jump Jets: None Cellular Ammunition Storage Equipment. In addition to its massive primary helped to further Meridius’ cause, allowing him to gain even stronger footing
Jump Capacity: 0 meters weapons systems, Rusty is armed with a Diverse Optics Type 2 Medium Laser as the Ronin continued to build their forces under him. From 3056-onward,
Armor: Star Shell Standard and an Olympus Flamer, giving the ‘Mech a reasonable direct-fire backup however, records on Free Colonel Meridius become sketchy at best, as much
Armament & Equipment: weapon and a potent antipersonnel defense weapon. With thirteen double of the Ronin Free Companies’ actions begin to become shrouded in secrecy.
1 Magna Supernova Heavy Particle Projector Cannon heat sinks, Rusty is surprisingly heat efficient, capable of running quite cool It is believed that between 3056 and 3059, the Ronin began to participate in
1 Shengli LB 20-X Autocannon even while operating at maximum speed and firing all its ranged weapons shadow engagements against the Word of Blake in Capellan territory, as well
1 Diverse Optics Type 2 Medium Laser constantly—only building minimal levels of excess heat that cannot be sinked as other operations in the Aurigan Coalition and the Magistracy of Canopus.
1 Olympus Flamer when firing its Flamer in addition to all its other weapons. It is not entirely clear which of the Free Companies were involved in each of
1 Guardian Electronic Countermeasures Suite these operations, and as a result, Meridius’ actual location during this time
Manufacturer: Shengli Arms Due to compatibility issues with the LB 20-X Autocannon, the installation is unknown. Even less information is available regarding Meridius’ activities
Primary Factory: Shengli Arms Facility; Victoria (Victoria II) of the massive autocannon required the removal and replacement of the during the Federated Commonwealth Civil War in the 3060s, leaving many
Modified By: Ronin Free Companies Mercenaries; Location Unknown LHU-4E’s normal 13.5 tons of Stealth Armor. However, this was a trade-off questions as to where he was and what he was doing during that timeframe.
Communications System: Dian-bao Comms, Standard that Free Colonel Donaldarus Meridius was willing to make so long as the
Targeting & Tracking System: O/P 911 TTS Star Shell Standard Armor provided equal protection to the original Stealth Meridius all but spontaneously reappeared in late 3067, when the Ronin
Armor—which it does. Additionally, during the removal of the Stealth Armor, Free Companies joined in the Capellan Confederation’s open campaign
Overview the construction of the left arm returned to a more traditional Lao Hu against the Word of Blake. While some of the Free Companies were deployed
configuration through the installation of a lower arm actuator. Although the into Aurigan and Canopian territory, Meridius’ own “Oni Slayers” and other
During Operation LANCASTER, Free Colonel Donaldarus Meridius piloted Stealth Armor was removed, the Guardian Electronic Countermeasures Suite Free Companies operated very actively in Capellan territory.
a refurbished prototype Sumaire Assault OmniMech, which the Dreadnought has been retained, due in no small part to Meridius’ experience with the
BattleCorps had provided for his use during the operation. The Sumaire had Dreadnought BattleCorps 1st RCT during Operation LANCASTER, where the Although his reasons for it are known only to him and those closest to him,
been provided as the Free Colonel’s personal Grasshopper was felt to be BattleCorps’ widespread use of powerful ECM effectively disabled the Word it is well-documented that Free Colonel Donaldarus Meridius was a staunch
inadequate for the commander of the Ronin Free Companies Mercenaries of Blake’s Improved C3 Networks. This tactical advantage proved invaluable anti-Blakist, to the point where he was said to take on lower-paying contracts
during their critical defensive role during Operation LANCASTER. Fortunately during the operation and helped to save numerous lives among the Lancaster just because the expected opposition was the Word of Blake. Because of this,
for Free Colonel Meridius, the foresight proved to be correct. Unfortunately, Coalition. Though the Ronin Free Companies had never been known to make it is suggested that Meridius and the Ronin became something of a favorite
the Sumaire itself was damaged beyond repair in combat, and its final close- significant use of advanced electronics prior to LANCASTER, the experience of Chancellor Sun-Tzu Liao, and as a result the Ronin were involved in the
quarters encounter with a hatchet-wielding assault-class Seraph Celestial was clearly one that Meridius has taken to heart and learned from. Capellan Confederation’s campaign against the Word of Blake right through
OmniMech left the Free Colonel himself badly injured. Meridius suffered two to the end of the Jihad—with one notable exception: Operation LANCASTER.
broken ribs, two bruised ribs, a broken arm, and a bruised kidney, all on his Other than the aforementioned modifications, Rusty’s internal systems
left side. However, he had survived, no thanks to a failed pilot seat harness are factory-standard LHU-4E, all of which are some of the most advanced There was clearly a strong business relationship between Dreadnought
in the Sumaire—which was apparently supposed to have been replaced. systems produced in the Capellan Confederation. Powered by a 375-rated Interstellar Industries and the Ronin Free Companies, and the Ronin had past
General Motors ExtraLight Fusion Engine, Rusty is capable of a top speed combat history with the Dreadnought BattleCorps during the 4th Succession
Leaving his unfortunate experience with the Sumaire behind, Meridius exceeding 85 km/h, giving the ‘Mech respectable mobility. To help counter War—before Donaldarus Meridius himself could speak. However, it is still
had been prepared to return to his Grasshopper once his injuries had healed, the heavy weight of the massive powerplant, the stability of the ‘Mech unclear why he chose to immediately shift two entire Free Companies—his
Equipment Mass
Internal Structure: Endo Steel 4
Engine: 375 Fusion XL 19.5
Walking MP: 5
Running MP: 8
Jumping MP: 0
Heat Sinks (Double): 13 (26) 3
Gyro: ExtraLight 2
Cockpit: Small 2
Armor Factor (Standard): 216 13.5
Internal Armor
Structure Value
Head 3 9
Center Torso 23 33
Center Torso (rear) 10
R/L Torso 16 24
R/L Torso (rear) 7
R/L Arm 12 23
R/L Leg 16 28
It should be noted that, in early 3085, after quietly taking personal leave
off-world, Fawkes returned to his new home on Acala III. His companions
noted that he showed signs of severe disappointment. He has never once
explained what happened during his time away. However, according to a
recent report, Fawkes and Ms. Grable have since altered the livery of Fawkes’
Marauder to a more standardized Dreadnought BattleCorps livery.
Captain Michael “Fox” Fawkes and
custom Marauder Heavy BattleMech
Type: Marauder (MAD-3R(BC)) “Bunty Hounder” “Bunty Hounder” originally created
Classification: Heavy BattleMech (Uniquely Modified/Customized) by Michael Berube.
Technology Base: Mixed Clan/Dreadnought
Tonnage: 75
Battle Value: 2,400
Notes: Features the following Design Quirks: Command ‘Mech,
Dreadnought Spec (Tier-2)*, Hyper-Extending Actuators,
Narrow/Low Profile. Arm Actuators: Lower (Right & Left).
Equipment Mass
Internal Structure: Standard (IS) 7.5
Engine: 300 Fusion (IS) 19
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks (Double (IS)): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 220 11.5
Internal Armor
Structure Value
Head 3 9
Center Torso 23 35
Center Torso (rear) 10
R/L Torso 16 24
R/L Torso (rear) 8
R/L Arm 12 24
R/L Leg 16 27
Custom Heavy LRM Carrier (SRM Refit) based on an idea by Zach Schaffer.
When first encountered on Ashkum IV in 3077, this Legacy had already The original Aldis Plate Standard Armor, of which very little remained, has
received significant upgrades over the standard LGC-03 chassis variant that been replaced entirely with a custom-pattern protective shell composed of
it was originally constructed as. This was rather unusual, as the rest of the Dreadnought’s own Titan-Plate Standard Armor. Though Isorla’s tough hide
BattleMechs fielded by the Word of Blake’s elite Manei Domini 55th Shadow meets the same durability specifications as the original armored shell on
Division were standard variants that had already been documented, unlike paper, the exterior does feature mild aesthetic differences that set it apart
the all-new “Divinus” configuration series of the 55th’s Celestial OmniMechs. from the standard Legacy BattleMech. However, although the chassis itself
This Legacy featured the same augmented Clan-tech ER PPCs that most of is identical and the exterior aesthetics of the machine are broadly similar to
the 55th’s Celestial OmniMechs were armed with—however, unlike any of its appearance when it was in service of the Word of Blake, nearly all of the
those machines, this Legacy BattleMech featured not one, but two of them. BattleMech’s electronics, armament, and other internal components have
This meant that its cooling system was taxed to keep up with the heat output been replaced or upgraded.
of its powerful weaponry, but it was a devastating opponent in combat.
The original 320-rated Light Fusion Engine was destroyed during the
The thirty-six BattleMechs of the 55th Shadow Division’s Fourth ‘Mech fighting on Ashkum IV. As neither Dreadnought Interstellar Industries nor its
Level III served as the 55th’s rear guard during the fighting in Vyrie City on partner corporation Orbital Heavy Industries produce Light Fusion Engines,
Ashkum IV in January of 3077, during the climactic final battle of Operation the wrecked powerplant was replaced with an Orbital Heavy Industries OHI-
LANCASTER. Because of their assignment as rear guard, the 55th’s Fourth 320XLC ExtraLight Fusion Engine. The replacement powerplant was originally
Level III found themselves facing off against the Dreadnought BattleCorps’ designed and built for use in a DII-EPR-BC1 Emancipator Assault BattleMech,
3rd “Wildcards” Battalion. The clash that followed was spectacular. The but because production of the BC-series Emancipator had been stalled for
Wildcards Battalion, which was comprised entirely of former Clan Warriors— years, the first series of powerplants built for them had been sitting idle,
many of whom were piloting Clan-made ‘Mechs of various types—had made gathering dust. Along with the powerplant, the entire cooling system was
it appear to the Blakists as though the Clans themselves had somehow joined pulled and upgraded. The resulting enhanced cooling system utilizes a total
the battle. Despite the confusion of the moment, the Fourth Level III lashed of eighteen of Dreadnought’s own Clan-tech double heat sinks. Two of the
Mass: 80 tons out at the Wildcards with an almost feral fury. This, of course, was entirely three original CurtissJet series jump jets were critically damaged, so all three
Chassis: Skobel Template 8 Endo Steel w/CASE-II calculated, as the BattleCorps was aware of the Word of Blake’s contempt were directly replaced with Dreadnought’s own Kangaroo Model IX units.
Power Plant: Orbital heavy Industries OHI-320XLC ExtraLight Fusion Engine for all things Clan—their technology aside.
Cruising Speed: 43.2 km/h The cockpit had to be completely rebuilt, as it was left an all but mangled
Maximum Speed: 64.8 km/h Much of the fighting was a confused mess, as urban combat often tends wreck by the Elementals who were tasked with executing the pilot when the
Jump Jets: Kangaroo Model IX to become. However, battle records show that the Level II of six ‘Mechs led order came down from Colonel Ann Lawrence to kill every member of the
Jump Capacity: 90 meters by this very Legacy engaged the Wildcards’ “Spades” Company directly, just 55th Shadow Division. This still-controversial order was issued because the
Armor: LGC-Custom-Pattern Dreadnought Titan-Plate Standard Armor as the Lancaster Coalition’s pincer began to close around the 55th Shadow Manei Domini quickly proved themselves far too dangerous to be captured
Armament & Equipment: Division. MechWarrior Benjamin of the Spades’ Support Lance was noted to alive or allowed to escape into the local population. The cockpit was rebuilt,
2 Thunderstruck XV Extended Range Particle Projector Cannons be the individual responsible for downing this particular machine. is heavily upgraded to meet Dreadnought Spec standards, including DAPSK,
w/Experimental Clan ER PPC Capacitors or DAPS Kit (Dreadnought Armored Pilot Survival Kit) compatibility.
1 PosiLock-IV Streak Short Range Missile 4-Rack Benjamin’s own Hammerhands IIC was destroyed before the end of the
4 Laserwerks Strobe Type 7 Medium Pulse Lasers fighting, and Benjamin himself was severely injured, resulting in nearly a year Nearly the entire electronics package—including the targeting & tracking
1 Dreadnought BC Special Mk-II TDN (Target Data Network) System spent recovering. He returned to active duty in mid-3078. It was then that and communications systems—has been replaced with Dreadnought’s own
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite Benjamin—who was now a Second Lieutenant of the BattleCorps—took equipment. The Word of Blake’s favored Improved C3 Computer is long
Manufacturer: Skobel MechWorks possession of his new machine: the Legacy Assault BattleMech that he has gone, and one of Dreadnought’s own Target Data Networking (TDN) Systems
Primary Factory: Skobel Primary Manufacturing Facility; Terra (Sol III) since simply referred to as “Isorla” (the Clan term for the spoils of war). is installed in the Legacy’s head, allowing it to network seamlessly with other
Modified By: Dreadnought BattleCorps; Acala III Linked BattleCorps machines in the field. Additionally, an Angel Electronic
Communications System: Intercon-Comm VII w/TDN System Capabilities Countermeasures Suite is installed in the center torso, further enhancing
Targeting & Tracking System: Pinpoint Version-IV Isorla’s defenses and providing it with powerful electronic warfare capacity.
Already a fearsome machine in its modified state prior to being downed
Overview and subsequently salvaged, this Legacy Assault BattleMech has since been The clearly used and abused Clan-tech Extended Range Particle Projector
further upgraded to bring it into line with the “Dreadnought Spec” standards. Cannons and Experimental Clan ER PPC Capacitors that had been installed in
Prior to being salvaged on Ashkum IV after the fighting that took place These upgrades were made as a part of the refit program launched later in the right and left torsos of this ‘Mech were removed altogether. These main
during Operation LANCASTER in early 3077, the history of this specific Legacy 3077 that focused on bringing the 3rd “Wildcards” Battalion’s ‘Mechs up to guns were directly replaced with Dreadnought’s own Thunderstruck XV
is a near-total unknown. What little information that has been gathered the same standard as the rest of the Dreadnought BattleCorps’ machinery. models, augmented with in-house-produced replicas of the Word of Blake’s
indicates that this machine was originally an early example of the Legacy The “Dreadnought Spec” refit of this Legacy, now known simply—and to X/C-ERPPC Capacitors. The battlefield performance of these weapons is
Assault BattleMech produced by Skobel MechWorks in late 3070 on Terra. some degree, affectionately—as “Isorla”, was completed in mid-3078, effectively identical, but with the parts being manufactured in-house by
The rest of the historical documentation regarding this machine appears to shortly before its new pilot returned to active duty. Dreadnought Interstellar Industries themselves, it allows the Dreadnought
have been lost with the fall of the Word of Blake in 3081. As a result, answers BattleCorps to make use of more readily available (if not off-the-shelf) parts
to questions regarding this ‘Mech’s original commission and prior combat This Legacy’s original Skobel Template 8 Endo Steel Chassis was repaired, and equipment—as opposed to depending on salvaged components that
involvement during the Jihad—as well as when it was assigned to the Word and the Compact Gyro that had been installed by the Word of Blake has been most likely cannot be easily sourced for replacement if they fail.
Equipment Mass
Internal Structure: Endo Steel (IS) 4
Engine: 320 Fusion XL 11.5
Walking MP: 4
Running MP: 6
Jumping MP: 3 3
Heat Sinks (Double): 18 (36) 8
Gyro: Compact (IS) 6
Cockpit: Standard 3
Armor Factor (Standard): 247 15.5
Internal Armor
Structure Value
Head 3 9
Center Torso 25 40
Center Torso (rear) 10
R/L Torso 17 27
R/L Torso (rear) 7
R/L Arm 13 26
R/L Leg 17 34
The model design of the Custom Legacy Assault BattleMech “Isorla” was
created by Aaron Swickard (“IonRaptor”). It is used here with permission.
Tragedy struck the Dreadnought BattleCorps during the fighting on the Capabilities
world of Jeronimo, shortly before Task Force Bulldog was to travel out of
known space into Clan territory, following in the wake of Task Force Serpent. In 3071, two years after the BattleCorps’ savage defeat on Basalt IV, Titan
An ambush resulted in casualties to command personnel. Colonel Lawrence was rebuilt for the second time. Its restored original Hollis Mark-X Chassis
himself was severely wounded. Requiring hospitalization, he had to be left aside, next to nothing of the original BLR-1G remains. Titan is powered by an
behind in the Draconis Combine for treatment, while the BattleCorps Orbital Heavy Industries OHI-340XLC ExtraLight Fusion Engine—the same
Mass: 85 tons continued its mission with Task Force Bulldog. With the Colonel effectively Clan-tech unit normally used in the BC-Series Reckoning Assault BattleMech.
Chassis: Hollis Mark X BLR w/CASE-II incapacitated, and the executive and third officers having been killed in the Titan has been reskinned with a newer, tougher fourteen-ton armored shell,
Power Plant: Orbital heavy Industries OHI-340XLC ExtraLight Fusion Engine same battle, the responsibility of command fell to his fourth officer—who composed of Dreadnought’s own ExoShield Ferro-Fibrous Armor, providing
Cruising Speed: 43.2 km/h also happened to be his daughter—Lieutenant Colonel Ann Lawrence. She considerably increased armor protection over even the previous refit. Titan’s
Maximum Speed: 64.8 km/h reluctantly became the BattleCorps’ sixth commander. However, the defenses are further enhanced through the addition of an Angel Electronic
Jump Jets: Kangaroo Model IX BattleMech traditionally piloted by the commander of the BattleCorps was Countermeasures Suite installed in the center torso. The Command Console
Jump Capacity: 120 meters but a gutted, armless chassis with a reparable engine and gyro, some badly installed on Pantheress VI in 3062 was repaired following the battle on Basalt
Armor: BLR-Custom-Pattern Dreadnought ExoShield Ferro-Fibrous Armor damaged armor, and a couple of lasers. IV, though it has since been reconfigured to serve as a TDN Control Unit for
Armament & Equipment: Titan’s new Dreadnought Target Data Networking (TDN) System. The head
1 Thunderstruck XV Extended Range Particle Projector Cannon In 3060, after taking possession of the former Smoke Jaguar star system was also refitted to suit the specialized pilot seats associated with the
1 PosiLock-VI Streak Short Range Missile 6-Rack of Pantheress, the BattleCorps occupied the world of Pantheress VI. During Dreadnought Armored Pilot Survival Kit (DAPSK) for both pilot and copilot,
4 Laserwerks Strobe Type 7 Medium Pulse Lasers the four years the unit spent dismantling and salvaging all the war materiel as well as all the other associated “Dreadnought Spec” standard equipment.
2 Laserwerks Strobe Type 2 Extended Range Small Pulse Lasers production facilities on the planet—taking everything that could be taken—
1 Dreadnought BC Special Mk-II Target Data Network Control System the opportunity to thoroughly rebuild and upgrade Titan presented itself for A PosiLock-VI Streak Short Range Missile 6-rack replaced the destroyed
1 Dreadnought TDN Control Interface Command Console the first time. The ‘Mech’s chassis was rebuilt and restored to its original missile system in the left torso, and a new Thunderstruck XV Extended Range
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite specifications. All of the BattleMaster’s weapons systems were replaced with Particle Projector Cannon directly replaced the ruined unit in the right arm.
Manufacturer: Trellshire Heavy Industries upgraded Clan-tech units, as were its heat sinks and armor. The head was Five of the six Clan ER Medium Lasers installed in the side torsos were a total
Primary Factory: Trellshire Manufacturing Plant; Twycross (Twycross III) modified and equipped with a Command Console, and the notoriously weak loss. Instead of sourcing another set of direct replacements, the engineers
Modified By: Dreadnought BattleCorps; Acala III head armor was reinforced. opted for twin pairs of Laserwerks Strobe Type 7 Medium Pulse Lasers. This
Communications System: Interconn-Command VIII w/TDN System means no more rear-firing weapons, but the enhanced mobility gained
Targeting & Tracking System: Pinpoint Version-IV It was not until 3069 before Titan saw real combat again, and its re-debut through the installation of four jump jets typically makes rear-firing weapons
was unfortunate. In the middle of a furious battle on Basalt IV against the altogether unnecessary. Lastly, twin Laserwerks Strobe Type 2 Extended
Overview Word of Blake’s 55th Shadow Division, the ‘Mechs of the BattleCorps’ Range Small Pulse Lasers are installed in the left arm for anti-infantry and
Command Lance—which was already down by one, with Melissa Tor’s Atlas close-range defense. The single ton of missiles housed in the left torso is
Beginning life as a typical BLR-1G BattleMaster Assault BattleMech, this having been taken out of action the previous day—were ambushed. After equipped with Second-Generation Cellular Ammunition Storage Equipment.
machine of war was built in 2848 by Trellshire Heavy Industries on Twycross. being badly mauled, one final Gauss round fired at Titan penetrated all the Meanwhile, Titan’s twenty double heat sinks work well to keep this machine
Though much of this BattleMech’s history involves simple patrols of border way through the center torso, bursting out through the shredded rear armor, cool, even in demanding combat situations.
As he did not care enough to bother asking beforehand, he only found out
afterward that the building had been successfully evacuated prior to his
explosive action. Although the way he went about it has been met with some
harsh criticism, there is no doubt that his actions—however reckless—most
likely averted total disaster.
Equipment Mass
Internal Structure: Endo Steel 4.5
Engine: 270 Fusion 14.5
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Single): 10 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 240 15
Internal Armor
Structure Value
Head 3 9
Center Torso 29 45
Center Torso (rear) 12
R/L Torso 19 30
R/L Torso (rear) 8
R/L Arm 15 11
R/L Leg 19 38
Capabilities Honor serves as part of the Blackwood Templars’ Flag Lance, operating in
support of the unit’s command staff. Honor is considerably slower than
The Highlander Assault BattleMech known as “Honor” is an oddity. The Bloodbath—Colonel Tyr Blackwood’s personal BattleMech—and though it
Mass: 90 tons heavily modified and refitted machine features several direct upgrades that comes closer to the groundspeed of Lieutenant Hank Cordova’s Berserker
Chassis: Star League XT w/CASE are perfectly sensible. However, some of the choices that have been made known as “Crossbones”, the heavier Berserker is still faster. However, Honor
Power Plant: GM 270 Fusion Engine w/MASC are unusual to say the least. and its pilot, MechWarrior Daisuke Shiro, are known as the “third punch” of
Cruising Speed: 32.4 km/h the fast-moving, melee-oriented Flag Lance for good reason.
Maximum Speed: 54.0 km/h, 64.8 km/h with MASC The centuries-old Star League XT Standard Chassis is largely unmodified,
Jump Jets: HildCo Model 10 and the original General Motors 270-rated Fusion Engine remains in place, Pilot
Jump Capacity: 90 meters though it has been upgraded to be compatible with double heat sinks. The
Armor: Custom-Fitted Starslab BW-Special w/CASE standard 54 km/h maximum speed of the Highlander has been increased to MechWarrior Daisuke Shiro – HGN-733 Highlander “Honor”: Daisuke Shiro
Armament & Equipment: approximately 65 km/h in short bursts, through the installation of Myomer served in House Kurita’s Draconis Combine Mustered Soldiery during the
1 Clan Gauss Rifle Accelerator System Circuitry (MASC) pulled from a salvaged Clan Gladiator Clan Invasion. The man had the unfortunate incident of freezing up in combat
1 Clan Long Range Missile 15-Rack OmniMech. during battle with the forces of Clan Smoke Jaguar, which resulted in the
1 Clan Streak Short Range Missile 6-Rack deaths of several of his fellow soldiers. Shiro himself survived the ordeal, but
2 Defiance B3M Medium Lasers The Starslab BW-Special Armor has been lightly modified, with some of at the time he wished he had not, as he was thrown out of the DCMS in
1 Hellion Spitfire Medium Laser the torso armor being relocated from the back to the frontal sections, as well disgrace all but immediately following the incident.
1 Martell Medium Laser as slightly reduced armor protection over the ‘Mech’s legs. The emphasis on
1 Sunglow Prism-Optic Small Pulse Laser frontal armor protection falls directly in line with the Blackwood Templars’ Soon the disgraced Shiro found himself drowning his sorrows with bottle
1 Sword aggressive combat style, and the slight reduction in leg armor is presumably after bottle of sake. In 3059, shortly after the launch of Operation BULLDOG,
Manufacturer: Hollis Incorporated done to allow for more freedom of movement, allowing the MASC to operate a chance encounter in a bar with Colonel Tyr Blackwood of the Blackwood
Primary Factory: Hollis Incorporated Facility; Corey III more efficiently. Interestingly, while having no impact on durability, the Templars Mercenaries changed the path of Shiro’s life forever. Little is known
Modified By: Blackwood Templars Mercenaries; Huntress II armor of the left arm has been stylized to resemble ancient Terran Samurai of what took place during this encounter, as even Shiro himself does not fully
Communications System: Hartford Com/A-7 Armor and adorned with Japanese kanji markings. remember the event, having been so drunk that he blacked out during it. He
Targeting & Tracking System: Starlight LX-1 only recalls awakening to a strange environment, surrounded by people that
The armament of Honor is a mixture of weapons sourced from the Inner he did not recognize—largely because he could not remember meeting them
Overview Sphere and weapons salvaged from Clan machinery. The HGN-733’s original the previous evening—and being asked if he wanted another chance. Soon
Mydron Class B Autocannon/10 has been replaced with a Clan-made Gauss after his split-second answer, he joined the Blackwood Templars, where he
Although the origins of this Highlander Assault BattleMech are unknown— Rifle fed by two tons of ammunition. The missile systems have been changed has remained ever since.
be it by accident or by design—it has been confirmed that “Honor” was first entirely. The 6-tube Short Range Missile system normally installed in the left
manufactured as an HGN-733 chassis variant. Only a partial serial number arm is removed altogether. Meanwhile, the original Long Range Missile 20- MechWarrior Daisuke Shiro is extremely loyal to the Blackwood Templars
remains, but what little is left indicates that Honor was originally an early rack in the left torso is replaced with both a 15-rack LRM system as well as a commander, and he has never disappointed his new family. Shiro reportedly
example of the HGN-733, and that it was manufactured in the mid-to-late Streak-type SRM-6, both of which are Clan-tech weapons. The LRM system has yet to ever freeze up in combat again. He can typically be found in the
29th Century by Hollis Incorporated. is fed by two tons of ammunition, while the Streak-SRM has a single ton. All thick of battle, fighting alongside the rest of Flag Lance and guarding both
the missile ammunition is housed in the left torso with the launchers and is Blackwood siblings with his very life.
As with this its origins, the circumstances surrounding the acquisition of equipped with IS-tech Cellular Ammunition Storage Equipment.
this BattleMech by the Blackwood Templars Mercenaries are a complete
unknown. Some suggest that it was acquired through another example of A total of four standard Medium Lasers serve as secondary weapons, with MechWarrior Daisuke Shiro and custom Highlander Assault BattleMech
Colonel Tyr Blackwood’s infamous gambling, while others suggest a simpler two Defiance B3M units installed in the right torso, a Hellion Spitfire unit in “Honor” originally created by Zach Schaffer.
Equipment Mass
Internal Structure: Standard 9
Engine: 270 Fusion 14.5
Walking MP: 3
Running MP: 5 (6)
Jumping MP: 3 6
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 271 17
Internal Armor
Structure Value
Head 3 9
Center Torso 29 44
Center Torso (rear) 14
R/L Torso 19 28
R/L Torso (rear) 10
R/L Arm 15 30
R/L Leg 19 34
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 4.5
Engine: 360 Fusion XL 16.5
Walking MP: 4
Running MP: 6
Jumping MP: 0
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 272 17
Internal Armor
Structure Value
Head 3 9
Center Torso 29 44
Center Torso (rear) 13
R/L Torso 19 29
R/L Torso (rear) 9
R/L Arm 15 30
R/L Leg 19 35
Overview Deployment
Among other things, the Blackwood Templars Mercenaries pride themselves on their relatively large wing of aerospace Together, the Scytha Heavy OmniFighter known as Dragon Slayer and its pilot, Major Angela Cross, lead the Blackwood
fighters. A handful of the craft fielded by the Templars are Clan Scytha Heavy OmniFighters. These Clan-made craft were Templars Mercenaries’ Seraph Aerospace Fighter Wing. During combat, most often the Dragon Slayer will be leading
captured through a ploy by the Templars’ commanding officer, Colonel Tyr Blackwood, where he issued a declaration of Templars’ fighters into battle from the front, where both the fighter’s abilities and the pilot’s skill shine most.
formal Batchall (the Clan term for “Battle Challenge”) against Clan Jade Falcon forces—with no intent to follow through.
The Templars were weary and desperate for supplies they could ill afford, so the Colonel gambled. He declared a location Pilot
and bid for the contest, all while claiming to be a Lyran unit of the Armed Forces of the Federated Commonwealth, rather
than a mercenary unit, to ensure that the Clan commander would not dismiss him out of hand as “bandit caste filth”. Major Angela Cross – Scytha “Dragon Slayer”: Angela Cross is the blonde-haired, blue eyed “angel” who is, on paper,
second in command of the Blackwood Templars Mercenaries. Cross was recruited out of the now-defunct Avanti’s Angels
The location selected for the Batchall was far from the planet’s spaceport, which was occupied by Clan Jade Falcon. mercenary unit when the Angels merged with the Templars during the Clan Invasion. Her initial training was cut short,
However, rather than meeting the Jade Falcon commander on the designated battleground, the Blackwood Templars after a stunt involving a Stuka, a control tower, and a noble-born student led to her expulsion from the prestigious
instead dropped on top of the airfield by the spaceport without warning, intent on capturing AeroFighters that had not Nagelring Military Academy on Tharkad. Fortunately for Cross, she found work through her infamous raw talent, flying
been bid for the contest, as well as any supplies and equipment they could secure. After securing the reinforcements that first with Avanti’s Angels, and then later the Blackwood Templars.
the Jade Falcon commander could call upon, the Templars had planned to leave the world—completing their typical
“smash and grab” without any casualties—rather than engaging the Jade Falcon forces in the field. Major Cross is known for feats of daring and skill that are at times bordering on psychotic. Her willingness to exceed
the factory specifications of her fighter has led her to score kills on lighter and faster crafts on several occasions. Stubborn
Instead of the expected desire to fight to the death typical of Clan warriors, however, the commander of the Jade as they come, once she has picked a target, she can be nearly impossible to shake off. It was this dogged stubbornness
Falcon Star of five garrison ‘Mechs on-planet stood down, accepting Colonel Blackwood’s offer of employment should that led to her once chasing a target into hostile airspace, where she lost one of her own fighter’s wings to enemy anti-
they surrender. Blackwood often made such an offer as a joke, if not an outright insult to his Clan opponents. Little did air artillery. She managed to nurse her crippled fighter back to base, eventually crash-landing onto the runway. She then
he know that the commander of the garrison Star was in fact a former mercenary himself, a MechWarrior by the name spent the next several minutes cursing incoherently and profusely on an open frequency for any who bothered to listen.
of Keith Knox. Knox had been taken Bondsman years earlier and eventually earned the honor of becoming a MechWarrior Cross’ skill in fighter-to-fighter combat—both in and out of atmosphere—is enough to match her arrogance, but her ability
of Clan Jade Falcon, not that he really cared about any of the “honor” involved. Knowing well that it was likely his only for to provide air-support for ground troops is somewhat lacking. When assigned the latter task, she will often turn the
chance of survival, Knox accepted Colonel Blackwood’s offer, surprising the Colonel. As members of Knox’s command operation into a contest—and she has nearly crashed Dragon Slayer more than once during such “contests”.
went so far as to physically restrain the ‘Mech piloted by the one warrior under his command who disagreed with the
decision, Colonel Blackwood decided to take Knox at his word and welcomed the warriors with relatively open arms. Over the years, the origin of the name “Dragon Slayer” has been the subject of conjecture and debate, and it is most
commonly believed to be a reference to either the Draconis Combine or perhaps even the Dreadnought BattleCorps, due
The best-known aerospace fighter salvaged during this raid is the Scytha Heavy OmniFighter known as “Dragon Slayer”. to the rather obvious symbology. However, according to Cross, the name is a reference to the Clans. She has been quoted
This fighter is piloted by the Templars’ second in command, one Major Angela Cross. The fighter’s nose art depicts an as saying that there is no reason for her to reference the other two, as she feels that they, in her words, “…Aren’t worth
angelic woman brandishing a sword, while one of the fighter’s stabilizer fins is painted with the same angel stabbing her it—especially the Dracs.”
sword into the chest of a dragon. As Major Cross is a member of the Templars elite “Red Arms”, her fighter’s right wing
and stabilizer fin are painted in a splattered, bloody red coloration. Between its pilot’s “insane” skill, the sheer firepower Her belief in her own superiority, as well as that of the Templars as a whole, has often led to additional friction between
of the fighter, and its unique livery, Dragon Slayer is certainly an unforgettable craft to witness in action. the mercenaries and local forces. It is not uncommon for her to share time in local jail cells with Candace Killian after the
two have spent an evening together either hustling gamblers at the pool table or getting themselves involved in a brawl—
Capabilities the latter often a direct result of the former.
The Scytha is already a formidable heavy OmniFighter, toting tremendous firepower in virtually any of its standard Despite her flaws and quirks, Major Angela Cross is a trusted member of the Blackwood Templars, and she has proven
configurations. It also features very respectable armor, and impressive maneuverability for its size and weight. The Scytha herself time and again. However, because of her more extreme personality traits—as well as those of the Templars’
known as “Dragon Slayer” was captured in the PRIME configuration. This meant that the craft was originally armed with commander, Colonel Tyr Blackwood—a running joke among unit’s personnel is the question of, “Who do you think is
twin Extended Range Large Lasers installed in each wing, an Extended Range Large and Small Laser grouped with an Ultra crazier? The Major or the Colonel?”
Major Angela Cross and custom Scytha Heavy OmniFighter “Dragon Slayer”
originally created by Zach Schaffer.
It was not until early 3079 before this desire to be reunited with her old
‘Mech was finally satisfied, but she found herself once again at the controls
of Star Burst, albeit a slightly different Star Burst than she remembered. At
first, she was somewhat dubious of the new Dreadnought Spec pilot seat and
suit, as well as the new TDN System. Despite her initial reservations, Larissa,
now holding the proper rank of Lieutenant, quickly grew accustomed to the
additions made to her machine, and she has since even come to be quite
complimentary of the new technology.
Equipment Mass
Internal Structure: Standard w/C-CASE 9
Engine: 270 Fusion 14.5
Walking MP: 3 Weapons and Ammo Location Critical Tonnage
Running MP: 5 Jump Jet CT 1 –
Jumping MP: 3 6 Gauss Rifle RT 6 12
Heat Sinks (Double): 16 (32) 6 Jump Jet RT 1 –
Gyro: Standard 3 Double Heat Sink RT 2 –
Cockpit: Standard 3 Ammo (Gauss) 16 RT 2 2
Armor Factor (Ferro-Fibrous): 278 14.5 Gauss Rifle LT 6 12
Internal Armor Jump Jet LT 1 –
Structure Value Double Heat Sink LT 2 –
Head 3 9 Ammo (Gauss) 16 LT 2 2
Center Torso 29 45 3 ER Medium Lasers RA 3 3
Center Torso (rear) 12 Double Heat Sink RA 2 –
R/L Torso 19 28 3 ER Medium Lasers LA 3 3
R/L Torso (rear) 10 Double Heat Sink LA 2 –
R/L Arm 15 30 Double Heat Sink RL 2 –
R/L Leg 19 38 Double Heat Sink LL 2 –
In September of 3069, the Dreadnought BattleCorps 1st RCT was pitted It was a challenge to modify the old, but reliable Vlar 300 Fusion Engine to
against the Word of Blake’s 55th Shadow Division—an elite cybernetically- make it compatible with the newer and more compact Clan-tech double heat
enhanced Manei Domini unit—in a terrible battle on the world of Basalt IV. sinks now favored by the Dreadnought BattleCorps, but it was eventually
The BattleCorps, which had by then been selected as Dreadnought’s weapon accomplished, and the powerplant itself was given a thorough refresh while
against the Word of Blake during the Blakist Jihad, proved to be woefully it was disassembled. What was left of the original armor was upgraded to
underprepared to face such an opponent. Dreadnought’s own ExoShield Ferro-Fibrous Armor, and CASE-II was installed
in the side torsos, maximizing the survivability of this ‘Mech beyond original
During the second-to-last day of the vicious fighting on Basalt IV, Captain specifications. Meanwhile, the iconic “Death’s Head” of the ‘Mech was
Melissa Tor’s Atlas was crippled while providing cover fire for Colonel Ann rebuilt, and it now features an upgraded cockpit, which includes a new pilot
Lawrence’s BattleMaster. Captain Tor was severely wounded, and although seat and all the associated equipment typical of a “Dreadnought Spec” refit.
the BattleCorps successfully escaped Basalt IV the following day, she was out
of commission for several months while she recovered from her injuries— As this Atlas had been modified previously to feature a custom weapons
injuries which most agree certainly should have killed her. array, the Clan-tech weapons installed during the refit of what has become
known as “Skully 2.0” are all seamless improvements over the previous
Under Colonel Ann Lawrence’s orders, a handful of the Dreadnought custom armament. The ruined right-torso Grizzard Gauss Rifle was replaced
BattleCorps’ best engineers and MechTechs created something truly special directly with a lighter Magna-Rail-15 unit, and the ammunition capacity was
for Melissa Tor to “come home to” once she had fully recovered. The Atlas increased from two tons to three. The wrecked left-torso 15-tube Mitchell
was already in dire need of repair and refit because of the severe damage it Long Range Missile system was directly replaced with a Reacher-Series unit,
had suffered on Basalt IV. However, instead of just repairing it, the highly and the ammunition capacity was likewise increased from two tons to three.
skilled technicians and engineers took the already-iconic BattleCorps ‘Mech In place of the old Donal PPCs, Thunderstruck XV Extended Range Particle
and made something altogether more impressive. Projector Cannons were installed in the Atlas’ forearms. Lastly, the Intek
Medium Laser, which had featured prominently as the “right eye” of the
The venerable Atlas had already been previously customized to Captain skull-shaped head, was replaced with a Flash-Sword VII Extended Range unit.
Tor’s personal taste—although the records of who made these modifications
Mass: 100 tons originally are still classified—and “Skully” had been an extremely potent and Replacing the destroyed Angst Accuracy Targeting & Tracking System, a
Chassis: Foundation Type 10X Standard AS7 w/CASE-II respectable war machine. However, after the Atlas was refitted to meet new and improved Pinpoint Version-IV System was installed. To make the
Power Plant: Vlar 300 Standard Fusion Engine “Dreadnought Spec” standards, the good Captain’s personal BattleMech was centuries-old BattleMech compatible with Dreadnought’s new Target Data
Cruising Speed: 32.4 km/h more powerful than ever. Despite the significantly more advanced and Networking (TDN) System, the aging Angst Discom Communications System
Maximum Speed: 54.0 km/h powerful technology packed under the skin of Tor’s Atlas, the team had been was replaced with an Interconn-Comm VII unit. The all-new TDN System
Jump Jets: None extremely careful to maintain the outward appearance of the machine, grants Skully 2.0 the ability to share targeting telemetry with friendly Linked
Jump Capacity: 0 meters making sure it looked just as it had been before the unfortunate events on units, which in turn enhances the accuracy of this powerful BattleMech’s
Armor: AS7-Custom-Pattern Dreadnought ExoShield Ferro-Fibrous Armor Basalt IV. extensive arsenal of long-range weapons when providing fire support for
Armament & Equipment: friendlies that are closer to its target. The addition of an Angel ECM Suite
2 Thunderstruck XV Extended Range Particle Projector Cannons To say that Captain Tor was happy to see her BattleMech rebuilt and ready provides it with potent electronic warfare capacity—among other things
1 Magna-Rail-15 Gauss Rifle for action would be an understatement. In a rare, overwhelmingly emotional allowing it to jam enemy communications and prevent hostile missile locks.
1 Reacher-Series Long Range Missile 15-Rack moment, the recently-recovered woman all but literally broke into tears of
1 Flash-Sword VII Extended Range Medium Laser joy. She sprinted across the ‘Mechbay and ran up onto the Atlas’ right foot Although its closer-ranged armament is less impressive, Skully 2.0 is a
1 Dreadnought BC Special Mk-II Target Data Networking System to embrace what little she could wrap her arms around of the ‘Mech’s shin. brutal long-range fire support unit. It can open a trio of gaping holes in an
1 EW-Special Mk-IV Angel Electronic Countermeasures Suite enemy’s armor at long range, then follow up with a wave of Long Range
Manufacturer: Defiance Industries This strong reaction does support the possibility that this ‘Mech might Missiles to inflict even further damage. With twenty double heat sinks, it is
Primary Factory: Hesperus II Facility; Hesperus II truly be a family heirloom, but it could also be evidence that it is the only sufficiently heat efficient to fire its primary weapons constantly while on the
Modified By: Dreadnought BattleCorps; Acala III holdover from her previous life before becoming the woman she is now. move until its significant store of ammunition is depleted—a minimum of
Communications System: Interconn-Comm VII w/TDN System Regardless, it became clear to all that the machine held far more sentimental four minutes of constant firing—at which point it is reduced to “just” its twin
Targeting & Tracking System: Pinpoint Version-IV value than she had ever previously let on. Extended Range Particle Projector Cannons.
Overview The rechristening of Captain Melissa Tor’s BattleMech from “Skully” to Variants
“Skully 2.0” was unofficial at first. The slightly altered nickname was teasingly
As with its pilot, the Dreadnought BattleCorps’ only Atlas is something of suggested by members of the team who helped to rebuild the ‘Mech from AS7-D “Skully” – When Melissa Tor all but spontaneously appeared among
an enigma. Some believe the iconic assault-class BattleMech to be a family the bits that were left, but Tor herself soon accepted it as her machine’s new the Dreadnought BattleCorps ranks in 3066 as a Lieutenant, her Atlas, built
heirloom of the seemingly extinct Tor family line. However, given the very “official” nickname. originally as an AS7-D chassis variant, already featured a custom weapons
Equipment Mass
Internal Structure: Standard (IS) 10
Engine: 300 Fusion (IS) 19
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 20 (40) 10
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 307 16
Internal Armor
Structure Value
Head 3 9
Center Torso 31 47
Center Torso (rear) 15
R/L Torso 21 32
R/L Torso (rear) 10
R/L Arm 17 34
R/L Leg 21 42
Space Allocation
Location Fixed Components Spaces Remaining
Head None 1
Center Torso None 2
Right Torso 2 XL Engine, 2 Double Heat Sink 8
Left Torso 2 XL Engine, 2 Double Heat Sink 8
Right Arm None 10
Left Arm None 10
Right Leg None 2
Left Leg 2 Double Heat Sink 0
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 5
Engine: 400 Fusion XL 26.5
Walking MP: 4
Running MP: 6 (8)
Jumping MP: 0
Heat Sinks (Double): 19 (38) 9
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 280 17.5
Internal Armor
Structure Value
Head 3 9
Center Torso 31 40
Center Torso (rear) 15
R/L Torso 21 32
R/L Torso (rear) 10
R/L Arm 17 32
R/L Leg 21 34
Capabilities
Type: Kraken (Bane) “Butcher”
Weighing in at a full hundred tons and having begun life as a Clan-made Classification: Assault BattleMech (Uniquely Modified/Customized)
BattleMech—even if a “mere second-line” one—Butcher is predictably an Technology Base: Clan
awe-inspiring machine. Still utilizing purely Clan-developed technology even Tonnage: 100
today, Butcher boasts an impressive array of long-range firepower. Battle Value: 2,747
Notes: Features the following Design Quirks: Extended Torso Twist,
A Gauss Rifle is housed in each arm, backed by an Extended Range Large Improved Targeting (Long), Protected Actuators; Difficult to Maintain, Non-
Laser installed in each side torso—these serve as Butcher’s main guns, while Standard Parts. Arm Actuators: Upper Only.
twin LB 5-X Autocannons mounted high in the side torsos above the lasers
fill a secondary fire role. As Butcher only carries cluster-type munitions for its Equipment Mass
Mass: 100 tons autocannons, the “secondary guns” are used to take advantage of holes in Internal Structure: Standard w/C-CASE 10
Chassis: Type AXT, Mk. XX w/Integrated CASE enemy armor created by the main guns, seeking to deal significant damage Engine: 300 Fusion XL 9.5
Power Plant: 300 Type I XL to a target’s critical internal systems. Should an opponent manage to close Walking MP: 3
Cruising Speed: 32.4 km/h into short range, a pair of four-tube Short Range Missile systems—mounted Running MP: 5
Maximum Speed: 54.0 km/h outboard on Butcher’s arms—allow it to deal even greater damage up close. Jumping MP: 0
Jump Jets: None Heat Sinks (Double): 13 (26) 3
Jump Capacity: 0 Meters A quartet of Light Machine Guns are installed in the machine’s side torsos Gyro: Standard 3
Armor: Custom-Fitted Clan Ferro-Fibrous Armor and arms, providing a potent defense against hostile infantry. The complex Cockpit: Standard 3
Armament & Equipment: ammunition feed mechanisms for the LB-X Autocannons, SRMs and LMGs— Armor Factor (Ferro-Fibrous): 288 15
2 Clan LB 5-X Autocannons which all pull from ammunition housed in the ‘Mech’s legs—require constant Internal Armor
2 Clan Extended Range Large Lasers maintenance. Given the nature of Butcher’s armament, its thirteen double Structure Value
2 Clan Gauss Rifles heat sinks are sufficient to keep the ‘Mech cool under most circumstances. Head 3 9
2 Pattern D-IV Short Range Missile 4-Packs Center Torso 31 44
4 GM Ultralight Light Machine Guns Pilot Center Torso (rear) 13
Manufacturer: Clan Hell’s Horses R/L Torso 21 32
Primary Factory: Tokasha MechWorks Alpha; Tokasha IV MechWarrior Celeste “Tinker” Colbrand – Kraken (Bane) “Butcher”: Celeste R/L Torso (rear) 10
Modified By: Blackwood Templars Mercenaries; Location Unknown Colbrand was orphaned when her home on Blue Hole was destroyed by a R/L Arm 17 34
Communications System: JNE Integrated flood. Unfortunately, her family died in the flood. With most of her personal R/L Leg 21 35
Targeting & Tracking System: Series IV TTS assets lost to the natural disaster, young Celeste had nowhere to go, and no
money with which to get there. As the Blackwood Templars Mercenaries Weapons and Ammo Location Critical Tonnage
Overview happened to be on Blue Hole at the time—and they were still licking their Double Heat Sink CT 2 –
wounds after a previous contract had gone badly for them—the Templars ER Large Laser RT 1 4
The 100-ton Kraken Assault BattleMech—originally designated the Bane accepted a short-term contract to assist with local disaster relief efforts. LB 5-X Autocannon RT 4 7
by its Clan creators—is a fearsome machine to its allies, and an absolute Light Machine Gun RT 1 0.25
terror to its enemies. “Butcher” is the Kraken owned and operated by Celeste Happening across young Celeste freezing and alone on the side of a road ER Large Laser LT 1 4
Colbrand of the Blackwood Templars Mercenaries, and it is a machine that between the flooded city and the local spaceport, Colonel Tyr Blackwood LB 5-X Autocannon LT 4 7
lives up to its nickname. This bulky BattleMech’s primary role is that of a picked her up and brought her aboard one of the unit’s DropShips to provide Light Machine Gun LT 1 0.25
long-range direct fire support unit, and it is often paired with the Templars’ her with food and shelter. The Colonel soon took her under his wing after Gauss Rifle RA 6 12
1st Company Captain’s Thunder Hawk. learning she had nobody else to turn to, and once she was introduced to the Light Machine Gun RA 1 0.25
Templars, she quickly became accepted into her new “family”. SRM-4 RA 1 1
Butcher is built on a standard Kraken chassis, which was salvaged with a Ammo (Gauss) 16 RA 2 2
wrecked engine during one of the numerous contracts accepted by the Colbrand received her nickname of “Tinker” after being constantly and Gauss Rifle LA 6 12
Blackwood Templars in the late 3050s that pitted them against various Clan consistently found in the ‘Mechbays and workshops when she was young— Light Machine Gun LA 1 0.25
forces—shortly before the mercenary unit became involved in Operation always learning and trying to assist the MechTechs with repairs. SRM-4 LA 1 1
BULLDOG. Following the same battle from which the Kraken was salvaged, a Ammo (Gauss) 16 LA 2 2
Vulture’s tattered remains were also salvaged. Although the chassis of the Years later, Colbrand became the youngest pilot in the history of the Ammo (SRM-4) 25 RL 1 1
Vulture was damaged beyond any hope of repair, certain key components Templars. She is also now regarded as the Templars’ best technician. Despite Ammo (LB 5-X Cluster) 20 RL 1 1
were still intact and salvageable—most importantly its ExtraLight 300-rated her status as a MechWarrior, she can nearly always be found in a ‘Mechbay Ammo (LMG) 100 LL 1 1
Fusion Engine, which soon became Butcher’s new powerplant. tinkering with one of her various personal projects. It was her tinkering that Ammo (LB 5-X Cluster) 20 LL 1 1
Equipment Mass
Internal Structure: Standard 10
Engine: 300 Fusion XL (Cl) 9.5
Walking MP: 3
Running MP: 5
Jumping MP: 3 6
Heat Sinks (Double): 15 (30) 5
Gyro: Standard 3
Cockpit: Command Console 6
Armor Factor (Fe-Fibrous (Cl)): 307 16
Internal Armor
Structure Value
Head 3 9
Center Torso 31 46
Center Torso (rear) 16
R/L Torso 21 31
R/L Torso (rear) 11
R/L Arm 17 34
R/L Leg 21 42
The Word of Blake’s elite Manei Domini 55th Shadow Division deployed over a hundred Celestial OmniMechs during the final critical battle of Operation LANCASTER. This by itself was not surprising,
as Manei Domini often piloted these machines. However, the 55th’s Celestial OmniMechs featured new weapons configurations, wielding far greater firepower than ever before. As many of these
machines were typically associated with much more limited armaments, these devastating “Divinus”-configured Celestial OmniMechs proved to be a lethal surprise for the Lancaster Coalition.
394 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
C-MK-O MALAK LIGHT CELESTIAL OMNIMECH “DIVINUS” (CONFIGURATION W)
“Demon” by those who fought against them. Type: Malak (C-MK-O)
Classification: Light OmniMech (Production)
Already a respectable light OmniMech to begin with, the Malak was made Technology Base: Inner Sphere
far more dangerous when equipped in its newer Divinus configuration. The Tonnage: 30
Lancaster Coalition had no way to anticipate the sheer firepower that the Base Battle Value: 482
Malak Divinus was packing until the first shot fired by one of these struck Pod Space: 9.5 tons
home. Data collected post-LANCASTER shows that the first shot in question Notes: Features the following Design Quirks: Improved Communications,
cleaved an unsuspecting Dreadnought BattleCorps 4th Battalion Ravage Improved Sensors; Bad Reputation.
scout OmniMech in two—shortly before the 4th was betrayed from within,
resulting in the demise of nearly the entire battalion. Equipment Mass
Internal Structure: Endo Steel 1.5
Unfortunately for the rest of the Lancaster Coalition, the devastating Engine: 210 Light Fusion 7
betrayal of the 4th Battalion was the result of a Word of Blake agent taking Walking MP: 7
control of the battalion’s Omniscience Command Vehicle. The agent not only Running MP: 11
blocked the battalion’s communications and scrambled the function of their Jumping MP: 0
own Target Data Networking (TDN) Systems, but he forwarded the 4th’s own Heat Sinks (Double): 10 (20) 0
tactical data to the attacking 55th Shadow Division in real time. The agent Gyro: ExtraLight 1.5
also blocked the 4th Battalion from communicating with the rest of the Cockpit: Small 2
Lancaster Coalition, preventing anyone else from learning anything useful. Armor Factor (Light Fe-Fibrous): 101 6
Internal Armor
Although the only confirmed encounters with Divinus-configured Malaks Structure Value
were those faced by the Lancaster Coalition in 3077, unconfirmed reports Head 3 9
indicate that later encounters occurred during one or more of the final Center Torso 10 14
battles to liberate Terra at the end of Operation SCOUR. It is believed that Center Torso (rear) 4
Mass: 30 tons none of these were captured intact or in an at least salvageable condition. It R/L Torso 7 11
Chassis: Celestial Series MK1E Endo Steel was fortunate for the rest of the Inner Sphere that the Word of Blake R/L Torso (rear) 3
Power Plant: DefHes 210 Light Fusion Engine apparently only fielded the devastating Divinus configuration Celestial R/L Arm 5 10
Cruising Speed: 75.6 km/h OmniMechs in significant numbers with their elite 55th Shadow Division. R/L Leg 7 13
Maximum Speed: 118.8 km/h
Jump Jets: None Capabilities Space Allocation
Jump Capacity: 0 meters Location Fixed Components Spaces Remaining
Armor: Divine Shield Light Ferro-Fibrous Featuring an already impressive array of advanced technologies at the Head None (Small Cockpit) 2
C-MK-O Fixed Equipment & Base Pod Space: time of its introduction, the Malak was a staple of the Word of Blake’s elite Center Torso None (ExtraLight Gyro) 0
1 Improved C3 Computer Manei Domini. This light Celestial OmniMech utilizes an ExtraLight Gyro, an Right Torso 2 Light Fusion Engine, 1 Light Ferro-Fibrous, 5
9.5 tons of pod space available Endo Steel Chassis, Light Ferro-Fibrous Armor, an Improved C3 Computer, 4 Endo Steel
“Divinus” (Configuration W) Armament & Equipment: and a Small Cockpit. However, despite all its advanced technology, the Malak Left Torso 2 Light Fusion Engine, 2 C3i Computer, 1
1 Clan Extended Range Particle Projector Cannon is only moderately quick for a light-class ‘Mech of the later 31st Century— 3 Double Heat Sink, 4 Endo Steel
w/Experimental Clan ER PPC Capacitor marking it as a competent, albeit not spectacular, scout-in-force machine. Right Arm 6 Endo Steel 4
1 Clan Medium Pulse Laser Left Arm 3 Double Heat Sink, 2 Light Ferro-Fibrous 5
1 Diverse Optics Sunbeam ER Small Laser An experimental configuration of the Malak—designated the “Caelestis”, Right Leg 2 Light Ferro-Fibrous 0
Manufacturer: Federated Worlds Defense Industries or Configuration “S”—was armed with an Inner-Sphere-tech Extended Range Left Leg 2 Light Ferro-Fibrous 0
Primary Factory: Gibson Federated BattleMechs Facility; Gibson III Particle Projector Cannon enhanced by a PPC Capacitor, backed by a trio of
Communications System: Master’s Voice Cel-Alpha IS-tech Extended Range Small Lasers. This configuration never saw significant Fixed Equipment Location Critical Tonnage
Targeting & Tracking System: Master’s Sight 1-Omega w/C3i Computer use in combat, as the armament limited its operational capacity too much. Improved C3 Computer LT 2 2.5
The Divinus, or Configuration “W”, appears to be an evolution of this design.
Overview Weapons and Ammo Location Critical Tonnage
The addition of Clan-based weapons technology completely changes how Divinus (Configuration W)
The lightest of the infamous Celestial OmniMechs created for the Word of the concept behind the Caelestis Configuration can be applied. The Divinus Medium Pulse Laser (Cl) H 1 2
Blake’s elite Manei Domini special forces, the Malak was an effective light- takes the Caelestis and enhances its battlefield capabilities considerably. The ER PPC (Cl) RT 2 6
class OmniMech during the Jihad. The Malak Light OmniMech was already Divinus’ primary weapon, a smaller and lighter Clan-tech Extended Range X/C-ERPPC Capacitor* RT 1 1
available in a variety of different weapons configurations prior to the combat Particle Projector Cannon, provides half-again as much punch as the weapon Lower Arm Actuator RA 1 –
debut of its Divinus Configuration, otherwise known as Configuration “W”. used in the Caelestis. With the addition of an Experimental Clan ER PPC Hand Actuator RA 1 –
The first known examples of these machines were fielded by the Word of Capacitor, the main gun of the Divinus is an astonishingly powerful long- ER Small Laser RA 1 0.5
Blake’s 55th Shadow Division, and they were a painful surprise for the range weapon. However, as the PPC itself cannot be fired while its X/C-ERPPC Lower Arm Actuator LA 1 –
Lancaster Coalition during the final critical battle of Vyrie City—the capital Capacitor is charging, this configuration of the Malak is best used as a hit- Hand Actuator LA 1 –
city of Ashkum IV—at the end of Operation LANCASTER in 3077. Named after and-fade sniper and harasser. Meanwhile, the combination of a Clan-tech Battle Value: 1,594
the Arabic word for “Angel”, the first Malak Light OmniMechs encountered Medium Pulse Laser and an IS-tech Extended Range Small Laser serve as
in Divinus configuration were initially given the rather ironic nickname of reasonable and effective backup weapons for the devastating main gun. * See Special Dreadnought / Lancaster Specific Rules (Pages 428-431)
It was only bad luck on the part of the Word of Blake that most encounters Although a handful of Divinus-configured Seraphs were spotted during the
with this machine involved the Dreadnought BattleCorps, whose even more fighting to liberate Terra from the Blakists, the only large-scale deployment
advanced Target Data networking (TDN) System shared telemetry far better of these machines recorded was that of the Word of Blake’s 55th Shadow
than even the Word of Blake’s own Improved C3 Networks, which generally Division on Ashkum IV in 3077. No examples of this machine have ever been
prevented the BattleCorps’ forces from falling for such a trap. However, confirmed as successfully salvaged. However, some rumors and unconfirmed
unlike the Word of Blake’s own C3i Networks, Dreadnought’s TDN Systems reports indicate at least two may have been salvaged on Ashkum IV by the
also proved to be impossible for the 55th Shadow Division’s electronic Lancaster Coalition, and three or more may have been salvaged on Terra—
countermeasures to disrupt. Meanwhile, the BattleCorps’ nearly excessive with at least two of the latter being recovered fully intact and undamaged.
application of powerful electronic warfare suites made most any battlefield
coordination between the 55th Shadow Division’s troops extremely difficult.
Type: Seraph (C-SRP-O)
Mass: 85 tons The assault-class Seraph Divinus lacks the primary weapon associated with Classification: Assault OmniMech (Production)
Chassis: Celestial Series SP1 Standard all other Divinus-configured Celestial OmniMechs—the Clan-tech Extended Technology Base: Inner Sphere
Power Plant: GM 255 Light Fusion Engine Range Particle Projector Cannon boosted by an Experimental Clan ER PPC Tonnage: 85
Cruising Speed: 32.4 km/h, 43.2 km/h w/Triple Strength Myomer Capacitor. However, its potent array of other Clan-tech weapons more than Base Battle Value: 1,080
Maximum Speed: 54.0 km/h, 64.8 km/h w/Triple Strength Myomer makes up for this omission. It is believed that some of the Clan-tech weapons Pod Space: 43 tons
Jump Jets: None systems used in the Divinus-configured Celestial OmniMechs were salvaged Notes: Features Triple Strength Myomer special equipment as well as the
Jump Capacity: 0 meters and restored units originally manufactured by the Clans themselves, but it is following Design Quirks: Improved Communications, Improved Sensors; Bad
Armor: Durallex Divine Guardian Standard far more likely that most or all of them were copies produced on Terra by Reputation.
C-SRP-O Fixed Equipment & Base Pod Space: the Word of Blake, utilizing Comstar-built facilities constructed specifically to
1 Improved C3 Computer manufacture replicated Clan technology and weaponry. Equipment Mass
43 tons of pod space available Internal Structure: Standard 8.5
“Divinus” (Configuration W) Armament & Equipment: Capabilities Engine: 255 Light Fusion 10
3 Clan Large Pulse Lasers Walking MP: 3 (4)
5 Clan Medium Pulse Lasers The Seraph is the second-heaviest of the high-tech Celestial OmniMechs Running MP: 5 (6)
2 Diverse Optics Sunbeam Extended Range Medium Lasers utilized by the Word of Blake. Although this machine does utilize relatively Jumping MP: 0
1 Diverse Optics Sunbeam Extended Range Small Laser conventional chassis and armor materials, it is powered by a Light Fusion Heat Sinks (Double): 10 (20) 0
1 Hessen IX Small Laser Engine, and it is equipped with an Improved C3 Computer, a Small Cockpit, Gyro: Standard 3
1 Zippo Flamer and most notably Triple Strength Myomer. The Seraph is normally somewhat Cockpit: Small 2
1 Divinity’s Smite Hatchet maligned because of its inability to make particularly efficient use of its Triple Armor Factor (Standard): 256 16
Manufacturer: Federated Worlds Defense Industries Strength Myomer in most of its configurations, but the Divinus Configuration Internal Armor
Primary Factory: Gibson Federated BattleMechs Facility; Gibson III of this machine seeks to take advantage of this underutilized feature. As with Structure Value
Communications System: Master’s Voice Cel-Alpha other Divinus-configured Celestial OmniMechs, the Seraph Divinus features Head 3 9
Targeting & Tracking System: Master’s Sight 1-Omega w/C3i Computer an array of powerful, largely Clan-tech weapons systems. However, unlike Center Torso 27 40
the others, the Seraph’s focus is split between ranged and melee combat. Center Torso (rear) 13
Overview R/L Torso 18 26
The primary ranged weapons of the Seraph Divinus are a trio of Clan-tech R/L Torso (rear) 9
An already intimidating machine in any of its normal configurations, the Large Pulse Lasers, installed high on the body across the head and side R/L Arm 14 27
Word of Blake’s Seraph Celestial OmniMech is surprisingly even more brutal- torsos. The secondary ranged weapons consist of five Clan-tech Medium R/L Leg 18 35
Note: Due to a mistake in the specifications supplied to Matt Plog during the
commissioning of the art, the Flamer was illustrated on the wrong side.
The Dreadnought BattleCorps 1st Regimental Combat Team gathered significant information regarding the Clans during the years they spent in Clan territory following Operation BULLDOG. This
notably included specifications and historical background information pertaining to previously-undocumented Second-Line BattleMech types employed by various Clans. The following BattleMech
Technical Readout articles contain the information gathered by the BattleCorps. It should be noted that these articles do include supplemental information gathered from other sources.
407 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
WASP IIC LIGHT BATTLEMECH
inquired about their attitude. The Snow Raven commander simply replied, Wasp IIC 4 – A more recent variant of the Wasp IIC utilizing newer weapons
“We will probably just create a Stinger IIC.” technology was introduced by Clan Star Adder in late 3062. The Wasp IIC 4 is
a basic weapons swap from the first-generation variant of the ‘Mech. The
These words later turned out to be all but prophetic, but the woman who Wasp IIC 4 focuses on the already-potent urban combat capability of the
uttered them would never know. It was a century later, nearly to the day, standard Wasp IIC, taking it a considerable step further by replacing the ER
when the joint venture between the Outworlds Alliance and Clan Snow Medium Lasers and with newer, more powerful Heavy Medium Lasers.
Raven did just that. In 3085, Alliance Defenders Limited, a manufacturer
under the banner of the recently-formed Raven Alliance, began producing The increased damage potential of the more powerful lasers does
the Stinger IIC as a scout companion to the Wasp IIC—the latter of which theoretically improve the design’s value as an urban combat specialist, but
continues to see use by the Raven Alliance. the significant increase in waste heat produced by the Heavy Medium Lasers
does render this machine more prone to eventual overheat if both of its
Capabilities lasers are used simultaneously with either its jump jets or Flamers. Although
waste heat buildup is a concern for this machine on paper, it is rarely an issue
The Wasp IIC Light BattleMech is a well-rounded, reconnaissance-capable faced in actual combat conditions.
machine with excellent mobility and a respectable punch for its twenty-ton
Mass: 20 tons weight. With its 210-meter jump capacity, this ‘Mech is particularly effective Heat management is not the Wasp IIC 4’s greatest issue, either. The
Chassis: Model W2E Endo Steel w/Integrated CASE in urban and canyon environments, and other areas with challenging terrain. notorious accuracy—or lack thereof—of its Heavy Medium Lasers generally
Power Plant: Type 43-Alpha 140 Fusion XL Engine Though created initially as a far more effective urban and mountain area draws considerably greater criticism than the increased waste heat output,
Cruising Speed: 75.6 km/h patrol ‘Mech, the Wasp IIC’s over-performing nature often led it to be used leading this variant to become arguably the most maligned version of the
Maximum Speed: 118.8 km/h in front-line reconnaissance applications when it was first introduced. Wasp IIC. (Battle Value: 713) Features the following Design Quirks: Easy to
Jump Jets: Andoran Model JJII Maintain, Extended Torso Twist, Rugged; Exposed Actuators.
Jump Capacity: 210 meters The Wasp IIC features very reasonable firepower for its weight class. It is
Armor: Forging BT Standard Armor primarily armed with an Extended Range Medium Laser installed in each Wasp IIC 5 – In early 3063, all but immediately following the introduction of
Armament & Equipment: forearm, and these anti-armor and anti-’Mech weapons are backed by an the Wasp IIC 4, another Heavy Laser upgrade of the Wasp IIC began stepping
2 Series 2b ER Medium Lasers anti-infantry Flamer housed in each side torso. Coupled with its impressive off assembly lines. The Wasp IIC 5 is a direct upgrade of the Wasp IIC 3, and
2 Series II “Hellfire” Flamers mobility, the Wasp IIC can make exceptionally good use of its weaponry by it is likewise built around a single weapon system—in this case, a Model X
Manufacturer: Clan Snow Raven firing and repositioning repeatedly and quickly. With just eleven double heat Heavy Large Laser. The bulky weapon, as with the Extended Range Large
Primary Factory: Clan Snow Raven Industrial Complex Chi; Lum (Lum IV) sinks, however, it will gradually build up more waste heat than the cooling Laser in the Wasp IIC 3, takes up the entire lower right arm of the ‘Mech,
Communications System: P1 Fenix Integrated system can dissipate when constantly pushed to its absolute limits. necessitating the removal of the right hand actuator to fit. However, Unlike
Targeting & Tracking System: Tokasha B-4T&T the Wasp IIC 3’s more streamlined and compact primary weapon, the Heavy
With its four tons of Forging BT Standard Armor, the Wasp IIC is well- Large Laser prominently featured in the Wasp IIC 5 is far bulkier, causing the
Overview armored—with the notable exception that its head is considered by most to right forearm to look swollen or bloated in comparison. (Battle Value: 897)
be lacking in relative armor protection. The fact that this 20-ton scout ‘Mech Features the following Design Quirks: Easy to Maintain, Extended Torso
Based loosely on one of the oldest scout ‘Mechs ever built, the Wasp IIC is can survive a direct hit from a weapon as powerful as a Gauss Rifle to the Twist, Rugged; Exposed Actuators.
most certainly a worthy successor to the original Wasp Light BattleMech first center torso and remain functional is certainly impressive, although any
introduced five centuries prior. additional damage dealt to the same area will all but surely incapacitate it. Wasp IIC 6 – The most recent variant of the Wasp IIC, the Wasp IIC 6, began
final testing by the Raven Alliance on their homeworld of Alpheratz in 3084.
Clan Snow Raven began producing the Wasp IIC Light BattleMech in 2962. Variants This new variant is slated to begin production in mid-to-late-3085. The newer
This was a time when most Clans were focusing much of their attention and Wasp IIC 6 returns to the “dual-wielding” style of the more common Wasp
resources on the creation of more advanced and powerful OmniMechs. The Wasp IIC 2 – Introduced in 2962 alongside the standard Wasp IIC, the Wasp IIC variants, and it is seemingly a direct upgrade over the Wasp IIC 4 first
choice by Clan Snow Raven to instead design and begin producing a new IIC 2 is armed in such a way as to vaguely emulate the centuries-old, original introduced by Clan Star Adder.
light-class second-line BattleMech as sophisticated and resource-intensive as WSP-1A Wasp. As with the first/standard version of the Wasp IIC, the Wasp
that of the Wasp IIC was met with many questions—and even some measure IIC 2 is primarily armed with two Extended Range Medium Lasers, which are This sixth variant is primarily armed with a Series X-a Improved Heavy
of mockery by some of the other Clans. installed in the arms, although the Flamers are removed. One of the double Medium Laser installed each forearm, backed by a Series 1c Extended Range
heat sinks in the left torso is also removed, bringing the total down to ten. In Small Laser housed in the right torso. The newly-developed, “slightly more
However, the Wasp IIC quickly began to prove itself to be a worthy place of the removed heat sink, a four-tube Short Range Missile system is explosive” Improved Heavy Medium Lasers are already considerably more
opponent for most of the light BattleMechs and even some of the light installed in the left torso, fed by a single ton of ammunition housed directly accurate than the previous models, but it seems that the Raven Alliance is
OmniMechs in use by the Clans at the time. Having the right MechWarrior at next to the missile rack. (Battle Value: 934) Features the following Design taking no chances with their new Wasp IIC 6, and it features an advanced
the controls has always been a key factor with any ‘Mech. The Wasp IIC was Quirks: Easy to Maintain, Extended Torso Twist, Rugged; Exposed Actuators. Targeting Computer installed in its head to further improve accuracy.
most certainly no exception, as its great emphasis on mobility often proved
to be the Wasp IIC’s only significant advantage over many of its opponents. Wasp IIC 3 – Created by Clan Star Adder just one year after earning the right To increase this new variant’s versatility, a Light Target Acquisition Gear
to produce the Wasp IIC, the Wasp IIC 3 is a purpose-built long-range sniper, package is housed in the left torso opposite the ER Small Laser in the right.
Clan Star Adder challenged Clan Snow Raven to a Trial of Possession over based loosely on Clan Wolf’s Wasp C. The Wasp IIC 3 takes the base Wasp IIC This variant is only equipped with a total of ten double heat sinks, five of
the right to produce the Wasp IIC in 2985. The Star Adders were victorious, and removes all of the standard armament, as well as one of the left torso which are built into the powerplant, while one is housed in each leg, one in
with only a single ‘Mech still standing of the two opposing Stars of five double heat sinks, and the right hand actuator. In place of all the removed the left torso and two in the right. Despite the cooling system’s limitations
‘Mechs that had entered the battlefield. After the trial, the Snow Ravens components is a single Serie 7J Extended Range Large Laser, which takes up on paper, the Wasp IIC 6 is remarkably cool-running, and it must be pushed
relinquished their exclusive rights to the manufacturing of the ‘Mech so the entire lower right arm. (Battle Value: 906) Features the following Design to its limits to encounter any risk of overheating. As of 3085, this variant is
casually that the ranking Star Adder presiding over the trial finally bluntly Quirks: Easy to Maintain, Extended Torso Twist, Rugged; Exposed Actuators. considered by most to be the ultimate evolution of the Wasp IIC Light
Related Designs
WSP-1A Wasp – The classic, iconic BattleMech that served as the inspiration
for the Wasp IIC. Introduced in 2464 by General Mechanics, this BattleMech
is one of the best-known and most recognizable scout ‘Mechs ever produced.
Stinger IIC – Arguably based directly on the Wasp IIC 6, the Stinger IIC is one
of the Raven Alliance’s latest designs as of 3085. Unlike the original Stinger
and Wasp, the new Stinger IIC Light BattleMech is much less of a twin to the
older Wasp IIC. Although it is less expensive to produce than the Wasp IIC,
even the Stinger IIC’s designers have openly admitted that the Wasp IIC is
not only more aesthetically appealing, but arguably more capable overall.
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 1
Engine: 140 Fusion XL 2.5
Walking MP: 7
Running MP: 11
Jumping MP: 7 3.5
Heat Sinks (Double): 11 (22) 1
Gyro: Standard 2
Cockpit: Standard 3
Armor Factor (Standard): 64 4
Internal Armor
Structure Value
Head 3 6
Center Torso 6 10
Center Torso (rear) 2
R/L Torso 5 8
R/L Torso (rear) 2
R/L Arm 3 6
R/L Leg 4 7
Fielded by Clan Hell’s Horses as a front-line reconnaissance BattleMech, Beholder 2 – The first alternate variant of the Beholder was introduced in
Beholders have most often been observed operating in small groups of two 2880, just two years after the BattleMech’s introduction. The Beholder 2
or three in advance of the rest of their star—and nearly always in advance of drops the torso-mounted Electronic Countermeasures Suite and Extended
a larger combat force. A common tactic involving a single Beholder is for the Range Medium Lasers. It instead features a pair of center-torso-mounted
MechWarrior to use the BattleMech’s Target Acquisition Gear to ‘paint’ a Flamers, as well as a pair of ER Small Lasers installed in each side torso. This
single target for supporting artillery to get a positive lock with semi-guided variant has been seen used to devastating effect against unarmored infantry
munitions. After the first hit, the Beholder will then retreat and reposition to and battle-armor-equipped troops alike, while using its TAG to continuously
repeat the process. Typically, whenever a Beholder encounters an enemy designate more heavily-armored targets for artillery strikes. (Battle Value:
force that it can continuously outmaneuver, it will begin the process of 814) Features the following Design Quirks: Accurate Weapon (TAG), Compact
constantly tagging target after target for its Long Range Missile support units ‘Mech; No Ejection Mechanism.
to fire upon. This approach easily softens the enemy long before the main
body of the Hell’s Horses battle force reaches the combat zone. Beholder 3 – A slight divergence from the normal formula for this BattleMech
was introduced in 2889, designated the Beholder 3. This variant appears to
Mass: 25 tons The primary reason why a group of Beholders is preferable to a single unit be more closely based on the Fire Moth OmniMech that inspired the original
Chassis: JFS-699 Endo Steel w/Integrated CASE is that multiples of these ‘Mechs can take turns designating targets from Beholder, as well as being a mishmash of the previous two variants in terms
Power Plant: Type-56 300 Fusion XL Engine different directions for missile strikes. This cuts down on time spent between of armament. The Beholder 3 takes the original Beholder and removes the
Cruising Speed: 129.6 km/h TAG locks because one Beholder can be actively painting a target while right Extended Range Medium Laser and the Electronic Countermeasures
Maximum Speed: 194.4 km/h another repositions to avoid return fire from the enemy once it has been Suite. In place of the removed weapon an Extended Range Small Laser and a
Jump Jets: None spotted. Flamer are installed. In place of the ECM, the Beholder 3 is equipped with
Jump Capacity: 0 meters Myomer Accelerator System Circuitry, boosting the top speed of this ‘Mech
Armor: J63-2B Ferro-Fibrous Armor Capabilities to nearly 260 km/h—far outpacing the Fire Moth. However, as with the Fire
Armament & Equipment: Moth, it can only achieve this amazing top speed in relatively short bursts
2 Series 1h ER Medium Lasers A remarkably effective high-speed reconnaissance BattleMech built with without incurring an increasing risk of damaging its own leg actuators.
1 Type-21 Alpha TAG extended combined arms operations in mind, the Beholder is a ‘Mech that
1 Pattern Iota ECM Suite has aged remarkably well in the two centuries prior to its first appearances The Beholder 3’s varied armament allows it to prey upon multiple forms
Manufacturer: Clan Hell’s Horses in the Inner Sphere. Powered by a massive 300-rated ExtraLight Fusion of opponents, albeit not very effectively. Although the Beholder 3 can indeed
Primary Factory: St. Louis MechWorks; Niles (Niles I) Engine, this BattleMech is built on an extremely well-engineered Endo Steel get into position to paint targets faster than any other variant, the lack of any
Communications System: Build 1685 Tacticom Chassis. It is protected by four tons of Ferro-Fibrous Armor, with an emphasis truly significant firepower with which to defend itself, combined with the
Targeting & Tracking System: Series II Integrated TTS w/TAG on the protection of the torso, legs, and head. Compared to the rest of the sometimes unpredictable nature of the MASC, has left this variant to be
body, the arms seem almost sacrificial with how little actual armor has been considered something of a failure—a remarkably fast failure, but a failure,
Overview applied to them. The Beholder’s defenses also include enhanced electronic nonetheless. (Battle Value: 987) Features the following Design Quirks:
warfare capacity, thanks to the addition of an Electronic Countermeasures Accurate Weapon (TAG), Compact ‘Mech; No Ejection Mechanism.
When Clan Hell’s Horses unveiled the Beholder Light BattleMech in 2878, Suite installed deep in the core of the ‘Mech’s center torso.
it appeared to be an attempt to rival the recently-introduced Fire Moth Light Beholder 4 – First introduced in 2902, the fourth variant of the Beholder was
OmniMech created by Clan Ghost Bear. In reality, although the Beholder had A handful of lightly tweaked and altered variants of this scout ‘Mech have designed to operate as an enhanced reconnaissance unit. In addition to the
taken heavy inspiration from the Fire Moth—and the Fire Moth was used as been introduced in the centuries since, but the original/standard Beholder, standard head-mounted Target Acquisition Gear, it is equipped with an
something of a benchmark during the Beholder’s development—it was never introduced in 2878, remains arguably the best representation of the design. Active Probe and an Electronic Countermeasures Suite, both of which are
intended to be a rival to the more adaptable OmniMech. The Hell’s Horses’ The standard version of the Beholder features a remarkably simple offensive installed in the center torso. As a result of the emphasis on specialized
new BattleMech was initially not taken seriously by many of the other Clans, armament, with just two Extended Range Medium Lasers installed in its side electronics suites, the armament of the Beholder 4 is even more limited than
but it has since proven itself to be a very real threat on the battlefield— torsos to directly engage an opponent. However, the single most critical that of other variants. An Extended Range Small Laser is installed in each side
especially when utilized in the combined arms tactics generally favored by piece of equipment, responsible for giving the ‘Mech its name, is the Target torso, giving the Beholder 4 extremely limited defensive capability at best.
Clan Hell’s Horses. Acquisition Gear that is installed in the Beholder’s head. The TAG’s laser- (Battle Value: 722) Features the following Design Quirks: Accurate Weapon
designator evokes the appearance of a cycloptic creature that brings nothing (TAG), Compact ‘Mech; No Ejection Mechanism.
Designed to serve as both a reconnaissance ‘Mech and an artillery spotter, but death and destruction raining from the heavens upon any who fall under
there were very few other ‘Mechs available at the time that could accomplish its gaze. Beholder 5 – A Beholder variant featuring newer Gauss weapon technology
these design goals as effectively or reliably as the Beholder. This is especially was first fielded by Clan Hell’s Horses in 3073. The distinctive Beholder 5 is
true when taking into consideration the Beholder’s sheer speed, respectable Additional Information armed with a quartet of Anti-Personnel Gauss Rifles, installed in pairs in the
armor, and reasonable—albeit somewhat limited—armament. side torsos, all of which are fed by a single ton of ammunition housed in the
As of this 3085 document, the Beholder is still heavily used by Clan Hell’s center torso. Though lacking any other specialized electronics, the Beholder
Speed has always been one of the Beholder’s greatest assets, but this was Horses. It is unclear if any examples of this machine have been captured by 5 is still equipped with the head-mounted Target Acquisition Gear typical of
especially true when it was introduced. Very few other ‘Mechs could rival its other Clans or forces of the Inner Sphere, as no confirmed sightings of this this BattleMech type. (Battle Value: 681) Features the following Design
maximum groundspeed without running the risk of damaging their own ‘Mech operating outside of Clan Hell’s Horses’ Touman have been reported. Quirks: Accurate Weapon (TAG), Compact ‘Mech; No Ejection Mechanism.
actuators by using systems like the Myomer Accelerator System Circuitry Examples of this ‘Mech have been identified in operation on the current Clan
employed by the slightly faster Fire Moth. The Beholder also boasted far Hell’s Horses’ new Inner-Sphere-based homeworld of Csesztreg. Several Beholder 6 – An upgraded version of the base variant, the Beholder 6 was
superior armor protection to that of the lighter Fire Moth. The Beholder also other confirmed reports place Beholders elsewhere, being used by various first recorded in 3075. This latest variant appears to utilize more recently-
managed to be packed into a slightly more compact chassis, despite weighing other combat forces operating under the Clan Hell’s Horses banner. developed laser weapon technology to increase its brute firepower, while
Despite being approximately ten years old as of this 3085 document, this
variant of the Beholder remains relatively undocumented, with knowledge
of its existence only due to battlefield observation and collected sensor data.
Specifics behind its creation are unclear, but one thing is certain: this
machine is particularly dangerous in close quarters, and given its ability to
close distance remarkably quickly, special attention should be given to any
example of this machine on the battlefield once it has been identified.
Type: Beholder
Classification: Light BattleMech (Mass Production)
Technology Base: Clan
Tonnage: 25
Battle Value: 1,123
Notes: Features the following Design Quirks: Accurate Weapon (TAG),
Compact ‘Mech; No Ejection Mechanism. Arm Actuators: Lower & Hand
(Right & Left).
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 1.5
Engine: 300 Fusion XL 9.5
Walking MP: 12
Running MP: 18
Jumping MP: 0
Heat Sinks (Double): 10 (20) 0
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 76 4
Internal Armor
Structure Value
Head 3 9
Center Torso 8 12
Center Torso (rear) 3
R/L Torso 6 9
R/L Torso (rear) 3
R/L Arm 4 4
R/L Leg 6 10
Despite its reduced cooling capacity, the Screaming Cricket 5 runs cold.
The lock-on nature of the Streak-fire missile systems ensures every shot
counts, while the reduced total number of missile tubes results in a slower
ammunition consumption rate and impressive battlefield staying power.
These advantages have led to the Screaming Cricket 5 being considered
arguably the “best of the breed”, despite its lack of the Long Range Missiles
systems that the Screaming Cricket was originally built around and is still
largely associated with. (Battle Value: 1,882) Features the following Design
Quirks: Easy to Pilot, Nimble Jumper; Obsolete (2932-2965), Weak Legs.
Type: Likho
Classification: Medium BattleMech (Mass Production)
Technology Base: Clan
Tonnage: 45
Battle Value: 1,924
Notes: Features the following Design Quirks: Cowl, Rugged (2). Arm
Actuators: Lower (Right & Left), Hand (Right & Left—on some models).
Equipment Mass
Internal Structure: Standard w/C-CASE 4.5
Engine: 270 Fusion XL 7.5
Walking MP: 6
Running MP: 9
Jumping MP: 6 3
Heat Sinks (Double): 14 (28) 4
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 144 9
Internal Armor
Structure Value
Head 3 9
Center Torso 14 20
Center Torso (rear) 7
R/L Torso 11 16
R/L Torso (rear) 6
R/L Arm 7 14
R/L Leg 11 18
Weapons and Ammo Location Critical Tonnage
ECM Suite CT 1 1
Streak-SRM-4 RT 1 2
3 Jump Jets RT 3 –
Double Heat Sink RT 2 –
Ammo (S-SRM-4) 25 RT 1 1
Streak-SRM-4 LT 1 2
3 Jump Jets LT 3 –
Double Heat Sink LT 2 –
Ammo (S-SRM-4) 25 LT 1 1
2 ER Medium Lasers RA 2 2
2 ER Medium Lasers LA 2 2
Double Heat Sink RL 2 –
Double Heat Sink LL 2 –
Capabilities Cooled by a total of thirteen double heat sinks, with one installed in each
leg and the rest housed within the powerplant, the War Cobra 2 is capable
Mass: 55 tons The War Cobra Medium BattleMech can wreak havoc on opponents from of firing all of its weapons while maneuvering at full speed indefinitely so
Chassis: Heavie-Series MX Endo Steel w/Integrated CASE afar, providing excellent fire support and even crippling opposing ‘Mechs and long as it is not repeatedly making use of its jump jets. (Battle Value: 2,075)
Power Plant: Type-275 Fusion XL Engine vehicles shortly after initial contact has been made with a hostile force. Even Features the following Design Quirks: Modular Weapons; Difficult Ejection.
Cruising Speed: 54.0 km/h in the 31st Century, Clan Star Adder’s War Cobra is still a very respectable
Maximum Speed: 86.4 km/h BattleMech, overshadowed only by its lack of more advanced OmniMech War Cobra 3 – Introduced in 2851, this variant is a departure from the
Jump Jets: SL-175 Mod. IV technology. With decent groundspeed and respectable jump range, the War normal use of the War Cobra chassis. The War Cobra 3 surrenders all long-
Jump Capacity: 150 meters Cobra is a delight for many a medium ‘Mech pilot, especially for those who range firepower for a specific focus on short-to-medium range engagements,
Armor: Forging ZM17 Ferro-Fibrous prefer to engage their opponents at longer ranges. With its pair of Extended such as urban combat or battles in canyons and mountainous terrain. Armed
Armament & Equipment: Range Particle Projector Cannons and twin ten-tube Long Range Missile with a Streak Short Range Missile 6-rack installed in each side torso, as well
2 Type DDS “Kingston” ER PPCs systems, this medium-class BattleMech is still a potent war machine today. as a brace of six Medium Pulse Lasers—two installed in each arm and one in
2 Mk. 46 Type I LRM-10s It can inflict significant damage on a target and quickly relocate before the each side torso—the War Cobra 3 is a devastating brawler. Each of the
Manufacturer: Clan Star Adder enemy can coordinate return fire. Streak-SRM-6s are fed by a separate ton of ammunition housed in each side
Primary Factory: Dagda Industrialplex Zeta; Dagda (Dagda III) torso, giving this machine an ample ammunition supply.
Communications System: BMR2-CC With only seventeen double heat sinks, the base variant of the War Cobra
Targeting & Tracking System: XS-485 Mk. V is somewhat hindered by the potential for considerable waste heat buildup. The War Cobra 3 is equipped with a total of sixteen double heat sinks. The
This weakness often necessitates a staggered firing approach to avoid the double heat sinks not installed in the powerplant are housed within the legs
Overview risk of overheating. In a worst-case scenario, if pushed far too hard by an and side torsos, with one in each location except for the left torso, which
extremely overzealous pilot, the War Cobra can suffer problems as severe as houses two. Though not as heat efficient as the War Cobra 2, the War Cobra
In 2838, Clan Star Adder began producing the War Cobra, a new machine crippling internal ammunition explosions after as little as twenty or thirty 3 is a relatively cool-running machine, even when strained with constant
designed to serve as a front-line medium BattleMech. It was used extensively seconds of constant firing and jumping. movement and liberal use of its impressive firepower. (Battle Value: 2,497)
in defending Star Adder holdings against attacks by Clan Mongoose in the Features the following Design Quirks: Modular Weapons; Difficult Ejection.
decades leading up to the introduction of newer OmniMech technology. Although it is notably lacking in terms of any form of advanced electronics
or electronic warfare packages, the War Cobra is well-armored in addition to War Cobra 4 – Often jokingly referred to as a “Miniature Timber Wolf” in the
An exceptional and effective design for its time, the War Cobra Medium its firepower and mobility. It is sheathed in a durable shell of more than nine 31st Century, the War Cobra 4 is a powerful BattleMech that first began to
BattleMech was created using the most advanced technologies available at tons of Ferro-Fibrous Armor. see use in 2920—a full quarter-century prior to the introduction of the
the time of its introduction. The War Cobra was initially a relatively rare sight, OmniMech that inspired its modern nickname. Though considered “second
given the costliness of the ‘Mech’s construction. However, in 2844, when Additional Information rate” due to its status as a BattleMech, the War Cobra 4 is a machine that is
Clan Mongoose openly attacked Clan Star Adder, the demand for War Cobras still highly respected on the battlefield by nearly all Clan warriors.
skyrocketed all but overnight, and this machine became a common sight Used extensively by Clan Star Adder in the 29th Century, the number of
among Star Adder deployments. For two decades, the War Cobra remained War Cobras in use steadily declined by the turn of the 31st Century. Those Each arm houses twin Medium Pulse Lasers, while a Long Range Missile
a staple of Clan Star Adder’s successful battles against Clan Mongoose. still in service were mainly seen on Star Adder worlds in defensive garrison 15-rack paired with an Extended Range Medium Laser is installed in each side
forces by the 3060s, though Clan Mongoose salvaged many of them in the torso. The War Cobra 4 carries four tons of ammunition for its missile
Predictably, the downsides of liberal application of advanced technology mid-2800s—which later became property of Clan Smoke Jaguar, following systems, with two tons housed in each side torso for each launcher. Fifteen
in the construction of the War Cobra were costly construction and increased their absorption of Clan Mongoose—as did Clan Coyote. double heat sinks cool this machine, with eleven housed in the powerplant
complexity of repair. These downsides became very real problems once Clan and the other four installed in the legs and side torsos. It should be noted
Mongoose introduced their newly acquired OmniMech technology into their The fate of most of these salvaged machines is not entirely clear, though that, while the cooling system is relatively effective, it can be overwhelmed
battles against Clan Star Adder. The Mongoose OmniMechs were able to be it has become obvious that Clan Steel Viper has taken possession of a rather easily if pushed too hard for too long. (Battle Value: 2,649) Features
repaired and redeployed far more rapidly than the BattleMechs being fielded significant number of these machines over the centuries, as War Cobras have the following Design Quirks: Modular Weapons; Difficult Ejection.
by the Star Adders, leading to a failing defensive capability in battles of been reportedly used by many of their own Solahma MechWarriors.
attrition. Most of the War Cobras being fielded by Clan Star Adder were Notable Pilots
either destroyed or forfeited on the field of battle as the superior might of Variants
Clan Mongoose tore through the Star Adders’ defenses. These attacks were Star Captain Tasha Graves – War Cobra “Snakebite”: This Bloodnamed Star
made all the worse as Clan Coyote, smelling blood, initiated attacks of their War Cobra 2 – Initially created as a field refit for use against Clan Mongoose Captain was the commander of the Binary of ‘Mechs defending the world of
Star Captain Tasha Graves’ own War Cobra was the last of the defenders
to fall. She savagely destroyed four ‘Mechs by herself—killing three of the
Mongoose MechWarriors and badly wounding the fourth—before she was
slain by a concentrated barrage of combined weapons fire from an entire
Binary of Clan Mongoose ‘Mechs. This devastating assault killed Star Captain
Tasha Graves instantly, and left her War Cobra a barely recognizable, half-
melted pile of metal.
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 3
Engine: 275 Fusion XL 8
Walking MP: 5
Running MP: 8
Jumping MP: 5 2.5
Heat Sinks (Double): 17 (34) 7
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 182 9.5
Internal Armor
Structure Value
Head 3 9
Center Torso 18 26
Center Torso (rear) 9
R/L Torso 13 20
R/L Torso (rear) 6
R/L Arm 9 18
R/L Leg 13 25
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 4
Engine: 300 Fusion XL 9.5
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Double): 14 (28) 4
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Ferro-Fibrous): 231 12.5
Internal Armor
Structure Value
Head 3 9
Center Torso 23 35
Center Torso (rear) 11
R/L Torso 16 24
R/L Torso (rear) 8
R/L Arm 12 24
R/L Leg 16 32
Though once a point of pride for Clan Jade Falcon, the Ristar was used only Defined as a second-line BattleMech in the current view of the Clans, the
by aging Solahma MechWarriors by the beginning of the 31st Century, largely Ristar is unfortunately a machine that is rarely deployed in the 31st Century.
because the very OmniMech technology that the Ristar had so famously As of 3064, it is unknown how many Ristars are still in service. Speculation
helped the Jade Falcons acquire had caused this powerful BattleMech to be has placed the number to be as few as one hundred intact and functional
rendered a second-line machine only. On three occasions, during trials of examples of this venerable BattleMech remaining in operation—the majority
various types which took place via ‘Mech combat, Freeborn MechWarriors of which most are certainly in service of Clan Jade Falcon. However, a handful
piloting Ristars have defeated Trueborn MechWarriors piloting OmniMechs, of Ristars have been reported to be operating within the Toumans of Clans
such as the newer Warhawk. Rare is it that Ristars have historically fallen in Wolf, Snow Raven, and even Hell’s Horses. These examples were presumably
honorable combat without circumstances significantly aiding their foes. taken as isorla following victorious Trials during the 29th and 30th Centuries.
It is unfortunate that this great BattleMech is now so badly mistreated and Variants
disrespected by the younger generations of Clan warriors, simply because it
was created so far ahead of its time. Production of the Ristar began to slowly Ristar 2 – The second version of the Ristar Assault BattleMech, which was
Mass: 85 tons decline following the turn of the 30th Century. Although replacement parts introduced in 2858, is a remarkably simple modification to the original. The
Chassis: Falcon 85-4ES Endo Steel w/Integrated CASE continue to be manufactured to keep all the existing Ristars still in service Ristar 2 trades the Extended Range Particle Projector Cannons for Large
Power Plant: FW “FalconWing” 340 Fusion XL Engine maintained and fully operational, production of this venerable war machine Pulse Lasers, resulting in a remarkably heat-efficient and accurate machine.
Cruising Speed: 43.2 km/h discontinued altogether in 2999 with the introduction of the Warhawk It lacks the sheer brute firepower of the original Ristar, but the Ristar 2 is
Maximum Speed: 64.8 km/h OmniMech—or “Masakari”, as it has come to be called in the Inner Sphere. capable of continuous fire with its entire weapons array, even while on the
Jump Jets: JF Heavy move. Only if using its jump jets while firing every weapon at its disposal will
Jump Capacity: 120 meters Capabilities a Ristar 2 begin to slowly build up waste heat that cannot be immediately
Armor: Starforge 45A Standard Armor dissipated. (Battle Value: 2,763) Features the following Design Quirks:
Armament & Equipment: The thought of being on the receiving end of a Ristar’s fury is enough to Extended Torso Twist, Stable; No/Minimal Arms, No Ejection System.
4 Talon-5 ER PPCs cause many of even the bravest Clan MechWarriors to flinch. Due to its age
2 Series 7J ER Medium Lasers and its lack of OmniMech technology, the Ristar is often not given the respect Ristar 3 – Introduced in 2867, this variant retains the ER Medium Lasers of
Manufacturer: Clan Jade Falcon it rightfully deserves by many of today’s Trueborn Clan MechWarriors when the original Ristar, but it removes all the ER PPCs, as well as half of the double
Primary Factory: Eagle Craft Group; Ironhold (Ironhold II) off the battlefield, but it is rightly feared when encountered in combat. The heat sinks—leaving just thirteen housed within the powerplant. The Ristar 3
Communications System: Model J-C 021 Ristar Assault BattleMech is oft directly compared with the newer Warhawk is protected by 11 tons of Ferro-Fibrous Armor, resulting in slightly reduced
Targeting & Tracking System: Hawkeye 34 OmniMech that all but replaced it at the turn of the 31st Century. It can be armor protection compared to the original design. Most of the reduction in
argued that the Ristar is the more dangerous of the two, thanks to its greater armor is from the arms, as this variant of the Ristar no longer has heat sinks
Overview maneuverability and cooling capacity, though the Ristar does have flaws that in its arms to protect, and the rear center torso’s armor is lightly reinforced.
the Warhawk does not. Many warriors have criticized the Ristar over what is A combination of a Large Pulse Laser and a Gauss Rifle is installed into each
“If the genetic legacy of an Awesome and a Champion were ever to be perceived as its most significant design flaw: the decision not to install its side torso. The Ristar 3’s twin Gauss Rifles are fed by a total of four tons of
combined...” is the beginning of an old joke shared by many Trueborn Clan primary weapons in its stubby, winglet-like arms. However, the Ristar ammunition housed in the ‘Mech’s thighs.
warriors when discussing the Ristar Assault BattleMech. compensates for this issue by having an enhanced torso-twist range and a
remarkably well-engineered gyro assembly. In fashion typical of Trueborn The Ristar 3 was an attempt to create a more heat-neutral design, like that
Clan Jade Falcon learned a great deal in the 2820s while developing the Clan warriors, however, the total lack of an ejection system seems to be of the Ristar 2, while retaining more of the brute firepower that made the
Wakazashi Assault BattleMech. They also learned a great many hard lessons often overlooked entirely when discussing the Ristar’s flaws. original Ristar so noteworthy. This variant was met with some apprehension
regarding the need to create machines that are easily serviceable over the among Clan warriors, as it introduced a dependence on ammunition and still
years following the Wakazashi’s introduction. Taking these lessons to heart, The original/standard Ristar’s primary armament is its quartet of Talon-5- had a reduced peak damage potential compared to the original design, even
Khan Natalie Buhallin commissioned the creation of a new BattleMech type Series Extended Range Particle Projector Cannons, which are installed in if it did reduce the likelihood of overheating. The apprehension felt toward
in 2849. When Clan Jade Falcon later unveiled the Ristar Assault BattleMech pairs in the side torsos. Meanwhile, twin Extended Range Medium Lasers are the Ristar 3 seems to have been justified, but not for the reasons originally
in 2854, it quickly gained popularity among Jade Falcon MechWarriors. Its installed in the center torso to serve as secondary weapons. Even with a believed. During a Trial of Position within Clan Jade Falcon, a standard Ristar
blend of an intelligent design, relatively simple construction, and devastating remarkable total of twenty-six double heat sinks, the Ristar tends to run hot was pitted against a Ristar 3, and the Ristar 3 was defeated in a single salvo.
armament, as well as impressive mobility for its eighty-five-ton mass, made under most combat conditions when pushed. As with the AWS-9Q Awesome As both ‘Mechs exchanged blows, the standard Ristar managed to penetrate
this machine an easy choice for nearly any combat situation where outright that its armament so closely resembles, its ER PPCs are best used with a 4-3- both side torsos of the Ristar 3 with focused PPC-fire, critically damaging the
speed was not a high priority. The greatest irony regarding the Ristar is that 4-3 staggered firing pattern. Despite the limitations of its cooling system, the Gauss Rifles housed in its sides. Both Gauss Rifles exploded simultaneously,
its potent design and successful application in combat resulted in its own Ristar can savage even the toughest of opponents quite quickly. crippling the reactor instantly and leaving the hapless Ristar 3 pilot to do
fade from prominence into near-obscurity. nothing but ride out his incapacitated ‘Mech’s to fall to the ground, and
With its fourteen-ton shell of Starforge 45A Standard Armor, the Ristar is nearly die from a head injury—though he would have no recollection of the
In 2863, when Clan Jade Falcon challenged Clan Coyote to a Trial of not necessarily the toughest ‘Mech of its eighty-five-ton weight class, but it event whatsoever, as the simultaneous Gauss Rifle explosions knocked him
Possession for the Coyotes’ new OmniMech technology, the Jade Falcons is certainly durable. The Ristar features a very respectable groundspeed, unconscious instantly. (Battle Value: 3,094) Features the following Design
defeated the Coyotes in a battle where the Falcons had bid just a single Star courtesy of its powerful 340-rated ExtraLight Fusion Engine, and it boasts an Quirks: Extended Torso Twist, Stable; No/Minimal Arms, No Ejection System.
of five BattleMechs against double their number of Coyote machines. Among ability that most Clan assault ‘Mechs of its era did not: the ability to jump. As
the Star of BattleMechs that Clan Jade Falcon fielded, two of them were none a result, the Ristar’s 120-meter jump range initially caught out many an Notable Pilots
other than Ristar BattleMechs. Although both were destroyed before the opponent due to unfamiliarity with the design. However, the distinctively
trial’s conclusion, the Ristars had between them downed a total of six of the shaped Ristar has long since lost any such element of surprise. Star Commander Romeo – Ristar “Death’s Talon”: As brutal minded as a
Star Commander Romeo’s liberal, at times excessive use of jump jets and
constant firing of his particle cannons left him all but roasting alive inside his
overheating Ristar as he claimed his fourth kill—only to suddenly blink out
of existence as the result from an autocannon/20 shell striking the head of
his machine. His death was instantaneous, his triumphant cry of victory over
his fourth vanquished opponent suddenly cut short. His contributions in
helping to forge the might of Clan Jade Falcon lives on in the Remembrance.
Type: Ristar
Classification: Assault BattleMech (Mass Production)
Technology Base: Clan
Tonnage: 85
Battle Value: 3,421
Notes: Features the following Design Quirks: Extended Torso Twist, Stable;
No/Minimal Arms, No Ejection System. Arm Actuators: Upper Only.
Equipment Mass
Internal Structure: Endo Steel w/C-CASE 4.5
Engine: 340 Fusion XL 13.5
Walking MP: 4
Running MP: 6
Jumping MP: 4 4
Heat Sinks (Double): 26 (52) 16
Gyro: Standard 4
Cockpit: Standard 3
Armor Factor (Standard): 224 14
Internal Armor
Structure Value
Head 3 9
Center Torso 27 38
Center Torso (rear) 13
R/L Torso 18 28
R/L Torso (rear) 8
R/L Arm 14 20
R/L Leg 18 26
Star Commander Romeo created and written by Tim “Critical Rocket” with
minor edits and additions by Devin Ramsey.
Type: Oblivion
Classification: Assault BattleMech (Mass Production)
Technology Base: Clan
Tonnage: 100
Battle Value: 3,077
Notes: Features the following Design Quirks: Extended Torso Twist; Cramped
Cockpit, Poor Performance. Arm Actuators: Lower (Right & Left).
Equipment Mass
Internal Structure: Standard w/C-CASE 10
Engine: 300 Fusion XL 9.5
Walking MP: 3
Running MP: 5
Jumping MP: 0
Heat Sinks (Double): 23 (46) 13
Gyro: Standard 3
Cockpit: Standard 3
Armor Factor (Standard): 307 19.5
Internal Armor
Structure Value
Head 3 9
Center Torso 31 46
Center Torso (rear) 16
R/L Torso 21 31
R/L Torso (rear) 11
R/L Arm 17 34
R/L Leg 21 42
A handful of new and powerful technologies were employed during Operation LANCASTER in 3077. These provided the – The Dreadnought TDN System’s secondary function is an integrated compound electronic warfare suite, which has two
forces involved with different flavors of equipment in combat. Most of the rules explanations these special equipment modes: ECM and Active Probe (both have a three-hex range). These two modes cannot be active at the same time, and
types relate to the specific limitations placed on these systems to give most of them a “double-edged sword” effect. These the secondary function’s mode can be switched during the movement phase of each turn immediately before the unit is
limitations allow the new equipment types to feel unique and will hopefully help to create fun gameplay experiences. moved. Unless a unit is equipped with a separate ECM Suite, ECM is the default mode.
Dreadnought Target Data Networking (TDN) System – When a TDN System is active (required for any unit to be a part of a “Link” or for a TDN Control Unit to rearrange Links),
this system produces 2 points of heat per turn. A TDN’s secondary function does not produce any heat by itself, regardless
“So, the geeks at R&D managed to come up with something that should give us all a bit of an edge in both coordination of mode. Note: A unit equipped with a functional and active Dreadnought TDN System is automatically considered to have
and accuracy in the field. Today, we’ll begin training with this system as a unit. Yeah, that means *teamwork* will be the “Improved Communications” quirk (See “Dreadnought Spec” quirk for details).
involved—STOP MOANING, JENKINS! Oh, and before I forget to mention, this system also just so happens to have a handy
secondary feature of making our communications nigh un-jammable. Because ‘screw you and the ECM you rode in with’!” – Only a unit equipped with an active TDN System may be part of a Link. A TDN Link requires three active ‘Mechs and/or
combat vehicles (including VTOLs). A single AeroFighter may share a Link with two ground units to aid in strafing runs.
Dreadnought’s Target Data Networking System, or “TDN System” for short, was developed behind closed doors by
Dreadnought Interstellar’s best scientists and engineers working closely with the command staff of the Dreadnought – As with C3 Networks, the TDN System allows “Linked” units to share targeting telemetry and other data with one
BattleCorps 1st RCT. The intent was to create something that could “one up” the Word of Blake’s own Improved C3 another. When determining range modifiers for firing, the range to a target can be measured from whichever of the three
Networks. The new TDN System has a blend of C3 and Improved C3 Network characteristics, but it is better than either units sharing the same Link is closest to a target, regardless of which of these three is firing. This does not allow weapons
of those systems in many respects—despite its unique limitations. to fire beyond their maximum range, which is still measured from the firing unit. Minimum ranges are calculated from
the firing unit.
Microwave transmission systems are rarely used in the battlefields of the 31st Century, but in terms of communication
forms that are virtually impossible to disrupt, not many alternatives exist. Because of this, the decision was made to – If a unit that is part of an active Link shuts down, is destroyed, or suffers a critical hit to its TDN System, the Link it is a
include microwave transmission capability as one of several redundant communications formats used by the TDN System. part of is broken at the end of that turn. When a Link is broken, the units that shared this Link lose all benefits gained by
However, this does result in substantial heat generation when the system is active. the Link. The remaining units’ TDN Systems remain “active” unless otherwise declared. If a Link is broken because a unit
in that Link shut down, that Link automatically reestablishes itself at the beginning of the turn that the unit powers back
The next challenge was integration and networking. In this area, the TDN System is in part a double-edged sword, but up, so long as the other two units are still active and all three units are still assigned to the same Link.
one where its drawbacks are generally outweighed by its advantages. The TDN System functions by operating multiple
“Target Data Network Links”, referred to as “TDN Links” or simply “Links”. As the TDN System functions through a specific – To qualify as a “TDN Control Unit”, a unit must be either a ‘Mech equipped with a Command Console or a vehicle
form of sensory triangulation, each Link can only operate with three units working together at any given time—no fewer, equipped with at least 7 tons of Communications Equipment—in either case, this unit is also required to be equipped
no more. Because of the way that the system uses shared targeting telemetry from each Linked unit to triangulate a target with a TDN System. A TDN Control Unit may operate in one of two modes: “Link Mode” and “Command Mode”. A TDN
and enhance the weapons accuracy of Linked units, if one of the three units in a Link is destroyed or rendered inactive, Control Unit in “Link Mode” can manage the organization of TDN Links, allowing it to rearrange which units are Linked
the Link is broken. The unique advantage to the TDN System that outweighs this limitation is that, by using a dedicated together at the beginning of any given turn. A TDN Control Unit in “Command Mode” serves as a standard command unit,
Command Console tied to a TDN System, or a TDN-equipped command vehicle, numerous Links can be managed providing a +2 bonus to the initiative roll of the force it is a part of (standard Command Console/Command Vehicle rules
simultaneously and even reorganized in real time. This allows a commander to reassign Links as new threats appear or apply in this mode). Because a TDN Control Unit may switch to Command Mode and provide an initiative bonus at any
target priorities change, as well as to compensate for lost Linked units. point during a game, even if it does not begin the game in Command Mode, the additional standard 5% Battle Value for
the associated force must be counted when a TDN Control Unit is added to a force, regardless of a TDN Control Unit’s
The TDN System also features an integrated compound electronic warfare suite as a secondary function. This electronic mode when deployed at the beginning of a game. Note: Design Quirks such as “Command ‘Mech” are unaffected by what
warfare suite includes both a short-range Electronic Countermeasures Suite and a Light Active Probe for added flexibility mode a TDN Control Unit is operating in.
on the battlefield. This secondary function does not produce heat on its own, but the Active Probe and ECM cannot both –– Optional: If a player elects to use a TDN Control Unit in Link Mode only, and therefore deprive the TDN Control Unit
be activated simultaneously due to internal interference. Operation of these secondary functions is entirely independent from being able to switch to Command Mode, the Battle Value penalty for having a command unit does not apply, but
of the TDN’s primary networked targeting telemetry and communications functions, and it does not affect them. at no point may this unit give an initiative bonus during the game. (This is a fairly standard practice for most games.)
Special Rules: – Though it is often beneficial to have a TDN Control Unit serve as the third member of a Link, a TDN Control Unit is not
itself required to be part of an active Link at any point, and there is no negative penalty that affects a TDN Control Unit’s
OPTIONAL: If preferred—because the Nova Compound Electronic Warfare Suite (Nova CEWS) is used as a stand-in for ability to manage Links if it is not itself part of a Link.
construction and Battle Value purposes—the “simpler” standard rules for the Nova CEWS may be used instead of the
following gameplay rules. However, it should be noted that while this is a perfectly reasonable option, the Nova CEWS is – Switching a TDN Control Unit’s “Mode” must be declared at the end of a turn.
considered by many to be “overpowered”, and the TDN System has unique limitations that make it more balanced and –– Switching from “Link Mode” to “Command Mode”: When this declaration is made, a TDN Control Unit immediately
more interesting to use in gameplay (if a little more involved). While this system has lengthy rules descriptions, the TDN loses the ability to manage TDN links. This TDN Control Unit begins to provide a +2 bonus to Initiative rolls at the
System is relatively straightforward in application, and largely not dissimilar to the Nova CEWS in gameplay. beginning of the second turn following the declaration of switching to Command Mode. (One turn of neither function.)
–– Switching from “Command Mode” to “Link Mode”: When this declaration is made, a TDN Control Unit immediately
– For all intents and purposes, the Dreadnought TDN System is essentially a “nerfed” version of the Clan Nova Compound ceases providing a bonus to Initiative rolls. This TDN Control Unit may begin managing/rearranging TDN Links at the
Electronic Warfare Suite (Nova CEWS). The TDN System uses the same tonnage, critical space, and Battle Value as a Nova beginning of the third turn following the declaration of switching to Link Mode. (Two turns of neither function.)
CEWS. (1 critical, 1.5 tons, and 68 base Battle Value. Add 5% to the total Battle Value of all units equipped with this system
if there are at least 3 units with this system installed, unless the controlling player chooses beforehand to not use any – While multiple units that qualify as TDN Control Units may be deployed simultaneously in a battle force, allowing for
TDN Links during gameplay). Dreadnought TDN Systems can only be installed in either the head or a torso section of a the option of having “Backup TDN Control Units” in case one is destroyed, only one of these may operate in Link Mode at
‘Mech, in the body of a vehicle, or the fuselage of an AeroFighter. Only one TDN System can be installed in any one unit. any given point. All other TDN Control Units must operate in Command Mode. (See “Optional Rules for Advanced/Large
Note: For the purposes of most forms of construction software, simply use a Nova CEWS as a substitute for a TDN System. Force Gameplay”, under “In Larger Battles”, for multiple TDN Control Units operating in Link Mode simultaneously.)
– In larger battles, multiple allied forces employing TDN Systems may be deployed simultaneously. If this happens, it must – Disruption Effects: During the “Disruption Impact Period” of a TDN Control Unit operating in Disruption Mode, the Links
be clearly noted/declared before the beginning of the game which units each TDN Control Unit is responsible for of all Disrupted Units are locked, and they are unable to be controlled by any other TDN Control Unit. In addition, all
managing the TDN Links of. Similarly, if there happens to be one or more “Backup TDN Control Units” deployed in Disrupted Units suffer a +2 to-hit penalty for all ranged attacks for the duration of the Disruption Impact Period.
Command Mode at the beginning of the game, it must be clearly noted/declared which units that each Backup TDN Double-Blind (Optional): If the game is being played with Double-Blind rules, a player who has captured an opposing TDN
Control Unit may control the Links of if it switches to Link Mode at any point during the game. Control Unit gains an additional advantage. A player in control of a captured TDN Control Unit operating in Disruption
Example: During Operation LANCASTER, when the Dreadnought BattleCorps deployed their First, Second, and Fourth Mode can use this captured unit to see the location of all Disrupted Units. This advantage is lost at the end of the last turn
Reinforced ‘Mech Battalions, they all used identical TDN organizational patterns. Each of these reinforced battalions of the Disruption Impact Period. On a roll-result of six, however, this tracking advantage lasts for an additional (sixth) turn.
consisted of three companies of twelve ‘Mechs each, one “Support Company” of twelve combat vehicles, and a “Battle
Armor Company” with twelve APCs, each of which carried a three-man squad of battle armor. At the head of each ‘Mech – There are three ways to counter a TDN Control Unit in Disruption Mode before the end of the Disruption Impact Period.
company was a Neugen Assault OmniMech, while the Support Company was built around protecting an Omniscience –– The first option available to the affected player is the most obvious: destroy the captured TDN Control Unit. If the
Command Vehicle. (The Neugen Assault OmniMechs and Omniscience Command Vehicle all qualify as TDN Control Units.) disrupting TDN Control Unit is destroyed, the Disruption Impact Period ends at the end of that turn.
The three Neugen Assault OmniMechs of each battalion were deployed in Link Mode, with each Neugen assigned the –– The second option is to retake the unit from the capturing player. As with destroying the TDN Control Unit, the
responsibility of only controlling the TDN Links of all the ‘Mechs in its own company (including itself). Meanwhile, the Disruption Impact Period ends at the end of the turn that the unit is recaptured by allied/friendly forces.
battalion’s sole Omniscience Command Vehicle served as a Backup TDN Control Unit for the entire battalion. The –– The third option is an all-or-nothing choice. The player in control of the negatively-impacted force can trigger a
Omniscience Command Vehicle was deployed in Command Mode, benefitting the initiative of the entire reinforced failsafe lockout protocol that will disable the affected TDN Systems. However, this affects not only the Disrupted Units,
battalion. (As the only unit in the Support Company that qualifies as a TDN Control Unit was deployed in Command Mode, but all units that could, under any circumstances, have their TDN Links be under the control of the TDN Control Unit
this means that all the vehicles in the Support Company had their Links preset to Link each lance of three vehicles together that has been captured. Note: This has no impact on TDN System secondary functions (Active Probe/ECM), which may
by default, and the Support Company’s Links could not be manipulated unless the Omniscience Command Vehicle switched continue to operate as normal for the rest of the game.
to Link Mode.) In the event that any of the Neugens were destroyed, leaving their companies without TDN Control Units, ––– This choice must be declared at the beginning of a turn (including the turn immediately after the TDN Control
the Omniscience could switch to Link Mode and take control TDN Links of any remaining ‘Mechs in those companies. If all Unit was captured), before the movement phase, and the declaration cannot be withdrawn after any unit has moved.
three Neugens were disabled or destroyed, the Omniscience Command Vehicle could take control over control of the TDN ––– All units that are affected by this declaration but are not “Disrupted Units” immediately deactivate their TDN
Links of the entire battalion simultaneously. Systems and may not join another Link for the rest of the game.
To represent this in gameplay, each of the battalion’s three Neugen Assault OmniMechs would be declared as being ––– At the end of the turn that the declaration is made, the controlling player must roll 1D6 for each Disrupted Unit.
deployed in Link Mode at the beginning of the game, and each stated to have the responsibility of controlling the Links of For each roll, add 2 to the result and compare to the unit’s piloting skill.
the ‘Mechs in its associated Company only. Meanwhile, the battalion’s Omniscience Command Vehicle would be declared ––– If the adjusted roll result is equal to or greater than the unit’s piloting skill, the TDN System for that unit is
as being deployed in Command Mode at the beginning of the game, with the stated ability to take control of the TDN Links immediately deactivated, freeing the unit from the negative effects of the Disruption Impact Period. Because this
of any/all units in the entire battalion if it switches to Link Mode at any point during the game. breaks the Link that this unit was connected to, the other two members of the same Link are automatically also
successfully freed. None of these units may joint another Link for the rest of the game.
– TDN Links can only be disrupted by a TDN Control Unit operating in what is known as “Disruption Mode”. In gameplay, ––– If the adjusted roll result is less than the unit’s piloting skill, the attempt fails for this unit, and if neither of the
this happens if a TDN Control Unit has been captured (or a scenario planned by the Game Master causes a TDN Control other two units that are Linked to this unit succeed, this unit continues to be affected by the Disruption Impact
Unit to fall under the control of an opposing player—or the Game Master). A captured TDN Control Unit can be switched Period. Repeat the attempt for this unit at the end of each following turn until successful or the end of the Disruption
to Disruption Mode at the end of the turn that the unit is captured. Once the switch is declared, the “Disruption Impact Impact Period, at which point the TDN Systems for all remaining Disrupted Units are successfully deactivated.
Period” starts at the beginning of the following turn, immediately affecting all “Disrupted Units”.
–– Optional: A die-roll with a difficulty set by the Game Master or agreed upon by the players may be used to determine
if the capturing player successfully switches the captured TDN Control Unit to Disruption Mode (Default 8+ on 2D6). Experimental Clan Extended Range Particle Projector Cannon Capacitor (X/C-ERPPC Capacitor)
– “Disrupted Unit”: This is a unit that is negatively affected by a TDN Control Unit operating in “Disruption Mode”. “This shiny little gizmo comes ‘courtesy’ of the Word of Blake. Don’t worry, we thanked them appropriately. Took a bit
–– If the captured TDN Control Unit was operating in Link Mode at the time of capture, a “Disrupted Unit” is a unit that of effort to get the ‘Blake’s Blood’ washed off, but it seems to work just about right, now.”
was a part of an active TDN Link under the control of the TDN Control Unit in question during the turn that the TDN
Control Unit was captured. These specially-created PPC Capacitors were created by the Word of Blake to augment Clan-tech Extended Range
–– If the captured TDN Control Unit was operating in Command Mode (such as a Backup TDN Control Unit) at the time Particle Projector Cannons. The first known examples of this specialized equipment were used by the 55th Shadow
– In the event of an X/C-ERPPC Capacitor malfunction, roll 1D6 to determine how severe the malfunction is: Special Rules:
–– On a result of 1-2, the Experimental PPC Capacitor explodes, destroying the Clan ER PPC in the process.
–– On a result of 3-4, the Experimental PPC Capacitor burns out, destroying the Clan ER PPC in the process. – Treat this weapon as a standard Clan Rotary Autocannon/5 for construction and gameplay purposes, with two notable
–– On a result of 5-6, the Experimental PPC Capacitor burns out, but the Clan ER PPC itself remains unaffected and may exceptions in gameplay: The Spin-Werx Type A10 Rotary-5 Autocannon can only fire a maximum of five shots per turn,
fire again normally after this turn. rather than six, and this weapon gains a +1 bonus on the cluster-hit table when firing 1-4 shots (no bonus when firing 5).
– If an X/C-ERPPC Capacitor explodes due to malfunction or it suffers a critical hit when charged, treat it as a 5-point CASE-
equipped internal ammunition explosion. If the X/C-ERPPC Capacitor is destroyed because of a critical hit, its associated
PPC is disabled until it can be repaired.
“You know that really, really fancy Clan missile system that you guys managed bring back from Pantheress that we just
finished installing the tooling needed to manufacture? Well, apparently Foyt got drunk last night and stuffed some bits
from a Streak launcher into it and uh... Well… The damned thing works! You guys really need to see this thing!”
Thanks to years of dealings with Clan Diamond Shark during the Dreadnought BattleCorps’ rather lengthy stay in Clan
Space, when the BattleCorps returned to the Inner Sphere they brought back with them all that was required to replicate
the 9- and 12-tube Advanced Tactical Missile systems. Following the BattleCorps return, Dreadnought Interstellar
Industries’ top scientists and engineers built upon a rather striking idea to enhance the weapon system—an idea that was
originally presented by some of the former Clan Smoke Jaguar scientists who were brought back with the BattleCorps.
The weapon’s original fire control system (which was roughly the equivalent of an Artemis IV Fire Control System as
standard) was replaced with a Streak-type lock-on system. It took time to research and develop the upgrade, but once
the method for adapting the Streak-type fire control system was discovered, implementation was almost overnight. The Decoy/Electronic Warfare Missile (DEWM) System
upgraded missile system was rolled out just in time to be included in the design of the Sumaire and Neugen Assault
OmniMechs from the beginning of their production in 3070. It was only discovered in the first live-fire exercises involving “‘Decoy/Electronic Warfare Missile’ System. ‘DEWM’ System… Seriously? You just wanted to be able to say you created
these ‘Mechs that the upgraded missile system had the additional benefit of being able to fire its missiles at a target something called the ‘Doom System’, didn’t you?”
indirectly—something that Dreadnought’s scientists and engineers had not intended but were happy to take credit for.
The DEWM System was under development when Operation LANCASTER took place, and it was completed too late to
Special Rules: see deployment during the campaign on Ashkum IV. Introduced in 3078, the DEWM System builds upon the Improved
NARC beacon launcher developed by the Word of Blake to utilize an all new missile developed by Dreadnought Interstellar
– Only available in 9-rack and 12-rack launchers (no 3-rack or 6-rack Streak-ATM launchers exist as of 3085). Industries: The Decoy/Electronic Warfare Missile (DEWM). A DEWM is dual-purpose, nondestructive missile. It is primarily
used as a decoy to confuse enemy targeting systems at long range, creating the appearance of another fighter or small
– Treat as Improved Advanced Tactical Missile systems in both gameplay and construction rules with the exception that craft on sensors. It also has a secondary function that can use the same decoy systems to clear areas of Space Mines by
they cannot use Improved Magnetic Pulse or Improved Inferno Warhead ammunition types. drawing attention to itself and triggering the mines to become hostile toward it.
As of 3085, the DEWM System is bespoke to the Dreadnought BattleCorps and DefenseCorps, though it is unlikely to
Spin-Werx Type A10 Rotary-5 Autocannon remain that way for long. Copying the technology has proven difficult, as no examples of a DEWM has ever been captured
intact. While not an offensive weapon, DEWMs are equipped with an explosive self-destruct systems that automatically
“Remember, nuggets: Your gun goes ‘pew-pew’, but my gun goes ‘BRRRRRRT!’” triggers once they have been identified by hostile forces as a decoy or have somehow missed a target minefield.
The Type A10 is the only Clan-tech-enhanced autocannon produced entirely in-house by Dreadnought Interstellar Special Rules:
Industries. A devastating weapon system, the Spin-Werx Type A10 Rotary-5 Autocannon is an upgraded version of the
Mydron units developed by the Federated Commonwealth in 3062. Dreadnought developed the Type A10 for use by their – DEWMs are wireless guided, nondestructive missiles that carry an advanced electronic warfare suite. These are
– A DEWM in “Minesweeper Mode” is fired like a conventional missile and has a maximum range of 20 hexes. During the
Movement Phase, a DEWM deployed in Minesweeper Mode will travel to a hex designated by the controlling player and Wing-Mounted Weapons
may be fired upon during the attack phase. It must end its movement in a hex occupied by Space Mines or in a hex
adjacent to one or more hexes occupied by Space Mines to be effective, and it will simply self-destruct at the end of the This negative quirk can only be applied to ‘Mechs equipped with a Partial Wing. If a critical hit is scored against the
turn anyway if for whatever reason it does not. If it survives until the end of the turn, all Space Mines in the same hex and Partial Wing of a unit with this quirk, and there is a weapon system in the same side torso location as the Partial Wing
any adjacent hexes will detonate at the end of the turn, and the DEWM/Minesweeper itself is destroyed in the process. critical that has been hit, roll 2D6. On a result of 11-12, the weapon takes a critical hit as well. If there are multiple weapons
in this section, the weapon with the highest damage potential in a single shot receives the critical hit first. This process is
– If fired upon, a DEWM has no special defensive modifiers. It only has normal defensive modifiers (movement, range, repeated if the Partial Wing suffers another critical hit unless no more weapons remain in that same location. Note: This
etc.). A successful hit that deals one or more points of damage will destroy the DEWM. applies to weapons only. It does not affect ammunition or any other systems/components.
Body Suits / Combat Kits: DII-Mi Mk 2.1 BA-Class Mimetic Armor Hover:
Dreadnought Dura-Frame / Dura-Frame II Standard Chassis
DAPSK / DAPS Kit (Dreadnought Armored Pilot Suit Kit) Dreadnought ExoShield Ferro-Fibrous Vector Endurance High Performance Hovercraft (All)
DEMICK / DEMIC Kit (Dreadnought Elite Marine Infantry Combat Kit) Dreadnought Mark 41 Vehicular Stealth Armor Fire Hunter Firefighting Vehicle (All)
Dreadnought Titan-Plate Standard Armor
Weapons:
Orbital Heavy Industries Sphere Spec Endo Steel Tracked:
Liberator Mk VI Laser Pistol Orbital Heavy Industries Special Type-C Endo Steel (Clan-Tech)
PAARR-15/GL Infantry Assault System Orbital Heavy Industries OHI-X Superheavy Spec-C Endo Steel (Clan-Tech) Sprinter Light Tank (All)
Orbital Heavy Industries Special Type-C Ferro-Aluminium (Clan-Tech) Marathon Medium Tank (All)
HEAVY WEAPONS: StealthyDread BA-Type-4 Stealth Armor Quake Tank Destroyer (All)
Unidentified BA-Type Improved Stealth Armor (Clan-Tech) Kodiak Heavy Tank (All)
Ballistic: Fusillade Flak Tank (All)
POWERPLANTS: Sledgehammer Artillery Vehicle (All)
Magna-Rail-15 Gauss Rifle (Clan-Tech) Triton Repair Vehicle (All)
Series-II Anti-Personnel Gauss Rifle (Clan-Tech; Reproduction, 3086+) Fuel Cell Engines:
Spin-Werx Type A10 Rotary-5 Autocannon* Wheeled:
Dreadnought Interstellar Industries DII-10(FC)
Energy: Dreadnought Interstellar Industries DII-45(FC) Vector Storm High Performance Motorcycle (All)
Dreadnought Interstellar Industries DII-300(FC) Successor DS9 Armored Supercar (All)
Short-Beam IV Extended Range Small Laser (Clan-Tech)
Foundation Utility Truck (All)
Flash-Sword VII Extended Range Medium Laser (Clan-Tech)
Fusion Engines: Streaker Recon Buggy (All)
Sniper-Blazer IX Extended Range Large Laser (Clan-Tech)
Cobra Patrol Vehicle (All)
Laserwerks Strobe Type 1 Micro Pulse Laser (Clan-Tech)
Orbital Heavy Industries OHI-10F-Series (Various Outputs/Sizes) Omniscience Command Vehicle (All)
Laserwerks Strobe Type 2 Extended Range Small Pulse Laser (Clan-Tech)
Orbital Heavy Industries OHI-10F/SC (Supercharged) Oxen Heavy Hauler (All)
Laserwerks Strobe Type 7 Medium Pulse Laser (Clan-Tech)
Orbital Heavy Industries OHI-44F
Laserwerks Strobe Type 9 Large Pulse Laser (Clan-Tech)
Orbital Heavy Industries OHI-50F VTOL/Helicopter:
Scorched-Earth Type 2 Flamer (Clan-Tech)
Orbital Heavy Industries OHI-60F
Thunderstruck XV Extended Range Particle Projector Cannon (Clan-Tech)
Orbital Heavy Industries OHI-165F Albatross Light Attack VTOL (All)
Orbital Heavy Industries OHI-200F
Missile:
Orbital Heavy Industries OHI-210F SMALL CRAFT:
Decoy/Electronic Warfare Missile (DEWM) System* Orbital Heavy Industries OHI-255F
OmniBow Streak Advanced Tactical Missile 9-Rack* Orbital Heavy Industries OHI-275F Skua Recovery Craft (All)
OmniBow Streak Advanced Tactical Missile 12-Rack* Orbital Heavy Industries OHI-285F
Note: Components manufactured by
Reacher-Series Long Range Missile 10-Rack (Clan-Tech) Orbital Heavy Industries OHI-300F DROPSHUTTLES / DROPSHIPS:
Orbital Heavy Industries are listed
Reacher-Series Long Range Missile 15-Rack (Clan-Tech) due to their partnership with and
Double-Take Version 3 Short Range Missile 2-Rack (Clan-Tech) ExtraLight Fusion Engines: Abeona-class DropShuttle / DropShip (All)
technology/materials supplied by
Quad-Shot Version 3 Short Range Missile 4-Rack (Clan-Tech) Borealis-class DropShip (All)
Dreadnought Interstellar Industries to
Six-Shooter Version 3 Short Range Missile 6-Rack (Clan-Tech) Orbital Heavy Industries OHI-65XL
manufacture Clan-tech components.
PosiLock-IV Streak Short Range Missile 4-Rack (Clan-Tech) Orbital Heavy Industries OHI-75XL JUMPSHIPS:
PosiLock-VI Streak Short Range Missile 6-Rack (Clan-Tech) Orbital Heavy Industries OHI-165XL
Orbital Heavy Industries OHI-175XL Mammoth-class Colonial JumpShip (All)
ELECTRONICS AND SPECIALIZED EQUIPMENT: Orbital Heavy Industries OHI-210XL Mammoth II-class JumpShip (All)
Orbital Heavy Industries OHI-220XL
DreadTech MiniFus Type 132 Power Pack Orbital Heavy Industries OHI-225XL WARSHIPS:
EW-Special Mk-IV Angel Electronic Countermeasures Suite Orbital Heavy Industries OHI-255XL
Compound-Sense Type-43-C Active Probe (Clan-Tech) Orbital Heavy Industries OHI-325XL Jackal-class Destroyer (All)
Compound-Sense Type-49-F Light Active Probe (Clan-Tech) Orbital Heavy Industries OHI-180XLC (Clan-Tech) Dreadnought-class Battleship (All)
Dreadnought BC Special Mk-II Target Data Networking (TDN) System* Orbital Heavy Industries OHI-240XLC (Clan-Tech) Firebrand-class Battleship (All)
Pinpoint-series Targeting & Tracking Systems (incl. “VariTrac” models) Orbital Heavy Industries OHI-275XLC (Clan-Tech)
Enhanced Pinpoint Version-V Targeting Computer (Clan-Tech) Orbital Heavy Industries OHI-280XLC (Clan-Tech) SATELLITES & SPACE STATIONS:
Bug-Zapper IX Laser Anti-Missile System (Clan-Tech) Orbital Heavy Industries OHI-300XLC (Clan-Tech)
Laz-Spotter IV Light Target Acquisition Gear (Clan-Tech) Orbital Heavy Industries OHI-320XLC (Clan-Tech) Clairvoyance Type-V Tactical Satellite
SmarTrac Artemis IV Fire Control System (Clan-Tech) Orbital Heavy Industries OHI-325XLC (Clan-Tech) Precognition Type-VII Tactical Satellite
Kangaroo-series Jump Jets Orbital Heavy Industries OHI-340XLC (Clan-Tech) Orbital Defense & Refit Platform (ODRP)
Interconn-Comm-series Communications Systems Orbital Heavy Industries OHI-350XLC (Clan-Tech) (Includes Supercharged)
Pinpoint Series Targeting & Tracking Systems Orbital Heavy Industries OHI-380XLC (Clan-Tech) * See Special Dreadnought / Lancaster Specific Rules (Pages 428-431)
Crossplane VTG-9 w/Integrated CASE (Vertigo DII-VTG-AS-BC1, -BC2, -X1) VXBA Generation 1 Light (Vixen Light Battle Armor; All)
Winged-Fang Series 12 SBT-AS w/Integrated CASE (Sabretooth DII-SBT-AS-BC1, -BC2, -Y1, -Y2, -Y3) VXBA Generation 2 Light (Vixen II Light Battle Armor; All – Likely to begin production in 3087)
Viper Flyer Version 39-Delta w/CASE-II (Steel Cobra DII-SCB-AS-BC1, -BC2, -BC3, -X1, -X2) KSBA Generation 1 Medium (Kitsune Medium Battle Armor; All)
J.S. Space Superiority Firestar w/CASE-II (Firestar DII-FST-AS-BC1) KSBA Generation 2 Medium (Kitsune II Medium Battle Armor; All – Likely to begin production in 3087)
Ceòlmhor Heavy Battle Armor (Reproduction design designated “DII-CLM-BA-1” – Scheduled to begin production in 3086)
BATTLEMECH / OMNIMECH CHASSIS: BWBA Type 3 AssaulTrooper (Breakwater Assault Battle Armor; All)
Standard:
Endo Steel:
Orbital Heavy Industries Experimental Superheavy Spec-C BHM-III-190/283ESC Endo Steel w/CASE-II (Behemoth III DII-BHM-3-BC1, -BC2(X))
Orbital Heavy Industries Special Type-C QUN-20/33ESC Endo Steel w/Integrated CASE (Quenn DII-QUN-O (OmniMech); All)
Orbital Heavy Industries Special Type-C RVG-25/43ESC Endo Steel w/Integrated CASE (Ravage DII-RVG-O (OmniMech); All)
Orbital Heavy Industries Special Type-C RVG-2-30/51ESC Endo Steel w/Integrated CASE (Ravage II DII-RVG-2-O (OmniMech); All)
Orbital Heavy Industries Special Type-C DGS-50/83ESC Endo Steel w/Integrated CASE (Dorgas DII-DGS-O (OmniMech); All)
Orbital Heavy Industries Special Type-C TYR-50/83ESC Endo Steel w/Integrated CASE (Tyrant DII-TYR-BC1, -BC2, -BC3, -BC4)
Orbital Heavy Industries Special Type-C CRR-55/91ESC Endo Steel w/Integrated CASE (Crusher DII-CRS-O (OmniMech); All)
Orbital Heavy Industries Special Type-C OX-60/99ESC Endo Steel w/Integrated CASE (Oryx DII-OX-BC1(X), -BC2, -BC3)
Orbital Heavy Industries Special Type-C HMD-65/104ESC Endo Steel w/Integrated CASE (Hammerhai DII-HMD-BC1, -BC2)
Orbital Heavy Industries Special Type-C GMN-70/107ESC Endo Steel w/Integrated CASE (Gemini DII-GMN-O (OmniMech); All)
Orbital Heavy Industries Special Type-C LNR-70/107ESC Endo Steel w/Integrated CASE (Lancer DII-LNR-BC1, -BC2, -SVII)
Orbital Heavy Industries Special Type-C EPR-80/122ESC Endo Steel w/Integrated CASE (Emancipator DII-EPR-BC1, -BC2, -BC3(X))
Orbital Heavy Industries Special Type-C RCK-85/130ESC Endo Steel w/CASE-II (Reckoning DII-RCK-BC1)
Orbital Heavy Industries Special Type-C SMR-95/145ESC Endo Steel w/Integrated CASE (Sumaire DII-SMR-O (OmniMech); All)
Acala III is known to most as the “Dreadnought Homeworld”, though it has more recently become the centerpiece of the Acala Semi-Autonomous Region (ASAR). In addition to its human population
and associated military forces, this planet is home to numerous and diverse forms of wildlife, ranging from the microbial to the massive. While many of Acala III’s indigenous life forms broadly
resemble the variety that can be observed on Terra, albeit with evolutionary differences, the following entries are sufficiently unique to this world to warrant special recognition—and caution.
433 – Operation Lancaster – A BattleTech Fan Project Led by Devin Ramsey
ACAROC (ACALAN ROC)
Classification: Colossal Avian the ability to cut through even the dense hide of a massive gaatee with
Homeworld: Acala III impressive ease, using its beak to smash and cut through so that it may bite
Environment: Adaptable, preference to subtropical regions away large chunks of meat. To prevent brain injury from smashing its prey
Average Mass: 4,100 kilograms with its head, the internal structure of its skull is much like that of a Terran
Average Length: 1,225 centimeters Woodpecker, just on a much larger scale, with a spongey impact absorbing
Average Height: 475 centimeters layer between the brain and the interior surface of the skull.
Average Lifespan: 120 standard years
The feathered back an acaroc’s body is wildly colorful, with beautiful
arrangements of ornate coloration all over its back and the outsides of its
wings. In sharp contrast, an acaroc’s underbelly, legs, and inner wings have
a dull coloration that is a mixture of sky blue and cloud-gray, creating a
natural camouflage when viewed from the ground in most weather
conditions. It has been observed during different seasons that an acaroc’s
underbelly feathers can shift between higher concentrations of blue and
different shades of gray.
Acarocs mate for life. Once they have, both the male and female will gain
a stronger red coloration in the feathers of their outer wings, marking them
as mated and warning off any other of their species. Though they mate for
life, they reproduce rarely. A female typically produces between three and
seven offspring every fifteen to twenty-five years. The parents will often
spend several years with their offspring, and it is notable that this is generally
the only time that acarocs will live and hunt in groups larger than two. While
raising their young, they become even more severely territorial, becoming
far more aggressive than normal. This has led to birth rates of acarocs being
studied heavily to keep track of the most dangerous areas of Acala III.
An acaroc that has lost its mate and has no offspring under its care is
generally quite easy to spot, as the normally bright colors of its wings and
back will quickly lose their vibrance, eventually fading to a near-grayscale
coloration over several years before the acaroc simply dies in its sleep.
While it was predicted that human settlement of the planet would result
in a decline in the population of gaatee on Acala III, the overall population of
the giant reptiles appears to be coping remarkably well, showing next-to-no
significant change in number. Each of the three attempts to eradicate or
reduce the gaatee population has only resulted in a temporary spike in the
population instead. Scientists have yet to explain this phenomenon.
Classification: Colossal Reptile
Homeworld: Acala III These giant predators are extremely aggressive in nature and are very Note: BattleCam footage of the first encounter between a gaatee and a
Environment: Variable (Preference to warmer climates) territorial. They will attack anything and anyone that encroaches on what BattleMech was used in the creation of the “Gaatee Encounter Experience”
Average Mass: 12,200 kilograms they perceive as their territory. Gaatee typically mate for life, though not at the gaatee exhibit of the Acala III Planetary Natural History Museum in
Average Length: 800/1,900 centimeters (Head and body/Overall) always, and they have been known to hunt in familial packs, though such New Sydney. This “Experience” is a simulated recreation of the first encounter
Average Height: 540 centimeters hunting groups are rare. A female gaatee will typically lay between forty and with a gaatee that a WSP-1 Wasp BattleMech was unfortunate enough to
Average Lifespan: 22 standard years seventy eggs at a time. A gaatee can live up to sixty standard years, although endure in 2483. Also on display are the remains of the ‘Mech’s hyperextended
most newborns are killed and eaten by acarocs or other gaatee before and partially-crushed right leg as a result of being struck by the gaatee’s tail;
Gaatee are the largest reptilian life forms on the world of Acala III. The reaching one year of age. Acarocs are the bane of a gaatee’s existence from as well as the right arm that was bitten by the massive creature, its teeth
name “Gaatee”—pronounced “Gah-Tee”—literally stands for “Gigantic birth until death. In addition to killing off the majority of newborn gaatee, perforating the arm and mangling the Medium Laser beyond recognition.
Armored Alligator That Eats Everything”. The massive quadrupedal reptiles the massive avians are known for attacking and killing even adult gaatee for
on average weigh more than twelve tons, but they have been known to food. While an adult gaatee can kill an acaroc in a one-on-one fight, acarocs Note: In addition to their remarkably durable hide and dense skeletal
weigh nearly fourteen. As their name’s acronym suggests, the gaatee have a generally attack in groups and overwhelm the gaatee. Many gaatee are also structure, gaatee have binary cardiovascular systems, a redundant nervous
remarkably thick, naturally armored scaly hide. They can survive direct hits killed each year by flights of Acalan dragons as the smaller flying reptiles system, and redundant internal organs, as well as the ability to regrow entire
from even weapons as powerful as ‘Mech-class Particle Projector Cannons. defend their homes from individual and familial packs of gaatee searching limbs and organs at an impressive rate. This combination makes them
An adult gaatee may even interpret such a hit as a territorial challenge. for food. extremely difficult to kill.
Several distinctions separate the Acalan dragon from being confused with
the Branth. The most obvious is their size, as the Acalan dragons only grow
to a fraction the size of the massive Branth. Acalan dragons differ in physical
appearance as well, as they have arms and legs, as well as hands complete
with opposable thumbs, while the Branth only have two legs. The Acalan
dragon’s fangs can secrete a form of venom that, while not lethal in small
doses, can leave the recipient temporarily paralyzed and completely numb
for multiple hours at a time. However, the larger the dose, the greater the
likelihood of stopping the recipient’s heart. A dragon is also capable of
spitting a moderately corrosive acid that can blind a human almost instantly,
and permanently, if truly enraged or forced to defend itself. Acala III’s native
flying reptile is also far more intelligent than the Branth, thanks to primarily
to a much larger and somewhat uniquely evolved cerebral cortex. The Acalan
dragon is so intelligent that early encounters left settlers believing that they
might have discovered the very first truly sentient extraterrestrial life form.
While dragons do not have any kind of discernible spoken language much
above those observed in the highest forms of terrestrial wildlife, the range
of sounds they can make is impressive. Their social interactions are noted to
be remarkably complex, and though their scales can be any number of wild
colors and exotic patterns, they do not appear to judge each other based on
this. In many ways, Acalan dragons are like the wolves of Terra. They move
in groups and tend to their own. They occasionally have territorial disputes
with other groups, and some groups will instead elect to merge with other
groups peacefully. These groups have become known simply as “flights”. A
flight of dragons can range anywhere from ten to more than fifty in number,
with the largest recorded flight numbering fifty-six in the year 2978.
A platoon of anti-’Mech infantry armed with short range missile launchers quickly moved up to her position from a
nearby tree line to give some additional suppressing fire against the Mad Cat and provide her some cover while she
worked to get to her feet. Even as they took up firing positions in front of her struggling Catapult, another Jade Falcon
Plain of Curtains machine crested the hill. Her tactical computer tagged the new arrival as a sixty-five-ton Loki OmniMech. The Loki was a
Twycross (Twycross III) little over three hundred meters away and just barely out of range for the infantry’s missiles.
15 September, 3050
Shandra felt her heart start to race as panic began to set in. While her own ‘Mech was a match for the Loki in terms of
weight, her Catapult was in poor condition and the superior Clan machine looked to be in far better shape. The humanoid-
“...Jaeger is dow...” shaped Loki watched Shandra as though bemused as she tried more cautiously to stand up.
“…all back...” The infantry opened fire on the closer Mad Cat. The short range missiles fired by the infantry at the Mad Cat only mildly
peppered their target. Shandra knew that if she gave up ground and allowed the Loki to advance, the infantry that had
“…ad Cat is still...” rushed up to help her would be torn apart by the Loki’s antipersonnel pods. She had seen footage of the weapons in
action during her briefing before her current deployment and knew how horrific the weapons were.
“…my leg is fu...”
Her heart skipped a beat when the Loki began to move toward her as though hearing her thoughts.
Shandra faintly heard the voices over her radio before a loud explosion nearby disrupted the comforting peace that
had settled over her. In its place her head began to ache. She felt a warm stickiness running down her nose and tasted Finally getting her ‘Mech up onto one reverse-canted knee, her attention was drawn to a bright flash of intense
blood on her lips. As she opened her eyes, she discovered that the visor of her neurohelmet was cracked. Flames licked weapons fire between the Marauder and Mad Cat. She looked over just in time to see both the Mad Cat and the Marauder
at the right edge of her Catapult’s broken canopy as she finally comprehended that she had lost consciousness. simultaneously collapse, smoke and flames pouring from around the cockpits of both ‘Mechs. Her heart cried out for her
longtime friend in the Marauder but there was nothing she could do. She had to defend the nearby infantry.
She knew she was probably concussed. With that in mind, Shandra quickly poured through her most recent memories
in search of gaps. Leftenant Shandra Jaeger of the 10th Lyran Guards had been providing close fire support for her Managing to get her Catapult onto its feet at last, she immediately unleashed her quartet of medium lasers at the Loki.
company commander’s Zeus during a hasty retreat when her Catapult had been broadsided by a Clan Jade Falcon Mad The Clan war machine shrugged off the damage and returned fire with its own short-range missiles and more powerful
Cat that seemed to appear out of nowhere. Finding herself faced with a heavier machine toting vastly superior technology lasers, forcing her to work hard to remain standing as the damaged gyro protested loudly from within the Catapult’s belly.
and firepower, she was convinced that she was going to die in that moment.
With her heads-up display gone and her targeting reticule with it, her only hope was to hold as steady as she could,
She fired everything she had. The Mad Cat barely seemed to take notice. In response, she was struck so heavily by the keeping the Loki roughly centered in front of her as a tone in her helmet indicated that her long-range missiles had begun
Clanner’s return fire that her ‘Mech pitched back and slammed to the ground. The heavily reinforced ferroglass canopy locking on to the enemy ‘Mech. As her already battered Catapult began to cave in around her, alarms screeched
protecting the Catapult’s cockpit had exploded inwards and the next thing she knew she had awakened in her current desperately for her attention. The missile lock tone stopped as a large warning message suddenly popped up on a
state. She was indeed almost certainly lightly concussed, but after checking to make sure all her fingers and toes were secondary monitor: “LRM Fire Control Malfunction”. Her long-range missiles, her primary weapons, were gone.
still working, she was satisfied that she could still fight.
The infantry let loose a wave of their missiles at the Loki as it closed to less than two hundred meters away. The Loki
Taking in her surroundings, she pieced together that her ‘Mech had slid down a steep slope after the fall. The sliding continued to pummel the Catapult mercilessly, seemingly ignoring the infantry. Warnings on a status display indicating
‘Mech had left gouges in the hill and uprooted a couple of smaller trees in the process. The Catapult had finally scraped breached armor over her left leg illuminated before another warning that the leg’s lower actuator had ceased responding.
to a halt at the bottom of a ravine on its back. As she gathered herself Shandra discovered that the Mad Cat had begun More failure notifications popped up on other monitors as virtually every display turned red, many of them flashing.
to engage the company commander’s crippled 80-ton Zeus Assault BattleMech at the top of the hill. Shandra struggled
to understand the Clan rules of engagement, but with the damage to the Catapult’s head and her lack of movement, the Shandra was forced to backpedal two shaky steps, fighting for control over her ‘Mech as the entire right side of the
pilot of the Mad Cat must have thought her vanquished and moved on to another target. With the Mad Cat still fighting Catapult’s torso was ripped apart under hits from the Loki’s particle cannons. The high-mounted, boxy missile launcher
her company commander at the top of the hill, it was likely that she had only been unconscious for less than a minute. of an arm on that side fell to the ground uselessly. The status lights for her right-side medium lasers turned red. The Loki
stormed forward and closed to point-blank range in what seemed like the blink of an eye even as she struggled to cope
A quick glance around the cockpit revealed that the Catapult had gone into a standby mode after having initiated an with the punishment it inflicted upon her. Metallic dust-clouds exploded from the sides of the Loki’s legs as it stormed
automatic shutdown to prevent damage from overheating. Being knocked out immediately after firing all of her weapons through the infantry and her heart sank in an instant. As her ‘Mech’s torso pitched and she was forced back an additional
had prevented her from overriding the safety protocols to keep the ‘Mech online. She quickly keyed in the restart unsteady step under the barrage from the Loki, her view was forced down just in time for her to bear witness as the
command, feeling more confident about her condition as she remembered the command without issue. Shandra was shrapnel from the explosive antipersonnel pods on the Loki’s legs tore the infantry to ribbons before her very eyes.
forced to watch as her commander’s Zeus was being picked apart by the Mad Cat while her Catapult powered back up.
The dying Catapult became increasingly unsteady as the failing gyro sent a shudder through the entire machine. Just
Adrian Steele’s Marauder seemed to all but instantaneously materialize at the top of the hill, smashing head first into as she fired off her remaining pair of medium lasers one last time in a vain attempt to lash out at her assailant, a massive
the Mad Cat and pushing it away from the Zeus. Though the Marauder weighed in at the same seventy-five tons as the explosion deafened her, and she found herself violently propelled sideways.
Shandra’s scream awoke her with a start. She thought at first that she
had awakened in a hospital bed, just like she had after the events that she
had relived in her dream.
No. Not a dream. A nightmare. The same nightmare she seemed to have
in one form or another every night.
For the last few months Shandra Jaeger had been the newest instructor
to join the Dreadnought-BattleCorps-sponsored Acala III Military
Academy. Early in her time at the academy she had to be excused from
evening formation as she routinely experienced an anxiety attack in
reaction to the ceremonial cannon fire. Staying indoors and feeling as
though she were cowering from the sound of a blank shell being fired had
been humiliating. In the months that followed, she had grudgingly come
to realize that it was a part of her life that she would simply have to accept.
Since that time, she had learned to stay late at night so she could be
alone to review her students’ work because she had grown to strongly
dislike how her peers always seemed to treat her as though she were
made of glass. They were always painfully polite and made it ever so
irritatingly clear that they were aware of her struggles with post-traumatic
stress resulting from her experiences on Twycross. Twycross had put her
through hell, sure, but that did not mean that everyone around her had to
treat her as though she were a live bomb. She sighed, leaning back in her
The familiar thumping sound of ‘Mechs moving around outside the building broke her from her reverie. Again, another part of her screamed back that she still should have tried.
Taking a second or two to think about it, she realized that there should not have been any kind of patrols moving If only she had done something differently, perhaps she would be dead, and they would be alive.
through that particular area of the city’s edge for another ninety minutes. She groaned when she thought about the
possibility of one of the cadets ‘borrowing’ one of the training ‘Mechs for a bit of ‘extracurricular training’–a joyride– She gritted her teeth in disgust with her thoughts and prepared herself to unleash hell upon whoever had taken a
again. It had only happened once before, but it had happened on her watch. She still felt disappointed with herself over ‘Mech out without permission. She opened the heavy metal door to the Mechbay slowly, still seeing the dent that her
the entire incident. foot had put into it during the last incident–and remembering the pain it had caused her.
A promising young cadet had managed to use an intimate relationship that he had developed with one of the academy’s What she saw as she entered the third level of the Mechbay was far, far worse than anything she could possibly have
maintenance technicians to manipulate her into letting him take a training ‘Mech out without permission. While nobody imagined. Her heart sank and she immediately took cover behind some nearby crates as quickly and quietly as she could,
had been hurt, the cadet was expelled from the academy and the technician had eventually been reassigned. Shandra did hobbling over to avoid using her cane and alerting anyone to her presence.
not know where either ended up.
Bodies. At least a dozen. The guards for the Mechbay as well as a couple of the technicians working late had been
She sighed and turned off her desktop computer. After a few more seconds of watching the tri-vid display once again murdered in the dead of the night.
show her the results of the simulated battle from the previous afternoon, she turned it off as well. The afterimage of the
Catapult that had been on the display lingered in her vision, frozen still. Just as she had been on Twycross. There were people she did not recognize clustered around the cockpits of a pair of Academy Chameleon BattleMechs.
There was small consolation in that those ‘Mechs were down for service and several key components had been removed
She muttered a curse under her breath as she grabbed her cane and slowly stood up, stretching out and letting her for rebuilding. But the intruders could not know that. At least that was wasting their time. There were a number of other
She heard a ‘Mech’s cockpit hatch opening just a few meters away from her. While she waited the few seconds for the cold start to engage, Shandra activated the Jenner’s comm system. “Mayday,
mayday, mayday! This is Shandra Jaeger of the Acala III Military Academy requesti–” She stopped speaking when she saw
In her growing panic, she had not even noticed that the most recent addition to the academy’s stable of ‘Mechs, a a message on the display screen stating flatly “No Signal”. The simple message told her that none of the communications
thirty-five-ton converted JR7-F Jenner had been parked just below her. The Jenner was fully functional. She sat for a frequencies were available. Everything was jammed. She let loose a frustrated howl.
moment, staring at it. It was just six meters away, but it looked like a kilometer from where she was sitting. There was no
way that anyone could make that distance without being noticed. She would just join the corpses below. She buckled together the six-point harness as she began to hear gunshots outside punctuated by bullets ricocheting
off the Jenner’s hull. The intruders had clearly pieced together what was going on. As prepared as she could ever be, she
A gunshot rang out from inside the Mechbay, followed by the wet sound of a body hitting the ferrocrete floor after grabbed the control sticks just as the interior lighting changed from white to red and the sound of the ‘Mech’s fusion
falling from a great height. The sound of the gunshot caused Shandra to jump and nearly knock a heavy torque wrench reactor successfully thrumming to life filled the cockpit. Over it all, her fast and ragged breathing echoed in her helmet
off one of the crates she was hiding behind. Silently pressing down on the torque wrench with her hand to keep it from louder than anything else. She reached down to stow her cane so that it would not fly out and strike her at some point
slipping off and clattering to the metal floor under her, she looked out to see what had happened. during the commotion that was sure to come, only to pause for a moment when she realized that she did not have it. She
only had the torque wrench. She wiped at the tears with the back of her hand as she pondered the discovery.
A cold chill shot down her spine.
“Reactor online.”
One of the computer technicians who serviced the ‘Mechs for both the academy and the militia, Jeanette Stevens, was
lying on the bay floor below some third-level scaffolding. Her white turtleneck was slowly turning red over her breast and A cold yet soft synthesized feminine voice filled her helmet, bringing her thoughts back to her situation. She quickly
a pool of blood was beginning to form under her head. She was not moving. stowed the torque wrench into a lockable storage bin beside the pilot’s seat and snugged the harness again. The display
screens all began to light up in front of her, showing real time telemetry and data feeds.
In that moment Shandra knew that if she did nothing, the cadets would likely meet the same fate. Realizing that the
death of Jeanette had captured the attention of just about everyone in the Mechbay, she seized her one opportunity. She “Sensors online.”
cursed under her breath and tightened her grip on the torque wrench. A fit of rage shuddered through her, and she
quickly ran the distance out to the Jenner. Four red lights in a row on an upper panel just to the right of her quickly flicked from red to green. “C’mon, c’mon,
”YES!” She cried out in elation. Now it was the pirates’ turn to be shot at. She immediately stepped the Jenner forward Circling around the buildings at a speed that caused her Jenner’s feet to start to skid on the ferrocrete mid-turn, she
and away from the scaffolding and turned to fire the ‘Mech’s lasers at the densest clusters of the pirates that she could fired two of her lasers into the upper body of one of the Wasps and then turned to escape as quickly as she could. The
spot, including by the heads of the Chameleons. Being fired upon by full-
fledged ‘Mech-class weaponry sent them all running like ants toward the
exit where their transport vehicles lay waiting for them.
She gasped as her body was bathed in heat. The spike in reactor output
to power the weapons unleashed what felt like hellfire into the ‘Mech’s
interior. Holding fire for a moment to allow the Jenner to cool down
internally, she stomped through a group of the pirates, screaming in
mixed terror, rage, and vengeful joy as she turned toward the barracks-
side exit and threw the throttle forward to maximum.
Out of the corner of her eye she caught a glimpse of a small screwdriver
falling from somewhere overhead in the cockpit. The screwdriver landed
on one of the buttons hard enough for it to illuminate. It was just the
external loudspeaker, so she did not bother to turn it back off.
For reasons she could not fathom, word must have not reached the
lance of four light ‘Mechs outside the barracks until the very moment that
she emerged from the Mechbay at full speed, dashing straight for them
and letting loose a banshee wail over the ‘Mech’s external speakers. All
four ‘Mechs looked startled as they turned toward her simultaneously.
Shandra braced herself for the scorching heat as she unleashed a full
volley of the Jenner’s four medium lasers into the legs of the Stinger. Only
two of them connected but they both hit the same leg, punching through
it mid-thigh, causing it to collapse. The surprised pirate MechWarrior
tried desperately to regain the ‘Mech’s balance on its remaining leg but
the effort was in vain. The pirate machine crashed to the ground right in
front of the barracks main entrance. Her tears evaporated, momentarily
fogging her neurohelmet as the cockpit temperature spiked to the point
of nearly intolerable.
She clenched her eyes shut so hard that it hurt, and she saw faint stars.
“Piss off!” She cried out to no one and yet everyone at once. The sound
of her voice was amplified by the ‘Mech to the outside world. She could
feel herself losing control. “Piss off!!” She screamed again as loud as she
could, trying to use her own curses to center herself in the present.
Her eyes snapped back open as she remembered her one goal. She had
Hyperventilating and her eyes swimming with tears that evaporated nearly as quickly as her body produced them, she “Reactor critically damaged. Emergency shutdown initiated.” The emotionless female voice reported calmly the most
began to feel faint. Whether it was more from the heat of the cockpit or from the hyperventilation she could not say. She terrifying thing Shandra could hear in that moment. The Jenner was dead. Through the now cracked and slightly broken
threw her throttle forward again and began to turn around, only to feel the Jenner rock violently under her as she was ferroglass canopy she could hear the sounds of ‘Mechs approaching as she began to lose consciousness. Just as she began
pelted with short range missiles from the Wasps that had caught up with her. Her dizziness did not help the ‘Mech’s to pass out altogether, the cold outside air circulating into the cockpit brought her back from the brink and breathed new
balance and nearly caused the Jenner to trip and fall. Red warning lights flashed while alarms wailed at her for attention. life into her. She began to become slick with sweat as the interior temperatures within the cockpit dropped down to a
level where her sweat did not instantly evaporate.
As she ran around the office building that the Locust had crashed into, the Jenner’s interior temperature suddenly
spiked, nearly knocking the wind out of her. One of the Wasps had managed to damage the Jenner’s reactor shielding Regaining motor control over her own body, she grabbed and weakly pulled the ejection handle. Nothing happened.
severely. One more hit like that, and she knew she was going to die. To make the situation even worse, an indicator was She pulled it again with greater strength and was once again rewarded with nothing. She let loose a string of incoherent
showing a damaged heat sink. Another indicator showed that the heat was building faster than the cooling system could profanities, cursing everything from the engineers who had designed the ‘Mech, the pirates, and whatever higher power
dissipate it, even without her firing her weapons. A warning display showed that she had an estimated seventy seconds there may be as she began to sob. She hastily unbuckled the seat’s harness and pulled off the neurohelmet. She slipped
until critical reactor overheat and automatic emergency shutdown. out of the pilot seat and heard the clatter of the torque wrench as it slipped off her leg. It must have come loose during
the ‘Mech’s final tumble. She wondered if that was what had hit her. She would never know for sure.
Having just taught her students about heat management the previous week, Shandra knew all too well that the
remaining time would be cut down considerably every time she fired any of her weapons. She tried to undog the hatch only to discover that it had bent on impact with the wall. Her hands quickly began to burn
from the hot metal as she tried with all her strength to open the hatch, but it would not budge. Clearing tears from her
The increasingly unsteady Jenner crashed clumsily into the side of the office building, bouncing off it and nearly toppling eyes with the back of her hand she looked around and realized that the frame of the cockpit had warped. With a cold
to the ground. Her next step punched through the tarmac and stalled her forward progress while she pulled her ‘Mech’s chill, she realized that if the ejection system had worked, the canopy likely would not have blasted clear, and the ejection
foot loose. She had accidentally turned onto a stretch of tarmac that was not built for BattleMech passage. Water seat would most certainly have killed her. She felt an embarrassing urge to apologize for the tirade of curses she had let
suddenly exploded up along the ‘Mech’s leg as she realized that she had managed to puncture a water main. As much as loose.
she wished she could remain there and possibly use the escaping water to help cool the Jenner down, she knew that every
second spent stationary brought her closer to death as the pirates closed in on her. She slumped back into the pilot seat to see the two Wasps looming over her like specters of death. Suddenly, out of
the blue, she felt calm. She did not know why. It was as though a burden had been lifted from her shoulders, and the fear
Risking even more heat buildup and reduced time before shutdown she triggered her jump jets to lunge over the and terror went with it. It suddenly occurred to her that she had done what she had set out to do. It dawned on her that
building to her left and out onto a highway that she knew was safe to run on. Two or three vehicles collided with one she had piloted a ‘Mech under the worst possible conditions and still accomplished her goal.
another as they swerved to avoid her landing ‘Mech. She knocked over three light poles and kicked through a portion of
the highway’s median to avoid stepping on the civilian vehicles as she stumbled forward barely keeping the Jenner upright. She was still trembling, but as one of the Wasps raised a barrel-ended arm, taking aim at her, she noticed it was not
just her that was trembling. Repeated vibrations were being transmitted through the fallen Jenner into the cockpit with
She had to get off the highway or else more civilians would be injured or killed. She quickly turned toward a large rapidly increasing intensity. She felt her heart swell in her chest and her throat try to squeeze itself shut as she realized
collection of warehouses just off the highway. She twisted the Jenner’s torso to the left to look back as she turned from that, for the first time since the entire ordeal had begun, she was not alone.
the highway and saw the Wasps land right where she herself had landed just seconds prior. She turned to face forward
as a large building blocked her line of sight. A fraction of a second later, multiple flashes of enemy weapons fire illuminated The Wasp that was aiming at her was slow to react. The other turned to see what was coming and immediately opened
her ‘Mech from behind, striking surrounding buildings and casting a shadow of her machine on the ground in front of her fire, its jump jets igniting as it tried to go evasive, forcing Shandra to immediately cover her ears as the painfully loud
for just the briefest moment. sound threatened to burst her eardrums inside the breached cockpit. She screamed against the increasing noise, her
hands still tightly clasped over her ears as a flurry of missiles and laser fire exploded into the two pirate ‘Mechs and tore
She screamed for help, but her words were panicked, becoming nearly incomprehensible for anyone who could hear them both apart in an instant. The concussion nearly knocked the wind out of her as a wave of heat washed over her.
them. She knew that she had moved too quickly away from the Mechbay for anyone to catch up in time to save her. The
Jenner would overheat long before inflicting enough damage to destroy the Wasps pursuing her if she turned to fight. All The gyro of the jumping pirate ‘Mech burst out through its back, then landed hard on the tarmac and spun off to smash
she could do was try to run. More laser fire and short-range missiles reached out for her as her pursuers regained line of into the remaining leg of the Jenner, lodging itself against the fallen ‘Mech’s inner thigh. The Wasp that had been standing
sight for a fraction of a second. One missile hit her before she managed to duck behind a hardened warehouse to use it over Shandra simply flopped onto the ground with a heavy thud, the cockpit of the pirate machine blown open from
for cover. An alternating high-low pitch warning informed her that her left arm had just seized at the shoulder. behind and smoking. Meanwhile, the jumping Wasp, sans gyro, rolled through the air out of control and crashed
“MechWarrior, you alright?” Adrian’s voice boomed over the Demoness’ external loudspeaker, loud enough to be “Yeah. It’s me. Are the–” Her voice caught in her throat until she swallowed dryly. “Are the cadets okay?”
heard clearly inside the compromised cockpit of the silent Jenner.
“They’re fine. The instructors got them to safety while we got the militia ‘Mechs mobilized.” He reported, his ‘Mech
With the dull throb of what was sure to be a massive headache already filling her skull, she reached over to the transmit clearly looking around to make sure that there were no additional pirates in the area.
key with a shaky hand. She then saw that the radio indicator was blinking red, indicating it had been damaged. She then
“Thank God.” She half whispered, laying her head back against the
seat’s headrest and closing her eyes.
“God had nothing to do with it. You did.” He paused for a moment,
“Look, we managed to take out the local jamming and learned there are
more pirates hitting other parts of the city as well as the proving grounds.
I don’t want to leave you like this but–”
“Go.” She cut him off, opening her eyes and staring up at the imposing
machine standing over her as though she could lock her gaze with that of
her friend inside it, “I’ve done my part. Now you do yours. I’ll catch up
with you later. After you finish making their lives a living hell.”
Shandra watched as the Mad Cat turned abruptly and sprinted off at a
remarkable rate of speed for a machine of its size. Her thoughts began to
trail off after the ‘Mech had disappeared from view and the sound of its
heavy footfalls faded, though she could vaguely hear the echoing sounds
of fighting several kilometers away.
As the adrenaline began to wear off, leaving her feeling lethargic, her
eyes slipped down to the torque wrench on the floor. Rubbing her thighs
absentmindedly, she thought about how she had run the distance across
the gantry to the Jenner minutes earlier without thinking about it. She
found herself smiling even as her eyes began filling with tears once more.
For the first time that she could remember, they were tears of joy.
That night, for what felt to her like the first time in years, Shandra
Jaeger—MechWarrior Shandra Jaeger—slept soundly, without a trace of
any nightmares.
Even though some additional security measures had been put in place, the hopeful belief had been that all the Word
of Blake operatives had been eliminated. That belief had proven to be in error and the security measures had proven to
be in vain. This time the remaining operatives had waited until the time was right. This time it seemed there might truly
be no stopping them.
Kayla was bleeding. Badly. She had suffered a needler wound to the stomach the moment that she and three others
had entered the ammunition magazine through a secondary service hatch. Her intent had been to try to bypass the
Dreadnought Battleship D.B.C. Trinity fighting and get into the magazine where she could possibly help with the increasingly dire situation. Her plan had
In orbit over Theris (Waycross II) backfired on her horribly. It was clear that without immediate medical attention she would surely die. It would not matter,
Waycross System though, if the explosive planted in the magazine detonated. If the device went off, it would trigger a catastrophic
27 May, 3075 secondary explosion that would blow the Trinity apart in the blink of an eye.
She fought through the immense pain of the stomach wound, knowing that the shrapnel from at least a dozen polymer
“What the hell is hap–?!” A panicked female crewman’s yell echoed down the hall, cut short by the sound of a gunshot. flechettes buried in her gut were surely causing more damage every time she moved. Unconsciousness called to her, but
she knew that she could not rest. If she were to die here, she wanted to be sure it counted for something.
“Why’ve you betrayed us?!” Another crewman’s deep voice boomed as he shouted from around a corner at the end
of the corridor. “Were you with the Word of Blake the whole time?!” He demanded before peeking out to fire at the The individual who had shot her, Sergeant Thomas Carter, lay bloody and unmoving on the floor by the explosive. His
Blakist operatives who had taken cover at the entrance to the D.B.C. Trinity’s ammunition magazine. body had snagged on a secured loading dolly, keeping him from sliding away as the Trinity maneuvered. Sure, Carter had
always been kind of a snarky asshole, but he had seemed like a good man at heart. He had been the kind of person that
The interior of the Trinity rang as her armored hull absorbed several more direct hits. The hollow ringing sounds mixed no one would have guessed to be a Word of Blake operative. The perfect sleeper agent.
with the muffled staccato sounds of dozens of autocannons of various calibers as the Trinity exchanged fire with the three
Word of Blake WarShips that were attacking her. The ship pitched about in a way that was unnatural for a vessel her size, Kayla was genuinely shocked that he had shot her. Carter had seemed almost as surprised as Kayla had been when she
causing Dreadnought BattleCorps Sergeant Kayla McKinney’s already unsteady legs to slip out from under her. Kayla had come through the hatch, the two finding themselves looking at each other down their respective gunsights for but a
slumped against a nearby wall, taking cover behind a dislodged armored hatch near the entrance to the Trinity’s fraction of a second. She had hesitated, recognizing him, and seeing that he was standing right next to the explosive
ammunition magazine. device that looked to have just been fully installed. Even as her mind processed that Carter had clearly been responsible
for planting the explosive, he had shot her without hesitation.
Eight days prior, multiple Word of Blake WarShips had entered the Waycross star system. They had ignored any
attempts at communication. Upon arriving at the system’s zenith jump point, the Blakist vessels immediately destroyed Seeing Carter’s body in a motionless bloody heap on the floor, it was clear that in the short moment after he had shot
two JumpShips that were transporting civilian evacuees from Theris, the Dreadnought-owned planet under the Trinity’s Kayla, someone else must have killed Carter. It may have been one of the others that came with her through the hatch;
protection. she would never know. Two of them were already dead, and with the way things were looking she would never get a
chance to ask the third.
Minutes after receiving the distress calls from the JumpShips, the aging Dreadnought-class Battleship D.B.C. Trinity
found herself under attack from within. Explosions in multiple key areas along the ship suddenly crippled her. In a matter Several flashes of laser rifle discharges illuminated the area around her. A hissing sound of superheated metal could be
of minutes, it became clear that Word of Blake operatives aboard the Trinity had sabotaged the vessel. The ship’s heard as liquified metal started dripping down to the floor from the deformed hatch door that Kayla had taken cover
interstellar jump drive was but a memory and several critical connections of the power distribution network had been behind. She looked down just as the Trinity was rocked by an impact that echoed throughout the ship with a hollow
severed, most notably to the weapons array. metallic boom. The lighting in the corridor and ammunition magazine went dark for a fraction of a second before flickering
back on. Kayla felt excruciating pain, and as the lighting restored itself, she discovered that some of the liquified metal
The sabotage had been premature. Eight days of investigations and haphazard repairs later, the Trinity had been had splattered across her thigh. She let out a coarse scream of pain that echoed down the corridor. She barely resisted
restored to a condition where she could at least hold her own against the trio of incoming Blakist ships. Given her sheer the urge to grab at the source of the pain with her bare hands, her mind just quick enough to recognize that it would only
size and sizable arsenal of heavy weaponry compared to the trio of incoming Pinto-class Corvettes that the Trinity was make things far, far worse. There was not much she had with her that could do anything about it.
faced with, it was possible that the BattleCorps vessel might claim victory, even in her wounded condition.
The last remaining member of the team that had entered through the hatch with her, a medic by the name of Sanchez,
The investigations had allowed the command staff to track down the operatives believed responsible for the sabotage quickly injected her with morphine and had begun to say something, but suddenly stopped talking as he collapsed to the
aboard the vessel. There had been no successful arrests, only corpses resulted from the attempted capture of the Blakist floor, unmoving. Smoke trailed up from his head and the stink of charred meat filled the air even more than it already
operatives aboard the Trinity. Unfortunately for the crew, the Blakists took several times their number down with them. had.
Kayla, herself a highly skilled technician that had been entrusted with maintaining some of the ship’s critical power Corpses lay all around, blood spattered over the walls from wounds inflicted by needlers and even some slug-throwers.
distribution systems for several months, had been suspected of being one of the saboteurs because she had been She knew a lot of the people around her. She had spent a lot of time with many of them. The morphine was making things
discovered close to one of the failure sites. The finger-pointing had been painfully common after the sabotage and the a bit hazy, and she was having trouble remembering some of the details. As she looked at the dead Blakists, she felt
ship’s crew had nearly consumed itself with suspicion. She was grateful that she had eventually been cleared as the failure nothing but sadness.
site had been close to one of the systems that she normally maintained. Despite being cleared, she was hyper-aware of
everyone around her as they continued to view her with a sense of palpable doubt. They had initially kept her from Another laser discharge again snapped her from her daydreaming. She was still being shot at. She gripped her pistol
working on primary systems and even then, they had double-checked everything that she did to help with repairing the and got ready to perch herself up when she suddenly realized that half of the weapon was missing. The front half of her
The explosive. She had to focus on the explosive device. There was no way of telling from where she sat whether the As she propped herself up, she heard noises from down the corridor causing her to look toward the entryway to the
explosive was on a timer or if it had a remote in another Blakist’s hands. It was equally possible that Carter had not even ammunition magazine.
activated the device before he was killed. It was possible that her arrival had distracted him and prevented him from
arming it. Even as her mind swam with possibilities, she realized she could not take any chances. As far as she could tell Her eyes rested on Davis’ corpse for a moment. In that moment she realized that the source of her regret was neither
she was the only one who could reach the device at this point, and if she did not get to it, she was sure it would be the the missed date nor the fact that she had been forced to kill him. Her true regret was that she had not been able to guide
end of everything, and all her pain would have been for nothing. She had to save her comrades, even if it was her final Davis to see the light that the Word of Blake had to offer. She had failed to enlighten the one person in the Dreadnought
act before she perished. As she glanced up to see if any other obstacles were in the way between the explosive and her BattleCorps that she had truly grown attached to during her years infiltrating the BattleCorps’ ranks. The years leading up
current position, she again saw the motionless body of the man who had shot her. She hissed under her breath, “Damnit, to this critical moment. She had been forced to kill him without his ever learning the true greatness of Blake. Kayla felt
Carter. You idiot.” that she had failed him.
She looked down around her and quickly found a needle pistol caught on some debris next to the wall. Grabbing it and The sounds were growing louder. Whoever it was had nearly reached the entryway to the bay. She looked down at
inspecting it, Kayla discovered that the weapon appeared to have more than half of its ammunition remaining. Knowing Carter. She whispered softly as she held a bloody hand shakily over the mortal wound that Carter had inflicted upon her,
that a nonfunctional weapon would be a horrific surprise when she needed it to work, she fired it across the bay. The “You are forgiven. It was an accident. May the peace of Blake be with you.”
needle pistol’s polymer flechettes shattered against the far wall harmlessly, but it gave her the answer she needed. She
then shifted her position to get a better view of the person who had been shooting at her. It appeared that the shooter Just as a figure stepped out of the corridor into view and aimed a weapon at her, she detonated the explosive charge.
was the only other person left alive in the entire section.
Another loud bang of an impact against the Trinity’s hull drowned out all noise with its volume and caused the lights
to dim and flash intermittently for a moment. At the same time, the Trinity’s guns suddenly went silent. She wondered if
the ship’s fire control systems had taken a direct hit. In the deafening silence that followed, she absentmindedly glanced
down at her personal chronometer and realized that she had been awake for forty-one hours straight. She sat still for a
moment as she considered the time, her mind wandering to how much she had done and how much had happened since
the last time she had slept. Sleep called to her ever more loudly as she continued to bleed out. Breaking her eyes away
from her chronometer, she gripped the needle pistol tightly.
Kayla heard a click and a soft pop. She recognized that sound. The other person was ejecting a power cell from their
weapon to reload. Now was the only chance that Kayla would get. She bit down her lower lip hard enough to make it
bleed to keep from screaming in agony as she summoned all her strength and hoisted herself up just as she heard what
sounded like some sort of explosion down the hall. The lights flickered and went dark once more. Sparks shot out from
an exploding power coupling somewhere behind her enemy, illuminating his silhouette just as he had stepped out to line
up a shot in her direction again. The emergency lights snapped on and she squeezed the trigger of her weapon.
Instantly stunned and disoriented, the man clutched his neck as blood flowed freely. He took one step to the side to
try to balance himself, firing his weapon aimlessly, only to strike the ceiling. She fired twice more, his body jerking with
each hit to his chest. His rifle clattered to the floor as he fell back, slumping against the wall behind him. In seconds, his
arms fell limp to his sides as the life drained from his eyes.
After what felt like an eternity spent staring in silence at the man she had just killed, Kayla suddenly recognized him
through the haze that had descended upon her mind. Davis. The man had played poker with her on a fairly regular basis
over the last few months. She had liked him, and even remembered that she had blushed heavily when he had asked her
out on a date while they were on leave. They never did get that date, as they had been recalled to duty before they had
the chance. She rather regretted it, now. Whether she regretted more having to kill him or not having been able to go on
that date, her muddled mind was not entirely sure. This caused her thoughts to become even more jumbled.
The sound of the Trinity’s guns beginning to fire again shook her from her distracted reverie.
The explosive… The explosive! She had to consciously gather her thoughts and force herself to focus. Every motionless
face that she saw, bloodied and ruined or otherwise, was someone she knew. It took everything she had not to let herself
slip into memories of the time she had spent with these people. She knew her time was limited, and she could spare none
of it.
“They may have been built some three hundred years apart, but the Trinity was the closest thing to a sister-ship that
Kayla felt the Trinity accelerating to her maximum thrust and the increased pull to the floor made moving that much the Phoenix ever had. And now… Now she’s gone. Torn asunder and left to drift. Worse still, everyone and everything that
harder. Her already weakened body would have never been able to stand up under one standard gravity of force. Now had been under the Trinity’s protection is lost. It almost feels like this whole damned ship is weeping—and crying out for
that the WarShip was accelerating enough to produce half-again that much force, she had no choice but to crawl. She revenge.”
dragged herself across the now silent bay, her consciousness slowly draining away as blood from her open wound left a – Colonel Kai Kelderman, Commanding Officer, Texas-LFR Battleship D.B.C. Phoenix, 28 June, 3075
“The stabilizer’s working as best we can make it,” Carlos said with a shrug, “How about you don’t test it?”
He glanced down at Bloodbath again. The ‘Mech’s hatchet was pitted and dented from battle, the red paint of the arm
contrasting with the silver and gold of the rest of the machine’s livery. Here and there Tyr could see portions of lighter
Overlord DropShip Cathedral colors where new armor had been fitted and painted over. The bold Roman numeral “IV” stood out proudly on the
Descending from orbit over Vyrie City ‘Mech’s chest, simultaneously a taunt to the reaper and a reminder of Tyr’s mistakes. Bloodbath was his ‘Mech, but it
Ashkum IV was much more than something so simple. The ‘Mech was the Templars’ symbol. He glanced to the shoulder where the
17th January, 3077 Blackwood Templars’ emblem, a knight templar cheating at cards, showed proudly.
“One day,” Carlos said, his voice dry, “You’ll bring it back in one piece. That or you’ll finally realize you don’t always
Tyr strolled up to where Bloodbath waited in its repair gantry. His Technician Carlos glanced over at him. Carlos was have to be out in front.”
already wearing the drop harness MechTechs were issued for safety and was clipped into the runner bars on the side of
the hangar. Tyr laughed, “Wait in the back for everyone else to hog all the fun?” He shook his head, “That’ll never happen.”
“Tinker said she fixed the Supercharger again,” He said, “She also said to stop pushing it every time.” Carlos sighed, “Figured as much. Just bring as much of it back as you can.”
“Where’s the fun in that?” Tyr asked, looking over the ‘Mech. “Why, Carlos, you sound like you only care about the ‘Mech.” Tyr grinned at him.
Only someone intimately familiar with Bloodbath would have noticed the slightly different shade of paint where “Col. “Tinker would have my head if you damaged that Supercharger. Or lost this thing,” He tapped the ‘Mech’s head, “She
Tyr Blackwood” was painted over the hatch. The paint had needed to be redone after a near miss by a Clan particle cannon still wants to build another one, but since we’re always stuck rebuilding yours, she never has the time or resources.”
had scoured the old away. The close call had also made the hatch sometimes stick, even jam when opening. Now it opened
smoothly, allowing Tyr to lean in to check the carbine on the back of the seat. “It’s not every time!” Tyr said, his grin growing before ducking into the cockpit.
The weapon’s dented stock was the result of a bad landing after being forced to eject. The same incident had left Tyr “Close enough.” Carlos muttered, his face pulling into a smirk before raising his voice again. “Everything is primed.
with a ring-shaped scar around his left ankle, marking where broken bone had punched through his skin. He had been Watch the energy flow to the left torso large laser. I think we nailed down what was causing the problem, short of test-
forced to make a hasty splint from sticks and branches around him and use his rifle as a crutch to hobble his way until he firing the thing at full power inside the DropShip multiple times, there’s no real way to be absolutely sure. Just keep an
had made it to allied lines. The same allied lines where, just to put the cherry on top of an already bad day, he had been eye on it if you can. The issue should be ironed out, but every time I’ve said that these past few months it comes back in
shot in the left thigh by a terrified friendly militia trooper. That puckered scar stood out prominently in the center of his a day or two. Should still work okay, I just can’t promise it’ll be everything it should.”
leg. Only occasionally did it give an uncomfortable twinge in bad weather.
Tyr nodded, “Thanks for the heads up.”
“You replaced it. Will it latch?” Tyr asked, tapping the hatch.
“Luck, sir. And bring it back, dammit!” Carlos shouted as Tyr started to close the hatch.
“It’ll latch.” Carlos said, his eyes tracing over the right side of Tyr’s face.
Tyr laughed and shut the hatch. Reaching above and behind him he pulled down the neurohelmet from its cubby. He
Tyr knew what Carlos was looking at. It was hard not to. A burn scar took up most of the right side of Tyr’s face. During rotated it in his hands, running his fingers over the portion of the helmet with his name on it. The helmet had been
a contract that pitted the Templars against forces of the Draconis Combine, an autocannon shell had hit Bloodbath’s head, replaced after yet another time Tyr had ejected. His old helmet had saved his life when an enemy soldier had gotten the
sending shards of cockpit ferroglass into Tyr. The hit resulted in a long scar where a particularly large shard of that glass drop on him and shot him. The face shield had shattered inward, and glass had given him a scar under his left eye about
had impaled his left side. The impact had also caused the cockpit hatch to come undogged, swinging open and letting three inches long. An inch higher and he would have been blinded. Tyr tapped the glass. He had been lucky that day.
burning debris careen into the cockpit. The following several moments had been unpleasant, to say the least, and he bore
the permanent record of the experience on his face. The same could not be said for the enemy soldier.
Tyr nodded and reached down to check to make sure his survival knife was secured in its hard sheath, bound tightly to Laughing to himself, Tyr pulled the helmet on and went through the startup sequence. “Life is a contest. One I intend
his left leg. He had learned the hard way to make sure of that when he had not been as careful. During a separate incident to win.” Bloodbath’s reactor hummed as it came to life. Tyr tossed a salute to the picture, taken years before, of all the
where he had been forced to eject, the force had caused the knife to cut through its sheath and buried itself in the top of original Templars. Many of those pictured had since died in combat.
his foot. He still had the scar from that mistake too. He double checked his sidearm, a heavy-barreled automatic pistol.
“Templars, sound off!” Tyr called and listened for the responses. Only after everyone had reported in did he speak up
“Stabilizer fixed?” Tyr asked, leaning into the cockpit and checking, vainly, as he always did, under the pilot seat. On again. “You all know the plan. I intend to get down there and get this job taken care of before those slowpokes in the Free
Huntress he had been forced to eject once more, only to discover firsthand what an incorrectly calibrated stabilizer for Companies even hit dirt.” Laughter and cheers came through the radio at his comment.
an ejection seat could do. He had tumbled through the air out of control, catching his arm on the end of a tree limb and
tearing it open from elbow to wrist. He rubbed the scar absentmindedly he had been lucky to survive that one, much less After a moment double-checking Bloodbath’s readouts as the powerful machine thrummed to life, Tyr spoke up again.
”The rest!” The shout held the same joy and anticipation it always did. The hangar door dropped open, allowing daylight
to spill into the bay. Tyr hit the button to disengage the restraints holding Bloodbath in its gantry.
It was not like he was some kind of unhinged murderer. No, he had standards. A code of sorts that he was cloaked in.
This kept him from being in the same pool as these zealous murderers. It was what kept him employed with the Ronin
Free Companies despite the warnings of the units he angered during Operation Bulldog. Even the warnings from Outreach
about him, most of which pertained to things like “Needless and excessive brutality unbecoming of a MechWarrior”,
seemingly left Donaldarus Meridius, his employer, unperturbed. Maximus supposed Meridius either did not care or that
Central Vyrie City he saw the bigger picture. What did those idiots know about command? About sacrifice? About doing what was necessary
Ashkum IV for results? Maximus had always done what it took to get the job done. It was what his handlers drilled into his brain as
30th January, 3077 a child after his kidnapping and brainwashing.
“You’re a killer, boy. But you must remember you have a creed. The mission is always your priority and anyone in the
Maximus took a long and lazy drag on the poorly rolled cigarette between his lips. He savored the smoke and the way is an obstacle to be swept aside or crushed.”
creeping burn in his chest the longer the smoke remained caged in his lungs. He exhaled calmly and repeated until it was
nothing more than a stub. Casually spitting it out of his mouth and onto the ground below him, he took out another of At the time, when he was but a child, his mission was to escape. After killing his captor with some jagged piece of glass,
the poorly rolled sticks and lit it. Again, he dragged and exhaled until it was a stub, spitting it onto the ground. He reached Maximus disappeared into the underbelly of that planet. Soon he found himself on a transport to Solaris VII where his life
for another from his cooling jacket pocket but decided against it as the wind picked up. There was a scent on the wind of really took off. Blood sports, assassinations, good old fashioned robberies, and eventually learning to pilot a BattleMech.
burned metal and a chemical fire nearby. Sounds could be heard as well. Thunderous explosions, small arms fire, the He had stolen the Cyclops he now piloted, got rid of the worthless electronics suite, and lived in his BattleMech from then
stomping of BattleMechs and other sounds of battle made Maximus’ hands shake ever so slightly with anticipation. on. He took contracts with numerous units, fought the clans, and even took the fight to them.
Shaking and then rubbing his shaved head, Maximus descended the short ladder of welded rungs from the top of The Clans were a real test and an opponent if he had ever found one. His last fight with them resulted with Maximus
Warcrime, his Cyclops BattleMech, to reach the entrance to the pilot cabin. Slipping into the opened hatch on the side of blowing up a large gas refinery, destroying two companies’ worth of Clanners retreating through it. The Clanners thought
the ‘Mech’s head, he turned and worked the hatch lever until the door was sealed and the cabin pressurized. He relished the place too valuable to warrant destruction, as did the local government and leaders on planet during Operation
the smell of the sweat-tainted recycled air that he was breathing and shuffled his way to the command chair. BULLDOG.
His reworked Kuritan Cyclops had a quite the roomy cockpit once the advanced electronics systems had been removed. Maximus saw it as a solution.
It was so roomy in fact he had a small place where he could sleep and a corner with a chem-toilet securely locked into
place and made of a heat resistant plastic. Having been a MechWarrior for so long the importance of not having to get Still, even after the incident had drummed him back to Solaris VII, he was never short of work. Donaldarus Meridius
out of his machine to sleep or relieve himself was never to be understated. It was too risky to pitch a tent or climb out to found him at some point and shaped him into bludgeon in the Shadow Wars against the Word of Blake. Black Ops missions
take a leak in any theatre so why not bring those amenities into the protected confines of his ‘Mech. where failure was death. Given a mission, he completed it, got paid, and Meridius never asked questions. Success was
enough.
A strange trophy from long ago, a hula girl novelty toy, sat on the shelf of the cockpit window and would perpetually
shake at him when he piloted the ‘Mech. It was always watching him but never judging. Now with Operation Lancaster tanking fast with the arrival of the Word of Blake’s 55th Shadow Division, Free Colonel
Meridius gave him a new mission: “Destroy as many of them as you can. Help is on the way, but you need to survive with
Plopping himself into the command chair, Maximus worked on a pair of skintight fingerless gloves. They had lines of as many friendlies as possible. Ronin actual, out.”
sweat running through them. Some were brown and others white, intertwining to make a pattern that reflected his
journey across the stars or the beams of light so commonly seen on a battlefield. These gloves were old but just as much His mission was clear, simple, and had an attainable goal. Maximus had taken up a position near a skyscraper belonging
a part of him and his ‘Mech as his cooling vest and neurohelmet. Sweaty hands could be detrimental in a firefight and to some inter-system banking company. Nearly sixty stories of hardened ferroconcrete and steel with more glass than
these gloves never let him down. He flipped a series of switches, pressed a row of buttons, and readied himself to recite seemed reasonable. It was the size of a couple city blocks but had apparently been built cheaply by the company. All that
the phrase needed to authorize the starting of his BattleMech. money and no sense, he thought. It was long evacuated, so it was simple to convince the engineers and other forces with
him to rig the building to collapse across the freeway running through the city at his command. This would cut the Word
A sultry female voice came from the two speakers he had mounted above the Cyclops’ viewing window and asked him of Blake forces into two parts, destroy the easiest means of navigation, and send up an obscuring cloud so thick that
simply “Who are you, cretin?” sensors, both thermal and others, would be obscured for hours if not days. More than enough time for him to eliminate
as many of the enemy as he could before backup arrived and got in his way.
Maximus felt a wry grin twist his face as he answered with a scratchy, deep voice. “I am a murderer awaiting his
promised visit to the hell of his victims.” Seismic readouts in his ‘Mech let Maximus know it was time.
The female voice did not answer. Instead, the fiery heart of his BattleMech roared to life, pouring power into the limbs He keyed his microphone five times, waited a few seconds, and then keyed it twice more. The signal was the only
of the machine. He cycled his weapons, four LB 10-X Autocannons, while simultaneously working the arms. Satisfied with warning that anyone in the area would have of what he was about to do. As he watched infantry quickly take cover and
his startup checks, he then began the process of attaching vitals monitoring pads to his temples and chest, in turn plugging tank crews dog the hatches of their tanks in front of him, he knew that the message had been received by those it was
wires into the pads. He then grabbed the hefty neurohelmet that all MechWarriors had to wear to pilot their giant metal meant for. He waited 30 seconds, and just as a number of Word of Blake machines came pouring into sight, he triggered
avatars. Seated firmly onto his head, he plugged it into a panel beside his chair and focused on the flood of information the firing studs on both of his control sticks. A full volley of high-explosive autocannon slugs blasted into the mountains
streaming into the helmet. of explosives wired into the building right next to the approaching Blakist ‘Mechs. The resulting explosion was massive,
Maximus cracked his neck and coaxed Warcrime forward, making for the remains of the freeway and the units that Stomping into the cloud, Maximus took with him a cold brutality and his mission. His mission was to stop as many as
had managed to survive. The thick cloud of dust, made up of so much ferrocrete and metal shavings, threw most sensors he could, and he would be damned if he did not complete his mission as ordered.
into complete disarray.
“And you wouldn’t have it any other way.” Shandra gleefully chided. “But back to what I was saying—”
“Shut up and paint when I’m talking to you.” Shandra said flatly, prompting Adrian to give her a sidelong glare. “Sir.”
She added before briefly sticking her tongue out at him.
Adrian snorted in amusement, a smirk forming as he shook his head for a moment before he finally gave a nod for her
Acala III Military Academy to continue. He dipped the brush into some more paint, beginning the process of coloring in a larger section’s base color.
New Sydney
Acala III “Look, you’ve got more kills than anyone else in the unit, and most of those have been in the defense of others. There
21 February, 3078 are so many people here who owe you their lives—”
He cut her off with a scoff, “You know full well that just about as many likewise owe their lives to you, too.”
The paint on the brush had started to dry up again, prompting Adrian Steele to stir the brush in the large jug of paint-
dirtied water sitting on the gantry by his side. After drying the brush, he dipped it into the can of darker red paint he had “That’s beside the point! What I’m getting at is, does it surprise you so much that they look up to you? Hell, you’ve
mixed earlier before returning to painting the curved side torso armor in front of him. even saved my life multiple times… In different ways…” She trailed off a little with her last words, but she was still speaking
loudly enough that he could hear her, even over the background noises of mechanical work being done across the
“No way I can talk you out of this?” He asked, already knowing the answer. cavernous Mechbay.
“Hell no.” Shandra Jaeger answered with a laugh as she leaned forward, crossing her arms, and resting against a railing His jaw tightened and he swallowed dryly as he recalled the events she was referring to.
a couple of meters away from him. “You know as well as I do what this thing means to people. It’s a symbol.”
Twycross, 3050. The shithole where Steele had almost died for the first time in combat, and where he had left parts of
“It was just a personal bit of art.” Adrian sighed, “Personal expression.” himself behind, both figuratively and literally. It had been a particularly difficult fight against Clan Jade Falcon. For Steele
and Jaeger, it was arguably the worst few minutes of their lives—not that it would be the last time that either of them
“You should’ve thought about that before you became someone so many look up to.” would be within touching distance of death.
After applying a couple more strokes of fresh paint, Adrian paused, lowering the brush for a moment to dwell on that During a hastily organized withdrawal to regroup, Steele himself had been momentarily separated from the rest of the
point. She was not exactly wrong, but she also knew that dealing with that kind of attention did not come very naturally command lance due to a heavy wave of missile fire, forcing him to break off and take a detour through a parallel canyon.
for him. Shandra knew how much of a natural introvert he was, even if over time he had become what is most commonly Moving as quickly as he could to meet up with the others, he could only listen as the comms traffic painted an ugly picture.
referred to as an ‘extroverted introvert’. It just meant that he was decent at putting on a good face to be around people.
It came with the territory of holding a higher rank. Of course, with Shandra and Adrian, rank did not really mean that A pair of Jade Falcon ‘Mechs, a Loki and a Mad Cat, had pursued the rest of the Command Lance after Steele had been
much when it was just the two of them. They had a relationship that was as close to being siblings as two people could separated. The Loki had already incapacitated the second officer’s Griffin. Meanwhile the Mad Cat had closed in on the
be, short of blood. company commander’s mauled Zeus and had downed Jaeger’s Catapult when she got in its way.
“Just because I’m a reasonably good pilot doesn’t mean—” Seconds after hearing that Jaeger had fallen, Steele found the hill he needed to charge his Marauder up and over to
give the commander some desperately needed backup. As he crested the hill, firing at the Mad Cat to try to draw its
“‘Reasonably good’? Damnit, Steele! Even on his best days Kai Allard-Liao himself would have his hands full trying to attention away from the Zeus, he had caught sight of the downed, motionless Catapult. It had clearly slid down the
fight you in a one-on-one.” Shandra motioned over to the Sumaire Assault OmniMech across the bay, “Even if you weren’t opposite side of the steep hill after being downed. The cockpit was blown open and appeared to be burning.
piloting that monster.”
In that moment, a part of him had gone cold and snapped. He still did not remember what came next, but from what
He took a deep breath and exhaled loudly through his nose. he was able to gather from others after the fact, he and the Mad Cat had exchanged salvos—each striking the other in
the head. Strangely, nobody seemed to know what happened to the Loki after Jaeger’s following fateful bout with it.
“Oh, don’t give me that crap.” She laughed again.
Adrian found himself staring at his right hand as he held the paintbrush with it. He had become an expert prosthetic
“What crap?” user, able to handle it as though it had been his born limb, but even with the haptic feedback sensors built into the highly
advanced limb, it was numb compared to his original arm. Looking at it, it was almost easy to be deceived into thinking
“That crap. That sound you make when you know you’ve lost but refuse to give in to the other person’s perspective. that his hand was natural, even when comparing it to his natural left hand. It was the price he paid on Twycross. Of course,
It’s really quite unbecoming of you.” the Jade Falcon Mad Cat pilot had fared far worse, as that very Mad Cat now sat in front of Adrian, decades later.
He lowered the brush back into the water jug and stirred it absentmindedly as he looked back at Shandra, “Now just “Hey. Come on back, now.” Shandra spoke softly, putting a gentle hand on his shoulder as she knelt down next to him,
hold on one damned minute, Lieutena—” leaning forward in front of him to look into his eyes. When had she walked over to him?
“Oh? You gonna pull rank to shut me up, now?” She grinned defiantly. “That the only way you can win this battle? Ha!” “I’m here.” He half-whispered with a slight nod and a slow blink.
She nodded as she lowered her head down to tuck her mouth
behind her forearms, muffling her voice a bit. “It was the end of one
chapter of our lives, and the beginning of the next.” Both of them knew
the unspoken gratitude there, as he had done a lot to help her start the
next chapter she spoke of.
Shandra had blamed herself for the death of an infantry platoon that
had died trying to assist her shortly after Steele had been taken out on
Twycross. She had been forced to watch them die in front of her before
her ‘Mech was destroyed—and her nearly with it. Afterward, she had
gone into a deep depression, suffering from post-traumatic stress and
textbook survivor’s guilt. Adrian had felt that she might have been
considering suicide, and he was not about to let that happen.
“I’m just glad you made it.” Steele smiled, dipping the paintbrush
into one of the paint pots to start outlining another section of the
design.
She nodded. “Vice versa.” She said loud enough to be heard, even
though she was speaking into her forearms. Suddenly her brow
furrowed and she raised her head to look at him, “You know, you’ve
never actually told me why you gave this thing the name you did.”
She sighed softly, staring at him for a moment in silence before speaking up again. “Amazing. Even now, your first “And yet still you blame the machine?” She eyed him suspiciously, “That’s a bit unlike you.”
thought is that I almost died, even though you almost did, too.”
He shook his head. “No. I never said I blamed it.”
“Is it really so strange?” He asked with a quirked brow, finally looking to meet her gaze for the first time since his mind
had returned to the present. “And yet you still sound an awful lot like you do.” Her expression grew even more confused.
The other mercenary unit hired by the BattleCorps, the Ronin Free Companies, had been holding the center of the city Sergeant Major Keiichi and Second Lieutenant Christina McRae landed their Ravage IIs on the highway not far ahead
for nearly half an hour as the rest of the Blackwood Templars and most of the remaining BattleCorps repositioned to and began sprinting back toward the relative safety of Alpha Company’s heavier machines, trying to use the buildings for
simultaneously attack the Word of Blake. cover. Meanwhile, Lieutenant Sienna McLaren, Alpha Recon’s Lance Leader, continued to jump her ‘Mech further back,
firing in the direction of their assailants in an attempt to provide cover for her lancemates’ retreat. Despite clearly trying
While the Ronin Free Companies had help in the form of the BattleCorps’ 5th Irregular Battalion and a cobbled together to draw fire, McLaren was seemingly ignored, and the other two ‘Mechs of her lance took heavy fire—some of it punching
understrength battalion of militia troops, it sounded like the 5th Irregulars had taken severe losses and the militia was straight through the nearest building. Keiichi took several direct hits to his left side, his Ravage II’s left wing and arm
but a memory. Now the Ronin were getting pounded. The Ronin Free Companies’ commander, Free Colonel Donaldarus simultaneously exploding away at the shoulder as bright flames began to engulf the left side of his machine. Just behind
Meridius, had promised Colonel Lawrence he could hold for thirty minutes. That time had nearly elapsed. The Ronin Free him, McRae barely kept her ‘Mech on its feet as both wings and both arms of her machine all but shattered like glass.
Companies’ force numbered a little more than one of the BattleCorps’
own reinforced Battalions. At least, it had been when Operation
LANCASTER had started nearly a month prior.
A part of him was reminded of the one thing that all the previous
events had in common. His old ‘Mech, the Mad Cat that he had named
the “Demoness”. Strange as it was, of all the things to be feeling in this
moment, he was suddenly struck by the feeling of nostalgia and how
much he missed that machine.
Twelve Word of Blake ‘Mechs. Even numbers. Adrian glanced down at his tactical display. Alpha Company was at the Though nearly all the hostile ‘Mechs that Alpha Company encountered were armed with the astonishingly powerful
Delta Four/Five Line. They were in position. He began to wonder if the rest of the units were in position to execute the yet seemingly slow-firing particle cannons and some other Clan-based weapons, all of their non-pulse-fire lasers were red
pincer. His mind had barely finished processing the question before he had his answer. The answer was that it did not in color. Adrian’s confusion continued to grow, as did his curiosity. The number of contacts in their sector was diminishing
matter, because the time had come, ready or not. She had to give the order now, or risk the order never being given. on his tactical display, yet with each one destroyed, Adrian felt a growing apprehension that he was missing something.
“Dragon Actual to all units! Engage! Open fire!” Colonel Lawrence’s voice almost cracked as she shouted the command The heavy return fire that had been weathered by the three mixed medium- and heavy-class ‘Mechs of the Intercept
over the open comms, the signal going out on all frequencies to make sure that everyone heard the order. The darkening Lance forced them to withdraw back behind the Command Lance after the next few enemy ‘Mechs had been destroyed.
city had been modestly illuminated with sometimes strobe-like flashes of weapons-fire exchanged between the 55th and The fifty-ton Tyrant piloted by Sergeant Jens Verrak was noticeably limping along with a severely damaged leg actuator.
the Ronin near the capital, just a kilometer to the north-west. The hellfire that erupted following the Colonel’s order was The Support Lance quickly moved up in front of the Command Lance, taking the place of the Intercept Lance in the
almost otherworldly, a huge section of the city becoming an instant wash of light and cacophonous noise. formation to maximize protection of the Colonel as the company continued to move forward. After making their way
through a business plaza filled with large office buildings and other structures, the company’s ‘Mechs stepped off the
Each of the hostile machines now appearing before Adrian, as well as several that he could not yet see, were quickly tarmac and onto the grassy field of the city’s central park, still wet from the horrific storm that had passed by days prior.
being painted up on his heads-up display as targeting telemetry was being fed through the Target Data Networking System
built into each friendly machine in the company. As Adrian began to pick a target and prepared to fire, a chevron appeared Just as mud started to cake onto the Sumaire’s feet with its first few steps off the tarmac, a sort of sixth sense told
over the nearest machine. His target had been chosen for him. The angularly styled Word of Blake Celestial OmniMech, Adrian to turn around. Adrian slowed and rotated his Sumaire to look back and immediately spotted a group of five Word
a seventy-ton Deva, was suddenly the recipient of the ire of most of Alpha Company’s combined firepower as the nine of Blake Celestial OmniMechs just rounding the corner into the park, almost directly behind the Intercept Lance. As none
‘Mechs comprising the Intercept, Command and Support Lances fired upon the machine simultaneously. The hastily of the five new hostiles showed outward signs of having been in combat, a sixth was surely seconds from appearing.
regrouped Recon Lance added their combined fire to the already devastating barrage a split-second later, McLaren
smartly leading her trio of battered light ‘Mechs to flank around and keep their distance, providing support as possible. “Contact! Six o’clock!” Adrian shouted.
The Deva was reduced to a pile of scrap and a memory in the blink of an eye thanks to a combination of missiles, lasers, Though the Blakists seemed to be just as surprised to see Alpha Company as he was to see them, they immediately
and the manmade lightning of particle projector cannons, all punctuated by hypersonic slugs from gauss rifles. It was as changed direction to engage Alpha Company’s rear flank. One of the Grigoris opened fire on Ann’s turning Neugen,
though the hand of God had simply reached down and chosen that the Deva should cease to exist. In truth, it had been striking it in the side. Adrian did not hesitate. He charged his Sumaire back onto the tarmac, slipping between the
Lieutenant Alex Harper, the Battalion Tactical Officer aboard the Colonel’s Neugen, who had simply designated a target scrambling ‘Mechs of Intercept Lance, and headed straight at the incoming hostiles that were trying to stab them in the
to engage, the information simultaneously transmitted to the targeting computers of every machine in the company. back—specifically targeting the Grigori that attacked Ann. Though the rest of the hostiles focused on the visibly damaged
‘Mechs of Intercept Lance, the Grigori’s pilot seemed to realize the threat that the Sumaire presented. The Grigori quickly
Seconds later, the same happened to a hundred-ton Archangel that had turned the corner to engage Alpha Company turned to Adrian, lashing out with its absurdly powerful particle cannon and a wave of missiles.
as the Deva was reduced to wreckage. As Alpha Company savaged it, the Archangel managed to fire off a handful of aimed
rounds with its rotary autocannon before the arm mounting the weapon was ripped cleanly off. The rapid-fire weapon The hastily-fired salvo was not spectacularly accurate. Several of the missiles passed by harmlessly, although a few of
was still discharging as it fell to the ground, spewing shells that split a multistorey shopping center straight down the the wayward missiles peppered two of the already-abused ‘Mechs of Intercept Lance, and the particle cannon only
middle before the spinning barrels dug into the tarmac, stopping the weapon dead. managed to graze the Sumaire’s right forearm. As all the previous targets that had been engaged by Alpha Company had
gone down before they had had a chance to target any member of the Command Lance, the Sumaire’s armor had
Even as it fell, the dying Archangel let loose a bright, flaring snapshot with a torso-mounted weapon that surprised managed to remain unmolested until this point. The big OmniMech shrugged off the Grigori’s attack as though it were
Adrian. He had seen a handful of different kinds of particle cannons in his life, but never anything quite like this. The nothing. The return-fire from the Sumaire, however, was far from “nothing”.
bright, arcing blast of directed “lightning” was reminiscent of the concentrated burst of a Clan-made particle cannon, an
already devastating weapon, but it was tuned almost into the purple spectrum, and seemed to carry with it a fury that he At short-to-medium range, especially with Steele’s preferred weapons configuration, the Sumaire OmniMech was one
had never seen in any such weapon system. of the most devastating machines ever produced.
The powerful blast managed to strike Keiichi’s burning Ravage II squarely in the center of the chest mid-jump. The light At point-blank, it was positively lethal.
‘Mech must have been nearly a hundred meters in the air, burning at the Archangel with its quartet of medium-range
lasers when it was struck. The Ravage II’s already abused, notoriously thin armor managed to absorb the autocannon Twenty-four high-explosive missiles spat forth from the Sumaire’s twin OmniBow Streak-fire Advanced Tactical Missile
rounds well enough, but the high-powered particle cannon blast was another story. The latter ripped straight through the systems and exploded against the sixty-ton Grigori’s hull with enough force to give the appearance that it had been hit
light ‘Mech, coring it out all the way from front to back, some of the concentrated charged particles even continuing on with a ‘Mech-sized wrecking ball. Even as the lighter Blakist machine reeled under the impact, already unsteady, it was
into the sky after burning through the rear armor and bursting out the back of the ‘Mech. then assaulted by the lasers mounted in the arms of Steele’s ‘Mech. The twin medium pulse lasers stitched a jagged gash
up the centerline of the Grigori that ended with a discharge of the twin extended range medium lasers stabbing directly
Keiichi ejected a split-second later as his Ravage II began to roll forward, out of control. Like a puppet with its strings into the Blakist machine’s head. The head of the Grigori seemed to first melt and then implode, erupting in flames.
cut, the light machine fell from the sky, its remaining wing snapping off as it fell. The dead ‘Mech landed head first on the
tarmac, caving in the remains of where the pilot had been just seconds prior. Adrian looked up just as the ejected The dead ‘Mech fell to the side and tripped up the legs of a Blakist Seraph just as the heavier Seraph was savaged by
MechWarrior’s seat deployed its parachute. He had begun to let out a sigh of relief but could only watch in horror as a concentrated fire from other members of Alpha Company. The Seraph’s hatchet-wielding left arm spun off to violently
flurry of steady green beams converged on Keiichi, erasing the ejected MechWarrior from existence. The beams had come smash into an office building as it tripped and fell forward over the dead Grigori. Though the Seraph was quick to try to
from behind several buildings to Adrian’s ten o’clock, roughly five hundred meters distant. recover, it would not get the chance.
Struggling against the weight of the heavier Sumaire pressing down on its back, the eighty-five-ton Seraph attempted A thrill ran up his spine as though death itself had run a claw along his back, the hairs on the back of his neck standing
to rise, only to be rewarded with being pressed even harder into the now-cracking tarmac as Adrian shifted his ‘Mech’s on end as he recognized the machine facing him. It was the Demoness. The original Demoness. The Mad Cat had been
weight even farther forward. modified a touch, but there was no question that it was his old ‘Mech, as though summoned by his earlier thoughts.
A burst of five emerald-green beams raked across the Sumaire, followed by a wave of long range missiles. The missiles The Mad Cat fired again, its lasers slashing across the Sumaire’s body and its missiles beating and banging on the big
scattered across the Sumaire’s body, minimizing actual damage, and the Sumaire shrugged off the assault in a way that ‘Mech’s heavily armored shell but failing to crack it. Adrian was not about to let the challenge go unanswered. He returned
few ‘Mechs could. However, the last of the missiles managed to clip the cockpit canopy. The actual damage done to the fire, pounding the Mad Cat heavily with the Sumaire’s far more lethal array of missiles and lasers, knocking it off balance
transparent armor was minimal, but the concussive impact hurt like hell, and it set Adrian’s ears ringing. and sending it reeling to the side to crash into a multilevel parking garage. Had the structure not been there to catch it,
the Mad Cat surely would have fallen.
Adrian stomped the Sumaire’s right foot down on the Seraph once
more, this time caving in the Seraph’s back and causing the core of the
Blakist machine to collapse. The Seraph’s fusion reactor gave a whimper-
like flash of light and heat as it scrammed itself in reaction to a failure of
its containment bottle.
As the staggered Mad Cat regained its composure, Adrian spotted his
customary demon-girl emblem, tattered and worn, still painted on the
otherwise completely re-liveried white and black Demoness. It surprised
him that the Word of Blake pilot that had taken his ‘Mech from him had
been so brazen as to leave the emblems on there. It was a taunt. Perhaps
even a show of overconfidence.
Adrian’s lip curled into a snarl, and he felt a cold, vindictive emotion
shudder through him. It was not like him to experience target fixation, but
the rest of the fighting around him seemed to cease to exist. Only the Mad
Cat and the Sumaire—only the Demonesses—remained.
After angrily yanking the Sumaire’s partially melted foot out of the
wrecked Seraph, he began to stalk his way toward the smaller Mad Cat.
The Mad Cat began to backpedal as another wave of its missiles and lasers
swept over the larger Sumaire. Adrian did not even flinch, throwing his
heavy machine’s weight into the impacts to continue forward unimpeded,
though the attrition was beginning to show. Large chunks of the Sumaire’s
armor started to litter the ground.
Adrian’s devastating return fire swept the battered Mad Cat’s legs out
from under it in an instant, the smaller ‘Mech’s right arm shearing off just
above the elbow and its left shoulder missile rack exploding as it toppled
to the ground on its back. Immediately the Mad Cat began to try to stand
up, but the Sumaire was upon it before it could even start to prop itself up
on its remaining arm. The Sumaire’s left foot came down and pressed on
the pelvis of the Mad Cat, pinning the fallen OmniMech in place.
Adrian leaned his Sumaire forward to stare down the smaller ‘Mech,
one of his double-barreled arms pressed squarely against the Mad Cat’s
head. It became clear that the Word of Blake pilot got the message, as the
Mad Cat ceased moving. He triggered on the Sumaire’s external
loudspeaker, his voice coming out as a low growl, “That’s certainly a nice
‘Mech you got there. Where’d you get it?”
There was a short pause before the voice spoke again. This time it sounded almost amused. “So, we meet again. I
gather you’re this machine’s previous pilot, then? If so, I suppose I should thank you for providing our blessed order Adrian lowered the brush into the dirty water jug, swishing it about to clean the brush of excess paint. He had finished
with—” Again, the strange voice was cut off, this time by the scraping of the Sumaire’s double-barrel-ended arm against his work on the sides of the Mad Cat’s torso. The rest of the ‘Mech had already been painted in the Dreadnought
the Mad Cat’s canopy. BattleCorps’ signature black and red livery, and a protective clearcoat would be applied later. Neither were his concern.
He had done his part.
“It was you on Basalt? In the Deva?” Adrian hissed the words through his teeth as his jaw clenched almost painfully.
His heart was pounding in his chest as an adrenaline rush pulsed in his veins unlike anything he had felt in years. Standing up, he stretched out, realizing how stiff his muscles had become from sitting and painting for hours on end.
He immediately regretted the swift action, his vision growing sparkly as he rapidly became lightheaded. He leaned forward
“Yes.” The metallic voice answered flatly. “Yes, it was.” and braced himself on the railing, gripping it hard even though he was in no real danger of falling off. He waited for his
vision to clear before reaching down to pop open his water bottle and take a nice long drink. A little bit of the ice he had
Adrian suddenly found himself unsure of what to say. He was surprised by how stunned he felt. Part of him had been put in the bottle when he filled it was still solid, thanks to the bottle’s vacuum insulation, the ice audibly knocking around
looking forward to this moment for years, but now that it was upon him, he did not know what to say. inside the bottle as he drank.
The short moment of silent stillness was broken when the Mad Cat suddenly began to move, the Blakist MechWarrior Capping the bottle and wiping his lips with the back of his left hand, he looked over his paintwork. The image of the
must have sensed Steele’s conundrum and chose that moment to bring his weapons to bear on the larger ‘Mech pinning naked, kneeling, winged demon girl looked back at him with a teasing, sly grin, one arm covering her breasts and the
it. The Mad Cat’s torso-mounted laser stabbed at the underside of the Sumaire’s forward-thrust chest as one of the Mad other reaching down to cover between her legs, her body wreathed in flames. The number sixty-six to the left of the
Cat’s legs kicked at the larger machine’s right leg, trying to break free. flames, with another six hinted at behind them. Roughly the same image was mirrored on the other side of the ‘Mech’s
torso, also just to the rear of the cockpit canopy.
Adrian simply squeezed his right-hand trigger in response.
Satisfied with his work, Adrian gave the Mad Cat a parting pat and whispered, “Take care of her, you hear me?” With
The cockpit and head section of the Mad Cat pinned under him at first seemed to collapse, before bursting into an a sigh, he walked away and made his way over to his awaiting Sumaire. As he suited up and then climbed into the cockpit
instant fireball under the assault of the Sumaire’s lasers. of his powerful OmniMech, he continued to reflect on the Mad Cat that stared back at him from across the bay. He could
not really grasp what it was about his old ‘Mech that had captured the hearts and minds of so many others, regardless of
The Mad Cat instantly froze mid-struggle, as though stunned. A few seconds later, it relaxed back onto the tarmac, its what Shandra said, but he honored her request that the ‘Mech be repainted in the livery with which he had piloted it for
body going limp as its fusion heart automatically shut down and its limbs lost power. so many years. He only knew about his personal connection to the symbol that she had so specifically requested he
recreate. He had never meant to create an iconic image, and to him it was still just a representation of his thoughts.
He stared at the decapitated ‘Mech under his Sumaire’s foot for a long moment in silence. He had hoped to feel a sense
of triumph or at least some form of catharsis in killing the man who had taken the Mad Cat from him. Instead, he felt Regardless, now that he had elected to give the Mad Cat to Shandra, that part of his life was finally over.
nothing. If anything, he felt a sort of cold emptiness within. What lay before him was just one more dead hostile.
He toggled in his powerup command and the gentle, feminine artificial voice of the Sumaire spoke up, “Voice print
“Major? Are you okay?” Ann’s voice filled his helmet. “We need to fall back to reload and repair.” recognition and security code, please.”
He took a deep breath, held it for a moment, then exhaled slowly. He was still trying to comprehend his feelings on the He took in a deep breath through his nose and exhaled softly, “I am Major Adrian Steele. I have bent my Demonesses
matter that had just been decided as Ann’s voice cut through the red mist that had descended upon him, causing him to to my will. They stand with me. Gods help whoever stands against me.” The last sentence was not actually a part of the
again become aware of his surroundings. password, but simply something that made him smile inwardly. As the Sumaire’s fusion-powered heart thrummed to life,
he could feel the awakening ‘Mech become a sort of extension of his body through the direct interface system connected
“Major Steele?” Ann repeated, concern entering her voice as her Neugen moved up on his right side. “Adrian? Are to his right arm.
you—Oh.” She said softly as she recognized the Mad Cat still pinned under the Sumaire’s foot.
Adrian’s Sumaire stepped away from the gantry, turning to depart the Acala III Military Academy Mechbay and head
Melissa’s Atlas stepped up to his left. “Wow.” Melissa piped up as her Atlas looked down at the felled ‘Mech. “I never for Castle Ramsay, the Dreadnought BattleCorps’ central headquarters, leaving the Mad Cat behind.
thought I’d see that again.”
He swallowed dryly. “Hostile eliminated, Colonel.” The emotionally drained Adrian sighed as he lifted his Sumaire’s
foot free from the incapacitated Mad Cat.
A button on the communications panel started to flash, indicating a private channel communication request. He tapped
the flashing button to acknowledge.
“Hey, are you alright?” Ann Lawrence’s voice soothed his mind, even in her worried tone.
“I’ll be fine.” He said, noting that his voice sounded almost mechanical, so drained of emotion was he. “We can talk
about it later. For now, you lead, and I’ll follow. Come what may.”
She at least found some modicum of respect among the garrison forces there, as more than half of them seemed to be
a collection of former bondsmen from virtually every Clan, though she was the only former Nova Cat. No one else could
truly understand her way of thinking no matter how hard they tried. Only a handful even attempted to try, and even they
soon gave up on the attempt. Those who did attempt to understand her thought process did at least become her friends,
and this included Star Captain Jorge, the commander of the garrison.
Lieutenant Asya’s Quarters With nothing to do aside from the constant drills put through by Jorge, Asya allowed herself to revert to her Nova Cat
Officers’ Residences, Acala III Military Academy ways in secret. The Star Captain did inevitably discover her pastime obsession but did little to get in her way so long as
New Sydney she was present when ordered. Whenever she could, she disappeared from the barracks and go on a vision quest. For
Acala III nearly three years it seemed that she was to be denied any chance of even glimpsing what her Nova Cat heart so yearned
1st January, 3080 to see. In late 3059, all her efforts were finally rewarded.
Asya’s thoughts of the past were interrupted when the door chime to her quarters rang. She stood up and straightened
“... just by being who you are. It has made my life worthwhile. I would like to take this opportunity to thank you dearly her uniform. She did like the BattleCorps uniforms better than anything that the Clans had to offer. They were the perfect
for everything you have done—especially for keeping an open ear for what I have to say. blend of utility and comfort while maintaining some modicum of subtle fashion. So many of the Clan uniforms either
chafed or were far gaudier than was practical.
“See you at the memorial ceremony tonight, my friend.”
“Enter.” She spoke aloud.
Asya’s fingers danced effortlessly over the control panel to end the trivid recording, type in a signature line and send
the message. She leaned back in her chair sighing softly and, in an unusually long moment spent thinking of the past, she The door opened, revealing arguably the most beautiful woman of the Dreadnought BattleCorps. A being of astonishing
found herself thinking about how challenging the last two decades had been. From there she began to reminisce about beauty with an appearance that promised seemingly unbridled sexuality, Asya thought to herself. It was unClanlike to be
her entire life. She thought of how many different uniforms she had worn in her life and how each had marked her so envious of another person’s physical or sexual endowment, but when Melissa was around it was somewhat difficult to
differently. avoid the feeling. Asya unconsciously looked down at her own chest for a moment, but she quickly shifted her gaze to her
desk and reached for a small data tab when she realized where her mind had drifted. She was grateful that she could not
Decanted as a genetically engineered warrior of Clan Nova Cat, Asya had been ‘born’ in 3032. A thin woman for a feel her cheeks burning.
warrior, she was not expected to be successful. Those around her were kinder than they would have been in other Clans
in terms of expressing such expectations, but she knew the truth. With her peers expecting failure she surprised many of “Sorry I’m a little later than intended.” Melissa purred with a sly grin, “Though I’m guessing you already knew when I
them by becoming a successful MechWarrior of Clan Nova Cat. She gained great respect and at one point was considered was going to show up, huh?” She winked salaciously, removing any sting from her barb.
a Ristar—the Clan term for a “Rising Star” within their ranks. Her reflexes had been honed to the point where it seemed
as though she surely had to see the future given how naturally and deftly she seemed able to avoid her opponents’ With a warm smile, Asya offered a seat and Melissa took it, her body moving with a catlike grace that Asya could not
attacks. help but appreciate. One glance at Melissa and Asya had all but immediately known what the taller woman naturally was:
a seductress. Among the most dangerous aspects of Melissa was that she had been trained so well that, even if her target
The truth of the matter was one only known to her and her Oathmaster. She had failed in her vision quest after attaining were aware of what she was, she could work herself so that most simply did not care. An equally dangerous facet of hers
the rank of MechWarrior. The vision quest was Clan Nova Cat’s effective rite of passage, whether ending in success or was that she seemed to be as adept with seemingly any known weapon as she was with her own body. She was even a
failure, into becoming a MechWarrior within the Clan. Clan Nova Cat was mocked by the other Clans that did not believe certified Aerospace pilot in addition to her primary role as a MechWarrior. This combination of astonishing appearance
in the validity of the visions of the future granted by a successful vision quest. Within the Nova Cat ranks, warriors who and equally astonishing skillset had granted Melissa Tor, a woman that Asya was grateful to be able to call her friend, the
had had successful examples of such vision quests were held in high esteem. Such individuals had guided Clan Nova Cat callsign of “Melter”.
in many ways over the centuries. Asya aspired to be one of the great seers within the Clan. She was denied any such
vision. Asya became obsessed with repeated attempts at a vision quest in her free time. She also became obsessed with Melissa had made it clear that she knew well just how important Asya’s contribution to the BattleCorps was, though
honing her fighting abilities further than any of her peers, despite already being considered by many to be superhuman. she had never said it in so many words. Over the years, Asya had begun to suspect that she may be the only person that
Melissa could truly open herself up to.
In 3054, it seemed that her efforts had all been for naught. In a Trial of Possession with Clan Smoke Jaguar, she was
defeated and taken Bondsman. She was severely wounded in the battle. She suffered, among other less life-threatening Melissa had been severely injured in 3069 on Basalt IV during an evacuation mission. The Dreadnought BattleCorps 1st
injuries, a high-speed impact to the head by a piece of flying debris as she ejected from her exploding ‘Mech. That the Regimental Combat Team had been deployed to safely evacuate members of the parent corporation, Dreadnought
debris had not killed her after puncturing through her neurohelmet and fracturing her skull just above her right eyebrow Interstellar, as well as the local DefenseCorps company there. It had been the last of eight such evacuation missions. It
was nothing short of miraculous. was also the only one of the missions to go horribly wrong. The Word of Blake had struck before the evacuation had been
complete and circumstances had required the BattleCorps forces to wage a standing defensive battle on the surface of
Her recovery took two months and required a sizable piece of sculpted carbon fiber be grafted to her skull above her Basalt IV while awaiting transport off-world.
right eye. While it faded over time, there was no question that she would bear the substantial scar marking her defeat
for the rest of her life, both physically and mentally. During the fighting, Melissa’s Atlas had been crippled. A direct hit to the head of her ‘Mech had damaged her ejection
system and left her with severe lacerations from shrapnel that would have instantly killed or at least maimed most. When
Unlike the Nova Cats, the Smoke Jaguars did not tend to bother with quality plastic surgery for sake of appearance. she attempted to eject after her disabled ‘Mech caught fire and ceased functioning, the ejection system had
Melissa had already been genuinely afraid of fire to begin with, but this had created a phobia that affected her to date. Melissa looked at Asya for a long time in silence, her eyes looking to be on the verge of tears but suppressed just barely.
She had suffered second and third degree burns to her back as a result of her ejection seat catching fire before Colonel “You know, for someone who was once a member of the Clan Warrior caste, you seem to know a lot about matters of
Ann Lawrence could sweep her up in her old BattleMaster’s hand while Adrian Steele had put himself at great personal the heart.”
risk to maneuver his old Mad Cat as a body-shield to protect both Melissa and Ann. The bond between the three of them
was tangible, yet it was never fully expressed. “A fair observation.” Asya allowed herself a small grin.
That was why Asya had called Melissa to her quarters before the memorial ceremony. “Yes, well. If I knew that, then I After another long pause, “That’s it? That’s all you’re going to say?” The signs of Melissa’s tears were fading but now
would likely have something clever to say in return, would I not?” Asya smirked. She did so enjoy the verbal jousting her brow was marred with confusion.
matches, though she could not let herself be drawn into one at this time.
“As someone who was once a member of the Clan Warrior caste, I say, ‘Aff’.” Asya’s grin grew wider.
Melissa picked up on the lack of sarcasm instantly, despite Asya’s best efforts, her brow furrowing in concern, “Is there
something wrong?” She asked softly as she leaned forward, her ample breasts squeezing together a bit within the just- “Oh, come on, that’s not fair at all!” Melissa whined. “You never really speak of your past!”
too-tight constraints of her uniform as she placed her elbows on her knees and clasped her hands together.
Asya reached out with her other hand and placed the small data tab in Melissa’s hands, “Never say never.” She smiled
Asya locked eyes with hers and offered a weak smile, “Changes are coming.” warmly. “Just promise me you will wait until after the ceremony to watch it.”
Melissa let her head hang limp, her long flowing hair cascading over her hands and forearms, “I’m not going to like it, Melissa took a moment to recover from the sudden shock that she might be about to learn of her friend’s past. “I... I
am I?” promise.” She smiled warmly, squeezing the data tab in one hand while squeezing her friend’s hand in the other.
Asya reached forward and placed one hand on Melissa’s own, “Seldom do we ever truly enjoy every facet of change, Looking at her wrist-comp, Asya noted the time as 16:48. “On that note, we had best get going. The memorial ceremony
but we must embrace the good parts of change.” She could see that Melissa was not convinced when their eyes met will be starting soon.”
again, “This change is for the best. If you trust me at all, please trust me when I say that.”
“Alright, then. I’ll see you there!” Melissa said as she stood up just quickly enough that certain parts of her body jiggled
Melissa’s brow furrowed, and she looked the smaller woman from head to toe, then shrugged with a smile, “Well, you pleasantly. She really was trained to the point where every little movement was perfectly executed, even if she did not
haven’t done me wrong, yet.” Melissa gently turned her hand over and clasped Asya’s own hand gently. mean to. Asya was unsettled at the thought that nearly all of Melissa’s natural mannerisms were dictated by her training
in espionage and seduction. She understood that these were common tactics in the Inner Sphere, but these tactics were
Asya smiled warmly, giving her friend’s hand a squeeze, “Nor shall I ever. I cannot promise that it will be painless, unthinkable, if not deplorable to someone raised in a Clan society. While Asya strongly respected Melissa, and even had
because that would be a lie, but it will be better in the end.” to admit some modicum of unusual envy of her friend’s physical appearance, part of Asya genuinely pitied Melissa.
Melissa took in a deep breath, her chest jutting out that much more before she let out a loud sigh, “Alright. I trust you. “Indeed. And again, promise me—swear to me—that you will go to see them tomorrow.”
You’ve helped me get back on my feet after my injury. You helped me get my confidence back.”
As Melissa stepped through the door, she nodded as though speaking to a nagging parent, “Yes, yes. I promise!”
“More importantly, I helped you get back into a position to be alongside those you care about most.” Asya spoke just
a bit softer, looking straight into Melissa’s eyes. She saw the taller woman’s cheeks redden slightly and knew that this Asya sighed, then smiled, “Alright. I will see you in a bit.”
was her one opportunity.
Melissa paused for a moment, as though seeing something in her friend’s expression. She seemed to think better of it
“I... I mean, I do care about them. They’re my friends and I–” and smiled back. She then turned to walk away, and the door automatically shut behind her.
“And you wish that they were far more than that.” Asya interjected. Asya looked around her quarters and saw the Dreadnought BattleCorps crest adorning her dress jacket’s back as it
hung off the back of another chair. Her thoughts drifted back to the moment in December of 3059, when she had had her
The taller woman’s blush deepened. Asya knew that she had hit her mark just as she had planned. first successful vision quest. At a cliff’s edge high above the small garrison base she had sat for three days and nights
without food, water, or sleep. The only time she had averted her gaze from the flames of the carefully created campfire
“I’m not sure whether that’s...” As Melissa started to speak, Asya could see just how vulnerable her friend looked. It had been to retrieve more wood to feed it further. Members of other Clans would mock her for trying to damage her
was the first time since Melissa’s injury that she had seen her like this. eyes, but it was the only way she knew how. Lacking an Oathmaster to carry out the ritual properly, she had to improvise.
“Melissa. Promise me something. Tomorrow morning, at 09:00, go to them and tell them how you feel.” At the point of exhaustion where hallucinations began to set in and her body felt ready to collapse, Asya had seen it. A
vision of such clarity that it could not be denied. Her mind was presented with the vision of a great gray jaguar being slain
The tall woman’s goldish-red hair was framing her equally reddened cheeks as she looked at Asya, her mind clearly by a wide array of warriors in different colors. Out of the corner of her eye, she spotted what looked like the jaguar’s
reeling as she was so suddenly confronted with her own feelings. shadow beginning to move on its own and suddenly it formed into an entirely new shape as it escaped from view. Black
panthers materialized before her, looking as though they were without guidance or purpose, before a great dragon being
“I don’t think it’s—” escorted by a large bird wreathed in flame swooped down from above, startling the panthers. After staring at one another
for a time, the dragon turned and the panthers moved up alongside it, where the dragon then spread a wing over them.
“Proper?” Again Asya cut off her friend, leaning forward with a warm smile. “Since when have the matters of the heart
ever been proper? All three of you have sacrificed for each other more than can ever be put into words. Adrian and Ann The fire crackled and suddenly it looked as though she were seeing a hand of cards. The cards suddenly dealt
The only remaining operable JumpShip left the system with the
requested equipment. After that, all JumpShip traffic and incoming
messages from Huntress mysteriously ceased, making the interstellar
communications blackout on Pantheress absolute. Only a damaged
JumpShip was in-system, and it was incapable of making an interstellar
jump without replacement parts, itself. The Obsidian Jaguars quickly
became restless but there was nothing that they could do.
After a couple of months, Asya began to feel that she was considered
a bad omen by some of those around her. Her friends had thankfully
stayed by her side and prevented matters from escalating too far. She had
had to fight a few of the more outspokenly critical amongst her fellow
warriors in Circles of Equals but had found no challenger that she could
not overcome.
By April, none dared challenge her, and some even began to wonder if
there was something to the vision she had spoken of. The longer the
communications blackout went on, the more it seemed the members of
the Obsidian Jaguars began to genuinely believe that the first piece of her
vision had come true, and that the ‘Great Jaguar’ that she spoke of was
Clan Smoke Jaguar itself being destroyed.
Then came the day in June of 3060, when the Dreadnought BattleCorps
had come to the world of Pantheress. Asya herself had been present in
the communications room when the first communique had come through
from Colonel Ann Lawrence aboard a WarShip named the D.B.C. Phoenix.
The dragon-headed crest of the BattleCorps had been displayed
prominently above and behind the Colonel as she explained that the
warring factions of the Inner Sphere had banded together under the
banner of a new Star League to execute the complete annihilation of Clan
Smoke Jaguar. Lawrence then stated that she wished to lay claim to the
In the center of the main hall, with a vaulted, stained ferroglass ceiling,
lay the memorial for which the hall was named. The memorial sculpture
of the late D.B.C. Trinity, the Dreadnought-class Battleship that had been
lost to an attack by the Word of Blake in 3075. Nearly every crewman had
a separate name plaque with their rank, birth, and death dates. There
were several blank plates, each one denoting a crewman that did not have
their own plaque because they had been recorded as having turned traitor
in the Trinity’s Black Box.
Her left hand ran over the display gingerly. She was surprised when she
felt a faint static electric shock as her index finger touched the name of
one specific plaque. Feeling that something was wrong, she looked closer.
The plaque that had shocked her was that of one Sergeant McKinney,
Kayla. She did not know why, but the name felt as though it should not be
there. It felt as though she was being attacked just by looking at it. She
quickly withdrew her hand and looked away. It was not her place.
She again felt the weight that had seemingly lifted from her shoulders
minutes earlier begin to press down on her.
Asya headed for the auditorium of the massive building. Upon entering,
she spotted Colonel Ann Lawrence on the stage giving a speech
commemorating the events of Operation LANCASTER, three years prior.
No doubt the speech was stirring and would pull at the heart as it always
seemed to whenever Ann spoke like this. Part of her wished that she could
hear the words, to be soothed by them and have the burden on her
shoulders eased.
She meandered over to the stage entrance on the right, then slowly
walked up onto the stage as the Colonel continued to speak. Asya felt
almost all the eyes shifting from Ann Lawrence to her as she slowly
approached the podium that Ann stood at. She met Ann’s eyes and could
see the confusion in her expression even as she continued to speak the
prepared speech. Asya gave Ann a sad smile as she remembered how
much Ann hated giving speeches.
For a brief moment, there was a red glowing dot of a sniper’s laser sight
on the Colonel’s forehead. As Asya stepped in front of the Colonel, the dot
disappeared.
For but a fraction of a second, Asya believed she could actually feel the
sniper’s laser sight aimed at the back of her head.
“No, I suppose that is a bit too formal. This is a message from a friend and colleague, rather than a subordinate.
“If you are seeing this message, it means that I am no longer among the living. I am sorry for the sudden departure, but
what happened was necessary. I sincerely apologize for not being able to warn you of what was coming. That too was
necessary. Necessary for you. Necessary for the BattleCorps. Necessary for the future of all.
“As you may expect, I will not dwell too heavily on the past, as the future is always where I tried to look while I was
among you. It was not always so, but with you I was able to find my true calling. The true calling of my Nova Cat heart.
“While I do understand that not everyone believes that I could glimpse the future, I would like to believe that the
outcomes of my efforts have been evidence enough of the sincerity of my claims over the years. I have never told you
this, as I did not wish to create doubt in your heart, but before the vision that I had prophesizing your arrival on Pantheress
all those years ago, I had never once had a vision. My original Clan will likely never know of what happened and my part
in it, which is for the best I suppose.
“With my passing, I must inform you that Melissa Tor will now be needing your tender care and guidance. She has had
feelings for you and Adrian both for quite some time. Feelings that she has suppressed subconsciously because of... Well,
you know her true history. You and I both know that she is a much older soul than any would suspect. At her core she is
still a woman, despite what she may be under the skin, and she is understandably genuinely afraid of rejection, given that
it has been a long time since she has been involved in any kind of truly deep relationship.
“I know how the three of you feel about one another, but I also know of the difficulties you and Adrian have had trying
to reach out to her. I now ask you to take her into your arms. She will likely take my passing rather hard, but with your
help, she will be stronger and more devoted to you than ever. I have no doubt that the three of you together will be able
to conquer every trial that awaits you.
“You know me well enough. I have never done anything to harm you, and I would in fact lay my life down without
hesitation if it meant saving yours. In fact, I suppose if what I believe has come to pass by the time you receive this
message, I will have done just that.
“Grieve if you must, I know your heart will demand it, but do not fail to use this opportunity for what it is.
“I offer you my final vision as the last guidance I can give you: ‘With her warriors gathered before her, the mother
dragon shall speak. Though loyal, the majority of her warriors are not all of the same shade as she. Every one of the
warriors show shades of their individual pasts, setting them apart and causing friction amongst each other. A white-robed
darkness is among them. One who was once a white cat shall stand up before the mother dragon, blocking the white-
robed darkness just before it can reach the mother dragon, and in so doing, the white cat shall be slain. In that moment,
all of the warriors shall become one color, dragons all, and burn the darkness from their ranks. In that moment, the
warriors become one with the mother dragon’s will for the first time.’
“It is not a perfect explanation but, as I have told you before, the visions are not always the easiest to put into words.
I know you will make the right decisions even though I will not be there to offer further guidance.
“It has been an honor to serve you, Ann Lawrence. You have allowed my life to have meaning and have given me
For all intents and purposes, all human life in the system had been wiped out in a near-instant. On her orders. The final
Colonel Ann Lawrence’s Quarters death toll was well upwards of ten thousand people, not including the Word of Blake attackers. She did not bother to
Castle Ramsay, Dreadnought BattleCorps Central Headquarters count the Blakists. While she understood that many of them were people simply on the wrong side of a conflict, she had
Outside New Sydney no way to know how many genuinely wanted her people dead just because they were not following the path supposedly
Acala III laid out by Jerome Blake.
27th May, 3085
It was “common knowledge” that the Word of Blake was to blame for the nuclear destruction that occurred in June of
3075 in the Waycross system. It was not above the Blakists to nuke their own forces in the process of attacking an enemy
As she walked through the entryway into her personal quarters, Colonel Ann Lawrence reached to her left to tap the force, especially if it seemed that the Blakists were going to lose. This was the great lie that she had had to live since the
ambient light control on the wall panel. The interior of her quarters illuminated warmly, in defiance of the darkening moment that the nukes had been detonated on the surface of Theris and within CrossWays Station. She could count on
twilight outside. Even as the door closed behind her, she blindly tossed her lightweight uniform jacket up onto the wall- one hand the number of people that knew the truth. Even the intelligence divisions of the Great Houses and Comstar
mounted coat hanger. She heard the jacket landing on the floor, but she did not bother moving to pick it up. She did not could not have found it, because the information gathered had been forever deleted, and only three people had ever
even bother to look. seen it, including herself. The other two were from the Dreadnought BattleCorps’ only other WarShip at the time, the
D.B.C. Phoenix: Colonel Kai Kelderman, the Phoenix’s commander, and Lieutenant Kazumi “Kazu” Koto, the ship’s
She slumped back against the door and stared at the floor through teary, unseeing eyes. There were times when she communications officer.
wondered how her father had dealt with the pressure without letting it show. She then reminded herself that there were
certain things that she had to deal with that he never had. She wondered how he would have dealt with them. In her Lieutenant Koto had sworn herself to secrecy over the matter, and she later took the secret with her to the grave.
mind’s eye, she believed that he would have simply shouldered the burden and carried on. He had always said that he Much to Ann’s dismay, Koto took her own life just two years later, following the events of Operation LANCASTER in 3077.
had a strong back. Only afterward did Ann discover that Koto’s lover, an aerospace fighter pilot attached to the Phoenix, had perished in the
fighting late during the final battle in space. Koto had left a private message for Lawrence, saying that she forgave the
This day had marked the tenth anniversary of the day known as “Trinity’s Fall”. A decade prior, the Word of Blake had Colonel for what had happened, understanding the reasons for each of Ann’s actions and orders. Koto went on to state
attacked the world of Theris, otherwise known as Waycross II. Theris was a world of great importance not just to the that while she did not understand where the nuclear weapons used on Theris had come from, she knew that they had
Dreadnought BattleCorps, but to the whole of Dreadnought as an entity. The world had been under a continuing not been used by the Word of Blake. She also assured Ann that this critical secret was safe, and that she had told no one.
evacuation for roughly a year prior to the incident. At the time, Theris still had thousands of soldiers and nearly twice as Knowing the honorable woman that Koto was, Ann felt she could trust her at her word. For security reasons, the message
many civilians waiting their turn to leave the world—a turn that they would never get. had long since been deleted, but Ann would never forget it. The circumstances around the message ensured it was burned
into her memory for all time.
Ten years ago, to the day, the D.B.C. Trinity, the only Dreadnought-operated WarShip available to defend the world,
had stood her ground against a squadron of Blakist Corvettes. Not only was the Trinity ancient and outdated, but she had Colonel Kai Kelderman, ever the professional, understood exactly why Ann had done what she did. He rightfully did not
been sabotaged and damaged internally prior to her encounter with the Blakist vessels. The crew of the Trinity had like the outcome, and he did not envy her position, but he understood. At that point, he was the only other living person
performed admirably, but betrayal from within resulted in the ship’s destruction. The Trinity had been lost with all hands. who knew the origin of the nuclear weapons: they had been in cold storage since their discovery within the depths of
More than seven hundred souls had perished aboard her. CrossWays Station decades before either of them had been born. Likewise, he was the only one aware of her orders in
early 3075 to unseal the weapons and transport five of them to the surface of Theris as a precaution, leaving two in the
The month following the loss of the Trinity had been nothing short of hell for the Dreadnought DefenseCorps Theris station to ensure that even if one failed, the station would still be destroyed. The only other people who had known the
Regiment. Orbital bombardments. Systematic annihilation. Public executions. Torture. The Word of Blake had made those truth of the nuclear weapons had been killed when the weapons were detonated by those very people. It was Kelderman
who were too stubborn to die suffer for it. In less than two weeks, the DefenseCorps Theris Regiment had lost two-thirds himself who had ensured that the recovered data from the satellite could never be found by anyone else. The only existing
of their personnel, and much of their equipment had been crippled. The survivors held on for roughly two more weeks copy of the data aboard the Phoenix had been physically removed from the databanks and destroyed. Meanwhile the
after the initial slaughter of the DefenseCorps’ main forces. Most of the survivors bottled themselves up in the bunkerlike satellite that had recorded the information was triggered to autodestruct.
massive underground structure that was the Cameron MechWerks facility and there they held the line as well as they
could. Meanwhile, the rest of the surviving DefenseCorps personnel worked to conduct guerilla raids against the Indeed, it was public “knowledge” that it was the Word of Blake that nuked everything of value and killed everyone in
temporary bases that the Word of Blake had set up. The cover of a long blizzard, weather typical of the ice world of Theris, the Waycross system. The truth that forever burned at Ann was that she was responsible. It was a lie she had to live with
had made their actions easier, but blinding weather was always a double-edged sword that complicated any operation. every day. It was easy to assure herself that it was the right decision, but she had to live with the knowledge that her
orders had caused the deaths of thousands of people, so many of whom were not even involved in the fighting, with
The communications logs recorded on a single remaining Precognition Type-VII Tactical Satellite in orbit over Theris nearly all of them never even understanding in their final moments what was happening or why.
indicated that all of the remaining DefenseCorps personnel had worked toward executing Colonel Ann Lawrence’s final
standing order: Should the defenses against the Word of Blake fail altogether, the Word of Blake were to be denied access She still occasionally had nightmares that derived themselves from the images she had seen of the utterly destroyed
to the facilities in the Waycross system. By any means necessary. The classified portion of these orders, only known to city on Theris, the ruined structures and the burned shadows of those who had died in the nuclear hellfire. Her nightmares
the highest-ranking personnel of the DefenseCorps Theris Regiment expanded upon this standing order: the release and had her walking among the dying, flames consuming everything and everyone around her before the nuclear shockwaves
When she was still a child, Ann had once asked him if he hated her for
being what killed her mother. His response still pulled at her heart: “If I
hated you for that, I would have to hate myself for falling in love with her
and wanting to have a child with her. And if you feel hate because you feel
love, you can never truly feel love.” He went on to say, “Do I miss her? Of
course, I do. But every day you’re alive, a part of her lives on in a very real
way. So, if I hated you, I would not only hate myself, but I would have to
hate her, wouldn’t I? I still love her with all my heart, and I always will.”
His voice cracked for the first time that she could recall as he added, “And
I love you just as much, Annie. I want you to remember that.”
Years later, her father brought up her question and told her, “Never
hate someone for what they are or how they came to be. Only let yourself
truly feel hatred of another if they’re someone who consciously chooses
to do things that make them worthy of that hatred. Never hate someone
for something they have no control over.”
She gently placed the framed holograph back on the mantel, her fingers
running down along the side of the frame. She remembered how her
father had kept this very holograph and frame on his mantel at home
when she was younger, among a collection of things that she never quite
understood until she was considerably older. Though she would never
know the specific meaning behind each of the objects on her father’s
mantel, she at least knew why he kept them and why every year, he spent
time just looking at or holding them in silent solitude. She knew that she
would forever wish that she could have known the woman who had so
firmly captured the heart of her father, as he had credited her for much of
who he was.
What surprised her most of all was that only the last two opponents
had been any sort of challenge for her. She was stunned to later discover
that her final opponent had previously won a championship that had
Soon after she discovered that her arrival had been quite literally prophesized with impressive accuracy, albeit in a Lawrence had told Lankenau—and later stood by her word—that the BattleCorps would not firebomb whatever they
rather abstract manner, by a female member of the defense garrison on Pantheress VI: a former Clan Nova Cat did not take with them, instead leaving everything left behind intact for the Snow Ravens.
MechWarrior named Asya.
The later surprise of Dreadnought standing by their word had been nothing compared to Lankenau’s surprise
After a bloodless Trial of Possession that Dreadnought’s representative had won, the Pantheress system and all its immediately after the conclusion of the trial, upon discovering that the chess set that the ‘Colonels Ann’ had been playing
inhabitants were officially considered to be the property of Dreadnought under Clan Law. The patch had been gifted to on had in fact been a relic from the Star League that Dreadnought had recovered over a century prior, claimed personally
Ann by Star Captain Jorge, the commander of the Smoke Jaguar garrison on Pantheress, as a symbol of the capitulation by her grandfather. It had been difficult to keep from laughing when, after Lawrence announced that the chess set had
of the Smoke Jaguars. The Smoke Jaguar warriors were collectively taken Bondsman. Jorge had been her personal once belonged to General Aleksandr Kerensky himself, the man often referred to as the “Grandfather of the Clans”,
Bondsman, as was her right as commander of the force that had defeated the defenders. She gently ran her fingers over Lankenau looked as though she was about to pass out. Lankenau’s face had turned pale as a ghost. When Lawrence had
the bondcord next to it, smirking slightly. Three pieces of nylon rope that had been cut with her combat knife in then stated that she had chosen to gift the chess set to Lankenau, the Snow Raven Star Colonel had been completely
accordance with Clan tradition, each at different times when Jorge had proven himself to be a worthy asset. gobsmacked. When Lankenau finally regained her composure, she first slipped into declaring that Lawrence had to be
lying, but Lawrence rebuffed it by simply pointing out that she was leaving the chess set for her to have, and that Lankenau
It had not taken long. could have it analyzed, herself.
When she had asked Jorge why he and his forces had so quickly sided with Dreadnought when they arrived, he Before Dreadnought’s departure back to the Inner Sphere began in 3064, Star Colonel Ann Lankenau had surprised
explained that he wanted his life to count for something. His Clan was dead, and there would be nobody to remember Colonel Ann Lawrence by arriving once more in the Pantheress system, but instead of declaring some form of additional
any sacrifices made on behalf of the Smoke Jaguars by his people if they were to lay down their lives to defend a world trial, Lankenau arrived under guarantee of Safcon—the Clan term for safe conduct—to meet with Lawrence in person.
that would surely be taken piecemeal by another Clan in the near future even if they had defeated Dreadnought in a Once the two were able to speak in private, the Star Colonel confirmed that the chess set had indeed been General
military engagement. He admitted that even if he had emerged victorious, he had his doubts that Dreadnought would Kerensky’s own, though one of the pieces had been replaced with a near-perfect duplicate: the white king. Lankenau then
hold to the agreement and simply depart after losing. Ann’s forces were not of Clan upbringing, after all. insisted on having a rematch with Lawrence, setting up a chess board that she had brought with her. As Kerensky’s own
Lawrence had slowly, gratefully taken the piece of beautifully crafted metal from Lankenau and held it respectfully, In September of 3069, the Dreadnought BattleCorps 1st Regimental Combat Team had been engaged in a defensive
inspecting it. Lankenau then dropped the bombshell that had she had been waiting the entire time to say, “It was first battle on Basalt IV. It was Ann’s first taste of hell. She swallowed dryly, remembering the feeling of utter helplessness as
worn by Khan Stephen McKenna himself when he founded Clan Snow Raven in 2804.” she tried desperately to keep the BattleCorps’ defensive line from collapsing under the relentless assault from the Word
of Blake’s 55th Shadow Division. She and a Corporal that she had selected to be her stand-in Tactical Officer, as the man
Lawrence recalled feeling shocked and completely speechless. She also remembered nearly dropping the pendant as who normally performed the duty had been severely wounded, were trapped in the partially collapsed cockpit of her
though it had bitten her. Her expression must have been quite remarkable because Lankenau was visibly fighting back a disabled BattleMaster. The Corporal, a man who wanted to be a civilian air traffic controller, continued to work tirelessly
grin. “Y-you’re serious?” Lawrence remembered finally managing to force the words out with a stammer. to not only keep her from dying from blood loss, but to help her command the unit despite clearly being scared out of his
wits.
Lankenau looked at the pendant, then at Lawrence, dragging out a long silence for several seconds before finally
breaking into a grin, “No, I could not secure such a thing, I am sorry. But I wanted to return the favor in at least some She had nearly lost both of her lancemates—her closest friends at the time, though they later became so much more—
small fashion. While the original pendant that Khan Stephen McKenna wore is very much safe and secure on Lum, this is in the fighting on that world. Melissa Tor had been critically wounded days prior when her Atlas had been crippled in a
in fact a later version that was crafted for Khan Stephen McKenna during his final years as Khan. This one is far lesser- vicious firefight. Adrian Steele lost his prized Mad Cat and nearly gave his life to buy time for other members of the unit
known, and I was able to… Convince the right individuals to allow me to have it for this purpose.” to drag her gutted BattleMaster with her onboard onto the DropShip. It had been the only time that Adrian ever defied
her orders. He had refused her order to stand down and get to the DropShip, and to leave her behind.
Lawrence could not think of anything more to say than to thank Lankenau and state how honored she was to receive
such a symbolic gift. Lankenau had then leaned in and stated in a soft voice, “You have made something of an ally. And In a matter of days, she herself had nearly died, her closest friends had nearly died and much of what was important
as most of the Clans—most certainly we Snow Ravens—are not prone to saying such things, do not take those words to all of them had been lost. If only she had known that the Corporal was himself mortally wounded. Instead of tending
lightly.” to himself, he had tended to her wounds and ensured her survival. Even as Ann had screamed for Adrian, panic mixing
with the realization that she loved him, a brave Marauder pilot named Michael Fawkes had taken it upon himself to block
The two continued to converse for some time, but eventually it came time for Lankenau to depart. After saying their the Mechbay entrance ramp and door with his own ‘Mech to give Adrian cover fire so that he could run from his disabled
farewells and beginning to go their separate ways, Lankenau had suddenly turned on the boarding ramp for her DropShip, Mad Cat to the DropShip on foot. The Marauder absorbed numerous direct hits from weapons fire that otherwise could
shouting in a boastful, challenging tone, “Remember, Colonel Ann Lawrence! I will find you again, and I will have that final have struck personnel, ammunition, or fuel inside of the DropShip. She vividly remembered watching as the gutted
piece!” The Snow Raven maintained a stern expression for several seconds, Adrian Steele beginning to grow visibly uneasy Marauder fell back away from the closing door and Adrian dove into the bay even as the DropShip began to ascend.
next to Lawrence. Only then did Lankenau’s expression soften, and she gave a playful grin as she slowly turned to continue
boarding her DropShip. Only then did Ann relax and look back to the Corporal. Only then did she realize that he had been silent for several
minutes. He had apparently died just as the BattleMaster had been dragged onto the DropShip. It was through that event
Ann’s thumb gently felt over the textured metal of the pendant, her mind gradually coming back to the present. “I that she learned to never take the loyalty of her subordinates for granted. To date, she never felt that she truly had, but
wonder if we’ll ever really meet again.” She sighed, mumbling the words just barely aloud. “I honestly hope so.” The it was something that she consciously strove to keep in mind, ensuring she never would from that point forward.
thought that they might not ever get to finish their little saga saddened her slightly, but it did not stop the smile that had
curved her lips as she set the pendant back on the mantel. She had allies in strange and unexpected places. The She would never forget what the Corporal had done for her and those under her command. Nor would she forget who
importance of that fact would never be lost on her. it was who had taken his life so early. She would also never forget his name. It was a name she would later ensure that
the Word of Blake would never forget, either, for as long as they existed.
Her smile shrank rapidly as she looked at the next object on the shelf, freezing up with her fingers still touching the
Snow Raven pendant. She took in a deep breath, her chest rising before she let out a long sigh. It surprised her how much Successfully fighting back the tears that threatened to well up in her eyes once more, she gently ran her free hand
it hit her every time she laid her eyes on the next object on the mantel. A sealed canary yellow envelope with her name down along the chain to grip the dog tag. She already knew what it said, but she wanted to see it, anyway. As she turned
handwritten on it. Her hands shook slightly as she looked at it. Dust had collected on it over the years, as she had never the dog tag to read it, the light caught the silver metal such that it flashed a direct reflection of the overhead light into
touched it since she had put it there. Long-dried blood stained the envelope as she stared at it, the tears that she had her eyes for a fraction of a second, leaving a momentary afterimage of the dog tag’s shape. The afterimage was distorted
forced back earlier welling up in her eyes and distorting her vision. by the areas on the piece of metal that were stained with long-dried blood. She stared through the afterimage to read
Melissa had at first refused to believe it, and for a short time felt a sense of betrayal. After a few days to mull over the It appeared that an oxygen line had been severed and was combining with some form of fuel source to create quite
information, she had come to accept it and had moved past it, their relationship only deepening in the end. Adrian had the impressive temporary flamethrower. It was only because of the intense fiery light that she noticed movement all but
meanwhile simply seemed to accept it at face value, surprising Ann. At first, she thought he was blindly following his love directly below the flame.
for Ann, but after discussing it with him further, it was clear that he saw the truth behind the importance of the deception.
She was only barely conscious of the presence of her lancemates Adrian Steele and Melissa Tor next to her as she
The hatred toward the Word of Blake had made Operation LANCASTER possible, and if others had blamed Ann for the bolted for the technician. When she spotted the technician, he was being slowly cooked alive by the continuous flame.
deaths on Theris as she herself did, then Dreadnought would likely have consumed itself from within. Most importantly, She pulled shut the visor of her armored pilot suit’s helmet and started to climb over the ruined and tipped scaffolding.
her choice was a sound tactical decision that, while she could not have foreseen the long-term outcome, was the right She vaguely remembered Steele and Tor both trying to stop her, but Lawrence knew that there was nobody else equipped
choice. Eventually, Melissa agreed with Adrian wholeheartedly. They also both agreed that the deception had to be to handle the inferno-like conditions long enough to rescue the trapped man before he was burned to death. She did not
maintained, as the possibility of Dreadnought tearing itself apart from the inside was still a very real threat if the truth remember her exact words, but the order that she barked at them immediately got her lancemates to cease trying to
came out—especially after so long. The support the two offered Ann was something that she had desperately needed. stop her and start trying to help.
Adrian had put it bluntly when he said, “What’s done is done. Now we have to live with it.” While the words had stung It was only with hindsight that she could perceive Melissa’s reluctance, despite her outward lack of hesitation. Given
at first, he had been absolutely right. She had known it, but hearing it said in so many words had helped her to strengthen the woman’s past experiences and general phobia of fire, throwing her into that situation was something that Ann still
her resolve. felt bad about to this day. At the same time, Ann was so proud of Melissa for facing her greatest fear in that moment.
Ann also knew, in hindsight, that Adrian was primarily coming along to ensure that Ann did not get herself killed. He surely
Ann took in a deep breath and let it out with a sharp exhale. She put the tube and dog tag back on the mantel before wished to save the trapped man as well, but Adrian had made clear that his loyalty and top priority was Ann’s wellbeing,
reaching up to gently run her hand along the largely mangled dedication plaque for a long moment in silence. Again, tears both on the battlefield and off. Though now that loyalty most certainly included Melissa as well, both Adrian and Melissa
threatened to burst forth from her eyes, but she refused to let them. She sniffed back what felt like the beginnings of a agreed that Ann was always to come first if either of them had to make a choice in a firefight.
runny nose consciously, realizing that she had already done that multiple times. She turned and retrieved a tissue from a
nearby desk table to blow her nose. Tossing the used tissue into the dust bin under the desk, she slid the box of tissues The three of them managed to free the trapped MechTech. Although he had suffered second and third degree burns
over to the corner of the desk so that she could reach them without moving from the fireplace. Feeling a slight chill, she to his arms and one leg, the technician was alive and made a near-complete recovery after significant surgery. All three
flipped the switch to trigger on the gas fireplace before turning back to the mantel. MechWarriors had come out of the event with suits that had distinctly seen better days. Melissa’s suit was mostly intact,
but her back showed thermal damage. Thankfully, she herself was alright. Adrian’s suit was much worse for wear, having
She looked over the dedication plaque once more before moving to the next piece. As her eyes came to rest on the charred his upper body and even burned through his suit’s right arm around his elbow. Having never seen his prosthetic
medallion and fabric strap it was attached to, it seemed almost fitting that the fireplace lit up behind the glass protector right arm damaged before that moment, seeing the melted synthetic skin and exposed myomer underneath had been
in front of her. The medallion rested atop a metal clipboard holding several pages’ worth of names on a list. The pages shocking to say the least.
were wrinkled in several places. More dried tears.
Adrian being Adrian, he simply shrugged it off, though she could tell he was displeased that everyone who saw him in
She picked both pieces up together and lovingly ran her fingers over the hand-crafted crest that made up the medallion that condition suddenly were aware that he had a prosthetic limb. Given the lengths he had gone through to keep that
itself. The familiar snarling dragon head over a shield and crossed swords seemed to look back at her as she stared at it. fact under wraps, she felt for him. Her own suit was on the verge of thermal insulation failure by the time she escaped
The fabric strap bound to the metal medallion was not the typical kind of decorative material used for such things. It was the flames, with much of her upper body’s protection buckled, cracked, and melted off, and only the innermost layer left.
singed military grade fabric that had once been used in the construction of a Dreadnought-BattleCorps-issue armored If she had stayed in the flames even a fraction of a second longer, it was likely that she would have had a failure like Adrian
pilot suit. had, and she did not have a single bit of prosthetic in her, so it most certainly would have been far more unpleasant for
her.
Her suit, in this case.
Thankfully, replacement suits were able to be sourced out after a brief medical checkup, and the three of them were
During the latter portion of Operation LANCASTER, in January of 3077, Ann had pulled her company off the front lines able to rejoin the fight after the tech crews finished the work on their ‘Mechs.
In her guilt-driven state, she chose to go through the list and confirm the dead, herself. She went through, one by one, As a pair of tears dripped down onto the papers on the clipboard to create new wrinkles to add to the old ones, Ann
torturing herself by ensuring that she saw the faces—or, in some cases, what was left of the faces—of those who had gingerly set the medallion back on the clipboard and placed it all back on the mantel. She began to feel slightly faint, her
died because of her command decisions. By the time she was nearly done, she was an absolute wreck. With fifty- body feeling weak as the same lump she had felt in her throat while on the stage all those years ago formed once more.
something names left on the list, she got to the body of a DropShip crewman whose corpse was tagged as number 57, an She braced her trembling hands against the mantel to steady herself, leaning forward and down to let her head hang low
eighteen-year-old private who had just finished training and been put into service two weeks prior to the initiation of as she let out a soft sob of raw emotion.
Operation LANCASTER. She read the boy’s name and she collapsed into a
heap, sobbing, while Adrian and Melissa tried to comfort her.
The name listed for corpse number 57 was Private Lancaster, Jonathan
F. She had not been aware of his posting to this mission, but she already
knew that he was Edward Lancaster’s younger brother. She found out
later that Jonathan had insisted on being assigned to a position where he
was under her command as soon as possible, mainly because his older
brother had spoken so highly of her.
She made sure to keep the clipboard and list of casualties for the entire
Lancaster Coalition intact and together as a second, painful reminder to
never take the loyalty of others for granted.
When she got to the end of the stage, the Triton crews surprised her
by presenting her the unique, hand-crafted medallion. In that moment,
that one singular act had saved her from what felt like falling into an
abyss. The technician that she had saved had been the one to place the
medallion’s strap over her neck as the crews presented it to her. She
easily noticed that the man still showed scars on his arms from the burns
he had sustained, and had lost a finger from each hand, but the way he
smiled was the thing that she remembered most about him. It was a
beautiful smile. Until the moment that she had been surprised with that
medallion, she had felt like she had done nothing but fail those under her
command. In that moment, as the crowd erupted in cheers suddenly and
loudly enough to make her jump a little, she realized that those under her
command felt differently about her than she felt about herself.
She had indeed begun to cry as she concluded the ceremony, which
was something she had only done in full view of her soldiers the one time
before, but this time she was smiling through the tears. None of her
previous experiences could compare to what she felt in that moment.
She picked up the framed holograph of herself, bandaged along her neck from where a would-be assassin had In that embrace, Ann felt safe, secure, and happy. “I’m better now.” She said softly, enjoying the warmth and comfort
attempted to slit her throat with a vibroblade, only to be body-checked by an Acalan dragon. It had been extremely painful of the two embracing her even as the smell of the pizza began to make her mouth water.
and genuinely terrifying for her at the time. Looking at the holograph in her hands, where Koree, the dragon that had
saved her, was licking her cheek, and making her clearly laugh aloud as he did… It was difficult to believe that it was just While Asya’s final message had indeed been a message seemingly from the great beyond to remind Ann that she must
minutes after the traumatizing incident had taken place. It was nearly as difficult to believe that it had already been seven be the leader that her people needed, it was also a clear reminder that she was not alone.
years since the event took place.
Many of those under her command, most especially the former Smoke Jaguars, could not help but at least consider it
something of a small sign that Koree was an extremely rare example of Acalan dragon: he was black and red in color. This
meant that not only was her savior of the same species of winged reptile upon which the Dreadnought BattleCorps’ crest
was based, the color of his scales also matched the signature livery of the unit. Koree later became something of a mascot
for the BattleCorps, and he quickly became arguably the most popular dragon on Acala III.
She kept the candid holograph of Koree and her together to remind herself that even in the middle of a moment of
terror and pain, there can exist a moment of perfect joy—and that she could and should savor those moments, regardless
of their context.
Ann turned to look through the large armored ferroglass sliding doors at the side of her quarters to see Koree curled
up outside. The big dragon was sleeping comfortably out on the large, softly lit balcony. He was twitching slightly in the
midst of a dream. He had earned a good rest. He had been by her side or watching over her all day. She needed to make
sure that she rewarded him with some kind of special treat later. He deserved it.
Ann’s eyes had just begun to dry up as she turned back to the mantel to place the holograph back where it belonged,
but immediately felt them begin to well up once more when she saw the final pair of objects at the end. The two pieces
went together as parts of the same story.
One was a piece of Lieutenant Asya’s uniform that had been cleanly cut and presented to her by Jorge after Asya had
been killed, putting herself in place to take a Word of Blake assassin’s bullet meant for Ann. The black piece of cloth had
sewn to it two patches, one being the simple name “LT ASYA” with the smaller text under it “WILDCARDS BATTALION”.
The second patch below it was the standard Dreadnought BattleCorps uniform patch. Both patches were red trimmed
over black backgrounds, with dried blood turning parts of the red insignia and letters a darker shade of red.
Next to the piece of dried-blood-spattered, patch-decorated cloth was a data tab that contained Asya’s final message.
The message that, as it was delivered the day after Asya’s death, had seemingly arrived from beyond the grave. The
patched piece of uniform she kept as a grim reminder of just how important she was to those around her, and how far
some of them would go to safeguard her wellbeing.
The message itself was a powerful message to be the leader that the BattleCorps needed. The message was also a
reminder that—
The door chimed twice, breaking her train of thought, and she knew that it was Adrian and Melissa. She had been
expecting them, but not for another few minutes.
She heard the door open softly and the two stepped inside. Adrian was carrying a large pizza box while Melissa carried
drinks for the three of them. Both saw the signs that Ann had been crying before she could even think to play it off. They
Through the BattleTech International Facebook group, I met artists Matt Maeda and Alan Blackwell, the awesome guys
who later become the unit crest designer and the cover artist for this project, respectively. I’m still amazed that Mr.
Maeda (at least at the time) was doing custom art designs for basically a “pay what you want” amount. Please, if you
commission him for anything, pay him well. His work is worth it!
Colorado As for Alan Blackwell, well… Keep an eye out for that “AB” signature in newer BattleTech art, and you will know it was
North America Mr. Blackwell’s work. Beautiful stuff, that man’s work! Feel free to contact and commission him, he is great to work with!
Terra
2 October, 2021 I have met so many friends through this project, many of whom are not mentioned in this note. My sincerest apologies
to those who are not mentioned here, because if I did, this little “bonus” might wind up being several pages of nothing
but gushing gratitude!
For anyone who has made it this far, I sincerely hope you have enjoyed this monumental project. Especially the short
stories! I know that the most detail-oriented people will surely be able to pick this apart for inconsistencies with canon, Now, with this rant being put to an end before it becomes far, far too long, onto the reason I added this entire article
but I assure you that every effort has been made for Operation Lancaster be able to slip into the canon BattleTech universe in the first place—to show some of the creative processes behind the project’s art and visuals (and the inspirations for
without “rocking the boat” too much. Is it “perfect”? No, and I hold no illusions that it ever really could be. However, this some of it) as it evolved to become what is presented in Operation Lancaster. I hope you enjoy!
is the story that I wanted to tell, and I really hope that those who take the time to read this truly enjoy it for what it is.
To say that Operation Lancaster has been a passion project would be a severe understatement. In a very real way, this
project is why I am still alive, because when I hit one of the lowest points of my life, the dogged desire to complete this
project kept me going—and it prevented me from making a very dark, very permanent choice. It may sound silly in so
many words, but yes, I have BattleTech and my desire to see this story told to thank for still being alive today to write this
personal note.
So, as a small bonus, I decided to add a small peek “behind the scenes” at some of Operation Lancaster’s artistic
development process. This project “properly” began in 2017-2018 as a fan-TRO (Technical Readout) just for kicks. It was
meant to be a way to have a bit of fun background lore for some custom designs I used in my local tabletop gaming—
little did I know how much this would snowball.
Sitting down and writing this, it is difficult to say where it truly began. Arguably it all started with my first contact wit h
Jason Spykerman, an excellent 3D miniature artist and someone that I am grateful to call a friend. It was through the
discovery of his store on Shapeways, Orbital Heavy Industries, that I met Jason. I contacted him (rather unnecessarily, I
admit) to ask if he was alright with me using one of his models—the Neugen—as a custom ‘Mech for BattleTech tabletop
gameplay. This was the beginning of a great friendship, and it led to more than just using a handful of his existing designs
in this project. Our collaborative effort to create the Sumaire was arguably the first domino of the project proper, because
it started me working on creating a couple of “fan-TRO” articles. The Sumaire would be far from the last custom design
that he created for me, though. The Ravage and Ravage II, Steel Cobra, and Ceòlmhor would follow. I feel it is fair to say
that this project would not have happened without Jason’s help, and he has my eternal gratitude. (Thank you, my friend!)
My exceptionally good experience with Jason soon inspired me to poke around and ask other artists if they would be Lending a Hand
willing to allow me to use their designs in this fan-project. Most of my experiences were quite positive, with people like
Shane Smith (Sandman Artistry) and Kirk Alderfer (Arbron Imagineering) being examples of such positive interactions. Pictured: An early concept sketch by Devin Ramsey,
depicting what was planned for Major Adrian Steele’s
Arguably the luckiest find, however, was Michael Szita. He ran a Shapeways store called Metal Core Collectibles. His prosthetic hand. It was going to play a more overt role in
designs were at the time rather basic, but he had one design that had caught my eye. (Amusingly, said design did not the character’s life, but in the end, this idea was later
actually make it into the project, but it is shown later in this section!) Little did I know that this would turn into an awesome abandoned for a more “natural-looking” prosthetic. The
long-term friendship and a fun journey collaborating to design many miniatures. It has been an amazing experience to idea that Adrian genuinely did not want most of those
work with him over the last few years to create the lion’s share of the all-new designs presented in this project, and to around him to be aware of his prosthetic added a little
witness his designs evolve into the excellent miniatures they have become. Without Michael, this project would not be depth to the character, and it seemed a good fit.
what it is today—and I am forever grateful for his willingness to contribute so much time and effort to this project.
It was unfortunate that these were unable to be worked into the project
as it stands, but at least they can be included here! These images were
commissioned by Donald Butler, and they were created by an artist
named Austin Schumaker.
Center Top: Profile image for Lieutenant Colonel Michael “Mike” Jordan.
Right: College-era sketch by Devin Ramsey featuring a custom “Glitter Girl” power armor suit, created for use in the tabletop RPG game
“Rifts”. This was used by Matt Plog as a reference when he created the illustration of the Vixen Light Battle Armor.
Below: An art piece by Devin Ramsey during his High School years featuring a concept of the “Vector Storm VI” motorcycle. This would later
be redesigned by Matt Plog into the beautiful beast of a sport bike presented in this project.
Yes, Devin is aware he failed to depict the motorcycle as having any kind of brakes.
Black-Water WIPs
The better part of two decades later, these finally saw the light of day once
more, when they were used as concept art by Jason Spykerman to create
the Ceòlmhor Heavy Battle Armor’s 3D-modeled miniature.
Tyrannical Evolution
Pictured: “Before and after” renders of Michael Szita’s Tyrant BattleMech from different eras of Mr. Szita’s work. On the left, the “Proxy War”
version of the Tyrant that was once sold on Shapeways. On the right, the redesign of this model that took place as a collaboration between Mr.
Szita and Mr. Ramsey (one of many!) in preparation for its inclusion in Operation Lancaster. This miniature, as with the rest of Mr. Szita’s miniatures,
is available from his store, “Metal Core Collectibles”—which can be found here: https://www.metalcorecollectibles.ca/
Devin is extremely proud and honored to have been significantly involved in the design on the left becoming the design on the right!
Left: Two different angles of the Steel Cobra. These art pieces were
by Devin Ramsey during his high school days.
Devin did not draw this fighter with BattleTech in mind, hence the
almost absurd armament. The name of the craft was partly chosen
because it was Devin’s MechWarrior 3 callsign/handle (hence the
logo), and partly because it was designed with twin rotary cannons
that were imagined as rising from the upper-sides of the fuselage
much like a cobra’s hood.
Pictured: A beautiful set of final renders of the Steel Cobra Heavy Aerospace Fighter
by Jason Spykerman. This design evolved considerably from Devin Ramsey’s original
art, but most certainly for the better. The fighter has an instantly-iconic silhouette that
clearly follows the ideas presented in the original art. While the body of the fighter
may look busy, it is designed with greebles that all make functional sense, including
the reload mechanisms, downward-aimed VSTOL assist jets, offset main gun, armored
landing gear housings, and numerous multidirectional reaction control thrusters.
Left: A render of the “Neugen Type B Late Production Model” miniature by Jason Spykerman. This was the first
miniature design by Mr. Spykerman that Devin Ramsey discovered on Shapeways. If not for this model, it is
entirely possible that the two would never have met, and Operation Lancaster may never have been created.
Thank you so much for allowing this to be used here, Jason! The Neugen Assault ‘Mech certainly is a beast!
Below: A render of a mecha model by Michael Szita, called the Torrent. This was the design that Mr. Ramsey
discovered on Shapeways that put him in touch with Mr. Szita. It is almost a shame that this was never used,
but things like the Oryx, developed years later for this project (and for sale on Mr. Szita’s website) simply fulfilled
the role so much better than what had been planned for this machine.
However, just because it was never updated for use in Operation Lancaster, that does not mean that all hope to
see a revised/higher-detail version of the Torrent is lost. Michael will surely be creating plenty more miniatures
long after Lancaster is done and released for his own purposes. This may yet be one of them!
Pelvic Flamers
Something of a small internal running joke in this project that may irk some and amuse
others is the pelvis-mounted anti-infantry weapons in a few Dreadnought ‘Mech
designs (Ravage, Lancer, Sumaire and Neugen). You have Jason Spykerman to thank
for this particular “pseudo-anatomical” feature. His reasoning is that you should never
take this stuff too seriously, and he is right about that. To be fair, however, even if you
do insist on taking this stuff seriously, there are actually plenty of reasons why this
particular mounting location works, as is explained in the lore, but the bottom-line is:
“If you’re not taking full advantage of every part of a chassis, you’re doing it wrong.”
Below: Original concept art of the Borealis-class DropShip, created by artist “Project Dark Fox” for Chris
“Thunderhead” Wailes to use as the basis of a 3D-printable model. This was designed to serve as both a
proxy of the canon Aurora-class DropShip as well as its own class of DropShip—hence its inclusion here!
Top-Right: A render of the finalized Borealis-class DropShip model by Thunderhead—in this case, the
“BattleCorps” variant that was used as a reference by Matt Plog for his illustration of the vessel. This is a
3D-printable supportless FDM ‘Mech-scale model that is fully playable as hex-based terrain. It features
articulated doors and interchangeable “pods” to allow the model to represent different variants.
Bottom-Right: Renders of other variants of the Borealis. From left-to-right: liquid transport, ‘Mech
carrier, cargo carrier, and aerospace fighter carrier.
The Thunderhead Studios product line (including the Borealis itself, once it is added to his new site) can
be found here: https://www.thunderhead-studio.com
Heads of Hammers
Left: A render of Michael Szita’s older “Proxy War”-era “Hammerhead” model, which was once available
through Shapeways. Like his early Tyrant model, this was made to be printed with Shapeways’ least-
expensive plastic, hence the low detail.
Right: A render of the revamped version of Michael Szita’s Hammerhead model. To say this was quite
the transformation would be a near-painful understatement.
Small side-note from Devin: It was planned to keep the name “Hammerhead” for this machine. However,
because of the recent introduction of a canon ‘Mech by that name—annoyingly it was introduced after
this miniature had gone on sale on Michael’s store—the name for this design was given arguably the
laziest change imaginable. It was changed to the German word for “hammerhead shark”: Hammerhai.
Above: A prop rifle made from scrap parts by Devin Ramsey. This
was used as the basis for Matt Plog’s illustration of the PAARR-
15/GL Infantry Assault System. The prop itself was built using a
Super Soaker XP 75 as the base, with the upper part of a Nerf
Defender T-3 added to the front. A part of an old Transformers
toy and the face of an old computer case formed the top-rear
section. Radio Shack “Lazer Shot” laser tag targets were used as
the “power packs” on the sides, while a couple pieces of PVC
pipe and some clamps—tipped with an internal part from the
Nerf gun—were used to create the “scope”. A duffel bag strap
was added to make it a usable cosplay prop.
Devin freely admits that the fact that art college annihilated his
artistic muse altogether unfortunately shows quite painfully for
all to see, here.
Pictured: Various renders of the Ravage Light OmniMech modeled by Jason Spykerman. Although it is nearly identical to the later Partial-
Wing-equipped Ravage II, this “first-generation” Ravage OmniMech—and its visually near-identical in-universe predecessor, the Guardsman
Light BattleMech, which was admittedly added later—features a conventional torso design and later included a slightly different armament.
Some Things Get Used, Some Get Redone, Some Get Neither
Above: A design that was created accidentally by Matt Plog. Yes. That can, in fact,
happen. It was an honest and entirely innocent mistake. This was the result of two
different designs being accidentally getting blended into one, just because they
were both on the same commission list. In this case, it was the Maxim-based Fire
Hunter Firefighting Vehicle and the Heavy LRM Carrier’s SRM Refit. For a long time,
somehow making this work was considered, because it looks terrifyingly awesome,
but eventually the idea was dropped because it unfortunately just did not work on
paper. Unfortunate indeed.
Right: The original version of the art depicting the D.B.C. Phoenix battling the
squadron of Blakist WarShips during the latter half of Operation LANCASTER. It was
decided that the Phoenix did not look “beat up” enough and the image was edited
to better match the scene described in the final text.
Right: The first sketch created for the Blackjack known as “Aces High”. This was the one-and-only instance during this entire project where the ‘Mech
depicted was vastly different than expected. However, most of the building blocks for what eventually evolved into the final design are present, and
it did not take long at all to get it turned into the machine presented in the Technical Readout article.
Below: The initial sketch of the Berserker known as “Crossbones”. Almost the entire design was approved. However, much of the left arm needed to
be redesigned, as the Berserker does not have a left hand actuator.
Bottom-Right: The first sketch for the Cobra Patrol Vehicle. Were it not for the fact that one of the priorities for the art featuring this machine was
placed on having a direct representation of Michael Szita’s miniature design, this may well have been approved, as it does lo ok good in its own right.
Unfortunately, Mr. Plog had to go back to redraw almost the entire hull and turret. The final result, however, is excellent!
Sometimes designs need more than one attempt to get right. For the record, however, out of the frankly ridiculous number of art pieces that Matt
Plog created for this project, something like 90% of the initial sketches that he created required little or no modification before being given the green
light to move on to finalizing. A total of two—yes, just two—sketches were altogether rejected out of everything that Plog did for this project. (Yes,
this includes the epic-looking missile carrier on the previous page!) That’s roughly 1%. These are some of the examples of designs that needed great er
reworking. For the record, these are not included to mock Plog in any way, shape, or form! This is all just a part of the development process.
Below: A render of the original Reckoning miniature design. This was a redesign of an existing model
called the Goliath, which was originally was designed for printing and sale on Shapeways by Michael
Szita.
Right: Matt Plog’s illustration of the original Reckoning Assault ‘Mech design. He did what he could!
The Reckoning was the very first bit of collaborative work that Michael Szita and Devin Ramsey did
together, and it was—comparatively speaking—quite rough around the edges. Even though it made
for quite the interesting miniature design, this was before the two had developed much of the design
language that was used going forward. As a result, this early version was relegated to the past, and
it never received a production model miniature—at least, not before it was completely redesigned
from the ground up! Interestingly, the Reckoning Assault BattleMech literally ended up being both the
first AND the last miniature that Devin and Michael worked on together for Operation Lancaster.
Pictured: The “Mammoth” spacecraft model by Michael Szita that would become
the basis for the Mammoth/Mammoth II JumpShip. Mr. Szita’s original design
featured the ability to dock plenty of modules along the spine of the vessel, which
is what inspired the first-generation “Colonial JumpShip” version of the Mammoth.
The original plan for the art—at least as it was proposed to Matt Plog—was that
the second-generation Mammoth II would replace the docking ports along the sides
of the ship’s spine with a sort of rotating tube-like structure that DropShips would
dock to. However, Plog’s idea of instead adding twin attachments at the sides of
the vessel’s bow was immediately embraced as it felt more interesting and much
cleverer.
Above: The original Critical Rocket logo designed by Kat “Grumpy Kitteh” (Tim
“Critical Rocket”’s significant other).
Below: A proposed redesign of the above by Matt Maeda that, in the end, was
not used. (Thank you anyway, Mr. Maeda!)
A Reimagined Legacy
Above: A 3D model render of a reimagined version of the canon Legacy Assault BattleMech. This model was
designed by Aaron Swickard, AKA “IonRaptor”. When IonRaptor created this model—albeit not originally with
this customized armament—it led to this ‘Mech becoming a late addition to this project. The render shown
includes the special weapons package created to represent the custom variant in Operation LANCASTER.
Right: Matt Plog’s depiction of the customized LGC-03 Legacy Assault BattleMech, given the nickname
“Whitehead” by the Dreadnought BattleCorps when it was fielded by the Word of Blake’s 55th Shadow Division
during Operation LANCASTER—later renamed “Isorla” after its capture and subsequent refit by the Dreadnought
BattleCorps. This is an alternate version of the illustration featured in the Technical Readout article for the ‘Mech,
showing it in its Word of Blake 55th Shadow Division livery.
This was a rather interesting situation where each artist informed the other. IonRaptor had redesigned the Legacy
to his own taste. However, when it came to creating a custom variant just for this project, it was decided to
include a pair of the powerful capacitor-boosted Clan particle cannons created just for the Word of Blake’s 55th
Shadow Division’s “Divinus” configuration Celestial OmniMechs. Matt Plog had already created a very specific
design aesthetic for these weapons when he drew up the custom Celestial OmniMechs for this project. As a result,
to keep the aesthetic consistent, IonRaptor ended up recreating the weapons that Plog had designed. Then, after
the 3D model was completed, it was used as the reference for Plog to create the illustration for it. The final
product of this collaboration speaks for itself: It’s awesome!
Pictured: The Word of Blake 55th Shadow Division’s version of the Mad Cat known as
the “Demoness”, by Matt Plog. The Word of Blake’s revised version of the Demoness
featured slightly different torso-mounted secondary weapons, and this illustration
reflects those alterations.
The Mad Cat known as the Demoness was Devin Ramsey’s first personal ‘Mech, and it
was piloted by his player-character Major Adrian Steele long before thoughts of
making anything remotely like this project had occurred to Devin. Steele’s story was
not truly fleshed out and thought through until this project became a serious endeavor.
The idea that the ‘Mech itself could serve as a sort of nemesis for the character was a
natural evolution of Steele’s story, as is illustrated in the short story “Demonesses”. In
the hands of a Clan MechWarrior, this iconic machine nearly killed him. When the
Demoness was taken from him by the Word of Blake, after it had been a part of his life
for decades, it hurt him deeply. Years after resigning himself to never seeing it again,
when he faced the Demoness once more, well… Read the short story to find out!
Left: Early concept art by Devin Ramsey that served as the basis to inspire the Sumaire’s design.
Right: The first concept sketch by Jason Spykerman depicting his first attempt to capture the
essence of what the Sumaire would become.
Below: Renders of Jason Spykerman’s final design of the Sumaire Assault ‘Mech. To say that this
design evolved quite a lot is an understatement. It was not intended to become a Mad-Cat-
esque design, but it evolved in that direction inadvertently. However, although this evolutionary
path was not planned, it did serve as something of a plot point in the short story “Demonesses”.
As an aside, this lovely—and lethal—Assault ‘Mech is what it took to finally push the Mad Cat
down from its place as the best-looking ‘Mech ever created for BattleTech (even if unofficially)
in Devin’s opinion.
“You brought me the wrong package—I just wish I could keep it!”
Pictured: Matt Plog’s first sketch of the “Hot Drop” scene used in the short
story “Scars”. This is a wonderfully dramatic illustration with truly astonishing
attention to detail. Just one problem: The wrong ‘Mechs are leaping out of
the DropShip! The ‘Mechs that were supposed to be pouring out of this
DropShip are those of the Blackwood Templars Mercenaries, but instead here
we have machines belonging to the Dreadnought BattleCorps! This was, of
course, fixed in the final version.
This is arguably the most amusing goof to happen during the creation of this
project, and it is not included to poke fun at Matt Plog. On the contrary, it is
included because it looks awesome. Due to Devin’s affinity for the Sumaire
Assault ‘Mech (the ‘Mech on the right in this sketch), having to tell Plog that
he drew the wrong ‘Mechs was one of the most difficult things for Devin to do
after seeing how epic the Sumaire looked leaping of a DropShip like this.
Left: The Hounds of Artemis, both the unit and their crest created by Brian Crosby. They were planned to play a larger role in
Operation Lancaster, but it was decided in the end to have the smaller mercenary unit be a much more minor entry. In the end,
it was reduced from being an entire unit entry at the beginning of the project and a unique character/pilot entry to just the single
character entry—Grayson Ostego, pilot of a DII-HMD-BC1 Hammerhai Heavy BattleMech—and a few passing mentions of the unit.
Bottom-Left: An incomplete first attempt to create the Dreadnought BattleCorps unit crest by Matt Maeda. This design was later
considered for use as the Dreadnought “ShadowCorps” crest, but the fact that this covert organization within Dreadnought was
unofficial in-universe, the idea of having a crest for the organization made no sense.
Below: Matt Maeda’s second attempt to create the Dreadnought BattleCorps crest ended up being the design used to represent
the unit. It initially had slightly more flourishes around the shield (pictured here) than what exists in the final version. The curved
flourishes on the right and left were eventually removed to clean up the crest’s overall appearance, and some additional small
refinements were made before it was finalized.