Will do. Na zdravie!You don't say! Pass my greetings from shutdown Bratislava.
In a proper Slovak household indeed slivovica never stops flowing...
Correct.VotG CG Max notation 12.6216
CGIII. Russian RG type I2 as an example. CG Max shows 3 red dot / 2 brown dot.
The slash denotes the meaning of "and" - is that correct?
So 5 total RG's may be purchased in the campaign, 3 with entry code red dot , and 2 with entry code brown dot.
I believe the intention is that you can't have units (MMC) do any kindling but that any burnable terrain can be "started on fire" or "kindled" via other destructive methods. Example: OBA, FT, etc.Has this apparent contradiction been addressed/resolved:
VotG1. EC are Dry, with no wind at start. Kindling is NA.
V4.1 ...Rail Car hexes may be Kindled.
Thank you.
I don't think there's really a contradiction here. V4.1 is a terrain rule. SSR VotG1 is an SSR. Someone might design a scenario when SSR VotG1 is NA, but uses the Rail Car rules.Has this apparent contradiction been addressed/resolved:
VotG1. EC are Dry, with no wind at start. Kindling is NA.
V4.1 ...Rail Car hexes may be Kindled.
4.1 instructs placement of S? </= 2 hexes from a Frontline Location, which essentially means a 3 hex deep line, i.e., the Frontline Location, then 2 additional hexes (the Frontline Location is range 0). The all-out attack results in all S? at ground level become Advance Attitude (so all 3 hexes of the line); General Attack results in all S? at ground level in the front 2 hexes of the line now are Advance Attitude; Probing Attack each S? of the front 2 hexes of the line has to roll </=3 to become Advance Attitude.Not sure if this belongs in the Solitaire sub-forum, but it is directed at Tom Morin for an answer.
Question came up about Tom's SASL VotG rules, where the 20.4/4.1 S? Placement rules say that for an Attack chit, S? are placed less than/equal to 2 hex from each frontline location. Fair enough it seems. However in the sub-para ATTACKING ENEMY, two of the three types of attacks, ALL OUT ATTACK and GENERAL ATTACK appear to say the same thing, namely that all locations (i.e. 2 hexes or less from each frontline location) are switched to Advance Attitude. Is there an error somewhere, possibly in 4.1 where it should read less than/equal to 3 hexes, inclusive of the frontline? Or does the initial 4.1 statement not include the actual frontline location hex, but the two ones 'behind' it?
Hopefully Tom you can clarify.
View attachment 20839