MercNet After Action Report.

[Watchman]

MercNews Report 5
Watchman Reporting
MercNet HQ, Kaitos (2)

I bid you greetings;

We have recently returned to a system between 118 Castor and 160 Fornax, about 15 L.Y. out from 118 Castor.  We have a Sky High Observer Drone (SHOD) doing a repeat survey of the fourth plant.  We are in an area of small mountain ridge lines, broken ground and an abandoned base of some sort.  This area must have had some high usage considering the size of that bridge.  We have had reports of the Black Cutlass activity; they most certainly stand out in a crowd... 

Well we are right on target, based upon the information we received on their occupying a base.  We find them moving into the abandoned base. It has been awhile since we last encountered them.  It appears to be an oversized, combined arms, company of sixteen CAVs, Armor, and Air assets.  No indications of where the rest of them may be deployed.   It appears their force consists of a Dictator, Duelist, two Wolf tanks, two Tsuiseki ground attack aircraft, a Ghast, two Starhawk V, Chieftain and Despot tanks, two Rhinos, Gladiator, and two Wights.

In a brief scan of the area, a company of an unidentified source is moving from behind a small mountain range to Black Cutlass’s front.  The identification is thus; there is a Gnomic, Butcher, Katana, Spider, Regent, two Specters, another Spider, Scorpion, two Sovereign IIIs, and one more Spider.  Some of these look rather familiar.  I have reported before we are trying to track down the 2^nd. ACR, 14^th. ACR, and the 11^th. ACR.  Well, let us see what develops here; a rendezvous or an engagement.

            The bulk of the opposing force appears to moving through the mountain crossover point unawares of what is on the other side, unless, as I mentioned before, this is a meeting.  This would not be a good place to become bottled up in.

We have our answer as the force moving out on the low lands has come under fire from the Dictator platoon on the right flank of the base.  The Gnomic has sustained several hits with Black Cutlass doing a move-fire-move action.  The Gnomic does score some hits but does a tactical retreat to survive.  The Katana has moved up to open up on Black Cutlass on the right flank.  Shots are being traded.  The Gnomic’s comm. set was knocked out, resulting in the Katana not being warned of the concentrated fire power.   Black Cutlass had, and maintains initiative, which does not bode well for the Katana.  Even though the Katana was in cover and hull down, Black Cutlass did extremely well and eventually KO’d the Katana. 

The Rhino platoon is moving up to the broken ground area, but highly doubtful they will proceed much further as tight as it is.  I would say the best they could do is be a covering force on this flank and keep the opposing side from breaking out of the mountains.

            On the bridge the Regent has come to a halt.  It appears to be in a position to observe the low lands to some extent, but has moved no further.  The rest of the platoon is continuing to close up.  The other platoon has reversed course and is heading back to support the platoon on the low lands.   It has moved in to reinforce the first unit.     In the mean time the opposing force is opening up with indirect fire on B.C.s left flank (the dice indicate the initial map coordinates designated for bombardment and in some cases where they ended up impacting.)  Ahh, it looks like Black Cutlass is following suit and returning the favor targeting the bridge (I think I will need to determine bridge strength for the possibility of knocking it out.)  All in all, little damage was done to either side by the incoming rounds.  B.C. came out a little worse overall.  B.C. did attempt to send the Ghast up the middle for an attack but he received more than he gave.  The battle pretty much bogged down.  Neither side was willing to press the issue.  B.C. was in the worse position having no support.  Our SHOD picked up an encoded transmission from the opposing force and in short order received a reply.  Evidently B.C. also picked up on the comm.  B.C., probably wisely, decided to pull back, rather than find out if it was a call for reinforcements.  B.C. clearly was the victor in this battle, severely damaging the Gnomic and taking out the Katana.   Who ever they are were clearly complacent going against a Pirate unit.  I bet that does not happen again.

This is the Watchman reporting, good day.

 

 

 

 

 

 

Edited July 17, 2018 by Watchman

[sentinel]

Man, I absolutely love all the photos you post of your battles and such.  Nicely done.  

[Watchman]

MercNews Report 5 Update 1
Watchman Reporting
MercNet HQ, Kaitos (2)

 

I bid you greetings;

        Since reporting that the unidentified unit looked familiar, I searched the Archives and spotted a match.  This appears to be the 11th. CAV.  If so they just received a bloody nose from Pirates!!!  This will not look good for them.  I fully expect retribution will be forthcoming.

 

This is the Watchman reporting, good day.

[Watchman]

MercNews Report 7
Watchman Reporting
MercNet HQ, Kaitos (2)
20200604

