Month: February 2023

Assault on Neo-Normandy Missions (2) – Commando Raids

Assault on Neo-Normandy Missions (2) – Commando Raids

The air war is done, and now it’s on to the Commando Raids in our continued set of linked games at our local LGS, Drawbridge Games in Pittsburgh, PA. As before (https://the-dark-muse.com/2023/01/11/assault-neo-normandy-missions-1-strategic-air-war/), I wanted to provide the rules for what we’re doing in the missions in advance of our actual games. The Command Raids will be two missions, representing airborne forces dropping to capture a key location and to sabotage a gun emplacement. They’re meant to represent the Saint-Mère Eglise and Pegasus Bridge drops during the Normandy invasion in World War II–just with Warhammer 40k factions continuing their battles (Aeldari as the Allies, T’au Empire as the Axis).

Commando Raids and Sentries Rules

These sentries rules were directly adapted from the battlefield rules released along Moon Base Klaisus set for Warhammer 40k 8th edition (https://www.games-workshop.com/resources/PDF/Downloads/40K_Moon_Base_Klaisus_CB.pdf)

For a mission with Sentries, the Defender includes an additional unit beyond the PL of the game they’re playing. This unit should normally have the Troops Battlefield Role, contain up to 10 models, and have a Power Rating of 10 or less. In this scenario, note that the options can include Fast Attack—Drones or Pathfinders are valid choices for sentries as well as Fire Warriors, Breachers, or Kroot when T’au are the defenders.

The “Sentry turns” exist prior to the start of the game, where the Attacker’s Units are moving (and potentially shooting or charging) and the Defender’s sentries are on patrol and moving around the board. The Defender’s other forces are “encamped” and do not move until the alarm is sounded.

Each Sentry model moves and acts as a separate, individual unit throughout the battle. At the start of each of the Defender’s Movement phases, both players roll a dice for each Sentry model, in an order chosen by the Defender. The player who rolled the highest can move the model the distance indicated on their dice in any direction (a Sentry cannot Advance as part of this move). If the rolls are tied, the Sentry does not move.

At the start of the game, all is quiet and the alarm has yet to be sounded, but it is raised if any of the following occur:

  • A model from the Attacker’s army fires a non-silenced ranged weapon. Silenced ranged weapons are weapons that can ignore the “Look Out Sir” rule (e.g. Sniper Rifles). If the Attacker’s army fires any silenced ranged weapons, the alarm is raised if they hit but fail to kill their target with that shooting attack (as the target certainly feels the shots!)—and if targeting units with multiple models, the alarm is raised if any of the models in the targeted unit survive.
  • A model from the Attacking player’s army attacks a Sentry or a non-Sentry unit in the Fight phase but fails to kill them (in the latter case, the entire non-Sentry unit would need to be killed in the single fight phase). Note that the Defender’s models cannot fire Overwatch during the “Sentry Turns” phase of the game.
  • A model from the Attacking player’s army is spotted by a Sentry. An enemy unit is spotted if it is within a certain range of any Sentry at the end of any Movement phase (whether or not that unit is visible to the Sentry). The spotting range depends upon the Power Level of the Attacker’s unit, as detailed below:
Power Level*Spotted Within
5 or less3”
6-106”
11-199”
20 or more12”
*Note that vehicles and anything deemed “loud” (e.g. all Ork units that aren’t Kommandos or Gretchin) double their PL for purposes of this chart.

When the alarm is sounded, the Sentry Turns end and the game begins with turn one. If the alarm is raised during the Attacker’s turn, their turn ends after the action that raised the alarm has been completed. It is now the Defender’s turn one. If the alarm is raised during the Defender’s turn, then the Attacker and Defender roll off, the higher roll being the first turn of the regular game. In either case, the Sentries are now under full control of the Defender. The sentries must move in the movement phase toward regaining coherency, and when they’re in coherency those elements “form up” and remain a unit for the rest of the game. They otherwise act independently (shooting and charging) until they “form up” in a movement phase or other movement on the board. The Defender’s units that were “encamped” now are fully active and participate normally.

Mission One: Capture the Town

The Attackers are conducting a night raid to capture a critically-placed town. Their goal is to disrupt the enemy reserves and keep them from massing at the nearby beaches the following morning where the full invasion will be taking place.

The Defender’s deployment zone should include two notable buildings that form the center of the “town”. These serve as the objectives of the battle. Sentries can be placed anywhere within 18” of the Defender’s board edge, and need not be in the deployment zone (can be closer to the board edges). The Defender deploys their army and sentries entirely before the Attacker deploys. See the deployment zone chart below for the layout for the mission.

At the end of the game (5 normal turns), the Attacker wins if they hold more buildings than the Defender—holding both buildings or holding one while the Defender does not hold the other. If both hold one building, it’s a tie. Any other result is a win for the Defender. “Holding” a building requires that a unit be inside the building’s board footprint, and that no enemy unit be inside that footprint.

Mission Two: Spike the Big Guns

The Attackers are conducting a night raid to disable one of the massive artillery weapons of the Defenders—in this case a titanic battlesuit waiting in a drydock staging area. The goal is to destroy the towering battlesuit so the Defenders cannot use its long-ranged capabilities to bombard their landing forces the following morning of the full invasion.

The Defender’s deployment zone has a single additional model added to the game—a Lord of War Battlesuit such as a Ta’unar or Stormsurge (if adapting to other forces use something similar), which counts as the “Big Gun” objective and should be in the center of the battlefield. Sentries are maintaining a close perimeter to the Big Gun, so they must deploy within 3” of the Defender’s deployment zone. The Defender deploys their army and sentries entirely before the Attacker deploys. See the deployment zone chart below for the layout of the mission.

The Big Gun model is inactive for the battle, and the Defender’s forces should not include an equivalent or larger model. This model is not “active” in the battle, and a piece of terrain should be set up next to it to represent the suit being still connected to staging rigging. The staging rigging means the suit cannot be disabled at range (fueled defensive shielding or otherwise encased safely). Instead, the Attackers must destroy it with the demo charges that they have brought for the purpose. A Ta’unar Big Gun has 30 wounds, while a Stormsurge Big Gun has 22 wounds. Attacking infantry units can begin an action in their shooting phase instead of shooting (unless they have a special rule to shoot and do actions) as long as they did not advance that turn and are in base-contact with the Big Gun to “Plant Explosives”. The action concludes at the end of their turn as long as they do not Charge in the charge phase or are not engaged in the Fight phase. At that point, count the number of infantry models that conducted the Plant Explosives action and record it. Defender’s infantry models on their turn have an action as well, called “Clear Explosives”. Their action has the same restrictions as “Plant Explosives”. Again, at the end of their turn count the number of models who completed the action. At the start of each Attacker’s Command Phases (and once more at the very end of the game) the Attacker rolls a number of d6’s equal to the count of Attacking models who successfully completed the Plant Explosives action, counting all dice of 3+. The Defender rolls a number of d6’s equal to the count of Defenders who successfully completed the Clear Explosives Action, counting all dice of 5+. Subtract the Defender’s successes from the Attacker’s successes, and then apply the remaining number of Attacker successes as wounds to the Big Gun. The mission ends after 5 turns. If the Big Gun is destroyed at or before that timing, the Attacker wins. Any other result is a Defender victory.

Campaign Outcomes

Capture the Town: This affects the response time for the Defenders’ reinforcements. If the Attackers win, then any Defender reinforcements suffer penalty on their reserve rolls for the invasion missions (cumulative with the penalty for the Strategic Bombing mission from the Aeronautica game if that was an Attacker win).  

Spike the Big Guns: This affects the quality of the barrage against the Attackers’ large landing ships, leading to slower deployment of the flotilla of landing craft. If the Defenders win this mission, then the Deployment zone for the Attackers on sea landing missions is only 12” rather than 18”.

Painting Progress

More progress on the Drukhari, this time finishing up five Incubi. I’ve been needing to get squads of these together for my force, as they’re quite effective in the game. I’d been fiddling with the paint scheme, but finally found what I wanted. I think they turned out quite well. Setting them amidst the rest of the force makes them certainly stand out, but they still keep the same core colors (just in a different pattern), so I think they click nicely.

I also added yet another unit of five Wracks to my force. That makes a total of 25 Wracks–two squads of ten and one of five, which should make for a really good foundation of warriors for my force.

Next up I’m adding a whole set of models to my Wych Cult for the Commando Drop Missions, so stay tuned for those. I’m also painting up a set of ship-board battle terrain that I’ll leave at my local gaming store (it’s the basic set from GW for Into the Darkness kill team boarding actions, with a bit of an Orky mod to it). I’ve also got a plot for an Aeldari Outcasts/Corsairs/Exodite ship and/or base that is in my long-term plans for my own gaming table which I’ll do up at some point.

Army Painted Totals

40k Aeldari (Primarily Drukhari but also Asuryani, Ynnari, and Harlequins): 129 PL

Aeronautica Imperialis Aeldari: 373 points

Nightwing Ground Attack

Nightwing Ground Attack

This is the second game of our “Invasion of Planet No’ohrm Ha’an D” series of battles, the second of the Aeronautica Imperialis missions that we’re doing to set the stage. The prior fluff is here: https://the-dark-muse.com/2023/01/02/the-invasion-of-planet-noohrm-haan-d/ and the recap of the first mission is here: https://the-dark-muse.com/2023/01/24/air-caste-in-retreat/. Plus the rules for running the Aeornautica Imperialis portion of the battles are here: https://the-dark-muse.com/2023/01/11/assault-neo-normandy-missions-1-strategic-air-war/. Enjoy!

Ezruin leaned in on the stick of the Nightwing fighter jet as it slipped near straight down to the surface of the planet below. He wanted to test the craft out a bit more in atmospheric flight, as he was not as familiar with the craft as some others. Archon Yraleath had connections somewhere on the Saim -Hann Craftworld, and had either bought, bartered, or pilfered thirteen Asuryani craft to form his own squadron of attack planes. Yraleath had dealt them out to his Dracons and Trueborn as gifts. And like all gifts from the Archon, these were double-bladed. Certainly their Craftworld cousins’ technology was excellent, and made for a sleek sky-borne force, and a handsome prize for each of Yraleath’s lieutenants. But at the same time none of them were expert pilots themselves, and Ezruin noted that the pair of Voidraven Bombers that the Archon used to supplement his raiding parties at times were nowhere to be seen amidst the attack. Was this yet another chance to potentially cull the various subordinates within the Kabal? If so, then Yraleath was foolish–as the more skilled would be more likely to survive. But then again, it may be a matter of setting them up in comparison to the well-trained Craftworlders whose blue jets and bombers had joined in the attack. A chance for Yraleath to berate the lack of skill of a Dracon by speaking well of a kin’s craft that beat them to the punch? Ezruin pulled back on the stick at the near last moment, his plane leveling out and barreling along the smoky ground. The distraction of these things would cost him. Focus on the mission.

Ezruin’s Nightwing had been fitted with underslung missile launchers, and served as a sort of torpedo bomber in design. Ride in low over the ground and loose missiles into the varied industrial and command-and-control targets that they had identified. Yraleath had some sort of network of scouts that had provided him information on critical targets of T’au logistics in advance. Ezruin hadn’t seen any Mandrakes slinking around the ship nor in the court of late, so he wondered if this was more collaboration with their Craftworld kin. Before the spread of the Ynnari into the streets and courts of Commorragh connections to the kin had been infrequent and often violent. Yraleath was no Corsair, but a proper Drukhari Archon, so these connections were unseemly to a Trueborn like Ezruin.

The Aeldari planes drew together into a wide formation, screaming toward the set of targets on the horizon. Their instructions were clear: destroy the critical infrastructure, down T’au planes where possible but if the foe hangs at range use defensive maneuvering and elevation changes to keep the defensive force chasing shadows. A trio of three Phoenix bombers raced ahead followed by a swarming cluster of the Craftworlders. Ezruin immediately noticed the difference–the Drukhari were all skilled, certainly. But they were not dedicated to the craft of flight in the way of their kin, not by a long shot. While his Kabal’s red planes flew in straight, swooping arcs, the blue planes of the Craftworld tore into all manner of complicated flight pathing, weaving in and out of each others’ way like some complicated ballet. Ezruin was impressed, will be more impressed if they could weave the death of their foes equally well.

In an instant, the battle was engaged in full, with planes from both sides criss-crossing each other amidst the complete dogfight. Ezruin kept his plane low, seeing the T’au anti-aircraft weapons spooling lines of flak fire thru the smoke. T’au fightercraft wove through the Aeldari forces, dropping plane after plane once they got closer. The thicket of fire was intense, but Ezruin finally loosed his two loads of missiles onto a T’au supply depot. The blossoming explosions caught some manner of ammunition depot inside, and the thing went off like a fireball–causing the hazy smoke of the sky to flash orange and nearly blind Ezruin.

Within just minutes the signal was relayed that all targets were hit and confirmed, and that flyers should return to their bays on the waiting Void Stalker starships that had puled back to low orbit after discharging them. Ezruin pulled the Nightwing sharply along a river canyon, low enough that the treeline obscured his progress. This was all part of the invasion plan, but the good part would be next. Fightercraft battles were fine, but the exhilaration of combat in person is where he would truly find some release. He could feel the dark whispers at the back of his mind, the pull on his soul. Soon enough, T’au blood would quiet them… at least for a stretch. The T’au at the actual beachhead should be suitably isolated thanks to this attack–their reserves delayed. While the Craftworlders wanted to get the world back as a whole, Ezruin knew that Archon Yraleath was not the sort to stick around for a protracted campaign. What he wanted and why remained to be seen.

Painting Progress

So much painting, so little time. I added three new Nightwings to my Aeronautica force for the game. You can’t see it really clearly in the pics below, but they have missile launchers so they’re suited for the ground attack role (which is why I went sweptwing extended, and a “torpedo run” angle pointing more downward than my other planes.

This was the last Aeronautica event (as our current plans stand, at least), so I also put some energy into painting regular Drukhari forces for the next stages of our Neo-Normandy invasion (as well as for some boarding action fun coming up at our outstanding local game store, Drawbridge Games).

That meant adding even more Drukhari Wracks to my forces. Tried to batch paint them in greater numbers, but working on groups of five ultimately became what I could tolerate. Did five (above) with an Acothyst bearing a Mindphase Gauntlet and a Stinger Pistol plus one model with a Liquifier Gun. Then another five to round them out to ten, with another Liquifier Gun. Again, I remain pleased with how these models look when they’re finished. Having now finished up 20 total of them they’re getting to be a sizeable addition to the force.

I also wanted to finally add some Incubi to my army. They’re such cool models, and great in the game. They took some thinking on how I would paint them, so I’m sharing the test model I did up below. I wanted to ensure they were mostly in black armor, and that there was enough red to tie them to the others. I saw some professionally painted models that did white in part that I really liked, so I gave it a go myself.

Overall I’m pretty pleased, and the full squad of five is next up in my painting queue. This is good as a start, because I’m also likely to be dabbling in a bit of Craftworlds Aeldari as I go forward, so working out the balance of aspect shrines with my own army overall colors will be a long term goal. Incubi are technically aspect warriors themselves, which is cool. So more ahead!

Army Painted Totals

40k Aeldari (Primarily Drukhari but also Asuryani, Ynnari, and Harlequins): 122 PL

Aeronautica Imperialis Aeldari: 373 points