Game.LambdaHack.Content.TileKind

The type of kinds of terrain tiles.

Documentation

data TileKind

The type of kinds of terrain tiles. See Tile.hs for explanation of the absence of a corresponding type Tile that would hold particular concrete tiles in the dungeon.

Constructors

TileKind

Fields

tsymbol :: !Char

map symbol

tname :: !Text

short description

tfreq :: !Freqs

frequency within groups

tcolor :: !Color

map color

tcolor2 :: !Color

map color when not in FOV

tfeature :: ![Feature]

properties

Instances

Show TileKind

data Speedup TileKind = TileSpeedup {

• isClearTab :: !Tab
• isLitTab :: !Tab
• isWalkableTab :: !Tab
• isPassableTab :: !Tab
• isDoorTab :: !Tab
• isSuspectTab :: !Tab
• isChangeableTab :: !Tab

}

validateTileKind :: [TileKind] -> [TileKind]

Filter a list of kinds, passing through only the incorrect ones, if any.

If tiles look the same on the map, the description and the substantial features should be the same, too. Otherwise, the player has to inspect manually all the tiles of that kind, or even experiment with them, to see if any is special. This would be tedious. Note that iiles may freely differ wrt dungeon generation, AI preferences, etc.

actionFeatures :: Bool -> TileKind -> IntSet

Features of tiles that differentiate them substantially from one another. By tile content validation condition, this means the player can tell such tile apart, and only looking at the map, not tile name. So if running uses this function, it won't stop at places that the player can't himself tell from other places, and so running does not confer any advantages, except UI convenience. Hashes are accurate enough for our purpose, given that we use arbitrary heuristics anyway.