You're doing something wrong then. Try re-applying the patch.The translation is not working for me also
Make sure you're extracting correctly, some people tends to extract compressed files to a separated folder instead of extracting directly to the root folder.well, i've been redownloading it etc., so what i did this time is: download the game, extract it on 1 file, then download the manual translation file, and extract it on the file with the game, and when i open the game it didn't work, do i have to download BepInEx also?
edit: quite confused but it seems to be not working alr, or there's something more to it about the "installation:"
v2022.06 is a really old game version.the "SaMwMS(TheButler)[2023-01]" file is where i extract were the "Spending_a_month_with_my_sister_v2022.06_KumarinSpecial" is already extracted on, then i get an option to replace existing files, which i pressed "Yes to All", and when i open the game(.exe) it's still japanese, i assume there's no settings option in order to change it to english
edit: there is another file made on my desktop,... im quite unsure about that View attachment 2387626
Have you got into the game past the Main Menu?alr, renewed and extracted 2 files, and still seemingly still japanese yet(when i open the game)
No new text.hello i would like to ask if there's any 2023.02 translation
OP (original post) has the most current one.hello i was wondering if the 1st page or header? is the latest translation of the game?
what if they use the same id?Normally scoping works when games have a different active scene id for different types of scenes, the scene id is passed to XUnity and it will try to translate first in just entries in that ID, and if not found then entries in the default scope. I don't believe this game uses that, but my plugin uses custom scopes for it's lookup to ensure strings only useful to the plugin don't pollute the default scope.
{w\=0.3}
is a wait. I encountered a few others as well...{s\=xxx}
maybe, not sure what the difference is.
Generally it's better to use the resizer support in xunity than to inject tags into the translations. The UI library used by this game only expects tags it put there after handling it's custom markup, and timing issues can cause the tags to just be printed instead.
I use this but it gives me the same result.CTRL + ALT + NP7: Print out loaded scene names and ids to console
[Info :XUnity.AutoTranslator] Active Scene: MainScene (1)
[Info :XUnity.AutoTranslator] Loaded Scenes:
[Info :XUnity.AutoTranslator] 0: MainScene (1)
Hi, I try it and sadly doesn't work for meWill english version compatible with this linkYou must be registered to see the links