|These pages are part of the of the Trainz Wikibook.
This Trainz Project category tracks Trainz 'Kinds' data definitions — reference articles which cover keywords defining 'types' of Trainz Assets and their associated data; all of which are declared and defined in asset's Trainz's config.txt ini files.
Category:Trainz Asset KIND is intended for article pages which describe KIND containers that are uniquely declared with one and only one legally occurring in every Trainz config.txt file. Further, any valid Trainz asset must have a legally and completely defined Kind data collection.
- The data structures listed are necessarily a mix of 2nd-level data tags and container keywords whereas ALL Kinds are considered a child of the TrainzBaseSpec.
- In practice the data defines required by a KIND declaration will be intermingled with the standard TBS keywords.
- The sister category Category:Trainz Config Container lists reference pages describing the defines-needs of various (subordinate Data types, 2nd and 3rd level—asset data structures in the Trainz software system). The KINDs container is a unique data type whilst containers are most often used by multiple KINDs as sub-containers when not part of the TrainzBaseSpec itself.