Reply to thread

Message: <blockquote data-quote="FAST6191" data-source="post: 5843265" data-attributes="member: 32303">Afraid my little netbook is the only thing set up to handle DS ROMs that I have with me at this point and hacking things on such a low res is no fun at all so I am going to struggle to do my usual full workupAnyway in the base directory there are some NFTR fonts which is nice as that means you have the encoding. It could still be another font/setup is used in the game but as I also see FontColor.NCLR I would wager on it being the chosen font for the game. The game otherwise does seem to almost exclusively use the .pak extension. There is also a folder called script with sub directories having all sorts of things. I have not checked it yet but <a href="http://filetrip.net/nds-downloads/utilities/download-nftredit-1-9-f29196.html" target="_blank">http://filetrip.net/nds-downloads/utilities/download-nftredit-1-9-f29196.html</a> is usually pretty nice for this sort of thing, crystaltile2's more limited abilities here worked so it should work in that.I usually find in these situations a big file and a small file of the same type are good things to have. In this case I would also grab some non script related .pak files just in case something odd happens and I could figure something out with it.I could already see in Cystaltile2 that the starting values would be different (it tries to detect things, including compression, based upon them and had all sorts of ones going on)Big or small it looks like 8 bytes before it has ASCII what could be file or section names, even for the single file non script thing I grabbed.No immediately obvious file size but the first value might well be some kind of file/section count.Names appear to be of random lengths as well and no size value there (just 00 between them, maybe 0000 to end or it might just be alignment)The later 4 bytes might well be a first file start location and that is usually at the end of the file name section so no idea where sizes might be hiding. Normally now I would try to find a known format (I mentioned NCLR and NFTR earlier so it is a good bet that they do use some somewhere in this .pak stuff) but none of my initial 5 random (3 script) samples had that, though I did see .txt in there. This is mainly to see if they had some kind of size value at the start of things. I watched a video though and there did not appear to be much 2d in the normal game (it looks 2d but that is classic texture overlay and the amount of .tex I was seeing would seem to indicate texture rather than classic 2d and with it many known formats), though the UI is probably 2d at some level. As I was not seeing much compression (the rom barely trims at all and is just under 64 megs but the 7z version is 36) I tried a normal strings search on the ROM to see what shakes loose and back trace that to a file but I am going to have to leave it there for now as it would take all day on this screen (I ran a min length of 4 search and was north of 60000 hits, most of which were noise, before I even got out of the first maybe 10th of the ROM). I did see BCA0 though which is associated with various DS 3d formats in the NSBMD family and a more directed strings search pointed me at the the one in the submenu folder. The first value did still point to the end of the name section but what should have been a normal graphics format was not there and it appeared somewhat later so I imagine that is where the size values are located. I have to run though so I will leave it there for now.I should also note I grabbed the one from the xls npc file and saw a bunch of things saying MSG in there which does mean the script/translation might not be contained to the script directory.</blockquote>

Verification

Search

Search

Reply to thread

Settings Notifications

Options