mapeditor / mapeditor/tiled

Omit properties from export

Open
#3,830 0 comments 2 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 I'm exporting to a tmj/tmx file, the json is full of useless information, which the engine ignores

**Describe the solution you'd like**
a toggle near every property, which is stored in the project file, this toggle is on by default, toggling it off, makes it so that property is ommited from the exported file (.tmx/.tmj)

Some properties like the background color have a "Not Set" state, which has the same effect, this would not work for some properties like Fill Mode, which tiled needs to render the map, but my engine already knows about, so useless information for the engine, useful for tiled, it needs to be set.

**Describe alternatives you've considered**
- Simply ignore the properties, not ideal, the file is polluted with useless information
- Post process the file, what I do, but again, I'm still exporting and then removing the information, not ideal

Since there are workarounds, this is low priority, I just wanted to point out the "not ideal" state of the matter.

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

The issue does not name specific files or tests. Start by locating the TMJ/TMX export and property-serialization paths, then determine how per-property preferences would be stored and applied; done means disabled properties are omitted while required export properties remain present.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.