ModdingWiki - User contributions [en-gb]

Commander Keen 1-3 Level format

2013-11-09T09:32:16Z

Dr. Kylstein: /* Compressed */ mention that the rest of the page assumes de/uncompressed data

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The file is composed of three sections, the header, and the tile and sprite planes.

==Compressed==

The compressed levels start with a dword giving the size of the decompressed level in bytes (always divisible by four) followed by the standard level data in RLEW compressed form. The rest of this page assumes decompressed data and uses offsets relative to the start of Level Data.

{| class=wikitable
!Offset||Length||Name||Note
|-
|0 || 4||Decompressed Size||always divisible by four
|-
|4 || ||Level Data ||(see below)
|}

==Header==

The level header is 32 bytes long in total. Most of the header is (or was) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These fields can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.
{| class=wikitable
!Offset||Length||Name||Note
|-
| 0|| 2||Level Width ||
|-
| 2|| 2||Level Height ||
|-
| 4|| 2||Number of Planes ||always 2
|-
| 6|| 4||Blank ||appears to always be zero
|-
|10|| 4||TED Variables ||ignored
|-
|14|| 2||Plane Size ||2(h * w) rounded to the next highest multiple of 16
|-
|16||16||Unknown ||ignored
|}

==Sprite and tile planes==

Each plane is an array of words, padded to plane size bytes with nulls. Each word is a tile, running from left to right, top to bottom. THe first plane is tiles, the second is sprites.

{| class=wikitable
!Offset||Length||Name
|-
|32 ||Plane Size||Tiles
|-
|32 + Plane Size||Plane Size||Sprites
|}

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-11-09T09:28:46Z

Dr. Kylstein: /* Compressed */

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The file is composed of three sections, the header, and the tile and sprite planes.

==Compressed==

The compressed levels start with a dword giving the size of the decompressed level in bytes (always divisible by four) followed by the standard level data in RLEW compressed form. The offsets in the following sections are given relative to the start of Level Data.

{| class=wikitable
!Offset||Length||Name||Note
|-
|0 || 4||Decompressed Size||always divisible by four
|-
|4 || ||Level Data ||(see below)
|}

==Header==

The level header is 32 bytes long in total. Most of the header is (or was) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These fields can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.
{| class=wikitable
!Offset||Length||Name||Note
|-
| 0|| 2||Level Width ||
|-
| 2|| 2||Level Height ||
|-
| 4|| 2||Number of Planes ||always 2
|-
| 6|| 4||Blank ||appears to always be zero
|-
|10|| 4||TED Variables ||ignored
|-
|14|| 2||Plane Size ||2(h * w) rounded to the next highest multiple of 16
|-
|16||16||Unknown ||ignored
|}

==Sprite and tile planes==

Each plane is an array of words, padded to plane size bytes with nulls. Each word is a tile, running from left to right, top to bottom. THe first plane is tiles, the second is sprites.

{| class=wikitable
!Offset||Length||Name
|-
|32 ||Plane Size||Tiles
|-
|32 + Plane Size||Plane Size||Sprites
|}

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-11-09T09:28:23Z

Dr. Kylstein: /* Compressed */ "below" was ambiguous

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The file is composed of three sections, the header, and the tile and sprite planes.

==Compressed==

The compressed levels start with a dword giving the size of the decompressed level in bytes (always divisible by four) followed by the standard level data in RLEW compressed form.

{| class=wikitable
!Offset||Length||Name||Note
|-
|0 || 4||Decompressed Size||always divisible by four
|-
|4 || ||Level Data ||(see below)
|}

The offsets in the following sections are given relative to the start of Level Data.

==Header==

The level header is 32 bytes long in total. Most of the header is (or was) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These fields can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.
{| class=wikitable
!Offset||Length||Name||Note
|-
| 0|| 2||Level Width ||
|-
| 2|| 2||Level Height ||
|-
| 4|| 2||Number of Planes ||always 2
|-
| 6|| 4||Blank ||appears to always be zero
|-
|10|| 4||TED Variables ||ignored
|-
|14|| 2||Plane Size ||2(h * w) rounded to the next highest multiple of 16
|-
|16||16||Unknown ||ignored
|}

