Author Topic: Chronological BattleTech Fiction Review - The Succession Wars  (Read 488374 times)

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1440 on: 07 October 2016, 13:11:19 »
Date: June 5, 3025
 
Title: Technical Readout: 3025
 
Author: Blaine Lee Pardoe, Boy F. Petersen, Jr., Anthony Pryor, Dale L. Kemper, and Shaun Duncan (writing); Duane Loose and David R. Detrick (interior art); Dana Knutson (cover art)
 
Type: Sourcebook (FASA)
 
Synopsis:  

The TRO:3025 Aerospace fighter section presents three fighters for each Successor State – one light, one medium, one heavy.  These are supplemented by the six generic fighters from the AeroTech boxed set – the Sabre, Centurion, Lightning, Hellcat, Eagle, and Thunderbird.  I would presume these fighters were designed before the AeroTech ones, since the art for the TRO:3025 fighters appears in the boxed set, but without stats. 

Sparrowhawk: The Sparrowhawk, introduced in 2520, continued production through the fall of the Star League.  It is used as a first-response craft to engage enemy fighters.  House Davion appropriated the Sparrowhawk factories on Quentin in the First Succession War, but House Kurita subsequently bombed the plant out of existence.  In 2901, the 8th Sword of Light engaged a Davion task force in orbit over Errai, but were repulsed after the Davion Sparrowhawks drew off the fighter escorts, leaving the DropShips vulnerable to heavier Davion fighters.  In 2955, Davion Sparrowhawks outmaneuvered and outfought slower heavier Liao fighters in the eight-day “Great Lee Turkey Shoot,” leaving several dozen Liao aerospace fighters destroyed.  In 3019, Davion Sparrowhawks engaged Kurita Sparrowhawks in the Harrow’s Sun system.  The Kurita Sparrowhawks appear to be a copy of the Davion design, with a slightly different weapon package.  Robard Miller II was wounded in the Battle of Marquez, and now leads a wing of the Crucis March Militia.  His father accounted for over 40 kills at the Great Lee Turkey Shoot.  Canto Pete Williams serves in the 10th Deneb Light Cavalry, and has a lengthy combat history of battling Capellan fighters in the Algo I system. 

Corsair:   Introduced during the Star League Civil War to bolster SLDF forces in their fight against Stefan Amaris, the Corsair is designed for close-range assault, making it an excellent atmospheric fighter.  Most of the manufacturing plants were in Davion space after the fall of the Star League, but all factories were in ruins within five years of the war’s start.  Corsairs took part in the border battles that raged for Cylene between 2945 and 2953, supporting the Capellan March Militia invasion force.  In 2982, Corsairs destroyed the fighter escorts for a long-range Liao strike against Rio, forcing the DropShips to retreat.  In 3013, Corsairs used a Union disguised as a harmless derelict in the David system, launching from it and destroying the Kurita fighters that had thought to score an easy kill.  Dale Randolph Harrison was the mastermind of the subterfuge in the David system, and now serves in the Third Davion Guards.  Josh Wallace pilots his Corsair, “Winged Death,” in the Draconis March Militia.  Wilma Torrensilli was instrumental in defending the world of Bahr against a Liao attack.  She was promoted from the Bahr planetary garrison to the 3rd Crucis Lancers as a reward.

Stuka:   Introduced in 2530 from the Demeter-based Lycomb IntroTechnologies for the Star League armies, production ceased only when Liao forces bombed the plant in the First Succession War.  House Davion maintained a monopoly on production, so few were provided to other Great House armies.  When the 15th Sword of Light attacked Quentin for the first time in 2899, it was violently repulsed by Davion Stukas based there, ultimately leading to the formation’s dissolution.  In 2999, false information planted by House Davion led House Kurita to raid Kasai, believing it to be completely undefended, but they were actually hiding in an asteroid belt, and caught the Kurita fighters when they were low on ammunition and fuel.  A Davion Stuka captured by the DCMS in 3004 later appeared in service with Wolf’s Dragoons.  Karl Stephens pilots his Stuka, “Karl’s Krusher,” in the 1st Ceti Hussars.  Mark Allan participated in the 2999 ambush at Kasai, and now serves with the NAIS Training Cadre.  James Doogan pilots his Stuka, “Dark Death,” in Wolf’s Dragoons.  His kill record since joining the Dragoons is only considered “fair.” 

Sholagar: The Sholagar has served as House Kurita’s primary light fighter for much of the Succession Wars.  Its popularity has recently fallen due to structural flaws that make it instable in some planets’ atmospheres, making it safe to operate only in a vacuum.  Akiro Kurita, nephew of the Coordinator, died while patrolling the Skondia system in his Sholagar in 3002, prompting a review and rumors of a new light aerospace fighter to supplant it.  In 2989, Sholagars pursuing LCAF fighters broke up in Sevren’s upper atmosphere.  In 3011, at Arboris, Sholagars successfully protected Kurita DropShips on station in orbit from enemy attack.  Reggie “Hellraiser of Hesperus” Hotspurn and his fighter, “Daggerdisk,” have survived eleven raids on Hesperus II.  He commands the light fighters attached to the 3rd Pesht Regulars.  JoJo Faust and his fighter, “Amenders Die Hard,” serve in the 3rd Benjamin Regulars. 

Shilone:   The Shilone, known as “The Boomerang” by its pilots, serves as House Kurita’s primary medium fighter.  Its design has been unchanged since a structural problem was discovered in 2799 and corrected in 2802.  The fighter debuted in 2796, during the fighting for Kentares IV, when they helped Kurita DropShips punch through Davion interceptors and land unopposed.  In 2804, Shilones participating in the “First Battle of Barlow’s Folly” with the Third Dieron Regulars were caught on the ground while refueling and destroyed.  Arvin Chin and his fighter, “Deathspanner,” serve in the 5th Amphigean Light Assault Group, and is a top mercenary ace.  Sheila Utchakov commands the headquarters air lance of the 1st Sword of Light from her Leopard-CV carrier, “Hai Namb.”  She is responsible for the safety of all key command officers of the regiment, which is traditionally commanded by members of House Kurita. 

Slayer:   The Slayer predates the collapse of the Star League, and serves as an assault craft equally comfortable on offense or defense.  Heavily armed and armored, it has helped the Combine achieve orbital superiority in many conflicts.  Fielded against House Davion for the first time in 2786 at the Battle of Kasai, Kurita raiders targeting a supply depot were repulsed by stiff AFFS resistance, with only the Slayers scoring kills.  In the Fourth Battle of Harrow’s Sun, in 3020, McKinnon’s Raiders overran a Combine fighter base and rescued a captured AFFS pilot, who said he could pilot one of the captured Slayers.  The pilot volunteered to decoy another flight of Slayers as they returned to the overrun base, allowing McKinnon to destroy them.  The plot then went on to rejoin the fight for Harrow’s Sun, ultimately crashing his fighter into the hangar doors of an orbiting Kurita DropShip.  Hans Horshaw pilots his Slayer, “Death from Kboje,” in the 2nd Benjamin Regulars.  Dierdre O’Malluki pilots her Slayer, “Mother’s Gift,” in the 5th Sun Zhang Academy Cadre, and rotates out to support frontline units on the Davion border. 

Thrush: The Thrush serves in defensive garrisons and as DropShip escorts in the Capellan Confederation.  It has excellent speed, but minimal firepower, which serves to screen friendly forces or scout, but leaves it unable to effectively engage enemy fighters.  It has the same design flaw as the Sholagar, making it unstable in atmospheric flight.  In 2812, Thrushes escorting the 1st Kearny Highlanders in a raid on Demeter were unable to assist their charges when superior Davion fighters attacked the DropShip “Panohai.”  The entire 1st Kearny company was wiped out, and only one Thrust survived to rejoin the Panohai.  In 2786, a massed force of ten Thrushes overwhelmed a rogue ‘Mech lance on Sax.  “Smiling” Jack Winfield commands the 14th Sian Air Defense Squadron, and is in charge of the Sian Aerospace Training Command.  He is a veteran of the 2nd Capellan Hussars.  Uchita Tucker received bionic legs and a right arm after surviving the crash of her Thrush, “Juni Bell II.”  At the helm of a new Thrush, “Give’m Hell II,” she is called the Automaton of Destruction.  She has won 13 dogfight victories in her bionic state, including one where a piece of her bionic leg was torn off. 

Transit:   The Transit is House Liao’s primary medium fighter, mainly serving as a squadron command ship and providing close support for ground engagements.  Though it has decent armor and heavy firepower, pilots complain its profile and relatively slow speed make it a vulnerable target for heavier fighters.  In 3012, on New Berne, Transits were in the rear guard for McCarron’s Armored Cavalry ships, successfully holding back Davion ground forces while the DropShips loaded and departed.  In 3018, Transits in the 15th Defense Squadron on Carver V engaged four incoming DropShips.  In the orbital plane of Carver V’s three moons, the 15th engaged the Davion fighter escorts, which outmassed and outgunned the ten Liao fighters.  The Davions lost only one fighter and successfully raided the Liao storehouse on Carver V.  Seiji Smith pilots his Transit, “Usuali Wong,” as part of the Liao defense squadron on Kathil.  Giles Ashtibula pilots his Transit in the 4th Tau Ceti Rangers.

Transgressor: House Liao’s assault fighter, it escorts DropShips and is included in defense squadrons for particularly important planets.  Its heavy laser array and impressive speed make it popular with its pilots.  In 2992, Liao Transgressors won a 14 hour battle over Acala, enabling Liao reinforcements to reach the planet surface and reinforce the garrison.  The ground battle was lost nonetheless, but the Transgressors prevented Davion forces from pursuing the retreating survivors.  In 2998, at the Battle of Tybalt, the Transgressors of the 10th Defense Squadron destroyed the FSS Heraldic, when Captain Lyle Shumgawa rammed it and sent it tumbling towards Tybalt to burn up in the atmosphere.  Lucy D’Urban pilots her Transgressor, “Duelist,” in the 4th St. Ives Armored Cavalry.  She enjoys challenging opposing pilots to one-on-one dogfights, and has never lost.  Harry S. Yoshita, one of the Transgressor’s designers, pilots his Transgressor, “Harry One,” in the 6th Sian Defense Squadron.  He is trying to get his unit moved to the frontier. 

Cheetah: A variant of an older Star League design, the Cheetah is House Marik’s primary light fighter.  It serves well as a DropShip escort, swarming enemy fighters, and is often used for ground support as a bomber.  Limited fuel supplies keep it close to its mother ship, except for the reconnaissance variant, which removes its lasers for extra fuel tanks.  In 2828, on Xanthe III, Cheetahs engaged the Xanthe Resistance, which had armed itself with old Star League equipment.  They distinguished themselves bombing a resistance base at Green River.  In a battle against Steiner fighters over Rochelle II, Cheetahs used their superior maneuverability in the gravity well to drive away the LCAF forces.  In 2952, however, House Marik’s raid on Andorian V was wiped out by Liao Thunderbirds and Eagles, as the Cheetahs could not prevail against superior firepower.  Michael Pearce serves in the 1st Regulan Hussars, and has an ongoing feud with John “Mad Jack” Reynolds, a Steiner Stingray pilot, over their opposing religious philosophies (atheism vs. fanaticism).  Diane “Vixen” Virgil commands a 12-fighter mercenary aerospace squadron that has served in every successor state. 

Stingray: The Stingray is based on aerodynamic fighter models developed on late 20th century Earth, notably the forward-facing wings.  Both Houses Steiner and Marik produced the design, based on a Star League-era experimental model.  The nose-mounted PPC makes it unstable in atmospheric flight.  In 2905, in the Van Diemen system, Stingrays and Cheetahs engaged an invading Liao fleet at Van Diemen IV, destroying five DropShips before they could land, then served as ground support bombers, forcing House Liao to retreat.  In 2942, on Bella I, Marik and Steiner Stingrays clashed – with Steiner fighters successfully holding off the Marik squadron while the raid progressed.  John “Mad Jack” Reynolds pilots his Stingray, “Trust Jesus,” in the 11th Lyran Guards, and seeks out atheist Regulan Hussar pilot Michael Pearce whenever possible.  Maria Gutierrez is a Lieutenant Colonel with 22 kills to her name, but chafes at her current administrative role.  She is considering getting a voluntary demotion to return to the front lines.

Riever: The Riever is House Marik’s heavy fighter, with heavy armor, but only a moderate weapon payload.  It was designed during the Succession Wars, with the intent of being easy to maintain and keep in production as technology regressed.  Its primary role is to engage and destroy enemy fighters and DropShips.  In 2815, Marik Rievers were first deployed against House Steiner on Phecda III.  Design flaws became apparent, necessitating a slight redesign before they were again deployed in 2820 on Graham IV, where they put down a local rebellion sponsored by House Steiner, smashing rebel Hellcats over the North Kashak River Valley when the rebel attackers couldn’t breach the Rievers’ heavy armor.  Arthur Lohkamp is an instructor at the Marik Military Academy.  He is periodically recalled for combat duty. 

Seydlitz:   In 2504, the Star League called for a planetary defense fighter with great speed and light armor.  Shipil Company delivered the Seydlitz and put it into mass production on the world of Vance.  House Steiner seized most of the Seydlitzes when the Star League fell apart.  During the First Succession War, House Marik attacked the world of Megrez, but the Marik bombers were shattered by swarms of Seydlitzes, prolonging the battle of Megrez for three years.  The 10th Skye Rangers used their Seydlitzes to escort heavy fighter/bombers in a raid on Worrell.  In 3002, the Donegal Guards attacked Solaris VII (then under Marik control) and their Seydlitzes destroyed most of the Marik fighters on the ground at their Callow Mountains airstrip.  Donna Doolie pilots her Seydlitz, “Raider,” in the Donegal Guards.  Mark Jacobs scored fifteen kills in service with the 32nd Lyran Guards over Wheel, in 3014.  Doris Wichal destroyed two lances of Marik ‘Mechs from the Marik Militia’s Amber regiment while serving with the Arcturan Guards.  She now flies for the 6th Lyran Guards. 

Lucifer: The Lucifer was introduced in 2526, but recalled in 2528 due to structural problems.  It was produced in sufficient numbers to be the dominant medium fighter in Steiner space.  Pilots appreciate its heat dissipation capacity and firepower, but it is slow, and requires faster escorts to keep enemy fighters off its flanks.  In 2913, a Steiner Lucifer flight without escorts was crippled by Marik Militia fighters when it attacked Loric.  Steiner raiders using Lucifers attacked a 9th Regulan Hussars DropShip over Rochelle in 2945.  Lucifers guarding Saffell repelled a rare Liao raid in 2978.  A deep penetration reprisal raid on Bella I took massive internal damage from ammunition explosions and had to call off the attack.  Lucifers performed poorly in Thorin’s high winds when defending against a Kurita attack.  David Wordington, of Richard’s Panzer Brigade, once crippled a Union over Vega.  Lewellen Stewert serves in the Royal Guards, despite having been shot down in his Lucifer four times. 

Chippewa: Manufactured for the Star League, most Chippewas were recruited into the Lyran Commonwealth after the fall of the Lyran Commonwealth.  It serves as a front-line fighter, with both close-support and long-range fire capabilities.  House Steiner seized the Chippewa factory on Dell prior to the First Succession War, but the plant was destroyed by a Kurita raid.  In 2966, Lyran Chippewas used Lyons’ moon to hide and successfully ambushed a Kurita raiding party.  In 2987, House Steiner sent Chippewas on its “Deep Raid” to hit Ling, smashing the air defense units and clearing the way for the force’s ground units to destroy a BattleMech plant under construction there.  In 2991, a Marik retaliatory raid sent commandos to Wyatt to steal Chippewas for study, returning with four.  In 3012, during a Marik raid on Laiaka, a Steiner squadron was unexpectedly attacked by an Overlord and six heavy fighters, but Chippewa pilot Dan McCleary rammed the DropShip and crippled its engines, forcing it to crash on the planet below.  Hank McCleary is Dan’s son, and was the first recipient of the McCleary Award for Heroism for his actions over Alexandria with the Arcturan Guards.  Georgia Pitts flies her Chippewa, “Vulture,” in the 19th Lyran Guards. 
« Last Edit: 07 October 2016, 13:13:50 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1441 on: 07 October 2016, 13:15:47 »
Date: June 5, 3025
 
Title: Technical Readout: 3025
 
Author: Blaine Lee Pardoe, Boy F. Petersen, Jr., Anthony Pryor, Dale L. Kemper, and Shaun Duncan (writing); Duane Loose and David R. Detrick (interior art); Dana Knutson (cover art)
 
Type: Sourcebook (FASA)

Notes:

Sparrowhawk: Though the Sparrowhawk shares some design elements with the Harpy and Siren fighters from Crusher Joe (the split-wing tips, the intake vents above/behind and to the sides of the cockpit, and the two forward pointing prongs) it’s significantly different from them in many ways as well, which is one of the reasons it was never put on the list of “Unseen.”  The Samurai is a far more obvious clone of the Harpy, and is featured prominently on the cover of the AeroTech boxed set. 

While the writeup praises the Sparrowhawk’s arsenal and armor plating, it doesn’t have much more than speed going for it.  As I noted in my review of the “Great Lee Turkey Shoot” scenario, the game mechanics should have led to massive casualties among the Sparrowhawks, rather than a rout of the Liao fighters.

Algo I = Algol, surely.  Marquez is not a mapped system.  It may be one of the Davion outpost worlds, like New Cleveland, Hamlin, Ral, and possibly New Boston. 

Corsair: Bahr does not appear on any maps.  One of the moons of Imbros III is named Behr, but that’s up on the Combine/Lyran border.  It’s interesting that Torrensilli was promoted from a Capellan March planetary garrison (probably a secondary world or habitable moon in a mapped system) to a Crucis March Militia. 

The Corsair’s design was also heavily influenced by the Siren from Crusher Joe, though it is more rounded, lacks the rear thruster cone, and only has one dorsal fin instead of two.  The Samurai (which was made into a Ral Partha miniature, but only given stats in the Fox’s Teeth scenario pack) is a direct copy of the Harpy fighter. 

Stuka: Both Karl Stephens and James “Dougie” Doogan are name-dropped by the self-absorbed DCMS aerojock in “And Then There Was the Time…” from the Shrapnel anthology.  The reference to Doogan’s “joining the Dragoons” implies he’s one of the rare outsiders adopted into the Dragoons.  He serves in LaSalle’s Company (“The Hunters”) of Delta Regiment’s Able Battalion, and joined the Home Guard after it was disbanded (following Misery). 

Looking through the rosters of the Dragoons, they’re light on aerospace assets compared to the “standard” ratio, which would place two fighters per company (giving the five regiments, plus roughly two battalions of independent commands and support forces, an “ideal” ratio of 100+ fighters, not counting any dedicated aerospace forces on Hephaestus).  I guess having a bunch of aerojock phenotypes with giant foreheads and tiny bodies would be a giveaway that something unusual was going on (though they do seem to have brought some Elemental phenotypes, based on the illustrations of the guards in “The Spider and the Wolf”). 

Including LAMs, I count 11 fighters in Alpha, 5 in Beta, 5 in Gamma, 7 in Delta, 7 in Epsilon, 2 in the Fire Support Group, 22 in the Orbital/Aerospace Operations Group, 4 in the Special Recon Group, and 6 in the Support Battalion, for a total of 69 (let’s assume I missed a LAM somewhere and round to 70).  That makes seven AeroSpace Stars, of which five are pure aerospace, and two are LAMs.  So, one Aerospace Cluster, and a LAM Binary, more or less, although scattered throughout the Dragoon regiments running air support, except for the OAG.   

Sholagar:   The poor Kurita pilots didn’t get the Sholagar’s replacement, the Sai, until 3048, and then the factory for it was overrun by the Clans, forcing them to fall back on the Sholagar again until they recaptured the plant in 3059.   

Reggie Hotspurn’s claim to have survived eleven raids on Hesperus II calls into question the number of “Battles of Hesperus II.”  By 3025, there had been thirteen “Battles of Hesperus II,” but there’s no way that Reggie was involved in any but the most recent (and those were Marik attacks).  It seems likely that minor raids against outlying storehouses aren’t counted, only serious invasion attempts. 

It appears that Sevren fell to the Combine in 2910, and the LCAF attacked several times to try to reclaim it, not succeeding until 3024.  The major push in 3011 nearly destroyed the 2nd Winfield’s Guards.  There appears to have been another attempt to reclaim it in 2989, though why the defeated LCAF forces would be fleeing into the atmosphere instead of out to their DropShips is a bit confusing, since it implies they were heading back to their ground-based landing areas. 

The 3011 Battle of Arboris is notable as an example of Kurita’s omnidirectional hostility and love of deep raids, since Arboris, at the time, was a Capellan world.  This was probably related to the Kuritan offensive against the Confederation that also saw clashes on the unmapped world of Lincoln between CCAF and DCMS forces.  It must have been difficult to tell the Sholagars apart from the Thrushes.

Shilone: The DCMS first hit Cussar (as Barlow’s Folly was then known) in 2787.  The Avalon Hussars fought for two weeks, then pulled out when news of the near total collapse of the Combine front arrived, leaving Michael Barlow behind to fight a guerrilla war that lasted until 2801.  The name changed as people in the border region began referring to it as such in respect for Barlow’s dedication and how he inspired the people of the world to continue fighting.  So, was the “First Battle of Barlow’s Folly” in 2804 the first fight there after the name change?  The First Succession War sourcebook notes that, by 2804, the Federated Suns counteroffensive was hitting Flushing, Batavia, Beecher, Barstow, Imbrial III, and Peabody.  The First War counteroffensives never reached Cussar/Barlow’s Folly, so the “First Battle of Barlow’s Folly” was probably a DCMS effort to suppress the first major rebel offensive following Barlow’s death in 2801. 

The 3rd Dieron Regulars started the First Succession War on Junction and ended on Marlowe’s Rift.  None of the Avalon Hussar regiments are noted as starting the war on Cussar, so one regiment must have been deployed there to support an intended AFFS offensive against the Combine, before everything went to pot.  The deployment tables show the 26th Robinson Chevaliers as Cussar’s garrison, noting them as destroyed by the war’s end.  The 2nd Arkab Legion was Cussar’s garrison circa 2821 (still listed as Cussar, so I’m not sure who’s calling 2804 the “First Battle of Barlow’s Folly.”  ComStar? 

Rather than being commanded by a member of House Kurita, the 1st Sword of Light is under the command of Ano Rentoshi in 3025.  Perhaps, had Theodore not spurned his father’s matchmaking efforts, he might have been put in command of that unit, rather than being relegated to the Legion of Vega. 

Arvin Chin serves with the 5th Amphigean Light Assault Group, but is noted for having served in every major Combine offensive between 3015 and 3025.  Does that mean he was detached from the LAG to support regulars?  Or was the LAG kept that busy, serving in a support role all over the border?  This entry confirms that the LAG came down on the “mercenary” side of its somewhat nebulous role as a quasi-House unit/quasi-corporate mercenary force circa 3025.

I tried to look up the meaning of “Hai Namb,” and it appears as part of the title of a “very sad Hindi song,” but putting it into Google translate for Hindi->English only returns “Is nmb.”  The song’s full title when translated, is “Why do your eyes nmb?” 

Slayer: Per the First Succession War sourcebook, Combine forces took control over Kesai IV in the “Great Hegemony Landgrab” in December 2786.  There wasn’t any fighting there during the First Succession War, since the main Combine offensive pushed in along a front that ran from Ozawa to Tishomingo, while Kesai IV is out towards the Outworlds Alliance border.  The AFFS counteroffensives pushed back across that same ground.  Kasai (aka Kesai IV) at the time was a “shared world” under Star League auspices, but the disappearance of Star League authority left it open to the Combine taking full control.  The story of the Combine forces being repulsed by Davion forces probably only referred to an early battle, as the world unquestionably fell to the Combine and stayed in Combine hands for the duration of the First Succession War. 

The 4th Battle of Harrow’s Sun is the setting for the “Fox’s Teeth” scenario “Cry Vengeance!”  This is the battle where Ross McKinnon dies in battle, leaving his son Ian in charge of the company for the first time.  Vengeance deals with ground action against the 12th Vegan Rangers (later clarified to be the Legion of Vega, since the 12th Vegan is a fanatically pro-FedSuns merc unit), so this account expands on the Fox’s Teeth’s exploits on Harrow’s Sun under its new commander. 

I’m pretty sure Hans Horshaw is one of the main characters in “And Then There Was the Time…” since that “Shrapnel” story indicates that the self-absorbed aerojock pilots a Slayer and at one point exclaims “Uff da!,” which would be in keeping with a name like Hans (implying Rasalhagian ancestry).  That story also name-drops other “notable pilots” from TRO:3025, so I’m guessing that the main character is also intended to be one, and Hans fits the bill. 

The note that a pilot from the 5th Sun Zhang Academy Cadre is regularly rotated out to line units on the front explains how a pilot from the 5th Amphigean LAG could take part in every major Combine offensive of the last decade – the DCMS transfers aerospace assets from garrison units to reinforce units mounting offensives.  Players wanting to reflect this should give defending units posted to interior Combine worlds little or no aerospace support.

Thrush: “Panohai” translates as “Opposition” in Malagasy. 

TRO:3025 was presumably part of the background materials provided to Ardath Mayhar to help her write “The Sword and the Dagger,” which was published in 1987.  (TRO:3025 was published in 1986).  Thus, Uchita Tucker became one of the early POV characters, taking part in the battle for Stein’s Folly.  She loses her bionic leg and scores her thirteenth kill during the Liao invasion, in which she commanded Dagger Squadron.  Though she’s last seen spinning off into space in her damaged fighter, she’s presumably recovered, since this entry refers to her in the present tense, and a Thrush is seen later strafing Davion troops on the ground during Ardan Sortek’s counter-invasion.  TRO:3039 later expands on Uchita’s character, noting her as part of the vicious Thuggee cult.  I wonder if Uchita was involved in the initiation ceremony for Kali Liao?  BattleTech Thuggees don’t seem to have a problem with bionics, judging from the Manei Kali during the Jihad. 

The 2786 Capellan “occupation” of Sax is a bit of a mystery, since Sax has remained in Capellan hands since its colonization, though losses during the Succession Wars moved it from being a rear-area world in the Andurien Commonality to a border world in the Sian Commonality.  The OpFor is described as a “renegade ‘Mech lance,” so perhaps local rebels decided to declare independence on the eve of the First Succession War, and a CCAF force was sent in to put it down. 

Designators such as the “14th Sian Air Defense Squadron” imply a massive aerospace defense force for Sian (84+ fighters), which would be appropriate for a Successor State capital world.  However, given the state of the CCAF, one wonders what percentage of those are Guardian conventional fighters.  Still, if Tikonov’s “Night Riders” totaled 70 aerospace fighters, Sian probably had at least as much (forcing Morgan Hasek-Davion to disguise his forces as the 4th Tau Ceti Rangers to be able to land safely and extract Justin Allard). 

Demeter fell to the Confederation in December 2795.  The AFFS launched its counteroffensive to recapture Demeter from the CCAF in December of 2809, and completed the reconquest by April 2810.  The First Succession War sourcebook noted that “the Suns would hold onto Demeter,” implying that the CCAF counterattacked.  Thus, a 2812 raid fits.  The First Kearny Highlanders are noted to have begun the war on Halloran V, just one jump from Demeter, and ended there as well, but down to 43% operational strength.  Oddly, no AFFS forces are noted to be stationed on Demeter at the war’s end.  You’d think, after spending so much effort to gain it, they’d leave a guard unit…  I guess with the Chancellor’s death during the final attempt to recapture the Chesterton-Demeter salient, the AFFS figured the fight had gone out of the CCAF and was comfortable reallocating its forces to the Combine front. 

Transit: New Berne isn’t a mapped system.  It may be one of House Davion’s outpost worlds that constitute a rapid-transit network linking key systems.  Those seem to have a semi-consistent naming convention of “New X,” such as “New Cleveland,” and possibly “New Boston” and “New Berne.” 

The House Liao sourcebook notes that Davion Transit fighters attacked Carver V in 3015 and 3018.  This entry says that Transits defended the world, but were overwhelmed by heavier Davion fighters (Stukas, most likely, unless they were older Thunderbirds.)  Carver V appears to have lost a moon between this entry and its WizKids writeup as Liberty, since that only lists two moons, while this entry claims three.  Only one moon is pictured in MechCommander 2, set on Carver V.

While the featured Thrush squadron was designated the “14th Sian Air Defense Squadron,” indicating a permanent base of operations, the Carver V garrison was designated the 15th Defense Squadron.  Does this imply that there were at least 14 other squadrons on Carver V?  Unlikely, since the 15th went up against the raiders alone.  More likely, the Capellan navy, such as it is, has a set number of fighter squadrons it assigns to bolster planetary militias and Home Guard units, naming them “Defense Squadrons” and numbering them. 

Seiji Smith’s fighter, “Usuali Wong,” may have been what inspired the author of the “Capellan Solution” novels and Field Manual: Capellan Confederation, Loren Coleman, to use a lot of phonetic Chinese puns to name unit commanders.  “Usually wrong” is also a fit appellation for the ComStar research, since it puts Smith as part of a Defense Squadron on Kathil…a solidly Davion world three jumps from the Liao border. 

Transgressor: How old is Harry Yoshita?  The Transgressor’s official date of introduction (from the MUL) is 2890.  He’d have to be at least 160 years old in 3025 to have been part of the design team.  Text from page 50 of the House Liao sourcebook indicates Transgressors first reached the battlefront in 2987, which would fit chronologically with Harry Yoshita’s profile. 

House Davion held Acala (spelled here as Alcala) at the start and end of the Third Succession War.  It appears that House Liao managed to retake it at least once during the Third War, however, since the battle in 2992 was a Liao defense against Davion invasion forces.  Many of the Liao combat records show them taking worlds, but being unable to hold them for long.

There’s an undercurrent of sexism in some of the fighter pilot profiles, with appearance being the first attribute described for many of the female pilots.  Lucy D’Urban is felt by many to be “too good looking to be a fighter pilot,” Sarah Nealson is “tall and beautiful,” Danielle Peterson is “blond and beautiful,” and Diane Virgil has “striking good looks.”  None of the male pilots are ever described as “handsome” or “too good looking to be a MechWarrior.”  Several BattleTech products directly address this issue.  The Atlas of the 4th Succession War notes that sexism in the DCMS led many women to become fighter pilots, instead of MechWarriors, because their smaller stature and faster reflexes gave them the edge they needed to prove themselves.  Christine Watkins, in “Fist and Falcon,” has a tendency to see sexism in the comments made by others.  The profile of Terra in Jihad Hot Spots: Terra notes that “racism, sexism, and other regrettable culture aspects of ancient Terran nations are markedly absent even in cultures that were once defined by them.”  By contrast, Cassie Suthorn encounters racism, ageism, sexism, cultural elitism, and insensitivity at the Rights of Towne Movement meetings in “Hearts of Chaos.” 

Cheetah:   I’m not sure exactly when Pearce and Reynolds could have gone to guns against each other, because the 1st Regulan Hussars haven’t been anywhere near Lyran territory for a good 10-15 years (since raiding Lyran border worlds during Alessandro’s “concentrated weakness” debacle).  Stationed on Regulus (a long way from Wyatt), I don’t see them clashing with the 11th Lyran Guards over and over, unless the FWL operates like the Combine, and transfers pilots from garrison units to support units up at the front.  The FWL’s “Home Defense Act” provisions would seem to put a damper on this practice, even if the LCCC wanted to do it, however. 

The references to the gravity well and bomb-carrying abilities are direct references to the AeroTech 1st Edition ruleset, where the map had gravity well rules for slingshotting around (or, if you’re unlucky, into) planetary bodies. 

The Free Worlds League took Xanthe III with the 18th Marik Militia in the early years of the First Succession War and held it thereafter.  It appears that the locals rose up and declared themselves independent at the outset of the 2nd Succession War using gear taken from an SLDF cache, and had to be forcibly put down.  FM: SLDF doesn’t indicate that any SLDF units were based there circa 2765, though, so this was probably a hidden storehouse intended to supply SLDF forces in the event a Canopian offensive cut them off from their regular supply lines.  The 48th Jump Infantry Division accidentally destroyed an orbital refueling station over Xanthe III while stationed in the Capellan Confederation, sending wreckage raining down on an inhabited lunar surface.  The cache might have been set up for the 48th, then sealed and left behind when they transferred to the Magistracy (much to Xanthe’s relief). 

I’m sort of at a loss to explain the 2952 Marik raid on “Andorian V” (almost certainly meant to be Andurien V).  No source ever mentions the Capellans being able to retake Andurien since they lost it in the First Succession War, but it appears that they managed to capture it, at least briefly, in the middle of the Third Succession War, and shattered at least one Marik retaliatory raid on the world.  Perhaps the League’s failure to defend Andurien led to the massive animosity of House Humphreys towards the central League government.  I note that the House Marik section on awards states “the provincial forces of the Duchy of Andurien have seldom seen combat action over the last 50-75 years,” which would imply that they did have heavy combat in 2950 – confirming a major Capellan incursion into Andurien space right around 2950. 

Stingray:   Again, having pilots from the 11th Lyran Guards and 1st Regulan Hussars engaged in a feud doesn’t seem plausible when the 1st is garrisoning Regulus and the 11th is on Wyatt.  The 1st Regulan was heavily engaged during Anton’s revolt hitting Avior, Tiber, McKenna, and Ling, but those aren’t anywhere near Wyatt.  Following Anton’s revolt, the 1st garrisoned Regulus, which would have taken a deep raid by the 11th to have the two meet.  My supposition is that the 1st Regulan encountered the 11th Lyran Guards when the 1st raided Lyran worlds to take advantage of Alessandro’s concentrated weakness strategy, and the two clashed repeatedly then.  But for the last 15 years, it’s been nothing but talk.  The fact that Reynolds’ superiors don’t approve of his fanaticism makes it unlikely that they’d approve a deep raid on his behalf. 

The CCAF conquered Van Diemen IV during the Second Succession War, when they took advantage of the ComStar interdiction.  They later lost it once the League’s communications were restored and it could launch a counteroffensive.  It’s interesting that the Capellan forces took the time to occupy the outer planets in the Van Diemen system.  We know nothing about any of the worlds except IV, but from the sounds of it, there must have been valuable mining operations on the outer worlds, if House Liao took the time to occupy them, and was able to extract trade concessions as the price for leaving. 

The 20th century designs that inspired the Stingray appear to have been the Russian Sukhoi Su-47 Berkut fighter (or its equivalent in a universe where the Soviet Union lasted until 2011), the Convair XB-53 medium bomber, and the Grumman X-29  (which also inspired the the G.I. Joe Conquest X-30).

Riever: The profile on Major Lohkamp would seem to be highly damaging to his political ambitions.  How are ComStar researchers going to get anyone to talk to them if they publish such damaging personal profiles describing people’s “secret ambitions” or roles as undercover operatives?  It works as a character profile for RPG use, but would never appear in a reputable journalistic publication, for fear of libel suits, if nothing else. 

The fact that Lohkamp gets called up for frontline service would seem to offer an avenue for Pearce, from the 1st Regulan Hussars, to be active around Wyatt, with a chance to run into Reynolds. 

House Marik conducted devastating border raids against Phecda in the opening years of the First Succession War, using orbital bombardment whenever possible.  The 16th Skye Rangers began the war there, but had moved to Wing by the war’s end.  The 2815 battle isn’t mentioned, though the First Succession War book notes that heavy raids by both sides had ravaged border systems.  The Phecda battle was probably one of those raids (though without WarShip support following the massive losses of the past decade). 

Graham IV was occupied by the Marik Guard in the 2793, when it was brought into the League along with Sirius, Procyon, and Pollux (a loose protectorate headed by Sirius and garrisoned by the Sirian Lancers).  The Lyrans hit the world with the Stealths in 2790.  Lyran and League representatives began negotiating a cease fire in 2820, but didn’t sign the Bella Accords until 2823.  Having the Lyrans sponsor a rebellion on Graham IV in 2820 probably didn’t help the negotiations.  (But neither did the FWL raid on Solaris VII in March).  Massive nuclear bombardment during the Star League Civil War had reduced the world to a radioactive cinder, with most of the population living in space habitats, so it’s not clear why the Lyrans coveted the former industrial world, since it only offered some minor mineral resources at that point.  The space habitats make Graham IV a major port of entry for traders circa 3025, but it’s not what made them attractive in 2820. 

Seydlitz:   2504 is somewhat early to be filling a Star League contract, so that should probably read “Terran Hegemony” or “Hegemony Armed Forces.”  The world of Vance is not mapped, so it’s probably a secondary planet in a named system – probably Skye, since that’s where Shipil Company has most of its operations. 

While this entry says the League invaded the Lyran world of Megrez in the First Succession War, the First Succession War sourcebook shows Megrez starting and finishing the war as a League world, garrisoned by the 25th Marik Militia.  The 25th ended the war at 47% strength.  I suppose it’s possible that the Lyrans invaded and established a foothold on Megrez, and it took three years for the 25th Marik Militia to push them off. 

That’s one heck of a deep raid for the 10th Skye Rangers, since Worrell is out by the Draconis Rift, a few jumps from Galedon.  (Perhaps the 10th was trying to match the FWL’s achievement of raiding the Outworlds Alliance.)

This entry yet again gets the attacker/defender mixed up on Solaris, which was attacked by the Free Worlds League in 3002, per the Solaris VII sourcebook (“Steiner forces roundly defeated a major Free Worlds invasion in September 3002.”)  The Donegal Guards were most likely relief forces that smashed the League’s forces in their zone of control on the surface. 

The “Amber” regiment of the Marik Militia is/was, I believe, the 21st Marik Militia.  Since the “Amber” regiment was disbanded in 3007, Doris Wichal’s actions would have been prior to that date. 

Lucifer: It’s interesting that Saffel – a world close to Terra – was in the Commonwealth circa 2978.  It was a Combine world for most of the Succession Wars, and ended up in Davion hands circa 3025.  That must have rankled the Combine to have a world so close to Dieron in Lyran hands. 

Bella I doesn’t seem like much of a candidate for a “deep penetration” raid, since it’s right on the Lyran/League border. 

Interestingly, the Lucifer doesn’t follow the standard Thrust/Overthrust ratios, listed as 5/7 instead of the traditional 5/8.  Not sure if this is a typo or an intentional attempt to reflect its reputation as “the Dragger.”  Looking at the arsenal, it really excels at strafing runs.

Chippewa: There’s a recurring theme in the Steiner fighter write-ups that implies that House Steiner acquired its fighters almost exclusively by recruiting SLDF personnel when the Star League fell.  The author seems to have not been aware of the Exodus or of the existence of member state armies, and suggests that the current arsenal came from active recruitment of SLDF pilots when central authority fell apart, and/or seizures from SLDF depots.  Such a scenario may be consistent with the Battledroids background, where no new war machines can be constructed, and states scavenge to keep the few remaining examples in the field.  (Under that version, Hesperus II was just a large parts storehouse.)  I’m guessing the Bowie Industries plant on Dell had an exclusive contract to supply the SLDF, since House Steiner had to “seize” it.  The world, itself, was a long-standing member of the Commonwealth, so I’m not sure why the Lyrans didn’t just sign a contract with it.  The front lines never came close to Dell during the First Succession War, but the attack is described as a raid, not an invasion, so that fits.  The garrison was the 23rd York Regulars, which was reduced to 36% strength by that raid. 

Unlike Bella, Ling is legitimately classed as a “Deep Raid,” being down in The Protectorate region.  I wonder why more wasn’t made of a new BattleMech factory being constructed in 2987.  ComStar was decidedly opposed to technological advancement, so rebuilding at the nadir of the Third Succession War would seem like a natural target for Operation HOLY SHROUD.  I wonder what prompted the Lyrans to go so far to hit a target not far from the Capellan/League border?  Did, perhaps, ComStar manipulate communications to leak information to the Lyrans about the new factories and frame them as both a threat and a vulnerable target of opportunity?  That way, the goals of HOLY SHROUD could be accomplished without ComStar having to get its hands dirty with a Blake’s Wrath strike team.

It’s somewhat surprising that the League didn’t obtain any captured or salvaged Chippewas until 2991.

The battle of Alexandria took place in late 3020 through mid-3021, so it took about eight or nine years for anyone to earn the McCleary award.  Since Dan didn’t “Miraborg” himself into an enemy ship, it appears that the reward isn’t intended to be awarded posthumously.
« Last Edit: 07 October 2016, 13:23:54 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1442 on: 07 October 2016, 21:34:37 »
Date: June 5, 3025
 
Title: Technical Readout: 3025
 
Author: Blaine Lee Pardoe, Boy F. Petersen, Jr., Anthony Pryor, Dale L. Kemper, and Shaun Duncan (writing); Duane Loose and David R. Detrick (interior art); Dana Knutson (cover art)
 
Type: Sourcebook (FASA)
 
Synopsis:  

Leopard:   The Leopard is the standard light transport used by the Successor States.  It was introduced in the early days of the Star League, shortly after the development of BattleMechs.  Blocky and angular, it earned the nickname “The Brick,” both for its appearance and its handling in atmosphere.  The later Leopard-CV is a dedicated fighter carrier, and has a more aerodynamic silhouette (but a more vulnerable tail section).  The Leopard is primary used by raiders, commandos, and bandits, with a preference for fast ‘Mechs.  Quarters are cramped and supplies are limited.  Initially accompanied by the company-sized Lion, only the Leopard remains of the early DropShips, due to its reliable design.  The “Teng” serves in the 4th McCarron’s Armored Cavalry under Captain Leeland Malbridge.  The “Hamilton” served with the elite Terran Guards during the Star League, and now serves in the 1st Regulan Hussars under Commander Ira Arkani, most recently evacuating seven ‘Mechs from Cavanaugh II after a disastrous raid.  The “Foxhound” serves in the Nightstalkers.

Union: Capable of carrying a full ‘Mech company, it is the standard medium DropShip, used for raiding parties and to support invasions.  The ship has significant firepower, but spartan crew quarters.  The engines are vulnerable, and several Liao Unions were shot down with engine hits during the invasion of Van Diemen IV.  Production of new Unions is extremely limited.  Unions debuted in the late history of the Star League, when they accompanied SLDF WarShips into battle.  It replaced the older Lion DropShip, and serves every Successor State and a few bandit kings.  “Sweet Chariot” serves in the St. Ives Armored Cavalry under Captain Lars Talbot, and has seen action from Ronel to Arboris.  “Red Eagle” serves under Captain Ilse Morrow in the Draconis Combine Admiralty, not attached to any specific ‘Mech unit.  The Red Eagle fought its way through heavy orbital resistance during the invasion of Hoan III in 2996. 

Overlord:   The Overlord is the largest combat vehicle remaining in the Successor States, 100 meters in length and rivaling the Star League’s star cruisers in size and firepower.  Crews deal with cramped conditions, foul air, and the breakdown of sophisticated Star League-era components.  Fewer are made each year.  Overlords are almost exclusively used for planetary invasions and major campaigns.  It frequently acts as a command center and supply vessel, but only very rarely as a raider.  In 3022, a Night Stalker battalion raided New Avalon itself, hoping to capture Hanse Davion at his winter palace.  They were driven off by a regiment of the Davion Guards.  In 2976, a Marik invasion lacking Overlords was repulsed when it tried to take the Ford system.  The “Running Fox” serves as Hanse Davion’s personal transport/command post when he is on campaign.  A third of its ‘Mech Bays have been reconfigured to serve this purpose, and provide more luxurious accommodations. 

Notes:   It’s somewhat surprising that TRO:3025 would contain write-ups for three DropShips, since it’s framed as “the latest in a series of reports on military hardware, this one focused on the BattleMech,” while the first in the series already covered DropShips in extensive detail (DropShips and JumpShips).  I can understand FASA wanting to make sure players had details on the three most common ‘Mech/fighter carriers all in one package (and this came out in 1986, while DS&JS came out in 1988), but it seems redundant from ComStar’s point of view, since, in-universe, DS&JS had just been published a few months prior. 

Leopard: The Leopard was introduced in 2537 – quite a while after ‘Mechs were introduced, yet before the Star League.  The writer’s bible at this point appears to have conflated the creation of the Star League with the start of the Age of War, or at least with the creation of the BattleMech.  The Lion wasn’t introduced until 2595 (though it would serve alongside Leopards until the creation of the Union in the early 2700s).

If the Leopard is not designed for extended operations, and quarters are cramped for 15 people aboard, how in the world was the Carlyle’s Commandos Leopard able to cram the entire surviving support staff on board when it evacuated from Trell I?  I can see cattle car conditions in the empty ‘Mech bays and heavily rationed food and water, sure, but was the ship able to produce sufficient oxygen for them all?

Visually, the Leopard is loosely based on the Minerva from Crusher Joe, though there are substantial differences.  The connection comes largely from the fact that existing plastic model kits for the Minerva were repackaged as a BattleTech Leopard.  The official version truncates the nose, but retains the protruding cockpit nub, and changes the mostly cylindrical body to have flat, sloping planes with large bay doors, which are absent from the Minerva.



Interestingly, the graphics guys at Infocom/Westwood apparently preferred the look of the Leopard CV for the Crescent Hawks’ Revenge – you can see in the screenshot that Jason and his four-‘Mech lance are apparently traveling to Lyons in a Leopard-CV, which has a completely different bay door arrangement, as well as the distinctive extended tail section.



Circa 3025, the 4th McCarron’s was “Leo’s Demons.” 

If the Hamilton was originally part of the elite “Terran Guards,” that implies it was part of the Hegemony Armed Forces, which became the Royal regiments of the SLDF.  Looking at the SLDF units that joined the FWLM, we don’t have any Royal units there.  However, the Hamilton serves now with the Regulan Hussars, and both the 166th Mechanized Infantry Division and 63rd Mechanized Infantry Division joined the FWLM as elements of the 6th and 7th Regulan Hussars, both of which are long gone by 3025.  I can see a Leopard serving in a Royal unit, then being transferred to a SLDF non-Royal unit when the Royals got new equipment, coming over to the Regulan Hussars, and then being transferred to the 1st when the 6th and/or 7th were struck from the rolls. 

The 166th MID (The Red Diamond Division) suffered terrorist attacks by Capellan agents before the Star League Civil War, so service with the Regulans makes sense.  Prior to the war, though, they were stationed in Davion space on Aucara.  During the war, they fought in the Fourth Army Group’s Fourth Army in Task Force Sun, seeing combat on New Rhodes III, Addicks, and Terra.  On Terra, they joined the landings in Afghanistan and then pushed into Iran and on to the Mediterranean.  The 63rd was stationed on Elidere IV, in Combine space, part of the XXIII corps, with which it fought on Yangtze.  There’s no record of the XXIII Corps being on Terra, so I’d hazard that the “Hamilton” was with the 166th, becoming the 6th Regulan Hussars.

The raid on Cavanaugh II can’t have been too recent.  The last recorded Marik invasion of Cavanaugh II was in 2952, when they were driven off by the Eridani Light Horse.  The Marik sourcebook notes that Marik and Steiner diplomats are currently (3025) meeting on Cavanaugh II to discuss further liberalization of trade along the border, so sending a raiding party into the middle of the talks would seem to be counterproductive. 

The note that it was able to haul nearly twice its normal complement suggested that DropShips weren’t limited to just what their ‘Mech bays could hold.  Loren Coleman would later use this as a plot point, having overstuffed Capellan DropShips surprise the Republic garrison on Liao after the Black Paladin’s betrayal.  Presumably the overstuffed conditions preclude the standard methods of rapid deployment or maintenance.

The description of the “Foxhound” is somewhat surprising, since, circa 3025, both Night Stalker regiments are posted far from the Davion border on Matamoras and Basiliano, not to mention that they’re very poorly regarded by the DCMS and the Coordinator for their reluctance to follow orders if they think they have a better idea.  Rewarding insubordination by giving them a brand new Leopard with “advanced weaponry and communication devices” seems highly out of character.  McGavin’s Regiment was still on Basiliano when the 4th Succession War broke out, and was forced to retreat.  Johiro’s Regiment wasn’t engaged, as far as I could tell, suggesting that the “Foxhound” may have been assigned to some of Johiro’s troops on detached assignment to raid the Davion border. 

Union: Hoan III is probably the same as Hean.  The spelling changes frequently from reference to reference, but most maps mark it as Hean, rather than Hoan.  (WizKids went with Hoan for its write-ups, FASA fluctuated between Hoan and Hean, and Catalyst has gone with Hean).

The downing of Liao Unions at Van Diemen IV is a reference to the 2905 invasion, which would be at least the second time House Liao invaded Van Diemen (first during the 2nd Succession War interdiction of House Marik, and again during the early years of the Third Succession War).

“From Ronel to Arboris” sounds like a wide swath, but the two systems are actually only three jumps apart.  It’s also odd that a unit of the St. Ives Armored Cavalry would be known for its actions up in the Tikonov Commonality theatre.  Why isn’t “Sweet Chariot” employed defending worlds “from Armaxa to Texlos”?

I can definitely see the utility of having independent DropShips to be assigned “as needed,” especially when there may be units without integral DropShip support – particularly mercenaries that are getting the “company store” treatment and will have to pay through the nose for DCA provided transport.  I’d imagine that most of the Combine’s assault DropShips are in the same category as the “Red Eagle,” and assigned to support assaults as needed. 

Overlord: Let’s evaluate the claim that the Overlord “rivals League star cruisers in size and firepower.”  Looking at the stats, the Overlord is 131.2 meters high, and has (BattleSpace stats) 18 points of firepower to hit something centered in its forward arc (hitting with both FL, FR, and N bays) and 22 points of nose armor.  The Vincent is 402 meters long, and has 8 points of firepower in the forward bays, and has 16 nose armor.  I’ve got to say, in a head-to-head shootout between an Overlord and a Vincent, I’d give the edge to the Overlord.  It also outclasses the Bug Eye and some of the other “lost design” corvettes.  Once you get into the destroyer range and above, however, the Overlord is rendered a juicy target.  The only WarShip it “rivals in size,” however, is the Bug Eye, at 129 meters.

The Night Stalkers haven’t ever gotten much page-time in the various fiction pieces – just a few small sourcebook write-ups.  However, in TRO: 3025, they were the “big damn heroes” of the Draconis Combine.  They get a custom Leopard designed to infuriate Hanse Davion, and they actually managed to pull off a raid on New Avalon which nearly captured or killed Hanse, just two years after their creation.  The raid would have probably taken place in very early 3022 (hitting the “winter” palace, after all), since by spring 3022, Hanse was on Terra hitting on Katrina Steiner and finalizing the Federated Commonwealth treaty.  The close call at his own palace probably reinforced his determination to secure a strong alliance to once and for all crush the Dragon.  (And then Max went and tried to replace him with a doppleganger, and the full fury of the FedCom came crashing down on the Confederation, instead.)

The Night Stalkers are noted to have received “private financing” to pull together two regiments of equipment manned by forcibly retired MechWarriors, along with academy washouts who failed to win placement into a DCMS line regiment (what, the Legion of Vega didn’t need fresh meat?).  I wonder exactly where that private financing came from?  Industry?  Nobles?  The Yakuza?  The Black Dragons/Council of Gems?  Perhaps the Stalkers are in poor regard with Takashi because he wonders the same thing I do – whose agenda are they really following?
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1443 on: 08 October 2016, 02:15:29 »
If the Leopard is not designed for extended operations, and quarters are cramped for 15 people aboard, how in the world was the Carlyle’s Commandos Leopard able to cram the entire surviving support staff on board when it evacuated from Trell I?  I can see cattle car conditions in the empty ‘Mech bays and heavily rationed food and water, sure, but was the ship able to produce sufficient oxygen for them all?
That's a problem/inconsistency that I've mentioned before: The classic DropShip trio are more or less pure deployment vehicles, but they're not very good transport vehicles and totally unsuitable as raiders (lacking comfort and life support facilities for the former and cargo space for the latter - seriously, a Union simply cannot carry home any booty and is often even hard-pressed to carry enough food and supplies for a one-way trip from the jump point to the planet so why would you take it as a raider unless it carries only half its 'Mech complement? Well granted the Black Thorns got away with loading a 13th 'Mech into the 'Mech bay of their Union, but special circumstances (otherwise known as "author fiat" and "poor factchecking") must have been involved, and in-universe there would have been problems involved that the novel glossed over.).

