Open DragonDePlatino opened 8 years ago
The CSV export was meant to be a rather simple format, suitable only when a single tileset is used and supporting a "name" tile property for changing what each tile is exported as (instead of their index in the tileset). In fact it was added because somebody wanted to import his maps into Excel.
Of course, there could be an option to add these flags, but the way I see it you could also just use the TMX or JSON formats with "CSV" tile layer data and get almost the same thing and it's really not hard to extract it from there.
Finally, #949 is about making Tiled scriptable and as such also making it easier to write your own simple export script for use-cases like this.
The problem is, I'm a very inexperienced programmer so I barely know how to parse pure CSV files...I've considered getting an XML-parsing library, but I'd like to reduce my number of dependencies. I've even tried pasting the map data into the CSV file myself but it won't load properly even though it looks the same as the CSV.
If we could create our own export scripts, that would be great! I'll definitely be keeping my eye on that.
I've been using Tiled to develop a roguelike and I recently added support for loading flipped tiles. If the 32nd bit of a tile is set (e.g. tile 4 becomes tile 2147483652) then I flip the tile horizontally when rendering it. This is exactly how the .tmx format handles flipping and it streamlines the process of porting maps into my game.
Unfortunately, exported .csv files do not have this functionality. A tile with an ID of 4 will remain 4 even if flipped or rotated. To solve this, could we have some configurable options in the Plugins tab? Alternatively, a "Conserve tile flipping on export" option in the General tab?