Duel Love Ds English Patch
. Tell us some more.
Upload in Progress. Upload failed. Please upload a file larger than 100x100 pixels. We are experiencing some problems, please try again. You can only upload files of type PNG, JPG, or JPEG.
You can only upload files of type 3GP, 3GPP, MP4, MOV, AVI, MPG, MPEG, or RM. You can only upload photos smaller than 5 MB. You can only upload videos smaller than 600MB. You can only upload a photo (png, jpg, jpeg) or a video (3gp, 3gpp, mp4, mov, avi, mpg, mpeg, rm). You can only upload a photo or a video.
Download Duel Love: Koisuru Otome wa Shouri no Joshin (2177) ROM for Nintendo DS (NDS) completly free. All roms have multiple mirrors and work across all devices.
Video should be smaller than 600mb/5 minutes. Photo should be smaller than 5mb.
Duel Love: Koisuru Otome wa Shouri no Joshin デュエルラブ 恋する乙女は勝利の女神 This project will have two main goals 1. Direct translation from japanese to english 2.
A second patch for a translation and hack for this game to be guy on guy again japanese to english the first goal will have the following: Complete translation of any and all japanese text into engish. Complete translation of any and all japanese graphics into english. The second goal will have the following: complete translation of the any and all japanese text into engish with an alteration to change the character you play from female to male. This will involve a sound hack as having a female voice talk when its supposed to be a guy, is just wrong. Complete translation of any and all japanese graphics into english.
Along with a more adult themed minigames (yes you get to see adult parts), instead of the way they are now. Which will mean that the patch for the second goal will get an adult rating and will include sexually explicit homosexual content. Although not much. READ CAREFULLY KIDS YOU WILL NEED YOUR PARENTS PERMISSION TO USE AND PLAY THIS PATCH WHEN AND IF IT BECOMES AVAILABLE, IF YOU ARE UNDER THE AGE OF MAJORITY I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGES ARISING FROM ITS USE AND WILL INSIST ON A DISCLAIMER BEING SIGNED FIRST.
THIS SECOND PATCH WILL UNDER NO CIRCUMSTANCES BE ALLOWED TO BE MIRRORED OR UPLOADED TO ANYWHERE WITHOUT MY EXPLICIT PERMISSION. Both goals are dependent on a de-compressor/compressor for the.ptd and.pth files. Which hasn't been made yet.
At this point if there are any programmers willing to work on one p.m. I may be able to pay you for this. (yes I am that desperate to get working on this). Please see later posts for current file dissemination, note information is incomplete.
At this point in time I Only have a little text from the arm9 and staff lists to translate. I think that some people have made an effort to translate other parts of the game, although they haven't been in contact with me on this. Which is more than okay as I haven't made this game a priority and will not until a tool is made. Thanks to jjjewel for the help. 【Disclaimer】As this is a commercial product this game belongs to the copyright holder and or the original maker of said game.
Duel Love Ds English
The english translated patch, any information contianed in this thread or with the patch is only for research study purposes. Organization(s) or individual(s) may not use this product, patch or the information discussed for commercial purposes in any form.
I will not bear any responsibility for the consequences arising from other(s) use. Edit: If you would like to start up you own translation of this game please do so. Click to expand.If you're looking for the text of this game, it's in adv/script/bf.ptd. The bf.ptd is the file that contain game scripts. However, you might have to find a way to unpack and decompress it. I tried to decompress bf.ptd with lz77 decompression programs (I tried gbalzss and the built-in function in CrystalTile2) and some parts of the text are readable (using Shift-Jis encoding) but some still look like garbage. So I think it was compressed with other program or maybe it can be decompressed with lz77 but you need to unpack the script to separate files first.
The file next to it (adv/script/bf.pth) seems to contain the script files' names so it might help. I am still translating and writing down pointers, ie nowhere near a patch release even if I find the beginning script edit october 31 2010 update I have started to hack this. The basic stuff is translated. I need to figure out how to make a custom compression thingy. The.ptd file contains the file data as in is a container file and, the.pth file contains the directory and the huffman tables for the files compressed in the.ptd. I currently have no idea how to uncompress this.
Still trying to figure out how to make a wav to swav converter as I need it to change the voices that play with the text. I have most of the images dumped except for those in the.ptd files. This project is still on the back burner. Edit research thats what ya gotta do. Okay I had to dig around a bit. At first I thought It was a compression from MGS Mobile&Game studio.
But nope none of the games I have investigated from them have anything like it. So I looked up bottlecube, papaya, etc any company that anything to with this game. Bottle cube seems to be the right one. For those curious take a look at Gundam Mahjong(not really the title but its better then the really long name, still gets you where you need to go), then look up Golgo13.
If you do you will see the similarities that have got me sure that some programmer with bottlecube is using these games to finesse their copmpression system. Now if you are wondering why I include Golgo13 in this, well aside from not having a compression system, it has a file structure that appears to match that of what is inside the conatainer files of duel love.
Gundam mahjong has the 2 file system where files are listed in one then the other is the container, but different in that it does not have the offset structure that appears in duel love. Close anough but not the same. One file.lst seems to load a bunch of other files that do make sense to load to together.
I just don't understand why it was not just done in an overlay or the arm9. Anyways similar enough to make me wonder what the heck is going on. So before this I was trying to decompress the files with quickbms from the xentax forums. When I realized there might be flags for compressed or file folder. Which doesn't quite make sense unless the files are being loaded into memory to that 'folder' at that address listed then decompressed later in the file but i cannot get past what type of compression or if I am right as this still leaves one number unknown, I think it is filesize/folder size but the math doesn't add up.
Nor does end of file offset. Will edit and add to later, gotta go. Edit again: 09062011 okay starts with file folder names with pointer to listing of files with possible flag for number of files. Pointer to beginning of file, size of file, flag for possibly compression or number of files, then file name. The first file sys1212.nftr from res.ptd has yet to come out right. Though there is some errors on the nftr extra characters where there should not be from a direct copy paste to a new file. Trial decompression with lz&(lzss) 10 11 40 produces nothing yasu decompression has done nothing.
Editing the extra characters out that I know are there has done nothing. Trimming the file a little again nothing trimming with decompression nothing.
The one flags I am unsure about could be a decompression flag backwards - as the folders do not have this flag with there listing. Every file in the res.ptd and bf.ptd starts with Magic stamp YKLZ though that is not the actual start of the file. Though I think that is a precursor to where the file is being loaded into memory. As after the yklz is some hex I still have to identify edit again 08072011 the hex I yet to identify seems to be a memory address as physical rom address is incorrect. Memory though, from investigation with desmune doesn't seem to point to the right area either.
'YKLZ four zeros'0000' flag for something '01', memery offset? 4bytes for beginning 4 bytes for ending then '00' padding before the file actually starts. Have you figured out the compression yet? I still can't find if it's any kind of existing compression or just a custom compression specific to this game. But some manual manipulation would let you decompress the files and reinsert the decompressed scripts back without problem. (You'll need to change some code in the.pth file though.) I can't recall how I did the manual decompression but the basis is similar to what was discussed in this topic.
(It's not exactly the same, but the concepts are similar.) Some of the extracted script looks like this. Here's the links for the above files in case someone might want to try writing a program to decompress it. Original compressed file: Decompressed file: (Note: Some of the bytes might be slightly off or were modified somehow. It's possible that I might change a few bytes to test something, but I can't remember which file I tested.) A few more notes for some codes used in this game. Date -henko = change (hidukehenko = date change) -jikanido????
Time Change -kakudai Enlarge effect -hikido Sliding door effect. Well any programmers reading this let me know if you are interested in making something. I can send you a used m3 simply in exchange. Edit: so load toc from file 1 with directory name(s), directory offset(s), directory size (folder size), compressed directory(folder) size, file offset(s), file size(s), compressed file size(s), file name(s) listed as strings. String to populate a menu listing with export and import functions.
When exporting file from file 2 use above information to find file (as a string) in file 2. May need to set a copy of the string. One for find operations one for replace operations. Add x offset to get to real file offset, use compressed file size as the size of string to load. After get to offset (may need to subtract yklz header and file size(s) listed beside header).
Find and do; find in string (the 00, 04, 08, 0C). When find load location to (xx) for replace/append function in second string. As some basic math needs to be done. Add 1 to byte beside (xx) location then use that to subtract form (xx) to go to offset (xa) then copy set number bytes (yy - depending on 00, 04, 08, 0C) and append/replace byte in/to offset (xx) in string 2. Continue from offset (xx+1) in sting 1 until having read (za) bytes form compressed file size in file 1. Oy more later.