What exactly 'PRT' stands for is unknown; it would be conceivable, for example, to assume 'Palette and Resource Table' - you can find it as op2_art.prt in maps.vol - would describe the function quite well.

Published on 06/10/2018, updated on 06/10/2018

ADR x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF
0000 0000 43 50 41 4C xx xx xx xx  
Number of palettes Data type: uint24
Specifies, contrary to the normal block format, the number of palettes to be found in this file - not the length of the block in bytes.
Flags? Data type: uint8
Probably, as usual, flags.
However, I don't know any flags; since all the values I know correspond to 0x00, it would also be potentially conceivable that the number of palettes would simply be a uint32.

This file contains a list of palettes, a table of all bitmaps used, all animation definitions and a number of unknown data. It loosely follows the previous container format, since not all data records follow this scheme.

The CPAL section (probably stands for palette container) only encloses the palette data by specifying how many of the usually 1052-byte 8-bit palettes are available.

The 1052 byte specification is not binding, as the palette format potentially provides for different palette sizes. It only applies to the database with which Outpost 2 is delivered.

The palette lists are immediately followed by the list of bitmaps, without an introductory header, and the animation lists are also immediately followed. Both are each introduced with a uint32 (or again uint24+uint8 flags?), which contains the number of data sets.


add a comment

Your comment may not be displayed immediately and will be moderated for spam prevention reasons.