JWE -> RE: Experimental map data file with stacking limits (10/7/2011 4:04:08 PM)
|
quote:
ORIGINAL: JeffK In late Dec 41, still working without any probs, although I havent streched the stacking limits yet. Maybe PH will be under pressure soon. Importantly nothing else seems broken by the change. Question 1. Is the stacking limit a total for the hex or for each side? Question 2. I one side holds the hex and the base, does the competing side share the same limits or are they at the base stacking limit?? Very nice to get that input. Thank you. The new SLs for a hex work just like the stacking limits for Island Size. They are a total for the hex. There is no bonus for the hex including a base. A hex SL is a hex SL. The presence of a base in a hex provides an extrinsic benefit to the side holding the base, even if the hex is 'overstacked'. The primary effects of overstacking are increased fatigue, disruption and greatly increased supply consumption (for both sides). The owner of a base has access to any supply stockpiles at the base and has the ability to use the base as a supply reception point (from ships if base is a port; from planes if base is an airfield). The attacker must rely on the overland supply flow model, or continuous amphib resupply TFs. [ed] quick note, there's a default routine that Michael put in place that ensures Very Small Islands have the nominal 6,000 troop SL, no matter what the algorithm says that hex type "should" have. So looking at certain hexes with Dave's new pwhexe editor can be a bit misleading. Always check the Island Size switch and if it's Very Small, the IS switch will control no matter what is in the SL field. Other (larger) Island Sizes don't go to default because the default values are darn close to the algorithm values so those are used instead.
|
|
|
|