ISP

ISP

Wednesday, October 18, 2017

State of the Sphere: Inner Sphere in Flames

Note - Whilst this is an SotS post, it isn't one of my normal "this is where we are/recap of the previous year" like I normally throw up at the beginning of a new year. I want this post to serve as a sounding board of ideas for an Inner Sphere in Flames/5th Succession War/Wars of Reaving grand campaign, that we've been meaning to do for like a decade. And I'll be picking on a couple factions/players whilst doing so, NOT because I strongly dislike those factions/players, but because they're the people I've had the most conversations with and the factions that we've talked the most about.

Format
This is where I've struggled the most. How do we run a massive multiplayer offline strategic wargame involving so many factions and players? We have all of the current line of core rulebooks, from the mano y mano A Time of War RPG all the way up to Interstellar Operations and the Campaign Operations book. ISO and CO have great ideas for abstract systems to represent forces in play, but whilst that is great for covering huge swaths of territorial conflict, that's just AccounTech, not BattleTech. But that's what being a Khan or House Lord really is - accounting, crunching numbers on a spreadsheet, weighing losses against the investment, etc. Tracking the minutiae of factory production and knowing how much you need in taxes to pay for a new company of FNR-5 Fafnirs is super important! If, you know, you're into that kind of thing.

Most of my players are not. Now, in my "professional" life, I'm constantly working spreadsheets and tracking logistics. That's old hat for me, and if I have to do it in my gaming, I'm not terribly sad about it. But my players are here to play, to conquer planets, to crush all opposition. Alpha Strike is a nice step in the right direction for a middle ground between the abstract ISO system and standard BattleTech play, since it's not feasible to play campaigns spanning thousands of planets one lance/3 hours of gaming at a time. The older MechForce idea is pretty sound too, wherein players tally up victories for their faction played in a certain period of time, and then translate them into X planets taken by that faction, but it maybe oversimplifies what we want to do.

GameMastering
In addition to the format of how battles are fought, there are a myriad of little additional things that can balance a war between six-planet Word of Blake and 2000-planet Federated Suns. Well, those 52 Divisions, Hidden Worlds, and WarShip fleet really already do that, but I mean more along the lines of intangibles, like anti-HPG electronic warfare, ROM operations, the classic ComStar "let's just kill all of their scientists" schtick, etc. Every major and minor power has some kind of intelligence apparatus for screwing with their friends and foes. And, in addition to that, each power has internal divisions. As opposed to Divisions, like military formations.

The Federated Suns, to continue with our examples here, isn't a monolithic organization. Sure, Victor "won" the Civil War and all is love, peace, & chicken grease on New Avalon with Yvonne in charge, right? Riiiight. There's also a bridge on Tharkad I'd like to sell you... Fact is, reading stuff like "En Passant" or pretty much any Hasek-heavy book, reveals that the noble families that produce the March Lords have their own schemes brewing. I'll get into this a little bit more below, and I'll use some Jihad examples, but suffices to say that the FS isn't alone in this. Free Worlds League? Divisive as hell. Draconis Combine? Do the "Black Dragons" ring any bells? Lyran Alliance? Well, Skye, Duke of Tamar, Democracy NOW!, I could go on all day with Lyran divisions.

With all of this, any massive campaign almost begs for a neutral, "has zero love for any faction" GameMaster to handle internal strife, external operations, and monthly/quarterly/yearly "time bombs" that hit factions. Except, well, that person a) has to have an encyclopedic BattleTech knowledge without any attachment and b) has to have the time to set everything up.

Clearly, I have the knowledge, but I am, unfortunately, biased as heck. I would love to use a lot of the canon happenings from '67 - '85 in the campaign, pursuant to what players are actually doing in between the turns/where their movements differ from canon, and hit all factions fairly hard, but at the same time, I want to play my Wolf Galaxies. Having the Word of Blake player, as one of the core kickers of the 5th SW be the GM would work great, but would require a lot more study and time investment on their part, and would take a bit of their enjoyment of BattleTech away.

The compromise there, and one Sean and I have talked about at length, is having a GM group of three or four people that can work on "storyline progression" as well as to coordinate, and approve or veto in-universe happenings.