My understanding is that week- or month-long interstellar travel must instead have taken place on some sort of troop carrier DropShip or even in quarters on the JumpShip, and only upon arrival at the target world would (most of) the crew and MechWarriors embark on the deployment DropShips for combat operations.
(Much like the marines from Aliens aren't travelling on their confined Cheyenne dropship, only using it to drop into action with their APC.)

Although barely sufficient life support is explicitly mentioned for the Union, there are several examples in fiction where Unions and Leopards are hauling largish infantry contingents, sometimes even with vehicles, in addition to their 'Mechs. By means of exclusion I understood this to mean the aerospace fighter bays must have been converted into infantry bays, with some sort of upgrade for the life support.
Or they were ripped out for cargo space which was then filled with prefab housing (which in turn presumably comes with life support upgrades, water reprocessing, oxygen supplies, etc) as seen on the Triptych Soliloquy in the Exodus Fleet.

If you consider the DropShips as pure deployment vehicles, ideally only from orbit to the surface, strained life support and overloading becomes less of a problem to explain/handwave. But that's clearly not what was happening during the Succession Wars era. Guess crew comfort was secondary to sheer haulage in that era.
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1444 on: 08 October 2016, 03:44:18 »
Date: June 5, 3025
 
Title: Technical Readout: 3025
 
Author: Blaine Lee Pardoe, Boy F. Petersen, Jr., Anthony Pryor, Dale L. Kemper, and Shaun Duncan (writing); Duane Loose and David R. Detrick (interior art); Dana Knutson (cover art)
 
Type: Sourcebook (FASA)
 
Synopsis:  

Swift Wind Scout Car: The Capellan Swift Wind is typical of scout cars found in the Inner Sphere.  It carries one scout who can report enemy numbers and positions, then use the sophisticated communication system to report back, or spot for artillery fire.  Drivers use a scaled-down neurohelmet, similar to Speeder racers, to help them control the fast vehicle.  The com system can handle data transmission, surface-to-air transmission to coordinate with telemetry from friendly fighter pilots (helping them strafe and bomb the right targets), and uplink with micro-satellites to relay messages planet-wide.  They can even communicate with JumpShips without relying on relay systems, and can eavesdrop on enemy communications.  The Federated Suns “Darter” and Lyran Commonwealth’s “Centipede” have similar capabilities.  The Combine’s “Skulker” lacks the dish antenna.  Mick Lewis serves in the 1st Brigade of the Fusiliers of Oriente.

Rommel/Patton Tanks:   The first attempt to create a new combat vehicle not based on a Star League design, the Rommel and Patton (which are just different weapon loadouts on the same chassis) are faster than the Demolisher, while still packing a punch.  These have a shorter silhouette than older tanks like the Demolisher, and mount autocannon and long range missiles.  The Rommel has heavier firepower, while the Patton has an anti-infantry flamer and more armor.  Standard practice is to fire in a hull-down position, so the body of the tank is not exposed to return fire, or to attack from elevated parking garages and basements.  Hansen’s Roughriders was chosen as the first unit to receive the new tanks for field testing.  Marik and Kurita spies are trying to obtain data on the tanks’ design, while the plans are being bartered to the Federated Suns in exchange for access to the New Avalon Institute of Science. 

Von Luckner Heavy Tank: Named after Count Felix von Luckner, the HartfordCo tank was introduced after the Reunification War to serve the Star League.  With an AC/20 and missile batteries, plus a machine gun and flamer, the tank can inflict heavy damage on any foe that challenges it, at any range, though it is highly ammo dependent.  The remaining Von Luckners serve throughout the Successor States, except House Liao, which stripped its for parts.  In 2859, House Kurita’s 3600th Heavy Armored Company used its Von Luckners to wipe out a light Davion company that had invaded Saffel.  In 2989, Lyran forces on Aubisson sacrificed their Von Luckners as a rear guard to enable them to regroup in the face of a strong Kurita advance.  In 3017, Redjack Ryan’s water raid on Icar was repulsed by Lyran Von Luckners.  Cromwell Jenkins commands his family Von Luckner for the Draconis Combine, and has supported several raids on Suk II.  Stephine Dawkins commands the 2007th Heavy Tank Group from her Von Luckner, which is still damaged from fighting on Hsien. 

Galleon Light Tank:   The Galleon light tank was produced on Free Worlds League planets to provide an infantry- and ‘Mech-support vehicle for the Star League.  Many served in Periphery garrisons until the exodus, and these ended up in Marik and Kurita hands.  It can outrun most ‘Mechs and has strong weapons, but weak armor.  On Kobe, House Steiner found itself outmaneuvered by Kurita Galleons in the lowlands of the Sounder Mountain Range, below Sounder’s Peak.  House Marik first deployed its Galleons in 2910 on Zion, pushing through the desert and assaulting Liao fortifications in the Gapston mountain area, breaching the walls and knocking out the Long Tom artillery.  House Davion Galleons inflicted heavy casualties on a Kurita raiding party on Ludwig in 2955, though most of the convoy was destroyed as well.  Wolf’s Dragoons maintains a platoon of Galleons, as does Richard’s Panzer Brigade.  House Liao is the only Successor State not to use the Galleon.  Shooman Wax pilots his Galleon, “Doris,” in the DCMS’ 1089th Light Armored Support Group, naming it after his sister, who died fighting on Alexandria.  Harley Tomis serves in the AFFS’ 5000th Mobile Tank Support Unit, a unit that served in the relief forces that liberated Kentares IV.

Packrat Long Range Patrol Vehicle: The Packrat Long Range Patrol Vehicle (LRPV) was designed as a mobile raider that could interdict both communications and supplies in enemy rear areas.  It was originally fusion-equipped, but most have been downgraded with internal combustion engines.  It can carry ten commandos if needed in its roomy storage bay.  It has a very powerful transmitter that can send and receive over great distances, and jam nearby transmissions.  In 2891, on Tannil, AFFS Packrats located Kurita raiders and allowed the AFFS to drive the Kurita Guards offworld for a while.  In 2944, on Carse, Steiner Packrats devastated the DCMS rear area, enabling a LCAF counteroffensive to drive the raiders offworld.  In 2990, on Lincoln, AFFS Packrats destroyed Liao aerospace fighters on the ground at their landing zone in Durban, giving the AFFS garrison air superiority and enabling them to drive off the Liao forces within hours.  Montgomery West serves in the LCAF’s 421st Long-Range Patrol Group, and once raided a Marik ‘Mech repair facility on Oliver.  Shormen Fielding commands “Mickey Rat” in the DCMS 2058th Deep Penetration Group.  He once drew off two AFFS companies on Quinten, letting Kurita raiders hit the underdefended cities of Troy and Birmingham. 

Mobile Long Tom Artillery:   The Mobile Long Tom is a powerful long range weapon system, dating from the Star League era.  It provides impressive fire support and defense, but is slow and vulnerable.  The last remnant of the Star League’s “main guardian defense system,” key cities on garrisoned worlds usually possess one.  It is usually assigned a dedicated guard force to protect against aerospace fighters and ‘Mechs.  In 2888, on Errai, AFFS Long Toms in the city of Trent held back Kurita raiders for six months before aerospace fighters destroyed them.  On Berenson, FWL forces used a Long Tom based in the city of Tromoth to bombard the city of Garth, initiating an artillery duel with a Liao Long Tom in Garth that lasted for a week before Marik commandos sabotaged the Liao gun, enabling Marik to take Garth.  In 3002, on Loric, LCAF forces used a Long Tom to drive Marik raiders away from the city of Treth.  John Cassion seves in the New Battle Creek Defense League on Kearny as a Long Tom fire crew leader.  Wendy Polanski is a firing officer in the FWL’s 3000th Rifleman Corps.  She destroyed ten ‘Mechs in four days during the defense of Pollux against enemy raids.

Boomerang Spotter Plane: The Boomerang is the Federated Suns’ variant of a typical spy plane of the type used by the Successor States.  The Lyrans call theirs the “Quick Dart,” while the Free Worlds League fields the “Chameleon,” which mounts a machine gun.  The unnamed Combine variant has three cameras, compared to the Boomerang’s two.  As satellites began to become scarce due to the decline in technology, aerial reconnaissance became an important part of the battlefield once more.  Fielded in 2888, it was the first dedicated aerial reconnaissance plane built in the Succession Wars, replacing civilian models.  It serves as a forward observer for artillery and ‘Mech units, sending telemetry via two auto-tracking cameras. 

Mobile Headquarters: The Mobile Headquarters serves as a nerve center for large scale operations.  Computer generated projections accurate down to the individual tree give commanders a sense of the action, aided by fusion power and sub-space communications.  The featured Mobile Headquarters unit is of the type used by the Star League throughout its 200-year history.  The trailer consists of the commander’s private quarters and a large map/communications room, centered on a TriHolo table with information from satellites, ‘Mech communications, and tracking devices.  Rare Star League computer systems can even make projections and offer tactical and strategic suggestions.  The communications officers can communicate with AeroSpace fighters, DropShips, JumpShips, and even break through electronic jamming, using a collapsible dish antenna.  Many Mobile HQs lack functional computers.  HQs are attractive targets for capture, so most units post ‘Mechs as guards.  Narhal’s Raiders motivates its troops by driving the HQ right into the middle of the battle.  House Kurita frequently uses HQs stripped of their command systems as bait for traps, with drop-down sides revealing heavy weapons.

Coolant Truck: Coolant trucks station themselves near battlefields and can hook up to overheated ‘Mechs for quick cooling.  The need for such units became evident during the Reunification War, where the cooler-running Periphery ‘Mechs wore SLDF forces down with heavy attacks.  The first coolant trucks were deployed to Cerberus in 2588, assisting SLDF ‘Mechs to fight in the desert.  The 135-K “Lifesaver” coolant truck is made by Buda Imperial Vehicles on the planet Buda, and uses liquid nitrogen to flush overheated ‘Mechs’ coolant systems.  It can also spray liquid oxygen as a fuel for its flamers, or switch over to “freezer” mode and hose ‘Mechs down with liquid nitrogen.  Coolant trucks slowly follow an advance, but are more frequently captured than attacked.  Succession War etiquette calls for ignoring ‘Mechs hooked up to a coolant truck as long as they do not fire. 

J-27 Ordnance Transport:   The J-27 Ordnance Transport transports ammunition from depots to rear area re-loading centers, serving the SLDF in large numbers.  The lack of protection and explosive cargo lead to most crews being forced to serve.  The Draconis Combine offers J-27 service to penal units as an alternative to the firing squad.  Most choose the squad.  The Capellans and Leaguers also use penal units to crew the transports.  On Les Halles, in 2880, Liao forces used the J-27 to supply its forces, and many were captured when House Marik captured the world.  Kurita fighters strafed and destroyed the supply convoys for the Davion Royal Militia in the Nestling Lowlands on Huan, allowing the Kurita forces to crush the Militia.  In 2080, on New Hessen, Liao’s 125th Deadmen Ordnance Carriers actually fought off Davion ‘Mechs that attacked a convoy, using makeshift launchers for the missiles they carried.  “Jumping” Jake Jackson III commands the 125th Deadmen.

Mobile Army Surgical Hospital: MASH units are present with every well-equipped regiment, close to the action.  They are rarely attacked, as they usually commit to serving the wounded from both sides.  Operating theaters are in the body of the vehicle, accessed by lowering hinged panels.  Temporary buildings can be erected using materials stored in the cargo bay.  They have diagnostic equipment, body fluid analyzers, x-ray machines, neuroscanners, recovery wards, automated robotic surgery tables, etc. – all overseen by triage officers, who can take control as needed.  In an emergency, surgeons can place patients in cryogenic freeze.  These sorts of MASH units were first fielded in the Age of War, though without the capabilities described above, which represent the Star League pinnacle.  The White Whales of the Free Worlds League are the largest, able to have seven surgeons operating simultaneously.  The smallest have only three.

BattleMech Repair Facility:   Once common throughout the Inner Sphere, the Succession Wars have destroyed many of these repair bases, leaving only a handful.  Those still fully functional are fortified, well-guarded, and have ample air cover.  They have sufficient bays to handle eight ‘Mechs at a time, with cranes, winches, myomer stringing systems, and landings for Techs.  The interior has room for an additional five ‘Mechs, brought in prone.  Parts are stored in other buildings.  Techs and their families live in underground quarters, to protect them from capture or assassination attempts.  LosTech tools are stored here.  Some have COMCore computers that can perform diagnostic work on damaged ‘Mechs.  On Morningside, LCAF forces left a repair base undefended to draw Kurita raiders in, then sprung a trap. 
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1445 on: 08 October 2016, 03:46:04 »
Date: June 5, 3025
 
Title: Technical Readout: 3025
 
Author: Blaine Lee Pardoe, Boy F. Petersen, Jr., Anthony Pryor, Dale L. Kemper, and Shaun Duncan (writing); Duane Loose and David R. Detrick (interior art); Dana Knutson (cover art)
 
Type: Sourcebook (FASA)

Notes:  

Swift Wind Scout Car:   Despite the opening note that Swift Winds are only found in the Capellan Confederation, the notable scout is a Free Worlder.   Sigh.  (I’m a die-hard Capellan, and the writer’s bible for TRO:3025 and TRO:3026 appears to have included a mandate that “House Liao never wins.”)

The Swift Wind’s communications capabilities are far beyond just about any other unit in the game, and make it a “must have” unit for any Strategic Operations-level game involving conquest of a system.  Grayson had to go to ridiculous lengths to get ahold of a deep space transmitter on Verthandi.  It would have been much easier if he’d just had a Swift Wind on the roster.

At 10/15, the Swift Wind is much slower than a Skimmer (a one-man hovercraft favored by scouts – essentially an unarmored Savannah Master), but more than makes up for that with its communications suite. 

Interestingly, the only design we’ve seen for a “Centipede Scout Car” is a hover vehicle produced in 3054.  We still don’t have official stats for the 8-wheeled Lyran scout car mentioned here, though you can pretty much just take the Swift Wind stats and replicate them, I’d guess.  The FedSuns “Darter” is six-wheeled, rather than three (as referenced here), and is nearly twice the size of the Swift Wind and lacks the onboard electronics package, so perhaps the wheeled Centipede justifies its own stats as well.  The Combine Skulker is 2.5 times bigger, and more heavily armed (but also lacking the electronics).  We’ve never seen anything on the Free Worlds League’s primary scout car – perhaps they just use the Pegasus, or rely on Skimmers. 

Rommel/Patton Tanks: The reference to the height of the Demolisher is a meta-reference to the fact that the original Ral Partha Battledroids miniature was way out of scale with the ‘Mech miniatures, being far too tall, and necessitating a redesign for a much lower profile. 

It appears that only the Draconis Combine was able to successfully infiltrate the “Desert Knights” project and steal the plans, which were later used by the Free Rasalhague Republic to manufacture their Axel I and Axel II tanks (Rommel and Patton clones – “Axel” means “axe” in Swedenese…though it means “shoulder” in regular Swedish).  (Alternatively, the Lyrans may have given the FRR the designs to facilitate their transformation into a friendly buffer state.)  If only the Rasalhagians had decided to call their clones the Axl and the Slash instead of the Axel Mk I/Axel Mk II. :)

The Periphery sourcebook has the Taurians manufacturing Rommels in 3026.  With Hansen’s Roughriders deploying the tanks in the field for the first time in 3020 (we think, based on the estimated date of Bear Peters’ “The Race is Not to the Swift”), it’s possible, but this raises questions about the Taurian Ministry of Intelligence demonstrating a reach and sophistication far beyond what its reputation would suggest.  Or else ComStar stole the designs and supplied them to the Taurians just to mess with House Davion.

The tank names, of course, are references to Erwin Rommel and George Patton, who fought massive tank battles against each other in North Africa during World War II.  (Thus, also, the “Desert Knights” moniker for the R&D project, since their battles were in the desert between “armored” troops.)

The statement that the Rommel and Patton are the first new tanks since the Star League is nonsense.  They aren’t even the first new armored vehicles Defiance Industries has created since the fall of the Star League, since their Hunter debuted in 2937.  In fact, almost all the vehicles profiled in TRO:3025 and TRO:3026 are post-Star League designs, including the Demolisher that the Rommel/Patton are to supplant (intro date: 2823). 

Amusingly, since William Keith only had these works to reference (and official intro dates hadn’t been established), he describes the Helm cache as filled with “dozens of tanks, from Vedettes (2943) to Demolishers (2823).”  The “Ask the Writers” response to a question about this was that, no, nobody was sneaking into the Helm cache in the late 2900s to add more modern tanks, and that the designs therein should be ones that have introduction dates prior to 2770, such as the Von Luckner (2612).

Von Luckner Heavy Tank:   The Von Luckner is a massively superior vehicle to the 5-ton heavier Demolisher, if only because it has the LRM 10 that makes it possible to engage enemies at long range.  A Phoenix Hawk vs. a Demolisher is almost always an easy kill for the ‘Mech, which outranges and outmaneuvers the tank.  Against a Von Luckner, the P-Hawk would at least have to deal with incoming missile flights from the LRM-10, while it retaliated with its Large Laser.  Still gives the advantage to the ‘Mech, but at least it’s a fight, rather than an execution.

Despite their presence in very limited numbers, the bondsman garrison on Port Arthur certainly seems to have plenty of Von Luckners in the MechCommander game.  Being a Star League-era unit, perhaps the Jaguars broke supplies out from Brian Caches and brought them forward to fill out Provisional Garrison Clusters. 

Count Felix von Luckner is a rather colorful fellow, per his Wikipedia page.  He commanded a commerce raider from 1916 to 1917, but took great effort to accomplish his mission with minimal loss of life, and managed to escape from a Chilean POW camp by pretending to put on a Christmas play, though he was captured weeks later by New Zealander forces.  He was strong enough to bend coins with his bare hands, and rip phone books in half. 

Galleon Light Tank: The Galleon Light Tank is a direct import from Crusher Joe, right down to the name.  As such, it was the only BattleTech tank to be classified as “Unseen.”



Its combat profile pretty much matches the capabilities of the 3025 Wasp and Stinger, and so could be considered a tracked equivalent.  It lacks the armor to stand up against heavier tanks, however, and its popgun array of small lasers makes it little threat to other battlefield units.  Supposedly intended to operate in conjunction with the Harasser, these guys get both outgunned and outrun by the far superior hovertank. 

The Zion battle paragraph is massively confused.  Why would House Marik take control of a vast number of Galleons in the 2780s, own and operate the factories that make them, but not use them until 2910?  The first two sentences state that the battle is House Marik vs. House Liao, which makes sense, as Zion is on the Marik/Liao border.  However, the third sentence switches to “the Combine ‘Mechs” and conclude that the Galleons allowed “the Kurita ‘Mechs to finish the job.”  It’s like the writer forgot which faction was involved midway through the sentence.  Some of you have speculated that an editor went through the completed drafts and changed some faction references in search of balance, and that may be the case here. 

House Marik seems to have captured Zion at least twice by force (2832 and 2910) and then lost it, but finally gained long-term control after convincing a Vicente Sian-Marik, who was the regional Capellan administrator for Zion and four other worlds, to defect to the Free Worlds League, forming the Zion Province and Ohrensen Province.  The 2910 assault was the culmination of Operation RED ROVER, a massive FWLM raiding campaign.

I checked the Wolf’s Dragoon sourcebook, and while their Armored Support Platoons include almost every kind of vehicle from TRO: 3026, there aren’t any Galleons.  I guess the Galleon platoon was a failed experiment that was disbanded (or destroyed) long before the showdown at Misery.  Or, perhaps  ComStar mistook the Dragoon Badger (also 30 tons, moving 6/9) for the Galleon.  They have a fairly similar profile.  Thanks to its fusion engine, the Badger has twice the Galleon’s firepower and longer range, with the same speed and better armor, and the capacity to carry an infantry platoon. 

The naming convention for the two featured Galleon units – 1089th Light Armored Support Group and 5000th Mobile Tank Support Unit, suggest that (circa 3025) the Successor States maintain large numbers of tank and infantry units that they normally parcel out on garrison duty, but can call up and assign to task forces in support of front line ‘Mech units.  The AFFS was somewhat unique in 3025 for permanently assigning such forces to ‘Mech units in regimental combat teams, whereas other Houses just assigned them on an ad-hoc basis. 

The Battle(s) of Alexandria are a running theme in TRO:3025, mentioned seven times in all.  The campaign in question seems to be the one that began in December 3020 and ran for seven months, through mid-3021, though it could also refer to the separate battle which took place in 3024.  When entries reference the “Battles for Alexandria,” they’re probably encompassing both the 3020-3021 and 3024 campaigns. 

Packrat Long Range Patrol Vehicle: With a 120-rated fusion engine, this begs the question – what units were getting the Packrats’ engines?  A 120-rated engine would let a 20-tonner go 6/9 (Wasp/Stinger), so that’s probably what they were used for (though they also could have gone for Galleons.)  Despite the note that most have had their fusion engines removed, stats are only given for the fusion version.  An ICE conversion would likely drop the flamer (which wouldn’t have a fusion engine for power) and one ton of armor, to maintain the speed, missiles, and infantry carrying capacity. 

The Packrat’s jamming abilities were used to great effect against the Gray Death Legion on Helm.  The Packrats there were even referred to as Packrat ECM vehicles. 

The Kurita Guards are not a unit that has ever been profiled.  Assuming it’s not just a typo, it may have been a short-lived brigade that was created in the 2nd Succession War or early 3rd Succession War, and died out in the 3rd.  The Federated Suns are referred to as the defenders, but the Combine has been shown as the world’s ruler on all the interbellum maps, so the AFFS must have punched a salient up to Tannil in the late 2800s and then been forced off.  The FedSuns/Combine border seems to have been constantly in flux, even in the relatively “stable” duration of the Third Succession War. 

Lincoln seems to have been a prominent feature of whatever map the writers were using for both TRO: 3025 and the Davion and Liao sourcebooks.  The 7th Crucis Lancers were forced off Lincoln in 3001 and returned in 3010; Shawn Phillips, of the 15th Dracon, was orphaned by a Davion attack on his homeworld of Lincoln V; the Avalon Hussars attacked Lincoln in 2930; House Liao’s invasion of Lincoln was thwarted in 2990; and Kurita mercenaries (Daemian’s Destroyers) and the Dieron Regulars attacked Lincoln in 2802 and 2803.  Given attacks from both the Combine and Federated Suns, it would seem to be a Tikonov Commonality world (probably former Terran Hegemony, to boot), but it has never appeared on a map. 

“Mickey Rat” is an explicit reference to Mickey Mouse, calling it “some long-forgotten cartoon character of the 20th Century.”  Perhaps not so forgotten as ComStar seems to think, however.  In Close Quarters, Enrico Katsuyama tells Ninyu Kerai he has a half-meter tall statue of Mickey Mouse in his collection, and Ninyu doesn’t have to ask what that is.   

Quinten = Quentin.  It must have been Quentin IV, rather than III, since there’s nothing resembling a wilderness on that hot and toxic world.  My guess is that Mickey Rat was there when Wolf’s Dragoons hit Quentin in Wolves on the Border in 3023. 

