Skip to content
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

"Remove Unused Tilesets" export option #3855

Open
eishiya opened this issue Dec 8, 2023 · 0 comments
Open

"Remove Unused Tilesets" export option #3855

eishiya opened this issue Dec 8, 2023 · 0 comments
Labels
feature It's a feature, not a bug.

Comments

@eishiya
Copy link
Contributor

eishiya commented Dec 8, 2023

It is usually a waste of space and parsing effort to deal with unused Tilesets in production maps, but it may be useful to leave the references in the working files. To solve this issue, it would be great if Tiled had an export option that removed unused tilesets.

There's a script available to remove unused tilesets, but it doesn't fully solve the problem: it affects the working map as well, and Tiled scripting has no good way to only affect exports. The script could be modified to re-add the removed tilesets after the asset has been saved, but then the order of tilesets will be changed, and the order is important for some engines.

This was requested by mingw on Discord.
Well, more accurately, they requested that Tiled should (provide the option to) remove unused tilesets automatically when tiles are removed. I think in practice this would be quite annoying, so I think an export option is better. If a user actually wants tilesets removed from their working map, the script linked above can be used to automatically remove tilesets on save, which should be less annoying than doing so whenever tiles are erased/replaced.

@eishiya eishiya added the feature It's a feature, not a bug. label Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature It's a feature, not a bug.
Projects
None yet
Development

No branches or pull requests

1 participant