Ie, places where a sourcebook is fuzzy or an operation needs to be carried out in secret - my Draconis Combine is going to launch a DEST operation against Jesse's Ghost Bears before a planned assault by my allied Nova Cats. Maybe we're going to sabotage a factory or assassinate a unit commander to cause a disruption to aid the assault. So, everyone in the committee is aware of what is going to happen, except for Jesse, and any rolls associated with this will be done in front of the committee so if it fails but the plot isn't uncovered, Jesse is none the wiser other than -something- happened. That works great for all the little in-fighting and back biting and internal strife. Continuing that, my Draconis Combine may or may not suffer a Black Dragon uprising on Dieron. So, without me around, one of the committee members rolls to see what happens. Of course, this requires that we build some catch-all random occurrence tables, but that is totally do-able. And every committee member would need a solid knowledge base to start from, requiring a little bit of study.

Metagaming
Is impossible to not do. One of the benefits to a vibrant universe is that so much of the backstory is filled in for you and you're not spinning much out of whole cloth to play. However, the downside to that, is if you're playing in a previous time to the most current (3068 vs 3150), you have "future knowledge" of many things, such as me knowing where all of the Word of Blake Hidden Worlds are, that is tempting to use in-game.

To go back to the Federated Suns - one of Sean's first orders of business is to create an "Outback March" and funnel resources that direction to bring the Suns' least cared for worlds up to snuff. This will help prevent the breakaway of Filtvelt and Malgrotta, which happens during the Jihad. So that is metagaming. But, it's also super logical - why would you not create the March and work towards making sure your people can at least read? Also, there's the mystery of Panpour (consensus is that they are either trying to rebuild a Texas-class WarShip, or build a new one from scratch, TPTB killed the plot thread before it went anywhere) and the whole issue with the black boxes, that have basically been written out of universe, or strongly de-emphasized over the years. Black boxes, though, only really aid military commands since they can't transmit much data in one shot, and don't lend too strong of an advantage to the FS (or the DC and LA, who also have some). Neither does the creation of a new March, really, but that one comes with some consequences - in "En Passant," noted above, the Sandoval family is not the strongest supporters of Victor, and by extension, the seat of government on New Avalon, even if Tancred is married to Yvonne. And the Haseks are the Haseks. So, as he and I have discussed, making a new March is a great idea, but at the same time, it also puts an upstart in the March Lord position alongside families that have supported the FS for centuries in the Sandovals and Haseks, inevitably leading to intrigue. And that's awesome. Because, at it's core, BattleTech is all about hitting the table top with your 'Mechs and doing a frighten, but the BattleTech UNIVERSE is a living, breathing, dynamic thing, populated by so much gray, you'd think colorblindness is a rampant trait. Any campaign that isn't just AccounTech needs to take that into consideration. We are all the "good guys" from our point of view, even the Word of Blake or the Clans.

Speaking of the Clans, there's another metagaming situation afoot. Operation: Ice Storm is the invasion of the Clan Jade Falcon and Clan Wolf occupation zones by the Ice Hellions and the Hells Horses respectively. Except, that'll be changing to the Cloud Cobras and the Blood Spirits. The former because they're tired of being in the Star Adder's shadow and the latter because it's their only long-term hope for survival. That's less metagaming (knowing the outcome of the Wars of Reaving) and more because I have an Iota Galaxy Blood Spirit cluster that I'd always planned on bringing to the Inner Sphere. The bigger metagaming, though, is that for it to logically work, a couple of things need to be moved up on the time table, and I'm loathe to "rewrite" history. But it only takes a tweak or two and suddenly, you can have a new invasion kick off as the Wars of Reaving hit full swing. Of course, me, as a Wolf player, knowing what is coming, could quickly send Galaxies worth of troops to the Periphery side of the Occupation Zone to stop that from even happening, but I'm actively looking forward to a mini-WoR campaign for the Spirits and Cobras to establish a foothold, with my weak-ass Omegas back there.

3068?
Given that 1 April '68 is about five months after the Whitting Conference where the Star League is desolved, and about 10 months after Field Manual: Updates, it might seem a weird starting point. However, one of the biggest hurdles to a 5th Succession War is, well, a lack of a war. So, we start in June '67. Star League meeting comes up, everyone stays in and votes for a new First Lord and then... PeaceTech? That may be the only outcome worse than AccounTech. Having the Word occupying New Avalon (whether they stay or not...), Tharkad blockaded, the Free Worlds League and Lyran Alliance going at it, the Capellans and Feddies going at it, Luthien dealing with a three-way battle, the Clans dealing with the Homeworld stuff, it all forces players to actually play.