Mobile Long Tom Artillery: The Long Tom’s impressive writeup conceals the fact that, at the time, the Long Tom was highly ineffectual, with just a 7-hex AOE burst.  The new rules giving it an extra ring of damage make it much more of a factor.  Just barely able to keep up with UrbanMechs (and with a miniature that doesn’t suffer turning well if you glue the central axis together), the Mobile Long Tom generally serves as a “thing to capture/defend” in a scenario, rather than an active participant in a dynamic battlefield.  If enemy forces are within firing range of a Long Tom, the defenders have screwed up.

The phrase “last remnant of the Star League’s main guardian defense system” is intriguing.  We know the Star League deployed the Reagan-class Space Defense System for Terra and lesser SDS grids for other Hegemony worlds, but did they also have a city-level Guardian Defense System (GDS) for major urban centers, consisting of mobile artillery (likely Thors and Marksmen) and other LosTech whizbangs?  We know they liked drones in the SDS – perhaps the “lost” component of the GDS was Security Robots (MW1E p. 50) – 6-ton 12/18 hovercraft with two small lasers in the turret and limited pattern recognition capability.  I would also guess that another “lost” GDS component would be Rattler-class mobile structures.

I’m not sure what makes them refer to Errai as a “lonely” world.  It’s got a population of more than 300 million, and has lots of casinos and nightclubs.  And mobsters…

The Garth/Tromoth battle on Berenson probably took place in either 2832 or 2840.  Since the Mariks are described as raiders, it was probably 2832, since the Mariks were the defenders in 2840, but the conquerors in 2832. 

Kearny, rather than being a planet in the Federated Suns, is actually a deep interior world of the Free Worlds League.  Not sure how John Cassion would have saved the life of Dr. Banzai all the way over there.  Perhaps Kittery was meant, rather than Kearny.

Boomerang Spotter Plane: William Keith used Boomerangs in both “The Price of Glory” and “The Dying Time.”  He generally worked hard to showcase the non-‘Mech elements on the battlefield, ranging from spotter planes to anti-‘Mech infantry to ECM vehicles to monorail trains. 

Iron Wind Metals introduced the Boomerang as one of its earliest “fan requested” web-store exclusives.  I got it along with the Monitor, Sea Skimmer, and Neptune.  The landing gear falls off if you look at it funny, but it’s a nice looking piece.  One of the early “Support Vehicles” before TRO:VA.  It makes a lot more sense to use one of these for artillery spotting than a ‘Mech, unless you’ve got hostile aerospace fighters in your vicinity.

Interestingly, the Boomerang’s movement is given in terms of BattleTech hexes – 13/20, rather than mapsheets, making it more of a VTOL than a conventional fighter. 

Mobile Headquarters: Another key unit that (until recently) lacked official game rules to reflect its benefit to the unit it controls, the Mobile HQ generally represents a target to be captured.  This is, in fact, its sole purpose in the MechCommander games, revealing parts of the map through the fog of war. 

The updated rules give units with Mobile HQs an initiative bonus.  In a Total Chaos game I participated in, our unit had a Mobile HQ, and used it to dominate the battlefield through consistent initiative wins.  This resulted in the HQ being aggressively targeted by the enemy, bringing it to an untimely end in a scenario when uncoordinated deployment left the HQ out on the flank, rather than safely in the middle of the company. 

In a meta-sense, tabletop games of BattleTech are being played out on the commanders’ Mobile HQ holotables (or, perhaps, jury-rigged mechanisms for representing the battlefield…such as paper maps and metal miniatures?)

The reference to HQs having “sub-space communications” seems like an accidental holdover from the writers who worked on FASA’s Star Trek RPG.  It may have been intended to refer to HPG transmissions – perhaps from the mobile SLDF units, but those would be “hyperspace” rather than “sub-space.” 

Coolant Truck: The planet “Buda” is not mapped.  Later sources have clarified that “Buda Imperial Vehicles” is located on Luthien. 

From the description of the coolant truck etiquette, I would expect to see these things racing around all over the battlefield.  I’ve never actually played a battle involving them, though.  (I’ve just used the miniatures as part of convoys.)  It sounds like you could get a lot of extra mileage out of a Rifleman, for example, by having a coolant truck standing by.  Fire all lasers, then call “time out” and cool down, then disconnect and open fire again.  This also evokes the early sourcebook references to entire battlefields calling for a general “time out” to perform search & rescue of downed pilots, cool down, and perform field repairs.  (Again – nothing I’ve ever seen done in a tabletop game.)

J-27 Ordnance Transport:   Another “big target” support unit, the miniature for the J-27 is spectacular, though the missiles are too big to fit into, say, a Catapult’s launchers (raising scale issues).  It comes with a towable Thumper artillery piece with either wheels for towing or legs for firing. 

The date of the “Deadmen” incident on New Hessen certainly isn’t 2080, but it has to be within the last 10-15 years.  The House Liao sourcebook lists Davion attacks on New Hessen in 3002 (Falkener’s Hussars), 2998 and 3007 (Deneb Light Cavalry).  Since the forces destroyed by the Deadmen were referred to as Davion rather than ‘mercenary,’ I would guess the 125th’s moment in the sun was in 3007, against the Deneb Light Cavalry (which were said to be performing poorly – an apt description for ‘Mechs that get destroyed by J-27s). 

House Steiner claims the moral high ground by not assigning prisoners to its J-27s, but they do use it as punishment duty for troops who “misbehave.”  Moreover, the LCAF did use penal units for ammo reloading during the Reunification War. 

Mobile Army Surgical Hospital: The MASH section includes a reference to the Korean War, a direct shout out to the show M*A*S*H.  I know that I, personally, did one of my MASH trucks up in olive drab with a 4077 on the side.  (The other’s in ambulance white).  Given Claudius Steiner’s obsession with misuse of medical equipment, I would hate to be around when the Archon’s personal meat wagon pulled up. 

MediQuick services mark their MASH units with twin yellow crosses, instead of a red cross.  If you look in the background of some scenes in the BattleTech animated series, you can see some MASH units marked thusly.  Their reputation is so bad that many warriors would rather die than get treated by them. 

The note that surgeons can do “emergency freeze” procedures for critical patients ties in with the reference to wounded AFFS troops being cryogenically suspended and sent to rear area planets for treatment in “The Sword and the Dagger.”  Later write-ups of the freezing process indicate that the procedure works, but the units are LosTech and in poor repair, making it a risky proposition to be frozen.  (Not that it stopped Sun-Tzu Liao or Devlin Stone). 

BattleMech Repair Facility: These large repair facilities are capable of handing a company at a time.  They’re pretty much the holy grail of any 3025-era merc unit or House regular.  Knock one over, and you’re set for life.  You could build a whole campaign around defending or assaulting one. 

In the various video games, these are portrayed as much smaller, single ‘Mech bays, with a limited stock of parts and (apparently) automated repair units.  They appear in the MechCommander game (implying perhaps that the automated single-‘Mech repair facilities are IIC versions).

