Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+1)

FYI from what I read, a 47 tiles blob tileset is equivalent to a 256 tiles tileset, so you could probably optimize this

(+1)

Oops, didn't see this until now. While it's true that the smaller tileset is enough for most projects, I personally ran into issues that required the full set for some textures. For example, I had a forest and river tileset I was using for large map generation. It was important in this case to address some of the more niche adjacencies in order to make the resulting landscape look more natural. In any case, I often duplicate tiles that fit multiple adjacencies (usually by just using a reference in code), but I've definitely found that having the full set as a baseline makes random map generation go much more smoothly. 


Thanks for the comment, and I definitely recommend using a smaller tileset, especially if you plan to place them by hand instead of using proc gen. This template is also free to use if anybody comes across a use case for it like I did.

(Just a note: this isn't to argue and it isn't meant to be criticism, I'm just genuinely curious)

Based on what I read and my own testing, there isn't any tile configuration where the 47 tiles aren't enough, even when going through the 256 possible configurations. If you had an image that shows where you found it useful or necessary, I'd love to see it because it genuinely intrigues me