Froonp -> RE: Units, Scenarios, Options, and Add-ons (7/7/2005 12:18:49 PM)
|
quote:
ORIGINAL: Shannon V. OKeets I Add-ons I am pretty sure that the first version of MWIF will include most of the add-on modules with the exception of Days of Decision, Patton in Flames, and America in Flames. I realize there are some of you who would really like to have DoD included. If it were easy to do, I would. It isn’t. The DoD mechanics are quite distinct from WiF and would require writing many additional software routines to implement them. Please note that the sheer number of special rules is already enormous. Even excluding DoD there is a ton of rule specific programming involved. I think it would be valuable to include the counters of AiF, PatiF & PoliF to the game (making them optional would be ok). Only the counters, and the Heavy units rule from RAW7. I say this because I find that these units and this rule are a good addition to the regular 39-45 WiF Campaign. They help solving the "great fighter race" and the "ufo problem" even if playing with advance building, and allow even more flexibility for those who want it, by allowing upgrade of land units either on the field or in the construction pool / spiral. quote:
II Scenarios Those of you who have seen CWIF have seen what I envision as the scenarios: the 11 scenarios listed in the WiF Final Edition. [CWIF beta only had 3 of them set up.] As far as there is the grand 39-45 campaign (extendable to 46), Im happy :-) quote:
III Options I expect to include all the options listed in Rules as Written 7.0 (RaW 7) as game options. The only addition I am thinking about concerns fog of war. In CWIF fog of war means that all the enemy units are visible but for units that are not in the front line all you can see are their backs. This means that you can see that there is a fighter in a specific hex but you do not know which fighter. Is it worth creating a second level of fog of war? The second level would only let you see units in the front line. Any units behind the line would not be seen. This change poses several problems vis-a-vis WiF compatibility. For example, what about port attacks? Do you just send planes to a port hoping that there are targets there? How about strategic bombing? Would ground strikes be limited to only units in the front line? It’s possible to make all units within 2 hexes of an enemy corps visible, if that strikes you as a reasonable compromise. Maybe this whole idea should just be discarded? WiF does not have any rule for fow, and I think that such grand strategic wargame has no need for fow rules. The real life commanders we as players are supposed to be in the game had no fow problems at the scale of WiF. I mean that they knew where the other side's force were, even if they were not sure of the level of strength of the units, and this is already factored in the game through the dices. I mean that, ok you know that there is the 1 SS Panzerkorp in front of you, but it does not mean that it will be efficient, you can roll over it, or the reverse, depending of the result of the dices. Well, I'm not sure I explain things correctly, I'm french and I am at work... quote:
IV Units Right now CWIF has all the units included in RaW 7. In my naivete I think this is all that is needed. I am planning on allowing players to change the names of units during game play (thereby addressing the aggravation of the “USS Bearn”). I also expect to make the unit lists available offline - in a spreadsheet. Players can edit the unit lists before starting a game and then simply request their own hand tailored unit list when a game starts. I do not want to enable players to modify units (other than their names) during game play. You see, I have this complex about imposing parental authority at times so players can’t cheat. Those were included in CWiF (renaming, but not listing). CWiF also included a valuable feature who was : allowing the player to put a note on a unit, to help not forgetting why the unit was send here or there, or else. quote:
So do you have any thoughts about these subjects before I start writing code concerning them? That's all for the moment, need to work too :-)
|
|
|
|