Why you should go to an ASL tournament

I notice there’s been quite a number of “new” players who are really “returnees” from Squad Leader or ASL decades ago. Invariably we talk about how they should join a tournament at least once, since tournaments are great places to learn and to meet the community that accelerates your learning and your enjoyment of the game exponentially. These folks do worry about their level of ASL knowledge and whether they will fit into an ASL community with characters who’s been around for decades. Before joining my first tournaments in 2014, I worried about putting up the expense only to suffer some form of hostility because I was (am) not up to par.

“The Malaya Madman” – Perry Cocke

This is Von Marwitz’s perspective, carried with his permission:

Whether new or coming back to the hobby, I would not be worried about not being good enough.

Back in the days, before I attended my first tournament, I had played exactly one single, very small 4.5 Turn scenario of ASL against an opponent. Besides that, all I had done was playing solitaire and teaching the game to myself – with all that entails.

I believe that even very fast players acknowledge, that under such circumstances nothing else than slow play can be expected. My personal experience regarding my treatment back then and by observation later is, that almost all experienced guys (fast or slow) are willing and open to treat such a game more as a tutorial than a competitive game. Needless to say, I did not win a single scenario during my first tournament but yet I had so much fun, that I am still sticking to ASL 25 years later.

So, this goes out to any newbies out here, to those returning to the hobby, and to those who have never attended a tournament:

Don’t worry about not being good enough or not fast enough. Take the dive and give attending a tournament a try. Altogether, the vast majority of players (of all playing styles) I have met, are a jolly bunch and welcoming.

von Marwitz

(von Marwitz is associated with Grenadier 2023, which is going to be held in Gelsenkirchen Germany, 2 Nov-5 Nov)

Related Article: “Journey to a Tourney, Part 1: Decisions”

Going over 8300 hexes, one by one …

Credit: MMPGamers.com, “Sword & Fire: Manila”

Re-reading Mark [Pitcavage’s] post while also going through the final rounds of quality-checking the [MMP Sword & Fire] Manila map.

One map-related quality thing that I don’t think Mark mentioned is the sheer amount of attention to detail that goes into making a map that doesn’t hinder play. Simply put, there are many ways that map artwork can get in the way of play, either by being hard to visually discern or by being confusing to interpret, rules-wise.

I thought I was good at this, just from my years of doing dozens of VASL maps, where every pixel has to be right, or at least not-wrong. But these last few months have shown me that Perry, Klas, and Chas are just impressive this way. Sure, the Manila map has over 8300 hexes, but I’ve strolled through that map dozens of times just looking for things to clarify or fix. And yet these MMP guys have caught a bunch of things I’d missed or never even thought of. And without those fixes, people would have questions about how to play what’s on the map. And that’s not good ASL.

Visual things like making sure hex IDs are easy to read and not obscured by the underlying terrain. Making sure Bypass Movement is obviously NA by having terrain touch the hexside (but not go over!) if possible. Making sure LOS is not messed up by having edges of LOS obstacles being obscured in some way. Even just making sure the text characteristics are consistent throughout the map – all water bodies are labeled in the same way, all buildings, all roads, etc.

And then the subtle things like making it obvious whether units can move from one hex to another of the same building while staying entirely within the building outline itself – not so easy when you’re trying to mimic historical buildings or buildings that are partially destroyed, like we have in Manila.

All of this painstaking effort means that people will spend less time fighting the map and more time playing ASL. And that attention to quality is what makes MMP a pleasure to work with and buy from.

– By Tuomo Repetti and posted with his permission, first posted on Gamesquad, 29 December 2021

Bishop: Converting a Spotting Round to Fire For Effect

First World War: soldiers of the English infantry in France, running out of their trenches at the signal to assault, Somme 1916. CREDIT: Fototeca Storica Nazionale.

(Author: Jim Bishop)

In August 2021 I attended the ASL Scandinavian Open tournament in Copenhagen. The French have OBA in WO33 “One-Eyed Jacques.. Walking around the room twice I observed players incorrectly convert a Spotting Round to a Fire For Effect (FFE). The scenario is an ideal case study for this all-too common error.

For this article I have excerpted a section of the OBA flowchart I will be referring to throughout the article. Understanding this section of the flowchart is key to placing and converting a SR effectively. Conversely, knowing the nuances of this section will help you frustrate your opponent’s attempts to attack with OBA. To make our
discussion clearer I have labeled two of the bubbles, one called A and one called B. Also recall the errata posted in Journal 11 changing AR to SR in bubble B.

For our purposes, we will assume you have successfully navigated the flowchart to the point where you maintained Radio Contact, announced your intention to convert, rolled for accuracy, and corrected the SR if needed. You are now ready to convert it to a FFE.

It is not enough to simply announce your intention to convert a SR as some players presume. There are a couple of crucial conditions which must be met before a SR can be successfully converted to a FFE.

We will first consider bubble A. There are two possible conditions tested in this bubble to determine how we proceed:

  • The Observer has an LOS to the Base Level of the SR hex. Normal LOS rules apply (Blind hexes, LOS Obstacles, LOS Hindrances, etc).
  • The Observer has an LOS to the Blast Height of the SR (C1.32) AND a Known Enemy Unit in or adjacent to the SR’s hex. Because the blast of an SR is visible two levels above the Base Level of a hex, it is possible for an Observer to see a SR in an otherwise Blind Hex. If there are no KEU’s in or adjacent to the SR’s hex the SR remains in place unconverted (the “No” path from bubble A).
    • Per footnote d, Concealed Units in non-Concealment Terrain are considered known to the Observer for purposes of conducting OBA actions.

Next, let’s look at converting the SR to an FFE covered in bubble B. To convert we need two things: a LOS to at least the Blast Height of the SR and an enemy unit. There is a case where an enemy unit is not required and we will examine that shortly.

Observer only has LOS to the Blast Height: When an Observer cannot see the Base Level we already know what happens if there are no KEU in or adjacent to the Blast Height; the SR remains unconverted and we never make it to this bubble. Since there must be one or more KEU and at least one of them must be known to get to bubble B, the SR is converted to a FFE and resolved (the “No” path from bubble B).

