Difference between revisions of "Exit Destination (.JMP) File Format"
Jump to navigation
Jump to search
(Created page with "{{RE}} ==Explanation== This file defines the destinations for exits. This does not define the exit definitions themselves, but is referred to by them. (See Zone (.MEH/.SCA/....") |
|||
| Line 3: | Line 3: | ||
==Explanation== | ==Explanation== | ||
This file defines the destinations for exits. This does not define the | 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== | ==File Format== | ||
Revision as of 16:09, 25 November 2021
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
uint32_t number_of_entries // One for each exit destination definition.
For each entry:
uint16 x_coordinate
uint16 y_coordinate
uint16 z_coordinate
uint16 ammy_orientation
uint8 area_id // See Level File ID Table.
uint8 region_id // See Level File ID Table.
uint8 unknown // Seems to reference the other side of the exit, but doesn't appear to do anything when changed.
uint8 exit_id // Index into this file.
Pad with zeroes for 64 byte alignment.