[ASLML] Dominant Terrain Type Question
Sam Belcher
sambelcher at cablespeed.com
Sat Mar 6 22:47:54 PST 2004
OK, They aren't all up there yet, but many of these are now posted on
http://dicetower.com/PerrySez/operation_watchtower.htm
Take a look and tell my what you think.
Perry, if you can, take a look and let me know if any of these are wrong.
Sam
> -----Original Message-----
> From: David Reenstra [mailto:vaslplayer at triad.rr.com]
> Sent: Saturday, March 06, 2004 8:53 PM
> To: 'Sam Belcher'; bprobst at netspace.net.au;
> perrycocke at comcast.net; Aslml at asl-forums.net
> Subject: RE: [ASLML] Dominant Terrain Type Question
>
>
> Hi Sam (and other interested parties),
>
> Since I started this, I guess I need to follow through on it.
>
> I also have both versions of the map, but it never occurred
> to me to check v1 to see if it clarifies some of the
> questionable hexes.
>
> Now that I compare the two side by side, I see that there are
> indeed many differences. On the v1 map, I don't see too many
> hexes where the dominant terrain type is really ambiguous.
> Let's start there. Following are a list of hexes that, on
> the v2 map, have some ambiguity (I've tried to be
> comprehensive since others stated that they have never seen
> the earlier version of the map):
>
> A1, A4, B1, B11, B15, B19, D4, D5, D6, D15, E18, F4, F17, H8,
> I14, I17, J14, J15, M20, N6, P21, P25, P26, Q11, Q12, Q22,
> Q25, R11, R21, R26, S22, S26, T9, T14, T15, T18, V10, V12,
> W20, X20, Y15, AA20, AA21, BB10, BB18, CC8, CC9, CC11, CC12,
> DD7, DD8, EE6, EE8, GG12, HH18, II8, II9, II18, JJ9, KK13,
> MM1, MM16, NN12, OO11, OO12, OO15, OO21, PP15, RR10, RR16, SS18, SS25
>
> On the v1 map, almost every one of the above hexes has the
> dominant terrain extended to cover the hex center dot. There
> are only three exceptions that I
> noted: F17, Q11, EE6 pretty much look the same between both
> versions. It would seem though, that the intention was for
> all these hexes to have the dominant terrain cover the center
> dot in order to comply with the rules.
>
> Still though, my other question remains unanswered, that of
> the ambiguous crest lines. Hexes such as M17, M18, N18, S14,
> U13, U14, and U15 still bug me. I have an unofficial list of
> clarifications that covers some, but not all of these. I
> guess I'm looking for a general rule of thumb. Take hex M17
> for example. The center dot is covered in jungle and there
> is a crest line visible to the right side at the top and
> bottom of the hex clear of the jungle. Are we to
> "extrapolate" that this crest line continues straight along
> and thus misses the center dot to the right, making this a
> level 0 hex? Or does having any part of a crest line
> depiction in a hex make it the higher of the two levels by default?
>
> The two issues seem to be at odds with one another. If you
> have a hex that contains both a crest line and some terrain
> other than open ground (or maybe orchard/palm), the terrain
> needs to cover the center dot to comply with the existing
> rules. But if the center dot is covered, it raises an issue
> of where the crest line goes.
>
> Dave Reenstra
>
> >
> >
> >> On Wed, 03 Mar 2004 22:46:10 +0000, perrycocke at comcast.net wrote:
> >>
> >> >We didn't discover until after the original maps were throw
> >> away that
> >> >when
> >> >re-printing the map the printer had used an old file from
> >> before we had cleaned
> >> >up the ambiguities. Ouch.
> >
> >And Bruce Probst wrote:
> >
> >> So, someone who has both versions of the map should be able to
> >> resolve ambiguities on the second map by looking at the
> first map?
> >> Cool.
> >
> >I have both maps. If someone will send me a list of hexes that are
> >problematic, I'll publish a list based on the original map.
> >
> >
>
More information about the Aslml
mailing list