BattleMech repair facilities mentioned in the fiction include: 
Alarion (aboard the Bowie orbital facility)
Blackjack (a small repair facility in the village of Orange)
Connaught (the remnants of Kong Interstellar Corporation)
Conroe (top notch repair facilities)
Glenmora (2nd tier)
Goshen (hit by McCarron's Armored Cavalry in 3023)
Grand Base (part of Pavel Ridzik's holdings)
Hall (South Harney)
Illyria (rumors of a lost Star League one as yet unfound)
Ironhold (one near Crash Camp)
Kaesong (repairs the Crescent Hawks en route to Luthien)
Marlette (pictured in Total Warfare)
Myrvoll (Destroyed in 3000)
Narellan (demolished in 2993)
Northwind (Cosara Weaponries)
Ohrensen (Fortress Gorndack, smashed by McCarron's Armored Cavalry in 3014)
Oliver (Brigadier Corporation facility under Warez; raided - current status unknown)
Pacifica (A chain of commercial repair facilities under the brand name "Mech-it-Lube")
Paris (at the SLDF's Fort McKittrick - probably destroyed in the Succession Wars)
Sirius (raided in 3000)
Solaris VII (a lance-capacity one for the Skye Tigers - also reference to another "main" one raided by House Marik in 2928, doing enough damage to put it out of commission for five years)
Tsitsang (in the city of Pealung - a facility capable of handling a lance)
Victoria (Star League-era repair facility)
Xanthe III (hit by Sung's Cuirassiers in 2668 - though that date is suspect, since it's in the middle of the "Good Years" of the Star League)
Yamarovka (a mammoth structure built by the Nova Cats after their Abjuration)
York (Blood Spirit main repair facility in Boques)

Since the Clans have the technology, I would assume they have plenty of repair facilities, and construct new ones all over their holdings. 
« Last Edit: 11 October 2016, 09:49:06 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1446 on: 08 October 2016, 03:50:55 »
Sigh.  (I’m a die-hard Capellan, and the writer’s bible for TRO:3025 and TRO:3026 appears to have included a mandate that “House Liao never wins.”)
But isn't that exactly why us 3025 grognards love the Confederation, Comrade? It's an uphill struggle with real opportunity for achievement, as opposed to Davion or Dragoons where anything but a complete walkover of any opposing force is considered a shameful loss. ;)

The Periphery sourcebook has the Taurians manufacturing Rommels in 3026.  With Hansen’s Roughriders deploying the tanks in the field for the first time in 3020 (we think, based on the estimated date of Bear Peters’ “The Race is Not to the Swift”), it’s possible, but this raises questions about the Taurian Ministry of Intelligence demonstrating a reach and sophistication far beyond what its reputation would suggest.  Or else ComStar stole the designs and supplied them to the Taurians just to mess with House Davion.
Although I cannot check my sources right now, TPTB have repeatedly stated that this is a genuine reporting error and that the tank was never produced elsewhere. (Isn't this even mentioned in TRO3039?) It's not even a canon rumor. It's just plain wrong.

And while you're technically correct on the intro date of the Hunter, there's a BattleCorps story (Broken Blade) that has it anachronistically appear the Hunter in a prominent role in 2787.

The Packrat’s jamming abilities were used to great effect against the Gray Death Legion on Helm.  The Packrats there were even referred to as Packrat ECM vehicles.
I was under the impression that these were special ECM systems mounted on Packrat frames, not regular Packrats, given how effective they were. Probably a FWL equivalent to the Capellan ECM attempts on the Raven. A FWL ECM system features prominently in a Snord's Irregulars scenario so the FWL is no stranger to recovered ECM tech, though it doesn't get much pagecount (probably on account of the FWL being the forgotten stepchild of BT fiction until it is used to breed the militant WoB).

The Long Tom’s impressive writeup conceals the fact that, at the time, the Long Tom was highly ineffectual, with just a 7-hex AOE burst.  The new rules giving it an extra ring of damage make it much more of a factor.
Given the hype about 'Mechs ruling the battlefield, I feel that the newer artillery rules are way overpowered. The Long Tom outshines all other artillery systems to the point where it is almost the only artillery ever mentioned in fiction at all until the arrival of Arrow IV, which is a bit bland imho. Thumpers and Snipers are sadly ignored although the impression was given that the Long Tom is somewhat rare and valuable, and the least likely of all artillery systems to appear on a battlefield.

It may be worth mentioning that both the Long Tom and the Boomerang have had problems getting their stats correct for a long time, being extreme examples of vehicle construction each in their own regard.

The Repair Facility is... not really a unit writeup. It says even in the text that not two look alike and that they're usually pretty much pounded to scrap anyways. The whole paragraph is more airy fluff than anything else imho.
« Last Edit: 08 October 2016, 04:12:58 by Frabby »
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1447 on: 08 October 2016, 09:05:07 »
The developers have given the Taurian Rommel as a pure error, and an example of why they consider Rick Stuart's Periphery book secondary canon.  I was just casting about for ways it could be true.

The Packrats on Helm could have been modified, since they're called Packrat ECM vehicles, rather than Packrat LRPVs.  However, the LRPV's write up says it can jam enemy transmissions, so it doesn't appear to have needed additional special equipment.

I included the repair facility because they are core tactical elements of MechWarrior 3, MechWarrior 4, and MechCommander.  One of the big ones appears in the Crescent Hawk's Revenge, as well (and possibly Inception, depending of what you make of the Mech-it-Lubes...).  While there are substantial variations, just as with Castles Brian, the one described could be considered a "baseline average" for such structures, while the Clan automated versions (equipped with COMCore IIC computers capable of carrying out diagnostics and repairs autonomously) on Port Arthur could be considered Clan standard.

I noted in the review of Broken Blade that the Hunter was an anachronism.  More recently, I've speculated that the "Broken Blade" Hunters were the Battledroids version, rather than the TRO: 3026 version.
« Last Edit: 08 October 2016, 09:51:34 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

skiltao

  • Lieutenant
  • *
  • Posts: 1218
    • SkilTao's Gaming Blog
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1448 on: 08 October 2016, 17:38:30 »
Lots of good bits in these sections. Can't call out everything, but I especially liked the crescent hawks' ship, and MediQuik units appearing in the animated series is clever and amazing and I'll have to look for them.

re: artillery effectiveness: the MW1e event table has artillery tubes often appearing in pairs. Partially overlapping the AoEs produces more impressive results.

re: units lacking official rules until recently: well, *I* certainly still think of Maximum Tech as a "recent" book, but with each passing decade I think fewer and fewer people agree. ;D

I’m not sure exactly when Pearce and Reynolds could have gone to guns against each other

No opinion on that, but I want to say that the combination of the name Reynolds with a God/no-God philosophical clash makes for a tantalizing parallel with Joss Whedon's Firefly.

Quote
I’m sort of at a loss to explain the 2952 Marik raid on “Andorian V” (almost certainly meant to be Andurien V). <snip> seldom seen combat action over the last 50-75 years,” which would imply that they did have heavy combat in 2950 – confirming a major Capellan incursion into Andurien space right around 2950. 

That's a good fit. The Andor/Andur thing has got me thinking that "Andoran Industries" might've had a facility somewhere in the highly populated area near Andurien (around Betelgeuse, Sigma Mare, Buenos Aires, Principia, Barras, Turin and Drozan).

If only the Rasalhagians had decided to call their clones the Axl and the Slash instead of the Axel Mk I/Axel Mk II. :)
<snip>
The statement that the Rommel and Patton are the first new tanks since the Star League is nonsense.

Heh. :) (I was wondering about the Slayer entry too.) The other tanks *might* be derived from Star League designs (your Battledroid Hunter theory could dovetail with that), but yeah, this seems like one of those bits with one foot in BattleDroids and one foot out. The "Desert Knights" bit is a really nice touch.

It is a bit perplexing that any of the Lyran-Taurian transplants weren't chalked up to Roughriders joining the Concordat.

Quote
Why would House Marik take control of a vast number of Galleons in the 2780s, own and operate the factories that make them, but not use them until 2910?
<snip>
perhaps ComStar mistook the Dragoon Badger (also 30 tons, moving 6/9) for the Galleon.

Well, the entry also says that Davion's Galleons are unremarkable because they aren't concentrated anywhere; so Marik could have had Galleons spread thinly (like most Houses do with Banshees and Chargers), with 2910 marking the first time they were used in a significant concentration. From the description in the Marik sourcebook, the Galleon wasn't a major part of Marik's tank forces until the Holt factory was rebuilt, shortly before the Battle of Zion.

The Badger connection is an intriguing thought.

The Repair Facility is... not really a unit writeup. It says even in the text that not two look alike and that they're usually pretty much pounded to scrap anyways. The whole paragraph is more airy fluff than anything else imho.

That's the point of half the units in the chapter, though. To flesh out the non-'Mech-battlin' parts of warfare.

Speaking of which, that entry mentions tool, cutting, joining, electrical, sensors, fusion and gyro kits - which are all described in MechWarrior 1st edition - and then also *emergency* kits, which aren't. What do you suppose those are for? Defusing live munitions?
Blog: currently working on BattleMech manufacturing rates. (Faction Intros project will resume eventually.)
History of BattleTech: Handy chart for returning players. (last updated end of 2012)

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1449 on: 10 October 2016, 21:51:46 »
The entry giving Taurians the Rommel was circa 3025, and the Roughriders didn't join the Concordat until decades later, so they couldn't be a vector. 

I'd guess "emergency" kits are toolsets to work on BattleMech emergency systems - ejection seat, fusion plant heat warning override, ammunition ejection mechanisms, etc.

I was thinking of the ruleset from the hardback rulebooks.  Maximum Tech came out while I was in the Peace Corps, and I didn't play in graduate school, so I never used the rules therein (by the time I got back to playing, Total Warfare was out).  Showin' my geezerhood.
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1450 on: 10 October 2016, 21:57:34 »
Date: May 17, 3025
 
Title: DropShips and JumpShips
 
Author: Clare W. Hess; Art by Steve Venters (cover) and Dana Knutson (ship design and illustration)
 
Type: Sourcebook (FASA)
 
Synopsis:

Scout: The Scout is the smallest JumpShip in use today, able to carry a single DropShip.  A purely military vessel, it has a bay for a single shuttle or aerospace fighter.  The command decks are at the fore, and the engineering section is at the ship’s aft.  Between the two is the Kearny-Fuchida drive, a docking collar, and a 450 ton cargo bay.  Crew have access to excellent recreational facilities and a well-equipped medbay.  Lacking a grav deck, it can generate the effects by thrusting back and forth while at the jump point, but not while charging the drive.  The Quetzalcoatl serves House Liao, but replaces the docking collar with bays for 20 aerospace fighters, to provide fighter superiority at a system’s jump point.  It is still manufactured by Houses Marik, Steiner, and Kurita, and its Frequency is listed as “Uncommon.”

Merchant:   The Merchant is used by independent traders corporations, and mercenary units, and was designed for commercial haulage.  It has a rotating grav deck for crew to use while the ship is on station-keeping mode, and contains a lounge and recreation center.  Some ships use it for crew quarters.  The design’s original power converters are LosTech, and replacements take 10-20% longer to recharge the jump drive.  The design is particularly common in the Lyran Commonwealth.  Even outside the Commonwealth, its Frequency rating is “Common.”  It is still in production by House Kurita, Liao, and Steiner.

Invader: The Invader is the most common JumpShip operating in the Successor States (46%), still being manufactured by all five Successor States.  With three docking collars, it can economically carry a significant amount of cargo (including an onboard 1,000 ton capacity bay), and could, with the right DropShips, bring an entire regiment into battle.  It is more self-sufficient than most JumpShips, equipped with two automated hydroponic gardens for oxygen and fresh produce in the domes attached to the command module.  The domes can pivot to maintain an orientation perpendicular to the direction of thrust, allowing “down” to remain constant when the ship is underway, though these systems frequently break down, and can interfere with K-F field formation when fully extended.  Most carry a few particle cannons or lasers for meteor defense.

Star Lord: The second largest JumpShip ever constructed, the Star Lord is still produced by Houses Marik, Kurita, and Davion.  It uses special grappling systems to assist with docking, reeling in smaller ships with electromagnets.  It can carry 3,000 tons of cargo on board, in addition to what its DropShips may be carrying.  It is unusually spacious and luxurious.  Its small fusion power plant is capable of quick charging the K-F drive in only 48 hours.  Its Frequency rating is “Rare.” 

Monolith: The largest JumpShip class still in existence, the Monolith is produced by Houses Liao, Steiner, and Davion.  It has a capacity of nine DropShips and 7,000 tons of cargo, and serves exclusively as a military asset.  As such, it has fuel tanks to serve as a fleet supply ship, a large, well-equipped combat operations control center, and relatively heavy armor.  Its Frequency rating is “Rare.” 

Notes:   I’ve decided to go back to DropShips and JumpShips and do the kind of “deep dive” I did for TRO:3025 and TRO:3026, since this is, properly, the first in ComStar’s TRO series.  The book has a completely different format than the Technical Readout series, but appears to be the first in the series nonetheless. 

The cover art contains some of the best illustrations of space vessels shown in the game to that point, clearly illustrating the aesthetic and, as usual for FASA, sneaking in some little in-jokes. (If you turn the book sideways, you can see the name of the Overlord DropShip on its hull – “Knockout Dropper”).  We have Steve Venters to thank for that.  He also did the iconic Mad Cat and Elemental cover for the BattleTech Compendium and several other covers for FASA’s BattleTech, Shadowrun, and Star Trek, as well as art for Traveller, Twilight 2000 and 2300 AD.

The Invader entry actually gives a statistical breakdown of the number present in the Inner Sphere – something popular in early products, but which became something to avoid in later products as the specificity got in the way of plot advancement.  Doing the math, it appears that FASA intended there to be 920 Invaders in the Inner Sphere circa 3025, with 469 serving the military, 294 in merchant hands, and 157 in mercenary service.  Since the Union is the most common transport, let’s assume each Invader, on average, carries a single battalion.  That would give the Inner Sphere a combined carrying capacity of 156 regiments circa 3025 – plenty for the anemic size of ‘Mech TO&Es, but nowhere near enough to carry all the supporting infantry and armor units.  Since Merchants are also “Common,” we can guestimate them at 40% (800, with 320 in the Lyran Commonwealth and an average of 120 serving in each other Successor State – probably with fewer in the Confederation, more in the Federated Suns – though since “most are privately owned and operated” it wouldn’t be very common in the Successor State fleets, maybe 10%).  That leaves only 280 vessels to represent all other JumpShip classes. 

The Scout is “Uncommon,” and the Star Lord and Monolith are “Rare.”  The Monolith entry equates “Rare” with “several dozen,” so… 36 Monoliths – all House military (16 for the Combine, 8 for House Davion, 8 for House Marik, 2 for House Liao and 2 for House Steiner), and 40 Star Lords – 30 of which serve the Successor States, the rest are for MegaCorps and major mercenary groups (12 for House Marik and 18 split among the other Houses – 8 for Kurita (they make ‘em), 4 for Davion, 4 for Steiner, 2 for Liao).  That leaves 204 Scouts, which fits the “Uncommon” moniker. 

The House Marik sourcebook, thanks to the “Adventure Architects,” gave the FWL twelve independent fleets of JumpShips, with 3-6 JumpShips each, with a minimum combined carrying capacity of 10 DropShips and a maximum of 15.  That would (assuming an average of 4.5 JumpShips per fleet) give the FWLN 50 military JumpShips not attached to ground units.  These would presumably carry the bulk of the League’s Assault DropShips.  I would guess the other Successor States have similar Assault DropShip/Military JumpShip fleets, probably in similar quantities.  So that accounts for 250 JumpShips. 

So, I’m guesstimating FASA’s intended House military fleet strengths to be approximately:
Liao:  30 Scouts; 8 Merchants; 64 Invaders; 2 Star Lords; 2 Monoliths (Capacity: 267 DropShips – 1 Scout is the 0 DropShip-capacity Quetzalcoatl)
Marik: 36 Scouts; 12 Merchants; 75 Invaders; 12 Star Lords; 8 Monoliths (Capacity: 429 DropShips - 150 for the Assault fleets, 279 for ground force transport)
Steiner: 41 Scouts; 32 Merchants; 80 Invaders; 4 Star Lords; 2 Monoliths (Capacity: 387 DropShips)
Kurita: 46 Scouts; 12 Merchants; 110 Invaders; 8 Star Lords; 16 Monoliths (Capacity: 598 DropShips)
Davion: 51 Scouts; 16 Merchants; 140 Invaders; 4 Star Lords; 8 Monoliths (Capacity: 599 DropShips)
Mercenary: 157 Invaders; 5 Star Lords; (Capacity: 501 DropShips)
Merchant: 294 Invaders; 720 Merchants; 5 Star Lords (Capacity: 2,352 DropShips)

Since House Davion controls about 25% of the Inner Sphere circa 3025, let’s assume that 25% of the merchant ships are in Davion systems.  The mass-impressment of commercial ships in the Federated Suns would have increased Davion troop carrying capacity by 588 DropShips – nearly doubling Davion troop carrying capacity)

Of course, the estimated number of JumpShips was raised from 2,000 to 3,000 by the 3055 Mercenary’s Handbook (presumably accounting for either a surge of new production or the arrival of the Clan JumpShip fleets into the Occupation Zone), and then boosted to at least 20,000-30,000 by Strategic Operations (which clarified that the 2,000 figure only represented the 10% of captains who had taken the time to register their ship with ComStar, and that the real number was at least an order of magnitude greater).  The ratios may still apply, though.

Scout:   It makes sense that the Scout is a purely military ship, since the transit time is about the same, but it can only haul one DropShip of goods and/or paying passengers.

The Quetzalcoatl variant essentially transforms the Scout into a Vengeance fighter-carrier, albeit one limited to hitting jump points.  If pirate points are used, its fighters can be used in a planetary strike as well.  There’s no need to make the conversion, however, if you already have a Vengeance, since you could just dock it with the JumpShip as normal. 

Merchant: Trade was the lifeblood of the Star League, so it makes sense that there were so many Merchants.  Likewise, when the Successor States were targeting enemy JumpShips during the First and Second Succession Wars, they’d be more likely to target military ships for destruction, while settling for capturing or ignoring merchant vessels. 

The capacity for two docking collars is especially critical for Merchants, since the most cost efficient cargo DropShip, the Behemoth, takes up two collars.  I can’t really tell from the illustration in DS&JS, but it appears to put one docking collar on the dorsal hull and one on the ventral, with small craft bay doors on the sides.  That would seem to preclude a Behemoth hookup.  (Alternately, the collars could be on the far side, opposite the bay doors.) 

The illustration in TRO:3057 doesn’t help, unfortunately, showing a different configuration of bay doors, but no docking collars on the ventral surface.  Even the picture of the IWM miniature in their store shows just the cargo bay doors, not the docking collars.  Still, the lack of a dorsal docking collar in the 3057 art, and the need for it to be able to accommodate Behemoths, is a strong argument for it having two collars side by side on a single side of the hull, opposite the small craft bay doors.  If anyone has the miniature, I’d appreciate hearing what the docking collar configuration is on the sculpt.

Invader: I’ve asked in the forum, but there aren’t any statistics for how heavy/expensive hydroponic domes should be – they aren’t accounted for in the construction ruleset, despite being major structural elements of the ship. 

The anti-meteor defenses are “still useful for repelling boarding attacks,” but unless just a single fighter is buzzing you, it won’t be enough to stop a serious boarding attempt.  I think the best use would be to try to burn down any boarding shuttles/battle taxis inbound.  They certainly aren’t capable of living up to Renfred Tor’s boast that the weaponry on an Invader can burn down an incoming DropShip from 30,000 kilometers away.   

Star Lord: The description of a 48-hour minimum for quick charge doesn’t sound like much of a drawback, given that the current rules usually require at least 5 days to hot-charge the engines.  The only time you really save is by not having to extend and retract the sail.  It appears that the original intent was for ships to be able to quick-charge their drives in just a day, dramatically increasing speed (at a not insignificant risk, unless you had an elite crew). 

Able to carry six DropShips, it could carry up to two regiments into battle, or three Behemoths. 

Monolith: The Monolith is named the largest JumpShip “still in existence,” implying there were larger at one time.  This doesn’t square with the Star Lord’s claim to be the second largest ever created, putting the Monolith in the #1 slot, and leaving no room above.  It might have been a poorly worded reference to the vanished combat WarShips of the Star League, though. 

The Star League liked to send out entire Divisions at a time, the better to overawe their foes.  The Overlord and Monolith were both very late additions to the Star League, with the Monolith actually beginning production during the Star League Civil War.  I can imagine that SLDF planners would have envisioned great uses for a transport ship capable of hauling a Brigade (three regiments) aboard nine Overlords.  That way, you could move an entire Division with just three JumpShips and 27 DropShips.  Give ‘em a WarShip for escort, and you’ve got a Naval Transport Lance that can put a massive amount of force in one place, or split off and hit three separate targets with a Brigade each.  Unfortunately for them, Overlords were just entering service a decade before the Civil War broke out, and comments by one of the MechWarriors in “When the Bears Left” suggested he’d never seen one before (during Exodus preparations).  Sure, Monoliths are expensive, but the Star League was rolling in resources, so what did they care?
« Last Edit: 10 October 2016, 22:13:00 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Kit deSummersville

  • Precentor of Lies
  • Freelance Writer
  • Lieutenant Colonel
  • *
  • Posts: 10402
  • The epicness continues!
    • Insights and Complaints on Twitter
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1451 on: 11 October 2016, 09:25:11 »
It seems odd that Houses Steiner and Liao would be producing the Monolith and only have a pair each while manufacturing it yet House Kurita has over a dozen and doesn't make any.
Looking for an official answer? Check the Catalyst Interaction Forums.

Freelancer for hire, not an official CGL or IMR representative.

Everyone else's job is easy, so tell them how to do it, everyone loves that!

Millard Fillmore's favorite BattleTech writer.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1452 on: 11 October 2016, 09:51:44 »
The DS & JS TRO was obviously meant to cover the types still in regular production (the Tramp was produced only sporadically at the time), and comments like "largest" and "smallest" refer to that frame. The Explorer-class JumpShip, for example, is much smaller than the Scout and as small as JumpShips get under standard construction rules.

Almost all of these standard JumpShips have quirks (at least per fluff):

The Scout can recharge faster than others, and has a smaller emergence signature making it somewhat stealthy. The former ability isn't reflected in any rules, but in-universe goes a long way to make the design, um, less non-viable.

The Merchant, by contrast, takes considerably longer to recharge than others. Which raises the question of how such a small and slow ship could ever become so widespread.

The Invader is known for its command center. Which suits its martial name, but... really makes zero sense on what is a purely civilian vessel, the proverbial yardstick and the Volkswagen Beetle of JumpShips. Sidenote, I never understood how or why the original Liberty JumpShip had four hardpoints but the most prolific later designs had fewer.

The Star Lord has those grappling arms and is explicitly mentioned as a useful recovery vehicle. Since Tramp production was largely switched over to Star Lords I find it surprising that they are supposedly "rare". In any case, they are probably the best standard JumpShip out there. And they are definitely not the "second-largest JumpShip class ever constructed". Not in the face of the Monolith and Leviathan, neither of which is particularly secret. ComStar dropped the ball here.

The Monolith, touted "the largest jump-capable vessel" of ca. 3025, notably had its mass changed from originally 380,000 tons to 430,000 tons in later publications to account for changes in the construction rules. This is of course problematic when a Monolith like the Rubicon from Tactics of Duty is explicitly spelled out to mass 380,000 tons.
Wonder what "largest" refers to. The Newgrange, if you consider it a civilian JumpShip, eclipses the Monolith in both mass and length, and the latest XTRO (which I don't have) gave us Leviathan stats.

ComStar's claims about merely less than 50 Monoliths still existing in the armies of the Successor States are a blatant lie, or at least a half-truth. They clearly omit those Monoliths operated by merc units (hello Wolf's Dragoons) and if the class was really so rare then it wouldn't have been mentioned in the document, being clearly outnumbered by Tramps. Personally I'm convinced that ComStar maintained a substantial commercial JumpShip fleet and that Monoliths were present in that fleet in some number.

I've posted my bets for JumpShip type ratios across the IS in the forum's previous iteration but the thread was unfortunately lost in the forum crash. The numbers were something like this (for 30,000 vessels in existence):

46% = 13,800 Invader
30% = 9,000 Merchant
12% = 3,600 Scout
8%  = 2,400 Star Lord
2% = 600 Monolith (a smaller percentage arguably wouldn't have been covered in the book)
2% = 600 other (Tramp {numbers unknown but implicitly most numerous "other" class}, Explorer {ca. 20 known to exist}, Leviathan {at least 1 known to exist}, Uma {1 mentioned with the Explorer Corps in 3055}, and all those other unmentioned, obsolete, apocryphal or questionable classes including Quetzalcoatl, Liberty, Cameron, Royalty, and whatnot.)

Finally, the Large DropShip quirk. This is based on the fluff for the Behemoth (which is explicitly confirmed to possess this quirk in StratOps) and obsolete and since abandoned rules stating that all DropShips above 60,000 tons (then only the Behemoth) require a second hardpoint. The reasoning given in fluff was not that they technically needed two KF booms, but rather that they would block an adjacent hardpoint due to their size. They could still be carried on Scouts.
« Last Edit: 11 October 2016, 09:53:50 by Frabby »
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1453 on: 11 October 2016, 09:57:19 »
It seems odd that Houses Steiner and Liao would be producing the Monolith and only have a pair each while manufacturing it yet House Kurita has over a dozen and doesn't make any.

I considered this - and the oddity of the Combine having the most without any manufacturing is explicitly noted in the writeup.  The entry says specifically that nearly half are in the Combine, with the fewest in the Commonwealth and Confederation.  The rate of manufacturing means that output probably doesn't really affect the number too much, and that the Lyrans and Confederation had the greatest losses in this class, while the Combine held onto their better.  The table of who manufactures what doesn't seem to have been well synched with the entry, which says the Federated Suns makes two vessels every three years, while (until recently) the Federated Suns made one every two years, but the factory has recently failed. 
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

skiltao

  • Lieutenant
  • *
  • Posts: 1218
    • SkilTao's Gaming Blog
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1454 on: 11 October 2016, 16:22:22 »
I usually figure Merchants as 46% of what's left over after Invaders, Scouts as 46% of what's left over after them, and so on; based on the random tables in MW1e and comments in DS&JS, I refined that estimate to 540 Merchants, 225 Scouts, 160 Star Lords, 65 Monoliths, and 90 more obscure types.

I think an average of three collars per JumpShip (or a total of 6000 collars sphere-wide) is a good rule of thumb. The Crucis Lancers' assault on Tikonov used approximately that ratio, and I notice that DS&JS has about 3x as many DropShips being built as Jumpships ("30 to 45" DS is roughly 37.5, vs 12 JS + .5 Monoliths from the broken Marik line).

It's interesting that the Invader's percentages amount to a 1d6 table.

The KF drives in DS&JS mass 40ktons + 35ktons per collar. Interestingly, 1.5x 35ktons is 52.5 ktons (the mass of a Mammoth) and 1.5x (35+35) ktons is 105ktons (the mass of a Behemoth). If the size of a KF Drive were proportionate to the size of the DropShips it can carry, then a ship like the Leviathan could have seven or more collars while still being smaller than a Star Lord.

The entry giving Taurians the Rommel was circa 3025, and the Roughriders didn't join the Concordat until decades later, so they couldn't be a vector. 

Whoops! I meant Little Richard's Panzer Brigade. (I should've just said "those mercs mentioned in 3050's Hatchetman entry.")
Blog: currently working on BattleMech manufacturing rates. (Faction Intros project will resume eventually.)
History of BattleTech: Handy chart for returning players. (last updated end of 2012)

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1455 on: 12 October 2016, 18:20:02 »
Date: May 17, 3025
 
Title: DropShips and JumpShips
 
Author: Clare W. Hess; Art by Steve Venters (cover) and Dana Knutson (ship design and illustration)
 
Type: Sourcebook (FASA)
 
Synopsis:

Fury: The Fury carries four infantry platoons and eight light (50 tons or less) vehicles.  They are typically deployed in groups of three, following behind an Assault DropShip group, and escorted by at least one fighter carrier.  They normally operate in conjunction with Gazelle-class armor carriers.  Its frequency rating is “Uncommon.”  It is manufactured only by House Marik.

Gazelle: The Gazelle’s purpose is to transport an armor company, with a bay capable of holding 15 tanks and their crews.  Designed for the small vehicles typical of the 2500s, the bay had to be enlarged to accommodate larger tanks.  The bay arrangement can cause substantial delays for green crews trying to get their vehicles offloaded, so Gazelle captains usually work out a detailed offloading plan for maximum efficiency.  Gazelles normally operate on raids and invasions in battlegroups accompanying Fury troop carriers, fighter carriers, and assault ships.  Its frequency rating is “Uncommon.”  It is manufactured by Houses Marik and Davion.

Seeker: Introduced in 2815, the Seeker’s mission is to carry a combined arms scout battalion into hostile territory.  It carries four ‘Mechs and 48 light vehicles (or 64 light vehicles and no ‘Mechs), and their crews.  Intended to operate completely independently, it has been designed to be self-sufficient in terms of supplies, and to have multiple redundancies for key systems.  It lacks fighter bays, but a vehicle bay can be jury rigged to carry a pair of fighters, though they cannot be recovered via combat landings – the ships must exactly match velocities and vectors, taking two or three times longer than normal recovery operations.  It is manufactured by Houses Liao, Steiner, and Davion, but the frequency rating is “Rare.” 

Triumph: The Triumph, introduced in 2593, can carry a full armor battalion, and to rapidly unload its cargo once landed.  The ship has a tactical operations center to coordinate ground movement.  With some modifications, it can also transport ‘Mechs, aerospace fighters, conventional aircraft, and artillery.  Circa 3025, it is manufactured by Houses Kurita and Liao, with a “Rare” frequency rating.

Condor: Capable of delivering an infantry battalion (12 platoons + 20 vehicles and their crews – 336 personnel in all), the Condor can offload its troops one company at a time.  The Condor was introduced in 2801 and, circa 3025, is manufactured by Houses Marik and Kurita, with an “Uncommon” frequency rating.

Excalibur: The “Rare” Excalibur is manufactured by Houses Kurita, Liao, and Steiner, and is designed to carry a combined arms regiment (two tank battalions, one infantry battalion, and one ‘Mech company) into combat.  Its primary role is to deliver reinforcements to support active invasions or sieges, escorted by fighters and landing in secure zones. 

Notes:  

Fury: From the description, the Fury is usually deployed as part of a large combat group.  Three Furies, a Leopard CV, 2-4 Assault DropShips, and probably another three Gazelles and another escort Leopard CV.  12 DropShips (12 infantry platoons, 12 fighters, 24 light vehicles, 45 heavy vehicles) – delivering an infantry battalion, an armor battalion, and two companies of support vehicles and transports.  Given JumpShip availability, this would likely be delivered by a naval lance of four Invaders.  Since it is only made by House Marik, this sort of combined arms fleet is probably unique to the Free Worlds League. 

This would give a raid or planetary assault a variety of combined arms assets – mobile HQs, coolant trucks, MASH units, APCs, scout vehicles, ordnance transports, etc., plus three companies of heavy tanks.  I can see this coming in as the support crew for a ‘Mech battalion – letting them do the heavy hitting, having the heavy tanks secure the flanks, infantry secure and police whatever they’re hitting, and light vehicles perform scouting and specialist support.

Gazelle: Appropriately, the 75-ton Merkava was the heaviest armored vehicle design fielded prior to the Gazelle’s introduction in 2531.  It was most likely the debut of the Alacorn 30 years later in 2561 that prompted the expansion of the cargo bay to hold more of those 95-ton beauties, since I’m sure everyone wanted to get as many of those as possible onto the field.  (The final tonnage of the bay – 950 tons – suggests the metric for the expansion was to accommodate 10 95-ton tanks.  The original design probably topped out at 750 tons – just fine for bringing 10 Merkavas into play, or filling each bay to capacity with fifteen 50-ton tanks like the LTV-4 Hover Tank or the Turhan.)

The description of the ship’s vulnerability while offloading on the ground highlights one of the main advantages of ‘Mechs – they can be dropped from orbit without exposing the DropShip to hostile ground fire.  I would presume they’d try to hit an LZ that the Furies’ infantry had taken first and secured, so that they could unload peacefully, but the fact that the captains are so concerned about offloading speed indicates that their LZs come under fire regularly enough to be an existential question.

The drive system listed in the entry must be an upgrade over the original design, because it would be passing strange for it to be called the “Star League V95” in 2531, 50 years before there was a Star League.  I would surmise, then, that the redesign to carry heavier vehicles took place during the Star League era, and that it was carried out concurrent with a change to the drive system, replacing the Age of War original with the V95. 

Since it is only manufactured by Houses Marik and Davion, the pairing with Fury-class DropShips is only likely in Marik space, while House Davion probably uses them as its primary armor transport (it’s the only one they make) for its RCTs.  Since each carries just one company, a full RCT (with three regiments of combat vehicles) would need 27 of these DropShips.  Moreover – the Federated Suns doesn’t manufacture any dedicated infantry transports, so its five infantry regiments would need to either ride in converted Gazelles or Monarchs refitted as troop transports (the former is probably more likely, since the Monarch entry says they are only rarely hired out as troop ships, and their low speed and lack of armament would seem to preclude successful combat insertion maneuvers).  Essentially, any time a full RCT moves out, it’s accompanied by a vast fleet of Gazelles.  (The Condor and Triumph would, of course, be ideal for RCT deployment…but they’re all exclusively made by Kapteyn Accord signatories – aka the FedCom Revenge Society).

Seeker: With a late First Succession War introduction date, and being made only by Houses Liao, Steiner, and Davion, you wouldn’t expect House Kurita or House Marik to have any of these.  As a scout ship, its complement should reflect its mission – gather intel and survive to report back.  It would also be an excellent command ship for running Loki, Rabid Fox, or Maskirovka black ops missions.

I would expect typical loadouts to include (in addition to the standard 3025-era style of scout lance – 6/9/6 or better with primarily energy weapons – though in the Liao case they may assign some of their 1X prototype Ravens to such ships):
Lyran:  Hi-Scout Drone Carriers + Drones; Packrat LRPVs; Skimmers; Centipede Wheeled Scout Cars; a Mobile HQ to coordinate, Quick Dart spotter planes; and some Drillsons for fast muscle in a pinch.
Davion: Darter Scout Cars; Skimmers; Boomerang Spotter Planes; Ferret Light Scout VTOLs; a Mobile HQ; and Condors for emergency combat.
Liao: Swift Wind Scout Cars; Skimmers; Condors.

There would also be utility in adding microsatellites to the mix, and to including a selection of civilian ground vehicles of the type that would be found on the target planet, so scouts could use them to blend in more easily than, say, a 50-ton Condor flying the Federated Sunburst blasting along full-speed down Kalvin Liao Boulevard.

Triumph: Introduced in 2593, it seems clear that it was commissioned commissioned in response to the evident need for a large-capacity armor transport – a lesson learned from more than a decade of fighting in the Reunification War.  It’s only manufactured by Houses Kurita and Liao, circa 3025.  Oddly, it assumes that an armor battalion = 45 heavy vehicles + 8 light vehicles, while Field Manual: Capellan Confederation defines an armor battalion as 36 vehicles.  A better description, therefore, would be that the Triumph can carry a reinforced battalion (48 vehicles).  Field Manual: Draconis Combine notes that the DCMS just deploys armor in battalion strength (36 vehicles), and doesn’t use reinforced battalions.  This would mean that Combine Triumphs deploy only partly full.  FM: SLDF shows that armor companies there were also 36 vehicles, making the Triumph oversized for their needs.  The extra slots, of course, could be used by support vehicles, letting a SLDF formation field 36 Alacorns, and still demonstrate tactical flexibility with engineering vehicles, mobile HQs, scout vehicles, etc.

The 45 tank capacity would seem to best fit the FWLM’s “Squadron” formation, which consists of 30-45 tanks (2-3 companies).  This would suggest that the Free Worlds League pioneered the design for their own use, and shared it with other League member states during the “Good Years,” but lost the factories for it during the Succession Wars, leaving the remaining factories in Capellan and Combine space (with a bay not exactly suited to their TO&E).

While Gazelle crews are described as being afraid to touch down on the field for long – wanting to offload and then flee back up to the relative safety of orbit, the larger Triumph appears intended to land and rely on the firepower of their reinforced tank battalion to own the surrounding terrain.  The command center would suggest it is intended to serve as a command post for the campaign, and not just as a resource for rapid orbital redeployment, like the Gazelle.  This ship would probably be the dominant armor transport in the Inner Sphere if not for its rarity.  While the Gazelle is “Uncommon,” the Triumph is “Rare.” 

ComStar gives an estimate of 25,000 DropShips in service in 3025.  If “Rare” for JumpShips equates to “several dozen” out of 2,000 (2%), then it may proportionately equate to the same percentage of DropShips, suggesting FASA intended there to be around 500 Triumphs serving in the Inner Sphere.  That seems sufficient to provide Capellan Home Guard Regiments some mobility, as well as enabling the Combine to shift their armor battalions around in support of DCMS BattleMech offensives. 

In modern times, of course, the “ComStar was off by an order of magnitude” guidance from Strategic Operations probably applies to the DropShip estimates, bumping it up to 250,000 in the Inner Sphere, and, therefore, 5,000+ Triumphs. 

Condor:   Unlike the Triumph, which seems custom fit to FWL armor company sizes, the Condor is too small to accommodate the larger-than-usual FWL infantry battalions, which consist of 448 troops (four 112-man companies).  I would presume, therefore, that League Condors are modified with additional infantry bays.  (This is a minor change that involves swapping out 20 tons of cargo bay space for infantry accommodations.)

The 20 vehicles would presumably consist largely of APCs.  Traditional APCs (one squad per vehicle) would only provide mobility for five of the nine platoons, whereas using Maxims or Heavy APCs would enable the entire force to be mechanized, and still leave 11 slots (Kurita) or 4 slots (Marik) open for light support vehicles – scouts, engineering vehicles, MASH units, etc.

Interestingly, despite its heavy reliance on infantry in its RCTs, House Davion does not manufacture any dedicated troop carriers, except the rare combined-arms Seeker.  Unless they have a stockpile from the early Succession Wars, AFFS infantry would appear to deploy in modified Gazelles.  Likewise, Steiner and Liao infantry would need to use the rare Seeker or the rare Excalibur.

Excalibur: It would seem that the initial landings would be relegated to ‘Mech carriers, while the Excaliburs bring in command companies and headquarters security forces after the landing zone is secured, and, later in the campaign, be tasked with bringing in replacement personnel for armor, infantry, and ‘Mech losses. 

Lacking a manufacturing line for armor carriers, House Steiner appears to rely heavily on the Excalibur to transport its armor units in support of ‘Mech-led offensives.  Despite manufacturing the Triumph, House Kurita is noted as a heavy user. 

The capabilities of the Excalibur are somewhat confused throughout the entry.  One paragraph says each of four vehicle bays can carry 25 heavy vehicles, giving the ship a carrying capacity of 100.  However, the next paragraph refers back to “besides these two vehicle bays…”, raising the question of whether the capacity is 100 or 50.  It is also listed as having accommodations for 600 troops.  The statistics bloc, however, says it can only carry 20 light vehicles and 336 troops, an evident copy/paste error from the previous page’s Condor.  TRO:3057 clarifies that this version can carry 90 heavy vehicles in four bays, 12 ‘Mechs, and 12 infantry platoons (336 infantry).

Being rare, Excaliburs would probably only be risked on major invasion campaigns.  Thus, the ‘Mechs would deploy in the ubiquitous Unions and Overlords, with the Excalbur bringing up the rear with the regimental command company, and elements of the conventional support forces attached to the operation.  The Lyran Commonwealth sourcebook indicates that the LCAF typically forms Combat Teams for offensives, consisting of three regiments of armor, infantry, and artillery.  Lacking the Fury, Gazelle, Triumph, or Condor, the LCAF probably relies heavily on its limited stock of Excaliburs, meaning you can expect to see at least three Excaliburs accompanying every Lyran ‘Mech regiment that goes on the offensive.  This is a relatively compact package that probably gets an Invader of its own. 
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1456 on: 13 October 2016, 00:57:27 »
You often see attacking forces bringing a 'Mech company and conventional support forces - mobile HQ, infantry, recon VTOLs. These all fit neatly on an Excalibur. Whenever the DropShip class isn't mentioned for combined arms deployments I assume Excalibur. Compare to the Kurita attack on Chara III in The Crescent Hawks' Revenge.

It makes a surprisingly good raider if you expect an unopposed landing.
« Last Edit: 13 October 2016, 01:00:33 by Frabby »
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1457 on: 13 October 2016, 02:16:41 »
Agreed, having brought 'Mechs, a Mobile HQ, a Galleon, and (incongruously) Rommels to Lyons (we only see Kurita 'Mechs and infantry on Chara), yet they retreat to "the DropShip," a combined arms carrier can be inferred.
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1458 on: 13 October 2016, 03:08:50 »
Yes, I meant Lyons, not Chara. Kurita is even a noted user of the Excalibur, so it fits.

