Action 2

Defining graphics set IDs.


Action 2 is used to group sets of sprites from the previous action 1 together to form a single unit for a single type of cargo.


In general, the data looks as follows:

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 vehicle/station should the following sprites be used?
<set-id>	B	What set number 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

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.


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.


Some features and/or num-ent1 values have a special format. These are detailed on the pages listed below.

• Action2Vehicles - Defining cargo IDs for vehicles
• Action2Stations - Defining station IDs
• Action2Canals - Defining an action2 for canals
• Action2HousesIndustryTiles - Defining an action 2 for houses, industry tiles and object
• Action2Industries - Defining the industry production callback
• Action2Cargos - Defining cargo IDs for cargos
• Action2Objects - Action 2 for Objects
• Action2Railtypes - Action 2 for Railtypes
• VariationalAction2 - Variational Action 2
  • VarAction2Advanced - Advanced features of Variational Action 2
  • VarAction2Vehicles - Variational Action 2 Variables for Vehicles
  • VarAction2Stations - Variational Action 2 Variables for Stations
  • VarAction2Cities - Variational Action 2 Variables for Cities
  • VarAction2Canals - Variational Action 2 Variables for Canals
  • VarAction2Bridges - Variational Action 2 Variables for Bridges
  • VarAction2Houses - Variational Action 2 Variables for Houses
  • VarAction2IndustryTiles - Variational Action 2 Variables for Industry and Airport Tiles
  • VarAction2Industries - Variational Action 2 Variables for Industries
  • VarAction2Cargos - Variational Action 2 Variables for cargos
  • VarAction2NewSignals - Variational Action 2 Variables for New Signals
  • VarAction2Objects - Variational Action 2 Variables for Objects
  • VarAction2Railtypes - Variational Action 2 for Railtypes
• RandomAction2 - Randomized Action 2
• Callbacks - List of available callbacks

Something to go here