Automapping: Ignore empty outputs per-rule #3894
Conversation
This change introduces a "compileOutputSet" step which is executed as part of collecting the rules. In this step, each rule only receives as possible outputs the output indexes that are non-empty for the region of that rule. This makes it much easier to add output variation to only some of the rules. Previously, due to the possibility of empty outputs being chosen, having rules with various amounts of variation required setting up separate rule maps. Closes mapeditor#3523
|
It looks like MatchType Ignore is counted as "no tile" for the purposes of determining whether a given output layer contains anything in a region. Ignore should be the main way that users specify a deliberately empty output (Empty is not sufficient, since that outputs Empty, which is not the same as "output nothing"). I think only literally empty regions should count as empty. The presence of any tile, including any MatchType tile, should make the layer count as a valid output. |
Even if it doesn't actually place any tiles.
|
Suggested wording for the documentation of this change, perhaps it could be added to the last paragraph before "Random Output Example":
(And don't forget the Changelog too xP) |
|
Accidentally pushed to |
This change introduces a "compileOutputSet" step which is executed as part of collecting the rules. In this step, each rule only receives as possible outputs the output indexes that are non-empty for the region of that rule.
This makes it much easier to add output variation to only some of the rules. Previously, due to the possibility of empty outputs being chosen, having rules with various amounts of variation required setting up separate rule maps.
Closes #3523