These files (like EmFileMes.pac or EmFileIcon.dat) have no structure at all. It's just one file appended to another and padded to the length of the largest file rounded up to the nearest 0x800. The padding is not stored within a file (probably in the executable itself), so you need to keep the offse...

You might try reaching Robin Colly on his site (balamb.pl). He's done both PS2 and PC (Steam) Polish translations.

Here's his FFX:Int PC Steam project release

Here's the forum

These files are not used. On PS2 these directories (AFAIR st0, std and one or two more) were empty.

An updated version of tools: http://ff12.pl/down/okami-tools-20180111v2.zip I've added support for PS2 binaries in okami-pack (via -ups2 and -pps2 switches). I've added support for external character replacement table to okami-msd (via -t=table_file). I've included default table (it's not necessary ...

It doesn't support any language in particular. It supports the glyphs supported by the game and present in character replacement table (hardcoded in executable for now). It so happens I encoded the table as utf8. The tool should work (provided you'll use proper replacement table) on any encoding tha...

Here is an updated msd tool that handles both u16 values properly. Now it also takes care of utf8 bom/signature. http://ff12.pl/down/okami-tools-20180108.zip Remember, though, the tool writes proper utf8 and expect utf8 but in fact is unaware of the encoding whatsoever. It's lazy but it works. @inno...

Remove the BOM (which doesn't have any sense anyway as utf8 has no byte order, you always read 8 consecutive bits at once, so no marker is necessary, they really should call it utf8 header or something). The tool is unaware of any BOM value at the beginning and it might cause these issues. As I wrot...

It does. Just make sure the text is utf8 encoded.

There is an issue with the MSD unpacker/repacker. The very first value (number of dialogs) is not u32 but u16 folowed by another u16. Trivial to fix, but the tool will crash on some of the files. Unfortunately I won't have access to the source code until Monday (I've been working on it during my lun...

Here's a simple tool to unpack/repack MSD files. It lacks some stuff like speaker codes (like hmff is narrator, etc. - I've got all of them from PS2 version, so no problem here) and some special codes are not recognized (it's fine, actual 16bit short values are inserted into the file). I might add t...

Quick update. I've written a simple unpacker/repacker. It can handle most of the binary containers, while repacking it also handles 64bit runtime offset file if it's present (it essentially contains the same pointers that at the beginning, only 64bit length and it's overwritten in memory to actual r...

Thanks. Nice finds. It will be helpful for quick changes and testing. To be honest, though, I've never understood this kind of forced and useless code. What was the point? The implementation was simple and didn't take much time, but has certainly cost a measurable amount of money to develop and test...

The first thing you need to realize is that Okami was initially a Wii (and then PS2) game. This means very strict memory and computing power constraints. That's one of many reasons why every format was developed to need the least possible memory footprint and the least possible processing. An XML pa...

AceWell wrote:nice work! what was the key, if you don't mind me asking?

I guess someone was hungry...

It's blowfish with 256bit key. The key had to be (obviously) in the game. I wrote yesterday a tool to decrypt/encrypt it (I'm porting our Polish translation project from PS2 to PC). Don't mind "compress/decompress" in usage, I've copied that part from my another tool ^^. Have fun. http://f...