From: Erik V. <eri...@hc...> - 2005-09-23 22:46:36
|
> > 4. A tag or attribute to define impassable hexsides where > upgradeable hexes > > border each other (e.g. C11/D12 in 1830) should be added to Map.xml. > > Perhaps a tag like > > <Hex name="C11" ....> > > <NoGo name="D12"/> > > </Hex> > > > The thing we need to be careful with here is that most hexes > only have one or two sides that are impassable. Other hexes, > like water, are completely impassable from all sides. > > I think we should see if we can leverage the code related to > checking neighbor hexes that still exists from importing the > Colossus hex code. It'll be much easier to do this if we > can easily check the neighbors of each hex and examine the > shared hexside for properties that mark it as impassable. > > I think that it'll be easier to write code to check hexside 3 > of hex A1 with hexside 5 of hex C3 for impassable=true on > either hexside. Yes, if the hex has such properties (like the preprinted grey ones) or is on the border of the map, the impassability can be derived. I was referring to the cases were it cannot, such as the one I gave as an example. In those cases an extra specification is needed. No big deal. Erik. |