here it gets 2 files correctly.
then I saw you linked another game (VivaFighter) but I don't see the relationship with the GP4 files

eh no, unfortunately was an error of mine in the script.
I have updated the script immediately (note the version 0.1.1 in it), sorry

why "math FILES -= 1"?
the FILES value is correct as is because there are 2 files in the archive.

it's a gzip file, open it with 7-zip

if someone follows this thread, I have just released a major version of QuickBMS. hope you like it

as promised:
http://aluigi.org/papers/bms/helldorado.bms

remember to update QuickBMS!

I have figured the algorithm today while I was working on the TTARCH files in general. practically this type of encryption works in the following way: first are read the 4 bytes at the beginning of the file, it's needed to select 3 parameters: - size of each block - after how much blocks is performe...

released script and new version of QuickBMS (necessary): http://aluigi.org/papers/bms/ttarch.bms http://aluigi.org/papers.htm#quickbms each game uses a different key for the blowfish encryption so the script must be edited manually for specifying the correct key. I downloaded some demos and collecte...

it's simple, build a FILE_OFFSET or a BASE_OFFSET that then you must simply add to the read OFFSET like in this example: get FILES long set FILE_OFFSET long FILES math FILE_OFFSET *= 176 math FILE_OFFSET += 4 for i = 0 < FILES getdstring NAME 160 get UNK1 long get ZSIZE long get SIZE long get OFFSET...

well the format is more simple than how it looked: get FILES long for i = 0 < FILES getdstring NAME 0x50 get OFFSET long get SIZE long get TYPE long log NAME OFFSET SIZE next i the only doubt remain for the first file you posted because that "Sound\subtitres.SUB" extracted from it seems to...

sure and indeed I have already written the script yesterday but the dynamic xor value has been re-introduced in the new version that I will release tomorrow.
so you need only to wait some hours :)

I have figured the algorithm and partially the file format (the folder names exist but don't seem used, mah). practically it works like an encrypted and compressed file system composed by chunks of 65536 bytes encrypted with blowfish and the key "\x96\xCA\x99\xA0\x85\xCF\x98\x8A\xE4\xDB\xE2\xCD...

an idea for catching the right XOR byte can be the reading of the byte at offset 0x18 which is 0xff in clear mode so it's enough to xor it with 0xff to get the right xor value. the only problem is that now the Filexor command uses a fixed number/string as argument while in the past it used a variabl...

the Padding command does a very simple job, gets the current offset of the specified file (the second argument, 1 in that script) and checks if it's correctly padded to the size specified in the first argument. so, for example, if the current offset is 23 and we choose a "padding 16" the c...

for the bin file there are no problems, the other is more chaotic (at a first look): idstring "KSS" goto 0x30 get INFO_OFFSET long get INFO_SIZE long goto 0x40 savepos INFO_OFFSET for INFO_OFFSET = INFO_OFFSET < INFO_SIZE get OFFSET long get SIZE long get DUMMY long get DUMMY long savepos ...