I can't even create the project bro. I don't know Japanese so I just wanted to machine translate the thing to an understandable degree, you could do that yourself (if you can open the game file in translator++ that is)
What you need to do is unpack the game executable into a different folder using enigma unpacker and then copy the www folder into it. THEN try to apply the machine translation using this program.
That kinda works, but Translator++ failed to parse one .json file - Map001.json, which is the one json file that contains like 80% of the game, so when I tried to export the translation to the game there are very little translation and it caused the game to bug out. I kinda gave up until a new version of Translator++ comes out.
Dunno why it takes forever, but you can uncheck all the boxes of the maps you don't want to include in your translation changes (there's a little minus button in the bottom left window that will toggle the check/uncheck option). I'd imagine that would speed up the process, especially if you only need to make a change or two to a specific map.
I found the solution, in my case I moved out some .ks files to outside of their folder and after that I launched translator++ again and then it could finish reading the other .ks files that were left in the folder (In your case some .tjs files could be the problem too, you will have to experiment with that). I guess the problem is those .ks files contained scripts that stops translator++ from doing its job, but another thing is those leftout of the folder files are still containing some texts that were required to be translated so my game was half translated , moreover translated .ks files broke some scripts in my game so it became half playable at them end. Kirikiri (and Kirikiri2) translating functionaty is still too flawed in translator++ so if nothing would work in your case you shouldn't be surprised.
thanks, I moved the first ks file and it started reading the other files.
