Allow showing a list of tilesets in the Tilesets view
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
I often use lots and lots of tilesets in one map, and it starts to get difficult to navigate, especially if they have long names.
This often makes me sink time into workarounds, such as condensing multiple smaller tilesets (how most tilesets come) into one huge tileset, and naming my .tmx files very tiny names so I can see more tileset tabs (which can cause confusion later). I have to do these in virtually every project if I don't want to get lost in my tilesets.
In this brief video, I illustrate how this affects my workflow and talk about UI that would work vastly better for me:
Tiled - Feature Request - See all tileset names at once
To sum up the video:
Let's use layer navigation as an example. When working with layers, I can resize the layer area to see as many or as few layers at a time as I want, and even rearrange them into folders.
But there's none of that for tilesets, even though I may have as many (or more!) tilesets as I have layers. (This is true for many of my projects.)
This UI change could be a HUGE relief of a constant pain point for those who use a lot of tilesets.
And here, eishiya has mocked up how the UI could look, which I think is spot-on!
Further functionality I would add:
- (eishiya's idea) A way to visually signify which tilesets are used vs. unused inside the current project.
- Being able to reorganize the order of tilesets - essential, and something you can't do currently with tileset tabs.
- Having folders (expandable ones like layers have) - I would gratefully use this functionality in every project.

Thanks for reading, and I hope something like this can be implemented soon!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Tilesets view and compare its navigation with the layer area described in the issue. Review the linked video and mockup to understand the proposed list UI and its optional features; the issue does not define a settled scope or acceptance criteria for completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100