- Dec 12, 2021
- 4
- 18
Hey everyone! I made an account expressly because I was really curious about this game. I did a lot of investigating, and I think I finally found the solution so that we can get a translation going! Hopefully this is new and helpful information, and I am not just piling on and looking like a dumbass here...
The game is written in NScripter, same as MGQ, and I found lots of instances of this particular issue with other games written in it. By pure chance when searching on the Japanese API for it (can't link as this is my first post), I discovered that you can enable an "English" mode to the interpreter by putting the command "english" after the "*define" line. In this case, for the first volume, it's in the 02.txt file.
This seems to virtually eliminate the issue of using half-width, English characters. From very limited experimentation, there seem to be 2 caveats to this:
The game is written in NScripter, same as MGQ, and I found lots of instances of this particular issue with other games written in it. By pure chance when searching on the Japanese API for it (can't link as this is my first post), I discovered that you can enable an "English" mode to the interpreter by putting the command "english" after the "*define" line. In this case, for the first volume, it's in the 02.txt file.
This seems to virtually eliminate the issue of using half-width, English characters. From very limited experimentation, there seem to be 2 caveats to this:
- Every non-string English line must be prefixed with a ">" character (mainly during the H scenes and dialogue). Seems you guys discovered that for the dialogue, and it was just the japanese in strings which you can't use this trick for.
- A weird, minor issue I ran into when translating the Sucking Leech page. It seems if you have a space, then a single character, then a space, it can do that weird thing of rendering incorrect characters again. My intuition is that NScripter requires a certain "minimum" byte size for words?