I bid you greetings;

          This encounter was precipitated by a platoon of fairly heavy CAVs for the pirate group:

Black Cutlass
Division C elements
Platoon strength

vs.

42^nd Legion (Black Watch)
1^st Battalion
3^rd Company elements
2^nd & 3^rd Platoons

            Black Cutlass advanced upon a static position; 42^nd Legion in defensive positions.  Black Cutlass was approaching from the South on the right flank. The 42^nd evidently did not have any air assets on surveillance patrol, as it appears Black Cutlass was able to approach fairly close before the 42^nd took notice of their presence.  The 42^nd sentries were not very diligent in being mobile to continually have a differing view of the surrounding terrain.  Never the less they spotted two Wights closing in.  Black Cutlass was driving his Wights while leaving the rest of his force behind.  The Purple Wight was in position to initiate combat but lacked the range, the Bishop, on the other hand was able to launch his DFMs and scored some damage which resulted in the Wight backing off to cover. The Bishop did try to rattle the Wight by launching some IFMs his way, but as there was no Target Lock, you can see the resulting impact point far enough to the right, that even his Area-of-Effect of 4” was unable to reach out and touch him.
          All the while this was going on the 42^nd Starhawk VI was moving out of the back of the fort, around to the left flank in a hurry, using the roads to good effect. The Sovereign III along with the Falcon, were moving in position to cover the South access point.  The Specter had moved up to the wall position to cover the Bishop. In the mean time the other Wight was moving up behind the ridge and eventually achieved a position where it was able to fire upon the Falcon, achieving hits but no damage.  The Falcon on the other hand did score.  The Wight fell back but was hindered by being in the water so did not achieve a point sufficiently far enough to get out of the line of fire.  The Specter achieving a lock-on could only use his DFMs, due to the range factor.  The Specter did zero in on target and while the missiles started to impact, the crew pod was ejected and the Wight suffered a critical hit putting that CAV out of commission permanently.  The Rhinos never made it to the battle, being bogged down in the heavy woods.  Black Cutlass determined it was better to perform a retrograde maneuver with the fast approaching 42^nd units.

Force details/objectives.

The Black Cutlass had three Veteran crews and one Regular.
Their objective was to probe the Fortress defensive units and:
Determine the size of force present and return with no losses.
They achieve half of their goal by observing six CAVs present.

The battle was considered a draw.
Their big failing was splitting their force, leaving major firepower behind.
Higher Command surmised there were at least two more present to form two complete Platoons and maybe another Platoon in the area for a full company.

The 42^nd had all Regular crews that performed quite well considering their lateness in getting on the ball, damaging one and killing another..

We have all CAVs listed thusly; all start as regulars, as denoted in the first column (R).
The next time that CAV goes into battle it will be as a veteran (V).
To achieve Elite status would require accomplishing ten battles. 
To be an Ace will require five kills.

 

 

 

[Watchman]

Battle Record Keeping/Terrain Modules update.

Battle Record

          The current plan is, as updated, starting as before:

Everyone starts as a Regular (R),

Second battle on, as a Veteran (V),

Kills recorded in every seventh column (K), denoted with a star,

Elites are survivors of eleven battles (E),

Ace is reached on the fifth kill (A).

 

Terrain Modules

 

       I think a compromise will work better by making new modules following the contours in close in places only, such as these:

And staying with the hex pattern everywhere else so as to not unduly reduce the number of places a CAV can set upon. This is based upon the narrowness of many places, if strictly adhering to the contour lines solely.  As you can see, battle planning will still be required for the deployment of certain CAV units due to restricting terrain.

[Watchman]

 

MercNews Report 8
Watchman Reporting
MercNet HQ, Kaitos (2)
202105022