Observer has LOS to the Base Level: It gets more interesting when an Observer has LOS to the Base Level of the SR’s hex. Here we will be following the paths from bubble B. Again, we have to ask if there are enemy units in or adjacent to the SR hex. If the answer is no, the SR is converted and resolved using the “No” path. If the answer is yes, we must ask a second question: are all of them Unknown to the Observer. Note footnote “d” telling us Concealed Units in non-Concealment terrain are considered KEU for the purposes of conducting OBA actions. If the answer is no (i.e. at least one of the units is known to the observer) then the SR converts to a FFE using the “No” path. If the answer is yes (i.e. all enemy units in or adjacent to the SR hex are unknown to the Observer) then an extra chit draw must be made from the existing OBA pile. This is the “Yes” path. If the xdraw is black, the card is shuffled back into the draw pile and we follow the “Black” path converting the SR into a FFE. If the draw is instead Red, the card is again shuffled back into the deck and follow the “Red” path resulting in Access Lost and removal of the SR.

Keep in mind the special case of Harassing Fire. While all of the rules about enemy units in or adjacent to the SR remain in play, any units located in the “outer ring” of a Harassing Fire FFE mission do not force extra chit draws. If an Observer has an LOS to the base-level and there are no unknown enemy units in or adjacent to the SR’s hex, the SR will convert to an FFE regardless of how many unknown units there are in the “outer ring” of the affected blast area.

From this brief note, there are some lessons to be learned here:

As the Defender:

  • Concealed Units are your friend. They make conversion more difficult.
  • Carefully watch placement of AR/SR and see if you can sort out where his Observer is. If
    you can stay out of his LOS, conversion is more difficult.
  • If you can force an extra chit draw it is possible you can negate the mission and make
    him start over again with a new card draw.
  • Knowing the flowchart is essential to effectively defending against OBA

As the Attacker:

  • Be careful where you place your SR. If it drifts to a hex where you have LOS to the Base
    Level of the SR’s hex and there are only unknown enemy units in or adjacent to the SR’s
    hex you could be forcing an extra chit draw.
  • An enemy skulking in a woods line can be mauled pretty badly with Harassing Fire even
    when out of LOS.
  • Knowing the flowchart is essential to effectively attacking with OBA.

Examples: For this section please refer to the illustration. The Observer is in 13aI5 on level 2. Three SRs are on the labeled SR — A, SR — B, and SR — C. We will discuss each of these in turn.

SR — A: The Observer has LOS to the Base Level of the SR. As such, we flow from bubble A to bubble B. There are enemy units in or adjacent to the SR’s hex. The unit is un-Concealed and in the LOS of the Observer. As such, it is a KEU meaning we flow from bubble B via the “No” path and convert the SR to an FFE and resolve it.

Were the 4-6-7 Concealed the situation would be entirely different. In that case, there are units in or adjacent to the SR’s hex and they are unknown to the Observer. We would flow from bubble B via the “Yes” path and make an extra chit draw. If the draw is a black chit we follow the “Black” path and convert the SR to an FFE and resolve the attack. If instead a red chit is drawn we would follow the “Red” path, Lose Access, and remove the SR.

SR — B: The Observer does not have LOS to the Base Level of the SR’s hex but he does have LOS to the Blast Height. Looking in bubble A, when the Observer has LOS to the Blast Height, we need to determine if the Observer has LOS to KEUs in or adjacent to the SR’s hex. In this case, there are two units Adjacent to the SR, but both are out of LOS of the Observer and do not meet the requirements of bubble A to leave via the “Yes” path. As such, we leave bubble A via the “No” path and the SR remains in place unconverted.

SR — C: For this one, the Observer is trying to convert the SR to an FFE Harassing Fire. In this case the Observer has LOS to the Base Level of the SR. We leave bubble A via the “Yes” path. In bubble B, we ask if there are enemy units in or adjacent to the SR. There are none so we exit bubble B via the “No” path and convert the SR to an FFE Harassing Fire. Even though the two 4-4-7s will be attacked by the FFE AND they are out of LOS of the Observer, the SR will still be converted. These units are not in or adjacent to the SR’s hex so they do not affect the conversion to FFE process.

Clearly, there is more to attacking with, and defending against, OBA than offered in this brief note. If you would like to see more about this or some other topic let me know what interests you and I may take that on. I hope this brief article is useful and if you find any errors please let me know and I will correct them. — jim

(Carried with Jim Bishop’s permission)

Original posted here : https://jekl.com/2021/09/10/converting-a-spotting-round-to-fire-for-effect/

Bishop: Stop and Go Traffic: A Synopsis


Royalty free HD Battle of the Bulge photos | Pikrepo

Author: Jim Bishop

Recently, players have posted questions surrounding Moving, Motion, Starting, Stopping and how these interact with C6 Target-Based To Hit DRM. These questions appear cyclically and I can recall answering them for as long as I have played ASL. Much of the information in this article appeared in Ole Boe’s Stop and Go Traffic article which originally appeared in the ‘96 ASL Annual. These old Annuals are available as PDF files or can be picked up used, through all the usual outlets. I highly recommend you read the original as it is still informative but for those who can’t, I offer this summary of that article here.

Moving and Vehicular Target:

To properly apply all the DRM it is important to first understand the difference between Moving and Moving Vehicular Target. Moving Vehicular Target, sometimes referred to as Moving Target, is defined in C.8. Any vehicle currently in Motion is a Moving Vehicular Target. In addition, any vehicle which starts ITS MPh in Motion, has entered a new hex, or bypassed a new hexside in its current hex during ITS MPh is a Moving Vehicular Target during Defensive First Fire or Final Fire. The key here is the vehicle either started in Motion or has moved to some new position on the board.

