This post marks the start of my venture into converting Force on Force to use in WW2 battles. I'll post my thoughts and whatever work I do with converting the rules here, or in follow-on posts, mainly to collect my ideas in one place, but also so that anyone else who is working on the same idea may find it useful.
Why Force On Force? There are a few reasons I prefer these rules: first, and most importantly, it's very interactive. Everybody is making decisions all the time. You are never left sitting there, looking at the pretty pictures in a sourcebook for forty-five minutes while your opponent plays out his entire turn. Second, the rules are entirely scenario-based. There are no points lists, and winning the scenario depends entirely on achieving your (non-abstract) objectives. Third, it just feels right. Firefights are frantic, you have to constantly try to gauge your opponent's strategy and evolve your own, and everything you do matters. It's fine-grained enough that there's room for detailed planning if you want, but it never feels like it's bogging down into minutiae.
There are a few particulars in which the WW2 scenarios I want to play were quite different from the sorts of modern fights that FoF typically represents:
Larger Actions: WW2 was (mainly) a war between organized, uniformed armies. I can easily imagine a lot of situations where the insurgency rules from FoF would be useable (partisan actions, Stalingrad, Berlin '45), but not in the battles I'll be fighting.
Command and Control: The impression I get from reading books on the subject is that soldiers were much less independent in WW2 than they are in modern armies. I'll use the command rules for Irregulars in my games for everyone, where a unit that does not have line of sight to a command figure must make a TQ check to activate. Teams will be exempt. Tokens (see below) will make the TQ test at +1 to the roll.
Weapons: The difference in weapons technology is actually the easiest change to deal with. In WW2, a man with a rifle is the basic 1FP unit, and other weapons and organizations will be extrapolated from there. I have come up with some stats for the support weapons in my first scenario (PIAT, panzerfaust, 2" mortar, etc.) which will appear in the unit's stat block when I publish it.
Vehicles and Armor: I have taken the stats for the tanks I'll be using in this first scenario from a list compiled by a user on the Ambush Alley forums here. (Registration is required to access the .pdf)
Fog Of War: One thing I think is missing from FoF is a proper fog-of-war system. This gets away somewhat from the FoF philosophy that the scenario represents the action once the engagement proper has already begun, ie shooting has started, but I want to have some maneuver/recon component in my game as well.
There are a lot of ways of achieving this, but the one I like best is using unit tokens. I have some color-coded, flocked poker chips I used as blinds in I Ain't Been Shot Mum, and I'll be using them in FoF for the same purpose. With tokens you have to have some sort of spotting system in place, so here's mine:
Spotting may only be done as a reaction, not an action. Identifying a token requires a successful TQ check using the TQ of a standard soldier of the force. Tokens may spot tokens. The following modifiers apply to the spot check:
spotter elevated: +1
spotter under fire: -1
target in cover/obscured: -1
target in building / prepared camo: -2
target within optimum range: +1
low light: -1target in optimum range and in the open*: automatic
target fires: automatic
*this can be at any point during the target's turn, even if they are only in the open briefly, such as when crossing a road.
Each force will have one token per section, team, or vehicle. Several 'dummy' tokens will be included in each force's setup also.
More To Come
So that's the current state of my rule adjustments for WW2 Force On Force. I'm sure I will have other thoughts, especially after I play my first test game tonight, with a scenario I have created. I will publish a report and the scenario itself here sometime soon.