Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Automapping: Added a "StrictEmpty" flag to input layers
In "StrictEmpty" mode, empty tiles in the input region match empty tiles in the set layer. So when an "input" layer contains an empty tile within the input region, this means an empty tile is allowed at that location. And when an "inputnot" layer contains an empty tile within the input region, it means an empty tile is not allowed at that location. Without the "StrictEmpty" option, when no "input" layer specifies any tile for a given location, and no "inputnot" layers exist, any tile that isn't used elsewhere on any input layer is considered valid. Also, when an "inputnot" layer contains an empty tile, it is simply ignored. This behavior can be convenient, but it is not always desired. The "StrictEmpty" mode can be enabled per input layer by adding a custom boolean property named "StrictEmpty" with the value "true". See also the following discussion on the forum: http://discourse.mapeditor.org/t/automapping-check-for-empty-tile/965
- Loading branch information
Showing
3 changed files
with
104 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters