Rather than stored as a property of a Tilemap, Tilesets should be distinct objects that can be independently passed across the network. This allows multiple tilemaps to use the same tileset without duplicate data, and allow for partial tilemaps such as chunks.
Tilesets should store the following information about every tile type:
Resource name
Collision
Pathing weight
Steps:
[x] Decouple TilesetData from TilemapData
[x] Implement pipeline for loading TilesetData and associating with Tilemaps
[x] Implement TilemapRequest and Tilemap packets
[ ] Implement client-side handling of decoupled data and loading
Rather than stored as a property of a Tilemap, Tilesets should be distinct objects that can be independently passed across the network. This allows multiple tilemaps to use the same tileset without duplicate data, and allow for partial tilemaps such as chunks.
Tilesets should store the following information about every tile type:
Steps: