Matrix Games Forums

"... but you'll understand that we don't yet have games for Antietam and Chancellorsville, so your point is somewhat in the future subjunctive."

I just love the fact that you mentioned both Antietam and Chancellorsville! You just raised our hopes by a multiple of ten.

As for "Future Subjunctive" ??? ha!

(I had to look it up to learn - courtesy Wikipedia - that it's a rarely seen or used form in "certain dialects of Spanish and in formal speech." The example given,

Phrases expressing the subjunctive in a future period normally employ the present subjunctive. For example: "I hope that it will rain tomorrow" would simply be "Espero que llueva mañana" (where llueva is the third-person singular present subjunctive of llover, "to rain").

So, not only do those of us who study / play ACW simulations have the chance to learn a bit here and there about military history, we also get pro bono (publico) Spanish lessons to boot. [8D]

FOW doesn't need to be extreme, just reasonable. Major improvements can be made to BAB with a minimum of software changes. Just not providing so much information to the player about the other side unless the units are in "physical" contact (adjacent) and even then you shouldn't know as much as we know about the unit. Randomizing the numbers reported for things like strength would also create some FOW.

Right now there are apparently three FOW types in BAB. You know everything about the enemy unit, you can't even see the enemy unit but you have some idea its out there because of the "X"'s, or you see a "?".

The "?" type needs to be dropped as now implemented because it is useless. It only occurs due to some command leader failure but since the units the turn before were probably displayed in their normal detail as FOW it just works for people with poor memories.

I would like to see any unit that isn't in combat range but can be seen displayed as a "?". Maybe selecting the hex would display more detail based on distance and other factors with some randomization of numbers thrown in. This probably wouldn't require a major software change and could be included in an update.