Difference between revisions of "Action2"
Planetmaker (talk | contribs) m (finally... heading sizes) |
m (Beautify wiki markup) |
||
| Line 5: | Line 5: | ||
Action 2 is used to group sets of sprites from the previous [[Action1|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3. |
Action 2 is used to group sets of sprites from the previous [[Action1|action 1]] together, and make them accessible by a variational or random action2 (chain) or an action3. |
||
| − | ==Syntax== |
+ | == Syntax == |
In general, the data looks as follows: |
In general, the data looks as follows: |
||
| Line 31: | Line 31: | ||
|} |
|} |
||
| − | ==Descriptions== |
+ | == Descriptions == |
| − | ===Sprite-number=== |
+ | === Sprite-number === |
This is just the number you are at. |
This is just the number you are at. |
||
| − | ===Length=== |
+ | === Length === |
Count the number of bytes in this action. |
Count the number of bytes in this action. |
||
| − | ===feature=== |
+ | === feature === |
This sets the type of feature that you wish to change. Set it to: |
This sets the type of feature that you wish to change. Set it to: |
||
| Line 71: | Line 71: | ||
10 for rail types (since OpenTTD r19056) |
10 for rail types (since OpenTTD r19056) |
||
| − | ===set-id=== |
+ | === set-id === |
| − | This defines the ID of the current action 2. |
+ | This defines the ID of the current action 2. This ID will later be referred to by [[Action3|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. |
You can reuse action 2 IDs, and there's no restriction on the order in which they are defined. |
||
| − | ===num-ent1, num-ent2=== |
+ | === 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. |
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=== |
+ | === 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. |
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=== |
+ | === Notes === |
Do not skip an action 2 using [[Action9|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 [[Action3|action 3]] instead. Skipping an action 2 with an [[Action7|action 7]] has no effect. |
Do not skip an action 2 using [[Action9|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 [[Action3|action 3]] instead. Skipping an action 2 with an [[Action7|action 7]] has no effect. |
||
| − | ===Feature specific formats=== |
+ | === Feature specific formats === |
Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu) |
Some features and/or num-ent1 values have a special format. These are detailed on their separate pages (see main menu) |
||
Revision as of 14:47, 15 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:
00 for trains
01 for road vehicles
02 for ships
03 for planes
04 for stations
05 for canals/rivers
06 for bridges
07 for houses
09 for industry tiles
0A for industries
0B for cargos
0F for objects
10 for rail types (since OpenTTD r19056)
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)
