Monday, February 19, 2018

Arena on GitHub

"Arena" is a Java code package I've developed over the years to simulate combat in Original D&D and generate statistics on the results. We've used it to look at level-based demographics, assess monster metrics, generate bands of men in the wilderness, and lots more.

Recently I placed all that code in a GitHub Repository, so if you're a coder, hopefully this a more convenient way to access, inspect, verify, download, run, and fork that package if you have any inclination.

Features added in the past few months that are new there: (1) Treasure generation by random methods (for both dungeons and wilderness: see DungeonTreasureTable and MonsterTreasureTable), whereas previously treasure XP was added based on pre-calculated averages. (2) Party-based combat in the Arena, so we can simulate groups of adventurers in a dungeon together (in Arena, see command switch -z), whereas previously it was solo encounters only. (3) Encounter table generation in the dungeon, based on Equivalent Hit Dice values (see EHDToTables). In future posts we'll look at some observations gleaned from these added features.

Also recently I put the up-to-date version of the OED Monster Database, used in conjunction with that software, up on the OED Games website. Recent modifications are changes to Equivalent Hit Dice (EHD) values for about a half-dozen monsters (as a result of new data from the software), and an addition of an "Env" column, which is 1 if the monster appears in the dungeon environment (used for the automatic encounter table generation). Again, hopefully the website is a convenient location at which to access that resource.

Monday, February 12, 2018

Sarge's Advice: Book of War Q&A

Some months ago (actually, a whole lot of months ago) Jarrett Perdue wrote to me with a number of good questions that arose from playing the Book of War fantasy miniatures supplement (see sidebar) with his daughter. This seemed like a really good opportunity to start a FAQ-like response list, so here it is. Hopefully it's useful/helpful. Here's our exchange:

First off, thank you for your willingness to field a few questions on Book of War.  I really appreciate how you've brought OD&D and wargaming back together in this product (Battlesystem was cool, but never felt like D&D to me).  My daughter and I have enjoyed the three games we've played since my copy of the book arrived.  The following are all situations that arose in those couple matches:

1. Who chooses which models to lay down (and later remove) as casualties, the attacker or defender?

The current book says all losses come from the back rank ("Formation", para. 2, p. 8), so there's usually little choice. In case of dispute I let the defender flip them over.

2. Are casualties ALWAYS removed from the back ranks of a unit or from the ranks farthest from the unit inflicting the casualties? (e.g. a unit being assaulted from behind)

I do actually go with the back rank all the time. I think this simulates men crowding forward, and getting wiped out more completely when attacked in the rear.

3. What happens when a unit takes enough casualties to cause it to no longer have contact with an enemy unit?

This happened twice in our recent game.  In one case a unit with many files (one rank) entered combat with a very small unit (4 files, two ranks) and suffered enough casualties that every model touching the enemy was lost. In the same match a unit flanked front and rear lost its entire rear rank due to casualties, leaving a "gap" between it and the rear attacker.

Does combat end (the units touching corner-to corner) or is the attacker simply moved forward to re-engage as a sort of bonus move?

The attacker certainly gets the benefit of all their allowed attacks in the current turn (i.e., however many hits accrued from the figures touching when combat was resolved). As the turn then goes to the next player, this may make some slight extra room for them to escape, if desired. In most cases the attacker will be able to close the distance on their next turn and continuing attacking, if they wish (which bears on the next question).

4. When a unit fails a morale check does it get a "free" about face or does it have to await its own turn and pay the regular cost for this maneuver (1/2 move) before moving away from the enemy that routed it?

If the latter is the case, doesn't that mean that routing units can almost always be overtaken by pursuers? (not that this is a bad thing of course)

There's no free movement. The routing unit does indeed have to wait until their normal move turn before about-facing and moving away. Yes, in the majority of cases the attacker can then run them over the backside on their next turn. Generally only light cavalry have the capacity to make the about-face and get far enough away to avoid follow-up attacks.

(I should point out that in current play here, we've actually removed the recovery-from-rout rule to the optional rules section; in default play there's no recovery, and so attackers generally just let them rout of the table and turn their attention elsewhere. See also question #14 below.)

5. When squaring up during an attack, does the attacker shift to match the defender's position or vice versa?

On contact the attacker (that is, the player moving at the time) should rotate forward in the normal fashion to meet the defender along a common line segment. That's not to say that the unit sideways-scrapes to get more contact surface. The basic idea is that units don't contact at just a point/vertex.

6. How do you resolve this when the squaring up adjustment carries the unit into contact with additional enemy units?

I've got to say, I don't recall this happening in a game. Since everyone only move forwards, I think the only way this could occur is for A to meet B at a corner, and somehow have C in the tiny "wedge" space in between. If that ever happened I'd engage "a long unit can be bent along its major axis" and wrap around both B and C as flush as possible.

7. Casualties from missile fire are also removed from the back of the unit first, true (even if the farthest archer couldn't actually reach the rear rank of the enemy unit)?

Yes. The idiom is that men are falling at the front, and other men are stepping forward to fill the ranks automatically. (See #10 below for a related point.)

8. What do you perceive to be the relative costs in points/gold for various attributes?  For example, skeletons would not break morale, regardless of losses.  We discovered that to be very impactful on the battlefield of course.  How should I weight the point value appropriately if I wanted to play a balanced match?

You're right that morale is probably the key mechanism by which games are won, lost, and become dramatic. Undead being morale-free is an advantage; but at least in OD&D they're also very slow (6") which offsets this. E.g., I've found normal skeletons to be balanced at 4 gold, the same as regular light infantry. That said, in playtests, undead force a very long/slow-paced game (has a "chalky" taste to me), where you just have to slowly smash them all down without respite from morale. I kind of recommend not having big undead battles of you can avoid it. See blog links:

9. How about the point values of movement, hit dice, and AH?

I definitely recommend against trying to price out individual attributes. As game design, that always breaks down, and you've got to consider each unit holistically. You might search for the phrase "acid test" on the blog here. (See more about this topic in a future post.)

10. No firing into woods, true?  What if a unit is only partially in the woods (left flank exposed)?

Right, no firing into woods. As written, if even part of one figure of a unit is sticking out, then that unit can be targeted normally. (At times I've considered an optional rule wherein a unit can be flush inside the edge of a wood, fire out normally, and get a +1 armor bonus on incoming fire; feel free to play with that if it sounds like a good idea.)

11. When turning (wheeling) are terrain costs counted as well as the cost of 1" per file for turns between 45 and 90 degrees?  For example, a cavalry unit wheeling in the woods pays double terrain plus the number of inches that it has files ... or the number of files it has times terrain cost x2 (since it is cav)?  Sort of an order of operations question :)

Right, wheeling has normal terrain cost applied to it; so e.g. cavalry wheeling through woods is number of files ×2. The foundational idea here is that the "wheeling" cost is just a shortcut for the normal distance moved on the table; if you get out a bendable ruler or string and measure the outside movement, then you'll find that it approximately matches up. (E.g., 3 figures each 3/4" wide through a quarter-circle has arclength 3 × 3/4" × τ/4 = 3.5").

12. Are terrain costs paid from the front of the unit?  For example, a unit five ranks deep is in the woods, 1" from the edge.  It advances an inch (at a cost of 2") then a second inch (at a cost of 1") before halting.  The rear two ranks are still in the woods, but when the unit moves next turn it doesn't pay any additional terrain costs, true?

Yes, move costs are only from the front of the unit. Once the lead rank gets out of the woods, everyone behind them catches up "for free". That's obviously a rough simplification for gameplay purposes. (Maybe that's a weak point that needs fixing? But I don't recall it being a major issue in the past. Arguably if the front line does anything "interesting" like engage in combat, then the back ranks would have time to catch up and join them.)

13.Can you launch arrows OUT of the woods?

No arrows shot out of woods. See #10 above for an optional rule that I sometimes imagine.

14. Pg 9, para 6 says, "At the end of a turn in which it [a routed unit] avoids any loss, a unit may attempt another Morale check to recover from the routed status..."  Since a unit can only take losses on its opponent's turn, is that what is being referred to here (the normal morale check phase rolled at the end of the enemy's turn, or is this referring to something else? A separate morale check made at the end of a unit's own movement for instance?)

Right, this recovery-morale check happens at the end of the enemy's turn, at the same time the same player in question is making morale checks for all their units who did take losses. (There are times when I consider making "morale checks" the start of the turn sequence, so that everything in the turn is being decided/rolled by one player in question. However, I like getting that over and sweeping dead figures off the board before the end of the turn. See also #4 above that in our current play we've actually removed the recovery rule from the basic play.)

15. A unit of skeletons was attacked both from the front and upon the right flank by two separate enemy units. The skeleton model on the front, right corner found itself in contact with two separate enemy models. The player would have to choose, as an entire unit, which enemy unit to attack on the skeleton turn, true?

If a unit is in contact with multiple enemy units, I do let the individual attacking figures make attacks against whichever unit they're contacting. For example: unit A in contact with enemies B and C; some figures of A will be attacking B, and others C, determined by direct base contact. If a single figure in A contacts both B and C (your corner case), then the attacking player gets to decide that particular figure's target.

16. In the same battle the skeletons, who were about four ranks deep, were simultaneously attacked from both front and rear. In this case could the skeletons, on their own attack phase, attack the enemy units both to their front AND their rear (at a -1) or would they have to choose between the two? If the answer is the former, what does that imply for the hedgehog formation? Does it merely prevent the -1 penalty?

To return attacks, figures do have to face their enemy; I always allow this changing-face for a unit on their turn who's already in combat. So when a unit gets hit from both front & rear, on their next turn they usually about-face outward ("hedgehog", effectively), and then get normal attacks with the units in contact on each side. (I don't think there's ever a ─1 for attacks; the idea being you're either facing/attacking someone, or not-facing/not-attacking at all. Of course, there is the +1 to hit if you're attacking a unit in the backside.)

Thursday, February 8, 2018

D&D Physics Lab: Falling

At the start of the week we revisited the (to some) infamous dueling articles in The Dragon #88 by Parker and Winter: principally, should damage from falling be proportional (a linear function) to speed (and thus the square root of height), or instead to kinetic energy (and thus to height itself)? The physics theory seems clear: work is a linear function of energy, not speed. But we would not be scientists if we never put such things to the test.


The experiment here is inspired by a teacher's guide for high school students: see Jones, "Understanding Car Crashes: It's Basic Physics", Insurance Institute for Highway Safety (2000). The goal of that experiment, "Lesson 2: Momentum Bashing" (p. 5-10) was to verify that momentum is a linear function of mass; here we modify it to check on the relation between fall height (or maybe speed) and work done.

The basic setup is to have some kind of track, one end raised on one or more books, with a ball rolling down into a catch-container. Jones' version used a marble, a ruler with a center groove, and a paper cup with a catch-hole cut in one side. I went looking for those things in my house and found I had none of them. So instead I scrounged up: a bouncy superball, a 15" cylindrical mailing tube, and an empty onion dip container with a hole cut out of it. Conveniently, the mailing tube was almost the same diameter as the ball; of course, if you want to try something similar, any replacement materials are fine.

For elevating one end of the track I used my stack of Conan paperback books. Fortunately, the books are all approximately the same width: 1/2" each. So where the track models the gravity of a falling body (angled tracks being a common means for "slowing down" a fall so we can observe it more closely), each added book will smoothly model an additional "floor" of the falling body. I ran the test ten times each with elevation heights of 1, 2, and 3 books. The distance that the catch-container gets pushed forward by the ball at the end is marked and measured with a millimeter ruler, and serves as a proxy for "work done" on the falling body at the end. See picture of apparatus below.


Results of all testing are shown in the chart below, along with a linear regression on mean displacement of the catch-container at each height of fall. For all practical purposes, this proves to be a perfect correlation: the relationship is exactly D = 38h (where D is catch-container displacement in mm, and h height of fall in books), and the 3 data points match a straight line through the origin with R^2 = 99.9994% precision. I wish that any of my high school lab experiments had come out this accurately; I might have gone into a different profession!


Our experimental observations exactly match the physics theory; work done by a falling body is proportional to the height of the fall. In the old D&D falling debate, this again confirms Steve Winters' argument that "kinetic energy is the key", and that damage should indeed be a linear function of the fall height (not the speed, i.e., square root of height, as argued by Parker).

Monday, February 5, 2018

Falling Revisted

The Dragon #88 (August 1984) had an infamous set of articles on the physics of falling damage. Some fans of the game maintain that this investigation of math and physics is unnecessary to a fantasy game. However, I’m on the other side of this argument; if there must be some base rule for a mundane activity like falling, then I see no reason not to “dial it in” correctly. Surely there’s no disadvantage to the parties who claim to simply not care one way or the other. Hence, I consider these articles to possibly be the very zenith of D&D system scholarship as it could be practiced.

Dragon #88: Parker vs. Winter

The issue in question appeared in the context of the OD&D and AD&D book rule that falls do a linear 1d6 per 10 feet; and a recent article and update in UA in which Gygax claimed this was a typo, and should have been a far more brutal 1d6 cumulative per 10 feet (e.g., 3d6 at 20’ and so forth). One of the Dragon #88 articles is by A.A. Parker on “Physics and Falling Damage”, arguing that damage should be proportional to velocity, and thus more violent at the start, but scaling down somewhat with greater height (e.g., starts at 3d6+1-5 for a 10’ fall; reaches 20d6 with a 260’ fall). The other article in that issue was by Steve Winter called “Kinetic energy is they key”, whose conclusion is that kinetic energy, and thus damage, is linear with height – thus arriving back at the 1d6/10’ rule we started with.

Let’s look a little more closely at the argument with the advantage of time. Interestingly – something I tend to forget – is that Parker was apparently conscious of Winter’s following rebuttal, and spends several paragraphs and a sketch (above) addressing the kinetic energy argument, and ultimately rejecting it (p. 14-15). But his culminating argument is fairly weak:
No physical law exists that says kinetic energy is the direct cause of physical injury. We know that there is some relationship between the two – because the more kinetic energy a person transfers to the earth, the greater his injuries are. But no law states that this relationship is linear, or that all the factors involved in kinetic energy relate to the injury. It may be, then, that some part of kinetic energy relates linearly to falling damage. Since no formula exists to tell us what part this might be, we have to use our intuition to determine the crucial property.
At best, all of Parker's counters here are equally applicable to his own velocity-based thesis. But worse: there is in fact a physical law which effectively asserts what he claims is missing, and it’s called the “work-energy principle”: per Wikipedia, “the work done by all forces acting on a particle (the work of the resultant force) equals the change in the kinetic energy of the particle”. Assuming a body goes from some initial velocity to a full stop, then the work on the body is exactly equal to the kinetic energy, given by KE = ½ mv^2. (where m is the mass of the body, and v the velocity). So we see that work done is not proportional to velocity as Parker argued; it is proportional to the square of the velocity, and hence directly proportional to energy, as Winter asserted.

Collision Model Data

Consider this from a different perspective: It’s now easy to access data sources such as those used to model pedestrian injuries and fatalities from auto accidents (a fairly good analog to a body hitting solid ground at high speed). See Richards, “Relationship between Speed and Risk of Fatal Injury: Pedestrians and Car Occupants”, Department for Transport, London (2010). Data for pedestrian fatalities, mapped against auto speed, follow a characteristic sigmoid curve. Several proposals for model formulas for probability of death are given; the simplest, by Rosen and Sander is: P = 1/(1 + e^(6.9 – 0.090v)), where v is the automobile’s velocity, and P is the probability of a fatality (p. 14). Below we attempt a linear regression against speed itself (as a test of Parker’s theory), and also speed^2 (proportional to kinetic energy, as a test of Winter’s theory).

Taking probability of death as proportional to damage to the body, then it’s rather obvious visually that the better fit belongs to the speed^2, i.e., kinetic energy measurement. The coefficient of discrimination to this fit is R^2 = 0.977, that is, kinetic energy serves to explain 97.7% of the variation in mortality asserted by the model.

Interestingly, the auto-collision industry uses a mathematical model for estimating speed from observed damage, called CRASH (Computer Reconstruction of Automobile Speeds on the Highway) which explicitly takes as a first assumption that depth of crush is a linear function of velocity (or momentum). However, at least one presenter admits that this is an approximate model only: see McHenry, “The Algorithms of CRASH”, McHenry Software, 2001 (p. 19-20):
Combined assumptions of (a) linearity of ΔV_c (i.e., the  ΔV preceding restitution) as a function of residual crush and (b) a  ΔV_c intercept near 5 MPH, at which no residual damage occurs, have served as the basis for extrapolations outside the range of available test data... The use of linear relationships may be viewed as a simple empirical process for interpolation and extrapolation of the results of staged collisions... it appears that bilinear fits might yield more accurate application results when a large ΔV range is included in the fitted data.

Terminal Velocity

Many editions of D&D (starting with the AD&D PHB, p. 105) have a rule capping fall damage at 20d6, and often times this is taken as a simulation of terminal velocity of a falling man (as in the Parker & Winter articles). One problem arises, however: in the core rule this occurs after a 200’ fall, when in reality terminal velocity of a falling person isn’t reached until much later. Compare also to Carl Sargent's revised falling rules in PC2 Top Ballista (1989, p. 61), in which he is clearly looking at real-world speed/distance of falls, and greatly reduces damage to have the 20d6 max occur at real terminal velocity.

Terminal velocity for a falling man in a stable, belly-down position is around 120 mph, or about 180 feet/sec (Wikipedia). Due to the asymptotic nature of gravity vs. wind resistance, a person only reaches 50% of this speed after 3 seconds or so (about 140 feet), 90% of terminal at 8 seconds (800 feet), 99% of terminal at 15 seconds (over 1500 feet), and so forth (in a theoretical sense, one never actually reaches the terminal speed; it's only a limit). See the excellent chart by Green Harbor Publications, 2010; to my eye, the “inflection point” in the graph is at around a 6-second, 500-foot fall, at which velocity is about 80% of terminal. In core D&D terms, this would argue for max falling damage of around 50d6 or something like that.

Let's compute for more specificity on that point. For simplicity, I define a new energy unit, the footman force, as one man × ft^2/sec^2 (compare to the foot-pound force). As a preliminary, we compute the speed from a 10' fall, assuming that for such a short height, air resistance is negligible: sqrt(10)/4 × 32 = 25 ft/sec. This allows us to compute the kinetic energy from the 10' fall: KE = 1/2 mv^2 = 1/2 (1 man)(25 ft/sec)^2 = 312 footman forces. On the other end of the continuum, where air resistance is total, we are told that terminal falling velocity is about 180 ft/sec; and in this case the kinetic energy is KE = 1/2 (1 man)(180 ft/sec)^2 = 16,200 footman forces. The ratio between these two energy amounts is 16,200/312 = 51.9; that is, very nearly 50 times the energy (and we would argue, damage) between a 10' fall and one at terminal velocity. 

Again, the calculations above are shortened a bit by assuming the mass (m) of the falling body is simply "one man". It could be an important point to observe that smaller creatures will generate less energy (damage) from a fall, and larger creatures more. Wikipedia quotes the biologist J.B.S. Haldane as writing:
To the mouse and any smaller animal [gravity] presents practically no dangers. You can drop a mouse down a thousand-yard mine shaft; and, on arriving at the bottom, it gets a slight shock and walks away. A rat is killed, a man is broken, a horse splashes. For the resistance presented to movement by the air is proportional to the surface of the moving object.
That said, we ignore this detail at the present time and consider a rule only for approximately man-sized creatures.

Falling Mortality

The real-world statistics of falling mortality are expressed in terms of “median lethal distance” (LD50), that is, the distance at which a fall will kill 50% of victims (who are presumably normal adults). Smith, Trauma Anesthesia, p. 3, asserts that LD50 is around 50 feet (4 stories). Wikipedia asserts that LD50 for children is at a similar height; 40-50 feet (one might think that children are less durable than adults, but note the observation on size/mass and damage above). Dickinson, et. al., in “Falls From Height: Injury and Mortality” (Journal of the Royal Army Medical Corps, 2013) notes that LD50 varies greatly by injury type: about 10.5m (34 feet) for those who land on their head or chest; about 22.4m (73 feet) for those who do not. (To me, this fact argues that falls should get some kind of binary saving throw, possibly save-vs-stone for half damage? And recall that the first falling rule in OD&D Vol-3 indeed gave a saving throw using a different mechanic.)

So: Around 50 feet kills about 50% of human victims. Note that this is actually much more generous than the standard D&D rule, which in its simplest form will kill about half of normal men with just a 10’ fall (1d6 damage vs. 1d6 hit points). It broadly contradicts Gygax’s advice in OD&D Vol-3, p. 6 (“there is no question that a player's character could easily be killed by falling into a pit thirty feet deep”). To say nothing of Gygax’s intuition at the time of UA that such damage should be massively upgraded with a cumulative rule.

Considered Rule Edits

Here we consider a few rule edits based on the mortality data seen above. Among the rules edits considered are:
  • A save-vs-death at zero hit points; this has been the existing OED house rule for some time (recently edited so that any "overkill" damage becomes a penalty to the save). If you like, consider this to be broadly analogous to permitting negative hit points before death.
  • A save-vs-stone for half damage; this is inspired by the medical findings that there is a binary difference in mortality depending on whether a victim hits their head/chest or not (specifically, almost exactly a 50% change in LD50 mortality).
  • Possibly reducing the damage dice to something like 1d6 per 20 feet.
If we consider such changes, we need to keep an eye on the overall effect at both low and high levels. A simulation in Java code was run for the event of falling 50', for each of the proposed edits, for characters of varying levels (trials N = 10,000 for each case). Results are shown below (highlights at around 50% mortality):

On the one hand, the basic D&D rule is unrealistically harsh: 1st level characters (and normal men) have 100% mortality from a 50' fall. Even if we engage any one of our cushioning rules, then it is 3rd-level characters who have around a 50% mortality rate (as shown in the first chart).

But on the other hand,  if we do calibrate the system so that 1st-level characters have a 50% mortality rate (as in the real world), then that requires engaging all of our proposed edits -- reduced base damage, a save for half, and a save vs. death at zero hit points (as shown in the second chart). And then as a result, any higher-level characters have effectively negligible chances of perishing from a fall of that height (further down the same column).

Let's take a case study from the pulp literature: in the short story "The Scarlet Citadel", Howard relates a scene in which Conan grapples the sinister and powerful Prince Arpello and hurls him from a 150' high tower, upon which, "the body came hurtling down, to smash on the marble pave, spattering blood and brains, and lie crushed in its splintered armor, like a mangled beetle" (Ch. 4). If we assume this worthy is a 9th-level Lord (he's described as a capable fighter, a veteran of many campaigns), then we can re-run the simulation at this greater height. If we use the latter fully-cushioned rule proposal, then mortality from this fall would only be 2% -- clearly unacceptable. If we keep the 1d6/10' rule but allow the two saves, chance of death would be 35%; with just the half-damage save 43% (I think both of those are still too soft); with just the existing OED save-vs-death mortality is 72%, which feels about right (no saves at all would give 85% mortality).


In summary: Calibrating the rule so that normal men have a real-world LD50 at 50' requires a rule so generous that it completely violates our intuition and literary examples for higher-level characters falling from truly stupendous heights. The best we can do is massage something acceptable in the middle. And it turns out that the classic 1d6/10' damage, with a single save of some sort (like: OED save-vs-death, or some negative hit point allowance) does give a vaguely reasonable result around 3rd level or so. Considering that this effectively requires no modification to our existing ruleset, it seems like living with this is among the best options.

It also seems like a recurrent theme that many parts of the D&D system are most "realistically calibrated" for characters of around 3rd level; perhaps this gives extra support for starting campaigns at around that level (as Gygax did in later years; see ENWorld Q&A thread, date 11/19/04). See also: Environmental Rule of Three. I'm comfortable with existing OED save-vs-death at zero hit point representing the variation in whether the victim lands on their head/chest or not. And I think I'm now compelled to bump up the maximum fall damage to 50d6 to reflect true terminal velocity (which neatly takes care of the need for extra saves-vs-massive damage or the like, since everyone up to a lesser god gets equally pancaked from arbitrarily high falls).

Open question: In pulp heroic literature what other examples of survivable falls do we see for figures like Conan, Fafhrd, Elric, etc.? Perhaps we could use that to “dial in” the rule better, if necessary.

Thursday, February 1, 2018

Book of War on the DM's Handbook Podcast

Friend of the blog, Michael "chgowiz" Shorten has a regular podcast called "Dungeon Master's Handbook". In his most recent episode he shares a really nice overview of the history of trying to incorporate mass-warfare rules into D&D games: including Chainmail, Swords & Spells, Battlesystem, War Machine, and so forth.

Just like me, he spent years struggling with them and finding all of them deficient in some way to what we really wanted (the primary weakness to TSR offerings being: rules that are simply out-of-sync with D&D mechanics and results, and likely too abstract and complex to boot). He uses the name "Holy Grail" for the problem of finding a system which is: (1) mechanically compatible with D&D, (2) easy to interface D&D monsters and characters into mass battle, (3) simple enough to easily introduce to RPG'ers who are not expert wargamers, and (4) fun to play.

And he concludes by calling our product, Original Edition Delta: Book of War (see sidebar) the best solution to that problem, using such complimentary words as, "an amazing solution", "worked wonderfully", and "it's all there". Of course, it's exactly these same motivations that had me tinkering for a couple decades or so to find the right, streamlined system -- so I couldn't be more honored to know that it works as a solution to other thoughtful gamers out there.

Chgowiz has consistently given great feedback on the game by email and blog comments here, too. He authored the supplement called "The Fellowship" which allows lower-level PCs to function on the battlefield as joint party-based figure -- he talks about his experiences with that in the podcast, and we wrote about it earlier here. All of his output is highly recommended. If you're not aware of the legacy of mass-combat rules orbiting around D&D, this is a great place to start!