Purpose

This Appendix index page is a master Table of Contents page for reference material relocated into Trainz Wikibook Appendix pages.

If you wish to contribute to clarifying the obtuseness of the N3V wiki, see Talk:Trainz/refs for guidelines or to post a question.

Main Data Types (KINDS)

The TOC for Containers and subcontainer topic pages is at containers.

All the below Child Classes are considered to have the TrainzBaseSpec (TrainzBaseSpec) as their Parent Class of data. Note: This list is 'wikified' on the N3V TrainzOnline Wiki, meaning the first letter has been capitalized after the word 'KIND', whereas actual data tag names in config.txt files are all lower case text.

• Here on the Wikibook, we are making our articles faithful in case to the actual keyword's case, that is lowercase, no capitalization. That wiki also uses double quotes in quite a few terms, a practice which we'll spare you from experiencing herein. This eases searching for terms and lessens confusion.
• The column evaluations, Importance and Frequency are blended evaluations weighted for the new Trainzer faced with the necessity of fixing assets to expand on Built-In assets and tap into the hundreds of thousands of Trainz assets available on the over 500 fan sites and the Trainz Download Station websites.
• The numeric weighted evaluation columns are explained below the following table.

Legend::

1. The higher the IMP figure (rated 0-10) the earlier a user should become familiar with the KIND. Part of the adjustment/rating is how often said KIND will be found as the subject of faulty content. Conversely, the lower the factor, the more specialized knowledge of it becomes, making it most important only to those doing advanced content creation. Such low numbers are both less frequent generally and less troublesome to those trying to use older content—which will always have utility off the tracks a few dozens of feet where less detail is tolerable and high definition is unneeded and indeed likely to have an adverse impact on framerates and rendering.
2. The frequency factor (range:0–9 is directly determined by the experience from fixing over 2,000 faulty assets of what KINDs one most often sees with faults which need correction.
3. The hyperlink in square braces (e.g. [14]) following each internal link accesses directly the matching page of the N3V Wiki enabling easy comparison and checks for updates. In general, the page topic herein will have better examples and a more robust explanations and background knowledge.

References TOC

General knowledge topics and appendices index

References TOC notations

By Column labels indent and/or indicate:  • 'R'=reference pages, usually data or data type article pages, Set off Parent and Child types with 'P' and 'C' when it makes sense, indent the child under 'S' and so forth.or  • 'G' for general or guidelines  • S is an amplifying sub-topic or data sub-type (defined-D or enumerated='E "Tags") such as a container in a container, while  • E is amplifying Examples or a sub-sub-data type, child types excluding those of config.txt INI files and it's TrainzBaseSpec should be listed under their parents in this table. If it gets cluttered, we can make a second alphabetical table later. By enumerated types, means tag values are predefined allowed values like category-region or category-class, versus defined type tags such as category-era entries.

See also

• Check out related changes to see what the state of this book is.

See also

• Trainz Asset KIND
• Trainz Config Container
• Check out related changes to see what the state of this book is.