==Sprite and tile planes==

Each plane is an array of words, padded to plane size bytes with nulls. Each word is a tile, running from left to right, top to bottom. THe first plane is tiles, the second is sprites.

{| class=wikitable
!Offset||Length||Name
|-
|32 ||Plane Size||Tiles
|-
|32 + Plane Size||Plane Size||Sprites
|}

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-11-09T09:26:36Z

Dr. Kylstein: Made role of compression clearer by restructuring, added tables, some tidying up

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The file is composed of three sections, the header, and the tile and sprite planes.

==Compressed==

The compressed levels start with a dword giving the size of the decompressed level in bytes (always divisible by four) followed by the standard level data in RLEW compressed form. The offsets below are given relative to the start of the level data.

{| class=wikitable
!Offset||Length||Name||Note
|-
|0 || 4||Decompressed Size||always divisible by four
|-
|4 || ||Level Data ||(see below)
|}

==Header==

The level header is 32 bytes long in total. Most of the header is (or was) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These fields can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.
{| class=wikitable
!Offset||Length||Name||Note
|-
| 0|| 2||Level Width ||
|-
| 2|| 2||Level Height ||
|-
| 4|| 2||Number of Planes ||always 2
|-
| 6|| 4||Blank ||appears to always be zero
|-
|10|| 4||TED Variables ||ignored
|-
|14|| 2||Plane Size ||2(h * w) rounded to the next highest multiple of 16
|-
|16||16||Unknown ||ignored
|}

==Sprite and tile planes==

Each plane is an array of words, padded to plane size bytes with nulls. Each word is a tile, running from left to right, top to bottom. THe first plane is tiles, the second is sprites.

{| class=wikitable
!Offset||Length||Name
|-
|32 ||Plane Size||Tiles
|-
|32 + Plane Size||Plane Size||Sprites
|}

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-11-09T08:51:28Z

Dr. Kylstein: /* Sprite and tile planes */ Planesize is the size in bytes, not words.

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The compressed level consists of a dword giving the size of the decompressed level in bytes (Always divisible by four.) and the compressed data.

The file is composed of three sections, the header, and the tile and sprite planes.

==Header==

Most of the header is (Or was.) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.

0 4 Data size Size of the DECOMPRESSED level in bytes (May be absent.)
4 2 Level width Width of level in tiles
6 2 Lev height Height of the level in tiles
8 2 Numplanes Number of planes in level (2)
10 4 Blank Blank
14 4 Ted var 2 TED 1.5 varaibles (Ignored)
18 2 Planesize Level planesize; = 2(h * w) rounded to the next highest multiple of 16
20 12 Unknown More TED metadata?

==Sprite and tile planes==

These are identical on format and composed of words,(Hence the RLEW compression.) one for each 'tile' with the level being read in the 'normal' way. (Left to right, top to bottom.) Each plane is Planesize bytes long, padded with nulls. Tiles are first, then sprites.

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-06-19T06:50:52Z

Dr. Kylstein: Found 12 unidentified bytes between planesize and the planes

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The compressed level consists of a dword giving the size of the decompressed level in bytes (Always divisible by four.) and the compressed data.

The file is composed of three sections, the header, and the tile and sprite planes.

==Header==

Most of the header is (Or was.) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.

0 4 Data size Size of the DECOMPRESSED level in bytes (May be absent.)
4 2 Level width Width of level in tiles
6 2 Lev height Height of the level in tiles
8 2 Numplanes Number of planes in level (2)
10 4 Blank Blank
14 4 Ted var 2 TED 1.5 varaibles (Ignored)
18 2 Planesize Level planesize; = 2(h * w) rounded to the next highest multiple of 16
20 12 Unknown More TED metadata?

==Sprite and tile planes==

