Incompatible tileset workflows?

It’s unintended in that, until 1.3, Aseprite wasn’t designed with tiles in mind at all. It only worked for tiles because tiles can be treated as a type of sprite.

I would say that a better workflow is already here (if you export your document instead of exporting a sprite sheet), it just has some flaws in that you don’t have as much control over exporting the tile sheet as you do when exporting sprite animations, due to missing an Export Tileset feature. Most people export their tilesets without spacing and margins though, so it should be just as good for them.

I posted a feature request asking for better tileset management and layers for tiles before here, and based on the answer from dacap there, it seems unlikely 1.3 will have these improvements, but they are planned for future versions.

I didn’t mention animation there because it’s already teeeechnically supported via frames. In Tiled and RPG Maker, tile animations are just different tiles being displayed in a given cell over time, and you can do the same thing in Aseprite by changing which tile is displayed in a cell in different frames, and when you export your tileset, those frames would all just be different tiles. However, automating this in Aseprite the same way it’s done in Tiled (defining a sequence of tiles to show in each instance of a given tile) would be a great time saver.