frc_

Just wanted to mention I've fixed a bug in the "vaconv" tool from RLDev (used for converting from and to the proprietary .g00 image file format of the RealLive and SiglusEngine game engines).
The bug is that if a .g00 file contains multiple images, vaconv places these over each other in the resulting .png, leaving only the last image visible and the others obscured partially or completely behind it. This typically makes editing impossible. Some people have found a workaround involving Crass, screenshots, manual image stitching and RealLiveMax (the all-Japanese RealLive SDK)... But this is a quite involved process.
Instead I fixed vaconv so it properly places the various images of a .g00 below each other in the output .png, allowing an editor to change all of them without the manual hassle mentioned above. (And by "fixed", I mean "rewrote from scratch in C++", since I gave up on trying to compile the original OCaml code after half a night)
This new tool is named "vaconv-cpp.exe" to distinguish it from the original "vaconv.exe" in RLDev. ("cpp" for "C++")
Example with a file from Hanasaki Workspring:
vaconv.exe _config_system_hscene_select_btn.g00

vaconv-cpp.exe _config_system_hscene_select_btn.g00

Download (includes complete source code as a VS2015 project). VS2015 runtime is required.

I'm dropping this project. My apologies to anyone who was looking forward to it.
Because the common route hasn't been edited, I won't release a partial patch (it wouldn't be enjoyable to read). Conversely, the editing in the heroine routes is so heavy (often replacing entire sections of narration by original text) that I also won't release the translation for others to pick up. If this game ever gets a full translation, it should be a consistent one.

I'm dropping this project. My apologies to anyone who was looking forward to it.
Because the common route hasn't been edited, I won't release a partial patch (it wouldn't be enjoyable to read). Conversely, the editing in the heroine routes is so heavy (often replacing entire sections of narration by original text) that I also won't release the translation for others to pick up. If this game ever gets a full translation, it should be a consistent one.

I'm dropping this project. My apologies to anyone who was looking forward to it.
Because the common route hasn't been edited, I won't release a partial patch (it wouldn't be enjoyable to read). Conversely, the editing in the heroine routes is so heavy (often replacing entire sections of narration by original text) that I also won't release the translation for others to pick up. If this game ever gets a full translation, it should be a consistent one.

I'm dropping this project. My apologies to anyone who was looking forward to it.
Because the common route hasn't been edited, I won't release a partial patch (it wouldn't be enjoyable to read). Conversely, the editing in the heroine routes is so heavy (often replacing entire sections of narration by original text) that I also won't release the translation for others to pick up. If this game ever gets a full translation, it should be a consistent one.

I'm dropping this project. My apologies to anyone who was looking forward to it.
Because the common route hasn't been edited, I won't release a partial patch (it wouldn't be enjoyable to read). Conversely, the editing in the heroine routes is so heavy (often replacing entire sections of narration by original text) that I also won't release the translation for others to pick up. If this game ever gets a full translation, it should be a consistent one.

Finding the .ybn decryption key is trivial: if you know the correct offset, it's right there in the file. No need to calculate or bruteforce anything.
Here's a zip with the scripts in an Excel file and a tool that'll put the translated text back into the .ybn files: https://www.dropbox.com/s/lbhwyrt7lio0zd0/Yome juu tools.zip?dl=0
The patched files get placed in the "patch" folder. Copy those to a new "ysbin" folder in the game and you're all set.
Some more remarks about the tool:
It handles word wrapping automatically by inserting line break instructions. You may need to adjust the "MonospaceCharactersPerLine" setting in tool\textpatch.exe.config to get this working correctly. If you're planning on working on this translation with multiple people, it's also possible to create a translation patch directly from a Google Docs spreadsheet rather than an Excel file. PM me for details on this.

What do you plan to
sorry, message cutting out, windows 10 has to update

@HoplessHiro @frc_ @Huang Ling Yin
Just to notice you with the new FreeMote v1.3 release.
https://github.com/UlyssesWu/FreeMote/releases/tag/v1.3.0
As I mentioned before, the new version is faster than ever, Dullahan Load feature allows you to drag&drop your compressed and encrypted "dx***-krkextract.psb" directly to PsbDecompile to get json result, and FreeMote now can pack/unpack known shell types (lz4,mdf,psz) - now FreeMote should be able to replace psbtools totally  Click the link for full release note. If you have found a bug, you can open an issue and I will look into it (when I have time).
And now you can use FreeMoteViewer to view motions (timelines):
Some examples to explain the workflow:
You have a LZ4 shell packed, encrypted (key: 123456789) PSB (dx.psb). To unpack it, purify it, edit it, encrypt it, and then pack it (if needed) -
In short - You can process a PSB without EmoteConv, just to set params in resx.json to control compile process (pack or not; encrypt or not etc.). Or you can use EmoteConv to get pure PSB at first for editing convenience.
 

Shigure planned to have them all get together with him though so why would she wait? My guess is that she will bribe the catgirls with tuna then switch place with one of them when they all plan to have sex with her brother at the same time. Shigure will probably just dress up like one of them and try to use the confusion to get him to insert it from behind and use the fact that he deflowered her to make him take responsibility.

I just played Nekopara 1 for the first time two days ago. I'm horrified. It's like the ultimate objectification of women. They're intellectually inferior, children, dependents, sex objects, they don't have goals or ambitions that conflict with your own, their job is to smile and be cute, they are suited to be your lover, play partner, free labor, whatever you want to buy them for, they're just playthings that have no agency whatsoever and they're custom designed to love, lust for, and worship you. They're the realization of the image that oppressed women across the world are forced into reflecting. They're disposable daughter wife sex slaves, and the entire world around them just treats it as normal. It makes me so sick.

Also, I came buckets and my heart grew three sizes that day. I can't wait to play the sequels.
 
 

@Ulysses My own converter uses FreeMote to go from PSB to Excel/Google Docs and back without a JSON step inbetween. I've found the library works on scenario files which other tools crash on, so if you ask me, it's the best .scn patching solution available. The converter is currently not public, but is being actively used in a number of translation projects - I'll probably throw it on Github at some point.

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

1) Visual Novel Reverse Engineering 101
2) The most common x86 instructions, how registers and memory work, how to use a disassembler, examples of file formats found in VNs.
3) Field trip: breaching the head office of a visual novel company and lifting their source control server while holding the CEO's daughter hostage. (Different company each year)
4) Writing a converter for a proprietary image format in Python.
1) Restoration of Hand-drawn Japanese Media
2) Methods for accurately estimating how a given damaged area originally looked like and faithfully restoring it. Examples of particularly tricky restoration works carried out by famous experts in the field.
3) Getting naked and acting out scenes in groups to take pictures for tracing.
4) Retouching a lightly damaged artwork.

1) Applied Localization of Bonding Segments in Visual Novels
2) Refresher on the various tropes and clichés found in Japanese romance scenes. Examples of common inaccuracies and exaggerations to be aware of. Techniques for improving upon overly repetitive or graphic descriptions.
3) Playing a segment on the projector and discussing how it could be rewritten to be more realistic and engaging to read.
4) Screwing a sibling of choice and recording the act for reference when translating intrafamilial bonding scenes. (Only children can ask their parents for help)

I'm glad you specifically mentioned "essence", as in some cases, the author is simply not very good (at least by Western standards) and you do need to make quite some changes to get an enjoyable result. The visual novel I'm currently translating suffers from, among others, the following deficiencies:
Repetition of random words like "city" up to six consecutive times. Narration that's redundant with preceding dialogue (e.g. a character saying "I don't know" followed by narration saying "Apparently she doesn't know"). Narration that's redundant with itself (two consecutive lines that say the exact same thing in a different way). Thoughts and dialogue that jump back and forth between topics without any sort of transition. Overly vague lines ("All of this happened because he's like that." Like what?) Overly detailed lines ("I hug her from the front"). Lacking vocabulary, especially in H scenes (everything is "happy" and "feels good"). It's problems like these that make you realize the source text is not holy and can - no, should - be rearranged, rephrased, and yes, rewritten to a certain extent. Clarify those vague parts. Cut those redundancies. Reuse space taken up by pointless filler to insert a badly needed topic transition.
Even some actual events in the story may need to be patched. Imagine the following: you're nearing the end of the route. A huge crowd has assembled on the central square to celebrate the MC and his girlfriend. In the middle of thunderous cheering, they draw closer and... she kisses him they kiss each other. Seriously, you can't have such a scene end on a one-sided kiss, especially not if the whole point of the route is that the characters become equals.

I only have this text in portuguese, but if you're interested, I could send it to you. Basically it is about the role of the translator, and how we usually don't have our identity as part of the work, which is not true. The translator has, as long as reason allows, an active role on the writing of a work. There is no such thing as "what the writer thought", because Language is never the same as thought. The author may have an intention when writing, but many factors come along with it, and it is the right of the translator to not simply "change words" to another language, but to make it available in the best way they can, even if it means changing some aspects from the original. As you start wondering about how languages differ and how are culturally spread, you cannot expect translations to be the passage from one to another.
One of the many examples I can think is the portuguese translation of Lolita (I believe in other languages as well), where the sentences in the first chapter have an emphasis on the same sound. If you read it alloud, you can notice the "intention" of the writer to make it happen. However, that was too specific to the wording the author used, so when it was translated, adaptations were necessary and this aspect was in some ways lost. There are MANY different ways, however, to go around this issue, and I'd recommend you (and all people) to read about some translations techniques and how many "problems" can be worked on. 
Btw, this is a request to everybody: start treating traslation as a science; many are spreading here and in other threads very opiniated views on translation, and most of them are innacurate. Translation is not a part-time job, it is not something anyone can do from nothing. It is being studied for decades now, and many things I see here were discussed over and over through the last decades, and it really doesn't take too much time to google it before posting.

