Purpose

This Appendix index page is a master Table of Contents page for reference material located only here in the Trainz Wikibook Pages. The cloned Official Reference pages with Added details is a separate TOC page.

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

One key expansion we will be having here are Route Tech Manuals, including:

1. an author's guide to both historical reasons he invested so much time and effort into the Trainz kind map,
2. a Driver's View Guided Tour, and perhaps most importantly;
3. a detailed list of places and features about likely, possibly, or historic operations on the map written with the point of view (i.e. thinking in depth) about what sorts of things 'another person' would like to know as well (as he, the Creator, does) for writing a session.

Both the latter guides are to let the most people take advantage of the map, with the most fun. There are several advantages of an online map tech manual:

1. Firstly, it's online and available by any communications device with a browser--hence multiple head computers, a nearby laptop or Pad computer or smart phone can access data while in the middle of running Surveyor, or Driver.
2. With an external List of Sessions, each can be added to an index listing Sessions on the Route's Map on the DLS without any need for reusing or over using naming terms. When used, this index will support locating sessions for the maps Creator. While newer Trainz releases allow for longer names in menus and there were no limits to those in surveyor, there are even in TANE no way to check dependent assets that may reside on the DLS—especially those put up by a 3rd party, now that we have the trird Windows release with layers.

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.

References TOC

Notice

See also

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

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 references Ini files and it's references 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.