Template:RCO TOC entry common area
Jump to navigation
Jump to search
| Offset | Length | Type | Name |  |
 |
Example (TOC) | Example (XML) | Notes |
|---|---|---|---|---|---|---|---|---|
| 0x00 | 0x04 | int | entry_type | Yes | Yes | 01 01 00 00 | <MainTree name="label"> | First and second byte indicates the entry type |
| 0x04 | 0x04 | int | entry_label_offset | Yes | Yes | 00 00 00 00 | Offset to the label (relative to the label table). 0xFFFFFFFF means the label doesn't exist for this entry | |
| 0x08 | 0x04 | int | entry_header_size | Yes | Yes | 00 00 00 28 | no XML representation | sizeof(RCOEntry) = 0x28 [ only used for entries with extra info (ie not "main" entries) ] |
| 0x0C | 0x04 | int | entry_size | Yes | Yes | 00 00 00 00 | main tables (main/img etc) uses 0x28 here, or is this the length of current entry (not including subentries)? | |
| 0x10 | 0x04 | int | children_number | Yes | Yes | 00 00 00 00 | represents XML hierarchy | |
| 0x14 | 0x04 | int | next_sibling_offset | Yes | Yes | 00 00 00 00 | ||
| 0x18 | 0x04 | int | prev_sibling_offset | Yes | Yes | 00 00 00 00 | this is usually 0x0 however (does make writing RCOs easier though :P I guess Sony's tools do something similar...) | |
| 0x1C | 0x04 | int | parent_offset | Yes | Yes | 00 00 00 28 | entry offset relative to parent start offset | |
| 0x20 | 0x04 | unk | toc_entry_unknown1 | Yes | Yes | 00 00 00 00 | no XML representation | |
| 0x24 | 0x04 | unk | toc_entry_unknown2 | Yes | Yes | 00 00 00 00 |