Closed leftiness closed 8 years ago
Walls as edges might be something that's not handled in hex_math. Am I going to have something like Plane<Hex>
where Hex { point: Point, other: Property }
in hex_math? I think not. This hex_math would just be provided with arguments like startingPoint: Point
and invalidPoints: HashSet<Point>
.
Well, maybe it would be part of hex_math. Otherwise, would I provide a cant_go_northwest_from_these: HashSet<Point>
? That kind of information is needed for fov, pathfinding, flooding...
Confirmed. #2 blocks #1, #3, #6.
Duplicated in #30.
TLDR
Walls could be stored as edges instead of full hexagon points.
Notes
By using an extra property (and perhaps a separate
HashSet<Wall>
), walls could be stored as edges instead of full hexagon points. This would impact calculations like field of view and pathfinding.Resources