Players can forge their alliances, break their vows, set up coordinated strikes, or lone wolf it all they want still. Using a base chart to show "alignment," ie "we are hostile to A, neutral-hostile to B, allied to C, and neutral to D" gives a starting point. Where everyone goes beyond that is up to them. Something I would like to see (not making this official, just throwing it out there) is that Arthur Steiner-Davion, the not-dead S-D who is now known as the Master's Protege (but not, thank the Gods, Devlin Stone, Ben and Herb confirmed), be returned to the FedSuns by the Word of Blake, after they pull their forces off of New Avalon, and in exchange, he brokers a temporary cease fire with the FedSuns wherein the worlds from Acamar/Genoa inward (worlds the Word takes eventually anyway), be given to the expansion of the Blakist Protectorate, freeing FedSuns troops to push against the CapCon, or defend themselves better against a renewed Drac invasion. I'd also suggest the death of several current leaders (Teddy Kurita, Yvonne and Peter S-D, that guy from Rasalhague) during the period after the Conference, to replace them with "more suitable" candidates (Hohiro Kurita, Jackson Davion, Adam Steiner, so on) as a further universe shake up. THAT IS ALSO NOT OFFICIAL DON'T BE UPSET YVONNE FANS.

Plus, planetary campaigns - I'm still down to run a Total Chaos style fight over Tikonov between the Feds and Caps, to give one or the other ownership as we go into the April 3068 start, akin to the Total Chaos campaign I ran for the Word of Blake to conquer Outreach (which went way better for the Word than it did in canon), giving them an extra manufacturing planet and strengthening their position in the Chaos March.

Factions
Something I've said forever, but will reiterate, is that I want people to play the factions they want to play, so long as we cover all our main bases. There's no reason we can't have multiple people rocking Lyran or Feddie or Drac, so long as we don't have half the universe with no players. And people are welcome to play more than one faction as long as they aren't bordering one another, or that they are willing to pick one or the other (if playing two) if a new player would like to head one up. THAT ONLY RELATES TO A MASSIVE CAMPAIGN THOUGH. To throw that out there more - pick up games, we can all play different units of the same faction, that's fine. Just based on what we have for assembled forces right now, here is where we're sitting with players and units (* = hard dead set on using, either because it's one of my mains, or because the force belongs to that player);

IS
Capellan Confederation - Three Kingdoms Lancers (Jesse)
ComStar - None (None)
Draconis Combine - Otomo, 1st Genyosha (Fen)
Federated Suns - 1st Davion Rangers* (Sean)
Free Rasalhague Republic - None (None)
Free Worlds League - 19th Marik Militia (Tiffy)
Lyran Alliance - 4th Skye Rangers* (Mitch)
Mercenary - 26th Royal Tyran (Jer), Kuroi Kaze* (Fen), Khaos Chevaliers (None), Song's Sentinels (None)
Word of Blake - 53rd Shadow Division* (Fen), 54th Shadow Division (Rachel)

Clans
Blood Spirit - Iota/Zeta Galaxy (None)
Cloud Cobra -  Pharaoh Keshik (None)
Diamond Shark - None (None)
Ghost Bear - 1st Bear Regulars, Tau Galaxy (Jesse)
Jade Falcon - Generic Camo, Turkina Keshik (Sean)
Nova Cat - Nekoryu Cluster (None)
Wolf - Golden Keshik*, Alpha Galaxy*, Beta Galaxy, Delta Galaxy, Omega Galaxy* (*Fen)

Periphery
Marian Hegemony - I Legio Martia Victrix (None)

WIP
Clan Diamond Beta Galaxy
Free Worlds League 1st Covenant Guard