Moving is slightly harder. Not only is it not defined in the Index, it is never well defined in the ASLRB. In ASL, Moving means the unit is currently conducting ITS MPh. There can only ever be ONE moving thing. That thing can be a single unit, multiple units moving as a stack, a Human Wave or some other Impulse-based movement, etc. The unit or units actively spending MFs/MPs are Moving regardless of how many units are doing it or if they successfully use the MF/MP(e.g., failed Smoke Attempt DR/dr). Even though Moving, a unit which doesn’t spend MP/MF’s cannot be fired upon unless they actually spend the MP/MF. The closest the ASLRB comes to stating this is in A8.1: “… The portion occurring during the enemy MPh is called Defensive First Fire and can be used only vs a moving unit(s)…” It would eliminate a lot of player confusion if such a key concept was in the Index.

Stopped and Non-Stopped:

The Index defines a Non-Stopped vehicle as one which has not expended a Stop Movement Point (MP) since its last Start MP expenditure during ITS MPh. This should sound a lot like the earlier definition of Moving. That’s because it is. A vehicle can only ever be Stopped or Non-Stopped while it is conducting ITS MPh, i.e., Moving as defined earlier. Knowing what Non-Stopped is, we can surmise a Stopped vehicle is one which has spent a Stop MP or somehow become Immobilized/Bogged while Moving. This is covered in C.8.

Motion Status:

A Moving vehicle, i.e., one conducting ITS MPh, cannot be in Motion status. It is either Stopped or Non-Stopped. A vehicle which ends ITS MPh without spending a Stop MP is covered with a Motion counter to reflect its Motion status and is treated as a Moving Vehicular Target. A vehicle which begins ITS MPh covered with a Motion counter has the counter removed and the begins ITS MPh as a Non-Stopped, Moving Vehicular Target. A vehicle not covered with a Motion counter begins ITS MPh as a Stopped, non-Moving Vehicular Target.

From all of this, it should be clear a vehicle can be Stopped but still qualify as a Moving Vehicular Target. Conversely, it is possible a vehicle can be Non-Stopped and not qualify as a Moving Vehicular Target. A vehicle under a Motion counter is ALWAYS a Moving Vehicular Target. In all cases, Moving, Moving Vehicular Target, Motion, and Stopped/Non-Stopped represent different states. Understanding those states along with a careful perusal of the various charts will make it easier to correctly apply DRM when the time comes.

With this as background, we are ready to explore how all these rules interact and how they are properly applied. Knowing the correct application of these DRM is among the first steps to better combined arms and AFV play. Onward.

EX 1: An AFV begins ITS MPh NOT in Motion and spends 1 MP to Start. This AFV is now conducting ITS MPh (i.e., it is Moving). Since it spent a Start MP it is now Non-Stopped but not yet a Moving Vehicular Target. Looking at the C6 Target-Based TH DRM Table, we see Case L would be NA (the AFV is a Non-Stopped target). Additionally, Case J would be NA (the AFV does not qualify as a Moving Vehicular Target). For the purposes of CC Reaction Fire or CC, the AFV is Non-Stopped so a +2 DRM would apply (A11.51). If the AFV survives all in-coming fire on the Start MP, it may enter a new hex or bypass a new hexside. Once it has done this, it qualifies as a Moving Vehicular Target, but not before. This has some serious implications. If you start for 1 MP and change the VCA 2 hexspines before entering a new hex or hexside, that would be three potential shots before Case J DRM applied.

EX 2: An AFV begins ITS MPh in Motion. As it is conducting ITS MPh, the Motion counter would come off and the AFV is considered Non-Stopped and Moving (i.e., conducting \ITS MPh). All fire against it during Defensive First Fire and Final Fire suffer Case J DRM. If it spends 1 MP to Stop, it becomes a Stopped vehicle but would still be considered a Moving Vehicular Target. As such, Case J DRMs would still apply but Case L could now also apply making it possible for an AFV to be both Point Blank and a Moving Vehicular Target. Also, once the AFV becomes Stopped, there is no +2 DRM in CC/CC Reaction Fire against that AFV even though it is still considered a Moving Vehicular Target.

EX 3: An AFV is covered by a Motion Counter outside ITS MPh. Case J would apply to all shots as the AFV is a Moving Vehicular Target. Case L would be NA as the AFV is In Motion. All CC would suffer a +2 DRM for attacking an AFV in Motion. The AFV is Non-Stopped.

EX 4: This is an extension of EX 2. The AFV survives all fire on the Start MP and moves 3 MP to a hex adjacent to an enemy AFV. Surviving all incoming fire, the AFV Stops for 1 MP. The enemy AFV could shoot at the Moving AFV. If it does so, it would pay +2 Case J but also qualify for a -2 Case L since the Moving AFV is now Stopped having spent a Stop MP.

EX 5: An AFV starts adjacent to an enemy AFV. The Moving AFV spends 1 MP to Start. The enemy AFV elects to shoot. It would not qualify for Case L (the target is Non-Stopped) but it would also not be hampered by Case J as the target does not qualify as a Moving Vehicular Target yet.

I have not covered Motion attempts in this briefing but from the last few examples you should be able to extrapolate how powerful it can be to save your AFV. If an AFV is being attacked by an enemy, making a successful Motion attempt instantly qualifies your AFV for Case J and negates any potential for Case L, a +4 DRM in favor of survival. Combine this with a free CA change as part of the Motion Attempt and you can point your thickest armor to the threat. In your friendly fire phase, freely change your VCA to point in a direction where cover is hopefully available, saving the AFV from destruction.

I hope this brief article is useful and if you find any errors, please let me know and I will correct them. Thanks and go read Stop and Go Traffic. It’s worth your time. — jim

(Carried with Jim Bishop’s permission)

Original posted here : https://jekl.com/2021/09/09/stop-and-go-traffic-a-synopsis/

2020 Top 10 Posts on HongKongWargamer

2020 Top 10 Posts on HongKongWargamer

Advanced Squad Leader

 

Folks, these are the top 10 articles that got the most reads this year.

10. Do not let Valuable ASL Time slip by – Walter Branham, Berserk Commissars

09. What I love best about the Global ASL Community

08. About Me

07. Grognards Speaks : Advanced Squad Leader Articles That Change Their Lives

06. Tactical Notes

05. Getting Started with Advanced Squad Leader

04. Katz: Designer’s Response to the Desperation Morale Review of Forgotten War

03. Resources for Advanced Squad Leaders

02. Advanced Squad Leader is the Greatest Wargame Ever Published

01. Upcoming Advanced Squad Leader Products

What I love best about the Global ASL Community

Mr Paul M Weir, Clovis

I have never met Mr Paul M. Weir.  I know he played ASL solo because he looked at the Advanced Squad Leader system as a sandbox.  I know he was a programmer and that he kept a few cats: Comet, Clovis & Halo.  I interacted with Paul more than a few times over the years.  This man’s an outstanding expert of World War 2 armor and weaponry and had lent his expertise on a few ASL designs.

I remember sending him a fuzzy black and white photo of a tank spotted in the China theatre.  He came back telling me that it’s some hybrid tank whose turret was taken off from one tank and added on the chassis of another.  Then he moved onto more details about the origins of the turret according to something peculiar he spotted.  It blew my mind but like a lot of people would tell you, we learned every time we heard from him.

He was also a moderator in the GameSquad forum.  I have always love his tone and the way he went about things.

Mr Paul M. Weir embodied what I love best about the global Advanced Squad Leader community.  Mr Weir passed away suddenly on Dec 6.  It had been such a great pleasure knowing him, I’d like to think there’s some way he can still play with his beloved ASL sandbox in the Great Beyond.

Articles that Mr Paul M. Weir allowed me to post on HongKongWargamer.com:

Do not let Valuable ASL Time slip by – Walter Branham, Berserk Commissars

Do not let Valuable ASL Time slip by – Walter Branham, Berserk Commissars

Hi Comrades –

I just want to send a little encouragement to those of us waiting for face to face. to begin learning.

in my opinion, playing face to face is the ultimate ASL experience, however there is a lot to be said about VASL online.

First, I believe VASL is a far superior learning tool than face to face.

It provides fast and quick exposure to counter retrieval. easy and fast set up, easy counter movement, easy Hidden Initial Placement (“HIP”), common dice rolls, easy guide to Off Board Artillery, and as a bonus: easy saving/storage of the game.  You can sit down and play/learn for a couple hours, save the game and start up later. A lot of the mechanics and important charts are built into VASL.

You avoid the time it takes to travel to the game and the time it takes to set up…….time that can be better used for actually playing the game.  In addition, if I piss you off, you can give me the finger and i won’t even know it!

Even when things get back to normal and it is easier to play face to face, and that could be a long time, i still believe VASL to be a great way to increase your ASL skills and abilities.  The two most important things to learning ASL is to make time to do it and to play.  Every day you delay you let valuable ASL time slip by.

Finally, in response to someones who said, “I want an understanding, sympathetic, and patient opponent for my first game. I have a lot of questions; and your after action reviews raise even more”.
I would just like to say that there are quite a few of us who fit that bill.  I would say most of us, some more than others.  Personally, it would be a pleasure for me if we can spend some time helping you learn the game and I know others who feel the same way.

I am grateful to the fellows in BC [Berserk Commissars] who were patient with me 12 years ago and still are today.

Of course, you have your own opinions and you must do what makes you most comfortable, but should you change your mind and decide that may be now is the right time to give this a try, feel free to hit me up and we can get started.

Kindest ASL regards, 

Walter Branham, Berserk Commissars of Portland. Oregon

Katz: Designer’s Response to the Desperation Morale Review of Forgotten War

Kenneth Katz is a member of the designer team for MMP’s groundbreaking Korean module – Forgotten War.  This is Ken’s response to Mark Pitcavage’s extensive critique of MMP’s Korean module – Forgotten War.  I find it so interesting by its own right that I asked Ken’s for his permission for HKWG to carry it.  While you can certainly read Mark’s critique first, I am sure you will get a lot out of this even if you read it as a “standalone”.  I certainly did.  These two learned gentlemen certainly make our ASL lives richer with their exchange.

ThumbnailOn behalf of the Forgotten War design team, I want to respond to Mark Pitcavage’s recent review of that module on his highly regarded ASL website Desperation Morale. Obviously, we have a protective attitude towards Forgotten War. Its development dominated much of our free time over the years (for some over 18 years!) and Mark’s critical review is less than pleasing to us as a team. However much we disagree with elements of the review, we want to commend Mark for his thorough critique.

The Forgotten War core design team consisted of Mike Reed, Ken Katz, Paul Works, Andy Hershey, and Pete Dahlin. Each brought a very strong skill set to the team and our differing styles and capabilities meshed well. The Forgotten War extended team included approximately thirty additional participants from across the globe; all such participants were included in the Korean War ASL Yahoo Group and had access to all development material, to include the rules. Any intimation (or direct statement) that development was done in isolation is false.

Mark’s discussion of the history of the product is generally correct up to a point but does not accurately describe the relationship between Forgotten War and the Kinetic Energy ASL module which was never published. It is true that one of the co-designers, Mike Reed, worked with Mark Neukom on the Kinetic Energy design and we are certain that earlier work influenced Mike’s contributions to Forgotten War. Personally, my only connection with the Kinetic Energy design was a 5-minute glance at it. The major design elements of Forgotten War, including Steep Hills and the CPVA rules that we created, did not come from Kinetic Energy. This is true for all the other core Forgotten War team members as well. Furthermore, the Kinetic Energy style did not mesh well with MMP’s vision for ASL, so a new design was necessary since a primary of objective of this project was to design a product that would become “official.” MMP put the product under contract in 2011. It then waited in MMP’s development queue for several years, with intensive work resuming around 2015 and publication in late 2017.

Steep Hills and Semi-Geomorphic Mapboards 80-83:

