Difference between revisions of "BUN file"
m (Espyo moved page Pikmin BUN Files to BUN file without leaving a redirect: Consistency.) |
(Cleanup.) |
||
Line 1: | Line 1: | ||
− | '''BUN''' files (short for '''Bundle''' files) are a Binary Large Object (BLOB) archive format used in Pikmin | + | '''BUN''' files (short for '''Bundle''' files) are a Binary Large Object (BLOB) archive format used in ''[[Pikmin]]''. '''ANM''' files (likely short for '''Animation Folder''') use the structure of BUN files as well. With minimal metadata, {{unsure|the bundle archive was likely used to reduce load time by packing several files into one}}. The purpose they serve is different from the [[Pikmin Paired ARC+DIR Files|Paired ARC+DIR Files]], however, as all of the files within a bundle are unpacked into RAM as soon as one is loaded, as shown by the [[OpenGl / Dolphin System]]. |
− | |||
__TOC__ | __TOC__ | ||
− | + | ==File structure== | |
− | ==File | ||
The bundle file is very simple. There is a header, followed by a repeating struct for every file contained within the BUN. Each struct has a subheader and file contained within it. | The bundle file is very simple. There is a header, followed by a repeating struct for every file contained within the BUN. Each struct has a subheader and file contained within it. | ||
− | Here is <code> | + | Here is <code>/dataDir/bosses/mizu/mizu.anm</code> annotated for reference. |
[[File:BUN_and_ANM_file_documentation.png]] | [[File:BUN_and_ANM_file_documentation.png]] | ||
[[File:Minty_Meeo_Documentation_Legend.png]] | [[File:Minty_Meeo_Documentation_Legend.png]] | ||
− | {| class="wikitable" | + | {| class="wikitable" |
|+ Header | |+ Header | ||
− | ! Offset || Size || Purpose | + | ! Offset || Size || Purpose |
|- | |- | ||
− | | 0x00 || 4 || Number of structs | + | | 0x00 || 4 || Number of structs |
|- | |- | ||
|} | |} | ||
− | {| class="wikitable" | + | {| class="wikitable" |
− | |+ File | + | |+ File entry struct |
− | ! Offset || Size || Purpose | + | ! Offset || Size || Purpose |
|- | |- | ||
− | | 0x00 || 4 || File | + | | 0x00 || 4 || File content indicator |
|- | |- | ||
− | | 0x04 || 4 || Enclosed | + | | 0x04 || 4 || Enclosed file size |
|- | |- | ||
− | | 0x08 || 4 || Mock- | + | | 0x08 || 4 || Mock-directory string length |
|- | |- | ||
− | | 0x0c || 0x08 value || Mock- | + | | 0x0c || 0x08 value || Mock-directory path |
|- | |- | ||
− | | 0x0c + 0x08 value || 0x04 value || Enclosed | + | | 0x0c + 0x08 value || 0x04 value || Enclosed file |
|- | |- | ||
|} | |} | ||
− | + | ===Mock-directory=== | |
− | ===Mock- | ||
Similar to the [[Pikmin Paired ARC+DIR Files|Paired ARC+DIR Files]], the bundle archive emulates a folder path. When the file is unpacked in-game, it is assumed that whatever code is responsible treats the contents of the bundle files as if they were in the folder path described, starting from the root of the disc. | Similar to the [[Pikmin Paired ARC+DIR Files|Paired ARC+DIR Files]], the bundle archive emulates a folder path. When the file is unpacked in-game, it is assumed that whatever code is responsible treats the contents of the bundle files as if they were in the folder path described, starting from the root of the disc. | ||
− | + | ===File content indicator=== | |
− | ===File | + | The file content indicator is a seemingly vestigial function. However, it has been observed that it is always set to specific values that reflect the type of file contained within the struct. |
− | The file content indicator is a seemingly vestigial function. However, it has been observed that it always | + | * 0 = [[PCR file|PCR]] |
− | * 0 = [[ | ||
* 1 = [http://wiki.tockdom.com/wiki/BTI BTI] | * 1 = [http://wiki.tockdom.com/wiki/BTI BTI] | ||
* 2 = DCA | * 2 = DCA | ||
* 3 = DCK | * 3 = DCK | ||
+ | {{Credits|[[User:Minty_Meeo|Minty_Meeo]]}} | ||
[[Category:Pikmin]] | [[Category:Pikmin]] | ||
[[Category:File formats]] | [[Category:File formats]] | ||
− |
Revision as of 15:59, 30 June 2018
BUN files (short for Bundle files) are a Binary Large Object (BLOB) archive format used in Pikmin. ANM files (likely short for Animation Folder) use the structure of BUN files as well. With minimal metadata, the bundle archive was likely used to reduce load time by packing several files into one[unsure]. The purpose they serve is different from the Paired ARC+DIR Files, however, as all of the files within a bundle are unpacked into RAM as soon as one is loaded, as shown by the OpenGl / Dolphin System.
File structure
The bundle file is very simple. There is a header, followed by a repeating struct for every file contained within the BUN. Each struct has a subheader and file contained within it.
Here is /dataDir/bosses/mizu/mizu.anm
annotated for reference.
Offset | Size | Purpose |
---|---|---|
0x00 | 4 | Number of structs |
Offset | Size | Purpose |
---|---|---|
0x00 | 4 | File content indicator |
0x04 | 4 | Enclosed file size |
0x08 | 4 | Mock-directory string length |
0x0c | 0x08 value | Mock-directory path |
0x0c + 0x08 value | 0x04 value | Enclosed file |
Mock-directory
Similar to the Paired ARC+DIR Files, the bundle archive emulates a folder path. When the file is unpacked in-game, it is assumed that whatever code is responsible treats the contents of the bundle files as if they were in the folder path described, starting from the root of the disc.
File content indicator
The file content indicator is a seemingly vestigial function. However, it has been observed that it is always set to specific values that reflect the type of file contained within the struct.