Kambi

Hey I'm new to this all decrypting business, but I have been trying to deal with .bcs files of RUNE games recently myself. The fact that there is a fan translation of one of their games gives me hope that my task is not insurmountable. But I have been hitting some bumps along the way. If you could link me to where I could download the original and the decrypted script of Hatsukoi I might be able to get a better understanding of whats going on there. Or at least narrow the possibilities.

Hey I'm new and I don't know if this is the most appropriate place to post this, but here goes. I have been trying to decrypt RUNE games. Their scenario files end with .BCS. I have searched through the internet, but don't seem to be able to find a decoder. When it comes to unpacking an archive there is no problems. Most tools are able to do it. The archives end with .g2 which as I understand are decoded with glib2. But basically GARbro can do it no problem. They also have their own image format .PGX. Which also GARbro can be used to understand it. But when it comes to scenario files I can't find anything. So I delved into the hex myself. I found several things there, but I don't seem to find a pattern to the first 5 u4 integers given at the start of the file. One of the problems is that the first int is bigger then the file itself. Which would imply some compression. And the last int seems to be always smaller than the file, except I have found exceptions where it is even bigger than the first int. I suspect it might be part of the actual file data. And when it comes to others ints. I have not been able to find a consistent pattern through all the files of how they are all linked. There always seems to be an exception to whatever file pattern I may find. The funny thing is even though it seems to be compressed I noticed that there was a lot of FF in the file. So I ran a xor(FF) and what I got almost makes sense. I can find glimpses of readable data. Commands, file names etc. But they always have some strange artifacts in the middle of them. Like an extra byte stuck in the middle of a word. Almost like the file is corrupted. Here is an example: 25 6E 6F 25 00 25 00 66 69 40 6C 65 6E 61 6D 00 65 0E 00 69 04 6E 66 0F 00 00 62 67 2F 62 67 00 30 00 31 61 2E 70 67 78 Without the nonsense it reads: no filename inf bg/bg01a.pgx... at least I think It's all encoded in shift-JIS. Similar stuff is in the rest of the file. Sometimes more obvious, sometimes less. I still have some ideas of what I might try next, but I feel I might be either, going in the wrong direction, or might face that I don't have the necessary knowledge to do it. So any info you can share would be appreciated.