Korean terrain had a tremendous influence on the conduct of the Korean War. Through research, it became apparent that the existing variety of ASL terrain types did not represent the tactical effects of much militarily significant Korean terrain. The result was the Steep Hills rules (W1.3), which could be described in a nutshell as doing to Hills what the Dense Jungle terrain does to Woods. The essential requirements of Steep Hills were to deny off-road movement for vehicles, burden infantry movement particularly by heavily laden troops, and provide some protection because the terrain is broken. Note that such terrain is not unique to Korea. Terrain with such characteristics can be found in places as diverse as Afghanistan, Italy and Israel. The use of Steep Hills terrain puts a premium on infantry and greatly restricts the use of heavier support weapons and vehicles, which is accurate for many Korean War battles. The mapboards not only represent the hills and valleys which were the sites of many Korea War valleys, but the topography of those mapboards combined with the Steep Hills rules mean that there are ample opportunities for an attacker to infiltrate and withdraw while being protected from enemy fire. Using Forgotten War boards and Steep Hills terrain, a defender cannot just sit on peaks with a MG and sweep the hill clean of attackers, and that was very much the intent. Taken as a whole, the rules and mapboards provide the “design for effect” that was intended and reflected the team’s research.

Chinese People’s Volunteer Army (CPVA):

Probably Mark’s most serious objection to the Forgotten War design is the CPVA. Before addressing the finer points of the CPVA rules (W7), we should preface our responses with several “big picture” points. The CPVA was a major combatant that fought in distinctive ways that deserves distinctive nationality characteristics. All nationality characteristics are exaggerated stereotypes, but that does not mean that they don’t have a significant element of truth. The best way to appreciate the CPVA in Forgotten War is not to focus on each rule but to see how the totality of the CPVA rules, the scenario orders of battle, and the scenario victory conditions combine to incentivize the CPVA player to fight the CPVA in accordance with its distinctive doctrine and tactics. The portrayal of the CPVA in Forgotten War was based on extensive research that utilized a wide range of sources. These included numerous historical books/narratives by Western (U.S., British, Canadian, French, Belgian, etc.) authors using multiple original sources; U.S. Army historical documents, to include multiple, previously-classified documents; U.S. Army operations research books/documents that included analyses of operations and interviews with CPVA personnel; South Korean historical documentation; and multiple books by Chinese authors. The CPVA’s representation was available to the entire, extended Forgotten War team. Scenarios and Chapter H content were informed by a Chinese-speaking team member that had access to additional Chinese-language source material.

The intent of the portrayal of the CPVA in Forgotten War was to represent several characteristics of that force: its mass, its willingness to tolerate very high casualties, the primitive nature of its communications and logistics, and its tactical doctrine which emphasise closing with the enemy. The latter both leveraged the strengths of the force and reduced the ability of its enemy to use its superior artillery and airpower. In the interests of brevity, we won’t take a deep dive into every rule, but we believe that to those who understand the CPVA and the CPVA rules in Forgotten War, the logic behind the rules makes sense. Needless to say, far from denigrating the CPVA, the Forgotten War rules and scenarios in combination show the CPVA to be a formidable foe.

CPVA Step Reduction:

The following represent the primary reasoning elements we used to select Step Reduction (W7.21) to represent the CPVA. Taken individually they are evidential and indicatory. Taken as a whole, and leveraging existing ASL rules constructs, Step Reduction was the answer.

  1. Prisoner ratio. Using estimated casualty numbers, we have the following historical percent-of-casualties data (i.e., these percentages show the percent of total casualties that prisoners represented): Allies WW2 (Pacific Theater) 24%; Japanese WW2 2.2%; CPVA KW 2.8%. Although more than moderately suggestive, these estimates do not address a number of related considerations (such as the huge number of Chinese troops freezing to death vice being combat casualties).
  2. Numerous personal narratives from KW participants about CPVA troops weathering huge amounts of firepower and still coming. Sort of like being berserk in ASL, except they were not berserk and could change what they were doing when commanded to do so (i.e., they did not just always charge right toward the nearest enemy).
  3. Accounts of many CPVA soldiers, who would begin a charge/human wave (HW) unarmed, picking up the weapons of their dead/wounded comrades and continuing forward. Some similar accounts appear in descriptions of Russian HWs (in Stalingrad, for example); in the CPVA case, however, the descriptions do not describe large numbers of Chinese troops breaking. Going to ground and melting away, yes. Large groups of them breaking and running away (like what can result in a standard ASL HW), no.
  4. The political indoctrination and presence of POs in even the smallest units had a major impact on how the CPVA troops behaved. They were more motivated by such indoctrination than typical Russian troops and were motivated as such to continue on in the face of significant casualties.
  5. Step Reduction is an existing ASL rule that will be familiar to most intermediate- and advanced-level ASL players.

Initial Intervention:

CPVA Initial Intervention squads represent troops armed with weapons obtained from the Nationalists (GMD) and the Imperial Japanese Army. The Soviet-Armed squads represent troops armed with Soviet weapons, primarily “burp guns,” which is what Americans called the Soviet-supplied PPSh submachine gun and its Chinese-manufactured version Type-50. The dates given in W7.12 and W7.13 are a simplification; the Soviet-Armed squads will not be available before April 1951, but the Initial Intervention squads obviously do not all instantly disappear or rearm after that date.

The CPVA that intervened in late 1950 in Korea lacked any significant amount of radios and motor transport. In general, CPVA troops on the front line during that period suffered terribly from cold, hunger, and lack of ammunition, the latter being exacerbated by the wide range of ammunition types used by the variety of weapons in the CPVA arsenal. That primitive and deficient CPVA communications and logistics generally caused the effects portrayed in W7.11 is no surprise. Nor is the absence of OBA during that time period surprising, given that artillery is particularly dependent on good communications and ammunition supplies. Of course, a scenario designer can add an SSR when these generalisations did not apply.

Leadership:

The CPVA leadership model in Forgotten War (W7.3) is not a slight against the quality of CPVA leadership any more than similar leadership models are intended to denigrate Finnish and Japanese leadership. Again, look at the big picture rather than each element of the module in isolation. The leadership model that was chosen by the designers works well with the rest of the rules for the CPVA.

CPVA AFVs:

