![]() |
General script file layoutBreaking the script into blocksA script file is arranged so that certain types of information can be grouped together into sections or blocks. Three tags are used to identify these major blocks of information: [SETUP], [MACROS] and [CONFIG]. A [VERSION] tag also is available to notify the ThrustMapper and other ThrustMaster software of the version of the software used to create the script.A matching [END] tag is needed with each [SETUP], [MACROS] and [CONFIG] block tags that occurs in a script file. A preface area also is available prior to the block tags.
General file format
Preface areaThe area above the block tags typically is used for any commentary that isn't suitable for the [SETUP] block. The preface by default is treated as part of a [CONFIG] block, even though it is not labeled as such. Comment statements must be used here (/* */ or //).
[SETUP] blockThe optional [SETUP] block is for documenting game setup information. The text under [SETUP] can include the name and revison number of the game the script was written for, the name of the author, and any procedures, helps or hints the author wishes to include.The [SETUP] section is treated as one large comment block, so comment statements (/**/ or //) are not needed. Sample script file with a [SETUP] block
[MACROS] blockMacros are a way to store portions of control assignments outside the [CONFIG] section. The use of macros in a script file is mostly a matter of organizational style, as the use of macros has no affect on the control's performance. The [MACROS] block is optional, and may be excluded from a script file.See a script file without macros
[CONFIG] blockThe [CONFIG] block is really where the overall operation of the control in a game is defined in a script file. In this section, you can:
![]() |