Squad Leader Series Scenarios Published by

Phil Grasha & Bill Gormley

• These scenarios were designed for played at COI level with use of COD terrain rules such as Orchards, Vineyards, etc. A brief and short description of these terrain features are listed within the SSR section of the scenario but the full rules are also listed below for aditional convienience.

• 118. ORCHARD

• 118.1 Any hex or half hex containing multiple dark green clusters is considered an orchard hex. An example of an orchard hex is 6F5. The term “orchard” is used to represent any wooded area without dense undergrowth.
  
• 118.2 The movement cost for entering an orchard hex is identical to that of Open Ground for all types of units.
  
• 118.3 Orchards have no terrain effect modifier of any kind. Therefore, target units moving through an orchard are not subject to the -2 defensive fire DRM for moving in the open. The TO HIT category for ordnance weapons firing at an orchard hex is “other”.
  
• 118.4 Orchard hexes do not block LOS or penetration except as listed below. They are not considered “woods” for any purpose.
  
• 118.41 Units on the same level as the orchard may not trace a LOS through more than two orchard hexes inclusive of the target hex. MG penetration may extend through more than 2 orchard hexes but in so doing is resolved as Area Fire. Remember, however, that MGs must have a LOS to a target (or suspected target) in order to fire. Keep in mind that the green clusters do not obstruct LOS, they merely identify the hex as an orchard hex.
  
• 118.42 The hex directly behind an orchard hex in direct LOS from a firing hex of higher elevation is considered a blind hex and cannot be fired upon during any scenario taking place during April through November.
  
• 118.5 The “kindling” (102.22) number of an orchard hex is 11+. The “Spread” (59.4) number is 9+.
  
• 118.6 Orchards do not cause breakdowns or present any movement hindrance to vehicles.
  
• 118.7 Broken units may rout through orchard hexes without being eliminated due to the presence of enemy units in LOS and normal range. An orchard hex is not suitable cover for a broken unit to end its rout in, although they could remain in such terrain until a possible route to a woods or building hex exists.
  
• 118.8 The allowable LOS through orchard hexes is increased from 2 hexes to 3 hexes during any scenario taking place during the December-March period.

taken from the VSQL4 module: HOLLOW LEGIONS 1st Edition

• 196.3 CACTUS HEDGE: A SSR may specify that wall/hedges are cactus hedges. All hedge rules apply to such hexsides - except that Infantry may cross one only during the MPh by expending all of their MF’s in the hex occupied prior to crossing the cactus hedge. Place a TI counter (-2 hazardous movement) on the units attempting to move across the cactus hedge. If the units are still in Good Order (ie not broken, locked in melee, etc) at the beginning of their next Movement phase, they may then remove the TI counter and again must spend all of their MF’s and cross the cactus hedge. Units crossing a cactus hedge may not carry more SW’s than their normal PP capacity allows them to. Cavalry, Horses, and Wagons may not cross a cactus hedge at all.

• 196.4 CACTUS PATCH: A SSR may specify that orchard hexes are cactus patch hexes instead. All orchard rules apply to such hexes, except that a cactus patch is a Half-Level Obstacle (thus affecting LOS just like rubble), has a +1 TEM, has Kindling and Spreading fire numbers of 12 and 10 respectively, its MF/MP costs are triple those of an orchard, and it is never out of season.

• 196.5 OLIVE GROVE: A SSR may specify that orchard hexes are olive grove hexes instead. All orchard rules apply to such hexes, except that an olive grove also has a +1 TEM, its MF/MP costs are double those of an orchard, and it is never out of season.

• 196.6 VINEYARD: A SSR may specify brush (or some other terrain) as being a vineyard. A vineyard hex is treated exactly the same as brush and a Bog hex. No boards contain these terrain features and must be placed on the board using the VSQL Terrain Overlays or Board Editor features.

• 196.7 PALM TREES: Same rules as Orchards. No boards contain these terrain features and must be placed on the board using the VSQL Terrain Overlays or Board Editor features. Will usually be found near an oasis, desert town/village, and less arid areas of the North African coastline.

• 196.8 INHERENT TERRAIN: Certain terrain depictions (i.e., orchard, crag, graveyard, shellholes, etc.) and counter contents of a hex (i.e., SMOKE, rubble, etc) [EXC: Bypass AFV/Wreck (COD 132)] identify the entire hex (exclusive of hexsides) as having the characteristics of that terrain type. It is not necessary that the LOS actually crosses such a symbol within the hex to be affected - the mere entrance of the hex (even if only to trace a LOS to or through a vertex of such a hex) [EXC: a LOS traced exactly along one of its hexsides does NOT suffice unless that LOS passes BETWEEN two such hexes containing Inherent Terrain]. A LOS traced exactly along such a hexside is considered to have passed through only one such hex - not two - if that hexside is shared by another LOS Hindrance hex (such as Smoke in two adjoining hexes in which the LOS passes between the two Smoke filled hexes). If the Hindrance DRM of two such hexes differs, the larger of the two DRM is used.