mapeditor / mapeditor/tiled

Allow pattern matching on automap input and output.

Open
#4,097 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
12.9k
Forks
2k
Avg merge
4h 27m
Merged PRs (30d)
8

Description

**Is your feature request related to a problem? Please describe.**
When working with Tiled, I design dungeons from a top-down perspective and have multiple levels / elevations by organizing the project into groups:
![bild](https://github.com/user-attachments/assets/fe2679bd-4d1e-4e28-a005-3768fbba2e4d)
Today I must edit the layer names of the input and corresponding output layer removing the trailing index number before I start automapping the dungeon layout. And then when I want to work on an other elevation, I need to re-add the indices and start the process over.

**Describe the solution you'd like**
If the automapping could be done with pattern matching like `input_in%d` and `output_out%d` so that edits to a layer called `in2` only outputs to `out2` would be really neat.

**Describe alternatives you've considered**
I've tried reading through the documentation and the issue backlog and haven't found any workaround besides the procedure I describe.
I noticed issue #428 is sort of similar, but I think, it is somewhat orthogonal.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Tiled's automapping implementation and the code or tests that handle input and output layer names. Trace how layer names are matched, then define completion as supporting patterns such as `in%d` and `out%d` so matching indices map to corresponding outputs without renaming layers.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.