Split tileset by kind of tile

[wjt]

Currently we have one big tileset, scenes/tileset.tres, which contains all the tiles used in the base game.

I wonder if we should split this up so that there is one tileset per "type" of layer: water, foam, bridge/shadow, grass/faded-grass/sand, cliffs, etc. Then it would be harder to accidentally place tiles in the wrong layer: you would only have the appropriate tiles for that layer in the toolbox.

[manuq]

Yes, as it is today it is very confusing and is easy to commit a mistake. Also the single tileset has all the terrains. And on top, the difference is hard to spot in pull requests because the tiles information is stored as binary inside a text file.

On the other side, it is flexible and I imagine the layers number growing if we do this. At least I would group grass/faded-grass/sand. Which I guess is what you mean by "type" of layer? In that case, 👍

[wjt]

Yes, I imagine:

• water
• foam (or maybe this should live with water?)
• cliff faces + clifftops
• grass + faded grass + sand + dirt - all surfaces that can sit on top of rock and each other
• bridges + bridge-shadows
• void

Stairs are currently part of cliffs - maybe that's OK but I think they should probably live separately.

[wjt]

I think I would also take the opportunity to only have a chroma-key void, not the static image void; then once all uses of tileset.tres have been switched over, we'll know it's safe to delete the static version.

[wjt]

We implemented this in:

• Split big TileSet into 6 smaller TileSets & update all scenes #1448