Utility, by 
This is the only tool publicly available on J2O (aside from J2E Creator by the same author) that provides the much needed functionality of creating and editing j2e files, so you kind of need it if you want to have custom episode files without writing your own software. So it was received well because it was software we needed. That is not to say it is a good tool for the job.
You open this up and you’re greeted with an awful, awful user interface that is hard to call an improvement over a console application. First thing you’ll do is probably try to open some file, either a j2e or a bmp, you’ll type in the file name (don’t count on a Windows file selection dialog), and you’ll be told that nope, that file doesn’t exist, because you’ve included the file extension like any sane person would do, but J2E Editor actually appends .j2e or .bmp to whatever you type in, so it just tried to open Home.j2e.j2e.
With some effort you get used to that and you load the bitmap you wanted. You know JJ2 uses palettes, so your bitmap already has the menu palette, so all that the software needs to do is take your indexed image and put it in a j2e file. Well, it won’t do that, because your menu palette is not the menu palette it wants. The menu palette it wants is in a file included with the software in a format that nothing opens. If you manage to open it, you can find out that the palette is blatantly wrong. Literally all you have to do to obtain the menu palette from the game is take a screenshot (F12 key) in 8-bit color mode and extract it from the file, so how the author managed to obtain his very discolored version of the palette escapes me. I sort of imagine that he tried to approximate it via trial and error until it more or less looked right.
But that shouldn’t matter, right? It can just take the bitmap, see that it’s indexed, and put it in the file as it is. No, what it will actually do is make sure the provided palette matches exactly, and perform color reduction if it doesn’t. Why? Just why? You take my picture crafted exactly for the menu palette and it’s ready for you to just put directly in a j2e file, all you have to do is zlib it, yet you have to convert it to your crappy wrong palette?
Writing text into prompts relies on key press events rather than character input events, and if you know what those two are, you should be cringing right about now. This means that handy functions like copy/paste will not work, long presses of a key will not produce multiple characters (including that you have to press backspace once for every character you want to delete), and what non-alphanumeric symbol you obtain by pressing a given button is very much dependent on your keyboard layout. Whenever I have to type in something like a dot, I just go through every symbol on my keyboard with and without shift because who knows which one will happen to produce a dot. This is an actual downgrade from a console application.
Oh, and here’s another fun fact, I wondered why I can’t edit the episode’s number in the list. So I looked into the readme, and apparently it’s the only thing that you interact with not by clicking on it like everything else in this program, but by pressing numpad plus and minus keys. Nothing indicates this, you just have to open the readme to find out. It was a matter of adding something like “±” to the user interface and it wasn’t done.
This is terrible software. It’s bad at interacting with the user, and it’s bad at its job of just taking some data and structuring it into a j2e file, but I guess the files it eventually produces are at least correct in the sense that JJ2 opens the j2e files and graphics software can open the bmp files it exports, so it’s not hopelessly useless.
