You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, tiles Features are implementing as an enum to represent the various types, and a connections field is provided on the few that touch the edges of the tiles (Roads, doesn't include all that are included in the base game. Specifically, we are missing:
A Feature of a Tile can touch zero, one, or more cardinal direction of the Tile. In the event it touches non, as in the case of a Monastery, it exists as a simple enum with no struct fields. However, in the case it does touch a direction, like a City, it contains a connections field which lists all the sides it touches.
The part of the above image is represented as follows:
Currently, tiles Features are implementing as an enum to represent the various types, and a
connections
field is provided on the few that touch the edges of the tiles (Roads, doesn't include all that are included in the base game. Specifically, we are missing:A
Feature
of aTile
can touch zero, one, or more cardinal direction of theTile
. In the event it touches non, as in the case of aMonastery
, it exists as a simple enum with no struct fields. However, in the case it does touch a direction, like aCity
, it contains aconnections
field which lists all the sides it touches.The part of the above image is represented as follows:
Note: roads that terminate in the centre are represented as only touching one
Direction
.The text was updated successfully, but these errors were encountered: