mapeditor / mapeditor/tiled

Make "file not found" behavior more source control friendly

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

@djad04 is already working on this.

Since Feb 6, 2026.

  • #4318 by @djad04 — open
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.**
Every time an open file is deleted or moved, Tiled pops up a dialog that requires user interaction to resolve, like this:
![image](https://github.com/user-attachments/assets/a4f63d20-a238-4a2e-a989-c69c01ad2106)

This gets very frustrating very quickly when you have a lot of maps open and you're working with source control. I use git, and I'm often moving between branches or commits, stashing and un-stashing changes, etc., and there's a constant cacophony of error dialog sounds from Tiled and an ever increasing stack of dialogs like the one above I have to press "OK" on before I can resume work after I'm done.

**Describe the solution you'd like**
I love the way Visual Studio Code deals with this situation. The open file gets a red color and a strikethrough on the open file tab, but otherwise nothing happens:
![image](https://github.com/user-attachments/assets/72c16651-e34a-4db7-86ed-8a67aa317238)
and if you bring the file back, it reloads it and goes back to showing it as a normal, open tab:
![image](https://github.com/user-attachments/assets/e9f111d2-c2f9-4dd1-b859-de19622e9b35)

If you happen to be editing the file and it is removed and restored *with different changes* since you started editing it, you will be notified of this only when attempting to save your new changes:
![image](https://github.com/user-attachments/assets/f87e0148-37ff-4481-953f-e7cbab4efb88)
and again, it's an important detail that this only shows up when the file being saved is *different* on disk than when the edit started. So even if you made a bunch of edits to the file behind the scenes, it'll still save just fine if the contents of it is back to what VSCode expects by the time you save, or if you deleted it.

**Describe alternatives you've considered**
Something that does work is closing all the maps before doing file operations as the editor only complains about rug pulls on open files. But it's easy to forget and a less friendly option when making on-going changes to multiple files that you like keeping open.

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 reproducing the issue with several open maps while moving or deleting files through source control, then inspect the existing file-not-found handling. No file or test is named in the issue; done means missing files no longer require repeated dialogs, tabs visibly indicate the missing state, restored files reload, and conflicting edits are reported when saving.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.