MuninKai
Well-Known Member
- Apr 29, 2020
- 1,928
- 3,710
- 405
So, cool fact about KiriKiri, it doesn't actually care about the file architecture. You can put any file in any folder and it will find it just fine. That's purely for human readability reasons. The catch is that it will only ever look at the folders that are described in I think startup.tjs? Either that or 0.ks. I have no idea how it will behave if you add /patch1 and /patch2 to its directory, but that's an option.great thx, this helps a lot, the 072 version also has 2 patchs and both patchs have redundants files for データ.ks and 回想関数.ks and a lot more, this helps narrow the search at least, thx, didn't know about overflow text problem for kirikiri, it could REALLY be it since the gallery in english is the only one missing the character names only showing the bottom of the gallery. will try fixing the data/system2, and if that doesn't work i will try my luck with the patchs files. the problem is when i extract the files on the patch the game doesn't even open anymore, return voids and such, but could be that the overflow problem becomes worse on the loose files. thank very much MuninKai, i'm not familiar with the tool(kirikiri) and how it works/common problems.
edit: yeah the chance for this to be the problem is high, the text in the 072 version is way more extended, but the patch structure is giving me problems, if i extract only the data folder and use patch1.xp3 and patch2.xp3 the game works and runs normally using the kirikiri executable from MuninKai version, but i can't change the データ_EN that is inside the patch2.xp3 and thus making the text smaller. if i try to extract patch1.xp3 and patch2.xp3 to patch1/ and patch2/, the game stops working says that is missing key parts like game battle items and such, maybe the executable that i got from this thread can't read the loose patch files. will try again later. will try extracting, then packing again the patch2/ to patch2.xp3 with the fixes to see if this bypass the problem.
View attachment 5348876
View attachment 5348859
View attachment 5348860
My solution was to write a Python script that walks through all the files replaces the originals with patched files. This is why my releases don't have any /patch folders. I should probably put all my code up on GitHub or something, but if you're familiar with Python, the script is
You must be registered to see the links
.