I bid you greetings;

            We received an anonymous report; location not stated.  It appears this involved the remnants of a Black Cutlass company.  The unit was some how cutoff and behind enemy lines.  The sector they are trying to effect an escape was screened by the 2nd. Cav.., 1/1/1.  The area is heavily wooded and very hilly.  Black Cutlass was inadvertently aided by Communications being jammed in the zone, which kept the 2nd. in the dark about enemy activity in their rear area.  Evidently Black Cutlass’s sole objective was to get back to their side.  There movements indicate stealth and evasion as much as possible.  They approached the front line in two groups, observing the terrain layout to best determine the most advantageous route of cover, maybe contemplating whether or not to engage on the way out.  But then again how many forces are near by..  2nd. is still unaware of enemy presence in their rear.  Black Cutlass checking their map coordinates anticipated the main pass through the ridge line would be covered.  Indirect Diversionary fire, with smoke, was carried out on the pass to attempt to draw the 2nd.’s focus on a possible assault through said pass; in the mean time try to slip through a small gap rarely used on the left flank of the 2nd.   The rest of the 2nd.’s 1st. Company had the 2nd. Platoon on the right flank and 3rd. Platoon on the left flank.  Black Cutlass was successful in their breakout.  Had they been in the frame of mind to attack on the way out, the 2nd could have suffered greatly with Black Cutlass coming up to point blank from behind before they could have reacted.

            Black Cutlass escaped with a Halberd, Butcher, Dictator 60, Duelist, and two Wights.

            2nd Cavalry had a Thunderbird, Starhawk VI, Tyrant, and a Crusader.

 

This has been the Watchman reporting.

Good day. 

 

Notes:  The spires in the last few shots indicate indirect fire impacts, these spires are for future peaks.

           Black Cutlass has indicated a desire to work on more module to effect a better visual display.  There are some other fifteen modules that can be built.  In the overall shot near the top you can see four modules alone without terrain features that otherwise would be covered with elevated features.

          We are still running CAV 1 rules.

 

[Watchman]

MercNews Report 9
Watchman Reporting
MercNet HQ, Kaitos (2)
202106026

I bid you greetings;

 

Black Cutlass raid on 2nd Cav. Airbase

 

Black Cutlass                                                2nd Cavalry

                                                                    1st Armored Company

                                   

Emperor           528                                         Centipede HQ

Ogre                487      Damaged                      17 Wolverine AFVs

Gladiator II       322                                          1 obliterated

Panther           199                                          1 KIA

                                                                     1 Damaged

Falcon             310

Rhino               598      Damaged

Dictator 60       306      Damaged

Talon                217

Black Cutlass Mission:

 

            Black Cutlass was hired to cause as much destruction and disruption of the Air Base as possible. Unbeknownst to Black Cutlass there were only five Wolverines deployed for base defense and the rest were in various stages of taking a break, performing minor repairs, or rearming; as they basically just arrived on station.

            Black Cutlass was most fortunate to be able to catch the 2nd Cav off guard.  They used ground cover to the utmost to get as close to the base as possible.  Taking some time with the convoluted terrain present.  They had the option of using a more direct route but then risked being spotted.  They finally reached a point where they were spotted, which started a countdown clock for the mobilization of the remainder of the Wolverines. For the most part the Black Cutlass units performed their move/fire/move actions. In the ensuing battle on each flank a wolverine was knocked out.  The Wolverine had two CAVs hitting him at point blank range and blew him away.  On the left flank the Wolverine crew survived being K.O.d.  Facing him was the Rhino, Emperor, and an Ogre. the three remaining Wolverines backed off finding more cover to stall as long as possible, till the rest of the unit swings into action.  Strangely enough, Black Cutlass ended its attack and withdrew.  Clearly he had the advantage and could have bottled up 2nd. Cav.  They definitely were the victors.   This time with a 1D6, it ended up being 6 turns to mobilize everyone.  Next time with something like this it will be a unit by unit basis to represent the random stages of readiness.. 

[Vil-hatarn]

Neat board! The next terrain project on my list is some 'installation' style terrain just like that. Six turns without reinforcements definitely sounds rough for the defenders, I like the idea of rolling separately for each model.

[Watchman]

5 hours ago, Vil-hatarn said:

Neat board! The next terrain project on my list is some 'installation' style terrain just like that. Six turns without reinforcements definitely sounds rough for the defenders, I like the idea of rolling separately for each model.

The completed ones in the pictures are mounted on 18"x24" Luan/Lauan plywood, many more to do.  The ones completed from now on will not have the elevated sections glued to the board just the ground level terrain, which will make it easier to store the boards and the terrain can be put in a bag.  I will mark the bottom of the pieces with the map number to facilitate faster placement.  The mountains on the other hand, there is no getting around trying to make it easier to store.  I want to make one more with a larger Air Base high up.  You can see the problem in: Sculpting, Conversion, and Terrain/Works in Progress pg3, 3D Terrain, unfortunately there is a height limitation of around 4'.  I will also address the issue of water depth, more  so than I have and the Battletech Boards that have many declivities down to depth 4.  Some challenges ahead, but it is all fun.

[Watchman]

Well, it appears they have been dorking with the web site again and I will not be able to post pictures. I have no idea about uploading from a URL, so It will be a discription of the terrain along with the Battle Report.