The Rommel can be explained by combat salvage, possibly even during the Lyons operation.
Thinking of it, it's kinda smart to bring techs and crews as "infantry" on an Excalibur in an "invasion raid" scenario (or however you'd call an extended raid that isn't hit-and-run so much as hit-and-stay-as-long-as-you-please-without-actually-conquering" - you roll over the enemy and capture their units to deploy against them. Makes the Excalibur a yet better baseship for such a raid or even smaller conquest operations, as it brings 'Mech bays but also room for all the bells and whistles - gantries, recovery vehicles, personnel - to make your invasion force self-sufficient and able to swelling their ranks through salvage.
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1459 on: 13 October 2016, 16:43:56 »
Date: May 17, 3025
 
Title: DropShips and JumpShips
 
Author: Clare W. Hess; Art by Steve Venters (cover) and Dana Knutson (ship design and illustration)
 
Type: Sourcebook (FASA)
 
Synopsis:

Leopard:   Introduced in 2537, the Leopard has served since the early days of the Star League, carrying a lance of BattleMechs and a pair of aerospace fighters into battle.  Its primary drive is the powerful Star League V84.  Its angular lines are due to it predating the technology required to forge curved armor plating.  If necessary, each fighter and ‘Mech bay can instead be used to hold up to eight light vehicles, with a combined weight of 150 tons.  It is intended to provide flexibility to unit supporting troops aboard larger ships – deploying reserves to plug holes in the line or executing strategic attacks during larger campaigns.  It is also a favored ship for raiders.  The Leopard is manufactured by Houses Marik, Steiner, and Davion, and has a frequency rating of “Uncommon.”

Union: Introduced in 2708, the Union is designed to take a company of ‘Mechs into battle, along with two fighters.  It has shown great utility on raids, as well as in support of major invasions.  Four drop chutes allow it to deploy its ‘Mechs from orbit a lance at a time.  It is described as having been designed and constructed at the same time as the Overlord.  Like the Invader, the Union is still manufactured by all the Successor States, and is an “Uncommon” sight in the Inner Sphere.

Overlord: The largest ‘Mech carrier of the Succession Wars, the Overlord can carry a full ‘Mech battalion plus a squadron of AeroSpace fighters.  Its rarity restricts it to being used in planetary assaults, positioned directly behind the Assault DropShips and fighters.  It prefers to drop its ‘Mechs from orbit, but if the defenders are able to contest that region, the ship can and will land and deploy its ‘Mechs on the ground (though that makes it vulnerable to attack from both air and ground units.)  If it has a secure landing zone, the Overlord generally serves as the command center and supply base for the invasion operations.  The Overlord is manufactured by Houses Kurita, Liao, and Steiner, but its frequency rating remains “Rare”.

Notes: A large amount of the flavor text in DropShips and JumpShips describes accommodations, quality of life issues, and internal layout.  It seems intended to provide a resource for gamemasters who want to have a detailed internal plan to work from when running boarding, hijacking, or stowaway scenarios.

Leopard: There are a number of problematic statements in this entry.  The argument that it was impossible to make curved armor plating for ships at the time the Leopard was introduced is disproved by the curved hull of the Manatee, introduced in 2449.  The Gazelle, introduced in 2531, also looks fairly curvy in its side-view. 

The use of the Star League V84 interplanetary drive in a 2537 design is anachronistic, since the Star League wasn’t formed until 2570.  (The Gazelle has the same problem, with a Star League V95 drive in 2531…though why an earlier design would have a later engine number is also confusing.)  Presumably it debuted with, say, an “HRAD VXX” interplanetary drive, and was later upgraded.  I would love to get a gander at the early writers’ bible, and see what dates it gives for the creation of the Star League.  My guess is it’s put around 2500, given all the anachronistic references in TRO: 3025 and DropShips and JumpShips. 

As Frabby earlier pointed out, the absence of any cargo space makes the Leopard’s utility as a lone raider dubious.  Where are they going to put what they take?  I would presume that any bandit raiding party would use at least a Merchant, and have the Leopard accompanied by a Buccaneer (what else would a self-respecting space pirate use?) to haul off the booty. 

The allowance of using a ‘Mech or fighter bay for light vehicles without any modifications begs the question of why it’s necessary to have vehicle bays at all?  Presumably it would take significantly longer to unload a bay filled with light vehicles (ranging from three 50-tonners to one 50-tonner and seven 10-ton APCs), but a standard light vehicle bay can only hold one, per standard rules.  It would seem to waste a lot of vertical space, but it’s more efficient than using dedicated vehicle bays.

Union: It’s odd that the writer would claim the Overlord was designed and constructed at the same time and by the same manufacturer as the Union, since the Union’s introduction date was 2708, and the Overlord’s introduction date is given on the next page as 2762.  If they were designed at the same time, why the 54-year gap?  Perhaps the original manufacturer did the design work for both simultaneously, and even made a prototype, but the SLDF rejected it – happy with its existing stockpiles of Dictators.  With tensions rising in the Periphery, I can see the SLDF wanting something with the Dictator’s carrying capacity, but also having integral fighter support, and deciding to order a production run of Overlords (asking the manufacturer to dust off the plans and go to work).

It’s never stated what company made the original Union design, just that the firm was responsible for both the Union and the Overlord.  Looking at the list of firms that make both the Union and Overlord in 3025, we see Matabushi Inc. on Avon and Earthwerks Ltd.  Matabushi is strongly linked with the Combine, but Earthwerks was founded on Terra in 2357.  I would presume, then, that the Terran branch of Earthwerks was the developer of the Union and Overlord in the 2700s. 

The deckplan illustration of the fighter bays shows two fighters lined up behind each other, apparently intended to use the same exit hatch.  The design specs, however, say it has two fighter bay doors, calling into question why both fighters in the illustration are using the same bay door. 

Overlord: Despite being introduced in 2762, it apparently did not reach many SLDF units before the Periphery Uprising in 2765 and the subsequent Star League Civil War.  An SLDF Firestarter pilot getting ready for the Exodus, in “When the Bears Left,” notes that he’s never seen an Overlord before the one that arrives to pick his battalion up. 

A picture of an Overlord appears on p. 44 of the Star League sourcebook in a section discussing the 2573 Malagrotta crisis, 91 years before it debuted.  That even predates the similar looking Dictator (2600).  Given the date, the only spheroids it could be are the Vulture, Pentagon, Jumbo, or Manatee - but none of those have the Overlord's distinct egg shape.  P. 91 shows six Overlords in formation preparing for the 2777 invasion of Terra, so the trooper in “When the Bears Left” was clearly not part of the Terran campaign.  The text notes that Kerensky used 60 unmanned Overlords to neutralize the Amaris battlestations guarding the jump points. 

The fighter bay illustration on the previous page, next to the Union, may actually be for the Overlord, since its six fighters share two bay doors, unlike the Union, where each fighter has its own bay door. 
« Last Edit: 13 October 2016, 18:58:02 by Mendrugo »
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

VhenRa

  • Captain
  • *
  • Posts: 2251
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1460 on: 13 October 2016, 19:23:49 »
Honestly, I have to wonder if those unmanned Overlords at Terra were in fact unfinished Overlords that the SLDF got their hands on during the long march to Terra.

Wrangler

  • Colonel
  • *
  • Posts: 25036
  • Dang it!
    • Battletech Fanon Wiki
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1461 on: 14 October 2016, 22:47:08 »
The description of the Leopard sounds like it's successor the Dark age era Aurora.
"Men, fetch the Urbanmechs.  We have an interrogation to attend to." - jklantern
"How do you defeat a Dragau? Shoot the damn thing. Lots." - Jellico 
"No, it's a "Most Awesome Blues Brothers scene Reenactment EVER" waiting to happen." VotW Destrier - Weirdo  
"It's 200 LY to Sian, we got a full load of shells, a half a platoon of Grenadiers, it's exploding outside, and we're wearing flak jackets." VoTW Destrier - Misterpants
-Editor on Battletech Fanon Wiki

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1462 on: 15 October 2016, 14:04:23 »
Date: May 17, 3025
 
Title: DropShips and JumpShips
 
Author: Clare W. Hess; Art by Steve Venters (cover) and Dana Knutson (ship design and illustration)
 
Type: Sourcebook (FASA)
 
Synopsis:

Avenger: Introduced in 2816, the Avenger packs the firepower of a Union and the armor of an Overlord into a compact 1,400 ton frame.  In addition to its direct-fire weaponry, it is equipped with a 20-ton bomb bay for ground support missions.  Standard procedure is for an Avenger to punch through orbital defenses, locate a landing zone for the invasion force, use its bombs to flatten any obvious defenders in the vicinity, and then land and use its direct fire weapons to keep surviving enemies at bay until orbitally-dropped ‘Mechs and other combat DropShips can land and fully secure the LZ.  Only then do troop ships and cargo transports arrive.  At this point, the Avenger is either reassigned to take another LZ foothold, or put on standby in orbit.  The Avenger is still manufactured by Houses Liao, Steiner, and Davion (with Davion making the most), but its role at the tip of the spear results in a very high attrition rate, giving it a frequency rating of “Unique.”

