ARC (Majiro): Difference between revisions
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
== Notes == | == Notes == | ||
Large space I can't ID with just looking at it. Could be protected. It is always divisible by 16 so each entry could be 16 byte. Could be two values, offset and filesize. Or could be filesize, offset, filename offset, and something else. Need debugger to check. Filenames initially look easy to see however they are not all null terminated. some are 0x0D0A between entries so this confuses things. especially since it's only the later half. File data does not appear compressed. Filenames are not in descending order. | Large space I can't ID with just looking at it. Could be protected. It is always divisible by 16 so each entry could be 16 byte. Could be two values, offset and filesize. Or could be filesize, offset, filename offset, and something else. Need debugger to check. Filenames initially look easy to see however they are not all null terminated. some are 0x0D0A between entries so this confuses things. especially since it's only the later half. File data does not appear compressed. Filenames are not in descending order. Some filenames have some shift-JIS. Could make things complicated. Mix of half and full width characters. | ||
Latest revision as of 02:02, 17 May 2015
Used in the following game(s):
- Starless
Structure
| Header | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Size | Content | Description | ||||||||||||
| 16 Bytes | Magic | MajiroArcV3.000 | ||||||||||||
| 4 Bytes | FileCount | |||||||||||||
| 4 Bytes | Filename Index offset | |||||||||||||
| Index1 Entry | ||||||||||||||
| Size | Content | Description | ||||||||||||
| 16 Bytes | Unknown | ? | ||||||||||||
| Filename Index | ||||||||||||||
| Size | Content | Description | ||||||||||||
| ? Bytes | Unknown | ? | ||||||||||||
Notes
Large space I can't ID with just looking at it. Could be protected. It is always divisible by 16 so each entry could be 16 byte. Could be two values, offset and filesize. Or could be filesize, offset, filename offset, and something else. Need debugger to check. Filenames initially look easy to see however they are not all null terminated. some are 0x0D0A between entries so this confuses things. especially since it's only the later half. File data does not appear compressed. Filenames are not in descending order. Some filenames have some shift-JIS. Could make things complicated. Mix of half and full width characters.