Now, I don't expect to fill every slot, and we have players that haven't really decided where they want to go yet, but if we're all running one or two (I would give up Draconis Combine and run Marian Hegemony/Clan Wolf, for instance, using my Kuroi Kaze as a full on merc force where other players need me to be, as example), we can cover a lot of interstellar ground. Plus, I start a new unit at least once a year, if I'm not expanding current ones (I only have a 5-'Mech star for the Diamond Sharks right now), giving us even more options as we go. On the Draconis Combine front - if two people wanted to play Drac, one could go 1st Genyosha and one can go Otomo, and then use the 8th Arkab Legion or the Nova Cats Nekoryu Cluster (both are works in progress) to round out their forces as needed, or as a supplement or whatever, depending on the system we use.

Non-Canon Forces
And that is really the best part of the above - all of our mercenary forces are non-canon, giving them supreme flexibility. Sean's FedSuns unit is (per our conversations) the core of a new brigade. The Three Kingdoms Lancers don't exist in the canon CapCon. So, we can use FM:U to nail down where canon regiments are located, but our custom stuff we can place anywhere to really drive home some drama. Since I mentioned Tikonov, the Three Kingdoms Lancers could be there to aid in the Warrior House defense, where Sean's FSU is in the vanguard of the Suns' campaign to retake the world. The 19th Marik Militia can choose to have close ties with the 53rd Shadow Division, where the 26 RTM and Jer can decide to either back Tiffy's faction, or side with Mitch against her, or even pledge service to the Draconis Combine and run that power.

What that means in play is that for every non-canon unit, a world of deployment will need to be picked after a faction is decided on (if applicable) and this can plug some serious canon holes in the old defenses.




BOOM. Campaign map added. NOW, an actual 3067 map will also need to be used to track which worlds are specifically in each region BUT here's how this will break down however we do the things;

Target power has less than 10 regions = 4 victories to secure
Target power has 11-15 regions = 3 victories to secure
Target power has 16-25 regions = 2 victories to secure
Target power has 26+ regions = 1 victory to secure.

This means the powers that divide their sections the most also have fewer forces in each section versus other powers. IE, there are fewer total units in one of the Capellan Confederation's 30 subdivisions than there are in one of Clan Wolf's 5.  

Tuesday, October 10, 2017

Building a Unit - Clan Goliath Scorpion

Much like with the BU: 53rd SD, I was sitting at lunch and reading some BattleTech forums regarding the Imperio del Escorpion, or the Goliath Scorpions post-War of Reavings when they said "fuck all" and conquered the Nueva Castile worlds and formed a "new" interstellar power, ala the Rasalhague Dominion and Raven Alliance. Unlike those two, however, the Imperio is a lot like "old school Mad Max" BattleTech - with a lower technology level than even the Outworld's Alliance and a Clan battered by the WoR, the Imperio actually has a decent amount of flavor... And, you know, with there being a good chance the Ummayyid invaders of Nueva Castile probably being a portion of the surviving Wolverines (just saying... Blake Documents hints at it, yo), you can kind of squint and see a microcosm of the Inner Sphere or Clan Homeworlds in this one new faction.

Which, of course, meant I started looking at a "paper Cluster" whilst sitting here. First, I started with looking up the Goliath Scorpion Touman, and their paint schemes, and I really like Beta Galaxy, since I don't really have much tan/beige going on right now, and it looks like a fairly easy scheme to do. From there, I looked at what Clusters exist from Operation: Revival onto FM: 3085, because you know my units have to cover a wide range of time periods. I decided on the 3rd Scorpion Cuirassiers. Thanks to Sarna, I know that a Cuirassier Cluster for the Scorps is made up of a Command Trinary, two Assault Trinaries, and two Battle Trinaries. That is: Command - a Trinary with two 'Mech Stars, and a composite Star of two 'Mechs, two Elemental points, and an Aerospace point; Assault -  a Trinary with two Heavy/Assault 'Mech Stars and an Elemental Star; and Battle - a Trinary with one Light to Heavy 'Mech Star, one Elemental Star, and one Aerospace Star.

Because, as expressed previously, we don't generally use Aerospace, I modified the composite Star in the Command Trinary to be a point of ProtoMechs, then replaced the Aerospace Star in the first Battle Trinary with a ProtoMech Star, and the Aerospace Star in the second Battle Trinary with a second Light/Medium 'Mech Star, so it wouldn't just feel like another Assault Trinary.

When selecting 'Mechs for this, I went with the official Master Unit List for the Goliath Scorpions and Ice Hellions (since the Scorps absorb what's left of them after Operation: Ice Storm is an epic fail) but for starters, I went to the Iron Wind Metals website, looked up the "Imperio Escorpion Star Packs" and used them for my first Assault and Battle Stars. For my Command Trinary, I began with Connor Rood's Kit Fox (using W config, not sure what Rood actually piloted) and built around that. Then, I took one Star from an Assault and Battle Trinary to do Star League-issue 'Mechs, representing that this force is fielding what it can, not necessarily the top of the line stuff, but also so I would basically have an Operation: Klondike Binary if I were to need one. Since I won't actually be purchasing anything prior to 2018, I might still tweak it, but for the moment, it looks good to me. I might still, for instance, swap out a Star of Elementals for a Star of Salamanders or Undines. (?) indicates I haven't built in a "default configuration" for that 'Mech yet.

2025 Update - When I said, originally, that I didn't have much in the way of tan/beige going on, that was prior to painting a portion of my Northwind Highlanders in a chocolate chip cookie desert pattern, and prior to painting Alpha Galaxy of Clan Blood Spirit (plus Iota Galaxy uses a tan-ish base) so I decided, instead, to go a little darker and make this a CGS Chi Galaxy/Scorpion Empire Seeker Galaxy force, probably First Scorpion Seekers. And I'm doing it all in plastic since the original was pre-CGL revitalization. Most of what I have below is already available, ProtoMechs are coming out soon, and I might also do some Word of Blake stuff per the MUL. We'll see. That means I'll need to do some updates on this overall though.

3rd Scorpion Cuirassiers
(First Seeker Cluster)


Command Trinary
Command Star
Uller/Kit Fox F - saKhan Connor Rood
Vulture/Mad Dog Prime
Vulture/Mad Dog Prime
Cauldron-born/Ebon Jaguar B
Cauldron-born/Ebon Jaguar B

Striker Star
Hellion C
Hellion C
Viper/Dragonfly E
Viper/Dragonfly E
Fenris/Ice Ferret E

Composite Star
Daishi/Dire Wolf C
Daishi/Dire Wolf C
Elemental Point
Elemental Point
Sprite ProtoMech x 5



1st Assault Trinary

Command Star
Gladiator/Executioner (?)
Masakari/Warhawk (?)
Blood Asp E
Daishi/Dire Wolf (?)
Kingfisher (?)

Support Star
Mad Cat/Timberwolf (?)
Hellfire
Night Gyr (?)
Galahad/Glass Spider
Naga

Elemental Star

Elemental Point
Elemental Point
Elemental Point
Elemental Point
Elemental Point

2nd Assault Trinary
Command Star
Loki/Hellbringer Prime/B
Galahad/Glass Spider
Rifleman IIC 3
Warhammer IIC 4
Behemoth/Stone Rhino 2

Support Star
KGC-000b King Crab
AS7-D-H2 Atlas II
STK-3Fb Stalker (Use Stalker II mini)
WHM-7A Warhammer
ARC-2Rb Archer

Elemental Star

Elemental Point
Elemental Point
Elemental Point
Elemental Point
Elemental Point

1st Battle Trinary
Command Star
Uller/Kit Fox (?)
Dasher/Fire Moth (?)
Dasher/Fire Moth (?)
Hankyu/Arctic Cheetah (?)
Hankyu/Arctic Cheetah (?)

Elemental Star
Elemental Point
Elemental Point
Elemental Point
Elemental Point
Elemental Point

ProtoMech Star

Roc ProtoMech x5
Satyr ProtoMech x 5
Triton ProtoMech x 5
Orc ProtoMech x5
Minotaur ProtoMech x5

2nd Battle Trinary
Command Star
Fenris/Ice Ferret (?)
Hellion (?)
Ryoken/Storm Crow (?)
Phantom (?)
Icestorm 2

Support Star
GRF-2N Griffin
CRB-27b Crab
Firefly C
SL-1G Sling
SL-1G Sling

Elemental Star

Elemental Point
Elemental Point
Elemental Point
Elemental Point
Elemental Point

Thursday, October 5, 2017

The Dragon Roars - Unit Spotlight: Draconis Combine

While I might play mercenary or Clan Wolf more than anything else these days, my heart and soul are pledged to the Dragon first and foremost. Way back when I started playing BattleTech, I was Draconis Combine. 4th Arkab Legion, in fact. Not even because I'm weeb garbage (that actually came later), since the 4th AL is an Arabic-flavored unit. I loved the Azami worlds and their North African flair, that they were never conquered but chose to work hand in hand with the heavily Japanese House Kurita. And, later on, I incorporated my time with the AL into the founding history of the Kuroi Kaze. My original "unseen/reseen/might never be seen" Arkab Wolverine is still one of my favorite single pieces, which actually led to me building (on paper so far) an 8th Arkab Legion, inspired by the Maganac Corps in Gundam Wing.

