Open frantisekhanzlikbl opened 3 years ago
The general idea was to have a single texture atlas, much like other tilemap implementations. Adds quite a whole other layer if its pulling from multiple. I can make that more explicitly clear.
I absolutely agree that it's a good thing that a single tilemap can only have one texture atlas, I just think that as a user it's hard to find out that I am supposed to use multiple tilemaps for that purpose
FWIW I'm trying to integrate ldtk and this is sort of an issue since each layer can have its own tileset. Honestly most asset collections I've seen out there aren't all combined onto a single sheet either, so I'd have to edit all my tiles together to a single atlas to use this.
I am going to explore the possibility of actually getting this in.
What problem does this solve or what need does it fill?
As a new user of the library it was not clear if it is possible to have multiple texture atlasses at all, and while #7 indicates that users are supposed to solve this by using multiple tilemaps, that issue is not super easy to find.
Describe the solution would you like?
A note in the readme or somewhere else visible feels like the easiest and clearest way to inform the users how to achieve this.
Describe the alternative(s) you've considered?
Adding a note to some other place, like a wiki if this project gets one.
Additional context
none