Getting Started in TrainzScript
From TrainzOnline
(Difference between revisions)
m (1 revision) |
(→Creating and Editing Scripts, Tools to Use) |
||
| Line 1: | Line 1: | ||
| − | == | + | ==Script Usage== |
* In TRS2004 and later, scripts can be used to make objects perform operations in reaction to events. For example a level crossing (grade crossing) can be made to operate as a train approaches it. | * In TRS2004 and later, scripts can be used to make objects perform operations in reaction to events. For example a level crossing (grade crossing) can be made to operate as a train approaches it. | ||
| Line 5: | Line 5: | ||
* In TRS2004 and later, driver commands are written as scripts, and these can also be included in Driver sessions so as to give train drivers a series of operations to perform. | * In TRS2004 and later, driver commands are written as scripts, and these can also be included in Driver sessions so as to give train drivers a series of operations to perform. | ||
* In TRS2004, scenarios (interactive activities) are written as scripts. This functionality was removed in TRS2006 and later although by various complex means it can be emulated to a limited extent. | * In TRS2004, scenarios (interactive activities) are written as scripts. This functionality was removed in TRS2006 and later although by various complex means it can be emulated to a limited extent. | ||
| + | |||
| + | ==Creating and Editing Scripts, Tools to Use== | ||
| + | |||
* Trainz scripts need to be included in your asset folder as plain text files. | * Trainz scripts need to be included in your asset folder as plain text files. | ||
* Any errors in the script, including spelling or syntax errors, won't be flagged up until you load a map which uses your asset or when you first place your asset on a map. | * Any errors in the script, including spelling or syntax errors, won't be flagged up until you load a map which uses your asset or when you first place your asset on a map. | ||
Revision as of 16:41, 12 February 2010
Script Usage
- In TRS2004 and later, scripts can be used to make objects perform operations in reaction to events. For example a level crossing (grade crossing) can be made to operate as a train approaches it.
- In TRS2004 and later, rules are written as scripts, and these rules can be included in Driver sessions, effectively as the session's program elements.
- In TRS2004 and later, driver commands are written as scripts, and these can also be included in Driver sessions so as to give train drivers a series of operations to perform.
- In TRS2004, scenarios (interactive activities) are written as scripts. This functionality was removed in TRS2006 and later although by various complex means it can be emulated to a limited extent.
Creating and Editing Scripts, Tools to Use
- Trainz scripts need to be included in your asset folder as plain text files.
- Any errors in the script, including spelling or syntax errors, won't be flagged up until you load a map which uses your asset or when you first place your asset on a map.
- Although you can use Notepad to create and edit files and commit them directly to the game, it will quickly become frustrating having to run TRS to find that you have missed out a semicolon or closing quote.
- TRS includes a command line compiler called gsc.exe, at C:\Program Files\Auran\TRS####\Bin\, which can be used to check script syntax, this won't guarantee that your script will work but it will guarantee that TRS will accept it as valid.
- Editors which will help you to ensure that your scripts are correctly formatted are freely available, one such is Context and details of how to obtain it and set it up for Trainz are included at this page: Using Context with Trainzscript. Another such program is TextPad (http://www.textpad.com).
Tutorials
The following are links to various tutorial pages available for TrainzScript:
For Beginners:
A set of tutorials by Andi Smith which will take you through the steps involved in setting up a simple script on a scenery asset, starting with the traditional 'Hello World' and ending with the use of a Property Interface to deal with basic effects, including animation, sounds and texture replacement. The tutorials largely avoid object-oriented terms such as encapulation, inheritance and polymorphism, and instead try to concentrate on getting your scripts working as quickly and painlessly as possible.
- Hello World, Setting Up An Asset Script.
- Getting Information From the Game, Writing Your Own Methods.
- Talking to Yourself, Sending Messages.
- Saving and Restoring Data, Using Properties.
- Setting Up the Asset.
- Automating Animations.
- Handling Corona Effects.
- Playing Sounds.
- Hiding Meshes.
- Handling Name Effects.
- Texture Replacement.