At any rate, I went with "The Dragon Roars" for one solid reason - the scenario book of the same name/the Twilight of the Clans pack. I once had a goal of going through TDR and building both a really solid Draconis Combine unit 'Mech for 'Mech from it, as well as a Davion Heavy Guards. Thanks, MechCommander Gold, for making me want to do it. After rereading the entirety of the Twilight of the Clans novels, I knew I had to do -at least- Hohiro Kurita's Genyosha force, the one that went toe to toe with the Blood Spirits (who I'm obviously a fan of, and will eventually be making an Alpha Galaxy/Khan Schmitt's Star to fight the Genyosha). But, being me, I can't just do the one force, I had to go with a whole company. Then, I was looking at 'Mechs that really needed swords, like the Wolverine and Hatamoto-Chi. Kit bashing, ahoy!

Interestingly enough, the Genyosha was my second full Drac force. I actually built a company of Otomo prior to that for a 5th SW/Jihad Luthien campaign idea. Like I do, I wanted to go with a mix of older staples and newer/future designs to keep things interesting and relevant as our timeline progresses. Plus, with hostile Ghost Bears on one side, hostile FedSuns on another, and a burgeoning Raven Alliance out the back door, the Dragon will need all of the busosenshi it can get. Which also means a Nova Cat force is inevitable.

Genyosha is that weeb trash I mentioned, aka "anime waifu division." Otomo is "heroes of the sengoku division."


1st Genyosha

Location: Luthien
Commander: Gunji-no-Kanrei Hohiro Kurita
Aide: Tai-sa Shih Chou

Company
Magical Girls Lance
Daishi/Dire Wolf Hohiro - GnK Hohiro Kurita
AKU-1XJ Akuma - Busosenshi Homura Akemi
SD1-OR Sunder - Bushosensi Sayaka Miki
HTM-28T Hatamoto Chi Shin - Busosenshi Madoka Kaname

Alpha Waifu Lance
AV1-OR Avatar - Chu-i Mari Makinami Illustrious
NDA-1K No Dachi - Busosenshi Asuka Shikinami Langley
NDA-1K No Dachi - Busosenshi Rei Ayanami
DGR-4F Dragon Fire - Busosenshi Kaworu Nagisa

Bravo Waifu Lance
BLK-NT-3A Black Knight - Chu-i Erza Scarlett
WVR-9K Wolverine - Busosenshi Saeko Busujima
CMA-2K Chimera - Busosenshi Moka Akashiya
DOL-1A1 Dola - Busosenshi Touka Kirishima

Otomo

Location: Luthien
Commander: Tai-sa Griffon Meshune
Aide: Tai-i Ginchiyo Tachibana
1st Company
Command Lance
HTM-30S Hatamoto-Suna - Tai-sa Griffon Meshune
GUN-2ERD Gunslinger - Busosenshi Ieyasu Tokugawa
LGB-12C Longbow - Busosenshi Nobunaga Oda
VTR-9K2 Victor - Busosenshi Hideyoshi Toyotomi

Ni Lance
SJA-7D Shugenja - Chu-i Kenshin Uesugi
WHM-8K Warhammer- Busosenshi Yoshihiro Shimazu
NDA-3X No Dachi - Busosensi Miyamoto Musashi
TDR-10SE Thunderbolt - Busosenshi Magoichi Saika


San Lance
BHKU-OF Black Hawk KU - Chu-i Sakon Shima
KIM-4K Komodo Bushi - Busosenshi Mitsuhide Akechi
WGT-1LAW Wight - Busosensi Koshosho
RK-4K Rokurobi - Busosenshi Kojiro Sasaki


Second Company
Shi Lance
Cougar Prime - Tai-i Ginchiyo Tachibana
Ocelot - Busosenshi Kanetsugu Naoe
VLN-3T Valiant - Busosenshi Toyohisa Shimazu
NX-80C Nyx - Busosenshi Kotaro Fuma


Infantry Detachment
Void Battle Armor Squad
Void Battle Armor Squad
Void Battle Armor Squad
Void Battle Armor Squad

Tank Lance One
Tokugawa Heavy Tank
Tokugawa Heavy Tank
Regulator Hover Tank
Regulator Hover Tank

Tank Lance Two
SRM Carrier
SRM Carrier
LRM Carrier
LRM Carrier