Later in the war, the CPVA did have a significant armored force in Korea. However, the only evidence of which we aware that claims this force (as opposed to the odd captured UN AFV being used) was actually engaged in combat with UN forces is traceable to one Chinese claim. We discovered no American after-action reports that describe losses to American armor caused by Chinese AFVs (one suggestive original source claims that Chinese tank guns were firing at U.S. troops; but after care examination of related sources, it is appears these “high-velocity rounds” were from direct-fire artillery). It’s axiomatic in military history that measures of one’s own losses are usually more reliable than claims of losses inflicted on the enemy. We disagree with Mark that including counters for vehicles that were present in theater but never saw combat is a good use of a finite number of countersheet spaces. If a scenario designer chooses to portray CPVA armor in a scenario, he can use Russian T-34/85, JS-2 and SU-76M counters. In addition, MMP informed us that if a counter did not see action it does not go in the box.

CPVA AA Guns:

As the war progressed, the CPVA became well equipped with AA guns. Such AA guns rarely were present in the front line within the scope of a typical ASL scenario. If a scenario designer chooses to portray CPVA AA guns in a scenario, he can use Russian 37mm and 85mm AA guns. Again, finite countersheets forced choices.

Night Rules:

It is true that Forgotten War has a lot of night scenarios for the simple fact that the Korean War had a lot of night actions. The US Army today likes to say that “We Own the Night” because of its excellent technology and proficient use of that technology. But during the Korean War, that technology did not exist and the Communist enemy preferred to fight at night because it tended to negate American advantages in artillery and airpower. Mark does not like the current night rules in E1 and laments that the Night rules were not revised in Forgotten War. But there is an unwritten but very real policy in “official” ASL that new additions to the ASL system must be backwards compatible with the existing system, including counters, rules, and scenarios. Making general ASL changes was simply outside the scope of Forgotten War.

Searchlight Combat:

Searchlight operations played a major part in the later stages of the Korean War. As mentioned previously, the CPVA used massed night attacks to mitigate American firepower and were very effective. The longest retreat in U.S. military history (U.S. Eighth Army in late 1950) was a direct result of effective CPVA manoeuvre and envelopment…at night. Searchlights took that advantage away from the Chinese.

Our research uncovered that searchlight tactics used against the Chinese were so effective that searchlight-equipped M46 and Centurion tanks became primary artillery targets, especially during the Battles for the Hook. Hide and seek tactics were developed. Tanks operating in pairs or groups. Shutters that could be opened and closed very quickly to minimize highlighting/silhouetting. We worked very hard to replicate these tactics in the rules. Searchlights are certainly chrome. That said, leaving them out or oversimplifying them would have been neglected a tactically significant aspect of the Korean War.

Two-Tone Counters:

Mark doesn’t like two-tone counters. De gustibus non est disputandum (“In matters of taste, there can be no disputes”), but we have been around the ASL community for 25 years and have never been aware of a significant group of players who don’t like two-tone counters (as opposed to the vocal opponents of overlays and terrain altering SSRs). The problem is that the sorts of colors that suit ASL counters (various shades of brown, tan, green, blue, and gray) are already taken, unless you want to either use minor and nearly indistinguishable variations of shade (which some find difficult to see) or use colors which just don’t seem to fit the game. Lavender counters, anybody? Furthermore, the use of two-tone counters has other advantages. ROK and Other United Nations Command forces were equipped by the US. Since their counters have a green border like American counters, they easily can use American SW, Guns, and Vehicles. The CPVA counters have a brown border like Russian and GMD counters, and they can easily use both Russian and GMD SW, Guns and Vehicles. In fact, MMP requires designers to fit their numbers of counters within a finite number of countersheets, and two-tone counters for some nationalities reduces the requirements for counters.

Small Forces: Rangers, American Paratroopers, Royal Marine Commandos, and Korean Marines:

Rangers, American Paratroopers, Royal Marine Commandos, and Korean Marines are unabashed chrome. These all were interesting forces that can be represented with very little rules overhead. Mark doesn’t seem to like this kind of chrome. The Forgotten Wars designers disagree. Judging by the plethora of obscure yet fascinating things in the system, so do most ASL players. Rangers and Royal Marine Commandos were true elite special operations troops, and their capability in Forgotten War are indicative of their training. The 7-4-7 American paratroop squads in World War II imply that those troops had a high percentage of submachine gun-armed soldiers. American paratroopers in the Korean War were armed with the M1 Garand rifle and not many submachine guns, hence the 6-6-7 value.

Rules Pertaining to Bayonet Charges and VT Fuzes:

Bayonet Charges were in fact occasionally used by UN forces in the Korean War. The inclusion of the rule in Forgotten War is simple and appropriate. Variable Time (VT) Fuzes for field artillery were first used by the U.S. Army in the Battle of the Bulge. They had an important effect on that battle and were very valuable in Korea when defending fortified positions against massed infantry attacks. Again, the rule in Forgotten War is simple and appropriate.

Rules Pertaining to HEAT and Bazookas:

The ASL armor penetration rules (C7) are fundamentally flawed and unrealistic in that they significantly misrepresent the actual interaction between ammunition and vehicle targets. Unfortunately, it is wildly impractical to do a wholesale overhaul of those rules, given the imperative of “backwards compatibility” and to maintain relative simplicity (if anyone has ever played the fun but very-detailed Tractics they know the issue). But the Forgotten War designers had a problem. The BAZ45, which equipped US Army and ROK troops in 1950, is somewhat effective against the T-34/85 in ASL. However, in 1950 Korea, the M9A1 launcher and M6A3 rocket which are represented by the BAZ45 counter were notoriously ineffective against that target. This is not an issue of chrome. The difference between ASL and historical performance greatly affected certain scenarios and had a real-life tactical impact. As a result, the Forgotten War designers chose to use rules W.8 and W.8A to model this important effect while avoiding an undesirable revision to C7.

Errata:

Players will observe that the astonishingly small amount of errata for Forgotten War is a testament to the combined efforts of the designers, the playtesters, and MMP.

In Conclusion:

The designers of Forgotten War remain confident that they have created an accurate, playable, and high-quality portrayal of ground tactical combat in the Korean War that fits well in the ASL system.

Kenneth Katz

Listen to Kenneth Katz’s interview on the 2HalfSquads: Episode 187 Kool Katz in Korea

Paul Weir : Did the 1st SS at The Battle of the Bulge have any Tiger Is?

One of the rockstars in the GameSquad ASL forums is the resident armor super-genius human Chapter H, Mr. Paul M. Weir. Mr. Weir has gratefully allowed the publication of his posts here.

pzvibThe Tiger II that accompanied 1SS belonged to 101/501 SS sPz Abt (heavy tank detachment). 101st got renumbered to 501st about Sept. ’44. 501st was a corps level unit (1ss Pz Korps), though originally built around the former 13th sPz Komp of 1SS Pz Rgt (1SS Pz Div). At full strength 501 had a HQ of 3 Tiger II and 3 14 Tiger II companies for a total of 45. At the start of Wacht am Rhein only 30 of the 45 took part in the initial offensive, the remaining 15 arrived after Peiper’s drive had long died, due to transport difficulties.

1SS had a Pz Regt with 2 Abteilungen (detachments/battalions). The 1st Abt should have had 76 Panthers and the 2nd 76 or 96 Pz IV with 3 Panthers and 5 Pz IV in Regt HQ. The Germans were only able to scrape up close to 37 Panthers and 34 Pz IV. That was sufficient for an Abt HQ (3 Panthers) and 2 each 2 companies of 17 Panther/Pz IV respectively. I can’t be arsed to check but I think it was 1st & 2nd (Pz IV) and 6th & 7th (Panther) that made up 1 Pz Abt. So they only had a single Abt’s worth of their own tanks and were loaned 501 SS SPz Abt to stand in for the missing 2 Pz Abt. 1SS Pz Div also had 21 Pz IV/70 aka JgPz IV L/70 but no StuGs, Marders, Wespes or Hummels. They did have SP 7.5cm (SdKfz 251/9) and 15cm sIG 33 on SdKfz 138/1 Grille.

pzvie1SS did get issued a company’s worth of Tiger I early in ’43, I think just during/after 3rd Kharkov. These were used through Kursk and until 1SS got sent home and rebuilding. The genesis of 101 SS sPz dates to the removal of 1SS, for West rebuilding, diverted to Italy. The 3 SS Pz divisions each had a Tiger I company but as 1SS and 2SS were withdrawn 3SS Totenkopf was the only one to retain Tiger I. Totenkopf and the Heer’s Grossdeutchland were the only divisions to finish the war with any type of Tigers and also both Tiger I not II. So 1SS had not had any Tiger on the books by the end of ’43. The SS Tiger I in Normandy belonged to 101 sPz SS Abt and 102 SS sPz Abt.

The only Tiger Is that I can think in WaR of belonged to sPz 301 (Fkl) which had 31 rebuilt Tiger I acting as command vehicles for RC demolition vehicles (Bogward IV) and that was a Heer (army) unit.

So 1SS only had the loan of Tiger II in 501 SS sPz Abt and had had no Tiger I since leaving Russia.

Were there any ‘Ferdinand’ TDs in the battle, at Bastogne, with Peiper, or at St. Vith? What TD or AG or SP, which looks most like a Ferdinand TD, was deployed with the VG divisions?

While I can’t recall the details, I’m fairly certain that KG Peiper was doomed by the time the last 15 arrived. With the demise of KGP, the 501 SS sPz Abt was in need of rebuilding. After the dregs of KGP escaped the 1SS withdrew for reorganisation and eventually reappeared near Bastogne. By that time 501 SS sPz Abt was no longer rigidly attached to 1SS and had reverted to being a corps unit, though obviously strongly associated with 1SS. So post KGP time would have been spent regathering scattered vehicles and repairs, including the 15 latecomers.

I don’t have a good number for the Tiger II losses in the initial offensive, but have a vague memory of only about 7 Tiger II pocketed with KGP. The buggers were just too slow to keep up and be pocketed. Allowing for recovered breakdowns 501 should have had about 2/3 of its official strength at least recoverable if not yet fit for combat by the time of the end of KGP.

pzjgNo Ferdinands/Elephants in Wacht am Rhein (WaR). The source of the confusion might have been the presence of sPzJgrAbt 654 which was one of the original two Elephant battalions, was in WaR but equipped with Jagdpanthers and the other, sPzJgrAbt 653 was involved in Nordwind and had Jagdtigers.

The VG divisions had a PzJg Abt with a towed 7.5cm PaK 40 battery (9, usually 12 guns), a SP light FlaK company (12 x SdKfz 10/5) and a SP battery with 10 (HQ 1, 3 platoons of 3) or 14 (2, 3 x 4) Hetzers or StuG III. All WaR divisions might also have had support from corps and army level StuG (usually 31 StuG, though up to 45) and sPzJg (45 Hetzers or 30-31 Hetzers and 14-15 Jagdpanthers) units. They also had either a Füsiliere (recon+assault) company or battalion which was mainly bicycled infantry and a few armoured cars (if they were lucky).

Pz IV/70 aka JgPz IV with 7.5cm L/70 gun were only issued to Panzer divisions PzJg Abt, typically 21 Pz IV/70 and 12 towed PaK 40.

Marder I/II/III usually equipped Pz and PzGren divisions but by then had practically disappeared, being replaced by JgPz IV and Pz IV/70.

StuG III could be in nearly anything; anybodies PzJg Abt, StuG Abt/Brigades or even Pz Regt, replacing the by now scarce Pz IV.

Paul M. Weir

(Note: I added the counter art, any error’s all mine.)

Paul Weir : What types of M4 Shermans did US forces use in Europe?

One of the rockstars in the GameSquad ASL forums is the resident armor super-genius human Chapter H, Mr. Paul M. Weir. Mr. Weir has gratefully allowed the publication of his posts here.

M4M4A1M4: The original design with radial petrol engine, M4A1 had the same engine but a cast hull, so I will deal with them together. Initially the preferred engine, both M4 and M4A1 (75) saw service from Torch to war’s end. They would have been the sole combat models until late ’43, early ’44 and between the two would still just have been the largest percentage of M4’s by VE day. Both later got better front hull armour (thicker at 47° vs older 56° from vertical). From early ’44 the M4A1 got the 76mm while some of the M4 were 105mm armed. From memory of photos the 105mm M4 always had the later 47° hull whilst many of those late 75mm M4 had a cast front (aka composite hull). A composite hull M4 would be a M4A1 in ASL terms. The 76mm M4A1 first saw service in Operation Cobra. Not sure when the 105mm M4 saw combat, but I suspect late French campaign. The British fitted 17lbr to M4 but not to M4A1. What looks like a 17lbr M4A1 is actually a 17lbr M4 (composite hull).

M4A2M4A2: Diesel twin engines. Starting with 75mm and 56° hull, they progressively went to 47° hull and finally 76mm. Used by the US for training, saw US combat service only with the USMC. Most LL to the USSR, Britain and France, in order of priority, indeed one of the USMC batches was “stolen” from a USSR allocation. Only the USSR used the 76mm versions.

M4A3M4A3: Ford petrol twin engine. Had all the variations of the M4A2, but also had a 105mm version. Indeed it is quite difficult to tell the 2 apart, only the different horizontal engine decks are a good guide. Though some may have been used mid-Italy campaign, it was really D-Day onwards when they would have seen much service. 75mm, 47° hulls, I suspect Cobra+ and the 76mm and 105mm versions only becoming common by the end of the French campaign. The USMC eventually switched to the M4A3 from the M4A2. The US switched from considering the M4/M4A1 engine as the preferred one to the M4A3’s Ford.

M4A3E2M4A3E2: Doled out in handfuls to (mainly) M4A3 battalions. I think they were preferentially given to separate tank battalions allocated to infantry divisions, though some saw use in armoured divisions. NW Europe only.

shervaM4A4: 5 car engines fused together!!! US training only, LL to Britain and possibly France. Only 56° and 75mm, though the British fitted their 17lbr.

M4A5: Not a Sherman, but a type designation for the Canadian Ram tank.

M4A6: Diesel radial engine. Training/development only.

Italy: M4 & M4A1 throughout the campaign. M4A3 starting to appear mid-’44, likely as new battalions fed in.

Northwest Europe: Initially mainly M4 & M4A1 with some M4A3. In the immediate post invasion many separate and armoured division battalions were shipped straight from the US. These seem to be mainly M4A3 variants.

Mixing: M4 and M4A1 were practically interchangeable, so while many units would have started as pure M4 or M4A1, replacements could have been either. Naturally the USA preferred that M4/M4A1 were not mixed with M4A3 but there were times like very late ’44 when the USA was running short due to losses. The British either offered or gave the USA some of their Shermans at that time. So you would see awkward mixes, especially when allocating 76mm and 105mm variants. The US could readily support logistically such less than optimal mixes.

Gun Mixes: From Cobra+ expect to see no more than 20% 76mm, the rest 75mm. By Bulge 40% 76mm and by VE 60%+ 76mm. The problem was that was not uniform. From memory, one of the post D-Day, direct from the US shipped armoured divisions came entirely equipped with M4A3(76) whilst most active M4A3 battalions could only dream of them.

105mm: Initially issued as a 3 tank platoon per tank battalion, later 1 was additionally added to each 17 tank M4-whatever company. So for 54 M4-? (75mm/76mm) tank battalion you could have 3 or 6 105mm M4/M4A3 in addition. They did not replace 75mm/76mm gun tanks. Production of M4A3(105) was roughly twice that of M4(105).

56° vs 47°: The early M4-? had 2″ at 56°, later upgraded (except M4A4) to 2.5″ at 47°. While almost the same effective horizontal line of sight thickness the 47° hull was a single plate without the driver/assistant driver hatch excrescences of the earlier 56° hull multi plate front, thus stronger. The 47° hulls also had bigger hatches allowing easier bail out.

As an addition to the above information I might as well complete the US battalion organisation by mentioning the light tanks and other lesser creatures.

A typical US battalion

The original OoB had a tank regiment with 1×3 company light tank battalion and 2×3 company medium battalions, each with 17 tanks/company and 3 in battalion HQ. The Battalion HQ had a 3 vehicle assault gun platoon and often a 3 vehicular 81mm halftrack MTR platoon. The assault gun platoon started with the likes of the T30 HMC (USVN 35), then the M8 HMC Scott (USVN 43) and finally by mid-late ’44 the M4(105) or M4A3(105) (USVN 17). The MTR platoon used the M4, M4A1 and M21 halftracks. That organisation was in effect until mid-late ’43 and indeed the 2nd, 3rd Armoured continued to use that “heavy” organisation until war’s end. In practice light and medium companies were often swapped to give 3 equal battalions with 1 light and 2 medium companies. A US “heavy” Armoured Division had 6 light and 12 medium companies total in 2 regiments. During ’43 the heavy organisation was replaced by the light version. That abolished the tank regiment and instead had 3 tank battalions. Each battalion had a similar HQ and 1 light and 3 medium tank companies, like before with 17 or 18 tanks for a divisional total of 3 light and 9 medium companies. The upside was the infantry component got beefed up at battalion level.

The light tanks started with M3 and M3A1 but by Sicily they started to or had been replaced by M5 and M5A1. By Wacht am Rhein tiny numbers of M24 had appeared but took some time to displace the M5A1s.

Now be aware that all the above is just an overall broad sweep picture. For designing scenarios always use AARs, TO&E unit details where you can lay your hands on them. You will undoubtedly find exceptions but the above should not lead you too far astray.

Paul M. Weir

(Note: I added the counter art, any error’s all mine.)

PS For more on Shermans, Witchbottles recommends the article “Wheels of Democracy” by Jeff Petraska from Avalon Hill Game Magazine vol 25 issue 3