Menkalinan Blues
For much of the 3rd Succession War, the world of Menkalinan on the Marik/Liao border was one of the few worlds garrisoned by forces from more than one Successor State. Of course, it achieved this “distinction” by being a backwater border world with few resources worth deploying heavy forces to secure, so it was a bit dubious and unremarkable as honors go. There were skirmishes between conventional units over the years, but for the most part an uneasy peace prevailed between the two sides.
In the year 3025, however, both the Free Worlds League and the Capellan Confederation began secretly smuggling lances of Battlemechs and extra supplies to the world, in the hopes of turning the balance to their favor. Given that the League was saddled with S.A.F.E. and the Confederation was saddled with Maximillian Liao, it is not overly surprising that both sides were convinced that they would catch their foes off-guard and finally gain the upper hand. Instead of a swift victory over an unprepared foe, each side was going to face a tough fight!
---------------------------------------------
Last year (how did the year go by so fast?) we ran a campaign featuring Clan Omnimechs and Lyran heavy units clashing for control of the world of Hood IV. After taking a bit of a Battletech break, we are back at it again, this time with some lower tech and lower point values to go with a more combined-arms approach.
This campaign is being run on a rules set we started working on many years ago (i.e. the late FASA days), set aside for a long time, and have recently revisited and refined. It is (mostly) based on the “Supply Point” system from Battleforce2 and the FedCom Civil War books. Given its age, it should come as no surprise that our rules set is heavily “hybridized” between the old BMR/BF2 rules and the current TW/Stratops rules, picking and choosing what we liked of the old and the new. I’m not going to infodump right off the bat, but there is some basic campaign structure to know about before we begin:
- We are using a modified version of the Linked Scenario rules from Strategic Operations. We simplified the orders phase down to just 2 options: Combat (ready for action with penalties to repairs) and Non-Combat (behind the lines, with bonuses to repairs and Fatigue recovery). We are fighting one Battletech-scale and one Battleforce-scale fight each campaign turn. We also strung out the scenario list(s) from the StratOps charts into a single column for each type of battle, rolling a 2d3 with bonuses or penalties depending on how each side is doing.
- Each player starts with a maximum of 40 elements and a fixed BV budget to buy starting forces, with roughly 1/2 of them generated via random rolls vs. the appropriate RAT.
- Repairs, replacements, skill upgrades, and a few other things are done at the end of each campaign turn, with rolls for success determined after all of the Supply Points (representing abstracted logistics) are allocated to each task. The pool starts out reasonably sized and does get incremental ‘resupply’ boosts, but repeated heavy losses could drain it before the end of the campaign.
- Each Battletech scenario is worth 1 point to the winner, and each Battleforce scenario is worth 2 points. If the attacker wins the Base Attack scenario, they get 4 points instead of 2. First one to 9 points claims victory in the campaign . . . though with limited supply and Fatigue rules (from StratOps) in play, one side may feel compelled to surrender or even be unable to field enough forces to fight if they get too beat up or are unable to rest their troops
The Combatants
The 948th Marik Militia - unit symbol is a penguin standing tall in the middle of a colony of other penguins singing “I just gotta be me!” - units in italics are from the RAT tables:
PHX-1 Phoenix Hawk, WSP-1A Wasp, VL-2T Vulcan, PHX-1 Phoenix Hawk
DV-6M Dervish, QKD-5A Quickdraw, WVR-6M Wolverine, OSR-2M Ostroc
BLR-1G Battlemaster, HBK-4P Hunchback, WHM-6R Warhammer, ON1-K Orion
AWS-8Q Awesome, STK-3F Stalker, CN9-A Centurion, WTH-1 Whitworth
Manticore, Scorpion, Hetzer, Manticore
Condor, Harasser, 2x Heavy Hover APCs
Striker, Hunter, 2x Heavy Wheeled APCs
Motorized Rifle Plt, Motorized SRM Plt, 2x Motorized Field Gun (3x AC-5) Plt
Foot Rifle Plt, Foot MG Plt, 2x Foot SRM Plt
3x Foot MG Plt, 1x ‘Heavy (Divisor 2) armor’ Foot SRM Plt
#TheRealMenkalinanMilitia (or ”1st Capellan RMM”) - unit symbol a gauntlet being thrown down - units in italics are from the RAT tables
LCT-1V Locust, LCT-1E Locust, JR7-D Jenner, ASN-21 Assassin
WSP-1L Wasp, CLNT-2-3T Clint, JVN-10F Javelin, PXH-1 Phoenix Hawk
2x GHR-5H Grasshopper(s), VND-1AA Vindicator, CPLT-C1 Catapult
DV-6M Dervish, VND-1R Vindicator, MAD-3R Marauder, ARC-2R Archer
2x Hetzers, Vedette (ML version), Manticore
Sturmfeur, Hunter, 2x LRM Carriers
Peregrine VTOL, Ferret (Cargo) VTOL, 2x Karnov VTOL
4x Maxim
Foot Rifle Plt, 2x Foot MG Plt, Foot SRM Plt
2x Foot Rifle Plt, Foot Laser Plt, Foot SRM Plt
Pre-Battle Thoughts from the GM
I am amused by the force names and logos. :)
With the Battleforce system in use, both players (unsurprisingly) arranged their lances to keep similar movement and range profiles grouped together.
The Marik player did a bit better on his RAT rolls in my mind - better weight results and some nice models like the 4P medium laser “Swayback” Hunchback - and chose to invest more in Mech and infantry firepower, and not so much in vehicles. Only two lances with movement faster than 5 (with one being half APCs) might hurt, but the two medium jumping Mech lances seem well equipped to ‘scout hunt’ should the need arise.
The Liao player got some odd ducks on the RAT table (The 1AA Vindicator and the VTOLs, for example, and that odd Sturmfeur that must have been pilfered from somewhere) and ended up placing a bit more emphasis on speed and on vehicles.