Exit Destination (.JMP) File Format
Revision as of 03:49, 22 November 2022 by Whataboutclyde (talk | contribs) (→jumpEntry: Making it more in line with the new ones I made.)
Note: This page pertains to Reverse Engineering of Okami.
Explanation
This file defines the destinations for exits. This does not define the loading zones themselves, but is referred to by them. (See Zone (.MEH/.SCA/.SCI) File Format for that.)
File Format
Overall
| Start (Bytes in Hex) | Width (Bytes in Hex) | Type | Field Name | Note |
|---|---|---|---|---|
| 0 | 4 | uint32 | Number of entries | Count of exit destination definition. |
| 4 | 12 each | jumpEntry array | jumpEntry | One for each exit definition. |
| padding | Pad with zeroes for 64 byte alignment |
jumpEntry
Describes a single exit destination.
| Start (Byte) | Width (Bytes) | Type | Field Name | Note |
|---|---|---|---|---|
| 0 | 6 | PackedTuple<int16> | coordinates | Location on destination map (x, y, z) |
| 6 | 2 | uint16 | orient | Ammy's orientation. Could be int16. |
| 8 | 1 | uint8 | area_id | See Level File ID Table. |
| 9 | 1 | uint8 | region_id | See Level File ID Table. |
| 10 | 1 | uint8 | unknown | Seems to reference the other side of the exit but doesn't do anything when changed? |
| 11 | 1 | uint8 | exit_id | Index into this file. |