Tiled/Manual — German @ Hosted Weblate: Input Example

Zen

	English (Developer)	German	Actions
	The `input` layers define the pattern(s) of tiles that a rule will look for. These are Tile Layers, and their names must follow this scheme:
	After the first underscore there will be the name of the target input layer. For example, `input_Ground` will look for tiles on a layer called Ground. The input layer name can include more underscores, so `input_test_case` will look for tiles on a layer called test\_case. If the working map includes multiple layers by this name, the bottom-most one will be used. If the working map does not contain the named target layer, the rule checks against a dummy empty layer.
	The not is optional. If present, it inverts the layer's meaning, so instead of matching the tiles on the layer, Tiled will match anything but those tiles.
	The index is optional. Indices on `input` layers allow you to create rules that match any of several completely separate inputs. Any inputs with the same index are treated as part of the same condition, and each different index is its own independent set of conditions. Any of these conditions being matched will count as a match for the rule. An index can be empty, or it can be any string that doesn't start with `not` and doesn't contain any underscores.
	Multiple input layers having the same name and index is explicitly allowed and is intended. Having multiple input layers of the same name and index allows you to define different possible tiles per coordinate as input, and any combination of those tiles will count as a match.
	Input Example	Hier ist ein Beispiel:
	Let's say you want to match two-tile areas of the ground, perhaps to randomise them. You might want to match any combination of grass and flower tiles, but only whole two-tile rocks. You can achieve this like so:
	Tile Layer
	Name
	![Two grass tiles.](images/automapping/automap_input1.png)
	Two grass tiles.

Loading…

None

String updated in the repository

English (Developer)

German 22 characters edited Current translation Needs editing

a year ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Glossary

English (Developer)	German
No related strings found in the glossary.

String information

Source string location

../../manual/automapping.md:60

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

docs/locale/de/LC_MESSAGES/manual.po, string 30