SCAN (Metroid Prime 2): Difference between revisions
Jump to navigation
Jump to search
>Sdmr m (grammar correction and minor improvements in readability) |
>Embyr 75 m ({{research}}) |
||
| Line 1: | Line 1: | ||
{{research|3|Crack SNFO}} | |||
The '''.SCAN file format''' describes SCAN POI data and has references to several resources. This variation of the format is completely different than its [[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 than its [[SCAN (Metroid Prime)|Metroid Prime]] counterpart. | ||
__TOC__ | __TOC__ | ||
Revision as of 07:35, 1 February 2015
|
This file format needs a lot of research Crack SNFO |
The .SCAN file format describes SCAN POI data and has references to several resources. This variation of the format is completely different than its Metroid Prime counterpart.
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