Achilles: Designed to engage other DropShips and AeroSpace Fighters, the Achilles was introduced in 2582, making its debut during the Reunification War.  It typically leads planetary assaults or the aerospace defense forces engaging inbound DropShips.  It follows close behind a fighter screen, and picks off enemy fighters with concentrated firepower, or trades shots with enemy DropShips.  It carries two fighters aboard for escort duty, and also two S-7A Bus small craft, which can carry 10 troops each.  The Achilles has 30 marines, so it can send two thirds over for boarding actions while still retaining a detachment to protect against hostile incursions.  The Achilles is manufactured only by House Kurita, and has a frequency rating of “Unique.”

Intruder: Introduced in 2655, the Intruder is an assault DropShip designed to support raiding operations or attack hardened ground targets.  It is heavily armed and armored, and carries up to two fighters and ten heavy vehicles for support, as well as three platoons of marines.  To coordinate marine operations, the Intruder boasts a state-of-the-art command center, with com gear, combat computers, maps, and tactical intelligence displays.  It is frequently used on raids and for intelligence gathering, and is able to defend itself without support from other ships.  On planetary assault missions, the Intruder either uses its firepower and support forces to establish a secure landing zone for follow-on transports, or attacks enemy troop concentrations directly.  The Intruder is manufactured by House Marik, Kurita, and Steiner, and has a frequency rating of “Rare.”

Fortress: The best armed and armored DropShip still in operation in 3025, the Fortress is only committed to major invasion operations where it has ample support and escorts.  Introduced in 2613 as a heavy combined arms troop transport, the Fortress can deliver a ‘Mech company, a vehicle company, and an infantry company onto the battlefield.  Its arsenal is mostly oriented towards its aft, allowing it to be unleashed against enemy ground forces within range once it lands.  Even those that pull back will have to contend with the Long Tom III artillery piece mounted on a turret in the nose.  The current rarity of this vessel is due less to combat losses as to age and the unavailability of spare parts, which have led to computer and fire control system breakdowns.  Though originally intended to land first and secure the landing zone with its massive firepower, its rarity now relegates it to the second wave, once other ships have cleared the way.  It then serves as a secure base of operations and supply depot for the invading force.  The Fortress is no longer manufactured, circa 3025, leading to it having a frequency rating of “Unique.”

Notes:

Avenger: Introduced in 2816, the Avenger is a product of post-Star League engineering.  As such, I’m surprised that three separate Houses manufacture it.  I suppose espionage would be responsible for the design getting around, and the Successor States would still have the resources to build new shipyards during the First Succession War. 

This is why I disagree with the First Succession War sourcebook’s explanation for why it lacked a “new technology” section – that the widespread destruction precluded the combatants from designing and fielding new equipment.  The Avenger is an excellent counter-example.  The First War is exactly when the Successor States, which had all been having their R&D teams work overtime in secret to prepare, should have unleashed a flood of experimental new designs and weapon systems, hoping that their superweapons would carry the day against their rivals.  (The cyborg-megafauna “BioMech” is an example of what the Combine R&D department was working on, for example.)

Seatbelts are a must on this ride, as its 30 crew members have to handle it pulling high gee combat maneuvers like a fighter (7/11) without going flying all over the craft’s interior.  A fair amount of page space is given over to explaining how the ship’s layout functionally changes when under thrust, vs. when in a gravity well.

A “Unique” frequency of sighting implies less than “Rare,” which I earlier guesstimated at around 500 (given the FASA numbers provided).  So, perhaps 50 remaining functional copies of the Avenger in the Inner Sphere circa 3025?

Achilles: Unlike the Avenger, which looks like an upsized Thrush, the Achilles doesn’t seem equipped with the necessary aerodyne control surfaces required for operation in atmosphere, relegating it to space-only operations.  Since its mandate is space superiority, that’s not a severe drawback, but it means that enemy ships that drop down into the atmosphere can evade its guns.  It must have had a different small craft aboard at its inception, since the S-7A Bus didn’t debut until 2602.  ST-46 Shuttles (introduced in 2528) would seem likely.  The Bus is multi-functional – helping to resupply the Achilles from cargo ships, facilitating personnel transfer, and enabling boarding actions (albeit only against enemy ships that have already been knocked out of the fighting, unlike the later Battle Taxi that allows boarding of still-hostile ships). 

House Kurita has the most of these, and still manufactures them.  The remainder are spread thinly but evenly among the other Successor States.  If “Unique” approximates 50 (as I’ve previously surmised for the Avenger), then Kurita should have about 38, with 3 each in the other Successor State fleets.

Intruder: The Intruder is ideally suited to make use of the Scout DropShip when on lone-wolf reconnaissance missions.  The flavor text gives it 675 tons of cargo, but the statistics bloc gives it 725 tons.  Presumably, the 50 ton differential is space reserved for supplies, ammunition, etc.  It doesn’t appear to have dedicated vehicle bays, so deployment and loading will be somewhat slower than it would be on, say, a Gazelle. 

I’m trying to determine a rationale for why the Star League Defense Force would decide, fifty years into “the good years” that they needed a ship capable of solo insertion into hostile territory and good for raids.  The Star League didn’t have any notable foes at the time, occasional insurgencies and pirate groups (and the occasional psychotic Coordinator) notwithstanding.  SLDF doctrine wasn’t to conduct raids or lone-wolf intel gathering.  If they wanted intel, they sent a Bug Eye (introduced 2620) or had Star League Intelligence Corps special forces field teams infiltrate said planet (by definition a League member) and surveil the target region covertly.  If the League wanted reconnaissance in force, they’d dispatch a WarShip squadron with a Brigade of support troops.  The League didn’t raid its enemies.  It came, smashed, and stayed – putting up a Castle Brian or two if things looked tetchy with the indigs.

One possibility, therefore, is that the Intruder was originally designed by one of the Great Houses for its own military (which would have lacked Bug-Eyes), and the design was later licensed.  It makes an economical pirate hunter – able to fight its way through the bandits’ fighter screens, land next to their stronghold, and then destroy it with two heavy armor lances and three marine platoons.  The marine platoons could also be used for boarding pirate JumpShips and DropShips, though without any small craft, the Intruder would need to maneuver alongside and have the environment-suited marines spacewalk over to the enemy craft.

Another possibility is that the Star League wanted a ship capable of handling itself in a scrape on deep range exploration missions (numerous sources have indicated the Star League had an equivalent organization to the Explorer Corps, which built the base at Columbus).  Out in the Deep Periphery, there’d be plenty of uncharted colonies, holdouts from the Reunification War, and other unknown threats where some heavy armor and gung-ho marines could have come in handy.

With a frequency rating of “Rare,” I’d guess FASA intended roughly 500 to still be active circa 3025 – the most common type of assault DropShip. 

Fortress: I personally remain unimpressed with the supposedly devastating arsenal on the Fortress.  A besieging force with AC/2 carriers, LRM Carriers, and/or artillery pieces could ignore 95% of the Fortress’ weaponry.  Sure, you have to watch out for their combined arms battalion, but if that group is sitting back and defending the home base, it isn’t out marauding, so you’ve at least managed to pin it down and remove it as a mobile threat. 

Since the defending forces in the Reunification War were heavy users of artillery (at least in the Taurian and Rim Worlds fronts), I can see the Fortress emerging from the SLDF’s “lessons learned” process – with commanders wanting a mobile artillery platform that could land within range of enemy emplacements and be able to shrug off enemy hits while pounding the defenders to rubble.  Once armor started to get thin, the Fortress could take off and pull back for re-armoring while other units maintained the siege.  Mobile Long Toms were too slow, and too likely to be blown apart by a lucky enemy hit in an artillery duel.  The combined arms battalion with the Fortress could prevent the enemy mobile forces from trying to overrun the battery, and could, once the enemy fixed defenses were smashed, spearhead the investment of the enemy fortress. 

Heck, the intent may have been to have a mobile artillery battery – the slots for the armor company could have been intended to be filled by Mobile Long Toms – introduced in 2602 – giving the enemy a 13-gun salute while the ‘Mechs and infantry maintain the perimeter.

As with other “unique” ships, I would guess 50 or less remain circa 3025.  The largest known group of Fortress DropShips is House Steiner’s six-ship Elvidner squadron, which shattered the Second Sword of Light during the Fourth Succession War.  (Note: Though DropShips and JumpShips says it’s not being produced, TRO:3057 claims that “less than two dozen” were made between 2974 and 3027, implying production rate of about 0.43 per year, or less, during that period, with the last construction facility closed due to lack of parts in 3027.  Production resumed in 3030, thanks to NAIS help via the FedCom alliance.)
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1463 on: 15 October 2016, 14:18:32 »
It comes some 30 years early, but the Intruder strikes me as an ideal LAM carrier. Perhaps an early example of the concept later epitomized by the Hamilcar - some sort of space raider/boarding carrier. The bane of JumpShips.
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins

VhenRa

  • Captain
  • *
  • Posts: 2251
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1464 on: 15 October 2016, 23:34:43 »
Production resumed in 3030, thanks to NAIS help via the FedCom alliance.)

I don't know what TRO 3057 says... but 3057r says production resumed (in Lyran space) in 3022 with 20 built in the 6 years prior to the 4th Succession War. I believe you might have read production rate reducing as beginning again.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1465 on: 16 October 2016, 02:30:21 »
Looks like they changed the narrative substantially between 3057 and 3057r.
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

VhenRa

  • Captain
  • *
  • Posts: 2251
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1466 on: 16 October 2016, 09:29:26 »
How so? The text is exactly identical in TRO 3057 (now that I have looked it up).

Quote from: TRO 3057
The years between 2974 and 3027 saw the construction of less than two dozen Fortress Class vessels. In the early part of this century it appeared the Fortress would become extinct, as the last construction facility closed due to a lack of parts. However, the alliance between the Federated Suns and the Lyran Commonwealth allowed Semier Data Tron to resume production of the vessel. The firm secretly constructed twenty Fortresses for Archon Katrina Steiner in the six years before the Outbreak of the Fourth Succession War.

Text is identical between TRO 3057 and TRO 3057r.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1467 on: 16 October 2016, 12:43:25 »
I think the issue I'm having is that I read the first part of that paragraph and then stopped, and there's a disconnect between the first paragraph and the last half.

The First part says "The years between 2974 and 3027 saw the construction of less than 24 Fortress Class vessels.  In the early part of this century, it appeared the Fortress would become extinct, as the last construction facility closed due to a lack of parts."

I didn't read the second part, which implies the construction (with FedSuns help) of 20 vessels between 3023 and 3028.

The question is, therefore, were just 3 Fortresses made by the factory that closed in 302X due to lack of parts between 2794 and 302X, with the other 20 coming from the secret factory on Tharkad using FedSuns parts?  Or were 23-ish made publicly, with an additional 20 being rolled out in secret in the run-up to the Fourth Succession War?
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Mendrugo

  • Freelance Writer
  • Major
  • *
  • Posts: 5907
  • Manei Tetatae
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1468 on: 16 October 2016, 12:44:17 »
Date: May 17, 3025
 
Title: DropShips and JumpShips
 
Author: Clare W. Hess; Art by Steve Venters (cover) and Dana Knutson (ship design and illustration)
 
Type: Sourcebook (FASA)
 
Synopsis:

Leopard CV: The Leopard CV is designed for space superiority operations, and is not intended to enter a planet’s atmosphere.  Capable of carrying six aerospace fighters, it deploys as part of the leading edge of any DropShip fleet, supporting its fighters with its arsenal of weapons.  Its goal is to disrupt defending aerospace formations and keep them busy while troop carriers sweep past and land on the target world.  It lacks a separate transit drive for maneuvering in a gravity well, so its internal decks are only configured so that “up” is towards the nose.  The Leopard CV is manufactured by Houses Marik, Steiner, and Davion (the same as manufacture the ‘Mech carrier variant), and has a frequency rating of “Rare.”

Vengeance: The largest fighter carrier in the Inner Sphere, the Vengeance, introduced in 2782, can carry 40 fighters and three small craft, and is able to launch eight fighters per minute.  Intended to serve as a mobile base of operations for a fighter wing, the Vengeance has separate launch and recovery decks.  With limited firepower and maneuverability, it is typically escorted by two assault DropShips and three transport DropShips, like the Union.  The Vengeance is manufactured by Houses Marik and Kurita, but is also noted as being in use by House Liao, which uses the CCS Omaha Beach as an invasion craft, using 43 small craft capable of carrying a single vehicle or infantry platoon to deliver a combined arms reinforced battalion onto an enemy planet.  Its Frequency rating is “Rare.”

Notes:

Leopard CV: This entry again makes the claim that the ship, introduced in 2581, looks different from the standard Leopard because of advances in armor curvature technology.  As noted previously, the Gazelle, introduced 50 years previously, demonstrated the ability for aerodynes to mount curved armor on hulls. 

The claim that the internal decks are oriented towards the nose makes the layout of the bay doors and the cockpit somewhat non-optimal.  The bay doors are wider than they are high, implying that the fighters are stored and launched at a 90 degree angle off of the vector of thrust.  (In practical terms, the pilots and bay personnel would be getting into their craft and working to launch with the thrust-generated gravity acting on them as though they were trying to stand on the walls of the room.)  If the internal decks were really oriented towards the nose, the bay doors should reflect that by being taller than they are wide.  Likewise, the cockpit seems designed for a pilot to sit in while strapped into an acceleration couch with the G forces pressing them backwards, but that would mean the bridge would have a perpendicular orientation to the rest of the decks on the ship.

It actually makes sense for this ship to have a Star League V84 drive, since it debuted towards the outset of the Reunification War.  It probably joined the Achilles at the forefront of Star League naval offensives into the Taurian and Canopian sectors.  (The Outworlds Alliance fighting didn’t feature much naval combat, and the majority of the Rim Worlds fleet seems to have remained loyal to House Amaris.)  It’s telling that neither of these ships are well suited for atmospheric operations, which gave the Taurians an opening to use conventional aircraft to strike landing zones, while the SLDF fighters remained up in orbit.

Vengeance: The Vengeance is an oddity – beginning production three years after the Star League was dissolved, it was probably commissioned by the SLDF during the civil war with the intention of replacing combat losses among the Titans and Leopard CVs, as well as giving WarShips the ability to carry an overwhelming number of fighters into battle – giving them better odds against the Amaris-controlled SDS drone fleets.  The Vengeance’s capacity more than doubles the Titan’s, making it an ideal accompaniment to a Star League WarShip, which still had plenty of fighters and pilots, but was beginning to run short of ships to carry them.  The question, then, is where the R&D was done, and where the construction was carried out. 

Since Houses Marik and Kurita ended up with the manufacturing capacity, it would appear that the R&D may have taken place outside of SLDF auspices, as part of a covert armament skunkworks R&D program.   With Kurita officially withholding aid to the SLDF because of the hostages held by Amaris on Terra, and with Kenyon Marik going so far as to assemble a fleet to attack an SLDF staging area (though the SLDF launched its invasion of the occupied Hegemony before Kenyon’s fleet got its marching orders), it seems doubtful they’d be willing to do any arms manufacturing for Kerensky’s forces.  Perhaps Houses Marik and Kurita collaborated on the design, with the intent of using it against whoever won the Amaris/Kerensky war, if necessary.  Neither of the worlds manufacturing the Vengeance were in the Hegemony – both were deep interior systems of the League and Combine, respectively.

I would imagine the Vengeance’s shining glory came during the First Succession War, when they accompanied FWL and DC WarShip fleets into battle and unleashed clouds of fighters against their enemies, who would be equipped with Leopard CVs or Titans scavenged from the SLDF, giving the League and the Combine a decisive advantage in the fighters/docking collar ratio.

This leaves House Liao as the only major power that doesn’t manufacture any dedicated fighter carriers.  It’s mentioned as fielding the Omaha Beach, but that’s probably a captured vessel.  The opening chapter of “The Sword and the Dagger” mentions Liao fighters deploying from modified freighters, with extra fuel tanks attached, to enable them to make the days-long system transit.  That appears to be the standard Liao modus operandi, since they lack the specialized carrier DropShips that would allow them to carry their fighters from the jump point to the planet.  This may also be why they converted at least one Scout into a fighter-carrier.  I would imagine that Tengo Aerospace turns out a number of Mules and Mammoths with cargo space given over to fighter bays, though probably without any of the specialized recovery and maintenance equipment found on dedicated carriers.

We’ve never seen stats on the kind of small craft that has a heavy vehicle bay or a full platoon compartment, ostensibly used by House Liao aboard the Omaha Beach.  None of the small craft described in DropShips and JumpShips is capable of those kinds of payloads, and not even the later Battle Taxi can handle carrying a tank.
"We have made of New Avalon a towering funeral pyre and wiped the Davion scourge from the universe.  Tikonov, Chesterton and Andurien are ours once more, and the cheers of the Capellan people nearly drown out the gnashing of our foes' teeth as they throw down their weapons in despair.  Now I am made First Lord of the Star League, and all shall bow down to me and pay homa...oooooo! Shiny thing!" - Maximillian Liao, "My Triumph", audio dictation, 3030.  Unpublished.

Frabby

  • Major
  • *
  • Posts: 4252
Re: Chronological BattleTech Fiction Review - The Succession Wars
« Reply #1469 on: 16 October 2016, 15:15:01 »
The Vengeance is an odd duck indeed. I believe there were no aerospace construction rules in place yet when we got DS & JS and TRO:2750, and getting rules later on required tweaks and changes to the published designs. You can clearly see that the Omaha Beach is a variant designed under a quite different ruleset, if any.

You cannot in good conscience call the Vengeance a carrier, as it is nowhere near capable of sustained operations - it can't really rearm or even refuel its fighter complement. It's a straight pure "fighter dispenser" deployment vehicle, much more so than a Union is a 'Mech deployment vehicle and not a self-contained base.

The "modified freighters" that deployed fighters to Stein's Folly were probably Quetzalcoatls. I never realized before that Liao has no domestic fighter carrier production. That suddenly makes the (otherwise harebrained) Quetzalcoatl a meaningful asset and explains why Liao would even consider crippling their precious JumpShips in this way.

CV variants of the Union and Overlord have been mentioned in canon, but not for any civilian DropShip class. Guess the Mule is too fragile and the Mammoth too expensive and/or useful on top of that. Why not use Behemoths straight away as spaceborne aerospace bases? Same reasons presumably, even if no refit is required.
« Last Edit: 16 October 2016, 15:21:29 by Frabby »
Sarna.net BattleTechWiki Admin
Author of the BattleCorps stories Feather vs. Mountain, Rise and Shine, Proprietary, Trial of Faith & scenario Twins