Karl Ostmo 936b30d22a extensible terrain (#1775) ... Closes #1641 The `data/terrain.yaml` file is now the authoritative source of terrains, though `BlankT` is still a hard-coded special case. I have not changed the underlying integer representation of terrain in the world function, which means that the `terrainIndexByName` Map in the `TerrainMap` record is needed for translating between `Int` and `TerrainType`. # Demo scripts/play.sh -i data/scenarios/Testing/1775-custom-terrain.yaml  # Changes * There used to be a function called `integrateScenarioEntities` that combined the `EntityMap` stored in the `Scenario` record with the global entity map. However, the global entity map is accessible at parse time of the `Scenario`, so we do the combining there and only ever store the combined map in the `Scenario` record. * JSON Schema for terrain * Removed the distinction between "World" attributes and "Terrain" attributes * Unit tests for scenario-defined terrain and related validations * Validate existence of referenced terrain at scenario parse time * Validate attributes referenced by terrains at parse time		2024-02-29 06:22:21 +00:00
..
doc	extensible terrain (#1775)	2024-02-29 06:22:21 +00:00
scene	preview rendered world with inotify (#1756)	2024-01-31 19:23:43 +00:00
Swarm	Remove Benchmark dependence on AppState and TUI (#1746)	2024-01-26 17:56:39 +00:00
Main.hs	extract scene renderer to its own binary (#1752)	2024-01-29 18:01:56 +00:00