-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it easier to set up terrain #1729
Comments
The only thing that was done regarding this issue is that you can now only remove single markings. It would still be nice, to improve the behavior when dragging while marking edges, as well as to be able to copy patterns across multiple tiles. |
Being able to copy terrains across tilesets would also be helpful. For example, this tileset and this tileset are very similar, it would be great to be able to copy+paste the terrains from one to the other and just change the terrain set and terrain names. Being able to select a group of tiles and have Tiled remap the colours in them would also be great for when you make mistakes. For example, say I have 4 terrain colours and I got two of them backwards on a subset of the tiles. I'd like to be able to select those tiles, replace all of Color 1 with Color 4 (let's say I'm not otherwise using that one on the tiles, so it's just a placeholder), then replace all of Color 2 with Color 1, and replace Color 4 (our placeholder) with Color 2. On mixed terrains especially, it can be easy to make mistakes like this, and it's punishing to fix them. Being able to copy terrains within a tileset and replace colours in them would be great for labelling tilesets like the examples above, where the tiles follow specific layouts and only the colours differ. Edit: In 2022 I wrote a script for copy+pasting terrains: https://github.com/eishiya/tiled-scripts/blob/main/CopyPasteTerrains.js |
Feedback from @therahedwig:
Hopefully @Bdtrotte will still find some time to continue working on this, and otherwise I shall need to have a look before the 1.1 release.
The text was updated successfully, but these errors were encountered: