From: Brett L. <wak...@ea...> - 2005-09-23 23:20:50
|
> 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. I agree. My point was, it's probably better to specify a hexside as impassible rather than a path from one hex to another. The difference is semantic, but I think it's a vital one. In terms of XML, the difference would be having this: <hex A1> <impassable sides="1,2,3"> </hex> versus <hex C1> <impassable hex="D2"> </hex> <hex D2> <impassable hex="C1"> </hex> That way, in the code, we make the calculation of "if your side X or your neighbor's corresponding side Y is impassible..." We're going to need to be working with examining hexsides and neighbor hexes when we do route calculation anyway, so this would be a good first step building the foundation for that. What do you think? ---Brett. |