Difference between revisions of "Action2"
(→feature: put all features in a table) |
(update feature table) |
||
| Line 41: | Line 41: | ||
Count the number of bytes in this action. |
Count the number of bytes in this action. |
||
| − | === |
+ | === Feature === |
| − | This sets the type of feature that you wish to change. Set it to: |
+ | This sets the type of [[Features|feature]] that you wish to change. Set it to: |
| − | {| |
+ | {|- | |
| − | !Value!!Feature |
+ | !Value!![[Features|Feature]] |
|- |
|- |
||
| + | |00||[[Action2/Vehicles | Trains]] |
||
| − | |00 || trains |
||
|- |
|- |
||
| + | |01||[[Action2/Vehicles | Road Vehicles]] |
||
| − | |01 || road vehicles |
||
|- |
|- |
||
| + | |02||[[Action2/Vehicles | Ships]] |
||
| − | |02 || ships |
||
|- |
|- |
||
| + | |03||[[Action2/Vehicles | Aircraft]] |
||
| − | |03 || planes |
||
|- |
|- |
||
| + | |04||[[Action2/Stations | Stations]] |
||
| − | |04 || stations |
||
|- |
|- |
||
| + | |05||[[Action2/Single_Set | Canals/Rivers]] |
||
| − | |05 || canals/rivers |
||
|- |
|- |
||
| + | |07||[[Action2/Sprite_Layout | Houses]] (special Sprite Layout format) |
||
| − | |06 || bridges |
||
|- |
|- |
||
| + | |09||[[Action2/Sprite_Layout | Industry Tiles]] (special Sprite Layout format) |
||
| − | |07 || houses |
||
|- |
|- |
||
| + | |0A||[[Action2/Industries | Industries]] (special Production Callback format) |
||
| − | |09 || industry tiles |
||
|- |
|- |
||
| + | |0B||[[Action2/Single_Set | Cargos]] |
||
| − | |0A || industries |
||
|- |
|- |
||
| + | |0C||[[Action2/Only_Callback_Failure | Sound Effects]] (callback failure only) |
||
| − | |0B || cargos |
||
|- |
|- |
||
| + | |0D||[[Action2/Single_Set | Airports]] |
||
| − | |0D || airports (OpenTTD r19204) |
||
|- |
|- |
||
| + | |0E||[[Action2/Only_Callback_Failure | Signals]] (callback failure only) |
||
| − | |0F || objects |
||
|- |
|- |
||
| + | |0F||[[Action2/Sprite_Layout | Objects]] (special Sprite Layout format) |
||
| − | |10 || rail types (OpenTTD r19056) |
||
|- |
|- |
||
| + | |10||[[Action2/Single_Set | Railtypes]] |
||
| − | |11 || airport tiles (OpenTTD r19204) |
||
| + | |- |
||
| + | |11||[[Action2/Sprite_Layout | Airport Tiles]] (special Sprite Layout format) |
||
|} |
|} |
||
Revision as of 21:32, 21 June 2011
Introduction
Defining graphics set IDs.
Action 2 is used to group sets of sprites from the previous action 1 together, and make them accessible by a variational or random action2 (chain) or an action3.
Syntax
In general, the data looks as follows:
<Sprite-number> * <Length> 02 <feature> <set-id> <num-ent1> <num-ent2> <entries...>
| Element | Size | Description |
|---|---|---|
| <Sprite-number> | dec | A sequential sprite number |
| <length> | dec | The total number of bytes used in this action |
| 02 | B | Defines action 02 |
| <feature> | B | For what type of feature should the following sprites be used? |
| <set-id> | B | What set-ID this action 2 defines |
| <num-ent1> | B | First number of entries, depends on feature |
| <num-ent2> | B | Second number of entries, depends on feature |
| <entries...> | W | Entry numbers, depends on the feature |
Descriptions
Sprite-number
This is just the number you are at.
Length
Count the number of bytes in this action.
Feature
This sets the type of feature that you wish to change. Set it to:
| Value | Feature |
|---|---|
| 00 | Trains |
| 01 | Road Vehicles |
| 02 | Ships |
| 03 | Aircraft |
| 04 | Stations |
| 05 | Canals/Rivers |
| 07 | Houses (special Sprite Layout format) |
| 09 | Industry Tiles (special Sprite Layout format) |
| 0A | Industries (special Production Callback format) |
| 0B | Cargos |
| 0C | Sound Effects (callback failure only) |
| 0D | Airports |
| 0E | Signals (callback failure only) |
| 0F | Objects (special Sprite Layout format) |
| 10 | Railtypes |
| 11 | Airport Tiles (special Sprite Layout format) |
set-id
This defines the ID of the current action 2. This ID will later be referred to by action 3, or a variational/random action 2.
You can reuse action 2 IDs, and there's no restriction on the order in which they are defined.
num-ent1, num-ent2
Each feature has two different graphics ranges, but their exact meaning differs from feature to feature. For example, for vehicles, the first set is used while moving, and the second while loading/unloading in a station.
entries
This is the list of action 1 sets to use, first num-ent1 for the first range, then num-ent2 entries for the second range.
Notes
Do not skip an action 2 using action 9 (unless it skips the whole file). Action 2 must not be skipped by action 9 or the patch will most likely crash. Skip or modify action 3 instead. Skipping an action 2 with an action 7 has no effect.
Feature specific formats
Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu)
