Terrain and terrain definition file
Posted: Sat Nov 07, 2015 10:00 am
If u plan to design a terrain tile, or tileset you should take these in consideration
(this is a list that will be expanded with ideas we face during development)
Terrain tileset file
- image tileset size should be always a power of two in both horizontal and vertical dimensions independently (examples: 128x128, 128x256, 256x256, 128x512, 512x512, 1024x1024, 1024x128)
- transparent png
Terrain definition json
- the all_terrain.json tiles "tilesetposition" value starts from 0, so first tile is on position 0
- if a tile got an ID than it must not be changed ever, it would cause major problems on maps made by these tiles.
- a tile (tileID) that is on the terrain_decor layer, than later we must not change it to be in terrain layer (and vica versa) because any map was designed by users using that tile might have major problems.
(this is a list that will be expanded with ideas we face during development)
Terrain tileset file
- image tileset size should be always a power of two in both horizontal and vertical dimensions independently (examples: 128x128, 128x256, 256x256, 128x512, 512x512, 1024x1024, 1024x128)
- transparent png
Terrain definition json
- the all_terrain.json tiles "tilesetposition" value starts from 0, so first tile is on position 0
- if a tile got an ID than it must not be changed ever, it would cause major problems on maps made by these tiles.
- a tile (tileID) that is on the terrain_decor layer, than later we must not change it to be in terrain layer (and vica versa) because any map was designed by users using that tile might have major problems.