MOMO and initial quest data offset info

[IncognitoMan]

MOMO format:

Offset	Size	Description
0x00	4	Magic ( OMOM )
0x04	4	Num. of files
0x08	4	File 1 offset
0x0C	4	File 1 size
0x10	4	File 2 offset
0x14	4	File 2 size
...	...	...
0x**	4	NULL ( 00 00 00 00 ) happens after the last file size in the index
0x**	*	DATA

Quest format:

Offset	Size	Description
0x00	40	Quest title
0x8C	40	Sub quest 2 objective title
0xB5	40	Sub quest 2 objective title
0x138	4	Quest time limit
0x330	4	Primary quest type
0x334	2	Primary objective type
0x336	2	Amount to kill/turn in of primary objective type
0x338	4	Sub quest 1 type
0x33C	2	Sub quest 1 objective type
0x33E	2	Amount to kill/turn in of sub quest 1 objective type
0x340	4	Sub quest 2 quest type
0x344	2	Sub quest 2 objective type
0x346	2	Amount to kill/turn in of sub quest 2 objective type
0x348	4	Quest fee
0x34C	4	Primary quest reward
0x350	4	Sub quest 1 reward
0x354	4	Sub quest 2 reward
0x358	4	Amount of zenny deducted per cart

I know other values too but I want to first figure out the full maximum length that the game reads as well as create a entire ID list for everything in the game.

For example with quest types a "Deliever" quest would be 00 00 00 02 while a "Slay" type quest would be 00 00 01 01

I still wish there would be an easier way to talk to you than through the issue tracker... :P

[sepalani]

Thanks for your help, but it was already discussed here at page 31. You didn't specify the string encoding which is very important and changes between Japanese and others versions.

By the way, it is not my priority right now. So unless, you're able to reverse the whole file format and more. Indeed, the arena quest file format is a little different because it grabs data somewhere else in the main.dol IIRC in order to propose those armors/weapons selection choice. There are also some bytes used to trigger events such as rocks blocking paths, etc.

Last but not least, online arena/event quests format remains almost unknown without tangible proofs.