These are identical on format and composed of words,(Hence the RLEW compression.) one for each 'tile' with the level being read in the 'normal' way. (Left to right, top to bottom.) Each plane is TWICE the planesize (A word is two bytes.) and padded with nulls. Tiles are first, then sprites

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Commander Keen 1-3 Level format

2013-06-19T04:18:03Z

Dr. Kylstein: Width and height were in the wrong spots, as determined by a quick look into LEVEL01.CK1 with a hex editor

The [[Commander Keen 1-3]] level format was widely used in early [[ID Software]] games, usually stored in the files <tt>LEVELxx.*</tt> (Usually with 8 or 16 levels.) The level files are usually compressed with [[RLEW compression]], though earlier games omit this. The compressed level consists of a dword giving the size of the decompressed level in bytes (Always divisible by four.) and the compressed data.

The file is composed of three sections, the header, and the tile and sprite planes.

==Header==

Most of the header is (Or was.) used by TED v1.5 to load the level and its associated graphics and is not used by games per se. These can be left blank and nobody will care, since the original TED is long gone.

The plane size is interesting, since it has to be divisible by 16 because of how some game engines work. It is how many tiles are in each plane.

0 4 Data size Size of the DECOMPRESSED level in bytes (May be absent.)
4 2 Level width Width of level in tiles
6 2 Lev height Height of the level in tiles
8 2 Numplanes Number of planes in level (2)
10 4 Blank Blank
14 4 Ted var 2 TED 1.5 varaibles (Ignored)
18 2 Planesize Level planesize; = 2(h * w) rounded to the next highest multiple of 16

==Sprite and tile planes==

These are identical on format and composed of words,(Hence the RLEW compression.) one for each 'tile' with the level being read in the 'normal' way. (Left to right, top to bottom.) Each plane is TWICE the planesize (A word is two bytes.) and padded with nulls. Tiles are first, then sprites

==Notes==

This format has been reverse engineered several times, always by the [[Commander Keen 1-3]] modding community.

Games that use this format are [[Commander Keen 1-3]], [[Dangerous Dave in Copyright Infringement]], [[Dangerous Dave 2]], [[Shadow Knights]], and [[Slordax]].

Dangerous Dave in Copyright Infringement appears to be the first game to use this format and has it uncompressed.

[[Category:File Formats]]
[[Category:Commander Keen 1-3]]
[[Category:Map Files]]

Keen 1-3 Tileinfo format

2010-06-21T03:23:56Z

Dr. Kylstein: The plane order was wildly innacurate. I decided to fix up the format and add more offsets while I was at it.

=Overview=
[[Commander Keen 1-3]] has an internal tileinfo file that details the properties of its tileset, whether they block the player, whether they kill, etc. The location of these segments are as follows (For the decompressed executable of each episode only.):

{| class="wikitable" border="1"
|-
! Episode
! Version
! Offset
! Number of tiles
|-
| 1
| 1.1
| 0x131F8
| 611
|-
|
| 1.31
| 0x130F8
|
|-
| 2
| 1.1
| 0x17938
| 689
|-
|
| 1.31
| 0x17828
|
|-
| 3
| 1.1
| 0x199F8
| 715
|-
|
| 1.31
| 0x198C8
|
|-
|}

The file is divided into six 'planes'; each composed of two-byte entries. Each plane covers a specific property of the tileset, such as blocking-up or general behavior. The total size of the tile file is thus (tilenum * 12) bytes. The blocks in order are:

* Number of animation frames
* Behavior
* Top blocking
* Right-side blocking
* Bottom blocking
* Left-side Blocking

=Plane functions=
The first plane deals with animations. The valid values here are 0, 2 or 4, defining the three length of animation used in game. (0, 2 or 4 tile sequences.) The game scans this plane and organizes tiles into 'animation loops' To work predictably a row of 2 or 4 consecutive tiles should all have the value of 2 or 4 respectively. If this is not the case, the first tile encountered will be considered the start of the loop, and the next 1 (Or 3) tiles as part of it.

The behavior plane is how the tile affects the player, with quite a variety of effects as follows:

