The current URL is datacrystal.tcrf.net.
Mother 3/SOB block: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 29: | Line 29: | ||
It is not known how secondary entries function. There are typically much fewer secondary entries than primary entries. | It is not known how secondary entries function. There are typically much fewer secondary entries than primary entries. | ||
[[Category: | [[Category:MOTHER_3_named_data_structures|SOB]] | ||
[[Category:MOTHER_3|SOB]] | [[Category:MOTHER_3|SOB]] |
Revision as of 20:29, 15 July 2013
Overview
SOB blocks are used for storing sprite arrangement data. They're organized of tables that are two levels deep. They need to be manually associated with a valid tileset and palette group.
Format
- 00-03 (04) = "sob " header
- 04-05 (02) = Number of primary entries
- 06-07 (02) = Number of secondary entries
- 08-.. (..) = Offset table
- ..-.. (..) = Primary entries
- ..-.. (..) = Secondary entries
- ..-.. (04) = "~sob" footer
Offset table
The offset table contains offsets for both the primary and secondary entries. The secondary entry offsets immediately succeed the primary entry offsets. Each offset is 16 bits, and is calculated relative to the start of the table (including the header).
Primary entries
The primary entries contain sprite arrangement data.
Primary entry format
- 00-01 (02) = Unclassified data
- 02-03 (02) = Number of OAM sprites in this entry
- 04-.. (..) = OAM entries
The OAM entries follow the same format as the standard GBA OAM data. Each entry uses 8 bytes.
Typically in MOTHER 3, a picture will be composed of many sprites; for example, the NK Cyborg picture is composed of six large sprites, so its primary entry will have 6 OAM sprites. Since the OAM entries store coordinate information, one can easily piece together a full picture from the OAM data, tileset and palette data alone.
Secondary entries
It is not known how secondary entries function. There are typically much fewer secondary entries than primary entries.