I'm glad you specifically mentioned "essence", as in some cases, the author is simply not very good (at least by Western standards) and you do need to make quite some changes to get an enjoyable result. The visual novel I'm currently translating suffers from, among others, the following deficiencies:
Repetition of random words like "city" up to six consecutive times. Narration that's redundant with preceding dialogue (e.g. a character saying "I don't know" followed by narration saying "Apparently she doesn't know"). Narration that's redundant with itself (two consecutive lines that say the exact same thing in a different way). Thoughts and dialogue that jump back and forth between topics without any sort of transition. Overly vague lines ("All of this happened because he's like that." Like what?) Overly detailed lines ("I hug her from the front"). Lacking vocabulary, especially in H scenes (everything is "happy" and "feels good"). It's problems like these that make you realize the source text is not holy and can - no, should - be rearranged, rephrased, and yes, rewritten to a certain extent. Clarify those vague parts. Cut those redundancies. Reuse space taken up by pointless filler to insert a badly needed topic transition.
Even some actual events in the story may need to be patched. Imagine the following: you're nearing the end of the route. A huge crowd has assembled on the central square to celebrate the MC and his girlfriend. In the middle of thunderous cheering, they draw closer and... she kisses him they kiss each other. Seriously, you can't have such a scene end on a one-sided kiss, especially not if the whole point of the route is that the characters become equals.

I'm glad you specifically mentioned "essence", as in some cases, the author is simply not very good (at least by Western standards) and you do need to make quite some changes to get an enjoyable result. The visual novel I'm currently translating suffers from, among others, the following deficiencies:
Repetition of random words like "city" up to six consecutive times. Narration that's redundant with preceding dialogue (e.g. a character saying "I don't know" followed by narration saying "Apparently she doesn't know"). Narration that's redundant with itself (two consecutive lines that say the exact same thing in a different way). Thoughts and dialogue that jump back and forth between topics without any sort of transition. Overly vague lines ("All of this happened because he's like that." Like what?) Overly detailed lines ("I hug her from the front"). Lacking vocabulary, especially in H scenes (everything is "happy" and "feels good"). It's problems like these that make you realize the source text is not holy and can - no, should - be rearranged, rephrased, and yes, rewritten to a certain extent. Clarify those vague parts. Cut those redundancies. Reuse space taken up by pointless filler to insert a badly needed topic transition.
Even some actual events in the story may need to be patched. Imagine the following: you're nearing the end of the route. A huge crowd has assembled on the central square to celebrate the MC and his girlfriend. In the middle of thunderous cheering, they draw closer and... she kisses him they kiss each other. Seriously, you can't have such a scene end on a one-sided kiss, especially not if the whole point of the route is that the characters become equals.

I'm glad you specifically mentioned "essence", as in some cases, the author is simply not very good (at least by Western standards) and you do need to make quite some changes to get an enjoyable result. The visual novel I'm currently translating suffers from, among others, the following deficiencies:
Repetition of random words like "city" up to six consecutive times. Narration that's redundant with preceding dialogue (e.g. a character saying "I don't know" followed by narration saying "Apparently she doesn't know"). Narration that's redundant with itself (two consecutive lines that say the exact same thing in a different way). Thoughts and dialogue that jump back and forth between topics without any sort of transition. Overly vague lines ("All of this happened because he's like that." Like what?) Overly detailed lines ("I hug her from the front"). Lacking vocabulary, especially in H scenes (everything is "happy" and "feels good"). It's problems like these that make you realize the source text is not holy and can - no, should - be rearranged, rephrased, and yes, rewritten to a certain extent. Clarify those vague parts. Cut those redundancies. Reuse space taken up by pointless filler to insert a badly needed topic transition.
Even some actual events in the story may need to be patched. Imagine the following: you're nearing the end of the route. A huge crowd has assembled on the central square to celebrate the MC and his girlfriend. In the middle of thunderous cheering, they draw closer and... she kisses him they kiss each other. Seriously, you can't have such a scene end on a one-sided kiss, especially not if the whole point of the route is that the characters become equals.

Oh, I forgot my biggest gripes:
Less invisible characters. Not drawing so much as a portrait for a character the MC talks with for ten minutes is plain lazy.
Less background reuse. If a route ends with a huge gathering of people in the streets, showing me the same sparsely populated road that I already saw on day one is lazy and disappointing.