{| class="wikitable" border="1"
|-
! Value
! Effect
! Value
! Effect
|-
| -2
| Masked
| 14
| Whiskey
|-
| -1
| Foreground
| 15
| Raygun
|-
| 0
| Nothing
| 16
| Pogo
|-
| 1
| Kills
| 17
| Exit
|-
| 2
| Door 1
| 18
| Key 1
|-
| 3
| Door 2
| 19
| Key 2
|-
| 4
| Door 3
| 20
| Key 3
|-
| 5
| Door 4
| 21
| Key 4
|-
| 6
| 500 points
| 22
| Message box pop-up
|-
| 7
| 100 points
| 23
| Light switch
|-
| 8
| 200 points
| 24
| Teleporter
|-
| 9
| 1000 points
| 25
| Switch on
|-
| 10
| 5000 points
| 26
| Switch off
|-
| 11
| Joystick
| 27
| Ankh (Keen 3)
|-
| 12
| Battery
| 28
| Ammo clip (Keen 3)
|-
| 13
| Vacuum
|
|
|}

The blocking planes can have values of either 0-1 (0-4 for top blocking) for each tile and control whether the player can move through that boundary. For example, the top blocking plane controls whether a tile can be stood on. A completely solid tile will thus have all its entries in these planes as 1. For the top blocking plane, the following values are valid:
{| class="wikitable" border="1"
|-
! Value
! Effect
|-
| 0
| Fall through
|-
| 1
| Solid
|-
| 2
| Slippery
|-
| 3
| Ice
|}
=Notes=

This format has been reverse engineered several times, most notably for the Tileinfo program for Keen.

[[Category:Commander Keen 1-3]]
[[Category:File Formats]]

ART Format (Build)

2010-06-08T18:48:48Z

Dr. Kylstein: /* File Names and Tile Numbers */ typo.

The '''ART format''' is used by Ken Silverman's Build engine to store game textures and sprites. It contains a number of individual graphics called tiles.

=File Names and Tile Numbers=
According to Ken Silverman's documentation, ART files can be named anything, as long as they end in three digits and .ART, but for most games they are named TILES###.ART. The Build engine games will load these in order starting from 000 until they can't find any more. Every tile in the game has a numerical index, and each ART file for a particular game holds a range of these. For example, TILES000.ART may hold tiles 0 to 255, and TILES001.ART would hold tiles 256-511. The range of indexes held by a particular file are indicated in the header. The tiles are normally stored sequentially (TILES000.ART holding the first set, and each higher numbered file continuing where the previous left off) with a consistent number of tiles per file, but it is up to the particular game's developers.

=Header=
{| class="wikitable" border="1"
|-
! Data Type
! Name
! Description
|-
| [[UINT32LE]]
| artversion
| version number, should be 1.
|-
| [[UINT32LE]]
| numtiles
| number of tiles, unused. The number of tiles can be determined by the localtilestart and localtileend fields.
|-
| [[UINT32LE]]
| localtilestart
| number of first tile in this file
|-
| [[UINT32LE]]
| localtileend
| number of last tile in this file.
|-
| [[UINT16LE]][localtileend-localtilestart + 1]
| tilesizx
| array of the x-dimensions of all of the tiles in the file
|-
| [[UINT16LE]][localtileend-localtilestart + 1]
| tilesizy
| array of the y-dimensions of all of the tiles in the file
|-
| [[UINT32LE]][localtileend-localtilestart + 1]
| picanm
| array of attributes for all the tiles
|}

=Tile Attributes=
Entries in the picanm array store several properties for each tile:
{| class="wikitable" border="1"
|-
! bits 31-28 (4 bit unsigned integer)
! bits 27-20 (8 bit signed integer)
! bits 19-12 (8 bit signed integer)
! bits 11 and 10 (2 bit enumeration)
! bits 9-4 (6-bit unsigned integer)
! bits 3-0
|-
| Animation speed
| Y-center offset
| X-center offset
| Animation type: 00 = no animation, 01 = oscilating animation, 10 = animate forward, 11 = animate backward
| Number of frames
| unused?
|}

