Open ilexp opened 5 years ago
I want to work on this issue but I am having trouble understanding what the intended behaviour of the autotiles are. I read #249 and #281 and have been testing it using Duality but I am still not fully understanding how it is supposed to function. From what I have seen, it seems that it is supposed to ease tile editing by automatically detecting where things like center or edge blocks would be, and then changing the actual shown texture based on that. Is there a ticket where it shows what the tileset editor UI looks like for a certain use case? Barring that, would the size of the AutoTile be essentially the smallest rectangle that encompasses all of the painted tiles in the tileset editor for a given AutoTile?
Are you familiar with the Tilemaps core and editor plugins from a user perspective, e.g. have you built a few maps with them and explored the existing Tileset features? I'm not sure I fully understood your question, but it sounds like it you might need a little more context.
This is how AutoTiles work right now. You can see it in action in the Tilemaps sample from the package manager.
Let me know if you need more info - or if I missed your point!
Thanks for the reply. The GIF was very helpful in understanding what the use case is. I assume this feature makes sense because users will usually have their tilesets structured such that the autotiles are directly adjacent and in the same format as one another. I suppose it's not a difficult task to structure them that way if you so desire, or to clear the automatically generated autotile if they are not.
Summary
Right now, every AutoTile in a Tileset has to be configured manually, even if its AutoTiles are laid out regularly in a grid. When creating a new AutoTile, it could copy and offset the previous items config to avoid repetitive work.
Analysis
IsAutoTile
andNeighbours
from the previous tile to the new one.