Chrono Cross Toolsets

[utunnels]

OK, so it is not the size that matters.

This is the modified lzss tool (it has a cygwin dll because on current pc I don't have other compilers installed).

[prizvel]

OK, so it is not the size that matters.

This is the modified lzss tool (it has a cygwin dll because on current pc I don't have other compilers installed).

This tool works perfect. Thank you.

[Schala Zeal]

What are the changes you made?

[utunnels]

Some unnecessary check for ring buffer length while searching the longest matching pattern.


while(l<LZSS_CHAINE && pos+l<LZSS_BUFFER && p%LZSS_BUFFER<LZSS_BUFFER-2
&& buffer[(p+l)%LZSS_BUFFER]==buffer[(pos+l)%LZSS_BUFFER]) {

[utunnels]

Just wrote a tool that imports tim files into vram so you can use a vram viewer to check their positions.

This was originally designed to construct battle field textures, but in theory it can be used for any tim files.

How?
Select all tim files and drag-drop them on the exe. The output file is vram.bin

[utunnels]

Similar tool but imports egfx file int vram. Useful when finding element textures (for example, starky's mecha)

[prizvel]

utunnels If you have time, could you make a tool to pack/unpack drp? Your unpackdrp good, but it ignores unreadable characters. It would be nice if the name of the decompressed file looked like this: "01.000a.7A697A31.zip1" where:
01 - the number of the file
000a - file type
7A697A31 - file name byte(7A 69 7A 31 - for packing with the same name)
zip1 - file name

I'd love to do it myself, but I don't know any programming language

[utunnels]

I'll see what I can do when I get home.
Maybe files and list.txt is a better solution, if not all characters can be used to name a file.

[prizvel]

I'll see what I can do when I get home.
Maybe files and list.txt is a better solution, if not all characters can be used to name a file.

Maybe. I recently came across a file named "1" (31 00 00 00)

[utunnels]

But "1" is legal file name.

[utunnels]

https://drive.google.com/open?id=0B5GvuiubpnUZYi1DMUk2R0pNZkk

By the way, I had a unpackcpt.exe and a cpt.exe in this folder, which I used to test the weapon pack (.weap files).

Usage:
Drag and drop the .weap (or maybe other cpt file) on unpackcpt.exe to unpack it.

Drag and drop all output files onto cpt.exe to repack it (the file will be save to outut.cpt).

Note, on windows, it seems the file order is determined by the first file you dragged, so it is safe to select the first one of all files.

[prizvel]

https://drive.google.com/open?id=0B5GvuiubpnUZYi1DMUk2R0pNZkk

By the way, I had a unpackcpt.exe and a cpt.exe in this folder, which I used to test the weapon pack (.weap files).

Usage:
Drag and drop the .weap (or maybe other cpt file) on unpackcpt.exe to unpack it.

Drag and drop all output files onto cpt.exe to repack it (the file will be save to outut.cpt).

Note, on windows, it seems the file order is determined by the first file you dragged, so it is safe to select the first one of all files.

Oh, thank you, I'm tired of counting everything in the hex editor

[utunnels]

drp.exe has been added.
Usage is the same as cpt.exe

[prizvel]

drp.exe has been added.
Usage is the same as cpt.exe

How to unpack? unpackdrp is not required?

[utunnels]

It is needed.