=Pixel Data=
The pixels are stored as bytes, corresponding to indexes in the palette stored in PALETTE.DAT. The pixels in each tile are stored columnwise, starting from the top-left. For a 4x4 tile, the offsets for each pixel would be arranged like this:
{| class="wikitable" border="1"
|-
| 0
| 4
| 8
| 12
|-
| 1
| 5
| 9
| 13
|-
| 2
| 6
| 10
| 14
|-
| 3
| 7
| 11
| 15
|}

=Source=
* This information comes from BUILDINF.TXT in the [http://advsys.net/ken/buildsrc/default.htm Build source] files.

[[Category:File Formats]]
[[Category:Graphics Files]]

[[Category:Build engine]]


[[Category:Duke Nukem 3D]]
[[Category:Redneck Rampage]]
[[Category:Shadow Warrior]]

CON Format

2010-04-02T21:19:30Z

Dr. Kylstein:

The '''CON format''' is used by [[Duke Nukem 3D]], WW2 GI, and Nam for scripting and game parameters. They are [[ASCII]] text files containing directives in a custom scripting language. The scripting language was extended by the later games, and those extensions were re-added to Duke3D by the EDuke project. EDuke has been superseded by EDuke32 which has it's [http://wiki.eduke32.com/wiki/Main_Page own wiki documenting the enhanced CON language]. The subset of commands available in the original Duke Nukem 3D are [http://wiki.eduke32.com/wiki/Category:Duke3D_1.3/1.5_commands listed here.]

CON Format

2010-04-02T21:19:02Z

Dr. Kylstein: Created page with 'The CON format is used by Duke Nukem 3D, WW2 GI, and Nam for scripting and game parameters. They are ASCII text files containing directives in a custom scripting language…'

The CON format is used by [[Duke Nukem 3D]], WW2 GI, and Nam for scripting and game parameters. They are [[ASCII]] text files containing directives in a custom scripting language. The scripting language was extended by the later games, and those extensions were re-added to Duke3D by the EDuke project. EDuke has been superseded by EDuke32 which has it's [http://wiki.eduke32.com/wiki/Main_Page own wiki documenting the enhanced CON language]. The subset of commands available in the original Duke Nukem 3D are [http://wiki.eduke32.com/wiki/Category:Duke3D_1.3/1.5_commands listed here.]

ART Format (Build)

2010-04-02T21:07:08Z

Dr. Kylstein:

The '''ART format''' is used by Ken Silverman's Build engine to store game textures and sprites. It contains a number of individual graphics called tiles.

=File Names and Tile Numbers=
According to Ken Silverman's documentation, ART files can be named anything, along as they end in three digits and .ART, but for most games they are named TILES###.ART. The Build engine games will load these in order starting from 000 until they can't find any more. Every tile in the game has a numerical index, and each ART file for a particular game holds a range of these. For example, TILES000.ART may hold tiles 0 to 255, and TILES001.ART would hold tiles 256-511. The range of indexes held by a particular file are indicated in the header. The tiles are normally stored sequentially (TILES000.ART holding the first set, and each higher numbered file continuing where the previous left off) with a consistent number of tiles per file, but it is up to the particular game's developers.

=Header=
{| class="wikitable" border="1"
|-
! Data Type
! Name
! Description
|-
| [[UINT32LE]]
| artversion
| version number, should be 1.
|-
| [[UINT32LE]]
| numtiles
| number of tiles, unused. The number of tiles can be determined by the localtilestart and localtileend fields.
|-
| [[UINT32LE]]
| localtilestart
| number of first tile in this file
|-
| [[UINT32LE]]
| localtileend
| number of last tile in this file.
|-
| [[UINT16LE]][localtileend-localtilestart + 1]
| tilesizx
| array of the x-dimensions of all of the tiles in the file
|-
| [[UINT16LE]][localtileend-localtilestart + 1]
| tilesizy
| array of the y-dimensions of all of the tiles in the file
|-
| [[UINT32LE]][localtileend-localtilestart + 1]
| picanm
| array of attributes for all the tiles
|}

=Tile Attributes=
Entries in the picanm array store several properties for each tile:
{| class="wikitable" border="1"
|-
! bits 31-28 (4 bit unsigned integer)
! bits 27-20 (8 bit signed integer)
! bits 19-12 (8 bit signed integer)
! bits 11 and 10 (2 bit enumeration)
! bits 9-4 (6-bit unsigned integer)
! bits 3-0
|-
| Animation speed
| Y-center offset
| X-center offset
| Animation type: 00 = no animation, 01 = oscilating animation, 10 = animate forward, 11 = animate backward
| Number of frames
| unused?
|}

=Pixel Data=
The pixels are stored as bytes, corresponding to indexes in the palette stored in PALETTE.DAT. The pixels in each tile are stored columnwise, starting from the top-left. For a 4x4 tile, the offsets for each pixel would be arranged like this:
{| class="wikitable" border="1"
|-
| 0
| 4
| 8
| 12
|-
| 1
| 5
| 9
| 13
|-
| 2
| 6
| 10
| 14
|-
| 3
| 7
| 11
| 15
|}

=Source=
This information comes from BUILDINF.TXT in the [http://advsys.net/ken/buildsrc/default.htm Build source] files.

ART Format (Build)

2010-04-02T20:52:08Z

Dr. Kylstein: Created page with 'The '''ART format''' is used by Ken Silverman's Build engine to store game textures and sprites. It contains a number of individual graphics called tiles. According to Ken Silve…'

The '''ART format''' is used by Ken Silverman's Build engine to store game textures and sprites. It contains a number of individual graphics called tiles.

According to Ken Silverman's documentation, ART files can be named anything, along as they end in three digits and .ART, but for most games they are named TILES###.ART. The Build engine games will load these in order starting from 000 until they can't find anymore.

=Header=
{| class="wikitable" border="1"
|-
! Data Type
! Name
! Description
|-
| UINT32LE
| artversion
| version number, should be 1.
|-
| UINT32LE
| numtiles
| number of tiles, unused. The number of tiles can be determined by the localtilestart and localtileend fields.
|-
| UINT32LE
| localtilestart
| number of first tile in this file
|-
| UINT32LE
| localtileend
| number of last tile in this file.
|-
| UINT16LE[localtileend-localtilestart + 1]
| tilesizx
| array of the x-dimensions of all of the tiles in the file
|-
| UINT16LE[localtileend-localtilestart + 1]
| tilesizy
| array of the y-dimensions of all of the tiles in the file
|-
| UINT32LE[localtileend-localtilestart + 1]
| picanm
| array of attributes for all the tiles
|}

=Tile Attributes=
Entries in the picanm array store several properties for each tile:
{| class="wikitable" border="1"
|-
! bits 31-28 (4 bit unsigned integer)
! bits 27-20 (8 bit signed integer)
! bits 19-12 (8 bit signed integer)
! bits 11 and 10 (2 bit enumeration)
! bits 9-4 (6-bit unsigned integer)
! bits 3-0
|-
| Animation speed
| Y-center offset
| X-center offset
| Animation type: 00 = no animation, 01 = oscilating animation, 10 = animate forward, 11 = animate backward
| Number of frames
| unused?
|}

=Pixel Data=
The pixels are stored as bytes, corresponding to indexes in the palette stored in PALETTE.DAT. The pixels in each tile are stored columnwise, starting from the top-left. For a 4x4 tile, the offsets for each pixel would be arranged like this:
{| class="wikitable" border="1"
|-
| 0
| 4
| 8
| 12
|-
| 1
| 5
| 9
| 13
|-
| 2
| 6
| 10
| 14
|-
| 3
| 7
| 11
| 15
|}

=Source=
This information comes from BUILDINF.TXT in the [http://advsys.net/ken/buildsrc/default.htm Build source] files.