SCAN (Metroid Prime 2): Difference between revisions
Jump to navigation
Jump to search
imported>Antidote No edit summary |
imported>Antidote No edit summary |
||
| Line 1: | Line 1: | ||
The '''.SCAN file format''' describes SCAN POI data, and has references to several resources, this variation of the format is completely different that it's [[SCAN (Metroid Prime)|Metroid Prime]] counterpart. | The '''.SCAN file format''' describes SCAN POI data, and has references to several resources, this variation of the format is completely different that it's [[SCAN (Metroid Prime)|Metroid Prime]] counterpart. | ||
{{researchmajor|reason= | {{researchmajor|reason=Crack SNFO}} | ||
__TOC__ | __TOC__ | ||
Revision as of 19:48, 26 January 2015
The .SCAN file format describes SCAN POI data, and has references to several resources, this variation of the format is completely different that it's Metroid Prime counterpart.
|
This file format needs a lot of research Crack SNFO |
Header
The header is rather simple, and consists of the following:
| Offset | Size | Description |
|---|---|---|
| 0x0 | 4 | Magic FourCC |
| 0x4 | 4 | Version Always 2, no matter what game |
| 0x8 | 1 | Boolean? |
| 0x9 | 4 | Unknown |
SNFO Chunk
The SNFO header is simply a FourCC and the total length in bytes, due to the fact that there is nothing in the header to determine which version of SCAN we're working with, we have to rely on the size of the SNFO chunk, if it's less than 0x0251 bytes, it's Metroid Prime 2, otherwise it's Metroid Prime 3.
Other than that SNFO is entirely unknown.
Dependency List
The dependency list follows the same format as DGRP