Action2

From GRFSpecs
Revision as of 15:54, 15 July 2005 by dmccoy (talk)
Jump to navigationJump to search

Define graphics set IDs

Action 2

Defining graphics set IDs.

-=Introduction=-

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.

-=Format=-

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 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||

-=Filling in the terms=-

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

07 for houses

09 for industry tiles

0A for industries

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 either action 7 or 9 (unless those skip the whole file). Action 2 must not be skipped or the patch will most likely crash. Skip or modify action 3 instead.

-=Feature specific formats=-

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

{toc}

-=Example=-

Something to go here